Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
Search
Losing Contact With Commander
|
aburkefl
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. 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? Art - N4PJ |
--- In dxlab@..., "aburkefl" <aburkefl@...> wrote:AA6YQ comments below 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? 73,There are many .ocx modules; to which one(s) are you referring? Dave, AA6YQ |
|
aburkefl
Not exactly certain how to engage this scenario. If I turn on "log debugging" and don't lose control, you'll learn nothing. If I work for a while and then discover I've lost contact with Commander, that won't help either, will it?
toggle quoted message
Show quoted text
How large can the file get before it will give you problems? I could turn debugging on first thing and then run as normal as possible (at least as normally as I've been running!), but the debugging file might get kind of large. Art - N4PJ --- In dxlab@..., "aa6yq" <aa6yq@...> wrote:
--- In dxlab@..., "aburkefl" <aburkefl@> wrote:AA6YQ comments below |
|
Your initial report stated that at some point, "Commander did not 'follow'
toggle quoted message
Show quoted text
the radio". This is the time to enable "log debugging info" for a minute or two, then disable it and send me the resulting errorlog.txt file. I just need to see what commands are being sent to your K3, and how your K3 is responding to those commands. 73, Dave, AA6YQ -----Original Message-----
From: dxlab@... [mailto:dxlab@...]On Behalf Of aburkefl Sent: Monday, September 07, 2009 8:00 AM To: dxlab@... Subject: [dxlab] Re: Losing Contact With Commander Not exactly certain how to engage this scenario. If I turn on "log debugging" and don't lose control, you'll learn nothing. If I work for a while and then discover I've lost contact with Commander, that won't help either, will it? How large can the file get before it will give you problems? I could turn debugging on first thing and then run as normal as possible (at least as normally as I've been running!), but the debugging file might get kind of large. Art - N4PJ --- In dxlab@..., "aa6yq" <aa6yq@...> wrote: did not "follow" the radio. Terminating and restarting Commander generally--- In dxlab@..., "aburkefl" <aburkefl@> wrote:AA6YQ comments below "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). background is creating some kind of conflict. Config window's General tab, wait a minute, disable "log debugging info",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 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. stop all unnecessary applications and let only the minimum of programs. DXLabs was also running. Could there be a potential conflict if the two are battling for the OCX? 73,There are many .ocx modules; to which one(s) are you referring? ------------------------------------ Yahoo! Groups Links No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.339 / Virus Database: 270.13.74/2339 - Release Date: 09/06/09 05:51:00 |
|
aburkefl
Okay - I understand. I guess where my thought processes were was that you needed to see what "stopped" when the contact was lost.
toggle quoted message
Show quoted text
I'll play with it some and see if I can be aware when the contact goes away. The MARAC Logger that I thought was possibly part of the problem doesn't use a serial port, so there's no competition there, at least not for COM control. The contact between Commander and the K3 did seem much better after I changed the router to use the "patched" version of the K3 file. It's just irritating to change bands and suddenly discover that Commander didn't react and DXKeeper, instead of recording the change to 17M, left the freq on 20M. Most of my activity lately has been relegated mostly to 20M, so it hasn't been too scary. Art - N4PJ --- In dxlab@..., "Dave AA6YQ" <aa6yq@...> wrote:
|
to navigate to use esc to dismiss