Date   

Re: CW-R problem

Ron KU7Y
 

Thanks Dave,

I'll give that a try later this afternoon or evening and let you know how it works.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: Dave AA6YQ [mailto:@AA6YQ]
Sent: Sunday, July 21, 2019 11:08 AM
To: DXLab@groups.io; ron@...
Subject: RE: [DXLab] CW-R problem

+ AA6YQ comments below

> The only somewhat interesting thing is that Commander shows CW-R.

I don't know why (or how) Commander can show CW-R when the rig is in CW
even if the rig is configured "backward". As far as I know, the only
communication between Commander and the FTdx3000 are the IF; OI; and MD;
command polls and they uniformly report 3 for CW and 7 for CW-R. I
don't see any CAT command that would allow any logging/control software
to determine whether CW is USB (normal), LSB, or Auto.

+ Correct, Joe. Commander has no way of knowing that by using the
radio's menu system, the meanings of CW and CW-R have been reversed.

+ My strong advice is "un-reverse them", and then configure DXLab
applications to use CW-R. Otherwise, there could be a large "confusion
event" down-the road after the details of what was done behind
Commander's back are forgotten.

73,

Dave, AA6YQ


Re: CW-R problem

Dave AA6YQ
 

+ AA6YQ comments below

> The only somewhat interesting thing is that Commander shows CW-R.

I don't know why (or how) Commander can show CW-R when the rig is in CW even if the rig is configured "backward". As far as I know, the only communication between Commander and the FTdx3000 are the IF; OI; and MD; command polls and they uniformly report 3 for CW and 7 for CW-R. I don't see any CAT command that would allow any logging/control software to determine whether CW is USB (normal), LSB, or Auto.

+ Correct, Joe. Commander has no way of knowing that by using the radio's menu system, the meanings of CW and CW-R have been reversed.

+ My strong advice is "un-reverse them", and then configure DXLab applications to use CW-R. Otherwise, there could be a large "confusion event" down-the road after the details of what was done behind Commander's back are forgotten.

73,

Dave, AA6YQ


Re: CW-R problem

Joe Subich, W4TV
 

The only somewhat interesting thing is that Commander shows CW-R.
I don't know why (or how) Commander can show CW-R when the rig is
in CW even if the rig is configured "backward". As far as I know,
the only communication between Commander and the FTdx3000 are the
IF; OI; and MD; command polls and they uniformly report 3 for CW
and 7 for CW-R. I don't see any CAT command that would allow any
logging/control software to determine whether CW is USB (normal),
LSB, or Auto.

73,

... Joe, W4TV


