Date   

DXlab Commander support for the Yaesu FT-891

Dave AA6YQ
 

+ AA6YQ comments below

Don't know why you don't see the FT-891 in the Commander list, but I wouldn't have spent a lot of time developing user defined sequences for an unsupported radio!

Works fine here. You should check with Dave on the DxLab group.

+ Commander has supported the FT-891 since the public release of Commander version 12.3.9 on 2016-11-01; see

https://www.dxlabsuite.com/commander/ReleaseNotes/1239.txt

+ and

https://www.dxlabsuite.com/commander/versions.htm

+ I evidently neglected to add the FT-891 to the documentation in

https://www.dxlabsuite.com/commander/radios.htm

+ That defect has now been corrected.

+ The current version of Commander is 15.5.1.

73,

Dave, AA6YQ


Re: SpotCollector WWV Old Info

w6de
 

Bill, thank you for the many years of reliable service your node has provided to me and others.  It will surely get a workout next weekend.

 

Very Best Regards,

Dave, w6de

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of n6ws via groups.io
Sent: 19 November, 2022 17:27
To: DXLab@groups.io
Subject: Re: [DXLab] SpotCollector WWV Old Info

 

Kent, Joe, & Dave,

If a user is connected to a DXSpider node, and is not receiving WWV updates, the user should enter the command:

set/wwv

The set/wwv command will enable WWV notifications to be sent to that terminal.  

If the user is connected to a DXSpider node, and wants the latest WWV data at login, they can initiate a startup script that automatically downloads the latest WWV data at login by entering the following commands in sequence:

set/startup
show/wwv 1
/ex


That script will remain on the DXSpider node and show the latest WWV data at every login.  The user should then receive normal updates of WWV info at the normal announcement times every three hours.  

73, Bill
N6WS

On 11/19/2022 9:19 AM, Kent N6WT wrote:

Joe

 

Thanks

 

73

Kent

N6WT

 

 

On Sat, Nov 19, 2022 at 8:39 AM Joe Subich, W4TV <lists@...> wrote:

Yes

73,

    ... Joe, W4TV

On 2022-11-19 10:58 AM, Kent N6WT wrote:
> Dave
>
> If I do a "sh/wwv" in the spot source window, will that update the info on
> the SC main window??
>
> Thanks
> 73
> Kent
> N6WT
>
>
> On Fri, Nov 18, 2022 at 7:04 PM Dave AA6YQ <aa6yq@...> wrote:
>
>> + AA6YQ comments below
>>
>> I am looking at the WWV info on SC. Mine is currently showing 11-18
>> 15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?
>>
>> + SpotCollector obtains SFI, A, and K information from WWV spots conveyed
>> by spot sources connected to the worldwide DX Cluster network. Such spots
>> typically appear every 3 hours or so, but not all spot sources convey them.
>>
>> + See
>>
>>
>> https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#WWV%20Propagation%20Reports
>>
>>         73,
>>
>>                Dave, AA6YQ
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>




-- 
73, Bill
N6WS


Re: FT-891 Not in Commander Supported Radio list

John P
 

Yes Bruce, but it's not listed in the list on the web page.
--
John P.
WA2FZW


Re: FT-891 Not in Commander Supported Radio list

Bruce N7XGR
 

John,  Version 15.2.0 for the Commander Configuration General tab
has the FT891 in the Radio dropdown.

Bruce  N7XGR


On Sat, Nov 19, 2022 at 7:15 AM John P <j.m.price@...> wrote:
Dave it was brought to my attention on the FT-891 group that the Yaesu FT-891 isn't listed in the list of supported radios for Commander.
--
John P.
WA2FZW


Re: SpotCollector WWV Old Info

n6ws
 

Kent, Joe, & Dave,

If a user is connected to a DXSpider node, and is not receiving WWV updates, the user should enter the command:

set/wwv

The set/wwv command will enable WWV notifications to be sent to that terminal.  

