Re: [Hamlib-developer] Rig Control Error

[Michael M. <cmo...@gm...>]

Hey Uwe - would it make sense for the diagnostic mode when it starts to
maybe iterate the available serial ports.  So instances like this would be
easy for us to know what ports are available?

73,  Michael, AA5SH

On Tue, Nov 11, 2025 at 9:35 AM Dave Baxter via Hamlib-developer <
ham...@li...> wrote:

> Just a thought.
>
> Does COM3 actually exist, and is it actually the rig?
>
> (Windows can re-enumerate ports as things are connected/removed, or when
> coming out of a sleep state, so sometimes what was on "COMx" is now on
> "COMy" !   There are ways to nail things down to stop that, but you then
> have to be very careful to reconnect things to the same physical USB port
> on the PC.   Put a Hub in the mix, and it gets very complicated very fast!)
>
> Is the rig connected by native USB, or via a common USB-Serial / CI-V
> adapter?   Many of such will have their drivers blocked by Windows, as
> there are hoards of fake chipsets out there used for such things, even FTDI
> look-alikes!
>
> If a native USB connection, what does Windows Device Manager say about it?
>
> Does any other software (Icom specific for the rig for example?) work OK
> with the radio?   If not, are the correct drivers installed?
>
> Also, does the rig have CI-V "Trancieve" enabled?   If so, try with that
> disabled.  (Though I think later Hamlib instances would disable that
> automagically if it was detected.)
>
> Just idle thoughts, based on experiences with that OS and COM ports in the
> past work life, where we often had multiple USB and serial connected
> instrumentation "things" at the same time.   Sometimes, Windows going to
> sleep, and then coming out of that, the Universe would implode, as various
> pieces of software suddenly lost sight of what they expected.
>
> That was true from Windows XP through Windows 10.   Glad I have nothing to
> do with that OS any more!.
>
> 73.
>
> Dave G8KBV.
>
>
> On 11/11/2025 14:09, prb...@gm... wrote:
>
> Hi Uwe
>
>
>
> Thanks for your help, I apologise if I appear to be making it complicated.
>
>
>
> I have downloaded V3.0 as you said and this time the Hamlib update button
> worked, but still the same error with no comms to the rig.
>
>
>
> I have set the diagnose mode and shut the program, then restarted it and
> closed it again.
>
>
>
> I have found the attached 2 log files from the desktop, is this what you
> required ?
>
>
>
> Thanks again
>
>
>
> Regards
>
>
>
> Peter
>
>
>
> 73
>
>
>
> M7PTS
>
>
>
> *From:* Uwe, DG2YCB <dg...@gm...> <dg...@gm...>
> *Sent:* 10 November 2025 13:49
> *To:* Peter Bearne <prb...@gm...> <prb...@gm...>; Hamlib
> Developers <ham...@li...>
> <ham...@li...>
> *Subject:* Re: [Hamlib-developer] Rig Control Error
>
>
>
> Sorry, I meant, of course: Follow the instructions (= restart *the
> program*, reproduce the error for a few seconds and close the program
> again)
>
>
> 73 de DG2YCB,
> Uwe
> ________________________________________
> German Amateur Radio Station DG2YCB
> Dr. Uwe Risse
> eMail: dg...@gm...
> Info: www.qrz.com/db/DG2YCB
>
> Am 10.11.2025 um 14:45 schrieb Uwe, DG2YCB via Hamlib-developer:
>
> Follow the instructions (= restart your computer, reproduce the error for
> a few seconds and close the program again)
>
>
>
> _______________________________________________
> Hamlib-developer mailing lis...@li...://lists.sourceforge.net/lists/listinfo/hamlib-developer
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer
>