On 2019-07-21 7:44 AM, Ron KU7Y wrote:
Many Thanks Joe!!!
I had printed out the CAT Operations Reference Book and had played with the little program Yaesu has to see how they work but I sure didn't understand much about them until I tried following your train of thought.
So I sent MD0A; to get into the FM mode. Then I played with some of the CW commands and finally thought to use the MD03; command thinking that would put into the default CW mode and it worked. If I had Menu 60 set for USB, the default CW was USB. If I had Menu 60 set to LSB then the default CW command went to CW LSB.
Net I started SC and Commander. Opened Config in Commander and on the Bandspread tab, under CW mode and changed that from CW-R to CW. Then I went into SC Config, General tab, Transceiver mode etc and changed that from CW-R to CW.
Now when clicking on a spot in SC it changed frequency and leaves the mode in CW LSB. (I also removed the Digital Mode Application and left it blank.
The only somewhat interesting thing is that Commander shows CW-R. Which might really be right because I do have the rig set "backwards" to what it might be expecting. If I change the mode, using the button on the rig, to CW USB, then Commander changes to CW.
Now I'll go save all the settings and then get on the air!
Thanks again Joe.
OK, back in my hole,
Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: Joe Subich, W4TV [mailto:lists@...]
Sent: Saturday, July 20, 2019 5:41 PM
To: DXLab@groups.io; ron@...
Subject: Re: [DXLab] CW-R problem


Ron,

On 2019-07-20 5:34 PM, Dave AA6YQ wrote:
> Here's the CAT command that Commander is sending to your FTDX-3000:
>
> 20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;

*HOWEVER* since you have configured your FTdx3000 (menu 60) to make
CW-L the default CW mode, you *DO NOT* want SC/Commander to issue MD07:
(CW-R) as that is *CW-U*. You want SC/Commander to issue MD-3: (CW)
as that is *CW-L*.

If you have configured the FTdx3000 with MENU 60 = LSB you want
SC -> CONFIG -> General -> Transceiver mode with no Digital Mode
Application connected -> CW Spot set to *CW*.

73,

... Joe, W4TV


On 2019-07-20 5:34 PM, Dave AA6YQ wrote:
Thanks for sending me the Commander errorlog.txt file, Ron.

Here's the directive that SpotCollector is sending to Commander when
you double-clicked on the Spot Database Entry for a station
operating in CW:

20-Jul-2019 01:32:37 > DDEServer.LinkExecute:
000xcvrfreqmode<xcvrfreq:9> 10104.0<xcvrmode:4>CW-R

So you've properly configured SpotCollector to specify that CW-R be
used.

Here's the CAT command that Commander is sending to your FTDX-3000:

20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;

As described on page 11 of the FTDX-3000 CAT manual, that's the
correct CAT command for placing an FTDX-3000 into CW-R mode.

SpotCollector and Commander are thus performing correctly. If your
FTDX-3000 is not correctly responding to the MD07; CAT command,
I suggest that you contact Yaesu Technical support.

73,

Dave, AA6YQ



-----Original Message-----
From: Ron KU7Y [mailto:ron@...]
Sent: Friday, July 19, 2019 9:52 PM
To: 'Dave AA6YQ'
Subject:

Took me forever to find this. Wasn't looking for the CI-V before
Commander!
:-)

Thanks for all your help.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...




Re: CW-R problem

Ron KU7Y
 

Many Thanks Joe!!!

I had printed out the CAT Operations Reference Book and had played with the little program Yaesu has to see how they work but I sure didn't understand much about them until I tried following your train of thought.

So I sent MD0A; to get into the FM mode. Then I played with some of the CW commands and finally thought to use the MD03; command thinking that would put into the default CW mode and it worked. If I had Menu 60 set for USB, the default CW was USB. If I had Menu 60 set to LSB then the default CW command went to CW LSB.

Net I started SC and Commander. Opened Config in Commander and on the Bandspread tab, under CW mode and changed that from CW-R to CW. Then I went into SC Config, General tab, Transceiver mode etc and changed that from CW-R to CW.

Now when clicking on a spot in SC it changed frequency and leaves the mode in CW LSB. (I also removed the Digital Mode Application and left it blank.

The only somewhat interesting thing is that Commander shows CW-R. Which might really be right because I do have the rig set "backwards" to what it might be expecting. If I change the mode, using the button on the rig, to CW USB, then Commander changes to CW.

Now I'll go save all the settings and then get on the air!

Thanks again Joe.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: Joe Subich, W4TV [mailto:lists@...]
Sent: Saturday, July 20, 2019 5:41 PM
To: DXLab@groups.io; ron@...
Subject: Re: [DXLab] CW-R problem


Ron,

On 2019-07-20 5:34 PM, Dave AA6YQ wrote:
> Here's the CAT command that Commander is sending to your FTDX-3000:
>
> 20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;

*HOWEVER* since you have configured your FTdx3000 (menu 60) to make
CW-L the default CW mode, you *DO NOT* want SC/Commander to issue MD07:
(CW-R) as that is *CW-U*. You want SC/Commander to issue MD-3: (CW)
as that is *CW-L*.

If you have configured the FTdx3000 with MENU 60 = LSB you want
SC -> CONFIG -> General -> Transceiver mode with no Digital Mode
Application connected -> CW Spot set to *CW*.

73,

... Joe, W4TV


On 2019-07-20 5:34 PM, Dave AA6YQ wrote:
Thanks for sending me the Commander errorlog.txt file, Ron.

Here's the directive that SpotCollector is sending to Commander when
you double-clicked on the Spot Database Entry for a station
operating in CW:

20-Jul-2019 01:32:37 > DDEServer.LinkExecute:
000xcvrfreqmode<xcvrfreq:9> 10104.0<xcvrmode:4>CW-R

So you've properly configured SpotCollector to specify that CW-R be
used.

Here's the CAT command that Commander is sending to your FTDX-3000:

20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;

As described on page 11 of the FTDX-3000 CAT manual, that's the
correct CAT command for placing an FTDX-3000 into CW-R mode.

SpotCollector and Commander are thus performing correctly. If your
FTDX-3000 is not correctly responding to the MD07; CAT command,
I suggest that you contact Yaesu Technical support.

73,

Dave, AA6YQ



-----Original Message-----
From: Ron KU7Y [mailto:ron@...]
Sent: Friday, July 19, 2019 9:52 PM
To: 'Dave AA6YQ'
Subject:

Took me forever to find this. Wasn't looking for the CI-V before
Commander!
:-)

