View Revisions: Issue #2151

Summary 0002151: Rig Control: Icom protocol handler doesn't correctly parse frequency change announcements.
Revision 2018-04-04 14:47 by WA9PIE
Description There's code common to all of the Icom radios that parses data sent from the radio in the the CIV protocol. One part of the parsing code only looks at a couple of bytes of data rather than the whole structure, and incorrectly assumes certain strings of bytes from the radio are announcing a frequency change. They're not; they're announcing something else. The code in HRD Rig Control reads that data, misinterprets it, and uses it to show there resulting bogus value as a tuned frequency in rig control.

This probably affects all Icom radios that speak the modern CI-V protocol, but all I have to test at the moment is my ID-51A. The problem readily reproduces with that radio, but I don't want to attempt a fix until I have at least one other Icom to try out. The code in question is in the path of reading data from any Icom radio.
Revision 2017-07-21 21:20 by K7ZCZ
Description
There's code common to all of the Icom radios that parses data sent from the radio in the the CIV protocol. One part of the parsing code only looks at a couple of bytes of data rather than the whole structure, and incorrectly assumes certain strings of bytes from the radio are announcing a frequency change. They're not; they're announcing something else. The code in HRD Rig Control reads that data, misinterprets it, and uses it to show there resulting bogus value as a tuned frequency in rig control.

This probably affects all Icom radios that speak the modern CI-V protocol, but all I have to test at the moment is my ID-51A. The problem readily reproduces with that radio, but I don't want to attempt a fix until I have at least one other Icom to try out. The code in question is in the path of reading data from any Icom radio.