ICOM ID-5100 - rigctl Get Frequency command failing

[leeott25]

When rigctld is started or when entering the "f" command in rigctl, rigctld sends fe fe 8c 03 fd to the ID-5100 which seems to be correct. The ID-5100 replies with fe fe e0 8c 03 98 45 01 fd. The actual frequency of the Main vfo is 145.980. You can see how the reply from the ID-5100 matches the actual frequency. However, the format of the reply does not match the description of the 03 command described in the ID-5100 full manual. See page 13-9. Rigctld detects the wrong frame length. The following shows a section of the log from rigctld.

write_block(): TX 6 bytes, method=2
0000 fe fe 8c e0 03 fd ......
read_string_generic called, rxmax=200 direct=1, expected_len=1
read_string_generic(): RX 6 characters, direct=1
0000 fe fe 8c e0 03 fd ......
icom_one_transaction: DEBUG retval=6, frm_len=6, cmd=0x03
read_string_generic called, rxmax=200 direct=1, expected_len=1
read_string_generic(): RX 9 characters, direct=1
0000 fe fe e0 8c 03 98 45 01 fd ......E..
icom_one_transaction: frm_len=9, frm_len-1=fd, frm_len-2=01
-23:frame.c(403):icom_one_transaction returning(0)
-24:frame.c(455):icom_transaction returning(0)
icom.c(1653) trace
set_vfo_curr: vfo=Main, curr_vfo=Main
set_vfo_curr: curr_vfo now=Main
icom.c(9402):set_vfo_curr returning2(0)
icom_get_freq: wrong frame len=3
-25:icom.c(1698):icom_get_freq returning(-9) Command rejected by the rig

rig_get_freq(2098): freqMainA=0, modeMainA=, widthMainA=0
rig_get_freq(2098): freqMainB=0, modeMainB=, widthMainB=0
rig_set_cache_freq(117): freqMainA=0, modeMainA=, widthMainA=0
rig_set_cache_freq(117): freqMainB=0, modeMainB=, widthMainB=0
rig_set_cache_freq(122): vfo=Main, current_vfo=Main
rig_set_cache_freq(142): set vfo=Main to freq=0
rig_set_cache_freq(215): freqMainA=0, modeMainA=, widthMainA=0
rig_set_cache_freq(215): freqMainB=0, modeMainB=, widthMainB=0
-26:rig_get_freq: elapsed=63ms
-26:rigctl_parse.c(2101):rigctl_get_freq returning(-9) Command rejected by the rig

rigctl_parse: return#1 RPRT -9
mutex_rigctld: client lock disengaged
handle_socket: rigctl_parse retcode=-9
mutex_rigctld: client lock engaged
mutex_rigctld: client lock disengaged
handle_socket: doing rigctl_parse vfo_mode=0, secure=0
rigctl_parse: called, interactive=1