[Hamlib-developer] Strange problem with response from IC-7300

[Stephen P. <st...@bi...>]

Hi,

I have a python program that starts rigctld in the background and then 
interrogates my IC-7300 by using the TCP access to rigctld. This works 
100% reliably and retrieves the frequency, tx state and mode of the 
radio every second.

Whilst experimenting with the "wfview" program which connects to the 
IC-7300 and allows the radio to be controlled by a PC, I have come 
across an odd problem. If I run the run the wfview program (which works 
just fine) and then exit the program and then execute by Python program 
as described above, my program intermittently malfunctions. Note I'm not 
trying to do these things at the same time. They both require access to 
the IC-7300 USB port.

To be specific, the response to the "get_freq" command using the 
extended protocol is for example as follows (in a python byte array)

     b'get_freq:|Frequency: 14243000|RPRT 0\n'

However, if I had previously run (and terminated) the wfview program, 
the response to the "get_freq" command is occasionally as follows

     b'get_freq:|RPRT -11\n'

Ie the actual frequency message is missing and back end code -11 is 
returned.

The analogous thing happens for "get_ptt" and "get_mode" commands every 
once in a while, although the error code is different.

If I cycle the power on the radio, the problem goes away, so clearly the 
wfview has changed something in the radio, but I have been unable so far 
to see any config that  it has changed that might have a bearing on this 
issue. I'm hoping that either the "-11" error code might convey a clue 
to the problem, or that someone might have come across this as well.

I get the same malfunction if I use the "simple" protocol instead.

I don't believe this is a hamlib error, but I'm hoping that someone here 
might have a suggestion for me to try.

Thanks de VK3SPX (Steve)