[Hamlib-developer] Re: Ham lib errors

[Stephane F. <f4...@fr...>]

Hi John,

On Mon, Sep 17, 2001, ROBERTS,JOHN (A-USA,ex1) wrote:
> I have an Icom 756 Pro connected via IcomCT-17 to a laptop running RedHat
> 7.1.
> 
> Is there a mailing list for hamlib?

yep, this is <ham...@li...>
This reply has been Cc'd to it. I hope you won't mind.

> When I run testrig I get these errors. Any idea where I should look to fix
> them?

The problem lies with the wrong CI-V address Hamlib is using with your 756PRO.
It looks like you selected "icall" backend, which is a good choice,
however, the icall backend is using the 706MkIIg as a default CI-V address.
The easiest fix (read ugly hack), is to edit line 58 of icom/icall.c
and change 0x58 to 0x5c.
Recompile, and give it another try. That should do it.

> jroberts@scif44ab(/mnt/geiswd/home/jroberts/src/hamlib-1.1.1/tests) 94$
> ./testrig 34
> testrig:hello, I am your main() !
> rig: loading backend icom
> icom: _init called
> rig_register (43)
> rig_register (44)
> rig_register (45)
> rig_register (76)
> rig_register (34)
> Calling init
> rig:rig_init called 
> After init
> Calling rig_open
> rig:rig_open called 
> Unsupported PTT type 1
> Port /dev/usb/ttyUSB0 opened ok
> TX 8 bytes
> 0000     ff fe fe 58 e0 07 01 fd        ...X....
                    ^^
  This is the rig address. The 756PRO has default set to 5c. That's why
it's not responding to simple command transmitted. With the change in icall.c,
this field should change, and also you should expect some reply...

> rig timeout after 7 chars or select error - Resource temporarily
> unavailable!
> rig timeout after 0 chars or select error - Resource temporarily
> unavailable!
> rig timeout after 0 chars or select error - Resource temporarily
> unavailable!
> icom_set_vfo: ack NG (0x07), len=2
> rig_set_vfo: error = Command rejected by the rig 
[snip]

Hamlib-1.1.2, which is expected to be release soon (as soon as I get
this #$%@$ libltl fixed properly), has a much cleaner approach
to cope with CI-V addresses (which are specific to the Icom backend).
This will be rendered possible through the following setup
between the rig_init() and rig_open() calls:

	token_t tok = rig_token_lookup(my_rig, "civaddr");
	rig_set_conf(my_rig, tok, "92");	/* 92 is decimal for 0x5c */

BTW, I noticed you're using a USB serial port. Since I've never tested
Hamlib with such a serial port, please let me know how it works.
Also, any feedback on the Icom backend and your IC-756PRO is welcome.
Commits to the CVS rep are pending, this rig will be supported in Hamlib-1.1.2.
This version has also a far better "rigctl" tool.

Cheers,

Stephane - F8CFE