Date   
Re: Using TS870 with CAT Keying the On Air light never turns off

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 6:28 PM
To: dxlab@...
Subject: [dxlab] Using TS870 with CAT Keying the On Air light never turns off

Using TS870 with CAT Keying the On-Air light never turns off. Otoh on CW and using PSK I must push the send button on the TS870 to
switch to receive or go to Commander and select receive. VOX is not on.

I am using a new USB Signalink interface, but it is not the problem because turning it off or even unplugging the Data cable form
the back of the radio does not unkey. If I select no port for CW PTT and do not select Xcvr Ctl App then I can use the other modes
and the keying is correctly handled. Of course, that means I cannot use CW keying by WW until I get my WinKeyer I was using a second
RSA232 for keying and that worked but I have removed that. It would be nice to solve this but it is not a really large problem since
I will be using the USB WinKeyer in a few weeks. However, quickly they get it to me.

It seems that perhaps WW is not sending the Switch to Receive command when needed and that happens on both CW and PSK ! if I have
Xcvr Ctl App selected.

When WinWarbler's "CW Keying" panel is set to "Xcvr Ctrl App", WinWarbler does not control RX-TX-RX switching: it doesn't know
exactly when the transceiver will start sending CW, or exactly when the transceiver will finish. WinWarbler simply sends the text to
be transmitted to Commander, which in turn uses the KY command to send it to your TS-870. Your TS-870 should switch from RX to TX
when it receives the first CW character to be transmitted, and switch from TX to RX when it has not more CW characters to transmit.

73,

Dave, AA6YQ

DXKeeper Slow Response to Filter Searches

sv.pleiades
 

Seems like DXKeeper has slowed down for me when doing a search for a callsign in the log by entering it in the "Filter" dialog and then hitting "Call". Each search is taking 5-6 seconds with the little blue spinning circle icon doing its thing. Then, when I clear the "Filter" dialog it takes the same amount of time to get back to the normal log display. Believe this is a recent change in performance. I have not made any changes to the computer DXKeeper runs on other than normal updates to Windows 10.

My log contains a little over 3300 QSOs. Am guessing that is not large by comparison to others and not the cause.

The computer is a reasonably high performance with i7 chipset and 16 gig of memory. In searching through the Yahoo group I found some suggestions from Dave about checking for a failing disk drive when things slow down. Have done that by checking the windows event logs and found nothing.

Thanks for any suggestions!

73, Tom
K1FR


Using TS870 with CAT Keying the On Air light never turns off

Gilbert Baron W0MN
 

Using TS870 with CAT Keying the On-Air light never turns off. Otoh on CW and using PSK I must push the send button on the TS870 to switch to receive or go to Commander and select receive. VOX is not on.

I am using a new USB Signalink interface, but it is not the problem because turning it off or even unplugging the Data cable form the back of the radio does not unkey. If I select no port for CW PTT and do not select Xcvr Ctl App then I can use the other modes and the keying is correctly handled. Of course, that means I cannot use CW keying by WW until I get my WinKeyer I was using a second RSA232 for keying and that worked but I have removed that. It would be nice to solve this but it is not a really large problem since I will be using the USB  WinKeyer in a few weeks. However, quickly they get it to me.

 

It seems that perhaps WW is not sending the Switch to Receive command when needed and that happens on both CW and PSK ! if I have Xcvr Ctl App selected.

 

Outlook Desktop Gil W0MN

Hierro Candente Batir de Repente

44.08226 N 92.51265 W

 

Re: Virtual ports

Steve - N3SL
 

Thanks, Joe and Rich.

Although the "simple" delete and recreate did not work, a complete uninstall and re-install of the Device Router did the trick.  No idea what happened, but then Windows is Windows, and users are users.....

Thanks again!

On Fri, Nov 10, 2017 at 4:55 PM, 'Joe Subich, W4TV' lists@... [dxlab] <dxlab@...> wrote:
 


As I answered earlier this afternoon from "support@...":

