toggle quoted messageShow quoted text
Putting out a blanket call again - I’ve tried all the suggestions and can’t get this thing up and running. I think I’m down to a few options.
- Would anyone be willing to zoom / FaceTime to help me troubleshoot or build from the ground up who also has the 857D and SignaLink? I’m really trying to get 2M packet up and running for Field Day demonstrations with ARES.
- If not, would anyone be willing to share their image with me so I can burn it and run it on my setup?
Now I’m completely lost - if I don’t have a cat cable going from Pi to Radio, then how is FlRig going to run? Don’t you need FlRig to run Direwolf and packet?
I unplugged the cable as suggested - now FLRIG doesn’t know what comms path to take to the radio. There are no readily-identifiable ports, so I tried every tty and ama/amo. No joy.
For now, remove the CAT cable so you're only using your Raspberry
Pi, Direwolf, the Signalink, and the radio.
For your Fldigi / Flrig setup, that's potentially something
configured very differently potentially asserting PTT via CAT
control (bypassing the Signalink based PTT control)
On 06/15/2020 06:33 PM, Grant Greenwell
Thanks for your reply. To clarify, I have the Pi
with a cat control cable to the 857D via the tuner (so Pi to
tuner to radio). I also have Pi to SignaLink to radio.
When I press “tune” in FLRIG it keys the radio, but
When I use FLDIGI, and press “tune” (or any other
command), the SignaLink PTT illuminates, and the radio
If you're just using a FT857 and a Signalink without a
CAT connection, then Flrig should do nothing. PTT
control is completely handled by the Signalink device.
Flrig should not even be used as it won't have any
function without CAT or some other control.
Would it be an issue with the SignaLink
even if FLRIG, FLDIGI, ARDOP can all get the radio
to transmit, or do you think it’s something in my
Direwolf configuration? I swapped the jumper
module, the SignaLink, and the cables with
known-good and I still have the symptoms.
I tried the radio in packet, FM, and
digital - the same problem exists on each mode.
Any thoughts on how to get the SignaLink
to not do CAT? (I thought CAT was being done
I am able to get
FLRig to PTT even in packet mode.
Direwolf starts up, RIGCTL turns green,
KISSATCH turns green, and Pat opens up.
When I try to initiate an AX.25
communication, SignaLink PTT will turn
red, but does not key the radio.
That's a new one. If the Signalink's PTT
LED lights up, your radio should key up
too. This is an issue with your Signalink,
it's jumper configuration, or your cabling.
It's very strange it works for other
You mentioned a FT857. What mode is the
radio in? Try PKT or DIG mode and try
And Pat opens up and
gives the radio frequency for my-rig, and
the AX.25 can key SignaLink... there's
just something going on with PTT maybe?
(Do I have that right? SignaLink
provides the audio/tones but something
else controls the PTT?)
Ok.. this doesn't make sense. The Signalink
only does audio and fakes out PTT. If
you're getting automatic frequency updates
from the radio back to Pat, this means you
have another connection to your radio doing
CAT control. This is ok but you need to be
cleat that the Signalink should do the PTT.
Configure all your programs NOT to use CAT
for PTT control.