Discussion:
FLRig and FLDigi - PTT locking in TX
Jim Rogers
2012-03-09 15:44:40 UTC
Permalink
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only FLRig should be controlling the radio.

I am having difficulty with the PTT locking in transmit. The only way I can clear it is to kill FLRig. After killing FLRig, if I restart it, FLRig will come up with PTT locked. To get everything back to normal I had to kill (required a "Forced Quit") FLDigi also and reboot.

I tried killing FLRig and then reconfiguring FLDigi for seperate port PTT and CAT and I could not successfully reconfigure without shutting down FLDigi and a restart. It appears to be some interaction between FLRig and FLDigi....

If I run FLDigi properly configured and do not use FLRig, everything stays together and works. I really like having FLRig in the mix for the additional rig controls.


Any help greatly appreciated.

Jim
w4atk-***@public.gmane.org
w1hkj
2012-03-09 15:58:38 UTC
Permalink
Post by Jim Rogers
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only FLRig should be controlling the radio.
I am having difficulty with the PTT locking in transmit. The only way I can clear it is to kill FLRig. After killing FLRig, if I restart it, FLRig will come up with PTT locked. To get everything back to normal I had to kill (required a "Forced Quit") FLDigi also and reboot.
I tried killing FLRig and then reconfiguring FLDigi for seperate port PTT and CAT and I could not successfully reconfigure without shutting down FLDigi and a restart. It appears to be some interaction between FLRig and FLDigi....
If I run FLDigi properly configured and do not use FLRig, everything stays together and works. I really like having FLRig in the mix for the additional rig controls.
Any help greatly appreciated.
Jim
Does flrig work with the K3 if it is not being used with fldigi?

If using flrig and fldigi together, fldigi must be configured for xmlrpc
rig control. It sounds like a contention between multiple programs
trying to access the serial port.

Dave


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

Yahoo! Groups Links

<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/linuxham/

<*> Your email settings:
Individual Email | Traditional

<*> To change settings online go to:
http://groups.yahoo.com/group/linuxham/join
(Yahoo! ID required)

<*> To change settings via email:
linuxham-digest-***@public.gmane.org
linuxham-fullfeatured-***@public.gmane.org

<*> To unsubscribe from this group, send an email to:
linuxham-unsubscribe-***@public.gmane.org

<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
Jim Rogers
2012-03-09 16:26:14 UTC
Permalink
Seems to Dave. Let me configure the xmlrpc thingy and see what happens. I am kinda new to FLDIGI and really like it.

73s Jim
W4ATK
Post by w1hkj
Post by Jim Rogers
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only FLRig should be controlling the radio.
I am having difficulty with the PTT locking in transmit. The only way I can clear it is to kill FLRig. After killing FLRig, if I restart it, FLRig will come up with PTT locked. To get everything back to normal I had to kill (required a "Forced Quit") FLDigi also and reboot.
I tried killing FLRig and then reconfiguring FLDigi for seperate port PTT and CAT and I could not successfully reconfigure without shutting down FLDigi and a restart. It appears to be some interaction between FLRig and FLDigi....
If I run FLDigi properly configured and do not use FLRig, everything stays together and works. I really like having FLRig in the mix for the additional rig controls.
Any help greatly appreciated.
Jim
Does flrig work with the K3 if it is not being used with fldigi?
If using flrig and fldigi together, fldigi must be configured for xmlrpc
rig control. It sounds like a contention between multiple programs
trying to access the serial port.
Dave
Jim Rogers
2012-03-09 16:29:02 UTC
Permalink
Dave,

XMLRPC was checked, I have the seperate port PTT unchecked, CAT is unchecked and HamLib is unchecked.

Jim

W4ATK
Post by w1hkj
Post by Jim Rogers
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only FLRig should be controlling the radio.
I am having difficulty with the PTT locking in transmit. The only way I can clear it is to kill FLRig. After killing FLRig, if I restart it, FLRig will come up with PTT locked. To get everything back to normal I had to kill (required a "Forced Quit") FLDigi also and reboot.
I tried killing FLRig and then reconfiguring FLDigi for seperate port PTT and CAT and I could not successfully reconfigure without shutting down FLDigi and a restart. It appears to be some interaction between FLRig and FLDigi....
If I run FLDigi properly configured and do not use FLRig, everything stays together and works. I really like having FLRig in the mix for the additional rig controls.
Any help greatly appreciated.
Jim
Does flrig work with the K3 if it is not being used with fldigi?
If using flrig and fldigi together, fldigi must be configured for xmlrpc
rig control. It sounds like a contention between multiple programs
trying to access the serial port.
Dave
Dave - G8FXM
2012-03-09 16:52:12 UTC
Permalink
I'm getting this also when set up with N1MM via XMLRPC.
I don't get this when running FLDIGI standalone as I don't use XMLRPC in
that scenario.

Dave, G8FXM
Post by Jim Rogers
XMLRPC
--
73's de Dai G8FXM (M3FXM)
Jim Rogers
2012-03-09 20:48:32 UTC
Permalink
OK Dave,