>
>> I don't know if a Win10 update or some other program has changed
>> anything but now when I launch the USB Device Router, I get errors
>> than COM3-5 fail. >
> That indicates that Windows updated some drivers (probably USB drivers)
> while Router was running.
>
>> Interestingly, COM3 (FT2000 CAT still tracks the radio perfectly) and
>> COM5 (PTT - still keys the rig when the "test" button is clicked.
>
> The "Eltima VSPAX" (virtual COM ports) are only used between the
> logging software and Router. A failure of the virtual ports will not
> keep Router from communicating with the rig.
>
>> Any ideas where to look/start?
>
> In Router select Virtual Port | Delete All. Close Router and
> *RESTART* Windows. When Windows has restarted, start Router and
> select Virtual Port | Create to create COM3, COM4 and COM5. You
> will most likely need to reassign the ports (CAT, PTT, FSK, WinKey)
> in Router and update any saved presets.
73,

... Joe, W4TV

On 11/10/2017 11:04 AM, n3sl.dxis@... [dxlab] wrote:
>
> Apologies in advance, as I know this isn't a DXLab problem, but the expertise with this group is notable....
>
>
> I've just discovered on my Win10 machine that I've lost "recognition" of my virtual ports. Not sure when it happened, as I've not used them (rig control, RTTY) for a couple of weeks. And I say "recognition" because within MicroHam Device Router (which I've used for years), I can still query and control my rig (COM3) and key it in CW (COM4), and key it in RTTY (COM5). However, neither MMTTY nor DXLab Commander even see these ports any longer.
>
>
> Any ideas? I've done reinstall of Device Router, unplugged and reset USB cables, deleted all my JT software (thought it may have been the problem). One other thing - and not sure if it's "normal" with Win10 - in the Win10 Device Manager I don't have ANY ports listed - i.e. the "Ports" option isn't even there.
>
>
> Thanks in advance for any assistance!
>
>
> Steve
>


Re: Virtual ports

Joe Subich, W4TV
 

As I answered earlier this afternoon from "support@...":


I don't know if a Win10 update or some other program has changed anything but now when I launch the USB Device Router, I get errors
than COM3-5 fail. >
That indicates that Windows updated some drivers (probably USB drivers)
while Router was running.

Interestingly, COM3 (FT2000 CAT still tracks the radio perfectly) and
COM5 (PTT - still keys the rig when the "test" button is clicked.
The "Eltima VSPAX" (virtual COM ports) are only used between the logging software and Router. A failure of the virtual ports will not keep Router from communicating with the rig.

Any ideas where to look/start?
In Router select Virtual Port | Delete All. Close Router and *RESTART* Windows. When Windows has restarted, start Router and select Virtual Port | Create to create COM3, COM4 and COM5. You
will most likely need to reassign the ports (CAT, PTT, FSK, WinKey)
in Router and update any saved presets.
73,

... Joe, W4TV


On 11/10/2017 11:04 AM, n3sl.dxis@... [dxlab] wrote:
Apologies in advance, as I know this isn't a DXLab problem, but the expertise with this group is notable....
I've just discovered on my Win10 machine that I've lost "recognition" of my virtual ports. Not sure when it happened, as I've not used them (rig control, RTTY) for a couple of weeks. And I say "recognition" because within MicroHam Device Router (which I've used for years), I can still query and control my rig (COM3) and key it in CW (COM4), and key it in RTTY (COM5). However, neither MMTTY nor DXLab Commander even see these ports any longer.
Any ideas? I've done reinstall of Device Router, unplugged and reset USB cables, deleted all my JT software (thought it may have been the problem). One other thing - and not sure if it's "normal" with Win10 - in the Win10 Device Manager I don't have ANY ports listed - i.e. the "Ports" option isn't even there.
Thanks in advance for any assistance!
Steve

Re: DXKeeper setup Club Contest

ART SEARLE <w2nra@...>
 

32 would be enough but the help file lists the RX# and TX# at 16 character limit. The RX-Info and TX-Info are 32 . . . per the help film

73, Art, W2NRA

On Nov 10, 2017, at 1:57 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:

 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:43 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper setup Club Contest

