Hi Saku
OK I think we are making progress.
I have two radios configured
Radio One is a TS 570 and Radio Two is a G90
Everything I have done has been with Radio Two selected but in the dump parameters from Radio One are being used.
Below is what I have done - the important bit is near the end.
checked CQRLog it is set to /dev/bin/rigctld OK
Re-boot for a clean start
I open a command window and enter
rigctld -m 3088 -r /dev/ttyUSB0 -t 4532 -s 19200 -vvvvv
a lot of messages scroll past then I get
rig model 3088 G90
Backend version 20250517.11
main using IPV4
main: listening on port 4532
so far that seems fine.
I leave this command window open
I then open a 2nd command window and enter
telnet 127.0.0.1 4532
it tries to connect trying 127.0.0.1 ......
then I get telnet: Unable to connect to remote host connection refused.
I try whereis telnet
/usr/bin/telnet
which telnet
/usr/bin/telnet
telnet gives
telnet>
so seems to be running
but telnet -v just gives "invalid command"
So there is an issue with telnet on my RPi.
I then go onto my other Ubuntu linux computer and open a command window
$ telnet 192.168.1.80 (the fixed ip of the RPi)
and it connects fine.
f on the Ubuntu machine returns the correct frequency from the G90 via the RPi
I now open a 3rd command window on RPi and enter CQRLog
CQRLog runs up fine but this is what I get in the command window.
Look closely at the rig ID its not 3088 but 2004 which is a Kenwood TS570 or TS 590
Also the baud is 9600 even though its configured as 19200
In CQRLog I have two rigs configured
Radio 1 is a TS 570 and that is working fine.
Radio 2 is a G90.
Its as if CQRLog is using the parameters for Radio One even though Radio Two is selected?
I have tried Window -> TRX control it defaults to Radio One so I select Radio Two.
Then I File -> Refresh TXR Control
But the command window still displays Radio One parameters even though Radio Two is selected.
I am running CQRLog 2.5.1.
Should I upgrade to a later version?
See below
73
Dave GM4NFI
Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld
Parameters:
-m
2004
-r
/dev/ttyUSB0
-tStarting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld
Parameters:
-m
2004
-r
/dev/ttyUSB0
-t
4532
-s
9600
--set-conf=data_bits=7,stop_bits=1,serial_parity=None,serial_handshake=Hardware,dtr_state=Unset,rts_state=Unset
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
rig_open: error = rig_confparam_lookup called for rts_state
rig_set_conf called
rig.c(1005):rig_open entered
rig_settings_get_path: path=/home/djcleckie/.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=57600,0x1001
serial_setup: cfsetospeed=57600,0x1001
serial_setup: data_bits=7
serial_setup: stopbits=1
serial_setup: parity=0
serial_setup: Handshake=Hardware
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptordjcleckie@raspberrypi:~ $ telnet 127.0.0.1 4532
Trying 127.0.0.1...
telnet: Unable to connect to remote host: Connection refused
djcleckie@raspberrypi:~ $ whoami
djcleckie
djcleckie@raspberrypi:~ $ groups djcleckie
djcleckie : djcleckie adm tty dialout cdrom sudo audio video plugdev games users input render netdev spi i2c gpio lpadmin
Hi Saku
OK
checked CQRLog it is /dev/bin/rigctld
Re-boot for a clean start
I open a command window and enter
rigctld -m 3088 -r /dev/ttyUSB0 -t 4532 -s 19200 -vvvvv
a lot of messages scroll past then I get
rig model 3088 G90
Backend version 20250517.11
main using IPV4
main: listening on port 4532
so far that seems fine.
I leave this command window open
I then open a 2nd command window and enter
telnet 127.0.0.1 4532
it tries to connect trying 127.0.0.1 ......
then I get telnet: Unable to connect to remote host connection refused.
I try whereis telnet
/usr/bin/telnet
which telnet
/usr/bin/telnet
telnet gives
telnet>
so seems to be running
but telnet -v just gives "invalid command"
So there is an issue with telnet on my RPi.
I then go onto my other Ubuntu linux computer and open a command window
$ telnet 192.168.1.80 (the fixed ip of the RPi)
and it connects fine.
f on the Ubuntu machine returns the correct frequency from the G90
I now open a 3rd command window on RPi and enter CQRLog
CQRLog runs up fine but this is what I get in the command window.
Look closely at the rig ID its not 3088 but 2004 which is a Kenwood TS570 or TS 590
Also the baud is 9600 even though its configured as 19200
In CQRLog I have two rigs configured
Radio 1 is a TS 570 and that is working fine.
Radio 2 is a G90.
Its as if CQRLog is using the parameters for Radio One even though Radio Two is selected?
I have tried Window -> TRX control it defaults to Radio One so I select Radio Two.
Then I File -> Refresh TXR Control
But the command window still displays Radio One parameters even though Radio Two is selected.
I am running CQRLog 2.5.1.
Should I upgrade to a later version?
See below
73
Dave GM4NFI
Starting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld
Parameters:
-m
2004
-r
/dev/ttyUSB0
-tStarting RigCtld ...
rigProcess.Executable: /usr/bin/rigctld
Parameters:
-m
2004
-r
/dev/ttyUSB0
-t
4532
-s
9600
--set-conf=data_bits=7,stop_bits=1,serial_parity=None,serial_handshake=Hardware,dtr_state=Unset,rts_state=Unset
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
rig_open: error = rig_confparam_lookup called for rts_state
rig_set_conf called
rig.c(1005):rig_open entered
rig_settings_get_path: path=/home/djcleckie/.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=57600,0x1001
serial_setup: cfsetospeed=57600,0x1001
serial_setup: data_bits=7
serial_setup: stopbits=1
serial_setup: parity=0
serial_setup: Handshake=Hardware
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig.c(1239):rig_open returning2(-2) Invalid configuration
Invalid configuration
rigctld failed to start!
1
2
3
4
5
6
4532
-s
9600
--set-conf=data_bits=7,stop_bits=1,serial_parity=None,serial_handshake=Hardware,dtr_state=Unset,rts_state=Unset
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
rig_open: error = rig_confparam_lookup called for rts_state
rig_set_conf called
rig.c(1005):rig_open entered
rig_settings_get_path: path=/home/djcleckie/.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=57600,0x1001
serial_setup: cfsetospeed=57600,0x1001
serial_setup: data_bits=7
serial_setup: stopbits=1
serial_setup: parity=0
serial_setup: Handshake=Hardware
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig.c(1239):rig_open returning2(-2) Invalid configuration
Invalid configuration
rigctld failed to start!
1
2
3
4
5
6
rig.c(1239):rig_open returning2(-2) Invalid configuration
Invalid configuration
rigctld failed to start!
1
2
3
4
5
6
4532
-s
9600
--set-conf=data_bits=7,stop_bits=1,serial_parity=None,serial_handshake=Hardware,dtr_state=Unset,rts_state=Unset
Recommend using --vfo switch for rigctld if client supports it
rigctl and netrigctl will automatically detect vfo mode
rig_open: error = rig_confparam_lookup called for rts_state
rig_set_conf called
rig.c(1005):rig_open entered
rig_settings_get_path: path=/home/djcleckie/.config/hamlib_settings
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=57600,0x1001
serial_setup: cfsetospeed=57600,0x1001
serial_setup: data_bits=7
serial_setup: stopbits=1
serial_setup: parity=0
serial_setup: Handshake=Hardware
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig.c(1239):rig_open returning2(-2) Invalid configuration
Invalid configuration
rigctld failed to start!
1
2
3
4
5
6
HI Dave !
I think you did not read my last message up to the end.
Console #1, you got rigctld running with lots of debug texts -OK
Console #2, you got telnet running with local lan IP -OK
If rig is connected to Rpi and console #1 is opened in Rpi then I think you opened the Console #2 in somewhere else than in Rpi because you needed lan IP to get connected.
Am I right ? You did open Console #2 in computer you are using for accessing Rpi, eh?
Otherwise, if console#2 is opened also in Rpi it should response to localhost (127.0.0.1).
Well, now if I am right the question is: Is Cqrlog running in same RPi where rig is connected?
Referring your previous message's picture the graphics look like Rpi's view.
Then the major setup issue:
If you managed to start rigctld in Console#1 and managed to telnet to it in Console#2 using Lan address then
you should change G90 settings in Cqrlog/preferences/TRXControl following way:
rig model: "2 Net Hamlib Net rigctl"
host 192.168.1.80
(if Console#1 running rigctld is at same Rpi than Cqrlog then 127.0.0.1 should also work, but if you say it does not work with telnet then use Lan IP instead in "host")
port 4532
Run rigctld at program start UNCHECKED
Show communication with TRX in console CHECKED
Start Console#1 (rigctld) as before with same parameters
Start Console #2 (telnet) as before and test with telnet that you get frequency
Start Console #3 (Cqrlog) after you have done those setup changes.
Forget "G90" settings in preferences/TRXControl. You are not configuring that rig to Cqrlog. You are configuring rig model "2 Net Hamlib Net rigctl" and that means you are configuring Cqrlog to connect to rigctld in Console#1. Rigctld running there knows all about G90, Cqrlog does not need those settings at all. Just how to get connected to Console#1
If we get this working then we can think to make easier setups without three consoles.
I have hard to imagine your systems and how you want to use them, and how deep is your knowledge about Linux is. That is why I try to go forward with this way. Step by step. First clearing up that Cqrlog can communicate with rigctld same way as the telnet console does.
From your debug texts I could now see that Cqrlog config was not set properly for this three console test.
You said you have two rigs configured with Cqrlog. We can do that but I think we need to separate ports for those two.
Then next I need to know are you running any other programs with Cqrlog in same Rpi like wsjt-x, fldigi or similar.
But first we need to pass this 3 Console test. We talk about these later.
--
Saku
OH1KH