More than 2 rigs in TRX control

9 posts / 0 new
Last post
NZ0T
More than 2 rigs in TRX control

I would love to have the ability to set up more than two rigs in TRX control. I currently have 3 HF rigs capable of CAT but can only have 2 set up at a time. That means I have to change the settings to a different rig if I want to us the 3rd rig with TRX control. I'm sure many others have more than 2 rigs they would like to have permanently available in TRX control!

73, Bill NZ0T

oh1kh
More than 2 rigs in TRX control

HI Bill!

That would need completely new design of TRXcontrol. Maybe a database for rig (and keyer) settings that would then be called from rig selection combo box.
Not impossible, but needs lot of work.

As a workaround I have suggestion:
Set cqrlog radio settings to use model #2 NetHamlib Rigctld. Uncheck "Run rigctld at program start". You can also clear all other settings except port, poll rate and host.

Then do three command line script files to use with your 3 rigs.
-----
#!/bin/bash
killall rigctld
killall rigctld # this line is not needed but will make sure that all previeus rigctlds are killed if there is another lying down somewhere
/usr/bin/rigctld -m 3073 -r /dev/icom7300 -t 4532 -s 19200 -C auto_power_on=0 &
-----

Use parameters your rigs need and do not forget " &" (space&) from the end. That makes rigctld run on background.
You can make desktop icons for all these for easy access.

When cqrlog is running execute one of scrips. After that switch TRXControl radio1/radio2/radio1 or use NewQSO/File/Refresh TRX/ROT control to make cqrlog reconnect to running rigctld. You should now see that TRXControl works with scripted rig.

When you want to switch rigs again, to the same but with different script.

That works but you can have keyer definitions only for two radios (TRXControl radio1 and radio2) and also user defined buttons (latest cqrlog versions) can support only 2 sets of definitions. But they work with 10^n rigs if same commands are ok for all those rigs. (you can even define 3 script starts to these 3 buttons!)

If you use wsjtx, jtdx, js8call, qsstv, fldigi with cqrlog use rig model #2 also with them to get them work with same rig as cqrlog. At least wsjtx/js8call will complain when you switch rigs but will reconnect with retry button. I have no experience what happens with fldigi,qsstv and jtdx but restarting the rig connection somehow connects them to switched rig again.

Maybe not user friendly, but working workaround. And the amount of rigs (scripts) is unlimited.

--
Saku
OH1KH

VK2XAX
More than 2 rigs in TRX control

I'll add my +1 to the 3 or more rig requirement plus with the ability to nominate the 3rd rig as a transverter with IF offset so the program knows that if the freq is set to 432.1 the QRG is actually 3398.1 :)

VK2XAX : QF56if : ITU59 : CQ30 : BMARC : WIA

oh1kh
More than 2 rigs in TRX control

Fine !

With latest cqrlog you have three user defined buttons at TRXControl. You can define those to run your rig scripts.
Actually even one button would be enough if you make your script circulating rig1-rig3-rig3-etc-and_back to rig1.

I have defined one key to switch keyer/straight key and it also restores full RF power as I have another usr button defined to set 60m band with legal power limit 15W so keyer/key switching restores full power back when returning from 60m. It also uses program notify-send to inform what key is assigned (could inform what rig is assigned in case of circulating rig switch). It goes like this:
--------------------------------

TRXControl:
Usr1 S/K run /home/saku/.config/cqrlog/voice_keyer/swkeying.sh

--------------------------------

script:
#!/bin/bash
#
#Switch between straight key and keyer IC7300
#linux netcat (nc) progam must be installed for communication to rigctld via TCP/IP
#echo -n -e [rigctld command] | nc localhost 4532
#
#Script does not use return value
#Command sent via netcat and rigctld
#
#
if [ -e /home/saku/.config/cqrlog/voice_keyer/straight.key ]
then
#Paddle
echo -n -e 'w \\0xFE\\0xFE\\0x94\\0xE0\\0x1A\\0x05\\0x01\\0x64\\0x02\\0xFD' | nc -w 1 localhost 4532
rm /home/saku/.config/cqrlog/voice_keyer/straight.key
notify-send 'CW keying via paddles'
else
#Straight key
echo -n -e 'w \\0xFE\\0xFE\\0x94\\0xE0\\0x1A\\0x05\\0x01\\0x64\\0x00\\0xFD' | nc -w 1 localhost 4532
touch /home/saku/.config/cqrlog/voice_keyer/straight.key
notify-send 'CW keying via straight key'
fi
sleep 1
#full power
echo -n -e 'w \\0xFE\\0xFE\\0xFE\\0x94\\0xE0\\0x14\\0x0A\\0x02\\0x55\\0xFD' | nc localhost 4532

---------------------------

--
Saku
OH1KH

PA1SBM
PA1SBM's picture
More than 2 rigs in TRX control

I have to give this a +1 as well....
pull down menu would be awesome to switch, i personally would not want an up/down to cycle through all the rigs...

If this is build, it would be nice if it was like a list where you can add and add... i have 6 rs232 poorts and a load of usb, and at least 3 rigs i cann hook up , and a spare cable to test would be a nice addition :)

please consider this one :)

73
Alex
PA1SBM

db5fp
+1 here too.

+1 here too.
What about raising some fund for this project?
73
Frank

oh1kh
More than 2 rigs in TRX control

Hi this thread!

I have been writing new TRXcontrol that supports more than two rigs.
Starting point is now 6 rigs, but it can be extended quite easy if someone really needs more rigs (!?!)

Writing is still in early phase and many things do not work properly and almost all are not tested in the way they should be.

Main things that needed to change are TRXControl, Modes and CW keying. Both in preferences (setup) side and operating side.

This project also fixes some bugs (and creates some new ;-).

The RTTY mode is replaced with DATA that mainly is just naming, but allows user to separate the data mode in log and the command needed to set rig to mode that can be used for working.
For example logging as FT8 can send PKTUSB to rig when data mode is selected. This has also effect to DXspot double clicking. When spot frequency is in data area double click can set right mode to rig and also sport coloring is done by working status of defined log mode.

Anybody interested to see the progress can follow https://github.com/ok2cqr/cqrlog/compare/master...OH1KH:cqrlog:fix4rigs

--
Saku
OH1KH

db5fp
Hi,

Hi,

any chance to test the new code?

73
Frank

oh1kh
More than 2 rigs in TRX control

HI Frank!
Yep!
It is now included in my alpha testing version.
You find source code from https://github.com/OH1KH/cqrlog/tree/loc_testing
If you can not compile by yourself there are ready compiled binary files at https://github.com/OH1KH/cqrlog/tree/loc_testing/compiled

Just download newupdate.zip from there, extract and start newupdate.sh. That will do backups and update.
Comments are welcome. You find my email from Hamqth or Qrz.

--
Saku
OH1KH