If the user is connected to a DXSpider node, and wants the latest WWV data at login, they can initiate a startup script that automatically downloads the latest WWV data at login by entering the following commands in sequence:

set/startup
show/wwv 1
/ex


That script will remain on the DXSpider node and show the latest WWV data at every login.  The user should then receive normal updates of WWV info at the normal announcement times every three hours.  

73, Bill
N6WS

On 11/19/2022 9:19 AM, Kent N6WT wrote:
Joe

Thanks

73
Kent
N6WT


On Sat, Nov 19, 2022 at 8:39 AM Joe Subich, W4TV <lists@...> wrote:
Yes

73,

    ... Joe, W4TV

On 2022-11-19 10:58 AM, Kent N6WT wrote:
> Dave
>
> If I do a "sh/wwv" in the spot source window, will that update the info on
> the SC main window??
>
> Thanks
> 73
> Kent
> N6WT
>
>
> On Fri, Nov 18, 2022 at 7:04 PM Dave AA6YQ <aa6yq@...> wrote:
>
>> + AA6YQ comments below
>>
>> I am looking at the WWV info on SC. Mine is currently showing 11-18
>> 15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?
>>
>> + SpotCollector obtains SFI, A, and K information from WWV spots conveyed
>> by spot sources connected to the worldwide DX Cluster network. Such spots
>> typically appear every 3 hours or so, but not all spot sources convey them.
>>
>> + See
>>
>>
>> https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#WWV%20Propagation%20Reports
>>
>>         73,
>>
>>                Dave, AA6YQ
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>





-- 
73, Bill
N6WS


Re: SpotCollector WWV Old Info

Kent N6WT
 

Joe

Thanks

73
Kent
N6WT


On Sat, Nov 19, 2022 at 8:39 AM Joe Subich, W4TV <lists@...> wrote:
Yes

73,

    ... Joe, W4TV

On 2022-11-19 10:58 AM, Kent N6WT wrote:
> Dave
>
> If I do a "sh/wwv" in the spot source window, will that update the info on
> the SC main window??
>
> Thanks
> 73
> Kent
> N6WT
>
>
> On Fri, Nov 18, 2022 at 7:04 PM Dave AA6YQ <aa6yq@...> wrote:
>
>> + AA6YQ comments below
>>
>> I am looking at the WWV info on SC. Mine is currently showing 11-18
>> 15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?
>>
>> + SpotCollector obtains SFI, A, and K information from WWV spots conveyed
>> by spot sources connected to the worldwide DX Cluster network. Such spots
>> typically appear every 3 hours or so, but not all spot sources convey them.
>>
>> + See
>>
>>
>> https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#WWV%20Propagation%20Reports
>>
>>         73,
>>
>>                Dave, AA6YQ
>>
>>
>>
>>
>>
>>
>>
>
>
>
>
>
>






Re: SpotCollector WWV Old Info

Joe Subich, W4TV
 

Yes

73,

... Joe, W4TV

On 2022-11-19 10:58 AM, Kent N6WT wrote:
Dave
If I do a "sh/wwv" in the spot source window, will that update the info on
the SC main window??
Thanks
73
Kent
N6WT
On Fri, Nov 18, 2022 at 7:04 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

I am looking at the WWV info on SC. Mine is currently showing 11-18
15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?

+ SpotCollector obtains SFI, A, and K information from WWV spots conveyed
by spot sources connected to the worldwide DX Cluster network. Such spots
typically appear every 3 hours or so, but not all spot sources convey them.

+ See


https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#WWV%20Propagation%20Reports

73,

Dave, AA6YQ







Re: SpotCollector WWV Old Info

Kent N6WT
 

Dave

If I do a "sh/wwv" in the spot source window, will that update the info on the SC main window??

Thanks
73
Kent
N6WT


On Fri, Nov 18, 2022 at 7:04 PM Dave AA6YQ <aa6yq@...> wrote:
+ AA6YQ comments below

