Date   

Re: DXKeeper Questions

N6MZ Michael Mraz
 
Edited

I was reconciling DXCC verified credits this week and saw the same behavior. When I filtered the log on a DXCC country prefix, if the selected QSO in the filtered list had 00:00:00 as the begin time, the "Changed item in QSO already uploaded to LoTW" appeared immediately. It also appeared every time I selected that QSO again, i.e. when I pushed the |< or >| buttons to move to the top or bottom of the list. DXKeeper v15.9.9.


Re: DXKeeper Questions

Dale Drake
 

The QSO was not uploaded to LoTW when I logged it with WW. 

 

In WW config on the Log tab “Upload to LoTW when logging” was not checked.

 

To upload the QSO to LoTW I right clicked the QSO in DXK and selected “Add entry to QSL Queue (Lotw)” along with several other QSO’s (not logged at 00:00:00) then in the DXK QSL tab I clicked the “Upload to LotW” radio button.  That produced the screen shot I previously uploaded.

 

Additionally if I now click on the subject QSO in DXK I get the popup “ Changed item in QSO already uploaded to LoTW, changed QSO_Begin item in QSO with N1STB at 2021-03-11 00:00:00 on 40M in CW, after completing and saving changes, resubmit this QSO to LoTW”  despite having made no changes to the QSO.

 

 

Dale AA1QD


Re: Satellite Modes

Dave AA6YQ
 

+ AA6YQ comments below

Newer satellite mode-names do use a combination of two letters, representing the up- and down-link band.

As there are: H 15m, T 10m, V 2m, U 70cm, L 23cm, S 13cm, C 6cm, X 3cm, K 1,2cm, Q 6mm

Maybe it might be a good idea to give the user an editable list, if this is not to much to change. This might be a good way to be prepared for any future changes. Of course you might fill a default list as a starter.

+ I have sent you a new version of DXKeeper that if on startup finds a file named SatelliteModes.txt in its Databases folder, loads its Satellite Mode selectors from the satellite modes specified in this file, one line per mode. Otherwise, the Satellite Mode selectors are loaded with the default Satellite Modes made provided in previous versions of DXKeeper.

+ Please let me know now it goes...

73,

Dave, AA6YQ


Re: DXKeeper Questions

Dave AA6YQ
 

+ AA6YQ comments below

I was able to reproduce the similar behavior (QSO logged as 0000z begin & end time) I saw b4. I uploaded a screen shot. I created a fake QSO and logged it with WW.

+ When you logged the QSO with WinWarbler, was the QSO uploaded to LoTW?

73,

Dave, AA6YQ


Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

+ Nor have I, Laurie.

+ Another possibility: the same message conveyed by TCP being delivered more than once. I've never encountered that either, but...

        73,

             Dave, AA6YQ

 


Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

Russ Ravella
 

Ok Dave,

Thanks very much.  I contacted you since I was hearing about the problem from DXK but this is obviously a JTA issue. I’ll contact Laurie and see what he thinks.  Thanks again for diagnosing this !

Have a great evening!
Russ


On Mar 11, 2021, at 7:04 PM, HamApps Support (VK3AMA) <vk3ama.ham.apps@...> wrote:


On 12/03/2021 12:45 pm, Dave AA6YQ wrote:
I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper. 
It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

de Laurie VK3AMA




Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

HamApps Support (VK3AMA)
 

On 12/03/2021 12:45 pm, Dave AA6YQ wrote:
I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper. 
It doesn't. It only ever sends one instruction, no repeats ever.

A zombie JTAlert process running perhaps?

I suggest the OP restarts his PC and see if that corrects the behavior.
FWIW, there have been no other reports of duplicate logging to DXKeeper in the 3 months since JTAlert 2.16.17 was released.

de Laurie VK3AMA




Re: ErrorLog file regarding: [DXLab] Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

Thanks for the errorlog, Russ. It shows that DXKeeper received a directive from JTAlert log a QSO with KG5HTH and submit it to eQSL and LoTW.

