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
|
Skyler, Responding through David's msg. - Assuming you're using PTY serial KISS to Xastir, it's unclear to
me how Xastir would deal with Direwolf going away and coming back. You don't have to restart Xastir, just go to interface control, select your down interface & click 'Start'. - Monitoring and restarting the various components of your APRS
stack can be done but it gets complicated. There are SystemD examples
for Direwolf out there but if you're using the Linux AX.25 stack, how
would that be managed. I have some scripts that install Direwolf & AX.25 and use systemd for start up here: The Direwolf script configs for a udrc hat but everything else is independent of that hardware. It also sets up the log & log rotate files for direwolf properly. Start with the README. For current Linux kernels systemd is the right approach for managing your daemons or any background process. Don't use cron. /Basil n7nix
|
Me too ... outside of the first two tries to Tx are not correct ... i think thats already fixed in next release.
toggle quoted message
Show quoted text
From: direwolf_packet@... <direwolf_packet@...> on behalf of David Ranch dranch@... [direwolf_packet]
Sent: Wednesday, November 23, 2016 9:03 PM
To: direwolf_packet@...
Subject: Re: [direwolf_packet] Crash proofing
?
?
John would know best but I've personally had reliable results with the -p option.
--David
On 11/23/2016 08:33 PM,
wb2osz@... [direwolf_packet] wrote:
?
Don't use the "-p" pseudo terminal option if you can avoid it. ?Each time the device number could be different, making it difficult for automatic attachment by some other application. ?It has been problematic in other ways.
Xastir knows how to use the AGW TCPIP socket interface. ? Use that instead. ?User Guide section 5.5.1.
?
|
John would know best but I've personally had
reliable results with the -p option.
--David
On 11/23/2016 08:33 PM,
wb2osz@... [direwolf_packet] wrote:
toggle quoted message
Show quoted text
?
Don't use the "-p" pseudo terminal option if you can
avoid it. ?Each time the device number could be different,
making it difficult for automatic attachment by some other
application. ?It has been problematic in other ways.
Xastir knows how to use the AGW TCPIP socket interface.
? Use that instead. ?User Guide section 5.5.1.
?
|
Don't use the "-p" pseudo terminal option if you can avoid it. ?Each time the device number could be different, making it difficult for automatic attachment by some other application. ?It has been problematic in other ways.
Xastir knows how to use the AGW TCPIP socket interface. ? Use that instead. ?User Guide section 5.5.1.
?
|
Hello Skyler,
Giving a reliability report would depend on a huge number of
factors.? To your other point, one item crashing and impacting the
other components entirely depends on :
?? - You mentioned you're starting Direwolf with the -p option
which I assume you're using with a PTY serial interface directly
to Xastir.? Yes?? Maybe you're connecting it to the Linux AX.25
stack?
?? - Assuming you're using PTY serial KISS to Xastir, it's unclear
to me how Xastir would deal with Direwolf going away and coming
back.? Will it retry / re-initialize things? ? You'd have to test
that
?
?? - Monitoring and restarting the various components of your APRS
stack can be done but it gets complicated.? There are SystemD
examples for Direwolf out there but if you're using the Linux
AX.25 stack, how would that be managed.? It's also unclear how
doing this for Xastir would work since it's a graphical
application.
The safe bet would be that if a daemon is found
missing/crashed/etc, you tear down all other related processes and
restart all of the APRS applications again.? You could do this
very crudely using cron (that's what the Direwolf documentation
recommends), you could try using tools like Monit, or you could
try doing this all via SystemD.? Up to you.
--David
KI6ZHD
toggle quoted message
Show quoted text
?
I just did an install on a friends vehicle
containing a raspberry pi running Direwolf, Xastir, and
GPSD (BU-353 GPS). The Pi operates in WiFi Access Point
mode for ease of wireless remote desktop to view Xastir
window maps.
The script I wrote for bootup contains code to
start Xastir and Direwolf. A terminal window is open
in the background while a GUI window is opened up for
Xastir.
I have a feeling that this is a lot of different
processes that have to go right on bootup, and need to
stay online for the duration that the vehicle is
online.?
If my direwolf -p window stops and then starts up
for example, xastir will not recognize packets and
have an interface error until I manually press the
button to start the interface back up.?
Can anybody give me a reliability report of all
these applications? Is there a chance one will crash
or do something funky and cause the system as a whole
to stop? If so, is there a better way to run it, maybe
a Daemon that detects crashing and restarts
everything?
|
I just did an install on a friends vehicle containing a raspberry pi running Direwolf, Xastir, and GPSD (BU-353 GPS). The Pi operates in WiFi Access Point mode for ease of wireless remote desktop to view Xastir window maps.
The script I wrote for bootup contains code to start Xastir and Direwolf. A terminal window is open in the background while a GUI window is opened up for Xastir.
I have a feeling that this is a lot of different processes that have to go right on bootup, and need to stay online for the duration that the vehicle is online.?
If my direwolf -p window stops and then starts up for example, xastir will not recognize packets and have an interface error until I manually press the button to start the interface back up.?
Can anybody give me a reliability report of all these applications? Is there a chance one will crash or do something funky and cause the system as a whole to stop? If so, is there a better way to run it, maybe a Daemon that detects crashing and restarts everything?
73 KD0WHB --
|
Re: recipe for target 'demod_afsk.o' failed
Hello Skyler,
Ok, so you're compiling with Rasbian Jessie but what version of
Direwolf?? 1.3 is stable and works well but there are some cool
new features in 1.4 that you might want to try.
--David
KI6ZHD
|
Re: recipe for target 'demod_afsk.o' failed
Odd .. i didnt see the previous post ... sorry if this is a repeat ...
did you verify all the dependencies ?
I just did a git pull on master (1.3) ... and was stil up to date and didint have that issue ...
Im using an odroid-X2 Ubuntu 14.04 ArmV8
odroid@odroid:~/Downloads/direwolf$ git pull
Already up-to-date.
odroid@odroid:~/Downloads/direwolf$ git tag
1.0
1.1
1.2
1.3
1.3-beta
1.3-dev-F
1.3-dev-I
1.3-dev-K
odroid@odroid:~/Downloads/direwolf$ git branch
* master
odroid@odroid:~/Downloads/direwolf$
toggle quoted message
Show quoted text
From: direwolf_packet@... on behalf of Skyler F electricity440@... [direwolf_packet]
Sent: Thursday, November 17, 2016 9:18 PM
To: direwolf_packet@...
Subject: [direwolf_packet] Re: recipe for target 'demod_afsk.o' failed
?
?
For got to say, I am running a raspberry pi with the latest release of jessie.?
|
Re: recipe for target 'demod_afsk.o' failed
Precompiled version --??
Then
apt-get update apt-get install direwolf
On Thu, Nov 17, 2016 at 9:18 PM, Skyler F electricity440@... [direwolf_packet] <direwolf_packet@...> wrote:
?
For got to say, I am running a raspberry pi with the latest release of jessie.?
--
John D. Hays K7VE
PO Box 1223, Edmonds, WA 98020-1223 ? ??
|
Re: recipe for target 'demod_afsk.o' failed
For got to say, I am running a raspberry pi with the latest release of jessie.?
On Fri, Nov 18, 2016 at 5:14 AM, Skyler F <electricity440@...> wrote: I am trying to build direwolf on my raspberry pi 3.?
I ran the command make, but got the following error:?
make: *** [demod_afsk.o] Error 1
When I ran make again, here it the entire output: Any suggestions?
gcc -O3 -pthread -Igeotranz -ffast-math -mfpu=neon -DUSE_ALSA -DENABLE_GPSD -DUSE_HAMLIB ? -c -o demod_afsk.o demod_afsk.c In file included from demod_afsk.c:51:0: demod_afsk.c: In function ‘demod_afsk_process_sample’: demod_afsk.c:884:28: error: ‘FFF_PROFILE’ undeclared (first use in this function) ? if (D->profile == toupper(FFF_PROFILE)) { ? ? ? ? ? ? ? ? ? ? ? ? ? ? ^ demod_afsk.c:884:28: note: each undeclared identifier is reported only once for each function it appears in : recipe for target 'demod_afsk.o' failed make: *** [demod_afsk.o] Error 1
Thanks, Skyler KD0WHB
--
|
recipe for target 'demod_afsk.o' failed
I am trying to build direwolf on my raspberry pi 3.?
I ran the command make, but got the following error:?
make: *** [demod_afsk.o] Error 1
When I ran make again, here it the entire output: Any suggestions?
gcc -O3 -pthread -Igeotranz -ffast-math -mfpu=neon -DUSE_ALSA -DENABLE_GPSD -DUSE_HAMLIB ? -c -o demod_afsk.o demod_afsk.c In file included from demod_afsk.c:51:0: demod_afsk.c: In function ‘demod_afsk_process_sample’: demod_afsk.c:884:28: error: ‘FFF_PROFILE’ undeclared (first use in this function) ? if (D->profile == toupper(FFF_PROFILE)) { ? ? ? ? ? ? ? ? ? ? ? ? ? ? ^ demod_afsk.c:884:28: note: each undeclared identifier is reported only once for each function it appears in : recipe for target 'demod_afsk.o' failed make: *** [demod_afsk.o] Error 1
Thanks, Skyler KD0WHB
--
|
John Hays - K7VE / WRJT-215
Basil Gunn