Dear Joe/Dev team,
A couple of Superfox behaviours were noticed today that I thought were possibly worth raising? I am not clear on the expected level of support for long callsigns, compound callsigns and special callsigns so I am not sure if these are bugs or not. I apologise in advance if these are already known or are not bugs but expected behavior. Software version 2.7.0-rc5 1. I called using a compound call of VK5/VK9CV (calling from the VK mainland) and observed the following sequence: TX1: <K8R> VK5/VK9CV RX: VK9CV K8R -05 <== should I have expected the Superfox to respond with a hashed call here? The QSO was successful but it dropped the compound part of my call. Is this expected behavior? TX3: K8R <VK5/VK9CV> R-13 RX: VK9CV K8R RR73 2. I then called using a special event callsign I have access to here and observed the following: TX1: <K8R> VI60IOTA RX: <.> K8R -07 <== I suspect this was for me but the hash coded response didn't decode by my end. TX1: <K8R> VI60IOTA RX: <.> K8R -07 <== retry of the same - I stopped calling after this and let the exchange time out. 3. Finally I tried using a call with one of the special post characters included: TX1: K8R VK5GR/P PF95 RX: VK5GR K8R -08 <== again it dropped the special format character for /P portable. The QSO was again successful but I was never explicitly acknowledged with my full callsign. TX3: K8R VK5GR/P R-15 RX: VK5GR K8R RR73 For your consideration. I have screen captures of these if they are useful at all to the team. I don't know of course what calls were written to the log files on site at the Superfox and that would be something to check as well. Regards, Grant VK5GR
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