2021-03-12 01:15:44.900 > TCPServerModule.DataArrival, ByteCount = 744
2021-03-12 01:15:44.902 > Request = <command:11>eqsllotwlog<parameters:705><CALL:6>KG5HTH<QSO_DATE:8>20210312<TIME_ON:6>011415<TIME_OFF:6>011515<FREQ:9>10.138186<FREQ_RX:9>10.138186<MODE:3>FT8<RST_SENT:3>+13<RST_RCVD:3>+02<GRIDSQUARE:6>EM02wi<LAT:11>N032 21.250<LON:11>W098 07.500<DISTANCE:4>1216<TX_PWR:2>12<COMMENT:49>Test QSO for Dave to debug DXK double log problem<NAME:18>PHILIP R FLINN, II<QTH:11>Morgan Mill<STATE:2>TX<CNTY:8>TX,Erath<ADDRESS:68>Philip R Flinn, II
PO BOX 96
Morgan Mill
TX, 76465
UnitedStates<ANT_AZ:2>85<DXCC:3>291<CQZ:1>4<ITUZ:1>7<CONT:2>NA<APP_DXKeeper_LOTW_MEMBER:1>Y<APP_DXKeeper_EQSL_MEMBER:1>A<SFI:2>78<A_INDEX:1>4<K_INDEX:1>3<APP_DXKEEPER_USER_DEFINED_1:1>Y<MY_GRIDSQUARE:6>DM41LX<OPERATOR:4>KR6W<STATION_CALLSIGN:4>KR6W<QSO_COMPLETE:1>Y<EOR>

The QSO was successfully logged

2021-03-12 01:15:46.104 > ADIF.ImportRecord complete

and then successfully submitted to TQSL for uploading to LoTW:

2021-03-12 01:15:47.840 > TQSL Version 2.5.7 [v2.5.7]
2021-03-12 01:15:47.841 > Signing using Callsign KR6W, DXCC Entity UNITED STATES OF AMERICA
2021-03-12 01:15:47.841 >
2021-03-12 01:15:47.842 > Attempting to upload one QSO
2021-03-12 01:15:47.843 > C:\DXLab\DXKeeper\LotWUpload.ADI: Log uploaded successfully with result:
2021-03-12 01:15:47.843 >
2021-03-12 01:15:47.844 > File queued for processing
2021-03-12 01:15:47.844 > After reading this message, you may close this program.
2021-03-12 01:15:47.845 > Final Status: Success(0)
.

5 seconds later, DXKeeper received a second directive from JTAlert to log the same QSO with KG5HTH, and submit it to eQSL and LoTW:

2021-03-12 01:15:53.395 > TCPServerModule.DataArrival, ByteCount = 744
2021-03-12 01:15:53.395 > Request = <command:11>eqsllotwlog<parameters:705><CALL:6>KG5HTH<QSO_DATE:8>20210312<TIME_ON:6>011415<TIME_OFF:6>011515<FREQ:9>10.138186<FREQ_RX:9>10.138186<MODE:3>FT8<RST_SENT:3>+13<RST_RCVD:3>+02<GRIDSQUARE:6>EM02wi<LAT:11>N032 21.250<LON:11>W098 07.500<DISTANCE:4>1216<TX_PWR:2>12<COMMENT:49>Test QSO for Dave to debug DXK double log problem<NAME:18>PHILIP R FLINN, II<QTH:11>Morgan Mill<STATE:2>TX<CNTY:8>TX,Erath<ADDRESS:68>Philip R Flinn, II
PO BOX 96
Morgan Mill
TX, 76465
United States<ANT_AZ:2>85<DXCC:3>291<CQZ:1>4<ITUZ:1>7<CONT:2>NA<APP_DXKeeper_LOTW_MEMBER:1>Y<APP_DXKeeper_EQSL_MEMBER:1>A<SFI:2>78<A_INDEX:1>4<K_INDEX:1>3<APP_DXKEEPER_USER_DEFINED_1:1>Y<MY_GRIDSQUARE:6>DM41LX<OPERATOR:4>KR6W<STATION_CALLSIGN:4>KR6W<QSO_COMPLETE:1>Y<EOR>

