Hello CQRLOG,
I'am digging deeper into the setup of CQRLOG.
Today was time to setup two rigs with hamlib and working CW interface.
I was not aware of the fact, that only the first rig can use the CW interface!
Menu CW interface -> Interface type: HamLib -> see description there
For my understanding I can use TRX control to switch the rigs.
Only the activated rig (first or second) is the rig which can use the CW interface!
I would be great to have this fixed.
73 de Martin, DL1MTG
Hi Martin!
Ok I got your point.
You would like to see HamLib CW working from currently selected rig, not from first rig settings.
I use 2 rigs and run 2 instances of rigctld port 4532 for IC7300 and 14532 for IC706.
As ic706 does have winkeyer connected I have never noticed that hamlib CW keyer does not follow rig.
In some cases (split frequency operations with 2 rigs, like satellite qsos) you might want to have keyer from 1st rig while actually use the 2nd one for RX and logging.
Perhaps a checkbox for hamlib keyer settings "follow selected rig" would be best solution.
Then you could keep it like it has always been, but can also change it to follow current rig.
I'll look the code and do some testing some day.
--
Saku
OH1KH
Hello Saku,
thanks for your quick reply.
That is exactly what is "needed", I guess. Only the selected rig should be able to send CW using Hamlib.
Later the day I started some debugging.
Rig one is enabled. CW using Hamlib is working.
Then I switch over to second rig (using TRX control) - no CW using Hamlib is possible. So let's go on.
I switched back to rig one. CW is not possible.
I did a "Reload CW interface". Taaadaa! Rig one is able to send CW using Hamlib!
So back to rig two.
Switching to rig two seems to left Hamlib and CW in a unconfigured state.
Here you can see the debug output:
Msg from rig: RPRT -11
Sending:?
HLsend MSG:b?:
CWint connect to hamlib FAILED: No connected socket to send through
Ack timeout left: 0(/20)
Repeats left: 499(/500)
Sending: fmv
RPRT -11 - failure from the ICOM-Rig - nothing special
Sending "?" to the rig two - using CW Hamlib
CWint connect to hamlib FAILED: No connected socket to send through
There seems to be no active connection to the CW interface using Hamlib.
VFO, QRG etc. is working.
Hopefully you can get the "small issue" - I'am not a programmer :-)
73 de Martin, DL1MTG
--
73 de Martin, DL1MTG
Hi Martin!
I have sent PM to your Email , please check!
--
Saku
OH1KH
Hi Martin !
Yes, that happens.
When you come back to 1st rig you must manually restart CW interface from NewQSO/File/Reload CW interface
That should be fixed too so that if cw interface is Hamlib, then it must be reloaded at same time when rigctld for rig is restarted.
--
Saku
OH1KH