RUMlog and FLDIGI TRX data exchange via XML-RPC

[arcix]

I'm using RUMlog 5.0.4 and Fldigi 3.21.50 on OS X 10.8.1 and yes, I have a radio too, the Kenwood TS-590.
I've not been particularly successful at configuring RUMlog to send TRX data to Fldigi.

I have RUMlog nicely controlling the TS-590 via the USB connection. Now I am trying to configure the whole thing so that Fldigi receives TRX (frequency and mode) data from RUMlog.

In the RUMlog Preferences/Digi panel, I have the Fldigi panel set with Host: localhost, Port: 7362, Send TRX Data: checked, Read TRX Data: unchecked.
In the Flidigi Configure/Rig Control panels, I have disabled RigCAT (so that Fldigi doesn't connect to the TS-590 directly), and tried with Use XML-RPC Program both checked and unchecked.

When I manually change the VFO (A) frequency, the new frequency immediately appears in RUMlog, but NOT in Fldigi, while f I change mode (from USB to LSB, for example), the mode is correctly updated in Fldigi. So it looks like the RPC mechanism is partly working (mode works), that means it is not a problem with port configuration or the likes, but not fully, as the Fldigi frequency information never changes.

The other way around works just fine... I can configure Fldigi to control the radio via the USB port, disable the RUMlog's interface and enable Read TRX Data, but this way there is a considerable lag in RUMlog when I change the VFO frequency on the radio, so I'd really prefer sending TRX data from RUMlog to Fldigi.

Am I missing something?

73, de Ulde IK2TYL

[DL2RUM]

No, you made all correct. I have just realized, that somewhen in the past this function was broken for few transceivers. Please try out version 5.0.5: http://dl2rum.de/rumsoft/RUMlogApp.zip
I hope this fix your problem. I can't test it, since I don't have a Kenwood handy here.

Please report further!

[arcix]

Please try out version 5.0.5
I hope this fix your problem.

yes, it works just fine now. Changing the frequency on Fldigi is also correctly tracked by RUMlog and consequently executed on the radio (if Read TRX is also enabled). Thanks a lot, Tom.

Let me take a moment to review my settings for an effective integration between RUMlog and Fldigi, if this can be of any help to others.

On the RUMlog side, I keep the Fldigi panel set with Host: localhost, Port: 7362, Send TRX Data: checked, Read TRX Data: checked.
On the Fldigi side, in the Configure/Rig Control panels, I have RigCAT configured for direct control of the TS-590, setting /dev/tty.SLAB_USBtoUART in the device selector.

With this configuration, I can quickly swap between a setup where RUMlog controls the radio, and Fldigi tracks the VFO A frequency, or the other way around, where Fldigi controls the radio, and RUMlog sees the frequency and mode settings via Fldigi:

### RUMlog controls the radio, and Fldigi tracks ###
In Fldigi, enable XML-RPC (this automatically disables RigCAT), then start RUMlog (or, if RUMlog is already running, click the Transceiver/Reinit TRX#1 menu).
This way you have faster radio control on the RUMlog side, while retaining the frequency information in Fldigi.

### Fldigi controls the radio, and RUMlog tracks ###
In Fldigi, enable RigCAT (this automatically disables XML-RPC), then start RUMlog (or, if RUMlog is already running, FIRST click the Transceiver/Disconnect TRX#1 menu, otherwise Fldigi will not connect to the radio).
This way you have better radio control from Fldigi (including the ability to QSY to center the signal you have selected in the waterfall, and to set the radio's passband), and still have the current mode and frequency on RUMlog.

73, IK2TYL