The attempt to submit this QSO to LoTW failed, since it had already been uploaded:

2021-03-12 01:15:55.098 > TQSL Version 2.5.7 [v2.5.7]
2021-03-12 01:15:55.098 > Signing using Callsign KR6W, DXCC Entity UNITED STATES OF AMERICA
2021-03-12 01:15:55.099 > Already Uploaded QSO suppressed on line 5
2021-03-12 01:15:55.099 > CALL: KG5HTH
2021-03-12 01:15:55.100 > TIME_ON: 011415
2021-03-12 01:15:55.100 > QSO_DATE: 20210312
2021-03-12 01:15:55.101 > MODE: FT8
2021-03-12 01:15:55.101 > BAND: 30M
2021-03-12 01:15:55.102 > FREQ: 10.138186
2021-03-12 01:15:55.102 > BAND_RX: 30M
2021-03-12 01:15:55.103 > FREQ_RX: 10.138186
2021-03-12 01:15:55.104 > PROP_MODE: F2
2021-03-12 01:15:55.105 > Signing aborted
2021-03-12 01:15:55.106 > All QSOs are already uploaded; aborted
2021-03-12 01:15:55.106 > No records to upload
2021-03-12 01:15:55.107 > Final Status: No QSOs written(8)

I do not know why JTAlert is sending two "Log QSO" directives to DXKeeper.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

Yeah, it seems like it's suddenly started trying to upload twice but I'm pretty darn sure I haven't touched any settings anywhere. I confirmed the 'Enable' box in SC is unchecked as requested but it would have to always have been unchecked since this has always worked ? What could be going on all of a sudden 1!?!

+ So that I can see what's going on, please do the following

1. on the General tab of DXKeeper's Configuration window, check the "Log debugging info" box

2. terminate DXKeeper

3. start DXKeeper, and wait for it to fully initialize

4. log a QSO with JT-Alert, and wait for this operation to fully complete

5. on the General tab of DXKeeper's Configuration window, uncheck the "Log debugging info" box

6. attach the errorlog.txt file from your DXKeeper folder to an email message, and send the email message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ


Re: Question about spot in FT8

Dave AA6YQ
 

+ AA6YQ comments below

The go QRT response (from me) was an attempt at levity. Sorry you took it literally.

Your problem is that you don't want to see spots of your Callsign from other FT8 users.

You can't force everyone else to turn off their PSKReporter spotting or Cluster spotting, so your only option is to configure
SpotCollector to avoid showing these spots. This is the correct group to get an authoritative answer as to how to do that, assuming
it is possible.

+ If you don't want to Spot Database Entries for your callsign to be created, add your callsign to SpotCollector's "Special
Callsign" list with no tags.

73,

Dave, AA6YQ


Re: Error Logging from JTAlert to DXKeeper

Russ Ravella
 

Hi Dave,

Yeah, it seems like it’s suddenly started trying to upload twice but I’m pretty darn sure I haven’t touched any settings anywhere. I confirmed the “Enable” box in SC is unchecked as requested but it would have to always have been unchecked since this has always worked ? What could be going on all of a sudden 1!?!

Thanks1
Russ

On Mar 11, 2021, at 4:08 PM, Dave AA6YQ <aa6yq@ambersoft.com> wrote:

+ AA6YQ comments below

After about 3 weeks away I just fired things up and there were a couple of s/w updates to DXL and the usual database updates which I installed. Now, when I complete a WSJT-X QSO and log from JTAlert, I receive several error messages/ notifications as follows:

An error box appears saying:
"No QSOs were uploaded to LoTW",
"no QSOs were processed because some QSOs were duplicates or invalid"

