Pat with FT-857 and Signalnk on Pi

[Bruce King]

Hi All,

I'm new to the Pat application and I'm try to get it working with my FT-857 and Signlink sound modem on my Raspberry Pi. I have it working on my FT-991A, using the internal sound card and USB for rig control. I've tried different configuration settings but can't get the ptt on the Signalink to work.

Would anyone have Pat working with an FT-857 and Signalink that maybe able to share their configuration settings?

Thanks
Bruce.

[KM4ACK]

Hey Bruce,

That is the exact setup I am using. I am not near my computer at the moment but would be glad to help when I get back in. What problem are you having? Are you able to key the radio from pat? If not, it is probably in your direwolf configuration.

Jason
KM4ACK

[Bruce King]

Hi Jason,

Thanks for the reply!

No, the Signalink is not keying the radio. I'm not running direwolf, is that required when using Signalink with Pat? 

Thanks,

Bruce

--
You received this message because you are subscribed to the Google Groups "pat-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+unsubscribe@googlegroups.com.
To post to this group, send email to pat-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/dd3e55e6-aaa2-4f74-83d7-7c9d590c4d03%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.

[KM4ACK]

Yes. Direwolf is the TNC.The signalink is just the soundcard that links the computer to the radio. Install direwolf with (sudo apt-get install direwolf) It will not install a direwolf.conf file so you will need to create one or download mine since we are using the same setup - https://www.dropbox.com/s/5uc8t2b3k5o2223/direwolf.conf?dl=0 Place the file .conf in /home/pi if you are using pi as your user. otherwise, change pi to YOURUSER name. You should only need to make one change to the direwolf.conf file.(Assuming you only have your signalink plug into the RPi) Look for the line that says MYCALL NOCALL and replace NOCALL with your callsign. Assuming you have already setup /etc/ax25/axports then start (direwolf -p). Then run (sudo kissattach /tmp/kisstnc wl2k) Now start pat (pat http) Then from pat's web gui, you should be able to make a connection.

I made several assumptions about your setup. If they are correct, it should work. You do not have to configure ptt in direwolf.conf as the signalink has VOX built in and handles it for you.

Jason
KM4ACK

On Wednesday, April 11, 2018 at 6:43:09 PM UTC-5, Bruce King wrote:

Hi Jason,

Thanks for the reply!

No, the Signalink is not keying the radio. I'm not running direwolf, is that required when using Signalink with Pat? 

Thanks,

Bruce

On Wed, Apr 11, 2018 at 9:25 AM, KM4ACK <jason....@gmail.com> wrote:

Hey Bruce,

That is the exact setup I am using. I am not near my computer at the moment but would be glad to help when I get back in. What problem are you having? Are you able to key the radio from pat? If not, it is probably in your direwolf configuration.

Jason
KM4ACK

On Monday, April 9, 2018 at 1:32:30 PM UTC-5, Bruce King wrote:

Hi All,

I'm new to the Pat application and I'm try to get it working with my FT-857 and Signlink sound modem on my Raspberry Pi. I have it working on my FT-991A, using the internal sound card and USB for rig control. I've tried different configuration settings but can't get the ptt on the Signalink to work.

Would anyone have Pat working with an FT-857 and Signalink that maybe able to share their configuration settings?

Thanks
Bruce.

--
You received this message because you are subscribed to the Google Groups "pat-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.

To post to this group, send email to pat-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/dd3e55e6-aaa2-4f74-83d7-7c9d590c4d03%40googlegroups.com.

[KM4ACK]

Oh. And once you have that working, you should move on to adrop for HF work. https://groups.google.com/forum/#!searchin/pat-users/ardop%7Csort:date/pat-users/CDXwyolvhx8/LhXCjNzgBQAJ It works great with this setup.

On Monday, April 9, 2018 at 1:32:30 PM UTC-5, Bruce King wrote:

[Bruce King]

Hi Jason,

Thanks very much! I will install Direwolf and reply back with the results.

Thanks,

Bruce

You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/SanAHJIbNvc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+unsubscribe@googlegroups.com.

To post to this group, send email to pat-...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/bd9e9635-8d2f-4c9a-9509-4eb6e87dd268%40googlegroups.com.

[Erlend Grimseid]

What mode were you using with the internal soundcard of the other radio? Direwolf is not required unless you want to use it for packet.

But back to the signalink. I have never used one, but I am under the impression that it simply is an usb sound card with an vox interface built in. If that's the case it should trigger ptt as soon as an appropriate signal is present from what ever sounds card modem you are using.

