Hi Phil It says in the WSJT v2 user guide section 7.5 “WSJT-X 2.0 offers no support for two nonstandard callsigns to work each other” so this is a well known limitation.
I do not understand the logic that WSJT does not give reception reports to PSK reporter unless a QRA and callsign exist in a single message whereas all QSOs made with my type B callsign are valid without any QRA locator information being exchanged at all? I wonder if anyone else has experienced what I call “callsign hijacking” where mid way through a QSO you start transmitting the wrong “other station” callsign. The message boxes are all filled correctly yet the wrong callsign appears to be transmitted and brings the QSO to a halt. Restarting the program and abandoning the QSO seems to be the only way to stop it. Presumably this is an unwanted result of using hash codes. As it stands v2.0.0 does a lot for “normal” callsign holders but is really quite tricky if you have a type B callsign. I have used FT8 a lot whilst operating from Australia with simple wire antennas and it has allowed me to work around the globe. However, tuning across 17m this evening the band was absolutely empty - until I hit 18100 and the S meter almost hit the stops. For a weak signal mode there are a lot of powerful stations crowded into that 3kHz and I felt sad the popularity of FT8 seems to have emptied the band of SSB stations. Paul G3NJV Sent from Mail<https://go.microsoft.com/fwlink/?LinkId=550986> for Windows 10 ________________________________ From: t...@gmx.fr <t...@gmx.fr> Sent: Thursday, January 24, 2019 7:26:59 PM To: wsjt-devel@lists.sourceforge.net Cc: wsjt-devel@lists.sourceforge.net Subject: Re: [wsjt-devel] WSJT Reporting to PSK Reporter Hi, Paul, I have the same issue when I use the call ZS1/F5FDV. Since december last year I was wondering why I get only few reports from PSKReporter. Your post provides a very relevant the explanation, in my opinion. Reporting went well with revisions prior to 2.0. It seems consistent with the statement that it is now impossible to make proper QSO between two type B stations (see previous posts from me to the group). I think that there is a weakness in the coding or decoding of type B call signs. Decoding maybe, because reporting of these stations by WSJT-X to PSKReporter do no happen. 73, Phil F5FDV Envoyé: jeudi 24 janvier 2019 à 03:50 De: "Paul Randall" <paulfrand...@hotmail.com> À: "wsjt-devel@lists.sourceforge.net" <wsjt-devel@lists.sourceforge.net> Objet: [wsjt-devel] WSJT Reporting to PSK Reporter Hi, I got this address from the WSJT website. I am new to this group and not sure of the protocols. I tried emailing yesterday but am unsure if this was received. I am operating as VK2/G3NJV. After upgrading to v2.0.0 I found reports of my transmissions almost disappeared from PSK Reporter. I now get just a handful of reports all from stations NOT using WSJT. Most of these come from stations using “Red Pitaya FT8 TRX 1.0”. I spoke to Philip Gladstone about this and he told me that WSJT does not send reception reports to PSK Reporter unless it receives callsign and locator in a single message. It is impossible for me to transmit a message like this. Because I have a type B callsign, all that will fit in a single message is “CQ VK2/G3NJV” This seems a particularly harsh outcome for type B callsign holders upgrading to v2.0.0. who, like me, are often operating portable stations with makeshift antennas where reception reports are extremely valuable. The reports from stations using a Red Pitaya are perfectly acceptable and I’m not sure of the reasoning behind the current WSJT “callsign + QRA” rule. Would it be possible to modify this to allow reception reports for type B callsigns received without a QRA? Many thanks for your attention. Paul Randall G3NJV PS After completing this email I checked the PSK Reporter website again. Sure enough there were just 5 reception reports, four from monitors using Red Pitaya but also a single report from K1HTV using WSJT-X v2.0.0 784f75. This is the only WSJT reception report seen since 10 December so now I’m not sure what is going on! _______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
_______________________________________________ wsjt-devel mailing list wsjt-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wsjt-devel
