Re: [wsjt-devel] FW: WSJT-X V2.0.0 WINDOWS 10 REPORT

[Bill Somerville]

On 22/01/2019 23:46, Bill Somerville wrote:

On 22/01/2019 23:42, Bill Somerville wrote:


For example after a QSO you could send:

G4WJS  QG61


Hi Paul,

also if you want a generic message to store as a Tx5 macro you can use:

DE  QG61

73
Bill
G4WJS.


Hi Paul,

just to confirm, I have just checked both of those messages with WSJT-X 
v2.0.0 in FT8 mode and can conform they will be spotted to PSK Reporter 
including your gridsquare.


73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FW: WSJT-X V2.0.0 WINDOWS 10 REPORT

[Bill Somerville]

On 22/01/2019 23:42, Bill Somerville wrote:


For example after a QSO you could send:

G4WJS  QG61


Hi Paul,

also if you want a generic message to store as a Tx5 macro you can use:

DE  QG61

73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

Re: [wsjt-devel] FW: WSJT-X V2.0.0 WINDOWS 10 REPORT

[Bill Somerville]

On 22/01/2019 22:47, Paul Randall wrote:
I am operating as VK2/G3NJV and discover that because I am a type B 
callsign, I cannot include my callsign and QRA locator in a single 
message. This in turn prevents anyone using WSJT-X V2.0.0 from 
reporting to PSK Reporter. I have spoken to Philip Gladstone about 
this and he confirms that the current version requires callsign and 
locator in a message before reporting.


Hi Paul,

with the new WSJT-X 2.0.0 FT8 (and MSK144) 77-bit protocol that's not 
quite correct. There is no longer any distinction between type 1 and 
type 2 compound callsigns, all compound and other non-standard callsigns 
that can be encoded are treated equally.


You certainly can send a standard message including your gridsquare, 
there is a limitation in that your callsign must be sent as a hash code 
but that is fine so long as your full call has been sent in a prior 
message. For example after a QSO you could send:


G4WJS  QG61

I need to check that when received this message is spotted to PSK 
Reporter, it may not be but that can be fixed.


Note that:

 VK2/G3NJV QG61

is not a valid standard message and will be truncated.

73
Bill
G4WJS.

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel

[wsjt-devel] FW: WSJT-X V2.0.0 WINDOWS 10 REPORT

[Paul Randall]

Sent from Mail for Windows 10


From: Paul Randall
Sent: Wednesday, January 23, 2019 9:38:41 AM
To: wsjt-devel@lists.sourceforge.net
Subject: WSJT-X V2.0.0 WINDOWS 10 REPORT

Hi, I am operating as VK2/G3NJV and discover that because I am a type B 
callsign, I cannot include my callsign and QRA locator in a single message. 
This in turn prevents anyone using WSJT-X V2.0.0 from reporting to PSK 
Reporter. I have spoken to Philip Gladstone about this and he confirms that the 
current version requires callsign and locator in a message before reporting.

Using V1.9 there was not this problem. Monitor stations using Red Pitaya 
software also do not have this problem and these are the only reception reports 
that I can get – perhaps a dozen globally.

This seems a particularly harsh outcome for type B callsign holders who, like 
me, are often operating portable stations with makeshift antennas where 
reception reports are extremely valuable. I’m sure it would only take a line or 
two of code to allow class B callsigns to be reported without the QRA 
information, as Red Pitaya does.

Many thanks for your attention.
Paul Randall
G3NJV

Sent from Mailfor Windows 10

___
wsjt-devel mailing list
wsjt-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wsjt-devel