Thank you, Dave, I just noticed the 16 character limit so I will try the Log QSOs Tab instead of the Capture window

>>>By that, I assume you mean that you'll record exchange information in the "TX Info" and "RX Info" items, which each have a capacity of 32 alphanumeric characters.

73,

Dave, AA6YQ

Re: Commander rig control with WSJT-X locking up

Björn Ekelund, SM7IUN
 

Thanks Bill,

I tried this and it worked.

73,

Björn

2017-11-10 21:57 GMT+01:00 bill.8@... [dxlab] <dxlab@...>:

 

Hi Björn,

clicking "Retry" or going into settings from a WSJT-X rig control error will reset the rig connection, that entails so CAT interaction and is not "passive". You should probably ignore the error message and leave it on screen, until you wish to revert to operating with WSJT-X.

73
Bill
G4WJS.


Re: Commander rig control with WSJT-X locking up

g4wjs
 

Hi Björn,

clicking "Retry" or going into settings from a WSJT-X rig control error will reset the rig connection, that entails so CAT interaction and is not "passive". You should probably ignore the error message and leave it on screen, until you wish to revert to operating with WSJT-X.

73
Bill
G4WJS.

Re: WSJT-X - DX Commander connection problem for 2nd radio.

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 2:53 PM
To: dxlab@...
Subject: [dxlab] Re: WSJT-X - DX Commander connection problem for 2nd radio.

Thanks to advice from Bill (G4WJS) the problem has been solved.

In case anyone else comes across the same problem the work round Bill sent me was:

This is an issue here because the Yaesu requires "Settings->Radio->Mode" to be set to "Data/Pkt" but the Kenwood requires it to be set to "USB". I suggest you create a second configuration in WSJT-X and have it set for the second rig with the required "Settings->Radio->Mode" option. Then when you switch rigs in Commander you will have to switch configuration in WSJT-X afterwards, you can do it from the rig error message pop up window or from the main WSJT-X menu.

As Bill suggested it does work.

Thanks, Ivor.
That's consistent with step 2.b.iv in the WSJT-X section of
<http://www.dxlabsuite.com/dxlabwiki/GettingStartedwithK1JTModes>

73,

Dave, AA6YQ

Re: Virtual ports

Scott Stembaugh
 

This often happens to me after a Win10 update.  A reboot usually re-engaes them  However, after getting the last Win10 update (Fall Creator) it happens if I leave the rig off with the programs running.  In the past I ave searched for USB power settings to be set to allow the USB port to sleep, and the I set them to not sleep.  Have not had a chance to check them yet this time.  Frustrating to see a spot for vk9ma on 80m, turn the rig on and click on the spot and the radio stays where it was even if Commander says it QSYed.  Situational awareness at dawn is not my strong suit....

On Fri, Nov 10, 2017 at 11:04 AM, n3sl.dxis@... [dxlab] <dxlab@...> wrote:
 

Apologies in advance, as I know this isn't a DXLab problem, but the expertise with this group is notable....


I've just discovered on my Win10 machine that I've lost "recognition" of my virtual ports.  Not sure when it happened, as I've not used them (rig control, RTTY) for a couple of weeks.  And I say "recognition" because within MicroHam Device Router (which I've used for years), I can still query and control my rig (COM3) and key it in CW (COM4), and key it in RTTY (COM5).  However, neither MMTTY nor DXLab Commander even see these ports any longer.  


Any ideas?  I've done reinstall of Device Router, unplugged and reset USB cables, deleted all my JT software (thought it may have been the problem).   One other thing - and not sure if it's "normal" with Win10 - in the Win10 Device Manager I don't have ANY ports listed - i.e. the "Ports" option isn't even there.


Thanks in advance for any assistance!


Steve


Re: WSJT-X - DX Commander connection problem for 2nd radio.

ihl.grange@...
 

Thanks to advice from Bill (G4WJS) the problem has been solved.

In case anyone else comes across the same problem the work round Bill sent me was:

This is an issue here because the Yaesu requires "Settings->Radio->Mode" to be set to "Data/Pkt" but the Kenwood requires it to be set to "USB". I suggest you create a second configuration in WSJT-X and have it set for the second rig with the required "Settings->Radio->Mode" option. Then when you switch rigs in Commander you will have to switch configuration in WSJT-X afterwards, you can do it from the rig error message pop up window or from the main WSJT-X menu.

As Bill suggested it does work.

So many thanks Bill

73

Ivor
MM0IEL




Re: Hanover County, NC

Jim Wright
 

Is it under N since it’s New Hanover County?

-jim KS4O


On Fri, Nov 10, 2017 at 13:18 Bill Billingsley billingsley2629@... [dxlab] <dxlab@...> wrote:
 

Above county in not listed in the NC county pull down on the capture window.  Internet says that it exists. Is it a combined area now?

Bill, N5IR

Re: Hanover County, NC

Bill N5IR
 

yep.  That's the answer.  Its under New Hanover County.  The station just sent Hanover as his county.

Tnx,
Bill, N5IR

On Fri, Nov 10, 2017 at 1:25 PM, Phil Irons ve1bvd@... [dxlab] <dxlab@...> wrote:
 

The answer is in the url you posted, Bill.  the 'n' stands for 'new'.  From the countyhunter website posted by Dave, in North Carolina: New Hanover County.  I don't have the DXLab Suite installed on this computer, but I'll bet if you check the NC county listings in DX Keeper, you'll find New Hanover County.

73,

Phil/VE1BVD
Sydney, NS

On Fri, Nov 10, 2017 at 3:09 PM, Bill Billingsley billingsley2629@... [dxlab] <dxlab@...> wrote:
 


On Fri, Nov 10, 2017 at 12:54 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:18 PM
To: dxlab@...
Subject: [dxlab] Hanover County, NC

Above county in not listed in the NC county pull down on the capture window. Internet says that it exists.

>>>Not every statement on the internet is accurate.

Is it a combined area now?

>>>What's a "combined area"?

>>>ADIF cites two sources for US Counties:

http://countyhunter.com/counties.htm

https://web.archive.org/web/20140128164414/http://www.itl.nist.gov/fipspubs/co-codes/states.txt

>>>Neither lists a "Hanover County" in North America.

73,

Dave, AA6YQ





--
Phil & Anne Irons
Sydney, Nova Scotia


Re: Hanover County, NC

Phil & Anne Irons
 

The answer is in the url you posted, Bill.  the 'n' stands for 'new'.  From the countyhunter website posted by Dave, in North Carolina: New Hanover County.  I don't have the DXLab Suite installed on this computer, but I'll bet if you check the NC county listings in DX Keeper, you'll find New Hanover County.

73,

Phil/VE1BVD
Sydney, NS

On Fri, Nov 10, 2017 at 3:09 PM, Bill Billingsley billingsley2629@... [dxlab] <dxlab@...> wrote:
 


On Fri, Nov 10, 2017 at 12:54 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:18 PM
To: dxlab@...
Subject: [dxlab] Hanover County, NC

Above county in not listed in the NC county pull down on the capture window. Internet says that it exists.

>>>Not every statement on the internet is accurate.

Is it a combined area now?

>>>What's a "combined area"?

>>>ADIF cites two sources for US Counties:

http://countyhunter.com/counties.htm

https://web.archive.org/web/20140128164414/http://www.itl.nist.gov/fipspubs/co-codes/states.txt

>>>Neither lists a "Hanover County" in North America.

73,

Dave, AA6YQ





--
Phil & Anne Irons
Sydney, Nova Scotia

Re: Hanover County, NC

Bill N5IR
 

On Fri, Nov 10, 2017 at 12:54 PM, 'Dave AA6YQ' aa6yq@... [dxlab] <dxlab@...> wrote:
 

>>>AA6YQ comments below

-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:18 PM
To: dxlab@...
Subject: [dxlab] Hanover County, NC

Above county in not listed in the NC county pull down on the capture window. Internet says that it exists.

>>>Not every statement on the internet is accurate.

Is it a combined area now?