Thanks for all your help.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...




Re: CW-R problem

Joe Subich, W4TV
 

Ron,

On 2019-07-20 5:34 PM, Dave AA6YQ wrote:
Here's the CAT command that Commander is sending to your FTDX-3000:

20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;
*HOWEVER* since you have configured your FTdx3000 (menu 60) to make
CW-L the default CW mode, you *DO NOT* want SC/Commander to issue MD07:
(CW-R) as that is *CW-U*. You want SC/Commander to issue MD-3: (CW)
as that is *CW-L*.

If you have configured the FTdx3000 with MENU 60 = LSB you want
SC -> CONFIG -> General -> Transceiver mode with no Digital Mode
Application connected -> CW Spot set to *CW*.

73,

... Joe, W4TV


On 2019-07-20 5:34 PM, Dave AA6YQ wrote:
Thanks for sending me the Commander errorlog.txt file, Ron.
Here's the directive that SpotCollector is sending to Commander when you double-clicked on the Spot Database Entry for a station
operating in CW:
20-Jul-2019 01:32:37 > DDEServer.LinkExecute: 000xcvrfreqmode<xcvrfreq:9> 10104.0<xcvrmode:4>CW-R
So you've properly configured SpotCollector to specify that CW-R be used.
Here's the CAT command that Commander is sending to your FTDX-3000:
20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;
As described on page 11 of the FTDX-3000 CAT manual, that's the correct CAT command for placing an FTDX-3000 into CW-R mode.
SpotCollector and Commander are thus performing correctly. If your FTDX-3000 is not correctly responding to the MD07; CAT command,
I suggest that you contact Yaesu Technical support.
73,
Dave, AA6YQ
-----Original Message-----
From: Ron KU7Y [mailto:ron@...]
Sent: Friday, July 19, 2019 9:52 PM
To: 'Dave AA6YQ'
Subject:
Took me forever to find this. Wasn't looking for the CI-V before Commander!
:-)
Thanks for all your help.
OK, back in my hole,
Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...


Re: Trouble from windows update

w6de
 

Nope, just select one way to stop the updates.   Usually regedit is for serious system administration use and a mistake there can easily break windows.  Of course, you can make mistakes in Group Policy editing too, but there are more functions that over time that you may use group policy to change.  For instance: setting the network time sync more frequently.

 

73,

Dave, w6de

 

From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Russ Ravella via Groups.Io
Sent: 20 July, 2019 23:12
To: DXLab@groups.io
Subject: Re: [DXLab] Trouble from windows update

 

Hello,
Thank you for this!  There is another item on this page titled:  "How to prevent Windows Update from installing driver updates using Registry”.  Should this step be performed as well?

 

Thanks,

Russ, KR6W

 



On Jul 20, 2019, at 3:07 PM, w6de <w6de@...> wrote:

 

Dave, w5sv,  To prevent this from happening in the future disable driver updates in Windows update using group policy.
Instruction are here:
https://pureinfotech.com/exclude-driver-updates-windows-10/
Scroll down to "How to prevent Windows Update from installing driver updates using Group Policy"

Dave, w6de