I am looking at the WWV info on SC. Mine is currently showing 11-18 15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?

+ SpotCollector obtains SFI, A, and K information from WWV spots conveyed by spot sources connected to the worldwide DX Cluster network. Such spots typically appear every 3 hours or so, but not all spot sources convey them.

+ See

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#WWV%20Propagation%20Reports

       73,

              Dave, AA6YQ







FT-891 Not in Commander Supported Radio list

John P
 

Dave it was brought to my attention on the FT-891 group that the Yaesu FT-891 isn't listed in the list of supported radios for Commander.
--
John P.
WA2FZW


Re: Synching up ARRL DXCC Credits and DXKeeper

BILL KENNAMER
 

Having been at the DXCC desk during the transition to computer, here is how it worked.

Your original, pre computer submission required that you fill out the blanks with a callsign beside the country name on a printed DXCC list. This became your permanent record. There was no provision for band or mode because originally there were only two types of DXCC, phone and mixed. The record was marked as such on the front page, and future submissions simply had new callsigns added to the original submission record. Some of them got pretty tattered over 50 years, I can tell you. Files were kept in order by last submission date, which is why you were asked to provide it on subsequent submissions.

When 5 band DXCC was introduced, it was even simpler; when the submission was made (separately from a regular submission), cards were simply counted per band and verified for accuracy. An award number was assigned, and, since the award was non-endorseable, the lists were thrown away, so there is no record at DXCC of any cards submitted for 5Band before 1992.

When the transition to computer was made in 1992, only the entity code was entered into the computer. If you had mixed, phone, and cw, that meant three original lists had to be entered, one for each mode. Only a number and mode for the mode specific awards was entered.

If you need band or mode credit for those old cards, they must be submitted again.

On Friday, November 18, 2022, 4:03 PM, WB1DX <wb1dx@...> wrote:

Thanks for the confirmation and for the awesome tool(s) that you have created for the amateur radio community. After spending some more time with the various check progress features, I certainly appreciate the feature/functionality that is offered.

Regards, Ken
WB1DX


Re: SpotCollector WWV Old Info

Dave AA6YQ
 

+ AA6YQ comments below

I am looking at the WWV info on SC. Mine is currently showing 11-18 15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?

+ SpotCollector obtains SFI, A, and K information from WWV spots conveyed by spot sources connected to the worldwide DX Cluster network. Such spots typically appear every 3 hours or so, but not all spot sources convey them.

+ See

https://www.dxlabsuite.com/spotcollector/Help/SpotDatabase.htm#WWV%20Propagation%20Reports

73,

Dave, AA6YQ


SpotCollector WWV Old Info

Kent N6WT
 

I am looking at the WWV info on SC. Mine is currently showing 11-18 15;06Z. The current time is 11-19 02:54Z. Why does it not update regularly?

Thanks
73
Kent
N6WT


Re: Synching up ARRL DXCC Credits and DXKeeper

Joe Subich, W4TV
 

On 2022-11-18 5:54 PM, Dave AA6YQ wrote:

+ There was a time before the DXCC desk used computers. If you submitted a QSL card during that time, you were only granted credit for the QSO's Entity-Band and Entity-Mode if you specifically
requested it.
Specifically, this was in the days of "paper" records at ARRL HQ.
Individual records (paper sheets) were kept for Mixed, CW, Phone,
and RTTY DXCC and for the "endorseable" single band awards - 80,
40, 20, 15 and 10 meters. For those "cards", one would either
receive entity-mode or entity-band credit but not entity-band-mode
unless one had used the same card for both mode and band endorsements.
If one never applied for the single band awards there would be no
entity-band credit.

I still have some 250+ QSOs between 1977 and 1984 in my log marked
QSL_RCVD='M'. All have been replaced by other QSLs for Challenge
(entity-band) credit over the years.

73,

... Joe, W4TV

On 2022-11-18 5:54 PM, Dave AA6YQ wrote:
+ AA6YQ comment sbelow


