RST means Report STrength.I don't see how this fits into the ADIF definition.Is
there some reference which calls for using this field for VHF contests?
And you're correct...JTAlert does not read the wsjtx log file. But they should
agree on the field usage.
de Mike W9MDB
On Wednesday, November 15, 2017, 10:16:22 AM CST, Neil Zampella
<[email protected]> wrote:
Bill,
What may be the problem is not what WSJT-X logs, but what is being sent via the
UDP connection to JT-Alert? I don't believe that JT-Alert actually reads the
log that WSJT-X creates.
In which case it may be a simple change to the UDP payload sent out, and
something that JT-Alert will need be able to read and populate the fields
accordingly.
Again, not quite sure of the mechanism.
Neil, KN3ILZ
On 11/15/2017 10:45 AM, Bill ND0B wrote:
Good morning Mike,
The point is in NA VHF Contest mode there is no signal strength exchanged
because the gridsquares are substituted. I will concur there are fields for
the gridsquare however they are the (usually)six character gridsquares being
filled from what is entered by the user at setup in the case of mygridsquare
and what comes from calls3.txt if I do a lookup or off the air if I do not in
the case of the worked stations gridsquare. As these are usually not what
went over the air they cannot be considered reports. Therefore the four
character gridsquares exchanged over the air ARE the reports. And it is a
requirement of most V/U contests that the grid received be logged. That is
currently not neccesiarily happening without user intervention.
The following WSJTx log entry was from a contact I had the other day using
contest mode. I logged it twice to show the point. In this case I did do a
lookup so the gridquare from K0TPP is from calls3.txt not from off the air.
Here is what WSJTx currently logs. The reports, sent and received never went
over the air. Nor did either gridsqare.
<call:5>K0TPP <gridsquare:6>EM48rj <mode:6>MSK144 <rst_sent:3>+05
<rst_rcvd:3>+05 <qso_date:8>20171114 <time_on:6>110236 <qso_date_off:8>20171114
<time_off:6>110236 <band:2>2m <freq:10>144.151500 <station_callsign:4>ND0B
<my_gridsquare:6>EN07gn <eor>
This is what I beleive should get logged. In this case I manually entered
the gridsquares that were exchanged on the air before logging.
<call:5>K0TPP <gridsquare:6>EM48rj <mode:6>MSK144 <rst_sent:4>EN07
<rst_rcvd:4>EM48 <qso_date:8>20171114 <time_on:6>105930
<qso_date_off:8>20171114 <time_off:6>105930 <band:2>2m <freq:10>144.151500
<station_callsign:4>ND0B <my_gridsquare:6>EN07gn <eor>
73 de Bill ND0B
From: Black Michael [mailto:[email protected]]
Sent: Wednesday, November 15, 2017 7:56 AM
To: [email protected]; Bill ND0B <[email protected]>
Subject: Re: [wsjt-devel] A minor suggestion
Is there someplace that says grids are supposed go into RST_RCVD and RST_SENT?
Don't the grids go into GRIDSQUARE and MY_GRIDSQUARE already?
de Mike W9MDB
On Wednesday, November 15, 2017, 7:01:54 AM CST, Bill ND0B <[email protected]>
wrote:
Good morning and thank you to the development team,
It is starting to be common practice to use NA VHF Contest Mode for MSK
operation on 2m and above. As a consequence those of us who use JT Alert to
automatically log have noticed that the Log QSO feature of WSJTx is reporting
signal strengths in the Rpt Sent and Rpt Rcvd field which JT Alert duly puts
into the log and I would assume (never looked) that WSJTx is putting into its
own log. In order to log what was actually exchanged, the four character
grids, they need to be manually entered into these fields. It would seem that
WSJTx, when in NA VHF Contest mode should be putting what is actually exchanged
for reports, namely the four character grids. Just a thought.
Thanks!
73 de Bill ND0B
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org!
http://sdm.link/slashdot_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
