+ AA6YQ comments below

I recently processed a batch of DX QSLs and noticed an annoying behavior when editing the "receive" and "send" window. I set "rcvd" to "Y" and :"sent" to "R" to enter a QSL I received and set up for a return QSL. When I hit the SAVE button, the boxes reverse to "R" for "rcvd" and "Y" for "sent". I would then have to redo the selections to fix the problem. The problem occurs randomly, usually with multiple QSOs for the same QSL.

+ Assuming you're referring to the "sent" and "rcvd" selectors in the QSL panel on the Main window's "Log QSOs" tab, I am unable to replicate this behavior, nor did a review of the relevant source code reveal a way for it to occur; this doesn't mean there isn't a latent defect.

+ The next time you receive a QSL card confirming multiple QSOs, please check the "Log debugging info" box on the Configuration window's General tab.

+ After processing those new confirmations, un check the "Log debugging info" box on the Configuration window's General tab. If the misbehavior occurred, please attach the errorlog.txt file from your DXKeeper folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

+ If the misbehavior did not occur, delete the errorlog.txt file from your DXKeeper folder, and wait for the next QSL card confirming multiple QSOs so you can repeat the process.

+ Thanks!

73,

Dave, AA6YQ

Found it.  I had changed tthe udp port for jt alert.  changed it back all ok I think
Thanks for trying to help.


--
Norm WA4ZXV EM64or

+ AA6YQ comments below

not sure the name, but dxKeeper no longer shows the callsign of station selected to call Nor does it sho up in Pathfinder.

+ As reported here earlier,

https://groups.io/g/DXLab/message/214042

+ QRZ.com was down this afternoon (east coast time), and only recently resumed service. Try again.

+ Take a look at the QRZ.com panel on the Configuration window's Callbook tab; you may have the "QRZ.com timeout" set longer than appropriate.

73,

Dave, AA6YQ

+ AA6YQ comments below

I am seeing something I do not believe I have seen before.

If I scroll to a QSO, select it and modify, for instance, its QSL properties, the second I press Save, the log scrolls to the most recent QSO in the log. It is extraordinarily annoying.
Is there a setting that could cause this? I am not aware of changing anything.

+ DXKeeper 17.0.7 included this defect repair:

- after logging a QSO via the Main window's "Log QSOs" tab, correctly sorts the Log Page Display when the sort order is set to "descending"