Nevertheless the question is are entity band and or entity mode etc.
credit automatically given for QSOes confirmed via LotW? I assume so but
thought I would ask
+ Yes, when you submit a QSO confirmed via LoTW or QSL card for DXCC award credit, you will receive credit for the QSO's Entity, Entity-Band, and Entity-Mode.
+ There was a time before the DXCC desk used computers. If you submitted a QSL card during that time, you were only granted credit for the QSO's Entity-Band and Entity-Mode if you specifically requested it. Thus there are ops like Ken WB2DX who have confirmed QSOs with "Entity-only" credit, or "Entity and Entity-Band" credit, or "Entity and Entity-Mode" credit. To accurately reflect these three scenarios,
1. check the "Partial DXCC Credit" box in the "Log Settings" panel on DXKeeper's Configuration window's Log tab
2. set the QSO's "QSL Rcvd" item to E for "Entity-only" credit, B for "Entity and Entity-Band" credit, or M for "Entity and Entity-Mode" credit.
+ See
https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Partial%20DXCC%20Credit
73,
Dave, AA6YQ


Re: Synching up ARRL DXCC Credits and DXKeeper

Dave AA6YQ
 

+ AA6YQ comment sbelow
Nevertheless the question is are entity band and or entity mode etc. credit automatically given for QSOes confirmed via LotW? I assume so but thought I would ask

+ Yes, when you submit a QSO confirmed via LoTW or QSL card for DXCC award credit, you will receive credit for the QSO's Entity, Entity-Band, and Entity-Mode.

+ There was a time before the DXCC desk used computers. If you submitted a QSL card during that time, you were only granted credit for the QSO's Entity-Band and Entity-Mode if you specifically requested it. Thus there are ops like Ken WB2DX who have confirmed QSOs with "Entity-only" credit, or "Entity and Entity-Band" credit, or "Entity and Entity-Mode" credit. To accurately reflect these three scenarios, 

1. check the "Partial DXCC Credit" box in the "Log Settings" panel on DXKeeper's Configuration window's Log tab
2. set the QSO's "QSL Rcvd" item to E for "Entity-only" credit, B for "Entity and Entity-Band" credit, or M for "Entity and Entity-Mode" credit.

+ See

https://www.dxlabsuite.com/dxkeeper/Help/Configuration.htm#Partial%20DXCC%20Credit

      73,

            Dave, AA6YQ

 

 


Re: Synching up ARRL DXCC Credits and DXKeeper

Gilbert Baron W0MN
 

At my age and station the chance of getting the challenge award is likely 0 to .0005. % . Likely will have to be satisfied with DXCC and other easier to obtain awards. Nevertheless the question is are entity band and or entity mode etc. credit automatically given for QSOes confirmed via LotW? I assume so but thought I would ask.

Outlook LT Gil W0MN
Hierro Candente Batir de Repente
44.08226 N 92.51265 W EN34rb

-----Original Message-----
From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Dave AA6YQ
Sent: Friday, November 18, 2022 2:17 PM
To: DXLab@groups.io
Subject: Re: [DXLab] Synching up ARRL DXCC Credits and DXKeeper

+ AA6YQ comments below
I thought I was all synched up and had everything accurate until I looked a bit closer, specifically to the DXCC Challenge stats. I know what the issue is I'm just not sure what the best solution is, so I'm looking for some feedback before I go to far.

The issue is this. My very first DXCC submission contained about 130 QSL cards all applied to the MIXED category. All of these credits appear in my DXCC account for the entity only. No Band or Mode is associated with them. Because there's no band, I am not receiving any credit for these contacts towards the DXCC Challenge. Well not all of them, just the entities where I do not have another confirmed/submitted contact which also gives me credit for the band (and mode).

My thought is to resubmit these cards to the desk so that I get the band and mode credits, then update and link these QSO's to the appropriate QSL Credit. This would also take care of the missing Challenge credits.