Thank you. That is a help. I don't get it when I run FLDIGI stand alone either. I was considering it might be in my remote hookup, but with your observation I do not believe it is.

Jim
W4ATK
Post by Dave - G8FXM
I'm getting this also when set up with N1MM via XMLRPC.
I don't get this when running FLDIGI standalone as I don't use XMLRPC in that scenario.
Dave, G8FXM
XMLRPC
--
73's de Dai G8FXM (M3FXM)
Ken
2012-03-09 17:50:12 UTC
Permalink
Jim,

Do you have a Signalink USB with the "to PTT" cable plugged into the K3 PTT socket? If so, unplug it and your problems will go away. You don't need it and sometimes that will lock the rig on TX even though it's not actually transmitting.

If you don't have the Signalink but still have something plugged into the PTT socket, try unplugging it.

Ken WA8JXM
Post by Jim Rogers
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only FLRig should be controlling the radio.
I am having difficulty with the PTT locking in transmit. The only way I can clear it is to kill FLRig. After killing FLRig, if I restart it, FLRig will come up with PTT locked. To get everything back to normal I had to kill (required a "Forced Quit") FLDigi also and reboot.
I tried killing FLRig and then reconfiguring FLDigi for seperate port PTT and CAT and I could not successfully reconfigure without shutting down FLDigi and a restart. It appears to be some interaction between FLRig and FLDigi....
If I run FLDigi properly configured and do not use FLRig, everything stays together and works. I really like having FLRig in the mix for the additional rig controls.
Any help greatly appreciated.
Jim
Jim Rogers
2012-03-09 20:46:17 UTC
Permalink
No Ken, I have a Navigator interface and do use the hardware PTT signal from the interface to the K3 "ACC" socket pin 4. I do not use VOX on DATA modes. The hang up is not with the K3 or its PTT circuit. It is coming from the confuser....er computer. The Navigator has indicator LEDs on board and the PTT signal is being raised by the RTS signal on the 2nd serial port.

It is quite strange that it only occurs with FLRig. If I run FLDigi without FLRig, it never occurs.

I have been testing a remote setup using a app called "Splashtop". Splashtop has a streamer app that runs on the MacBook that links directly to the app on my iPad. Don't think it is Splashtop but have killed that to see if it goes away.

Jim
W4ATK
Post by Ken
Jim,
Do you have a Signalink USB with the "to PTT" cable plugged into the K3 PTT socket? If so, unplug it and your problems will go away. You don't need it and sometimes that will lock the rig on TX even though it's not actually transmitting.
If you don't have the Signalink but still have something plugged into the PTT socket, try unplugging it.
Ken WA8JXM
Post by Jim Rogers
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only FLRig should be controlling the radio.
I am having difficulty with the PTT locking in transmit. The only way I can clear it is to kill FLRig. After killing FLRig, if I restart it, FLRig will come up with PTT locked. To get everything back to normal I had to kill (required a "Forced Quit") FLDigi also and reboot.
I tried killing FLRig and then reconfiguring FLDigi for seperate port PTT and CAT and I could not successfully reconfigure without shutting down FLDigi and a restart. It appears to be some interaction between FLRig and FLDigi....
If I run FLDigi properly configured and do not use FLRig, everything stays together and works. I really like having FLRig in the mix for the additional rig controls.
Any help greatly appreciated.
Jim
David A. Ranch
2012-03-13 04:56:37 UTC
Permalink
Hello Jim,

I also reported this new behavior with Flrig+XMLRPC+Fldigi with a US
Interface Navigator + FT950 on Centos6.2 to Dave F. a few weeks ago.
Glad to see I'm not the only person having this problem! I haven't
played much with it recently but I was suspecting that Flrig was turning
on either:

- Flrig is asserting RTS on the dedicated PTT line when Flrig
shutdowns which then keys the rig. I have to *unplug* the US Int.
Navigator or start back up FLrig to unkey the rig which isn't pleasant

- the "FSK PTT" or "WinKeyer PTT" on the US Interface could be
somehow getting asserted


I need to play more with this and see what's going on but this is 100%
reproducible just using Flrig (no need to start Fldigi). It does NOT
happen with Hamlib on Fldigi.

--David
Post by Jim Rogers
I have FLRig and FLDigi installed on a 15" MacBook Pro running OS-X Lion.
My rig is a K3.
My interface is a Navigator. (basically six USB - Serial ports and a USB Codec)
I have installed the very latest FTDI drivers.
I have all of the rig control options in FLDigi disabled. So only
FLRig should be controlling the radio.
I am having difficulty with the PTT locking in transmit. The only way
I can clear it is to kill FLRig. After killing FLRig, if I restart it,
FLRig will come up with PTT locked. To get everything back to normal I
had to kill (required a "Forced Quit") FLDigi also and reboot.
I tried killing FLRig and then reconfiguring FLDigi for seperate port
PTT and CAT and I could not successfully reconfigure without shutting
down FLDigi and a restart. It appears to be some interaction between
FLRig and FLDigi....
If I run FLDigi properly configured and do not use FLRig, everything
stays together and works. I really like having FLRig in the mix for
the additional rig controls.
Any help greatly appreciated.
Jim
Loading...