I am chasing a problem where I am getting initial start up failures
connecting to RigCAT and I need some help.
Here is the reproducible failure scenario.
I have a virtual com port pair [COM4<->COM14] defined. RigCAT is
configured to use the COM4 end.
When I reboot the PC and start Fldigi, 99.9% of the time RigCAT fails to
initialize. The only entry in the log is:
I: rigCAT_init: Failed serial port test.
At this point I can open the RigCAT configuration screen, change *any*
parameter to a different value and back to the original parameter to get
the INITIALIZE button to enable and once I click on INITIALIZE, RigCAT
connects. The entry in the log file is:
I: testCommPorts: Found serial port COM4
Now at this point, I can shut down and restart Fldigi over and over
again and RigCAT connects to the radio 100% of the time. It just fails
after a PC reboot.
I have checked and before connecting to COM4 with RigCAT after a reboot,
other programs on my PC are properly enumerating the virtual com port
pair (COM4/COM14)
As I indicated above, once in a rare occasion, RigCAT will connect the
first time after a PC reboot, so I am suspecting that RigCAT
initialization is notwaiting long enough for the conditional check to
complete properly or a race condition enumerating the comports.
(WARNING: I am not a programmer or play one on TV, but I have fiddled
with C and C# some, so forgive me if I use the wrong nomenclature).
So I have a few questions.
Is there away to generate a more verbose log file for the rigcat_init
process?
Any help would be well appreciated. I have several hundred people
bugging my about this issue.
-Tim
--
Tim Ellison, W4TME
Customer Experience Manager
FlexRadio Systems™
4616 W Howard Ln, Suite 1-150
Austin, TX 78728
_______________________________________________
fldigi-alpha mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/fldigi-alpha
