I have followed up on this reported issue. It appears that because QRZ
only provides for one user account per person I could not test the case
where a non-paying user of its XML API service would attempt to use it
(since I am a paying subscriber). However, based on the documentation, I
believe I have made the necessary modification to detect this condition
and exit out. (I have tested it to the best of my ability.)
The new version is posted to GitHub.
73,
-Dave
On 2/27/2021 4:53 PM, Dave Slotter, W3DJS wrote:
Thank you for reporting this issue. I will investigate it and get back
to you as soon as possible.
Part of my investigation requires how you set up the virtualenv. Can
you please provide the steps you used so I may duplicate it exactly?
On Sat, Feb 27, 2021, 6:39 AM Kari Sillanmäki <[email protected]
<mailto:[email protected]>> wrote:
Dave,
On 26.2.2021 18.48, Dave Slotter, W3DJS wrote:
Fellow hams and users of WSJT-X:
I am pleased to announce the creation and immediate availability
of a Python script to address some of the deficiencies of WSJT-X
not providing a method to automatically look up callsigns and
missing grid squares and fill them in.
<clip>
The Python script, update_wsjtx_log.py may be located and
downloaded from here:
https://github.com/dslotter/ham_radio_scripts/blob/main/update_wsjtx_log.py
<https://github.com/dslotter/ham_radio_scripts/blob/main/update_wsjtx_log.py>
I tested your script on "Ubuntu 18.04.5 LTS" using Python 3.6.9
under virtualenv. It seems that the script is not working
correctly. I worked a DM station whose information looks good on
QRZ.com. Yet, the script spat out: ______ Parsing log entry from
WSJT-X... Requesting callsign information... 200 OK *Error* *=
'name_fmt'* Writing Log entry: ______ The log entry written was
the same as from WSJT-X but with two additional fields of zero
lengt: "<name:0> <operator:0>" Below is the screen output ( with
the other station's callsign masked ... ) 73's de Kari, oh2gqc
Screen output:
***************************************************** * WSJT-X Log
Updater written by Dave Slotter, W3DJS *
*****************************************************
Authenticating to QRZ.com... 200 OK WSJT-X logfile current size:
370593 Waiting for additions to WSJT-X logfile... Modified WSJT-X
logfile. WSJT-X logfile new size: 370890 Got log entry:
<call:5>***** <gridsquare:4>JO62 <mode:3>FT8 <rst_sent:3>-06
<rst_rcvd:3>-18 <qso_date:8>20210227 <time_on:6>110600
<qso_date_off:8>20210227 <time_off:6>110700 <band:3>60m
<freq:8>5.357745 <station_callsign:6>OH2GQC
<my_gridsquare:6>KP20IF <tx_pwr:2>30 <comment:25>FT8 Sent: -06
Rcvd: -18 <eor> Parsing log entry from WSJT-X... Requesting
callsign information... 200 OK Error = 'name_fmt' Writing Log
entry: <call:5>***** <gridsquare:4>JO62 <mode:3>FT8
<rst_sent:3>-06 <rst_rcvd:3>-18 <qso_date:8>20210227
<time_on:6>110600 <qso_date_off:8>20210227 <time_off:6>110700
<band:3>60m <freq:8>5.357745 <station_callsign:6>OH2GQC
<my_gridsquare:6>KP20IF <tx_pwr:2>30 <comment:25>FT8 Sent: -06
Rcvd: -18 <name:0> <operator:0> <eor> WSJT-X logfile current size:
370912 Waiting for additions to WSJT-X logfile...
_______________________________________________
wsjt-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wsjt-devel
