Date   

Re: Commander not recognizing Kenwood TS-440SAT

Steve
 

I believe I have the USB Interface II and DxLab working together. One of the programs had the baud rate at 9600, where the IC-10 kit in the TS-440S needs 4800. I was a little concerned with having RTS On, because the PTT light in the USB Interface came on and stayed on, however, the radio was not transmitting. Spot Collector is working, too.

I am going to try and get N1MM+ working with them now, but that appears to need a different setting for RTS, which I don't understand yet.

Dave, Joe, thank you for your help.
73 Steve W1LV


Re: DXLabs, WSJT-X (ft8) and Yaesu FT-950

g4wjs
 

Hi Jack,

with respect to WSJT-X, ensure that you have the option "Settings->Radio->Mode->Data/Pkt" checked.

73
Bill
G4WJS.

On 16/06/2020 01:44, Jackson McNees wrote:

Bill,

 

This is with WinWarbler and WSJT-X connected through Commander.

 

Jack

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of g4wjs
Sent: Monday, June 15, 2020 7:36 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLabs, WSJT-X (ft8) and Yaesu FT-950

 

On 15/06/2020 22:29, Jackson McNees wrote:

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.  Looked high and low through Commander docs to see if something there but found nothing.  Based on this discussion, will have to see if I have to set up a command sequence to change mode after transmitting.  Hopefully this will give the fix I need!

 

Jack, K4IJQ

Jack,

is this with WinWarbler, WSJT-X, or some other data comms application?


--
73

Bill

G4WJS.



--
73

Bill

G4WJS.


Re: DXLabs, WSJT-X (ft8) and Yaesu FT-950

Jackson McNees
 

Bill,

 

This is with WinWarbler and WSJT-X connected through Commander.

 

Jack

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of g4wjs
Sent: Monday, June 15, 2020 7:36 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLabs, WSJT-X (ft8) and Yaesu FT-950

 

On 15/06/2020 22:29, Jackson McNees wrote:

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.  Looked high and low through Commander docs to see if something there but found nothing.  Based on this discussion, will have to see if I have to set up a command sequence to change mode after transmitting.  Hopefully this will give the fix I need!

 

Jack, K4IJQ

Jack,

is this with WinWarbler, WSJT-X, or some other data comms application?


--
73

Bill

G4WJS.


Re: myQTH changed on most QSO's

Dave AA6YQ
 

+ AA6YQ comments below

The genesis of my problem was when my computer became useless last autumn. Win10 ran a troubleshooter and advised me to do their wipe and reload. That gets rid of all applications but leaves the data files.

The problem started when TQSL stopped working. Apparently, TQSL won't reload certificates onto a "different" computer.

+ You can't effectively move e a Callsign Certificate file (.tq6) from one computer to another unless you also move the Callsign Certificate's "private key". TQSL provides a easy means of moving all Callsign Certificates, Station Locations, and Settings in a single file from one computer to another; see

<https://lotw.arrl.org/lotw-help/backuprestore/>


Since it has a new OS build, to TQSL, this is a "different" computer.

+ No, it's computer whose private keys were deleted by the Windows "wipe and reload" process.


I got only the certificate for my latest call and QTH. When I was trying to fix my requested QSO's in LoTW, when I updated and uploaded to LoTW, it caused everything to be overwritten as W1ES and QTH as Graham.

I have asked Bart at LoTW to send me new certificates.

When I get the new certificates, am I correct in thinking that I will have to make the mass change per the instructions, then upload to LoTW again?

+ No. There is no "mass change" to make, and no need to re-submit anything to LoTW.

+ If you have more than one "My QTH" defined in DXKeeper, it would be a good idea to ensure that each logged QSO specifies the correct "My QTH". This can be accomplished by filtering the Log Page Display to contain QSOs within a date range, and en masse modifying the "My QTH ID" of all of those QSOs to the correct value. Be sure to backup your log before undertaking this process, and don't hesitate to ask for help if you need it.

73,

Dave, AA6YQ


Re: DXLabs, WSJT-X (ft8) and Yaesu FT-950

