¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io
  1. DXLab
  2. Topics

Commander loosing control of radios

 

I been having trouble with commander loosing control of my radios and sent an email earlier about it. At that that time I checked all ports to make sure they would not turn off automatically and set Windows Defender (the only anti-virus program on my computer) to accept the DXLabs folder as well as all the individual folders within the main folder.

After doing some checking around, I have found that Commander 1426 works without a glitch. All versions after that produce the connection loss problem. Commander versions 1431 and up will loose contact after 1/2 hour or there abouts. Last week when Version 1455 became available I installed it and upon running it discovered it looses contact every 5 minutes.

I'm happily running 1431 but am curious why later versions are causing the problem. My radios are Yaesu FT-2000 and Ft-847 and my computer is a 6 month old intel i5 with Windows 10Pro..

Any clues would be appreciated.

Tom WN?DRC
 

+ AA6YQ comments below

I been having trouble with commander loosing control of my radios and sent an email earlier about it.

+ Please point me at your previous post here so I can have the full context.

At that that time I checked all ports to make sure they would not turn off automatically and set Windows Defender (the only anti-virus program on my computer) to accept the DXLabs folder as well as all the individual folders within the main folder.

After doing some checking around, I have found that Commander 1426 works without a glitch. All versions after that produce the connection loss problem. Commander versions 1431 and up will loose contact after 1/2 hour or there abouts. Last week when Version 1455 became available I installed it and upon running it discovered it looses contact every 5 minutes.

I'm happily running 1431 but am curious why later versions are causing the problem. My radios are Yaesu FT-2000 and Ft-847 and my computer is a 6 month old intel i5 with Windows 10Pro..

+ Please do the following:

1. start Commander 14.5.5

2. on the Configuration window's General tab, check the "Log debugging info" box

3. wait until Commander stops tracking the radio's frequency changes

4. on the Configuration window's General tab, uncheck the "Log debugging info" box

5. attach the errorlog.txt file to an email message, and send the message to me via

aa6yq (at) ambersoft.com

73,

Dave, AA6YQ
Dave / NR1DX
 

Tom

Since there was also a WIN-10 update recently go check all the settings under power management in Window's setting. and look at the settings on the COM port you use to talk to Commander in device manager (<WIN><X><Device Manager>) I had a similar problem last year after an update where my mouse would would suddenly die after 30minutes . There was a windows setting that powered down some of the USB ports after a while, that the genius's at MS decided to check or uncheck the box for me during an update

Dave
NR1DX

On 4/13/2020 5:06 PM, tgzuber wrote:
I been having trouble with commander loosing control of my radios and sent an email earlier about it. At that that time I checked all ports to make sure they would not turn off automatically and set Windows Defender (the only anti-virus program on my computer) to accept the DXLabs folder as well as all the individual folders within the main folder.

After doing some checking around, I have found that Commander 1426 works without a glitch. All versions after that produce the connection loss problem. Commander versions 1431 and up will loose contact after 1/2 hour or there abouts. Last week when Version 1455 became available I installed it and upon running it discovered it looses contact every 5 minutes.

I'm happily running 1431 but am curious why later versions are causing the problem. My radios are Yaesu FT-2000 and Ft-847 and my computer is a 6 month old intel i5 with Windows 10Pro..

Any clues would be appreciated.

Tom WN?DRC


--
Dave
Manuals@...
www.ArtekManuals.com
--
This email has been checked for viruses by Avast antivirus software.
 

If power on the USB port were the problem it seems the other Commander would
see the same thing. I think it is something else.

Outlook Laptop Gil W0MN
Hierro candente, batir de repente
44.08226N 92.51265W EN34rb

-----Original Message-----
From: [email protected] <[email protected]> On Behalf Of Dave / NR1DX
Sent: Monday, April 13, 2020 16:26
To: [email protected]
Subject: Re: [DXLab] Commander loosing control of radios

Tom

Since there was also a WIN-10 update recently go check all the settings
under power management in Window's setting. and look at the settings on the
COM port you use to talk to Commander in device manager (<WIN><X><Device
Manager>) I had a similar problem last year after an update where my mouse
would would suddenly die after 30minutes . There was a windows setting that
powered down some of the USB ports after a while, that the genius's at MS
decided to check or uncheck the box for me during an update

Dave
NR1DX

On 4/13/2020 5:06 PM, tgzuber wrote:
I been having trouble with commander loosing control of my radios and
sent an email earlier about it. At that that time I checked all ports
to make sure they would not turn off automatically and set Windows
Defender (the only anti-virus program on my computer) to accept the
DXLabs folder as well as all the individual folders within the main
folder.