Then a Notepad screen appears titled "LoTWResult.txt" with several lines including:
"Already uploaded QSO surpassed on line 5" and further down, "Signing aborted. All QSOs are already uploaded; Aborted", "No records to upload", "Final Status: No QSO written(8)"

Another status box also appears titled "DXKeeper Club Log Upload" which says:
"Upload QSO to Clublog Succeeded: Dupe"

When I click off this later, a second entry for the same QSO is placed in DXKeeper

I checked JTAlert and sure enough there was a newer version which I also installed but it had no effect on the above. I haven changed any settings in any software, or added or deleted any software since before the issue started. I don't see that anyone else has reported this so it must be unique to my configuration. I would very much appreciate some help.

+ I sounds like you have things configured in a way that uploads each new QSO to LoTW and Club Log twice.

+ If you're using JT-Alert, then the Enable box should be unchecked in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window. Is that the case?

73,

Dave, AA6YQ







Re: Error Logging from JTAlert to DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below

After about 3 weeks away I just fired things up and there were a couple of s/w updates to DXL and the usual database updates which I installed. Now, when I complete a WSJT-X QSO and log from JTAlert, I receive several error messages/ notifications as follows:

An error box appears saying:
"No QSOs were uploaded to LoTW",
"no QSOs were processed because some QSOs were duplicates or invalid"

Then a Notepad screen appears titled "LoTWResult.txt" with several lines including:
"Already uploaded QSO surpassed on line 5" and further down, "Signing aborted. All QSOs are already uploaded; Aborted", "No records to upload", "Final Status: No QSO written(8)"

Another status box also appears titled "DXKeeper Club Log Upload" which says:
"Upload QSO to Clublog Succeeded: Dupe"

When I click off this later, a second entry for the same QSO is placed in DXKeeper

I checked JTAlert and sure enough there was a newer version which I also installed but it had no effect on the above. I haven changed any settings in any software, or added or deleted any software since before the issue started. I don't see that anyone else has reported this so it must be unique to my configuration. I would very much appreciate some help.

+ I sounds like you have things configured in a way that uploads each new QSO to LoTW and Club Log twice.

+ If you're using JT-Alert, then the Enable box should be unchecked in the WSJT-X panel on the "Spot Sources" tab of SpotCollector's Configuration window. Is that the case?

73,

Dave, AA6YQ


Re: DXKeeper Questions

Dave AA6YQ
 

* AA6YQ comments below

+ DXKeeper displays that message when it detects that you have made an "LoTW-significant" change to a QSO that has already been submitted to LoTW.

Understood.

+ What actions did you take leading up to the appearance of that message?


I created and ran a new SQL Query Filter to identify CW QSOs with Illinois stations that were not part of a contest: (State='IL') and (Mode='CW') and Contest_ID=''
With the log display so filtered, I scrolled through the listing, and when I came to the one for W9WE, the warning message popped up. I did not make any modifications to the QSO. I don't recall making any modifications to it previously, but of course it has been over nine years since uploading it to LoTW.


+ What is currently shown in the QSO_Begin item of that W9WE QSO?

10/17/2011 00:00
Today I logged into lotw.arrl.org and pulled up the record for that QSO. The only difference in the data is that in LoTW the ITU Zone is listed as 08, and in DXKeeper there is no value assigned for ITU Zone. All other data fields are identical, including the Date/Time 2011-10-17 00:00:00.

* Thanks, Steve! The evidence that you and Dale AA1QD have provided implies that DXKeeper will erroneously warn you to re-submit a modified QSO to LoTW if that QSO's QSO_Begin time item happens to be 00:00:00. I am investigating.

73,

Dave, AA6YQ


Re: DXKeeper: Filtering/Exporting QSO data of QSOs made with members of a club to an ADIF-file

Dave AA6YQ
 

+ AA6YQ comments below

thank you for providing the, so far, non-public version DXKeeper 16.0.5

