Re: [Hamlib-developer] rigctld issue: Unexpected response from get_rig_info
Library to control radio transceivers and receivers
Brought to you by:
n0nb
|
From: <gm...@bt...> - 2026-07-31 15:33:15
|
Actually I've seen something similar with "set_mode ?" and "set_vfo ?". philip@chinook:~/run$ echo "|\set_mode ?" | nc -w 1 localhost 4532 set_mode: ?|AM CW USB LSB RTTY FM WFM CWR RTTYR PKTLSB PKTUSB FM-D AM-D D-STAR RPRT 0 philip@chinook:~/run$ echo "|\set_vfo ?" | nc -w 1 localhost 4532 set_vfo: ?|VFOA VFOB MEM RPRT 0 73 Phil GM3ZZA. ________________________________ From: George Baltz <geo...@gm...> Sent: 29 July 2026 5:11 PM To: ham...@li... <ham...@li...> Subject: Re: [Hamlib-developer] rigctld issue: Unexpected response from get_rig_info Yep, that command is missing the separator(has an extra '\n' instead). The response is a single record with internal newlines. Patch generated, On 7/29/26 10:41 AM, Philip Rose via Hamlib-developer wrote: > I am currently assessing using rigctld on another project and I am > getting an unexpected response as follows: > > > philip@chinook:~/run$ echo "|\get_rig_info" | nc -w 1 localhost 4532 > get_rig_info:|VFO=VFOA Freq=145575000 Mode=USB Width=3000 RX=1 TX=1 > VFO=VFOB Freq=7070000 Mode=PKTUSB Width=2400 RX=0 TX=0 > Split=0 SatMode=0 > Rig=IC-705 > App=Hamlib > Version=20241103 1.1.0 > Model=3085 > CRC=0xb644552f > > RPRT 0 > > Rigctld was started with: > > philip@chinook:~/run$ rigctld -m 3085 -r /dev/ttyACM0 -s 19200 > > According to the man page: > > Separator character summary: > > ‘+’ Each record of the response is appended with a newline > (‘\n’). > > ‘;’, ‘|’, or, ‘,’ > Each record of the response is appended by the given > character > resulting in entire response on one line. > > These are common record separators for text > representations of > spreadsheet data, etc. > > So I would expect each line to have been separated with the '|' > character. I can sort of justify that there is a single record > "VFO........CRC=0xb644552f" (with internal CR/LF) but I would then at > least expect the separator before the RPRT 0 part of the response. > > 73 Phil > > GM3ZZA > > > > > > > _______________________________________________ > Hamlib-developer mailing list > Ham...@li... > https://lists.sourceforge.net/lists/listinfo/hamlib-developer _______________________________________________ Hamlib-developer mailing list Ham...@li... https://lists.sourceforge.net/lists/listinfo/hamlib-developer |