g4wjs
 

On 15/06/2020 22:29, Jackson McNees wrote:

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.  Looked high and low through Commander docs to see if something there but found nothing.  Based on this discussion, will have to see if I have to set up a command sequence to change mode after transmitting.  Hopefully this will give the fix I need!

 

Jack, K4IJQ

Jack,

is this with WinWarbler, WSJT-X, or some other data comms application?


--
73

Bill

G4WJS.


Re: myQTH changed on most QSO's

Steve Wedge <Steve27302@...>
 

The genesis of my problem was when my computer became useless last autumn.  Win10 ran a troubleshooter and advised me to do their wipe and reload.  That gets rid of all applications but leaves the data files.

The problem started when TQSL stopped working.  Apparently, TQSL won't reload certificates onto a "different" computer.  Since it has a new OS build, to TQSL, this is a "different" computer.  I got only the certificate for my latest call and QTH.  When I was trying to fix my requested QSO's in LoTW, when I updated and uploaded to LoTW, it caused everything to be overwritten as W1ES and QTH as Graham.

I have asked Bart at LoTW to send me new certificates.

When I get the new certificates, am I correct in thinking that I will have to make the mass change per the instructions, then upload to LoTW again?

Sorry this has been such a mess.  There are so many interactive pieces here.

73,

Steve, W1ES


Re: DXLabs, WSJT-X (ft8) and Yaesu FT-950

Dave AA6YQ
 

+ 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


Re: DXLabs, WSJT-X (ft8) and Yaesu FT-950

Jackson McNees
 

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.  Looked high and low through Commander docs to see if something there but found nothing.  Based on this discussion, will have to see if I have to set up a command sequence to change mode after transmitting.  Hopefully this will give the fix I need!

 

Jack, K4IJQ

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of g4wjs
Sent: Saturday, June 13, 2020 9:07 PM
To: DXLab@groups.io
Subject: Re: [DXLab] DXLabs, WSJT-X (ft8) and Yaesu FT-950

 

On 14/06/2020 01:39, Jerome Sodus wrote:

Hello Dave,
Relative to Bill G4WJS's reply, I'm making a command sequence to put VFO-A in USB and VFO-B at USB-PKT; both set at 7074000 Hz.
It is not working; perhaps you can spot my error(s) or omission(s).

Here is my code per Yaesu's CAT-manual and your email about 'split':
FA7074000;
MD02;
FB7074000;
MD0C;
FT3;

TIA for any help.
73 jerry km3k
PS..it is a great feeling to be 'coding' again.

Jerome,

you don't need to set any frequencies or SPLIT. Try this:

'VS1;
'MD0C;
'VS0;
'MD02
<END>

This is assuming that the FT-950 does limit the Rx passband in USB-DATA mode, the user manual doesn't make it clear. If it doesn't then just check the WSJT-X option "Settings->Radio->Mode->Data/Pkt" and let WSJT-X sort it out for you.


--
73

Bill

G4WJS.


Re: myQTH changed on most QSO's

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


Re: Commander not recognizing Kenwood TS-440SAT

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


Re: Commander not recognizing Kenwood TS-440SAT

Joe Subich, W4TV
 

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

On 2020-06-15 3:22 PM, Steve wrote:
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.


Re: Commander not recognizing Kenwood TS-440SAT

Joe Subich, 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?


myQTH changed on most QSO's

Steve Wedge <Steve27302@...>
 

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


Re: Commander not recognizing Kenwood TS-440SAT

Steve
 

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


Re: Commander not recognizing Kenwood TS-440SAT

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?


Re: Commander not recognizing Kenwood TS-440SAT

Steve
 

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.


Re: Commander not recognizing Kenwood TS-440SAT

Joe Subich, W4TV
 

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?


Re: Commander not recognizing Kenwood TS-440SAT

Dave AA6YQ
 

+ 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


Re: Commander not recognizing Kenwood TS-440SAT

g4wjs
 

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.


Commander not recognizing Kenwood TS-440SAT

Steve
 

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;

5661 - 5680 of 200131