Keyboard Shortcuts
ctrl + shift + ? :
Show all keyboard shortcuts
ctrl + g :
Navigate to a group
ctrl + shift + f :
Find
ctrl + / :
Quick actions
esc to dismiss
Likes
- Direwolf
- Messages
Search
Re: Help with CM108 PTT
So you are using Direwolf with 2 different applications. One is working and the other is not? My assumption would be that the QtTermTCP has a means of controlling the PTT line outside of Direwolf. Your description says: "Note: PTT not configured for channel 0. (Ignore this if using VOX.)" ? Well, it doesn't sound like you are using VOX, so you should not ignore this. ? AGW is a different protocol (8000) than the protocol for KISS over TCP/IP (8001).? So there may be something in the AGW setup that is controlling the PTT, but not in the KISS TCP setup/ So, I suggestconfiguring Direwolf to control the PTT via the DINAH PTT pin GPIO 3 ? I believe this needs to be configured in the DireWolf.conf, something like ?? PTT CM108 3 /dev/DIHAH? ? You may have to change some udev rules to access this. Robert Giuliano
On Friday, February 5, 2021, 8:45:07 PM EST, W8DSB <w8dsb@...> wrote:
I have direwolf with QtTermTCP running with a DINAH with no issues. The hardware is hooked up and working. The system is using the CM108 chip and again it works ok? When I run PAT on the same system the hardware does not key up.. This is what I see when I start direwolf. Note: PTT not configured for channel 0. (Ignore this if using VOX.)
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/1
Created symlink /tmp/kisstnc -> /dev/pts/1
How can it work via port 8000 tcp but not 8001 via serial. I must be missing something. |
Help with CM108 PTT
I have direwolf with QtTermTCP running with a DINAH with no issues. The hardware is hooked up and working. The system is using the CM108 chip and again it works ok?
When I run PAT on the same system the hardware does not key up.. This is what I see when I start direwolf. Note: PTT not configured for channel 0. (Ignore this if using VOX.)
Ready to accept AGW client application 0 on port 8000 ...
Ready to accept KISS TCP client application 0 on port 8001 ...
Virtual KISS TNC is available on /dev/pts/1
Created symlink /tmp/kisstnc -> /dev/pts/1
How can it work via port 8000 tcp but not 8001 via serial. I must be missing something. |
Re: Direwolf as a service
¿ªÔÆÌåÓýHello Darrell, ?? CGroup: /system.slice/direwolf.service Ok.. that looks good.
Ok.. so this doesn't look like it has anything to do with direwolf, etc.? Few things: ?? - what does "ls -la /tmp/kisstnc" show? ?? - what does "ls -la /dev/pts/*" show? If you run "sudo su" and then run "kissattach /tmp/kisstnc radio", does it work?
Seems you should fix the perms here so you make systemd happy.
Per my test above, not everything works properly with sudo.? Usually, issues are seen when using redirects, pipes, etc. and a simple command like kissattach should work but I'm not 100% sure.? The above test will help you narrow that down. --David |
Re: Direwolf as a service
On Fri, Feb 5, 2021 at 11:53 AM, David Ranch wrote:
journalctlHi David, I think this is what your asking for: ? ?CGroup: /system.slice/direwolf.service
? ? ? ? ? ?`-572 /usr/local/bin/direwolf -t 0 -c /home/pi/direwolf.conf -p
?
Feb 05 12:53:14 hampi direwolf[572]: Dire Wolf DEVELOPMENT version 1.7 A (Dec? 6 2020)
Feb 05 12:53:14 hampi direwolf[572]: Includes optional support for:? gpsd hamlib cm108-ptt
Feb 05 12:53:14 hampi direwolf[572]: Reading config file /home/pi/direwolf.conf
Feb 05 12:53:14 hampi direwolf[572]: Audio device for both receive and transmit: plughw:2,0? (channel 0)
Feb 05 12:53:15 hampi direwolf[572]: Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate / 3.
Feb 05 12:53:15 hampi direwolf[572]: Using /dev/hidraw0 GPIO 3 for channel 0 PTT control.
Feb 05 12:53:15 hampi direwolf[572]: Ready to accept AGW client application 0 on port 8000 ...
Feb 05 12:53:15 hampi direwolf[572]: Ready to accept KISS TCP client application 0 on port 8001 ...
Feb 05 12:53:15 hampi direwolf[572]: Virtual KISS TNC is available on /dev/pts/0
Feb 05 12:53:15 hampi direwolf[572]: Created symlink /tmp/kisstnc -> /dev/pts/0
?
pi@hampi:~ $ sudo kissattach /tmp/kisstnc radio
kissattach: /tmp/kisstnc: open: Permission denied
?
pi@hampi:~ $? journalctl
?
Feb 05 12:55:09 hampi sudo[1817]:? ? ? ?pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/bin/systemctl status direwolfFeb 05 12:55:09 hampi sudo[1817]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 05 12:55:09 hampi systemd[1]: Configuration file /lib/systemd/system/direwolf.service is marked executable. Please remove executable permission bits. Proc
Feb 05 12:55:09 hampi systemd[1]: Configuration file /lib/systemd/system/direwolf.service is marked world-writable. Please remove world writability permission
Feb 05 12:55:09 hampi sudo[1817]: pam_unix(sudo:session): session closed for user root
Feb 05 12:55:38 hampi sudo[1975]:? ? ? ?pi : TTY=pts/1 ; PWD=/home/pi ; USER=root ; COMMAND=/usr/local/sbin/kissattach /tmp/kisstnc radio
Feb 05 12:55:38 hampi sudo[1975]: pam_unix(sudo:session): session opened for user root by (uid=0)
Feb 05 12:55:38 hampi sudo[1975]: pam_unix(sudo:session): session closed for user root
? |
Re: Direwolf as a service
¿ªÔÆÌåÓýHello Darrell, I have a service I wrote to start direwolf on boot up but I have two issues with this. First it works but does not create the virtual tnc.? if I add the "-p" in the service I get a permission denied when trying to attach the kisstnc. Can you show us the output the of journalctl lines when you get this permission denied error?? I confirmed the other day that Direwolf does NOT need to run as root with the -p option. First is there a way to run direwolf as a service and still get a virtual tnc? Well.. the issue here is that to have a complete LInux AX.25 stack, you need to run a lot more than just Direwolf.? You need to at least run kissattach and kissparms as well to properly configure the stack.? Yes, you can make both of those programs as systemd units and work on getting all the dependencies figured out so that if say Direwolf dies and Systemd restarts it, Systemd will kill the old kissattach process, restart it and also re-run the kissparms command as well. Second is there a way to attach the kisstnc from within the service itself? I personally haven't tried to run all these different Linux ax.25 bring up/down commands via a systemd.? Maybe it's possible but I've always seen that a systemd unit only runs ONE command, not multiple.? There are various websites out there that talk about this though.? Search for "linux ax.25 systemd unit" ?? In this example, this person is not using Direwolf but just using a KISS TNC but regardless, they are running things as ROOT and also is just using systemd to run a script of commands.? I think calling out a script of commands for bringup / down is probably the sane thing to do. [Service] Are you 100% sure that the "pi" user has the "dialout" group permissions as well as anything else required to operate properly?? I would bet this is where your above "permission denied" errors are coming from.? It is worth mentioning that I do believe that "kissattach" must be run as root. --David KI6ZHD |
Re: Can't get audio output
¿ªÔÆÌåÓýHello Ryan, Rob is spot on on things to look at though I would offer some additional troubleshooting tricks.? You are stating you're both not being heard (aka.. an issue with your transmissions) and what you hear is too low (aka.. a receiving problem).? ?? - Take an amplified speaker and connect it to end of the the cable that's supposed to plug into the Direwolf soundcard.? Use alligator clips, etc. to make the connections and this step will help you confirm your cable is wired correctly, etc.? You MUST hear all the packet sounds when say tuned to 144.390 ?? - Take an amplified speaker and connect it to end of the the cable that's supposed to plug into the Baofeng's microphone input.? Use alligator clips, etc. to make the connections and this step will help you confirm your cable is wired correctly, etc.? Now reconfigure Direwolf to send a beacon say every 60 seconds and make sure you hear sounds when it transmits.? It's worth noting that Baofeng radios are renown for incorrect dimensions for the speaker/microphone jacks and you need to shave off some of the plastic on the connectors going into the radio or you'll never have a reliable connection. See the top entry in this FAQ: ??? Overall, Baofeng radios can be made to work but they are renown for being inconsistent from one radio to the next, being very flaky, and downright unreliable.? With a lot of persistence, I bet you'll get it working but many people recommend to spend a little more money and get a better radio for reliable packet operations.? Up to you but I thought I'd put that warning out there. --David KI6ZHD On 02/05/2021 05:18 AM, Rob Giuliano
via groups.io wrote:
|
Direwolf as a service
All, thanks for reading. I am trying to get my club back into packet and maybe then APRS later on.? I am modifying HAMPI because it already has a bunch of great tools for the club to run QTterm and PAT.
First If I start direwolf as a script it runs great with QTtermTCP using AGW. After asking questions last week I was told to add the "-p" to have it create a virtual kiss tnc for PAT I did this and again it all seems to work. I have a service I wrote to start direwolf on boot up but I have two issues with this. First it works but does not create the virtual tnc.? if I add the "-p" in the service I get a permission denied when trying to attach the kisstnc. First is there a way to run direwolf as a service and still get a virtual tnc?? Second is there a way to attach the kisstnc from within the service itself? This is what I have: [Unit]
Description=Direwolf Daemon
Wants=network-online.target
After=sound.target syslog.target network-online.target
?
[Service]
User=pi
ExecStart=/usr/local/bin/direwolf -t 0 -c /home/pi/direwolf.conf -p
StandardOutput=syslog
StandardError=syslog
SyslogIdentifier=direwolf
?
[Install]
WantedBy=multi-user.target |
Re: Can't get audio output
Hello,
Thanks for the input. I am at work now, but I'll go through your steps and recheck everything. I reinstalled all software yesterday.? When my truck APRS signals a beacon, my direwolf is picking it up on the screen. However, when I go to APRS.fi it doesn't show my mobile station listed as a station 'directly heard' by my digitpeter.? In fact, I have never had any stations directly heard by my station ever, despite multiple stations being near me. Is there something I'm missing? Thanks for your help, Ryan KF8IV I |
Re: Can't get audio output
Can't really say what your issue is, but some direction on troubleshooting: 1. Does the radio go into TX when Direwolf wants to transmit (TX LED come ON)?? 2. Check audio levels (especially 'Mute') for the sound card you are using. ??? Can you hear any audio on another radio on Direwolf TX? 3. Wiring. ??? a) if no TX LED, check the PTT method and wiring.? ??????? HTs can be tricky depending on the PTT circuit required. ??? b) If you don't hear your signal in another receiver, but TX LED does come on, ??????? Audio levels may be too low. ??????? Audio path wiring. Robert Giuliano
On Friday, February 5, 2021, 7:40:43 AM EST, Ryan Hartnett <ryan@...> wrote:
Hello. I have direwolf running on a Raspberry Pi 4 with a UV5R and a magmount antenna. I have gotten direwolf and xastir running, however the output on direwolf after it loads is 0(0/0) or 1(0/0). When I check my digitpeter on the APRS website, nobody is hearing me (even when I have my APRS mobile in the driveway 20 ft away). I have messed with the soundcard, traded out radios, tinkered with the mixer, etc. I have tried reinstalling and following other peoples videos/websites for installation without success. Anyone happen to know what my issue may be??
|
Can't get audio output
Hello. I have direwolf running on a Raspberry Pi 4 with a UV5R and a magmount antenna. I have gotten direwolf and xastir running, however the output on direwolf after it loads is 0(0/0) or 1(0/0). When I check my digitpeter on the APRS website, nobody is hearing me (even when I have my APRS mobile in the driveway 20 ft away). I have messed with the soundcard, traded out radios, tinkered with the mixer, etc. I have tried reinstalling and following other peoples videos/websites for installation without success. Anyone happen to know what my issue may be??
|
Re: Could not open audio device
I think I found the issue although I don't know how to fix it ... I'm not that good at linux commands.
I changed directory to direwolf10-28-10 ? ?which I think is the day I downloaded the v1.6 from there I ran direwolf and it started. Looks like I need to fix the program name on / How? |
Re: Could not open audio device
Also did you try starting Direwolf with sudo?? If it works with sudo, it's a permissions issue.
On Monday, February 1, 2021, 5:54:21 PM EST, KP3FT via groups.io <kp3ft@...> wrote:
What does aplay -l show?? Is there anything starting up on boot in the background that is using the card? Might also be a permissions thing, but maybe I'm thinking of only the CM108 PTT permissions.
On Monday, February 1, 2021, 5:39:57 PM EST, Keith Kaiser <wa0tjt@...> wrote:
I've rebooted this Raspberry Pi 15 times or more working on this so I don't think another instance of Direwolf is running. This is v5.4.79-v7+ Which translates to Buster Version 10 Completely updated and upgraded. |
Re: Could not open audio device
What does aplay -l show?? Is there anything starting up on boot in the background that is using the card? Might also be a permissions thing, but maybe I'm thinking of only the CM108 PTT permissions.
On Monday, February 1, 2021, 5:39:57 PM EST, Keith Kaiser <wa0tjt@...> wrote:
I've rebooted this Raspberry Pi 15 times or more working on this so I don't think another instance of Direwolf is running. This is v5.4.79-v7+ Which translates to Buster Version 10 Completely updated and upgraded. |
Re: Could not open audio device
It could be a "hidden" instance of Direwolf running in the background at the same time; you'll get that error.? Also, what OS are you using?
On Monday, February 1, 2021, 4:37:05 PM EST, Keith Kaiser <wa0tjt@...> wrote:
I've been running Direwolf for years. Recently I upgraded to 1.6 and can not get it to run any longer. I'm using the same audio device as always, and because I have 3 of them I've tried all three. I also tried a iMic from years passed which used to work too. But regardless of the audio device I get the error. My command to run is: direwolf -c direwolf-NEW.conf -t O Which results with: Dire Wolf Version 1.6 Includes optional support for: hamlib cm108-ptt Reading config file direwolf-NEW.conf Audio device for both receive and transmit: plight:1,0 ?(channel 0?) Could not open audio device plight:1,0 for input No such file or directory Pointless to continue without audio device. I also tried using the default by just running; direwolf Which results in exactly the same response. Has anyone else run into this issue, have a way to fix it? |
to navigate to use esc to dismiss