Does the red ptt led light up when you try to transmit?
Are you using the correct cable and jumper settings for your radio?
Is the soft modem you are using pointed to the correct sound card?
If you are using the tnc connector on the back of the ft857, Is the radio set to Digi mode (for USB) or Packet (for FM packet). If it's set to ssb or FM it's expecting ptt and audio from the microphone connector and not the rear data port.

Hope this helps.
73
LA4TTA
Erlend

[Bruce King]

Hi Eriend, Jason,

I followed your tutorial at :

https://la4tta.blogspot.ca/2018/04/setting-up-ardop-on-raspberry-pi.html

I can get the ft-991A  radio with the internal soundcard to work with ARDOP only. The SignaLink works on both radios when using Winlink Express on Windows OS.

Can't get the ft-857 with signalink working yet. I installed Direwolf and configured it as Jason suggested but keeping getting the following:

Unable to QSY: Missing rig reference in config section for ax25, don't know which rig to qsy

when I define my rig in the config file using pat configure I then get:

Unable to QSY: Unable to get rig frequency: dial tcp [::1]:4532: getsockopt: connection refused

My data cable from the ft-857 is going to the SignaLink, so I'm not expecting rig control. Maybe I'm missing some setting on the ft-857.

Jason, could you share your config.jason file you have for your ft-857? What pat mode are you using with the SignaLink? Are you running  direwolf -p  for only AX.25 and  ./piardopc -p gpio for ARDOP?

Thanks,

Bruce 

--
You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/SanAHJIbNvc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+unsubscribe@googlegroups.com.

To post to this group, send an email to pat-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/8a7dc1fb-2bfc-4b92-a52d-f4d3e9f33ce7%40googlegroups.com.

[Erlend Grimseid]

Ok. So I'm just going to do a quick reply before going calling it the night here in Norway.  Hopefully it will get you a bit closer.  Let's focus on ardop first as I think that is the easiest to master. 

I'm assuming you are using rig control with the 991, and Pat is configured to do so since pat expects a qsy and works with the 991. Try doing an connect without typing in an frequency. If that don't work try connecting the 991, or start rig control with an dummy rig.

To use ardop with an vox interface you don't have to use the -p option.  It should trigger ptt when piardopc starts to play music. But make sure that the .asoundrc file points to the correct soundcard.  I believe the command for listing soundcard is arec -l  or something like that.  Or you can find it in alsamixer. I think it's f6 that lists cards, but you will find that in the terminal "gui". Remember that if you are using soundcard 2.0 the .asoundrc file need to point to plughw:2.0 not hw:2.0.

Also.  For vox to work levels needs to be high enough.  If the terminal window with piardopc reports that it is transmitting and the interface don't trigger ptt. Check that levels are high enough. If it still don't work double check that you are using the right sound card. 

73

LA4TTA 

Erlend 

Thanks,

Bruce 

To unsubscribe from this group and all its topics, send an email to pat-users+...@googlegroups.com.

[KM4ACK]

Bruce,

Just to clarify, direwolf is only needed for packet work. ardop is for HF work. Use direwolf -p for packet. There is no -p option for piardopc. The 857D will key using the signalink in USB mode, FM, or digi, mode. I have run mine successfully in all of those modes. For now, I would follow Erlend's advice and just get the radio to keying before trying to get rig control working. Rig control is a bit limited in Pat anyway. It will change the frequency but from what I have learned, it can't change modes on the radio. So if you are using FM at the moment and tell pat to use ardop for work on 7.102, Pat will move the radio to 7.102 but leave the radio in FM mode. Initially set the knobs on your signalink as TX=half, RX=half, and delay all the way counter clockwise. Full counter clockwise will be off.  The link for my config.json file is here - https://www.dropbox.com/s/k2vjif6vs5tx37s/config.json?dl=0 You will need to mod the callsign, password, and locator (gridsquare) before using it. Everything else should work. On the connect screen inside the pat gui, choose your transport, enter the callsign of the station you wish to reach (including the SSID if needed), and click the connect button. I have found that it can sometimes take 20-30 seconds for pat to start keying the radio. Also, it might be easier to help over the phone. I would be willing to setup a phone call. Just shoot me an email at my call...@arrl.net if that's of interest and we can arrange a good time.

Jason
KM4ACK

[Bruce King (Sea Shanty)]

Guys,

 

Thanks very much for the help with this, awesome support on this site.

 

