On 24/01/2019 08:26, t...@gmx.fr wrote:
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
Phil,
your statement that it is impossible to make proper QSOs between two
type B stations is ridiculous, whatever a type B station is. As for PSK
Reporter spotting, see my replies to to Paul when he asked the same
question a couple of days back:
https://sourceforge.net/p/wsjt/mailman/message/36524657/
and also to Lorin, WA1PGB, after a similar query:
https://sourceforge.net/p/wsjt/mailman/message/36525529/
Please remember that the sending a gridsquare is not essential for a
valid QSO, the reason gridsquares are sent with standard callsigns when
calling and replying to CQ messages are largely for use on VHF and above
and on EME paths where location information is critical for aerial
pointing and Doppler calculations. There use on HF is handy and does
enable tools like PSK Reporter to give accurate mapping information but
you can work around that as I have explained.
Most importantly, the changes in the 77-bit protocol related to compound
and non-standard callsigns benefits many current and potential WSJT-X
users. There are a few who will loss some no-essential capabilities but
TBH making QSOs with compound callsigns has never been optimal and for
those with other non-standard callsigns virtually impossible. When there
are strict constraints on a protocol a major rework will mean some
losers but we hope the many winners will make the changes worthwhile to
the community.
73
Bill
G4WJS.
_______________________________________________
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