I could go through DXKeeper and change the QSL received status to "E", but the entity still shows up as "C" in DXView (confusing)

+ DXView's DXCC progress table does not display entity credit; it displays entity-band and entity-mode credit.

and this does not get me the credit for DXCC Challenge.

+ That's correct. If you set a QSO's "QSL Rcvd" or "LoTW QSL Rcvd" item to 'E', then that QSO does not contribute the Entity-Band credit required for DXCC Challenge.

Are there any other options here that would get me the missing Challenge Credits and synch up my account to my log?

+ The only way to obtain missing Challenge credits is to resubmit your "Entity-credit only" cards to the DXCC desk. After they notify you that they've processed your submission, you can direct DXKeeper to Verify that submission, which will update your DXCC award family progress.

73,

Dave, AA6YQ









--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop


Re: Synching up ARRL DXCC Credits and DXKeeper

WB1DX
 

Thanks for the confirmation and for the awesome tool(s) that you have created for the amateur radio community. After spending some more time with the various check progress features, I certainly appreciate the feature/functionality that is offered.

Regards, Ken
WB1DX


Re: Synching up ARRL DXCC Credits and DXKeeper

Dave AA6YQ
 

+ AA6YQ comments below
I thought I was all synched up and had everything accurate until I looked a bit closer, specifically to the DXCC Challenge stats. I know what the issue is I'm just not sure what the best solution is, so I'm looking for some feedback before I go to far.

The issue is this. My very first DXCC submission contained about 130 QSL cards all applied to the MIXED category. All of these credits appear in my DXCC account for the entity only. No Band or Mode is associated with them. Because there's no band, I am not receiving any credit for these contacts towards the DXCC Challenge. Well not all of them, just the entities where I do not have another confirmed/submitted contact which also gives me credit for the band (and mode).

My thought is to resubmit these cards to the desk so that I get the band and mode credits, then update and link these QSO's to the appropriate QSL Credit. This would also take care of the missing Challenge credits.

I could go through DXKeeper and change the QSL received status to "E", but the entity still shows up as "C" in DXView (confusing)

+ DXView's DXCC progress table does not display entity credit; it displays entity-band and entity-mode credit.

and this does not get me the credit for DXCC Challenge.

+ That's correct. If you set a QSO's "QSL Rcvd" or "LoTW QSL Rcvd" item to 'E', then that QSO does not contribute the Entity-Band credit required for DXCC Challenge.

Are there any other options here that would get me the missing Challenge Credits and synch up my account to my log?

+ The only way to obtain missing Challenge credits is to resubmit your "Entity-credit only" cards to the DXCC desk. After they notify you that they've processed your submission, you can direct DXKeeper to Verify that submission, which will update your DXCC award family progress.

73,

Dave, AA6YQ


Synching up ARRL DXCC Credits and DXKeeper

WB1DX
 

I thought I was all synched up and had everything accurate until I looked a bit closer, specifically to the DXCC Challenge stats. I know what the issue is I'm just not sure what the best solution is, so I'm looking for some feedback before I go to far.

The issue is this. My very first DXCC submission contained about 130 QSL cards all applied to the MIXED category. All of these credits appear in my DXCC account for the entity only. No Band or Mode is associated with them. Because there's no band, I am not receiving any credit for these contacts towards the DXCC Challenge. Well not all of them, just the entities where I do not have another confirmed/submitted contact which also gives me credit for the band (and mode).

My thought is to resubmit these cards to the desk so that I get the band and mode credits, then update and link these QSO's to the appropriate QSL Credit. This would also take care of the missing Challenge credits.

I could go through DXKeeper and change the QSL received status to "E", but the entity still shows up as "C" in DXView (confusing) and this does not get me the credit for DXCC Challenge.

Are there any other options here that would get me the missing Challenge Credits and synch up my account to my log?

Thanks in advance,
Ken
WB1DX


Re: windows update reassigned comports and lost rig control

Rick Murphy
 

