|
Post by Neil G0JHC on Jan 22, 2023 7:28:08 GMT
They dont work, even when a station/DXCC worked and logged, still comes up as new DXCC etc.
|
|
|
Post by Arvo ES1JA on Jan 22, 2023 12:42:31 GMT
what was freq and band tag in wsjtx_log.adi? Freq from 40-41 MHz should be decoded as 8m band.
|
|
|
Post by Pat 9A5CW on Jan 23, 2023 9:00:13 GMT
Hi Arvo, if you restart JTDX and you come on 8m band again to work stations, all stations are marked as Non worked... even in the latest release what i am using. 73 Patrik
|
|
|
Post by Neil G0JHC on Jan 23, 2023 11:21:01 GMT
Hi Arvo, here is the wsjt_log.adi file of my last few 8m contacts. As Pat mentions, once you restart JTDX they are marked as not worked again. This only happens on 8m. Hope this helps.
<call:5>ZS6OB <gridsquare:4>KG44 <mode:3>FT8 <rst_sent:3>-17 <rst_rcvd:3>-15 <qso_date:8>20230121 <time_on:6>145630 <qso_date_off:8>20230121 <time_off:6>145714 <band:2>8m <freq:9>40.681394 <station_callsign:4>GR9B <my_gridsquare:6>IO83pq <eor> <call:5>ZS4TX <gridsquare:6>KG30bw <mode:3>FT8 <rst_sent:3>-06 <rst_rcvd:3>-08 <qso_date:8>20230121 <time_on:6>145803 <qso_date_off:8>20230121 <time_off:6>145844 <band:2>8m <freq:9>40.680925 <station_callsign:4>GR9B <my_gridsquare:6>IO83pq <eor> <call:6>ZS6WAB <gridsquare:4>KG46 <mode:3>FT8 <rst_sent:3>-02 <rst_rcvd:3>-01 <qso_date:8>20230122 <time_on:6>115000 <qso_date_off:8>20230122 <time_off:6>115044 <band:2>8m <freq:9>40.681234 <station_callsign:4>GR9B <my_gridsquare:6>IO83pq <eor> <call:6>WM2XAN <gridsquare:4>EN74 <mode:3>FT8 <rst_sent:3>-15 <rst_rcvd:3>-14 <qso_date:8>20230122 <time_on:6>160200 <qso_date_off:8>20230122 <time_off:6>160244 <band:2>8m <freq:9>40.681492 <station_callsign:4>GR9B <my_gridsquare:6>IO83pq <eor>
|
|
|
Post by Arvo ES1JA on Jan 23, 2023 13:53:43 GMT
This is strange, at least I can't repeat problem. I entered those 4 QSO-s as mine into my log ( replaced station_callsign and my_gridsquare) and faked 10 band to 8m band. attached results as pictures
Notifications looks like correct, Most decodes as New CQ Zone Canada is new ITU zone US calls new grid or prefix. also attached my Notification settings.
Then forced all decodes to CQ from ZS6WAB
I would say all is perfect. I believe in Notification settings is not checked by band everywhere or something like that. New call by band checked is essential.
|
|
|
Post by Neil G0JHC on Jan 23, 2023 14:48:41 GMT
Hi Arvo, I will set my settings same as yours and test again, only see 3 or 4 stations a day so it could be a few days. Hard to understand why Pat and I have same issue after restart with stations appearing not worked again. Lets see now we have same notifications. I did not have "per mode" ticked for all options, but cant she why that would cause the issue. Not identical. TU
|
|
|
Post by Pat 9A5CW on Jan 23, 2023 16:07:19 GMT
Hi Arvo, I have worked ZS6OB several times on 8m, exactly 6 times, i was courious and i edited my wsjtx_log.adi and i found that none of them has been logged into that adi file, checked all other worked callsigns and none of them ended into the adif.
Is it possible that the logged QSO stays into the adif only when JTDX is running, if you close it and start again there is no more that data inside the file?
I was using wsjt-x and JTDX for all my QSO's... same bug in both version when logging 8m QSO's ? Did search for also for <BAND:3>8m and still nothing. Btw via UDP all those QSO where logged into my main Logging program Winlog32. 73, Patrik 9A5CW
|
|
|
Post by Arvo ES1JA on Jan 23, 2023 16:34:40 GMT
Sure qso goes into wsjtx_log.adi only when jtdx is running and You pressed ok in logqso window, or enabled auto log in settings. There is no bug because Neil has log entries. Sure if there no entries then Notifications will not work. Neil’s problem my be also in logbook filtering options in Settings/General. I see maybe different station callsign for 8m qso.
|
|
|
Post by Neil G0JHC on Jan 23, 2023 16:57:29 GMT
I think we have two seperate issues here, I dont have a problem logging the QSOs, but I think Arvo has found (my issue). When I operate 8m I change my call in general to GR9B, does JTDX think G0JHC needs it after a restart? Even though I changed the call in general? I will keep my call as G0JHC and see what the results are. Ive not heard any signals today so hard to test so far.
|
|
|
Post by Arvo ES1JA on Jan 23, 2023 17:11:58 GMT
Remove Filter Use current callsign and Use Current grid and all should be OK. I have them set, as I use same file for all my used / callsigns.
|
|
|
Post by Neil G0JHC on Jan 24, 2023 6:36:59 GMT
Thank you Arvo, Id forgot all about the log book filtering option, as you say "no bug" user error, appreciate your patience.
|
|