Re: Serial PTT not functioning after exit
On 05/03/2017 19:48, wb2osz@...
[direwolf_packet] wrote:
?
Nick B. wrote:
> ? Despite
being able to write to GPIO as my normal user,
> ? Direwolf
always wants a sudo password.
Commit?58c2707f7d65b5b074b5e67e00c06a50fb968349, on the
'dev' branch, should fix this.
Raspbian Jessie has a new 'gpio' group which was not in
Wheezy.
The logic for getting access to the GPIO pins has been
rewritten to take advantage of that.
Just pulled and rebuilt from dev branch. That works for me (user is
a gpio group member). Thanks!
|
Re: Digipeater hearing & repeating itself
This has been fixed. 67b11d4922ce538e55ab7853c1a449ad4de6ec83 in the 'dev' branch.
Don't digipeat packets when the source is my call.
|
Re: Serial PTT not functioning after exit
Nick B. wrote:
> ? Despite being able to write to GPIO as my normal user, > ? Direwolf always wants a sudo password.
Commit?58c2707f7d65b5b074b5e67e00c06a50fb968349, on the 'dev' branch, should fix this.
Raspbian Jessie has a new 'gpio' group which was not in Wheezy. The logic for getting access to the GPIO pins has been rewritten to take advantage of that.
?
|
Re: Audio input device 0 error: Input/output error
Hello John,
?
Ok.. and it's fully patched:
??? apt-get update
??? apt-get upgrade
??? apt-get dist-upgrade
??? rpi-update
??? reboot
?? - Are you running in
command line only mode or running
Xwindows?
Command line
Ok.. and how is your Syba sound device connected to your Raspberry
Pi?? Directly connected (recommended) or via an attached USB hub
(not recommended)
--David
KI6ZHD
|
Re: Audio input device 0 error: Input/output error
Dave, Please see responses below.? 73, John, NX2I
V3
Raspbian Jessie Basically nothing.
Command line
|
Re: Audio input device 0 error: Input/output error
Hello John,
I've been running Direwolf v1.4 on both a Raspberry Pi v2 and v3
with Syba USB devices with good luck for months.? A few questions
if I may:
?? - Are you running on a Rpi v1, v2, or
v3???
?? - What Linux distro and version of distro are you running?
?? - What else is your Rpi running along side Direwolf?
?? - Are you running in command line only mode or running Xwindows?
--David
KI6ZHD
On 03/01/2017 01:26 PM, John Spoonhower
jpspoonhower@... [direwolf_packet] wrote:
toggle quoted message
Show quoted text
?
Thanks Tim.
I have been testing this solution for the
last couple days. Bottom line.....
I still see the same error.
Thanks and 73,
John NX2I
|
Re: Audio input device 0 error: Input/output error
Thanks Tim. I have been testing this solution for the last couple days. Bottom line..... I still see the same error. Thanks and 73, John NX2I
On Feb 27, 2017 9:08 AM, " overrocking@... [direwolf_packet]" < direwolf_packet@...> wrote:
?
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: Audio input device 0 error: Input/output error
Hi,
It may also be worth reducing checking the CPU load by running
top or htop in another terminal. Then reduce the sampling rate by
running with e.g. "direwolf -r 11025" . This made a difference for
me on slower single-core processors (A10, Pi Zero). It could also
be an issue with the soundcard itself.
I would agree that dwg_otg=1 can break usb keyboards and mice in my
experience. It did, however solve some issues I was having with SD
card readers when backing moving file systems from SD ->
microSD...
Nick.
toggle quoted message
Show quoted text
?
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.?
?
|
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 ...
|
Nick G4IRX