+ AA6YQ comments below

Very pleased to see this discussion. Sometime back I used a Yeasu FT-920 with SignalLinkUSB to the mike port and worked fine. Recently decided to get back active again but decided to switch to the data port to free up mike and to start using DxLab Suite. Although the FT-920 is in DATA mode, after transmitting, the 920 changes to USB.

+ Does the post-TX switch from DATA to USB happen if Commander is not running?

73,

Dave, AA6YQ

+ AA6YQ comments below

This may have to do with updates from LoTW. I was told that I only really needed to update my latest call sign with LoTW unless I was entering more Q's from paper logs.

+ What do you mean by "update my latest callsign with LoTW"?

Yes, I may do that someday but I just want to make sure that I have everything I already have at 100%.

I don't know how it happened but just about all of my QSO's, going back to 1982, have myQTH changed to my current QTH. For DXCC and WAZ purposes, it won't matter (I'm still in Zone 5) but I am (a) curious as to how this could have happened

+ You evidently directed DXKeeper to make those changes; it cannot make such changes autonomously.

and (b) wondering if I could correct this data -- or would it mess up LoTW?

+ You should correct your logged QSOs to specify the correct "my QTH". Each "my QTH" should specify the associated "LoTW Station Location".

+ See

<https://www.dxlabsuite.com/dxlabwiki/LotWMultipleCallsignsLocations>;

73,

Dave, AA6YQ

+ AA6YQ comments below

Hi Dave,
Let me look again for the radio settings for baud rate, parity, word length, and stop bits that match your radio's settings.

I'm not sure what to make of this:


a. set the RTS selector to On unless you're using a Kenwood TS-890's USB interface, in which case the RTS selector should be set of Off

b. if an external interface is being used and it derives its power from the serial port's DTR modem control signal, set the DTR selector to On

I think the 'external interface; is the MicroHAM unit, so DTR is On?

+ Since you're using a microHam interface, I will defer to Joe W4TV.

73,

Dave, AA6YQ

The only differences between the DXLab Suite and N1MM+ configurations
are in the CW/PTT settings and are due to the differences in the way
DXLab Suite and N1MM+ do CW/FSK.

73,

... Joe, W4TV

Joe, I have DTR Off (there is not an option for None,)

OK, I was working from memory. Off is fine.

the RTS choices are Off, On, Tx and Flow. Should I use Tx?

Yes, if you are using Commander for PTT. See the example
configuration for USB Interface II with DLab Suite is the
USB II area at www.microHAM-USA.com/Support.html.

73,

... Joe, W4TV


On 2020-06-15 3:26 PM, Steve wrote:

Joe, I have DTR Off (there is not an option for None,) and the RTS choices are Off, On, Tx and Flow. Should I use Tx?

This may have to do with updates from LoTW.  I was told that I only really needed to update my latest call sign with LoTW unless I was entering more Q's from paper logs.  Yes, I may do that someday but I just want to make sure that I have everything I already have at 100%.

I don't know how it happened but just about all of my QSO's, going back to 1982, have myQTH changed to my current QTH.  For DXCC and WAZ purposes, it won't matter (I'm still in Zone 5) but I am (a) curious as to how this could have happened and (b) wondering if I could correct this data -- or would it mess up LoTW?

Thanks!

Steve, W1ES/4

Hi Dave,
Let me look again for the radio settings for baud rate, parity, word length, and stop bits that match your radio's settings. 

I'm not sure what to make of this:

1. set the RTS selector to On unless you're using a Kenwood TS-890's USB interface, in which case the RTS selector should be set of Off

2. if an external interface is being used and it derives its power from the serial port's DTR modem control signal, set the DTR selector to On
   
   I think the 'external interface; is the MicroHAM unit, so DTR is On?
   Thanks,
   Steve
   

Joe, I have DTR Off (there is not an option for None,) and the RTS choices are Off, On, Tx and Flow. Should I use Tx?

I do not think I do, as there seems to be disagreement in the suggestions in the MicroHam setup for N1MM+ vs DxLabSuite. Currently in Commander config, Port 5, 4800, 8, N, 2 stop bits, DTR Off, RTS On. When I left it earlier the command port was 2. That switch is a first.

do you have the RTS/CTS flow control options set correctly?

microHAM USB Interface II does not pass RTS/CTS. The radio RTS
line is held high ("always on") by the hardware. The UART RTS
and DTR "outputs" are used for PTT and CW respectively.

In Commander one would set DTR to None (PC Generated CW is not
available with Commander) and set RTS to "X" (use for PTT).

In WSJT-X one would set DTR to None and use RTS on the same
COM port as CAT (but preferably not CAT commands). Without
looking at "File -> Settings" Handshake should be "none",
PTT Method = RTS and Port should be the same as "Serial Port"
in CAT Control.

73,

... Joe, W4TV


On 2020-06-15 1:09 PM, g4wjs wrote:

On 15/06/2020 14:58, Steve wrote:

MicroHAM USB Interface II is operating correctly, but Commander does not reflect the radio frequency, or anything else. Any suggestions?

Thanks,
Steve W1LV

Hi Steve,
do you have the RTS/CTS flow control options set correctly?

+ AA6YQ comments below

On Mon, Jun 15, 2020 at 10:09 AM, g4wjs wrote:

On 15/06/2020 14:58, Steve wrote:

MicroHAM USB Interface II is operating correctly, but Commander does not reflect the radio frequency, or anything else. Any suggestions?

Thanks,
Steve W1LV

Hi Steve,

do you have the RTS/CTS flow control options set correctly?

+ Step-by-step configuration instructions are here:

<https://www.dxlabsuite.com/dxlabwiki/TranceiverControlKenwood>

        73,

                Dave, AA6YQ

On 15/06/2020 14:58, Steve wrote:

MicroHAM USB Interface II is operating correctly, but Commander does not reflect the radio frequency, or anything else. Any suggestions?

Thanks,
Steve W1LV

Hi Steve,

do you have the RTS/CTS flow control options set correctly?



--
73

Bill

G4WJS.

MicroHAM USB Interface II is operating correctly, but Commander does not reflect the radio frequency, or anything else. Any suggestions?

Thanks,
Steve W1LV

Here is part of the error log:
2020-06-15 13:46:11     > CI-V Commander version 14.6.2
2020-06-15 13:46:11     > App.Path          : C:\DXLab\Commander
2020-06-15 13:46:11     > App.exe           : CI-V Commander
2020-06-15 13:46:11     > Module            : C:\DXLab\Commander\CI-V Commander.exe
2020-06-15 13:46:11     > Operating System  : Windows 10 Enterprise (64-bit) build 18363
2020-06-15 13:46:11     > Locale ID         : 1033 (0x409)
2020-06-15 13:46:11     > ANSI CodePage     : 1252
2020-06-15 13:46:11     > OEM CodePage      : 437
2020-06-15 13:46:11     > Country           : United States
2020-06-15 13:46:11     > Language          : English
2020-06-15 13:46:11     > DecimalSeparator  : .
2020-06-15 13:46:11     > ThousandSeparator : ,
2020-06-15 13:46:11     > DXLab Apps        :
2020-06-15 13:47:19     > Monitors          : 1
2020-06-15 13:47:19     > Monitor 1
2020-06-15 13:47:19     >    width          : 1707
2020-06-15 13:47:19     >    height         : 960
2020-06-15 13:47:19     >    dimensions     : (0, 0)-(1707, 960)
2020-06-15 13:47:19.133 > CIVModule.PollXcvr, Idle Mode = 2, PollCount = 52
2020-06-15 13:47:19.149 > CIVModule.SendCommand: IF;

I wasn't sure what I had done to create the enormous queue that I had.  Some of the QSO's went into the 1980's.  It may have been my wanting to add needed ones back 13 years ago.  Since then, I've had a lot of updating on LoTW and reckoned that many of the card requests would have been confirmed electronically.  At any rate, clearing them out is what I wanted to do.  I'll do another "Add Needed" once I get LoTW sorted out at the Newington end.

Thanks for all your help.

'ES

+ AA6YQ comments below

On Sun, Jun 14, 2020 at 05:20 PM, wb6bee wrote:

Instead of letting Launcher load the before, DXL and after programs automatically, I loaded them manually, one at a time watching CPU consumption on Launcher.   It always came to Zero.

One of the programs is Alex's CW Skimmer.   I started CW Skimmer and Launcher went to 1.5 % cpu consumption.   I stopped CW skimmer (not terminated, just stopped it) and Launcher CPU went to 0%.    Cycled that a few times and that is the issue.    

Not sure why Launcher wants to do something when CW Skimmer is running

To complete the test, instead of using Launcher to start CW Skimmer, I just started from the EXE program.   

Without using Launcher to start CW skimmer, Launcher sets at 0 % CPU, even with CW skimmer running.   

Something about using launcher to start CW skimmer, when CW skimmer is running, Launcher is consuming

+ When directed to Launch a non-DXLab application, the Launcher directs Windows to start it; that's all the processing the Launcher does. There is no post-start monitoring or any other activity.

+ When I configure the Launcher to start CW Skimmer, the Windows 7 Task Manager shows the Launcher's CPU consumption to be 0.

+ Try rebooting Windows into "Safe mode with networking"; does the Launcher still consume CPU time after starting CW SKimmer?

        73,

             Dave, AA6YQ

 

 

Not yet Dave.

Doing arrl vhf contest all weekend.

73 doc n4ww

+ AA6YQ comments below

Yes they print well.

+ Did you follow the recommended steps in this post?

<https://groups.io/g/DXLab/message/194417>;

73,

Dave, AA6YQ

Yes they print well.

doc n4ww

+ AA6YQ comments below

I have been off the air for quite a while putting up a new tower and antenna.

Today opened DXLab to update what I have missed. I'm told "Unable to open LOTW database Unrecognized Database Format C:\dxlab\dxview\databases\LOTW.mdb".

Sounds like something happened while OTA.

+ No DXLab application attempts to modify the LoTW database; with respect to this database, they are all "read only".

+ So I can see what happened to your LoTW database, please place the file

C:\dxlab\dxview\databases\LOTW.mdb

+ in a zip archive, attach the archive to an email message, and send the message to me via

aa6yq (at) ambersoft.com

+ Then do the following:

1. terminate DXView, DXKeeper, and SpotCollector

2. delete the file

C:\dxlab\dxview\databases\LOTW.mdb

3. on the Databases tab of DXView's Configuration window, direct DXView to install the LotW database

73,

Dave, AA6YQ