(first item in https://www.dxlabsuite.com/dxkeeper/ReleaseNotes/1707.txt )

That defect repair is responsible for the behavior you're reporting. I have modified the next version of DXKeeper to only sort the Log Page Display after logging a new QSO, and sent it your way.

Please let me know how it goes…

Dave

not sure the name, but dxKeeper no longer shows the callsign of station selected to call
Nor does it sho up in Pathfinder.

I believe I've followed the instructions, but it still doesn't work

Worked this morning and for the other 11,000 qso's before now.


--
Norm WA4ZXV EM64or

+ AA6YQ comments below

On my 6400M I have a Tune button that that will key the rig with audio at 15w which I use to tune my HF-Auto on different antennas and bands.

I would like a button like that in Commander.

+ the command to set your 6400M's RF output power 15 w is

~transmit set rfpower=15

+ the command to set your 6400M's slice 0's mode to RTTY is

~slice s 0 mode=rtty

+ the command to make your 6400M's slice 0 transmit is

~slice s 0 tx=1 dax=1

+ the command to make your 6400M's slice 0 receive is

~slice s 0 dax=1

+ An example of a user-defined command that toggles between two states - in this case toggling between two antenna selections - is here:

https://groups.io/g/DXLab/files/Command%20Sequences%20and%20Sliders/FlexRadio/6000%20series/FlexSig%20SelAnt.txt

+ Try converting the "toggle between two receive antennas" sequence to a sequence that toggles between these two states:

* transmitting 15 watts in RTTY

* not transmitting

73,

Dave, AA6YQ

On my 6400M I have a Tune button that that will key the rig with audio at 15w which I use to tune my HF-Auto on different antennas and bands.

I would like a button like that in Commander.

73 de NS9I

WORKED BEFOREI TRIED TO ADD JTALERT.  AFTER GIVING UP ON JT ALERT, I LOST MY connectivity LINK
Any help appreciated.

--
Norm WA4ZXV EM64or

Its not the fault of JTAlert you have a Windows permission issue that is blocking UDP comms between JTDX and JTAlert.

Until you sort out why you have permissions problems you will not be able to get SpotCollector <-> JTDX to work either.

Possible causes have been posted to your HamApps posting.

de Laurie VK3AMA
(JTAlert author)

+ AA6YQ comments below

I'm sorry I was not clear... my DXCC credit is for DA and the QSO in DXKeeper is labelled DL in DXLab. I will reference your section on deleted entities to solve this.

+ Then the correct action is to change the DL6VP QSO's DXCC entity from "Federal Republic of Germany" [country code 230] to "Germany (deleted)" [country code 81]; then the "DXCC Credit Manager" should enable you to link your "Germany (deleted)" Credit to your DL6VP QSO.

I have lots of "credits" with only a DXCC entity and no band/mode or QSO info whatever. Those have ended up marked as duplicates, unless I have adequate QSOs to cover all the other credits for that band/mode.

Working with the Credit Manager, listing all unlinked credits, I first look for an entity "credit" that contains entity, band and mode. (I have quite a few that are entity-mode without a band.) Since I cannot assign more than one credit to a QSO (which is what actually happened) I look for one of the credits for that entity issued after ARRL started recording band and mode with the credit. Then I look for a QSO with the required "credit" info to link. I then mark all other credit(s) as duplicates.

+ That's all correct, Dave.

I think that is what you meant to use as a decision tree. Mark credits duplicate which are covered by later credits with more info.

I doubt that having an incorrect QSO linked to an entity credit that happened 30 years ago will negatively affect DXLab or DXKeeper operation. There won't be many of these in the log. And DXLab should then correlate with ARRL with regard to my DXCC progress.

+ It should be possible to link the "Germany(deleted)" credit to your "Germany(deleted)" QSO. If not, please let me know.

73,

Dave, AA6YQ

+ AA6YQ comments below

Sorry, forgot to answer your question. Yes, I am using DXKeeper's "DXCC Credit Manager".

I have many cases where I sent in a card multiple times for credit.  First was country, then it went in for mode and lastly for band.  Each of those trips resulted in a credit.  So I am making many of those credits duplicates and linking one of the same QSOs with a credit having more data eg band and/or mode.

I hope this is an OK approach.

+ You should link the QSO to the DXCC Credit that specifies the Band, and mark the "Entity only" Credit as a duplicate.

+ Do you have a DXCC Credit for "deleted Germany" (country code 81) ? If so, that's the Credit to link to your DA QSO.

       73,

             Dave, AA6YQ

-- 
vy 73, Dave, w0rx

If you have the Callbook tab of DXKeeper's Configuration window configured to use either of the two QRZ callbook services, click the None box in the tab's upper-left corner until service is restored. After re-enabling Callbook lookups via QRZ in DXKeeper, any QSOs you log between now and then can be updated "en masse" by filtering the Log Page Display with the appropriate time range and then clicking the CBA button above the Log Page Display on the Main window's "Log QSOs" tab.

       73,

            Dave, AA6YQ

+ AA6YQ comments below

WORKED BEFOREI TRIED TO ADD JTALERT.  AFTER GIVING UP ON JT ALERT, I LOST MY connectivity LINK

+ What's a "Connectivity Link"?

+ Step-by-step instructions for using DXLab with JTAlert are here:

https://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModesWithJTAlert

     73,

          Dave, AA6YQ

 

 

WORKED BEFOREI TRIED TO ADD JTALERT.  AFTER GIVING UP ON JT ALERT, I LOST MY connectivity LINK
Any help appreciated.

--
Norm WA4ZXV EM64or

+ AA6YQ comments below

Well thank you for the response Dave ... that is all way beyond me so guess I'll live without it.\

+ What is it that you are seeking to do?

73,

Dave, AA6YQ

+ AA6YQ comments below

I didn't think a local spot was supposed to involve any clusters. My spot Source Status lights are in the top margin is that what you're asking about? I don't have anything in the right margin.

+ So that I can see what's going , please

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

2. Make a local spot of my callsign

3. On the Configuration window's General tab, uncheck the "Log debugging info" box

4. Attach the errorlog.txt file from your SpotCollector folder to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ

I missed the part about the config page. Sorry. Yes the cluster is checked and highlighted.

Julio

Well thank you for the response Dave ... that is all way beyond me so guess I'll live without it.

thank you again 73 Dwight NS9I

I didn't think a local spot was supposed to involve any clusters. My spot Source Status lights are in the top margin is that what you're asking about? I don't have anything in the right margin.

Julio