Re: [Hamlib-developer] IC-736 backend status and converter power

[Andrea B. <bo...@st...>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Stephane Fillod wrote:


| 	rigctl -vvvvvv -Crts_state=ON -m 320
| There's also a config 'dtr_state' param. You can check them all with
| the -L option. Let me know if this solves your powering problem.

Funny thing is, minicom does read some garbage when turning the VFO
knob, so apparently it is not a hw problem, but rigctl doesn't work,
this is what I get:


- -cut-cut-
[andrea@deunan]/local/hamlib-1.1.4cvs-030227/tests$ ./rigctl -vvvvvv -r
/dev/rig -Crts_state=ON -m 320 -L -s 9600
rigctl, Hamlib version 1.1.4cvs-030227
Report bugs to <ham...@li...>

rig:rig_init called
rig: loading backend icom
icom: _init called
rig_register (309)
rig_register (310)
rig_register (311)
rig_register (313)
rig_register (314)
rig_register (319)
rig_register (320)
rig_register (321)
rig_register (330)
rig_register (326)
rig_register (327)
rig_register (347)
rig_register (334)
rig_register (344)
rig_register (335)
rig_register (340)
rig_register (342)
rig_register (304)
rig_register (307)
rig_register (352)
rig_register (353)
rig_register (351)
civaddr: "Transceiver's CI-V address"
~        Default: 0, Value: 64
~        Range: 0.0..255.0, step 1.0
mode731: "CI-V operating frequency data length, needed for IC731 and IC735"
~        Default: 0, Value: 0
rig_pathname: "Path name to the device file of the rig"
~        Default: /dev/rig, Value: /dev/rig
write_delay: "Delay in ms between each byte sent out"
~        Default: 0, Value: 0
~        Range: 0.0..1000.0, step 1.0
post_write_delay: "Delay in ms between each command sent out"
~        Default: 0, Value: 0
~        Range: 0.0..1000.0, step 1.0
timeout: "Timeout in ms"
~        Default: 0, Value: 200
~        Range: 0.0..10000.0, step 1.0
retry: "Max number of retry"
~        Default: 0, Value: 3
~        Range: 0.0..10.0, step 1.0
itu_region: "ITU region this rig has been manufactured for (freq. band
plan)"
~        Default: 0, Value: 2
~        Range: 1.0..3.0, step 1.0
serial_speed: "Serial port baud rate"
~        Default: 0, Value: 9600
~        Range: 300.0..115200.0, step 1.0
data_bits: "Serial port data bits"
~        Default: 8, Value: 8
~        Range: 5.0..8.0, step 1.0
stop_bits: "Serial port stop bits"
~        Default: 1, Value: 1
~        Range: 0.0..3.0, step 1.0
serial_parity: "Serial port parity"
~        Default: None, Value: None
~        Combo: None, Odd, Even
serial_handshake: "Serial port handshake"
~        Default: None, Value: None
~        Combo: None, XONXOFF, Hardware
vfo_comp: "VFO compensation in ppm"
~        Default: 0, Value: 0.000000
~        Range: 0.0..1000.0, step 0.0
rts_state: "Serial port set state of RTS signal for external powering"
~        Default: Unset, Value: ON
~        Combo: Unset, ON, OFF
dtr_state: "Serial port set state of DTR signal for external powering"
~        Default: Unset, Value: Unset
~        Combo: Unset, ON, OFF
rig:rig_open called
Opened rig model 320, 'IC-736'
Backend version: 0.2, Status: New

Rig command: f
TX 6 bytes
0000     fe fe 40 e0 03 fd      ..@...
read_string: timedout without reading a character
get_freq: error = Communication bus error
- -cut-cut-


Where should I look to get a clue of what's going on? I gather you do
not have a 736 so I'll do the tests.

Andrea.

- --
Undergraduate student of Computer Science @ University of Bologna
Key fingerprint: 4037 9711 85C6 F9F9 A505  FA0A BB62 3A3C F7BA 9B13
ICQ: 4905369 / JID: bo...@ja... / HAM: IZ4FHT
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Debian - http://enigmail.mozdev.org

iD8DBQE+Yn1jKhgqEyuO+p4RArI7AJ9SVaIgxNFfOaEJ0Mz8uyYLNxmfiACgjpM+
kGvIx4ixPRPZAPerouWkYQw=
=iPvl
-----END PGP SIGNATURE-----