True, Windows 11 "broke" it. Still quite a useful shortcut.
73,
    -Rick

On Thu, Nov 17, 2022 at 9:43 PM Ken Bandy, KJ9B <ken.kj9b@...> wrote:

Interesting shortcut, Rick.  Actually on my W11 laptop, the Windows and Break key brings up the “System>About” screen, on which Device Manager is available by scrolling down.  Still pretty cool!

 

73,

Ken, KJ9B

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Rick Murphy
Sent: Thursday, November 17, 2022 21:34
To: DXLab@groups.io
Subject: Re: [DXLab] windows update reassigned comports and lost rig control

 

Device Manager opens if you hold down the "Windows" key then press the Break key.

(Break Windows, get it?)

73,

    -Rick

 

On Thu, Nov 17, 2022 at 9:02 PM Ken Bandy, KJ9B <ken.kj9b@...> wrote:

Great idea, Bruce!  I had thought of doing this on my laptop, that I use for POTA.  I use my Ten-Tec Eagle for POTA, and invariably, I will have to restart the Eagle multiple times to get the USB control to actually “take”.  The shortcuts will save lots of time getting to the Device Manager.

 

73,

Ken, KJ9B

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Bruce N7XGR
Sent: Thursday, November 17, 2022 18:34
To: DXLab@groups.io
Subject: Re: [DXLab] windows update reassigned comports and lost rig control

 

Dave and others,  On every computer that I have used I have a shortcut

for the Device Manager and the Control Panel on the desktop.

I have them there because of frequent checking especially the Device Manager

for troubleshooting purposes.

My location for Device Manager is here, C:\Windows\System32\devmgmt.msc

Right click on it and select Send to, then click on Desktop (create shortcut).

Once on the desktop you can rename this to simply Device.

Control Panel location is here, C:\Windows\System32\control.exe

Do the same for creating a shortcut then rename this to simply Control.

 

Hope this helps,  Bruce  N7XGR

 

On Thu, Nov 17, 2022 at 5:08 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

Hello ….I have been running DX Labs suite and HDSDR with a TS-590SG and a TS50D for years with little trouble but today after the latest Windows Feature update…I have lost rig control on the 590 and have partial rig control on the 570. I have used comport 5 for the 590 and comport 4 for the 570 . Comport 4 allow for partial rig control thru the 570 but comport 5 does nothing for the 590. The UART bridge is using comport 5. Unfortunately I did not record the previous UART bridge comport.

How can I reassign the proper comports ?  Should I delete Commander and start over?

+ That won't correct the situation, but might create a much bigger problem.

Should I delete the UART bridge and re download it?

+ That won't correct the situation either.

I am not a computer wizard but I got this thing to work once .

+ The second rule of computing is "If you're using Windows, don't guess!". Windows is a fragile operating system. It is all too easy to make changes that result in your having to re-install it and then re-install your applications.  So if you encounter a situation where you don't know what to do, seek assistance, rather than try something with the hope that it will succeed; a wrong guess could make things much worse.

I have read about this and since I did not record the UART comport location prior to this mess have I screwed the pooch?

+  What's happened is that Windows has given different names to your COM ports. What was previously COM 4 might now be COM 8, for example. Writing down your previous COM port assignments would not have shed light on the new COM port assignments.

+ Step one is to determine what COM ports are currently present. To do that,

1. open the Windows Control Panel, and click the entry for "Hardware and Sound"

2. on the right side of window, under "Devices and Printers", click on "Device Manager"

3. in the "Device Manager" window,

3a. open on the View menu, and invoke the "Show hidden devices" command

3b. in the list of devices, find the "Ports (COM & LPT)" entry; click the > character to its left to expand this section to show which COM ports are present

+ Which COM ports are listed as present? Please post the exact text of each entry in the expanded the "Ports (COM & LPT)" section.

       73,

               Dave, AA6YQ





 

--

Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA



--
Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA


Re: windows update reassigned comports and lost rig control

Ken Bandy, KJ9B
 

