[Xlog-discussion] Hamlib support in 1.4

[Nate Bargmann]

Hi Joop.

I'm trying to make XLog talk to my FT-920, but it seems to not "see"
the rig data.  I have the FT-920 working in gMFSK and through rigctl. 
I am using a USB to serial device, perhaps that is the problem.

In gMFSK success was found by adding stop_bits=2 to the config field. 
In XLog I tried stop_bits=2,serial_speed=4800, but still no luck.  I
manually entered /dev/ttyUSB0 in the device field.  When I do a trace I
get the following: 

rig:rig_init called 
ft920_init called
rig:rig_open called 
ft920_open called
ft920_open: write_delay = 50 msec
ft920_open: post_write_delay = 5 msec
ft920_get_vfo called
ft920_get_update_data called
ft920_get_update_data: read pacing = 1
TX 5 bytes
0000     00 00 00 01 0e .....
ft920_send_static_cmd called
TX 5 bytes
0000     00 00 00 01 fa .....
RX 8 bytes
0000     00 40 10 00 01 00 08 00        address@hidden
ft920_get_update_data: read 8 bytes
ft920_get_vfo: vfo status_0 = 0x00
ft920_get_vfo: vfo status_1 = 0x40
ft920_get_vfo: set vfo = 0x10000000

Which continues to repeat verbatim non-stop.  Meanwhile, in rigctl I get
the following: 

$ rigctl -r /dev/ttyUSB0 -m 114 -vvvvv
rigctl, Hamlib version 1.2.6
Report bugs to <address@hidden>

rig:rig_init called
rig: loading backend yaesu
yaesu: initrigs2_yaesu called
rig_register (121)
rig_register (110)
rig_register (105)
rig_register (106)
rig_register (107)
rig_register (120)
rig_register (101)
rig_register (122)
rig_register (123)
rig_register (115)
rig_register (113)
rig_register (114)
rig_register (116)
rig_register (103)
rig_register (124)
rig_register (104)
rig_register (125)
rig_register (117)
rig_register (119)
rig_register (118)
rig_register (126)
ft920_init called
rig:rig_open called
ft920_open called
ft920_open: write_delay = 50 msec
ft920_open: post_write_delay = 5 msec
ft920_get_vfo called
ft920_get_update_data called
ft920_get_update_data: read pacing = 1
TX 5 bytes
0000     00 00 00 01 0e .....
ft920_send_static_cmd called
TX 5 bytes
0000     00 00 00 01 fa .....
RX 8 bytes
0000     00 40 10 00 01 00 08 00        address@hidden
ft920_get_update_data: read 8 bytes
ft920_get_vfo: vfo status_0 = 0x00
ft920_get_vfo: vfo status_1 = 0x40
ft920_get_vfo: set vfo = 0x10000000
Opened rig model 114, 'FT-920'
Backend version: 0.3, Status: Alpha

Rig command: f
ft920_get_freq called
ft920_get_freq: passed vfo = 0x20000000
ft920_get_freq: priv->current_vfo = 0x10000000
ft920_get_update_data called
ft920_get_update_data: read pacing = 1
TX 5 bytes
0000     00 00 00 01 0e .....
ft920_send_static_cmd called
TX 5 bytes
0000     00 00 00 02 10 .....
RX 28 bytes
0000     09 00 3b d0 80 00 00 00 00 10 00 00 00 00 09 00        ..;.............
0010     3b d0 c6 00 00 00 00 10 00 00 00 00                    ;...........
ft920_get_update_data: read 28 bytes
ft920_get_freq: freq = 3920000.000000 Hz for vfo 0x10000000
Frequency: 3920000

Rig command: m
ft920_get_mode called
ft920_get_mode: passed vfo = 0x20000000
ft920_get_mode: priv->current_vfo = 0x10000000
ft920_get_update_data called
ft920_get_update_data: read pacing = 1
TX 5 bytes
0000     00 00 00 01 0e .....
ft920_send_static_cmd called
TX 5 bytes
0000     00 00 00 02 10 .....
RX 28 bytes
0000     09 00 3b d0 80 00 00 00 00 10 00 00 00 00 09 00        ..;.............
0010     3b d0 c6 00 00 00 00 10 00 00 00 00                    ;...........
ft920_get_update_data: read 28 bytes
ft920_get_mode: mymode = 0x00
ft920_get_mode: set mode = 8
ft920_get_mode: set width = 2400 Hz
Mode: LSB
Passband: 2400

Rig command: 


I am using both of the Debian Sid packages of Hamlib and XLog.

73, de Nate >>

P.S. Yes, as the Hamlib "maintainer", I should know all this.  ;-)

-- 
 Wireless | Amateur Radio Station N0NB          |  Successfully Microsoft
  Amateur radio exams; ham radio; Linux info @  | free since January 1998.
             http://www.qsl.net/n0nb/           |  "Debian, the choice of
             My Kawasaki KZ-650 SR @            |     a GNU generation!"
        http://www.networksplus.net/n0nb/       |   http://www.debian.org