AA6YQ comments below
--- In dxlab@..., "aburkefl" <aburkefl@...> wrote:
At times, I've changed bands on my K3 and then discovered that Commander did not "follow" the radio. Terminating and restarting Commander generally "cures" the problem - for a while. I'm using a microHAM USB interface and when Commander loses contact with the K3, I can see that the Router still maintains contact with the K3 (patched).
At this point, I can only assume that some other program running in the background is creating some kind of conflict.
Windows won't let more than one application open the same serial port.
The next time this happens, please enable "log debugging info" on the Config window's General tab, wait a minute, disable "log debugging info", and then attach the errorlog.txt file from your Commander folder to an email message to me at aa6yq@... . The errorlog will include Commander's directives to your K3 and the K3's responses, so I'll be able to see what's going on.
I can't remember the name or source of one of those programs that will stop all unnecessary applications and let only the minimum of programs.
Dave, right off the top of your head, is the OCX a potential problem?
Once I tried to start something running involving the MARAC Logger while DXLabs was also running. Could there be a potential conflict if the two are battling for the OCX?
There are many .ocx modules; to which one(s) are you referring?
73,
Dave, AA6YQ