Interesting shortcut, Rick.  Actually on my W11 laptop, the Windows and Break key brings up the “System>About” screen, on which Device Manager is available by scrolling down.  Still pretty cool!

 

73,

Ken, KJ9B

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Rick Murphy
Sent: Thursday, November 17, 2022 21:34
To: DXLab@groups.io
Subject: Re: [DXLab] windows update reassigned comports and lost rig control

 

Device Manager opens if you hold down the "Windows" key then press the Break key.

(Break Windows, get it?)

73,

    -Rick

 

On Thu, Nov 17, 2022 at 9:02 PM Ken Bandy, KJ9B <ken.kj9b@...> wrote:

Great idea, Bruce!  I had thought of doing this on my laptop, that I use for POTA.  I use my Ten-Tec Eagle for POTA, and invariably, I will have to restart the Eagle multiple times to get the USB control to actually “take”.  The shortcuts will save lots of time getting to the Device Manager.

 

73,

Ken, KJ9B

 

From: DXLab@groups.io <DXLab@groups.io> On Behalf Of Bruce N7XGR
Sent: Thursday, November 17, 2022 18:34
To: DXLab@groups.io
Subject: Re: [DXLab] windows update reassigned comports and lost rig control

 

Dave and others,  On every computer that I have used I have a shortcut

for the Device Manager and the Control Panel on the desktop.

I have them there because of frequent checking especially the Device Manager

for troubleshooting purposes.

My location for Device Manager is here, C:\Windows\System32\devmgmt.msc

Right click on it and select Send to, then click on Desktop (create shortcut).

Once on the desktop you can rename this to simply Device.

Control Panel location is here, C:\Windows\System32\control.exe

Do the same for creating a shortcut then rename this to simply Control.

 

Hope this helps,  Bruce  N7XGR

 

On Thu, Nov 17, 2022 at 5:08 PM Dave AA6YQ <aa6yq@...> wrote:

+ AA6YQ comments below

Hello ….I have been running DX Labs suite and HDSDR with a TS-590SG and a TS50D for years with little trouble but today after the latest Windows Feature update…I have lost rig control on the 590 and have partial rig control on the 570. I have used comport 5 for the 590 and comport 4 for the 570 . Comport 4 allow for partial rig control thru the 570 but comport 5 does nothing for the 590. The UART bridge is using comport 5. Unfortunately I did not record the previous UART bridge comport.

How can I reassign the proper comports ?  Should I delete Commander and start over?

+ That won't correct the situation, but might create a much bigger problem.

Should I delete the UART bridge and re download it?

+ That won't correct the situation either.

I am not a computer wizard but I got this thing to work once .

+ The second rule of computing is "If you're using Windows, don't guess!". Windows is a fragile operating system. It is all too easy to make changes that result in your having to re-install it and then re-install your applications.  So if you encounter a situation where you don't know what to do, seek assistance, rather than try something with the hope that it will succeed; a wrong guess could make things much worse.

I have read about this and since I did not record the UART comport location prior to this mess have I screwed the pooch?

+  What's happened is that Windows has given different names to your COM ports. What was previously COM 4 might now be COM 8, for example. Writing down your previous COM port assignments would not have shed light on the new COM port assignments.

+ Step one is to determine what COM ports are currently present. To do that,

1. open the Windows Control Panel, and click the entry for "Hardware and Sound"

2. on the right side of window, under "Devices and Printers", click on "Device Manager"

3. in the "Device Manager" window,

3a. open on the View menu, and invoke the "Show hidden devices" command

3b. in the list of devices, find the "Ports (COM & LPT)" entry; click the > character to its left to expand this section to show which COM ports are present

+ Which COM ports are listed as present? Please post the exact text of each entry in the expanded the "Ports (COM & LPT)" section.

       73,

               Dave, AA6YQ





 

--

Rick Murphy, D. Sc., CISSP-ISSAP, K1MU/4, Annandale VA USA