-----Original Message-----
From: 
DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of David Reed
Sent: 20 July, 2019 14:24
To: 
DXLab@groups.io
Subject: [DXLab] Trouble from windows update

early this morning, Windows tried to install (but failed) 2019-07 
Cumulative Update for Windows 10 Version 1803 for x64-based Systems 
(KB4507435).

As a result, I have lost my virtual com ports...

in Device Manager, under USB controllers, they show as USB Serial 
Converter (with a yellow triangle with an exclamation mark inside it), 
and have the correct driver loaded, but somehow they are not working, 
not findable in the config for DXLab Commander, and so I am at a loss 
what to do /change / fix next...

Any help will be greatly appreciated.

Thanks & 73 de Dave, W5SV







 


Re: Trouble from windows update

Russ Ravella
 

Hello,
Thank you for this!  There is another item on this page titled:  "
How to prevent Windows Update from installing driver updates using Registry”.  Should this step be performed as well?

Thanks,
Russ, KR6W


On Jul 20, 2019, at 3:07 PM, w6de <w6de@...> wrote:

Dave, w5sv,  To prevent this from happening in the future disable driver updates in Windows update using group policy.
Instruction are here:
https://pureinfotech.com/exclude-driver-updates-windows-10/
Scroll down to "How to prevent Windows Update from installing driver updates using Group Policy"

Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of David Reed
Sent: 20 July, 2019 14:24
To: DXLab@groups.io
Subject: [DXLab] Trouble from windows update

early this morning, Windows tried to install (but failed) 2019-07 
Cumulative Update for Windows 10 Version 1803 for x64-based Systems 
(KB4507435).

As a result, I have lost my virtual com ports...

in Device Manager, under USB controllers, they show as USB Serial 
Converter (with a yellow triangle with an exclamation mark inside it), 
and have the correct driver loaded, but somehow they are not working, 
not findable in the config for DXLab Commander, and so I am at a loss 
what to do /change / fix next...

Any help will be greatly appreciated.

Thanks & 73 de Dave, W5SV








Re: Filter for SC

Dave AA6YQ
 

+ AA6YQ comments below

So many people spot FT4/FT8 QSOs as either CW or RTTY.

How can I make a "filter" to exclude the areas of the bands that have FT8/FT4 activity?

+ If you wanted to hide Spot Database Entries for stations operating in the standard FT8 watering holes on 40m and 20m, you'd use an
SQL expression like

NOT ((FREQUENCY>=7074) and (FREQUENCY<=7077) or (FREQUENCY>=14074) and (FREQUENCY<=14077))

+ However, 1A0C has announced that its using 7071 and 14071 for FT8, so you'd have to expand the above expression while 1A0C is QRV:

NOT ((FREQUENCY>=7074) and (FREQUENCY<=7077) or (FREQUENCY>=14074) and (FREQUENCY<=14077) or (FREQUENCY>=7071) and
(FREQUENCY<=7074) or (FREQUENCY>=14071) and (FREQUENCY<=14074))

+ There is a better way to hide Spot Database Entries for stations operating in FT4 or FT8!

+ Instead, you should

1. upfsyr your sub-band definition file to specify the sub-bands on which FT4 and FT8 operation is currently taking place, as
described in

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

2. terminate and restart SpotCollector

3. click the Mode button in the Filter panel at the bottom of the SpotCollector's Main window

4. in the "Mode Filter" window that appears, uncheck the FT4 and FT8 boxes (at the beginning of the next-to-last row of checkboxes)


+ If you are running the current version of SpotCollector (8.3.6), then your SpotCollector folder contains a sub-band definition
file named

BandModes 2019-05-02.txt

+ that includes sub-band definitions for both FT4 and FT8.

+ You can configure SpotCollector to use this file, or you can edit this file to expand or contract the sub-bands it specifies. If
you do the latter, give it a new name, like

Bandmodes KU7Y 2019-07-20.xt

+ so that it won't be over-written the next time you direct the Launcher to upgrade SpotCollector.

73,

Dave, AA6YQ


Re: Trouble from windows update

w6de
 

