RUMLog with fldigi PTT problem

[NA4M]

Not sure that this is the proper place for this question but have to start somewhere so here goes...

I'm trying to get fldigi working with RUMLog. I have RUMLog's Digi prefs set with the suggested loopback and port settings along with "Read TRX". fldigi will receive/decode RTTY signals and RUMLog and fldigi are displaying & following my K3's mode & freq correcly.

I start RUMrouter, then RUMLog, and then fldigi along with a microHam Digikeyer II interface

But for the life of me I can't get the RUMLog/fldigi/RUMRouter/Digikeyer II combination to key my K3's PTT in Data mode FSK D.

I've tried all kinds of combinations of PTT settings in flgdigi & RUMLog/RUMRouter including the fldigi Hardware PTT/uHrouter PTT options as well as the XML-RPC option. Nothing keys the K3's PTT.

Running RUMLog/RumRouter with CocoaModem Lite with the Digikeyer II keys the K3 PTT in Data mode FSK D just fine. Seems the RUMLog/RUMRouter with fldigi & Digikeyer II combination should as well.

Anyone have suggestions to get PTT working? Am I missing something or overlooking something somewhere?

[DL2RUM]

No, this will not work for fldigi!
Fldigi doesn't provide a way to command the PTT via the XML-RPC protocol. The only possibility to archive that, is to poll fldigi every 5ms and ask for the PTT status. This is not a very useful way. cocoaModem is more flexible at this point.

You could connect your TRX direct to fldigi. (never tried) When all is working, RUMlog can read the tx data from fldigi, but you will loose other CAT features.

A better way could be to use RUMlog for all CAT functions and fldigi does just the PTT keying, using a simple USB-Serial converter. The K3 has another connection just for PTT (in) keying.

[NA4M]

Tom - tnx for ur reply.

I finally managed to get fldigi to key my K3's PTT.

First starting uHRouter and enabling its configuration to "Fixed FSK Routing" in the Keyer Mode Panel and then starting fldigi. fldigi's Rig Control H/W PTT is set to "Use uHRouter PTT" enabled with the microHamRouter device & "Use RTS".

fldigi's right channel pseudo-FSK is also working with the DKII for FSK to my K3 by enabling "right audio FSK" in the RTTY Options panel of uHRouter's config.

The downside is that microHam's controller is not supported in OS X by fldigi (per W4TV). So - RigCAT in fldigi does read/follow the K3's VFO or mode.

As workaround in RUMLog I've disabled TRX #1 by setting "No TRX Connected" in RUMLog's TRX 1 prefs. This requires manual entry of the K3's operating frequency/mode/etc. when operating RTTY FSK with fldigi and logging in RUMLog. Disabling TRX #1 at least allows RUMRouter to start and support RUMLog at the same time as uHRouter is supporting fldigi's PTT and pseudo-FSK to DKII & K3.

So this is a configuration that allows fldigi to enable PTT and FSK for the K3 with a Digikeyer II as well as running RUMLog at same time for manual logging. Just no RigCAT support in either RUMLog or fldigi when using this config.


Or just use CocoaModem for CAT & FSK support with DKII/K3 and hope it continues to work with OS X 10.8 and later...

73 Phil NA4M

[DL2RUM]

You should get all running when you take the DKII out of the CAT control loop. Connect the K3 direct to the Mac, not via the DKII. You will need another USB port and a simple USB-Serial converter.

[NA4M]

Hmm -
I have one of the Elecraft KUSB USB-Serial cables used to update the K3's firmware.

I bet that might work for K3's CAT.

I'll unplug DKII's RS-S232 cable from K3 and plug in the KUSB cable and see what happens.

Tnx Tom!

[NA4M]

Using a separate USB-Serial cable (Elecraft KUSB in my case) in a 2nd USB port in addition to the Digikeyer II seems to have provided the function I was looking for with RUMLog and Fldigi.

Specifically right audio channel pseudo-FSK from Fldigi as well as PTT is now working via the DKII interface while K3 CAT is working in RUMLog using the USB-Serial cable with RUMlog sending K3's VFO data via the XML-RPC interface to Fldigi.

Changes to both RUMRouter and uHRouter settings were also needed to make everything work.

The only minor issue seems to be that RUMLog doesn't seem to want to read/follow the K3's mode via the USB-Serial interface.

[DL2RUM]

The only minor issue seems to be that RUMLog doesn't seem to want to read/follow the K3's mode via the USB-Serial interface.

When you have the K3 CAT connected to RUMlog, make sure you have disabled the "Read TX Data" in the RUMlog Preferences in the fldigi section.

[NA4M]

The only minor issue seems to be that RUMLog doesn't seem to want to read/follow the K3's mode via the USB-Serial interface.

Thanks Tom.

I double checked the CAT behavior I mentioned above.

What is happening is if I have VFO A=ModeA and VFO B=ModeB and use the VFO A/B to switch between VFOs RUMLog does not switch mode in the log window. Using the K3 Mode button will set the correct mode after switching VFOs. Appears RUMLog is not reading the mode when switching between VFO A & B and the modes are set different. This behavior is with or without Flgidi.

Not a big deal.

[DL2RUM]

Oh yes! Just checked, you are right. Here this happens only, when both VFOs are set to the same band. There is no info from the K3. Looks like a firmware bug.