I just tested the new function "From Callsign File" with the member list of the A1C CW club (Japan).


In "DXKeeper Advanced Sorts, Filter and Modifiers":


After pressing the button "From callsign file" I have chosen the according member list txt-file.

When the scanning process was finished

I defined a SQL-Query filter
"SEL-AWD" by: APP_DXKeeper_SELECT = 'Y'

After pressing the "Filter" button I got 383 QSOs in the DXKeeper Log Page and checking some of the callsigns showed they are members of the A1C.

WOW -- it seems to work as I wanted it to work!

The good news for me is that I now know where I am standing in relation to awards and ranking lists of the A1C club.

I also think this new function will serve for other member lists or in other selection purposes based on a callsign txt-file as well.

+ Thanks for the testing and the report, Tom!

73,

Dave, AA6YQ


Re: Question about spot in FT8

iain macdonnell - N6ML
 

On Thu, Mar 11, 2021 at 12:37 PM Joe Subich, W4TV <lists@subich.com> wrote:
Spotting stations that end in "-#' are RBN nodes. You are being spotted
when the RBN digital nodes see your CQ. There is nothing you can do to
prevent those spots except *NOT* call CQ.
It's not just CQs - (starting a week or so ago) I've been instantly
spotted by these -#'s when I've just been calling DX stations. I very
rarely CQ.

73,

~iain / N6ML


Re: {SPAMFILTER} Re: [DXLab] Question about spot in FT8

Anthony W. DePrato
 

At 03:45 PM 3/11/2021, you wrote:

> I've noticed it within the last week or two too. Apparently some sort
> of connection has been established between automated FT8 spotting
> (maybe PSKReporter??) and the DX clusters.

Yes, someone has turned on a link between the RBN/Digital network and
the general cluster network.

73,

   ... Joe, W4TV


     Joe:
   i just called and worked HP1RY on FT8 14074 and guess what i was spotted my a dozen different - # stations. as being on 20 mts. so guess calling CQ is not the problem.
  73 tony wa4jqs
 
   


Re: {SPAMFILTER} Re: [DXLab] Question about spot in FT8

Anthony W. DePrato
 

Iain:
thanks i think you are correct as i had not seen this until the past week or so. before if i wanted to see my spot i would open the psk reporter page which INHO is still the way to go .
73 Tony WA4JQS


I've noticed it within the last week or two too. Apparently some sort
of connection has been established between automated FT8 spotting
(maybe PSKReporter??) and the DX clusters.

73,

~iain / N6ML


Re: {SPAMFILTER} Re: [DXLab] Question about spot in FT8

Anthony W. DePrato
 