>>>What's a "combined area"?

>>>ADIF cites two sources for US Counties:

http://countyhunter.com/counties.htm

https://web.archive.org/web/20140128164414/http://www.itl.nist.gov/fipspubs/co-codes/states.txt

>>>Neither lists a "Hanover County" in North America.

73,

Dave, AA6YQ


Re: Hanover County, NC

Tad Danley <tdanley@...>
 

There is no Hanover County in North Carolina.
https://en.wikipedia.org/wiki/List_of_counties_in_North_Carolina

73,

Tad Danley, K3TD

On 11/10/2017 1:54 PM, 'Dave AA6YQ' @AA6YQ [dxlab] wrote:

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:18 PM
To: dxlab@...
Subject: [dxlab] Hanover County, NC

Above county in not listed in the NC county pull down on the capture window. Internet says that it exists.

Not every statement on the internet is accurate.
Is it a combined area now?

What's a "combined area"?
ADIF cites two sources for US Counties:
http://countyhunter.com/counties.htm

https://web.archive.org/web/20140128164414/http://www.itl.nist.gov/fipspubs/co-codes/states.txt

Neither lists a "Hanover County" in North America.
73,

Dave, AA6YQ

Re: DXKeeper setup Club Contest

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:43 PM
To: dxlab@...
Subject: Re: [dxlab] DXKeeper setup Club Contest

Thank you, Dave, I just noticed the 16 character limit so I will try the Log QSOs Tab instead of the Capture window

By that, I assume you mean that you'll record exchange information in the "TX Info" and "RX Info" items, which each have a capacity of 32 alphanumeric characters.
73,

Dave, AA6YQ

Re: Hanover County, NC

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 1:18 PM
To: dxlab@...
Subject: [dxlab] Hanover County, NC

Above county in not listed in the NC county pull down on the capture window. Internet says that it exists.

Not every statement on the internet is accurate.

Is it a combined area now?

What's a "combined area"?

ADIF cites two sources for US Counties:
http://countyhunter.com/counties.htm

https://web.archive.org/web/20140128164414/http://www.itl.nist.gov/fipspubs/co-codes/states.txt

Neither lists a "Hanover County" in North America.
73,

Dave, AA6YQ

Re: My own call in SpotCollector

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 12:45 PM
To: dxlab@...
Subject: Re: [dxlab] My own call in SpotCollector

After calling CQ type your call in SpotCollector’s Filter-Text-Box and hit the Call button. Do they show up then?

Doing that leaves the Band, Mode, Continent, Origin, Age, LoTW, and eQSL filters active, and so could hide a Spot Database Entry bearing your callsign.
73,

Dave, AA6YQ



On Nov 10, 2017, at 11:43 AM, Kent Olsen kilo6dko@... [dxlab] <dxlab@...> wrote:







I cannot recall ever seeing my call sign showing up in the SC window after I call CQ using CW (or any mode for that matter). Does SC filter my own call out. I can do a sh/dx n6wt, in command line in the cluster window, to see that I have been spotted (by the rbn).


Thanks

73

Kent

N6WT








<http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient> Virus-free. www.avg.com <http://www.avg.com/email-signature?utm_medium=email&utm_source=link&utm_campaign=sig-email&utm_content=emailclient>

Re: Key CW with CIV CAT

Dave AA6YQ
 

AA6YQ comments below
-----Original Message-----
From: dxlab@... [mailto:dxlab@...]
Sent: Friday, November 10, 2017 12:02 PM
To: dxlab@...
Subject: [dxlab] Key CW with CIV CAT

Is it possible to key the TS870 using the KY commands and WinWarbler.

Yes.
That is CW operation without any RS232 port and without any other hardware such as Winkeyer?

Correct.
If so can someone point me to the documentation to set this up. Thanks.

See the 4th bullet point in step 1.f of
<http://www.dxlabsuite.com/dxlabwiki/ConfigureCW>


By the way, "CI-V" refers to the bus used in Icom (and some old TenTec) radios to convey commands and responses.
73,

Dave, AA6YQ