I managed to get Pat and SignaLink to key the FT-857 with ARDOP transport, I had to increase Menu # 37 DIG GAIN to 50 and it started keying. The PTT light doesn’t come on while its keying, so I’m not sure if that’s normal or if it still needs tweaking. I’m about to try with Jason’s config file and will report back.

 

Thanks again for your help and the offer for phone support.

 

I can’t get this type of support from my internet service provider here in Canada.

 

Bruce

--

You received this message because you are subscribed to the Google Groups "pat-users" group.

To unsubscribe from this group and stop receiving emails from it, send an email to pat-users+...@googlegroups.com.
To post to this group, send email to pat-...@googlegroups.com.
To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/4a079941-85d4-4904-aa83-cb8d2591ec81%40googlegroups.com.

[KM4ACK]

Glad you got it working Bruce. You should see the PTT light on both the 857D and the signalink while it's transmitting. Have you made a successful connection?

Jason 

KM4ACK

[Bruce King (Sea Shanty)]

Hi Jason

 

The PTT light is on the radio when transmitting but not the signalink.

 

I used your config file but I have to add :

my_rig": {"address": "localhost:4532", "network": "tcp"} and then run  rigctld -m 1 -p=/dev/ttyS0 and add my_rig to the ardop  rig section.

 

If I don’t run rigctld I get:

Unable to QSY: Unable to get rig frequency: dial tcp [::1]:4532: getsockopt: connection refused

 

 

 

When I run:

pi@raspberrypi:~/pat $ sudo arecord -l

**** List of CAPTURE Hardware Devices ****

card 1: CODEC [USB AUDIO  CODEC], device 0: USB Audio [USB Audio]

  Subdevices: 0/1

  Subdevice #0: subdevice #0

 

And my .asoundrc file is:

 

pcm.ARDOP {

type rate

slave {

pcm "plughw:1,0"

rate 48000

}

}

 

Does that look correct for your setup? No connection yet.

 

Thanks

Bruce.

 

Sent from Mail for Windows 10

 

From: KM4ACK
Sent: Friday, April 13, 2018 12:41 PM
To: pat-users
Subject: Re: Pat with FT-857 and Signalnk on Pi

 

Glad you got it working Bruce. You should see the PTT light on both the 857D and the signalink while it's transmitting. Have you made a successful connection?

 

Jason 

KM4ACK

--
You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/SanAHJIbNvc/unsubscribe.
To unsubscribe from this group and all its topics, send an email to pat-users+...@googlegroups.com.

To post to this group, send email to pat-...@googlegroups.com.

To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/df9eb232-c4e8-4053-95ae-1525f1e59e06%40googlegroups.com.

[KM4ACK]

That's odd that the signalink ptt light isn't on. Ive never had that to happen.

You will have to run rigctld in order for rig control to work. I would add that to my rc.local file so it happens on startup if you want to use rig control.

I did not modify my .asoundrc file. I tried the default and it worked so i haven't messed with it. I did read that others have changed it to get things going.

The results from arecord -l look identical to mine.

Are you starting ardop with ./piardopc 8515 plughw:1,0 plughw:1,0

one of the tutorial I read said ./piardopc 8515 hw:1,0:hw:1,0 but that would't work for me.

Jason
KM4ACK

[Erlend Grimseid]

It sounds like your 857 uses digi vox. Ant that is what is triggering ptt.

Try using alsamixer to adjust levels.
Just run the command alsamixer in the terminal and an simple mixer should appear. Use the F buttons to select card, in and output. Arrow buttons to select faders and adjust volume, ashes space and the m button to switch switchers and turn on and of channels. Some people advice that you turn off auto gain.

Adjust rx volume so that ardop reports an average level of around + and - 20000.

[Bruce King]

I finally got it working. Adjusted the levels using alsamixer as suggested and lowered the digi gain. The other issue that maybe a factor, I was using a 1 amp power supply on the Pi, once I plugged in the correct power supply the ptt on the Signalink started keying the radio and lighting up.

I was able to make a good connection using ARDOP.

Thanks again for all the help!
Bruce.

Sent from my iPad

> --
> You received this message because you are subscribed to a topic in the Google Groups "pat-users" group.
> To unsubscribe from this topic, visit https://groups.google.com/d/topic/pat-users/SanAHJIbNvc/unsubscribe.
> To unsubscribe from this group and all its topics, send an email to pat-users+...@googlegroups.com.

> To post to this group, send an email to pat-...@googlegroups.com.
> To view this discussion on the web, visit https://groups.google.com/d/msgid/pat-users/9cad71ff-44a0-4486-9e25-538c249c016b%40googlegroups.com.