Has anyone tried running Direwolf on Pine64? Wondering I should move to Pi3 or Pine64 instead if it works.
Thanks. 73 de VR2ZDX
|
I believe I parsed this from the O.P.:
73,
Jim A.
|
Re: DireWolf 1.3 Digipeating bad packets
Everyone with a TX-capable IGate running DireWolf should use this filter: FILTER IG 0 t/m | ( ! d/TCPIP/TCPXX )
for each audio channel until, this gets sorted out. The third-party packets with TCPIP and the q-construct in the PATH should not be transmitted on RF.
respectfully,
Jim A.
---In direwolf_packet@..., <petitnoel47@...> wrote : Other stations are picking up back packets from my station (WB0VGI-7) and KB0GTF-1 both running DireWolf 1.3.?
? I run an APRS RX-iGate (AE0RF-10) in Minneapolis (occasionally) and noticed this:
Nov? 7 21:05:06 spmn-cdma-1 pymultimonaprs: rejected: WB0VGI-7>APDW12,N0HOY-10*,WIDE1*,qAR,AE0RF-10:}K0JDD-1>APRX28,TCPIP,WB0VGI-7*:T#309,22.6,0.0,107.0,17.0,0.0,00000000 Nov? 7 21:06:47 spmn-cdma-1 pymultimonaprs: rejected: WB0VGI-7>APDW12,W0YC-5*,qAR,AE0RF-10:}N0DZQ-10>APWW10,TCPIP,WB0VGI-7*:;145.230MN*080306z4607.62N/09230.58WrKE0ACL/R 145.230- T146.2 (Pine County ARES) Nov? 7 21:06:49 spmn-cdma-1 pymultimonaprs: rejected: WB0VGI-7>APDW12,N0HOY-10*,WIDE1*,qAR,AE0RF-10:}N0DZQ-10>APWW10,TCPIP,WB0VGI-7*:;145.230MN*080306z4607.62N/09230.58WrKE0ACL/R 145.230- T146.2 (Pine County ARES) Nov? 7 21:07:08 spmn-cdma-1 pymultimonaprs: rejected: KB0GTF-1>APDW13,W0YC-5*,qAR,AE0RF-10:}K0JDD-1>APRX28,TCPIP,KB0GTF-1*::K0JDD-1? :PARM.Avg 10m,Avg 10m,RxPkts,IGateDropRx,TxPkts Nov? 7 21:07:51 spmn-cdma-1 pymultimonaprs: rejected: WB0VGI-7>APDW12,W0YC-5*,qAR,AE0RF-10:}N0DZQ-10>APWW10,TCPIP,WB0VGI-7*:;146.745MN*080307z4543.27N/09341.92WrN0GOI/R 146.745- T107.2 (Skywarn) Nov? 7 21:09:13 spmn-cdma-1 pymultimonaprs: rejected: WB0VGI-7>APDW12,W0YC-5*,qAR,AE0RF-10:}N0AGI-5>APMI06,TCPIP,WB0VGI-7*:=4455.11NJ09328.11WnAPRS Digi+iGate. . John 3:16
Nov? 7 21:09:14 spmn-cdma-1 pymultimonaprs: rejected: WB0VGI-7>APDW12,N0HOY-10*,WIDE1*,qAR,AE0RF-10:}N0AGI-5>APMI06,TCPIP,WB0VGI-7*:=4455.11NJ09328.11WnAPRS Digi+iGate. . John 3:16
Note that it appears that digipeating packets are mergers of more than one packet. I suspect some buffer in DireWolf 1.3 is not cleared before a new packet arrives. The result is that the transmission includes pieces of more than one incoming packet.?
Any ideas where to look in the code??
Noel WB0VGI-7 Harris, MN
|
?
I'm getting an invalid command 12 from the client
application. What does that mean?
What is the name of the "the client application" here ?
73,
Dana K6JQ
?
On 11/26/2016 10:35 AM,
Seth Stevenson rcflyer30@...
[direwolf_packet] wrote:
?
Also checking, you're using the correct cable and
jumper plug for the
Signalink USB?
If you got the cable and jumper plug from
Tigertronics, it's
probably a plug-and-play operation (note that you have
to install
the jumper plug inside the Signalink, unless it came
from the
factory with it installed, you have to figure that out
yourself).
With the correct cable, jumper plug and DireWolf
UserGuide, it's
pretty much plug-and-play.
1. Install "Alinco RJ-45" jumper plug in the
Signalink.
2. Plug the Signalink cable into the radio and the
Signalink.
3. Plug the Signalink USB into your Windows machine
(wait for new device
??? config to complete).
4. See "9.1.2 Audio Device selection - Windows" for
the rest.
73,
Dana? K6JQ
|
I'm getting an invalid command 12 from the client application. What does that mean?
toggle quoted message
Show quoted text
On Nov 26, 2016, at 2:01 PM, Dana Myers dana.myers@... [direwolf_packet] < direwolf_packet@...> wrote:
?
On 11/26/2016 10:35 AM, Seth Stevenson
rcflyer30@... [direwolf_packet] wrote:
?
Also checking, you're using the correct cable and jumper plug for
the
Signalink USB?
If you got the cable and jumper plug from Tigertronics, it's
probably a plug-and-play operation (note that you have to install
the jumper plug inside the Signalink, unless it came from the
factory with it installed, you have to figure that out yourself).
With the correct cable, jumper plug and DireWolf UserGuide, it's
pretty much plug-and-play.
1. Install "Alinco RJ-45" jumper plug in the Signalink.
2. Plug the Signalink cable into the radio and the Signalink.
3. Plug the Signalink USB into your Windows machine (wait for new
device
??? config to complete).
4. See "9.1.2 Audio Device selection - Windows" for the rest.
73,
Dana? K6JQ
|
I don't even know if this is a stupid question...
What flavor of the C programming language is Dire Wolf written in?
Thanks in advance
Jim A.
|
On 11/26/2016 10:35 AM, Seth Stevenson
rcflyer30@... [direwolf_packet] wrote:
?
Also checking, you're using the correct cable and jumper plug for
the
Signalink USB?
If you got the cable and jumper plug from Tigertronics, it's
probably a plug-and-play operation (note that you have to install
the jumper plug inside the Signalink, unless it came from the
factory with it installed, you have to figure that out yourself).
With the correct cable, jumper plug and DireWolf UserGuide, it's
pretty much plug-and-play.
1. Install "Alinco RJ-45" jumper plug in the Signalink.
2. Plug the Signalink cable into the radio and the Signalink.
3. Plug the Signalink USB into your Windows machine (wait for new
device
??? config to complete).
4. See "9.1.2 Audio Device selection - Windows" for the rest.
73,
Dana? K6JQ
|
On 11/26/2016 10:35 AM, Seth Stevenson
rcflyer30@... [direwolf_packet] wrote:
?
Are you using the DireWolf UserGuide, too? :-) It's in the same
download as DireWolf.
Section "9.1.2 Audio Device selection - Windows" is surely what you
want.
I just plugged the Signalink USB in and ran DW 1.3.1 and it works
like
the documentation describes.
Signalink uses VOX for PTT - note that if you turn the output level
down too
much on Windows, the VOX PTT won't activate, you probably need to
run about
20% volume or so, possibly a bit higher, then set the audio level
with the TX knob
on the Signalink. For my configuration using 6-pin mini-DIN, the
setting is rather
low and I'm going to customize the Signalink config header with a
10:1 pad.
73,
Dana? K6JQ
On Nov 26, 2016 1:23 PM, "Dana
Myers dana.myers@...
[direwolf_packet]" < direwolf_packet@...>
wrote:
?
On
11/26/2016 7:24 AM, Jim Alles kb3tbx@...
[direwolf_packet] wrote:
?
Oh.
USB or something else - the specific
model number would be helpful.
I just set up the Tigertronics Signalink USB for
DW myself, under
Ubuntu on a RPi2. There's documentation for this
in the "Raspberry Pi TNC"
document. If you have no other sound devices
added to the system, it comes
down to uncommenting the line for ADEVICE 1 and
off to the races you go,
but please have a look at the DW documentation.
73,
Dana? K6JQ
P.S. The Signalink USB shows up as a TI PCM2904
USB audio codec.
There
is this, for USB:
**The Linux operating system is not officially supported by our chipset manufacturer,
or Tigertronics. We will do our best to help you get your SignaLink working in
Linux if you call for Tech Support (click for some customer provided information
on running the SignaLink USB in Linux), but please understand that we do not run this
OS ourselves so support for it will be very limited. If you are not familiar with
installing and configuring software/hardware in Linux, then we strongly suggest
that you use a different OS with your SignaLink.
You are going to need to identify how the sound card shows up in /dev/
I can't tell how PTT shows up in their serial port mapping, either.
.ja.
|
toggle quoted message
Show quoted text
?
On 11/26/2016 7:24 AM, Jim Alles
kb3tbx@... [direwolf_packet] wrote:
?
Oh. USB or something
else - the specific model number would be helpful.
I just set up the Tigertronics Signalink USB for DW myself, under
Ubuntu on a RPi2. There's documentation for this in the "Raspberry
Pi TNC"
document. If you have no other sound devices added to the system, it
comes
down to uncommenting the line for ADEVICE 1 and off to the races you
go,
but please have a look at the DW documentation.
73,
Dana? K6JQ
P.S. The Signalink USB shows up as a TI PCM2904 USB audio codec.
There is this, for
USB:
**The Linux operating system is not officially supported by our chipset manufacturer,
or Tigertronics. We will do our best to help you get your SignaLink working in
Linux if you call for Tech Support (click for some customer provided information
on running the SignaLink USB in Linux), but please understand that we do not run this
OS ourselves so support for it will be very limited. If you are not familiar with
installing and configuring software/hardware in Linux, then we strongly suggest
that you use a different OS with your SignaLink.
You are going to need to identify how the sound card shows up in /dev/
I can't tell how PTT shows up in their serial port mapping, either.
.ja.
|
On 11/26/2016 7:24 AM, Jim Alles
kb3tbx@... [direwolf_packet] wrote:
?
Oh. USB or something
else - the specific model number would be helpful.
I just set up the Tigertronics Signalink USB for DW myself, under
Ubuntu on a RPi2. There's documentation for this in the "Raspberry
Pi TNC"
document. If you have no other sound devices added to the system, it
comes
down to uncommenting the line for ADEVICE 1 and off to the races you
go,
but please have a look at the DW documentation.
73,
Dana? K6JQ
P.S. The Signalink USB shows up as a TI PCM2904 USB audio codec.
There is this, for
USB:
**The Linux operating system is not officially supported by our chipset manufacturer,
or Tigertronics. We will do our best to help you get your SignaLink working in
Linux if you call for Tech Support (click for some customer provided information
on running the SignaLink USB in Linux), but please understand that we do not run this
OS ourselves so support for it will be very limited. If you are not familiar with
installing and configuring software/hardware in Linux, then we strongly suggest
that you use a different OS with your SignaLink.
You are going to need to identify how the sound card shows up in /dev/
I can't tell how PTT shows up in their serial port mapping, either.
.ja.
|
I can understand the issue with Linux, but I'm using Windows. Is it not supported either?
?
Oh. USB or something else - the specific model number would be helpful.
There is this, for USB: **The Linux operating system is not officially supported by our chipset manufacturer,
or Tigertronics. We will do our best to help you get your SignaLink working in
Linux if you call for Tech Support (click for some customer provided information
on running the SignaLink USB in Linux), but please understand that we do not run this
OS ourselves so support for it will be very limited. If you are not familiar with
installing and configuring software/hardware in Linux, then we strongly suggest
that you use a different OS with your SignaLink. You are going to need to identify how the sound card shows up in /dev/
I can't tell how PTT shows up in their serial port mapping, either.
.ja.
|
Oh. USB or something else - the specific model number would be helpful.
There is this, for USB: **The Linux operating system is not officially supported by our chipset manufacturer,
or Tigertronics. We will do our best to help you get your SignaLink working in
Linux if you call for Tech Support (click for some customer provided information
on running the SignaLink USB in Linux), but please understand that we do not run this
OS ourselves so support for it will be very limited. If you are not familiar with
installing and configuring software/hardware in Linux, then we strongly suggest
that you use a different OS with your SignaLink. You are going to need to identify how the sound card shows up in /dev/
I can't tell how PTT shows up in their serial port mapping, either.
.ja.
?
Sorry if I was unclear but I have a tigertronics signalink. That's what I was trying to set up.
|
Sorry if I was unclear but I have a tigertronics signalink. That's what I was trying to set up.
?
This will not be a direct connection to the computer.
I think I would buy a , or something similar.
73, Jim A.
|
I mean you have to get the wiring correct from your audio device, what you call a "soundlink" to the radio, if you have the manual, see page 41 on packet connection.? The manual can be pulled down in pdf format from?
This will take figuring out the wiring.? Once you have the wiring right, then you can configure direwolf.
On Fri, Nov 25, 2016 at 4:21 PM, rcflyer30@... [direwolf_packet] <direwolf_packet@...> wrote:
?
Not sure what you mean?
?
This is a physical wiring issue, not configuration. Map your inputs and outputs from your sound device to the radio.
--
John D. Hays K7VE
PO Box 1223, Edmonds, WA 98020-1223  ?  ??
|
|
|
|
|
This is a physical wiring issue, not configuration. Map your inputs and outputs from your sound device to the radio.
On Nov 25, 2016 15:33, " rcflyer30@... [direwolf_packet]" < direwolf_packet@...> wrote:
?
I'm trying to set up dire wolf for rms express with a soundlink and an alinco dr-605. The alinco has an rj45 connection for Mike. No com ports. How do I set up the rj45 in the dire wolf config file?
|
I'm trying to set up dire wolf for rms express with a soundlink and an alinco dr-605. The alinco has an rj45 connection for Mike. No com ports. How do I set up the rj45 in the dire wolf config file?
|
Hi David, I just put the turkey on the weber so my answer is brief. Happy T-day. I would generally agree with you that cron is NOT the right way to
go. The challenge here is that SystemD is super complicated and new
Linux are usually already overwhelmed. I've spent some time learning how to use the systemd transaction files. Not sure that systemd is complicated to config but there definitely is a learning curve that can be steep depending on your background. As such, cron is probably a
easy place to start to create some level of resiliency. Unfortunately
today, there are few solutions in between say cron and Systemd other
than monitoring tools like Monit, etc. If it's what you know that's what you will use ... even if it's the wrong thing to use. Sounds like we need to discuss this over a beer. Anyway, thanks for posting your SystemD configs. As you put them
together, do you know if one SystemD restart can also signal other
running processes to HUP, restart, whatever? systemd has extensive restart capability. It can restart on-success, on-failure, on-abnormal, on-watchdog, on-abort or always. In the transaction files you specify ExecStartPre, ExecStartPost etc and you can conditional a process restart based on the exit codes of these processes as well. Having said that I haven't used those features .. yet. My setup is very stable and the problems I've seen using direwolf & Xastir have to do with the window manager locking up. I'm using an Rpi & a 7" display for home & car. /Basil
|
Hello Basil,
You don't have to restart Xastir, just go to interface control, select
your down interface & click 'Start'.
Yes.. I was going to mention that for Xastir but it's not
automatic. I think Skyler is looking for highly reliable and
auto-remediating solution other than having to reboot the whole
thing every time. In this specific example, I wonder if Xastir can
"restart" it's KISS or AGW connection if it see's a failure. I have
one other friend that setup something similar for less Linux-savvy
HAMs and I'll see what he did to create a more-reliable system.
I have some scripts that install Direwolf & AX.25 and use systemd for
start up here:
The challenge I see here is highly dependent on Skyler's setup and
what system's require to maintain state. Serial KISS is stateless
protocol but if the serial device goes away and then comes back,
will the lower level system re-initialize it and all of it's AX.25
parameters? Usually not. Maybe Systemd can do this when the
low-level /dev/ttyUSB* device is re-created. Instead, say we're
using TCP-KISS. That requires the TCP connection but if it's lost
for whatever reason, will the upstream application re-establish
it?. AGW is also a TCP session and again, if connection is lost,
will the application automatically try to re-establish it? I don't
know.. all this would need to be tested.
For current Linux kernels systemd is the right approach for managing
your daemons or any background process. Don't use cron.
I would generally agree with you that cron is NOT the right way to
go. The challenge here is that SystemD is super complicated and new
Linux are usually already overwhelmed. As such, cron is probably a
easy place to start to create some level of resiliency.
Unfortunately today, there are few solutions in between say cron and
Systemd other than monitoring tools like Monit, etc.
Anyway, thanks for posting your SystemD configs. As you put them
together, do you know if one SystemD restart can also signal other
running processes to HUP, restart, whatever?
--David
KI6ZHD
|
John Hays - K7VE / WRJT-215
Basil Gunn