I'm seeing an odd problem, but it might be difficult to describe. I have a Raspberry Pi Zero running the latest software and DireWolf 1.4.E. ?But it has also done this with version 1.3. I am running this as a digipeater only without any internet.
When the transmitter is turned on (PTT from GPIO Pin) normally the audio/data is sent almost instantly.
Sometimes there is a long delay between PTT and sending any audio. ?This long delay is sometimes 5 seconds, and I've even heard close to 10 seconds of carrier only, no audio, then the data burst. You might think that it is waiting for the frequency to be clear, but it has already turned on the PTT and is transmitting, just no audio or data yet.
I'm sure this isn't enough information yet to figure this out, so where do I start looking?
Thanks, Arnold KQ6DI
|
Re: Serial PTT not functioning after exit
As far as it concerns permissions, everything seems to be fine. Something else is grabbing your serial port as soon as direwolf exits. After stopping direwolf, try: $ lsof | grep PTT and $ lsof | grep ttyUSB0 On ¦¤¦Å¦Ô, 2017-02-27 at 22:54 +0000, overrocking@... [direwolf_packet] wrote:
Thanks for the reply,
here is the results:
kd9dcs@bluetracker:/dev $ ls -al /dev/ttyUSB0
crw-rw---- 1 root dialout 188, 0 Feb 27 15:26 /dev/ttyUSB0
as an added bonus here is the udev rule I wrote to create the link:
ATTRS{product}=="CP2104 USB to UART Bridge Controller", SYMLINK
+="PTT", GROUP="dialout", MODE="0660"
Tim ...
|
Re: Serial PTT not functioning after exit
Hi David, thanks for your reply.
I've been exploring the sudo issue for a few days now and here's
what I've found.
- Works perfectly on the default pi user on Rpi. This is because
pi is set up for sudo access without password. Can be verified by
examining the sudoers file with visudo.
- Direwolf calls chmod go+rw on the gpio direction and value
irrespective of whether the permissions are set correctly. Can be
verified by examining the system logs -? # journalctl | grep gpio.
All my user permissions are set up for gpio as you recommended
below. I can create gpio devices, change direction and write to
value as a normal user with gpio group membership.
gpio devices are created by udev rules with root:gpio 0770
permissions. This is set in /etc/udev/rules.d/99-com.rules. Also
worth noting that when a gpio device is created under
/sys/class/gpio it's actually a symlink to
/sys/device/platform/soc//3f200000.gpio/gpio.
So Direwolf appears to do some checks for permissions in ptt.c. I've
not quite figured that part out yet but for whatever reason it still
decides it needs elevated permissions to change the gpio direction
and value even if it is correct. I've sent a bug report/query to
John regarding this.
That aside, the decoding performance on HF is fantastic! I've had a
Windows build running with 5@30 300 modems and it's decoding stuff I
can barely hear on 10.1476MHz.
73
Nick G4IRX
On 28/02/2017 05:05, David Ranch
dranch@... [direwolf_packet] wrote:
toggle quoted message
Show quoted text
?
As for GPIO access, the running user needs
to be apart of the "gpio" group.? Quick example is:
--
??????? b. Add this new user into the following
unix groups:
????????????? - "audio" (allow users to access
the soundcard)
????????????? - "dialout" (allow serial port
access - if needed)
????????????? - "gpio" (allow access to the
GPIO pins)
????????????? - "sudo" (allow root access)
????????????? - "video" group (allow diagnostic
permissions to the GPU)
???????????????? sudo usermod -G
audio,dialout,gpio,sudo,video
--
As far as killing direwolf, control-c should be fine as
well as using "kill" but don't use the -HUP signal.?
When you kill Direwolf and the serial port is no longer
available, try running "ps aux | grep modem" and tell us
if NetworkManager's "modem-manager" is running.
--David
KI6ZHD
On 02/27/2017 09:37 AM, 'Nick
B.' nick@...
[direwolf_packet] wrote:
?
Hope you don't mind if I join in with this Tim as I'm
watching this with interest. I have similar problems
trying to get GPIO PTT and DCD working with the
correct permissions. Despite being able to write to
GPIO as my normal user, Direwolf always wants a sudo
password.
I haven't tried USB serial PTT yet but I may well do
and see if I get a similar result to you.
Nick.
?
I'm always game for learning more, thanks for
diving in with some help.?
Here are the results of the commands:
kd9dcs@bluetracker:~
$ who
kd9dcs ? :0 ? ? ? ?
? 2017-02-26 17:51 (:0)
kd9dcs ? pts/0 ? ? ?
?2017-02-27 05:34 (192.168.2.10)
kd9dcs@bluetracker:~ $ groups
pi adm dialout cdrom sudo audio video
plugdev games users input netdev gpio i2c
spi
kd9dcs@bluetracker:~ $ ls -al /dev/PTT
lrwxrwxrwx 1 root root 7 Feb 26 17:51
/dev/PTT -> ttyUSB0
Thanks again for looking at this
Tim ...
|
Hello all,?
I've been using DireWolf for quite some time now and I'm really happy with it. The decoding performance is amazing and the program is pretty stable. Uptime without restart at all before the SD-card broke was pretty close to a year.
I've used DireWolf as a TNC and digipeater, while APRX had fun taking care of the i-gating.
After a sudden death of a micro SD-card in my Raspberry Pi 3, I had to set it all up again and thought I should give DireWolf all the honors being i-gate and all.
There are some things I want to RF-gate, messages (of course) and objects within a certain area + my own TCPIP-devices.
The issue, as far as I can see, is that I can only select one RF path for all packets I gate from IS to RF (IGTXVIA). Is there a way I can set one path for each line of filters (or something similar)?
I'd like messages to be sent as WIDE2-1, objects (originating from IS) to a specific digipeater and my own budlist calls to WIDE2-2. This are just examples, but it's there to show what I mean.
If it's not possible; consider it a thing to put on the wishlist :)
Thanks in advance.
73 de LA1HSA, Asbj?rn
|
Re: Serial PTT not functioning after exit
As for GPIO access, the running user needs to be
apart of the "gpio" group.? Quick example is:
--
??????? b. Add this new user into the following unix
groups:
????????????? - "audio" (allow users to access the
soundcard)
????????????? - "dialout" (allow serial port access - if
needed)
????????????? - "gpio" (allow access to the GPIO pins)
????????????? - "sudo" (allow root access)
????????????? - "video" group (allow diagnostic
permissions to the GPU)
???????????????? sudo usermod -G
audio,dialout,gpio,sudo,video
--
As far as killing direwolf, control-c should be fine as well as
using "kill" but don't use the -HUP signal.?
When you kill Direwolf and the serial port is no longer available,
try running "ps aux | grep modem" and tell us if NetworkManager's
"modem-manager" is running.
--David
KI6ZHD
On 02/27/2017 09:37 AM, 'Nick B.'
nick@... [direwolf_packet] wrote:
toggle quoted message
Show quoted text
?
Hope you don't mind if I join in with this Tim as I'm
watching this with interest. I have similar problems
trying to get GPIO PTT and DCD working with the correct
permissions. Despite being able to write to GPIO as my
normal user, Direwolf always wants a sudo password.
I haven't tried USB serial PTT yet but I may well do and
see if I get a similar result to you.
Nick.
?
I'm always game for learning more, thanks for diving
in with some help.?
Here are the results of the commands:
kd9dcs@bluetracker:~ $
who
kd9dcs ? :0 ? ? ? ? ?
2017-02-26 17:51 (:0)
kd9dcs ? pts/0 ? ? ?
?2017-02-27 05:34 (192.168.2.10)
kd9dcs@bluetracker:~ $ groups
pi adm dialout cdrom sudo audio video plugdev
games users input netdev gpio i2c spi
kd9dcs@bluetracker:~ $ ls -al /dev/PTT
lrwxrwxrwx 1 root root 7 Feb 26 17:51
/dev/PTT -> ttyUSB0
Thanks again for looking at this
Tim ...
|
Re: Serial PTT not functioning after exit
Thanks for the reply,?
here is the results:
kd9dcs@bluetracker:/dev $ ls -al /dev/ttyUSB0? crw-rw---- 1 root dialout 188, 0 Feb 27 15:26 /dev/ttyUSB0
as an added bonus here is the udev rule I wrote to create the link:
ATTRS{product}=="CP2104 USB to UART Bridge Controller", SYMLINK+="PTT", GROUP="dialout", MODE="0660"
Tim ...
|
Re: Serial PTT not functioning after exit
OK lets see the permissions of ttyUSB0 $ ls -al /dev/ttyUSB0 On ¦¤¦Å¦Ô, 2017-02-27 at 17:37 +0000, 'Nick B.' nick@... [direwolf_packet] wrote:
Hope you don't mind if I join in with this Tim as I'm watching this
with interest. I have similar problems trying to get GPIO PTT and DCD
working with the correct permissions. Despite being able to write to
GPIO as my normal user, Direwolf always wants a sudo password.
I haven't tried USB serial PTT yet but I may well do and see if I get
a similar result to you.
Nick.
On 27/02/2017 11:41, overrocking@... [direwolf_packet] wrote:
I'm always game for learning more, thanks for diving in with some
help.
Here are the results of the commands:
kd9dcs@bluetracker:~ $ who
kd9dcs :0 2017-02-26 17:51 (:0)
kd9dcs pts/0 2017-02-27 05:34 (192.168.2.10)
kd9dcs@bluetracker:~ $ groups
pi adm dialout cdrom sudo audio video plugdev games users input
netdev gpio i2c spi
kd9dcs@bluetracker:~ $ ls -al /dev/PTT
lrwxrwxrwx 1 root root 7 Feb 26 17:51 /dev/PTT -> ttyUSB0
Thanks again for looking at this
Tim ...
-- ¦ª¦Å¦Õ?¦Ë¦Á? ¦¡¦Ð?¦Ò¦Ó¦Ï¦Ë¦Ï? - SV1LJJ ¦Ó¦Ç¦Ë: +30 6979 976 039 Echolink id: 309275 skype: apostolis.kef sip:apkefalas@... PGP: 0xA3C19DA0
|
Re: Digipeater hearing & repeating itself
This is exactly what I did (with it's own callsign). ? I guess I was hoping that DireWolf would add itself into the list where it wouldn't repeat that exact same packet for the 30 seconds. ?(Can't think of the exact name of that.) ?
I was think that maybe I had missed some setting to fix it without an explicit filter.
Thanks, Arnold KQ6DI
From: "Jean-Francois f1evm@... [direwolf_packet]" To: "direwolf packet" Sent: Monday, February 27, 2017 10:11:23 AM Subject: Re: [direwolf_packet] Digipeater hearing & repeating itself
?
Hi Arnold,
I had the same issue on my digipeater (still in test on a CHIP). I got a solution with this filter :
FILTER 0 0 ! b/F1EVM
You need to change F1EVM by the callsign of the digipeater.
Best regards.
? Jean-Fran?ois F1EVM
IN98NC?- d¨¦pt 53 - La Mayenne
Site WEB : http://f1evm.fr Le Dimanche 26 f¨¦vrier 2017 2h49, "kq6di@... [direwolf_packet]"
?
My digipeater is hearing its own transmissions, and because it is sending with a path of WIDE1-1, and will digipeat WIDE1-1, it digipeats itself. So how do I make it so it knows it already sent its own message?
Arnold KQ6DI
|
Re: Digipeater hearing & repeating itself
Hi Arnold,
I had the same issue on my digipeater (still in test on a CHIP). I got a solution with this filter :
FILTER 0 0 ! b/F1EVM
You need to change F1EVM by the callsign of the digipeater.
Best regards. ? Jean-Fran?ois F1EVM
IN98NC?- d¨¦pt 53 - La Mayenne
Site WEB : http://f1evm.fr
Le Dimanche 26 f¨¦vrier 2017 2h49, "kq6di@... [direwolf_packet]" a ¨¦crit :
?
My digipeater is hearing its own transmissions, and because it is sending with a path of WIDE1-1, and will digipeat WIDE1-1, it digipeats itself. So how do I make it so it knows it already sent its own message?
Arnold KQ6DI
|
Re: Serial PTT not functioning after exit
Hope you don't mind if I join in with this Tim as I'm watching
this with interest. I have similar problems trying to get GPIO PTT
and DCD working with the correct permissions. Despite being able
to write to GPIO as my normal user, Direwolf always wants a sudo
password.
I haven't tried USB serial PTT yet but I may well do and see if I
get a similar result to you.
Nick.
toggle quoted message
Show quoted text
?
I'm always game for learning more, thanks for diving in
with some help.?
Here are the results of the commands:
kd9dcs@bluetracker:~ $ who
kd9dcs ? :0 ? ? ? ? ?
2017-02-26 17:51 (:0)
kd9dcs ? pts/0 ? ? ?
?2017-02-27 05:34 (192.168.2.10)
kd9dcs@bluetracker:~ $ groups
pi adm dialout cdrom sudo audio video plugdev
games users input netdev gpio i2c spi
kd9dcs@bluetracker:~ $ ls -al /dev/PTT
lrwxrwxrwx 1 root root 7 Feb 26 17:51 /dev/PTT
-> ttyUSB0
Thanks again for looking at this
Tim ...
|
Re: Audio input device 0 error: Input/output error
John,?
I have run into a similar error.? What I found was that the Raspberry Pi processor couldn't keep up with the audio demands at the higher USB speeds. This resulted in dropped USB packets that caused the Rpi to lock up.?
The solution was to force the Rpi to the lower USB speed by adding a parameter to the cmdline.txt?
sudo
nano /boot/cmdline.txt
and
adding dwc_otg.speed=1 to the end of the text.
?However, this solution is not without its side effects. Some keyboards and mice refuse to operate at this speed. This is not an issue if you are connecting to the Pi via ssh or VNC.
If there is a better solution, I am all ears.?
?
|
Re: Serial PTT not functioning after exit
I'm always game for learning more, thanks for diving in with some help.? Here are the results of the commands: kd9dcs@bluetracker:~ $ who kd9dcs ? :0 ? ? ? ? ? 2017-02-26 17:51 (:0) kd9dcs ? pts/0 ? ? ? ?2017-02-27 05:34 (192.168.2.10)
kd9dcs@bluetracker:~ $ groups pi adm dialout cdrom sudo audio video plugdev games users input netdev gpio i2c spi
kd9dcs@bluetracker:~ $ ls -al /dev/PTT lrwxrwxrwx 1 root root 7 Feb 26 17:51 /dev/PTT -> ttyUSB0
Thanks again for looking at this
Tim ...
|
Re: Serial PTT not functioning after exit
Hello Tim, This is a permission problem and not a direwolf exiting problem. give us the output of the below commands: $ who $ groups $ ls -al /dev/PTT 73 de SV1LJJ On ¦ª¦Ô¦Ñ, 2017-02-26 at 15:15 +0000, overrocking@... [direwolf_packet] wrote:
Good morning guys, Tim (Kd9DBG) with the high school telemetry car
project,
Here is my current question...
How does one "cleanly" shutdown Direwolf?
Here is the behavior after launching direwolf on a Raspberry Pi with
the command
direwolf -c dw-tracker.conf
Direwolf functions flawlessly. The serial PTT functions without issue.
Shutting down direwolf with either a:
[Ctrl] + c
or
kill -HUP (direwolf process number)
both stop direwolf as expected. However when restarting direwolf with
the same command as before I get the following error message:
ERROR can't open device /dev/PTT for channel 0 PTT control.
Device or resource busy
the error message disappears when restarting direwolf with sudo.
There has to be a better solution than elevating to root.
What are your thoughts?
Tim ...
|
Serial PTT not functioning after exit
Good morning guys, Tim (Kd9DBG) with the high school telemetry car project,?
Here is my current question...
?How does one "cleanly" shutdown Direwolf? Here is the behavior after launching direwolf on a Raspberry Pi with the command
direwolf -c dw-tracker.conf
Direwolf functions flawlessly. The serial PTT functions without issue.
Shutting down direwolf with either a:
[Ctrl] + c or? kill -HUP (direwolf process number)
both stop direwolf as expected. However when restarting direwolf with the same command as before I get the following error message:
ERROR can't open device /dev/PTT for channel 0 PTT control. Device or resource busy
the error message disappears when restarting direwolf with sudo.
There has to be a better solution than elevating to root.?
What are your thoughts?
Tim ...
|
Re: Digipeater hearing & repeating itself
Attached is an example. ?I have another receiver and another computer running DireWolf as well. ?The receiver only has a small HT antenna so it can only hear what comes out of this digipeater. ?I thought I was hearing doubles... Arnold KQ6DI
From: "kq6di@... [direwolf_packet]" To: "direwolf packet" <direwolf_packet@...> Sent: Saturday, February 25, 2017 5:49:44 PM Subject: [direwolf_packet] Digipeater hearing & repeating itself
?My digipeater is hearing its own transmissions, and because it is sending with a path of WIDE1-1, and will digipeat WIDE1-1, it digipeats itself. So how do I make it so it knows it already sent its own message?
Arnold KQ6DI
|
Digipeater hearing & repeating itself
My digipeater is hearing its own transmissions, and because it is sending with a path of WIDE1-1, and will digipeat WIDE1-1, it digipeats itself. So how do I make it so it knows it already sent its own message?
Arnold KQ6DI
|
Re: IGFILTER in Rx only iGate
IGFILTER works on V1.4 Windows 7 , don't, like i said , V1.4 linux on Ubuntu 14.4
|
Re: Direwolf APRS I-Gate over Cellular
Thanks for the info. I'd like to see if I can get it to work with a Project Fi data-only sim card, which costs a penny per megabyte, with no ongoing monthly charge. It's cheap enough to try it for a little while and tinker with the filters if necessary.
For the hotspot hardware, did you find any special needs from the direwolf or pi perspective, or should I be able to use anything that works with the sim card?
On Fri, Feb 24, 2017 at 10:13 AM, Bryan Campbell bbc@... [direwolf_packet] <direwolf_packet@...> wrote:
?
Initially used it in a mobile application using the APRSDroid for
the GPS tracker function.? APRSDroid can also send short, text
like, messages.
APRSDroid talks to Direwolf.? Direwolf talks to APRSDroid via
AGWPE port or TCP connection.? Have used both.? Other software can
also.
But, as an I-Gate or Digi, it was left sitting still for weeks
without any issues.? Direwolf AGWPE port will shut down if not
used regularly/often (documented intended behavior).
As for bandwidth, usual and customary bandwidth for AX.25 is
1200-9600 baud or 13-104 MBytes per day for a full link.? That is
389-3111 MBytes per month for a full link.
Depending upon where you live, and the number of APRS devices
transmitting over RF that you can hear and for which
Direwolf/APRSC will determine it should I-Gate, you might have
10-20% duty cycle at peak.? So, at the very worst, I would expect
that you would see less than half a GB per month.? But, you can
control that directly by having Direwolf use APRSC locally
installed and just tell APRSC to ignore traffic outside a
1,5,10,20 mile radius.? You can also tell APRSC to just ignore
inbound from the Internet.?
Lots of options.? And, yes, using a T-Mobile GSM SIM in a Wifi
hotspot is the least expensive option for this application.? There
are add on boards for the Pi that allow a radio/SIM to be added to
the Pi directly.? But, they are much more expensive and are not as
extensible a solution.? A GSM Wifi hotspot could service many
devices simultaneously.?? For example, APRSDroid can talk directly
to APRS-IS over the GSM Wifi link.? So, you could augment your cell
data coverage with the Wifi hotspot.
For Advanced Users . . . Also, you can insert a router with queuing
between the Wifi hotspot and all your devices that would allow you
to control your bandwidth.? I recommend the Mikrotik hAP Lite.? It
is inexpensive, small, USB powered and has a ton of features . . .
including queuing.? Also, if you want to get a little more
complicated with your setup, you can add a cellular connection
directly to a little more expensive Mikrotik hAP (non Lite) router.?
But, this is outside the scope of this list.
.
KD0GYL
.
On 2/24/17 6:37 AM, Jared Yates
junk@... [direwolf_packet] wrote:
?
Thanks for the help. In this application the
pi will be stationary. So you are using the pi's wifi to
talk to a hotspot, and have your sim card in the hotspot?
Are you using APRS Droid to work with the pi when you need
to, or is the droid there all the time?? And by not much
data, do you mean something like 10mb, 100mb, 1gb, etc?
|
I am currently using APRX to convert DPRS from D-STAR radios to APRS and forward it to APRSIS. Specifically, a program called D-RATS parses the position data from D-STAR radios and presents it to TCP port 9500. From there, APRX converts it and sends it to APRSIS. I am looking for a similar function in Direwolf as it would simplify my station. I have read through the User's Guide and have not found any mention of it. Have I missed it? Is that something that could added in a future release?
Patrick (N3TSZ)
|
Audio input device 0 error: Input/output error
I am experimenting with setting up a "two-way" IGate on a Raspberry Pi 3 running Jessie. The Direwolf version is the current one, downloaded form GitHub. I keep getting the error show in the subject line that eventually results in Direwolf crashing. This occurs after about an hour or so of successfully processing packets at a modest pace from traffic on 144.390 MHz. I saw some mention of this in this group earlier on but I am not sure how this was resolved. From the direwolf output console I see: [ig>tx] WB2UTI>APWW10,TCPIP*,qAC,T2MSSOURI:;TVRH ? ? *241542z2857.01N/08157.51WhThe? Villages Regional Hospital (WB2UTI) !H4OH! Tx IGate: Already transmitted maximum of 12 packets in 5 minutes.
Audio input device 0 error: Input/output error
this will occur multiple times until giving up with:
[ig>tx] W4MCO>APWW10,TCPIP*,qAC,T2FRANCE::BLN0 ? ? :Ready for check ins for the? OCARES Net
Tx IGate: Already transmitted maximum of 12 packets in 5 minutes. Audio input device 0 error: Input/output error Terminating after audio input failure.
from dmesg I see:
[ 7276.035136] usb 1-1.2: 1:1: cannot set freq 44100 to ep 0x1 [ 7281.075209] usb 1-1.2: 1:1: cannot set freq 44100 to ep 0x1 [ 7286.115241] usb 1-1.2: 1:1: cannot set freq 44100 to ep 0x1 [ 7286.660299] Transfer to device 4 endpoint 0x2 frame 594 failed - FIQ timed out.?
Data may have been lost.
This (bad) behavior has been consistent across multiple power supplies ( the usual diagnosis for all RPi problems....) and multiple usb audio devices ( SYBA usb soundcard recommended in the Direwolf docs, and a Signalink USB) Both devices work ?flawlessly under Win 7, BTW. The RPi3 has only 1 device (the usb soundcard) connected directly (no usb hub).
Not sure what to do next about this... 73, John, NX2I
|
Nick G4IRX
Patrick Connor