Re: [Hamlib-developer] Rigctld fails to find IC7300 in certain setup combinations

[Sakari N. <sak...@ni...>]

HI!

Auto baud is ok. As rigctld always offers 115200 without rigctld's "-s" 
parameter the rig can find it out.
The problem is on other way. If rig has different than "Auto" or 
"115200" rigctld can not figure it out without telling it with "-s 
<rig's speed>"

All that is also ok, as normal cases "-s" should be used then. If user 
has just done RTFM.
But the problem lays with the rigctld's TCP connection.

In case rigctld can not find rig due to baud rate the debug says:

***3:icom.c(833):icom_get_usb_echo_off returning(-5) Communication timed out

icom_rig_open: echo status result=-5
icom_rig_open: Unable to determine Icom echo status -- is rig on and 
connected?
**2:icom.c(1193):icom_rig_open returning(-5) Communication timed out

How ever it opens telnet server for connections normally.
Then, when client connects to server and sends /any command/ _there is 
no response at all. Not even after any possible timeout.
_

Then there is no way for client to know what is happening there!

I assume that if rig initialization goes wrong (debug says:Unable to 
determine Icom echo status -- is rig on and connected?Communication 
timed out).
rigctld should then respond to TCP client _immediately with RPRT -5  (or 
RPRT -20) via TCP connection for every command received.
_

Then client has no need to hang on until possible own timeout (if any).

There is again another "silence response" case that makes client living 
hard.

-- 
Saku
OH1KH

Black Michael kirjoitti 23.1.2025 klo 14.43:
> No debug needed -- this is a known problem with the "link to" entry as 
> the manual explains.  When linked you can only do whatever the link 
> rate is.
>
> I'll have to look that the Icom AUTO baud stuff.  Don't think that's 
> ever been implemented.
>
> Mike W9MDB
>
>
> On Thursday, January 23, 2025 at 02:33:06 AM CST, Sakari Nylund 
> <sak...@ni...> wrote:
>
>
>
> Hi!
>
> Found following bug (or property ... ??):
>
> if icom 7300 rig settings are:
>
> Menu/Set/Connetors/CI-V/CI-V Baud rate = 19200
> Menu/Set/Connetors/CI-V/USB Port = Link to [REMOTE]
>
> rigctld will fail if started without "-s 19200"
>
> Failure is problematic because the telnet connection can still be done
> normally, but there is NO response to any command.
>
> -----------------------------------------------------------------
> Then if icom settings are changed so that:
>
> Menu/Set/Connetors/CI-V/USB Baud rate = AUTO
> Menu/Set/Connetors/CI-V/USB Port = Unlink from [REMOTE]
>
> rigctld does find the rig and telnet connection responds OK when started
> without "-s" parameter.
>
> -----------------------------------------------------------------
>
> if rig settings are again changed:
> Menu/Set/Connetors/CI-V/USB Baud rate = 115200
> Menu/Set/Connetors/CI-V/USB Port = Unlink from [REMOTE]
>
> rigctld does find the rig and telnet connection responds OK when started
> without "-s" parameter.
>
> BUT!:
> If any other baud rate than "Auto" or "115200" is selected at rig side
> rigctld will again fail if started without "-s <same speed as in rig's
> settings>"
>
> Failure is problematic because the telnet connection can still be done
> normally, but there is NO response to any command.
>
>
> This may cause long search for average user because there is no glue
> where to start.
> Debug available if needed (mailing list does not allow ZIP attachment)
>
> -- 
> Saku
> OH1KH
>
>
>
> _______________________________________________
> Hamlib-developer mailing list
> Ham...@li...
> https://lists.sourceforge.net/lists/listinfo/hamlib-developer