After doing some checking around, I have found that Commander 1426
works without a glitch. All versions after that produce the connection
loss problem. Commander versions 1431 and up will loose contact after
1/2 hour or there abouts. Last week when Version 1455 became available
I installed it and upon running it discovered it looses contact every
5 minutes.

I'm happily running 1431 but am curious why later versions are causing
the problem. My radios are Yaesu FT-2000 and Ft-847 and my computer is
a 6 month old intel i5 with Windows 10Pro..

Any clues would be appreciated.

Tom WN?DRC



--
Dave
Manuals@...
www.ArtekManuals.com


--
This email has been checked for viruses by Avast antivirus software.








--
W0MN EN34rb 44.08226 N 92.51265 W

Hierro candente, batir de repente

HP Laptop
 

Dave,

Commander 14.6.2 solved the problem.

I installed Commander 14.6.2 on 6/4 and it found my FT-2000? and it has not lost control of it since and I run my computer 24/7. All updates of Commander after 14.3.1 have lost control so I have been running 14.3.1. I did not change anything just installed 14.6.2 and it worked.

One of the intermediate upgrades lost my FT-847 and my computer does not talk to it so now I have to trouble shoot that.

Tom WN?DRC


On 4/13/2020 5:06 PM, tgzuber wrote:
I been having trouble with commander loosing control of my radios and sent an email earlier about it. At that that time I checked all ports to make sure they would not turn off automatically and set Windows Defender (the only anti-virus program on my computer) to accept the DXLabs folder as well as all the individual folders within the main folder.

After doing some checking around, I have found that Commander 1426 works without a glitch. All versions after that produce the connection loss problem. Commander versions 1431 and up will loose contact after 1/2 hour or there abouts. Last week when Version 1455 became available I installed it and upon running it discovered it looses contact every 5 minutes.

I'm happily running 1431 but am curious why later versions are causing the problem. My radios are Yaesu FT-2000 and Ft-847 and my computer is a 6 month old intel i5 with Windows 10Pro..

Any clues would be appreciated.

Tom WN?DRC
 

+ AA6YQ comments below

Commander 14.6.2 solved the problem.

I installed Commander 14.6.2 on 6/4 and it found my FT-2000? and it has not lost control of it since and I run my computer 24/7. All
updates of Commander after 14.3.1 have lost control so I have been running 14.3.1. I did not change anything just installed 14.6.2
and it worked.

One of the intermediate upgrades lost my FT-847 and my computer does not talk to it so now I have to trouble shoot that.

+ When you first reported this behavior back in early April, I asked you to send me an errorlog.txt file:

< /g/DXLab/message/192901>

+ I have no record of receiving an errorlog.txt file from you in response to this message.

+ None of the changes made in Commander 14.6.2 (compared to its predecessor) had anything to do with radio interaction: the changes
were limited to extending user-defined Command Sequences and RadioInfo UDP messages:

< >

73,

Dave, AA6YQ
 

Every time I did an error log it was too large to email so I just ran 14.3.1.

I didn't change any radio settings from 14.3.1 but all the proceeding updates lost connection until 14.6.2.

Tom

On 6/13/2020 4:04 PM, Dave AA6YQ wrote:
+ AA6YQ comments below

Commander 14.6.2 solved the problem.

I installed Commander 14.6.2 on 6/4 and it found my FT-2000? and it has not lost control of it since and I run my computer 24/7. All
updates of Commander after 14.3.1 have lost control so I have been running 14.3.1. I did not change anything just installed 14.6.2
and it worked.

One of the intermediate upgrades lost my FT-847 and my computer does not talk to it so now I have to trouble shoot that.

+ When you first reported this behavior back in early April, I asked you to send me an errorlog.txt file:

< /g/DXLab/message/192901>

+ I have no record of receiving an errorlog.txt file from you in response to this message.

+ None of the changes made in Commander 14.6.2 (compared to its predecessor) had anything to do with radio interaction: the changes
were limited to extending user-defined Command Sequences and RadioInfo UDP messages:

< >

73,

Dave, AA6YQ
 

+ AA6YQ comments below

Every time I did an error log it was too large to email so I just ran 14.3.1.

I didn't change any radio settings from 14.3.1 but all the proceeding updates lost connection until 14.6.2.

+ A wild guess: one of your anti-malware applications was interfering.

73,

Dave, AA6YQ

1 - 8 of 8