Page 1 of 2
Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 22 Jul 2024, 15:40
by wo9b
Been using the Beta version for a week or two. I'm a long time user of Log4OM.
Noticed an intermittent behavior: Program is set to autostart CAT (OmniRig). Roughly 1/3 of the time this fails and the CAT connection is not established. This stands out to me as the previous version never failed to establish the CAT connection. The solution I use is to exit the program and restart it.
I don't know that this a a big deal or not. Let me know if I can provide debug info if you choose to pursue this report.
BTW I have established a specific order for "bringing up" my station to avoid software/hardware conflicts. The order is:
- Boot up Computer
Power on Radio
Start VSPE
Start Log4OM
....
Thanks for the great logging software. I'm a big fan.
MJ WO9B
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 22 Jul 2024, 15:48
by G4POP
Might seem a silly question but where are you setting 'Program is set to autostart CAT (OmniRig).' ?
What VSP emulator are you using?
What radio?
Why are you using a VSP?
What other programs are running?
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 22 Jul 2024, 21:12
by wo9b
Might seem a silly question but where are you setting 'Program is set to autostart CAT (OmniRig).' ?
Settings>Program Configuration>CAT Interface : Settings Tab, first line, CAT auto-start box is checked
What VSP emulator are you using?
Virtual Serial Port Emulator (x64 version)
What radio?
Kenwood TS-590SG
Why are you using a VSP?
The software I use are either OmniRig friendly or not. In particular N1MM does not accommodate OmniRig. I use VSPE to share the TS-590SG com port to allow for both Log4OM and N1MM to operate concurrently with both having CAT control.
What Other Programs are you using?
As stated in the original writeup, the only ham related software running when the bug is noted is VSPE. The normal multitude of Windows 11 software is running of course. It is possible that Chrome may be running, but usually I fire up the radio first.
Additional Info:
Once the CAT connection is established, there is never any problem with drops or errors and lock ups. It is only the initial CAT connection. To emphasize, I am only bringing this up as prior versions NEVER balked on the initial connection. The fix is an exit and restart of Log4OM, so not a huge problem.
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 22 Jul 2024, 21:47
by G4POP
Please try the connect/CAT menu to disconnect/connect instead of a restart and report the results
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 24 Jul 2024, 13:27
by wo9b
Took a day or so for the error to show up again.
Just now booted computer, started VSPE, started Log4OM..... CAT connection failed.
Stop CAT
Start CAT ... No effect
Exit Log4OM, Stop VSPE, Start VSPE, Start Log4OM..... CAT connection successful.
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 24 Jul 2024, 14:24
by G4POP
What happens if you use Log4OM with Omnirig direct to the radio - no VSPE or N1MM?
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 24 Jul 2024, 23:03
by wo9b
I set up Omni Rig slot #2 for testing your request: No VSPE nor N1MM running.
I booted the computer 6 times: No CAT connection failure occurred. The Stop CAT and Start CAT button worked perfectly.
I also use SDR Console to provide a band scope capability and that is a Omni Rig friendly software package as well. That is working flawlessly using Omni Rig slot #2.
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 24 Jul 2024, 23:12
by G4POP
Are you running Omnirig, log4OM and SDRRC as an administrator?
If not check the Omnirig information which stipulates that if using Omnirig's multithreading ability then all prograns should be 'run as an administrator'
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 24 Jul 2024, 23:27
by wo9b
Yes. All the programs are run As Administrator.
Re: Beta Ver 2.32.1.6 - Start Up Intermitant Bug
Posted: 25 Jul 2024, 07:35
by G4POP
Strange one!
Are you sure about running as an admin, did you check properties/compatability for each application?
I would try a different VSP, perhaps ComOcom