|
Setup...
FTM-857D
FTM-300DR
2 x SCU-17
Linux Mint 20.3
AMD Ryzen Embedded 1605B 16GB
I'm trying to figure out how to configure Direwolf to act as a TNC for the 300. Yes the 300 has APRS built in but I want to do over the air packet and APRS with mapping and all the features that come with using a PC application. Obviously the APRS modem in the radio will be turned off during this time.
I'm new to TNC stuff. I've used JS8Call, FT8, FLDigi, ect but those connect directly to the sound device or at least connect through pulse.
I need Direwolf to connect directly to the SCU-17 that is connect to the 300DR or at least directly through some virtual interface to the USB sound interface as I have 2 radio connected to the same machine.
One is a 857D the other a 300DR.
The idea is to be able to operate digital HF and APRS at the same time if needed but for now I'm just focusing on VHF/UHF
Heck it might even be nice to be able to act as a bridge for APRS HF and APRS VHF or UHF, but I think that would complicate things. For now just getting Direwolf to connect to my SCU-17 to do packet via my 300DR is a great start.
Any help is appreciated.
My Google-foo seems to have failed in finding a how to on just configuring Direwolf as a TNC
Obviously by my misc jumping around in my description I'm a bit flustered trying to figure this out.
|
Hello Patrick,
I need Direwolf to connect directly to the SCU-17 that
is connect to the 300DR or at least directly through some virtual
interface to the USB sound interface as I have 2 radio connected
to the same machine.
This is very possible.
The idea is to be able to operate digital HF and APRS at the
same time if needed but for now I'm just focusing on VHF/UHF
Only one sound device will be available at any one time to a program
but if you operate "digital HF" on your FT857 using SCU-17#1 while
you operate "VHF APRS" on your FTM300 using SCU-17#2, that will work
fine.? Any other combination than that will be very difficult if not
impossible as neither radio supports dual sound inputs.
Heck it might even be nice to be able to act as a bridge for
APRS HF and APRS VHF or UHF, but I think that would complicate
things. For now just getting Direwolf to connect to my SCU-17 to
do packet via my 300DR is a great start.
Any help is appreciated.
Have you read the Direwolf User Guide and given it a try??
??
Please do can some back here if you have any problems.? If you're
currently stuck, please provide lots of details of what's the issue
and only then can people really help you.
--David
KI6ZHD
|
Thank you for the reply.
I've given that a go before though I may have missed what I was looking for and I don't think I realized it was the official Direwolf howto guide so let me give it a go again and see what I can get done and get back to you.
Regarding operating on the FT857 while operating VHF APRS it's very likely I'll have something like JS8Call or WSJTX or FLDigi going on the FT857 while the 300DR is doing APRS.
Basically they'll be handled by different applications at the same time though I'd like to be able to switch it up when and if needed.
Such as putting it in a APRS bridge or something of the sort. Bridging VHF to HF such as in the situation of being unattended for any reason there by allowing a local station to reach far away stations and visa versa while off the grid.
This would be a just in case situation
Being able to have a application like YAAC monitor, send and receive messages at the same time would be handy as well with both.
Basically it's a contingency plan, just in case.
For now I'll start with just the 300DR, make a backup of the config then try other options.
Baby steps, get it working then go from there.
I'll report back if I start racking my brain against the wall.
|
OK, so yea, going to need some help. I'm finding it a bit overwhelming. Direwolf is capable of doing quite a bit considering.
The biggest issue I'm having right now is trying to target the correct sound device.
Here is my list of sound devices...
**** List of PLAYBACK Hardware Devices ****
card 0: Generic_1 [HD-Audio Generic], device 3: HDMI 0 [HDMI 0]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 0: Generic_1 [HD-Audio Generic], device 7: HDMI 1 [HDMI 1]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 0: Generic_1 [HD-Audio Generic], device 8: HDMI 2 [HDMI 2]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 0: Generic_1 [HD-Audio Generic], device 9: HDMI 3 [HDMI 3]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 2: CODEC [USB Audio CODEC], device 0: USB Audio [USB Audio]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
card 3: CODEC_1 [USB Audio CODEC], device 0: USB Audio [USB Audio]
? Subdevices: 1/1
? Subdevice #0: subdevice #0
In Direwolf I set the sound (AChannels) as follows...
ACHANNELS 1
ARATE 44100
ADEVICE plughw:CARD=CODEC_1,DEV=0 hw:CARD=CODEC_1,DEV=0
DWAIT 0
SLOTTIME 10
PERSIST 63
TXDELAY 30
TXTAIL 10
FULLDUP OFF
The extra parameters weren't in the config file, I assumed likely the default anyhow but for future reference and to be sure, I put them in to be set.
It's likely they're not in the right spot, but anyhow....
I targetted what I believe is the correct sound device but I'm not seeing any decode nor PTT
I'm transmitting from my APRS iGate (connected over the network via KISS from my desktop) but it doesn't look like the 300DR received it though I can hear the 300DR heard the traffic.
When I run direwolf and then open YAAC I get the following.......
Dire Wolf DEVELOPMENT version 1.7 E (Apr 25 2022)
Includes optional support for:? gpsd hamlib cm108-ptt
Reading config file direwolf.conf
Audio input device for receive: plughw:CARD=CODEC_1,DEV=0? (channel 0)
Audio out device for transmit: hw:CARD=CODEC_1,DEV=0? (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Attached to KISS TCP client application 0 on port 8001 ...
Ready to accept KISS TCP client application 1 on port 8001 ...
KISS protocol set hardware "TNC:", chan 0
KISS protocol set hardware "MODEM:", chan 0
KISS Set Hardware unrecognized command: MODEM.
KISS protocol set hardware "MODEML:", chan 0
KISS Set Hardware unrecognized command: MODEML.
KISS protocol set hardware "MODEMBW:", chan 0
KISS Set Hardware unrecognized command: MODEMBW.
Direwolf has to point directly to the device and not depend on Pulse or ALSA to determine the inputs and output or there's no way I can use two radios at the same time on one machine.
Keep in mind the 300DR is on a dummy load, all it can hear is my iGate and if it transmits I'm sure only the iGate will hear it.
PTT is configured as follows....
PTT /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if00-port0 -DTR
#PTT RIG 1021 /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if00-port0 19200
I have the other PTT there as I was testing with it, there was no PTT with either
Other config settings I have is....
CHANNEL 0
MY CALL KD7WPQ
MODEM 1200
AGWPORT 8000
KISSPORT 8001
FIX_BITS 1
Everything else in the config file is all commented (#) out
|
OK, I seemingly overlooked the volume on the sound interface and have confirmed direwolf sees traffic but YAAK isn't, not sure why since YAAK does report a connected application on port 8001 when I open it.
Just got PTT kind of working but it will dead key with either PTT line I use when direwolf is run.
|
Hello Patrick,
OK, I seemingly overlooked the volume on the sound
interface and have confirmed direwolf sees traffic but YAAK isn't,
not sure why since YAAK does report a connected application on
port 8001 when I open it.
I cannot help you with YACC APRS application running over Java but I
would assume you have a configuration issue with that application.?
Consider joining the YACC support group at [email protected] but
beyond that, try enabling debugging on YACC and see what that might
tell you.
Just got PTT kind of working but it will dead key with either
PTT line I use when direwolf is run.
How have you connected your sound device to your radio?? Is it via a
specific serial port's control signal?? Maybe you're using GPIO pins
on the sound device, GPIO pins on a Raspberry Pi?? Maybe you're
using a Signalink with "auto-VOX"?? Are you using something like an
easy-digi isolation device?
--David
KI6ZHD
|
I'll jump over there and see what I can get figured out. I have the radio connected via USB to a via a ?which provides CAT control via a serial port and sound via a 10-pin mini-DIN to 6-pin Mini-DIN. The 6 pin is plugged into the I am able to see Direwolf decode what the radio receives, now I need to get PTT working to verify I have the correct outgoing or microphone port. Currently my PTT configuration(s) only lock the radio in transmit when Direwolf is run. #PTT COM1 RTS #PTT COM1 RTS -DTR PTT /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0 DTR #PTT RIG 1022 /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0 19200 I have another SCU-17 on my FT-857D on the same computer, it is controlled via FLRig and it shows the following working configuration... 
|
Anyone have an insite on how to get PTT working or some things I can test to get it working?
I've tried ending the first un-commented PTT line with RTS, RTS DTR, RTS -DTR, -DTR and DTR and it will dead key
Being that hamlib doesn't have any of the D (digital) variations in it's library I tried RIG 1021, RIG 1022 and RIG 1043, none of those seemed to work either.
I do know my com port is set to 19200, I set it, Data speed is set to 1200, so I know that is set correctly but I'm not sure what other options I have regarding PTT configuration.
Does anyone have any ideas, thoughts and or suggestions?
I'm willing to give whatever you think up a go to see if we can get the SCU-17 to key PTT
|
Patrick,
The following is the entire contents of my direwolf.conf running on a Raspberry pi.
ADEVICE plughw:1,0 plughw:1,0 ACHANNELS 1 CHANNEL 0 MYCALL K5CG MODEM 1200 PTT /dev/ttyUSB0 RTS TXDELAY 30 TXTAIL 10 AGWPORT 8000
The serial port is an FTDI USB to RS-232 cable and the radio (a KW TM-V71A) is set to key on the assertion of RTS (using it's Echolink Sysop mode feature). This appears as /dev/ttyUSB0.
Audio in/out is via a simple USB sound fob. This appears as device #1.
YAAC connects to the AGWPORT and direwolf keys the radio when needed.
I don't know anything about the SCU-17 but is there a way to know the COM port number or device name from whatever PC you are connecting it to?
From: "Patrick" <kd7wpq@...>
To: [email protected]
Sent: Thursday, April 28, 2022 10:35:45 PM
Subject: Re: [direwolf] Direwolf as a TNC Help
Anyone have an insite on how to get PTT working or some things I can test to get it working?
I've tried ending the first un-commented PTT line with RTS, RTS DTR, RTS -DTR, -DTR and DTR and it will dead key
Being that hamlib doesn't have any of the D (digital) variations in it's library I tried RIG 1021, RIG 1022 and RIG 1043, none of those seemed to work either.
I do know my com port is set to 19200, I set it, Data speed is set to 1200, so I know that is set correctly but I'm not sure what other options I have regarding PTT configuration.
Does anyone have any ideas, thoughts and or suggestions?
I'm willing to give whatever you think up a go to see if we can get the SCU-17 to key PTT
|
Danny, thank you for the reply.
There is a way to find the device, yes
Basically instead of using /dev/ttyUSB0 or 1 I'm targeting it by ID by using /dev/serial/by-id/............
I had not however tried /dev/ttyUSB* but just gave it a go and the results were the same. /dev/ttyUSB1 DTR gave a dead key
I am however going to give creating a link to each device a go so they are better sorted as found here () starting at 8:39.
Something I didn't realize you could do until I saw that.
Basically once I figure out exactly what is what I'm going to at least create a /dev/300PTT and a /dev/857PTT link with rules so that no matter how or when the system starts I will always know exactly where and what my /dev/PTT is.
I'm about 90% sure /dev/USB1 and /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0 is CAT/PTT control and I believe the problem is that PTT is controlled by CAT and not just a simple RTS DTR command.
The question is how to work with and/or around a CAT command for something so new that it's not listed in any libraries yet?
On the SCU-17 you have two devices per SCU-17. One is CAT control the other is a sound interface.
For instance I have /dev/ttyUSB0, /dev/ttyUSB1, /dev/ttyUSB2 and /dev/ttyUSB3 as I have two SCU-17's connected.
ls /dev/serial/by-id/ lists them as the following...
usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00AC0110-if00-port0
usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00AC0110-if01-port0
usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if00-port0
usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0
The other SCU-17 is connected to a 857D and that is listed in hamlib, well the 857 is, not the 857D specifically though the commands should be the same.
FLRig has absolutely no problem controlling the 857D so for FLDigi, WSJTX and JS8Call I just point them to FLRig for control and it works great, plus it allows me control of my rig on my screen, pretty much just bling there but hey, whatever, could come in handy for remote stuff.
Anyhow, indeed a good thought about using another app to control it, it does have me thinking about other ways to achieve the same objective though not certain how at the moment.
|
OK, I've done a bit more testing and have verified that FLDigi has no problem keying the SCU-17 but direwolf is having problems.
If I set FLDigi's Hardware PTT to /dev/ttyUSB1 RTS then I can trigger PTT with tune. If I turn tune off PTT is let go.
DTR gives me FSK properly
RTS = +V gives me a PTT dead key
DTR = +V give me a FSK dead key
If I set direwolf to...
PTT /dev/ttyUSB1 -RTS
I get a FSK RTS dead key
RTS gives me a FSK dead key
DTR gives me a PTT dead key
-DTR gives me a FSK and PTT dead key
This has to be a config issue I'm missing somewhere
Edit: Just did some digging, seems I'm not the first to have this issue....
https://github.com/wb2osz/direwolf/issues/44
|
I'll ask the obvious question: ?? You aren't trying to use /dev/ttyUSB1 when both FLDigi and Direwolf are running? ?? Being more specific, you are sure FLDigi is 'dropping' its connection to /dev/ttyUSB1 before you start Direwolf?
On Saturday, April 30, 2022, 07:10:07 PM EDT, Patrick <kd7wpq@...> wrote:
[Edited Message Follows]
OK, I've done a bit more testing and have verified that FLDigi has no problem keying the SCU-17 but direwolf is having problems.
If I set FLDigi's Hardware PTT to /dev/ttyUSB1 RTS then I can trigger PTT with tune. If I turn tune off PTT is let go.
DTR gives me FSK properly
RTS = +V gives me a PTT dead key
DTR = +V give me a FSK dead key
If I set direwolf to...
PTT /dev/ttyUSB1 -RTS
I get a FSK RTS dead key
RTS gives me a FSK dead key
DTR gives me a PTT dead key
-DTR gives me a FSK and PTT dead key
This has to be a config issue I'm missing somewhere
Edit: Just did some digging, seems I'm not the first to have this issue....
https://github.com/wb2osz/direwolf/issues/44
|
Great question to be sure I'm not pointing two applications to the same device :)
A easy mistake to make for sure, but no.
I opened FLDigi and ran it without direwolf running to see if it would key PTT any different, and it did
The two applications are not run at the same time.
I'm trying to run YAAC with Direwolf as a KISS TNC interface but without PTT working in Direwolf it's kind of pointless
And yes, I'm very sure FLDigi was dropping PTT when "Tune" was turned off (not green).
I tested it twice.
|
What about Flrig? Are you using that with Fldigi? If so, Flrig is the program that is owning the serial port, not Fldigi, so it is what has to be shut down before starting DireWolf. Andrew, KA2DDO author of YAAC ________________________________________ From: [email protected] < [email protected]> on behalf of Patrick <kd7wpq@...> Sent: Saturday, April 30, 2022 8:36 PM To: [email protected]Subject: Re: [direwolf] Direwolf as a TNC Help Great question to be sure I'm not pointing two applications to the same device :) A easy mistake to make for sure, but no. I opened FLDigi and ran it without direwolf running to see if it would key PTT any different, and it did The two applications are not run at the same time. I'm trying to run YAAC with Direwolf as a KISS TNC interface but without PTT working in Direwolf it's kind of pointless And yes, I'm very sure FLDigi was dropping PTT when "Tune" was turned off (not green). I tested it twice.
|
Nope, I have FLRig and FLDigi configured to use my 857 by default.
FLRig is pointed to /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00AC0110-if00-port0
Firewolf (/dev/ttyUSB1) is configured to use
/dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0
No other applications are running using those devices unless I open them
And just for the heck of it I just configured FLDigi to use Hardware PTT (CAT turned off) to /dev/serial/by-id/usb-Silicon_Labs_CP2105_Dual_USB_to_UART_Bridge_Controller_00F8CEC3-if01-port0 with "Use RTS" checked, closed the config window and clicked on "Tune" and it keyed up. Click Tune again (to turn it off) and PTT let go.
|
Hopefully I haven't baffled or stumped everyone.
Granted I'm a bit stumped as to why it's not working.
Is it possible it's a application bug and if so what do I need to do to request it be fixed?
|
Hello Patrick,
It's a pretty remote possibility that this is a code bug since 1000s
of people are successfully using Direwolf.? The unique thing here is
that you're using the Yaesu SCU-17 device with matching Yaesu cable
which many people don't have.? I would imagine you can make it work
but you need to work your way through the testing steps I've offered
to confirm you're actually getting the signals you expect.? To me,
your core issue seems to be showing up with FSK led lighting up
symptom.? It would be interesting to see if toggling that switch
inside the radio body itself to see how that changes your outcome.
--David
KI6ZHD
On 05/01/2022 12:45 PM, Patrick wrote:
toggle quoted message
Show quoted text
Hopefully I haven't baffled or stumped everyone.
Granted I'm a bit stumped as to why it's not working.
Is it possible it's a application bug and if so what do I need
to do to request it be fixed?
|
Understood, but toggling the switch should only switch the PTT method whether that by PTT or FSK in accordance to the signal it receives, be that RTS or DTR, but I digress, if my buddy and I have no luck I will give that a go, pull it out and do some tinkering.
I'm still curious why I can get PTT in FLDigi without a issue but not Direwolf, or rather it works correctly.
Another thing I thought about doing is grabbing one of my USB serial adapters that shows what signals are being sent via LEDs on the adapter and seeing what it shows me.
I'll report back when I have more results.
|
I had a similar problem when using a USB to serial adapter and an EasyDigi board. Both the RTS and DTR pins are wired to the EasyDigi - presumably so that either one can be selected for PTT by the client. Lines that seemed like they should work either gave me no PTT or a constant transmit. The only line that worked in direwolf.conf was this:
PTT /dev/ttyUSB0 RTS DTR
At the time I implemented the above, it was not considered a valid option based on my interpretation of what's in the manual, but it worked.? If it hasn't been tried already you might want to try the above and also try reversing RTS and DTR in the line if the above doesn't work. Of course change the serial port to match yours.
73, Lee K5DAT
On Sun, May 1, 2022 at 3:25 PM Patrick < kd7wpq@...> wrote: Understood, but toggling the switch should only switch the PTT method
whether that by PTT or FSK in accordance to the signal it receives, be
that RTS or DTR, but I digress, if my buddy and I have no luck I will
give that a go, pull it out and do some tinkering.
I'm still curious why I can get PTT in FLDigi without a issue but not
Direwolf, or rather it works correctly.
Another thing I thought about doing is grabbing one of my USB serial
adapters that shows what signals are being sent via LEDs on the adapter
and seeing what it shows me.
I'll report back when I have more results.
|
Well dad gum, I could have SWORE for the life of me I tried that
I swapped RTS and DTR back and fourth and they both worked though it is triggering FKS and PTT at the same time it is working and I've successfully sent some messages to myself.
I tried some other combinations and got a dead key, but whatever, RTS DTR seems to do it, very weird
toggle quoted message
Show quoted text
On 5/1/22 14:38, Lee Bengston wrote: I had a similar problem when using a USB to serial adapter and an EasyDigi board. Both the RTS and DTR pins are wired to the EasyDigi - presumably so that either one can be selected for PTT by the client. Lines that seemed like they should work either gave me no PTT or a constant transmit. The only line that worked in direwolf.conf was this:
PTT /dev/ttyUSB0 RTS DTR
At the time I implemented the above, it was not considered a valid option based on my interpretation of what's in the manual, but it worked.? If it hasn't been tried already you might want to try the above and also try reversing RTS and DTR in the line if the above doesn't work. Of course change the serial port to match yours.
73,
Lee K5DAT
|
Danny K5CG