Laurie:
Not a problem i guess it was the way it was worded . things down under and here in the states can have different meaning. No i am not opposed to having someone spot me on the cluster. i just thought I had something set wrong and was self spotting on the dx cluster. i do not think i am seeing spots from another FT8 user since all the source spots are coming from stations with (- # after their calls) so i guess it is a skimmer or a psk reporter spotting me. i know i can go into spot collector and turn a spot with my call sign off . i was more worried about a lot of uncalled for spots on the cluster . Laurie  you have answered my question thank you.

73 Tony WA4JQS / VP8SSI / 3Y0PI / V31SS





The go QRT response (from me) was an attempt at levity. Sorry you took it literally.

Your problem is that you don't want to see spots of your Callsign from other FT8 users.

You can't force everyone else to turn off their PSKReporter spotting or Cluster spotting, so your only option is to configure SpotCollector to avoid showing these spots. This is the correct group to get an authoritative answer as to how to do that, assuming it is possible.

de Laurie VK3AMA
(JTAlert author)


 Virus-free. www.avg.com


Re: Question about spot in FT8

Joe Subich, W4TV
 

I've noticed it within the last week or two too. Apparently some sort
of connection has been established between automated FT8 spotting
(maybe PSKReporter??) and the DX clusters.
Yes, someone has turned on a link between the RBN/Digital network and
the general cluster network.

73,

... Joe, W4TV


On 2021-03-11 3:30 PM, iain macdonnell - N6ML wrote:
On Thu, Mar 11, 2021 at 11:34 AM Anthony W. DePrato <wa4jqs@mikrotec.com> wrote:

i have started seeing this FT8 spot with my call sign show up after
updating WSJT. i know this is dxlab group but i use dxlab as my
logging software. i can call one station and i will see a spot for my
call show up then the Source station will changes maybe 10 times in
the next min.
without me making another transmission.i have looked in both spot
collector and wsjt and turned off all psk and anything that might
cause this spotting. i am thinking it is either skimmers or a rev
beacon. i feel this just add's to the dx cluster over head and not
needed. anyone have any ideal.
I've noticed it within the last week or two too. Apparently some sort
of connection has been established between automated FT8 spotting
(maybe PSKReporter??) and the DX clusters.
73,
~iain / N6ML


Re: Question about spot in FT8

Joe Subich, W4TV
 

Tony,

Spotting stations that end in "-#' are RBN nodes. You are being spotted
when the RBN digital nodes see your CQ. There is nothing you can do to
prevent those spots except *NOT* call CQ.

If you don't want to see RBN spots for digital modes (RTTY, FT8, FT4,
etc.) or CW, in SpotCollector, select Config -> Special Callsigns,
and *Check* "Discard spots from spotting station callsigns ending in -#"

73,

... Joe, W4TV

On 2021-03-11 2:34 PM, Anthony W. DePrato wrote:
Callsign       DXCCCountry                            Freq  Mode FirstTime           Source         Notes
VE7EA          Canada                             18,093.0  CW 2021-11-03 19:10    ZL2IFB         SOTA VE7/CL021
R7KEA          European Russia                    14,074.0  FT8 2021-11-03 19:17    LU4EFC         FT8 QSO TNX!!
4Z5ML          Israel                             14,074.0  FT8 2021-11-03 19:16    LU4EFC         FT8 QSO TNX!!
HC5AI          Ecuador                            14,018.0  CW 2021-11-03 19:15    K6INM          cw heard in ne ca
VE1WAN         Canada                             18,101.0  FT8 2021-11-03 19:15    WB4EHG
EA3HMM         Spain                              14,074.0  FT8 2021-11-03 19:14    LU4EFC         FT8 QSO TNX!!
S51CK          Slovenia                            7,137.0  SSB 2021-11-03 19:14    ZL3CHE         Tnx Ivo / CQ
PQ213CFN       Brazil                             28,406.0  SSB 2021-11-03 19:12    PS7DX          cq
KB1VFU         United States                      18,140.0  SSB 2021-11-03 19:12    W0WOW          1812 miles
EA2K           Spain                              14,245.0  SSB 2021-11-03 19:17    NY6G           59 in CA!
PZ2YT          Suriname                           14,190.0  SSB 2021-11-03 19:12    KT4LR          59 IN FL
KA7GPP         United States                      14,059.0  CW 2021-11-03 19:20    W6LEN          KFF-3208                    WA
WA4JQS         United States                      14,074.0  FT8 2021-11-03 19:19    WA5VAH-#       FT8  -11 dB 1339 Hz         KY
i have started seeing this FT8 spot with my call sign show up after updating WSJT. i know this is dxlab group but i use dxlab as my logging software. i can call one station and i will see a spot for my call show up then the Source station will changes maybe 10 times in the next min.
without me making another transmission.i have looked in both spot collector and wsjt and turned off all psk and anything that might cause this spotting. i am thinking it is either skimmers or a rev beacon. i feel this just add's to the dx cluster over head and not needed. anyone have any ideal.
BTW i asked this on the JTLERT ground and was told i needed to learn how to use my software or go QRT. nice bunch .. wont be going back there.
73 Tony WA4JQS

3201 - 3220 of 203488