Dave, w5sv, To prevent this from happening in the future disable driver updates in Windows update using group policy.
Instruction are here:
https://pureinfotech.com/exclude-driver-updates-windows-10/
Scroll down to "How to prevent Windows Update from installing driver updates using Group Policy"

Dave, w6de

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of David Reed
Sent: 20 July, 2019 14:24
To: DXLab@groups.io
Subject: [DXLab] Trouble from windows update

early this morning, Windows tried to install (but failed) 2019-07
Cumulative Update for Windows 10 Version 1803 for x64-based Systems
(KB4507435).

As a result, I have lost my virtual com ports...

in Device Manager, under USB controllers, they show as USB Serial
Converter (with a yellow triangle with an exclamation mark inside it),
and have the correct driver loaded, but somehow they are not working,
not findable in the config for DXLab Commander, and so I am at a loss
what to do /change / fix next...

Any help will be greatly appreciated.

Thanks & 73 de Dave, W5SV


Re: CW-R problem

Dave AA6YQ
 

Thanks for sending me the Commander errorlog.txt file, Ron.

Here's the directive that SpotCollector is sending to Commander when you double-clicked on the Spot Database Entry for a station
operating in CW:

20-Jul-2019 01:32:37 > DDEServer.LinkExecute: 000xcvrfreqmode<xcvrfreq:9> 10104.0<xcvrmode:4>CW-R

So you've properly configured SpotCollector to specify that CW-R be used.

Here's the CAT command that Commander is sending to your FTDX-3000:

20-Jul-2019 01:32:37 > CIVModule.SendCommand: MD07;

As described on page 11 of the FTDX-3000 CAT manual, that's the correct CAT command for placing an FTDX-3000 into CW-R mode.

SpotCollector and Commander are thus performing correctly. If your FTDX-3000 is not correctly responding to the MD07; CAT command,
I suggest that you contact Yaesu Technical support.

73,

Dave, AA6YQ

-----Original Message-----
From: Ron KU7Y [mailto:ron@...]
Sent: Friday, July 19, 2019 9:52 PM
To: 'Dave AA6YQ'
Subject:

Took me forever to find this. Wasn't looking for the CI-V before Commander!
:-)

Thanks for all your help.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...




---
This email has been checked for viruses by AVG.
https://www.avg.com


Re: Help with WW and Commander setup for Elecraft K3S

Dave AA6YQ
 

+ AA6YQ comments below

@@ No change. No switch over.

+ Ok. That means something is preventing Commander and WinWarbler from communicating.

I have noticed that DXLab applications have to start and run before I power up the rig. If not, Commander Tx/Rx buttons do not do anything. Don't know if this helps in understanding what is going on.

+ Starting Commander before you power up the radio should not be necessary, but let's stay focused on the task at hand, which is determining why Commander and WinWarbler do not communicate on your system.

+ How are you starting Commander and WinWarbler?

+ Please do the following:

1. reboot Windows into "Safe Mode with Networking"; this will start Windows without starting any firewall or anti-malware applications

2. start Commander; note that it will be unable to communicate with your K3 because serial port drivers are not loaded in "Safe Mode with Networking"

3. make the General tab of Commander's Configuration window visible on-screen

4. with WinWarbler configured for RTTY AFSK, click the Start button in WinWarbler's "RTTY transmit (soundcard AFSK) panel"

Does the caption of the PTT panel on the General tab of Commander's Configuration window change from "PTT: Rcving" to "PTT: Xmitting" ?

+ After determining the answer to this question, reboot Windows normally.

73,

Dave, AA6YQ


Re: Help with WW and Commander setup for Elecraft K3S

Joe Subich, W4TV
 

Daryl,

What is the *MODE* setting on the PTT tab in WW CONFIG?

73,

... Joe, W4TV

On 2019-07-20 3:35 PM, Daryl Popowitch wrote:
Dave,
I have done this and repeated the test.   See @@ below.
On 7/19/2019 11:33 PM, Dave AA6YQ wrote:

This is the test on which we are currently focused. After you configuring your anti-malware to consider WinWarbler and Commander to be safe, please repeat it:

1. make the General tab of Commander's Configuration window visible on-screen

2. with WinWarbler configured for RTTY AFSK, click the Start button in WinWarbler's "RTTY transmit (soundcard AFSK) panel"

Does the caption of the PTT panel on the General tab of Commander's Configuration window change from "PTT: Rcving" to "PTT: Xmitting" ?
@@ No change.   No switch over.   I have noticed that DXLab applications have to start and run before I power up  the rig. If not, Commander Tx/Rx buttons do not do anything.   Don't know if this helps in understanding what is going on.
73, Daryl - N8AID

     73,

           Dave, AA6YQ


Re: Help with WW and Commander setup for Elecraft K3S

Daryl Popowitch
 

Dave,
I have done this and repeated the test.   See @@ below.


On 7/19/2019 11:33 PM, Dave AA6YQ wrote:

This is the test on which we are currently focused. After you configuring your anti-malware to consider WinWarbler and Commander to be safe, please repeat it:

1. make the General tab of Commander's Configuration window visible on-screen

2. with WinWarbler configured for RTTY AFSK, click the Start button in WinWarbler's "RTTY transmit (soundcard AFSK) panel"

Does the caption of the PTT panel on the General tab of Commander's Configuration window change from "PTT: Rcving" to "PTT: Xmitting" ?

@@ No change.   No switch over.   I have noticed that DXLab applications have to start and run before I power up  the rig.   If not, Commander Tx/Rx buttons do not do anything.   Don't know if this helps in understanding what is going on.

73, Daryl - N8AID

     73,

           Dave, AA6YQ



Re: CW-R problem

Joe Subich, W4TV
 

On 2019-07-20 11:37 AM, Ron KU7Y wrote:

When I start Commander the Mode shows as CW-R, which is correct.
That is not correct. When Menu 60 is LSB, the FTdx3000 should be
reporting CW-L as CW and CW-U as CW-R.

I think Dave requested that you enable debugging in Commander/SC
and perform/capture a series of specific actions so he can see what
is going on. I suggest doing so ...

BUT, after starting SC, and then clicking on a spot the rig QSYs to
the right frequency but the Mode changes to CW and Commander will not
change it back to CW-R.
When SC/Commander issues a MODE=CW command (MD03;), the FTdx3000 should
switch to CW. If menu 60 = LSB, that should be CW-L. The only time
the FTdx3000 should indicate CW-R (CW-U with menu 60=LSB) is if
SC/Commander issues a MODE=CW-R (MD07;) command.

73,

... Joe, W4TV


On 2019-07-20 11:37 AM, Ron KU7Y wrote:
Joe is right.
I have Menu #60 set to LSB. This gives the tuning I want. When I start Commander the Mode shows as CW-R, which is correct. If I try to change the Mode to CW using Commander it does not change which is fine with me.
BUT, after starting SC, and then clicking on a spot the rig QSYs to the right frequency but the Mode changes to CW and Commander will not change it back to CW-R. I can change the Mode using the Mode button on the rig and Commander follows as it should. But the next time I click on a spot in SC the Mode goes back to CW.
When using SpotSpy with Commander the Mode stays on CW-R when clicking on a spot.
This is not a major issue but just something I find interesting.
OK, back in my hole,
Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joe Subich,
W4TV
Sent: Saturday, July 20, 2019 8:17 AM
To: DXLab@groups.io
Subject: Re: [DXLab] CW-R problem


Actually, the FTdx3000 default CW mode *IS* USB.
MENU 060 CW BFO USB/LSB/AUTO DEFAULT= USB

Selecting AUTO will make CW = LSB on 160/80/40 and
USB on 30 and above. Selecting LSB will select
LSB on all bands.

See page 117 of the FTdx3000 Operating Manual.

73,

... Joe, W4TV


Filter for SC

Ron KU7Y
 

So many people spot FT4/FT8 QSOs as either CW or RTTY.

How can I make a "filter" to exclude the areas of the bands that have
FT8/FT4 activity?

Thanks,

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...


Re: CW-R problem

ART W2NRA
 

My Oops!

