If this only occurs for ft8 qso, then JT alerts is likely directing dxkeeper to upload each qso to lotw... This is a dxkeeper setting in jtalerts settings .. In jtalerts, Open settings -> logging ->dx

Filter the log to the contest dates before exporting the adif....

Pretty certain this gets updated in the eqsl app....

You are correct, but this curious datapoint: It doesn't happen below about 1500 or so on the WSJT-X waterfall. Which has seemingly been disproven...

Wait. So the radio does not change, but the commander display does? Wow. Maybe commander IS losing cat comms to the radio? I think I misread the description. I understood the RADIO changed. Ok, maybe

I would be surprised if it truly IS rf on the cat cable since this look very much like a CAT command to adjust the frea. I'd think rf on the cat cable would create a CAT error by disrupting the commun

Do you RIT (clarifier in Yaesu...) enabled and tuned on the rig? If so, the tx freq will change as RIT gets removed for TX....

You don't need to do it that way. Using work spaces is recommended. This allows configuring 1 workspace for each callsign... Then swap between workspaces to change callsigns.

what "rig" is selected in WSJT-X setting radio tab? It should be DX Labs Suite Commander

Al, you are correct. I had recalled incorrectly. it is right below the "upload each QSO" checkbox I had reference below... same for the EQSL.cc tab....

here is the place in the wiki that describes this upload operation: http://www.dxlabsuite.com/dxlabwiki/AutomaticLotWUpload yes, you can change this from upload each logged qso from the capture window

How does commander and wsjt cat commands get arbitrated? Might be better to connect wsjt to commander to avoid cat command contention and collisions. Dave told me a port splitter to connect wsjt and C

did you try "load settings from workspace" after you saved the workspace? I don't recall setting any option to get the WS to show in launcher window... ki4us

I think you missed the radio cat address as the way byte.. I think it is 94 You did not have a byte for CAT1hex in the n1mm sequence

did you try clicking the "X" (close box) to the right of the text box entry fielsdin the filter window at the bottom of dxkeeper to unfilter the log?

ok. commander does NOT talk to radio in this config. satpc32 talks to BOTH the radio AND commander.... so satpc32 needs to be set to the COM port of the radio.. you should be able to work sats with Co

are you sure its DDE to the radio? I know its DDE to Commander, but I suspect the radio is a COM port so 0 would not work... what com ports show in device manager? does a com port disappear if you tur

I'll try that. The satpc32 com port I did not see a change, so its not configured. Thanks!

1st and most importantly, THANKS!! the capture window populates well. I seem to have a couple of odd things with the serial port controlling the radio. if I open satpc32, and get it connected to the r

On the edge of my seat now waiting... :=D