Memory failed again.  My FTdx3000 has been boxed up for 2 years now replaced by 7300 and 7610. 

73 art w2nra 


Re: CW-R problem

Ron KU7Y
 

Joe is right.

I have Menu #60 set to LSB. This gives the tuning I want. When I start Commander the Mode shows as CW-R, which is correct. If I try to change the Mode to CW using Commander it does not change which is fine with me.

BUT, after starting SC, and then clicking on a spot the rig QSYs to the right frequency but the Mode changes to CW and Commander will not change it back to CW-R. I can change the Mode using the Mode button on the rig and Commander follows as it should. But the next time I click on a spot in SC the Mode goes back to CW.

When using SpotSpy with Commander the Mode stays on CW-R when clicking on a spot.

This is not a major issue but just something I find interesting.

OK, back in my hole,

Ron, KU7Y
Mountain Home, ID DN23dc
CW Ops #1211
QRP ARCI #8829
SOC #2
Idaho DX Association
Ron@...

-----Original Message-----
From: DXLab@groups.io [mailto:DXLab@groups.io] On Behalf Of Joe Subich,
W4TV
Sent: Saturday, July 20, 2019 8:17 AM
To: DXLab@groups.io
Subject: Re: [DXLab] CW-R problem


Actually, the FTdx3000 default CW mode *IS* USB.
MENU 060 CW BFO USB/LSB/AUTO DEFAULT= USB

Selecting AUTO will make CW = LSB on 160/80/40 and
USB on 30 and above. Selecting LSB will select
LSB on all bands.

See page 117 of the FTdx3000 Operating Manual.

73,

... Joe, W4TV


On 2019-07-20 8:50 AM, ART W2NRA via Groups.Io wrote:
Hi Ron,

The Yaesu FTdx3000’s default CW mode IS LSB so you need to choose the
CW setting (not CW-R) in DXLab software. This will give you “Tune up
frequency to raise side-tone frequency reception” and “tune down
frequency to lower side-tone frequency reception”. CW-R will give you
USB CW.

art w2nra


Re: Trouble from windows update

David Reed
 

Thanks, that did it!

On 7/20/2019 15:16, g4wjs wrote:

Hi Dave,

often deleting the offending device from Device Manager then restarting to get the drivers automatically reinstalled sorts things like this out.



Re: Trouble from windows update

g4wjs
 

On 20/07/2019 15:24, David Reed wrote:
early this morning, Windows tried to install (but failed) 2019-07 Cumulative Update for Windows 10 Version 1803 for x64-based Systems (KB4507435).

As a result, I have lost my virtual com ports...

in Device Manager, under USB controllers, they show as USB Serial Converter (with a yellow triangle with an exclamation mark inside it), and have the correct driver loaded, but somehow they are not working, not findable in the config for DXLab Commander, and so I am at a loss what to do /change / fix next...

Any help will be greatly appreciated.

Thanks & 73 de Dave, W5SV
Hi Dave,

often deleting the offending device from Device Manager then restarting to get the drivers automatically reinstalled sorts things like this out.



--
73

Bill

G4WJS.


Re: Trouble from windows update

CSM\(r\) Gary Huber - AB9M
 

One tool is COM Name Arbiter Setter V0.9 
you may need something different, but COM name arbiter generally fixes Windows update created problems on com ports.


From: DXLab@groups.io <DXLab@groups.io> on behalf of David Reed <w5sv.dave@...>
Sent: Saturday, July 20, 2019 9:24 AM
To: DXLab@groups.io <DXLab@groups.io>
Subject: [DXLab] Trouble from windows update
 
early this morning, Windows tried to install (but failed) 2019-07
Cumulative Update for Windows 10 Version 1803 for x64-based Systems
(KB4507435).

As a result, I have lost my virtual com ports...

in Device Manager, under USB controllers, they show as USB Serial
Converter (with a yellow triangle with an exclamation mark inside it),
and have the correct driver loaded, but somehow they are not working,
not findable in the config for DXLab Commander, and so I am at a loss
what to do /change / fix next...

Any help will be greatly appreciated.

Thanks & 73 de Dave, W5SV