¿ªÔÆÌåÓý

Date

Re: Direwolf digipeater with weather data

 

Good morning,
The subject interests me too. Did you get any answers?


Re: RPi Direwolf packet station.

Mike Berg
 

Thanks for the reply, David.
I would be interested in both abilities as I will be comparing the Direwolf - Pi - Signalink combination with Pi - Putty - TNC's.
The purpose is to eventually do a dog & pony show for the local club re-introducing packet.
Since most newer hams don't have a TNC laying around I was looking for alternatives.
Many would be fine with just connected mode sessions while others might want to do a BBS mailbox.
73,
Mike N0QBH


Re: can't pick correct device on PTT RIG command with latest source

 

And isn't it coincidental that this problem shows up the first time I ran DireWolf after I did a significant upgrade to my Fedora system.....

________________________________________
From: [email protected] <[email protected]> on behalf of Andrew P. <andrewemt@...>
Sent: Sunday, September 17, 2023 7:51 PM
To: [email protected]
Subject: Re: [direwolf] can't pick correct device on PTT RIG command with latest source

Re: the first issue: when I run the Fedora Core 37's distro install of direwolf 1.6 with the same direwolf.conf file (I am explicitly using the complete absolute file path), everything works perfectly (receive and transmit). And it's the same O/S-installed version of libasound.so.2.0.0, which is odd.

No, I take that back. Direwolf 1.6 managed to transmit my first beacon, but it started the alsa failures on the second beacon transmission attempt.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of David Ranch <direwolf-groupsio@...>
Sent: Sunday, September 17, 2023 7:38 PM
To: [email protected]
Subject: Re: [direwolf] can't pick correct device on PTT RIG command with latest source


Hello Andrew,

It's VERY strange that Direwolf is choosing /dev/ttyS0 when you've configured /dev/ttyUSB5. When you start direwolf, are you possibly loading the wrong direwolf.conf file? Also, is the "apavlin" user in the dialout Unix group? Next, regarding your "Error preparing after bad state: Bad address" error, this is a known issue with bleeding edge versions of ALSA. This is discussed AND fixed per this thread here:

/g/direwolf/topic/99527314#8286

--David
KI6ZHD


On 09/17/2023 02:32 PM, Andrew P. wrote:

Greetings.

I just pulled the latest git clone code for hamlib and direwolf (2023-Sep-17 17:00 US/Eastern time), and rebuilt my copy of direwolf on the dev branch. Now I can't have PTT control over my Icom IC-7100 radio. Every time I start up DireWolf, it reports the following:
---------------------------------------------------------------------------------
Dire Wolf version 1.7 (Sep 17 2023) BETA TEST 7
Includes optional support for: gpsd hamlib cm108-ptt dns-sd
Warning: Could not open 'symbols-new.txt'.
The "new" OVERLAID character information will not be available.

Reading config file /home/apavlin/direwolf.conf
Audio device for both receive and transmit: plughw:1,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 0.
User configuration overriding hamlib CAT control speed to 19200.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Hamlib Rig open error -2: rig_settings_get_path: path=/home/apavlin/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/apavlin/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/apavlin
rig_open: /home/apavlin/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=19200,0x000e
serial_setup: cfsetospeed=19200,0x000e
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig_open: rs->comm_state==0?=0
1:rig.c(1023):rig_open returning(-2) Invalid configuration

Invalid configuration
-----------------------------------------------------

Note there are long delays between printouts of the "Retrying Hamlib Rig Open" call. Also, the PTT directive in my direwolf.conf file says:

PTT RIG 3070 /dev/ttyUSB5 19200

but the above error messages are complaining about /dev/ttyS0. My system doesn't have a motherboard serial port, and I can access /dev/ttyUSB5 with the rigctl command (although it has other issues). There is no rigctld daemon running on my Fedora Core 37 system, uname reports:
Linux 6.4.15-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 7 00:23:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

There is only one CHANNEL defined in my direwolf.conf file.

Before I installed a local copy of the latest hamlib, building the latest DireWolf would successfully start and receive packets successfully, but it would fail with dozens of errors trying to transmit (and it still didn't key the transmitter):
------------------------------------------------------------------------
[0L] KA2DDO>APJYC1,WIDE1-1:=4003.35N/07527.42W? YAAC development<0x0d>
Audio output start error.
Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Audio write error retry count exceeded.
-------------------------------------------------------------------------

Any suggestions as to what went wrong?

Andrew, KA2DDO


Re: can't pick correct device on PTT RIG command with latest source

 

Re: the first issue: when I run the Fedora Core 37's distro install of direwolf 1.6 with the same direwolf.conf file (I am explicitly using the complete absolute file path), everything works perfectly (receive and transmit). And it's the same O/S-installed version of libasound.so.2.0.0, which is odd.

No, I take that back. Direwolf 1.6 managed to transmit my first beacon, but it started the alsa failures on the second beacon transmission attempt.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of David Ranch <direwolf-groupsio@...>
Sent: Sunday, September 17, 2023 7:38 PM
To: [email protected]
Subject: Re: [direwolf] can't pick correct device on PTT RIG command with latest source


Hello Andrew,

It's VERY strange that Direwolf is choosing /dev/ttyS0 when you've configured /dev/ttyUSB5. When you start direwolf, are you possibly loading the wrong direwolf.conf file? Also, is the "apavlin" user in the dialout Unix group? Next, regarding your "Error preparing after bad state: Bad address" error, this is a known issue with bleeding edge versions of ALSA. This is discussed AND fixed per this thread here:

/g/direwolf/topic/99527314#8286

--David
KI6ZHD


On 09/17/2023 02:32 PM, Andrew P. wrote:

Greetings.

I just pulled the latest git clone code for hamlib and direwolf (2023-Sep-17 17:00 US/Eastern time), and rebuilt my copy of direwolf on the dev branch. Now I can't have PTT control over my Icom IC-7100 radio. Every time I start up DireWolf, it reports the following:
---------------------------------------------------------------------------------
Dire Wolf version 1.7 (Sep 17 2023) BETA TEST 7
Includes optional support for: gpsd hamlib cm108-ptt dns-sd
Warning: Could not open 'symbols-new.txt'.
The "new" OVERLAID character information will not be available.

Reading config file /home/apavlin/direwolf.conf
Audio device for both receive and transmit: plughw:1,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 0.
User configuration overriding hamlib CAT control speed to 19200.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Hamlib Rig open error -2: rig_settings_get_path: path=/home/apavlin/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/apavlin/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/apavlin
rig_open: /home/apavlin/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=19200,0x000e
serial_setup: cfsetospeed=19200,0x000e
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig_open: rs->comm_state==0?=0
1:rig.c(1023):rig_open returning(-2) Invalid configuration

Invalid configuration
-----------------------------------------------------

Note there are long delays between printouts of the "Retrying Hamlib Rig Open" call. Also, the PTT directive in my direwolf.conf file says:

PTT RIG 3070 /dev/ttyUSB5 19200

but the above error messages are complaining about /dev/ttyS0. My system doesn't have a motherboard serial port, and I can access /dev/ttyUSB5 with the rigctl command (although it has other issues). There is no rigctld daemon running on my Fedora Core 37 system, uname reports:
Linux 6.4.15-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 7 00:23:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

There is only one CHANNEL defined in my direwolf.conf file.

Before I installed a local copy of the latest hamlib, building the latest DireWolf would successfully start and receive packets successfully, but it would fail with dozens of errors trying to transmit (and it still didn't key the transmitter):
------------------------------------------------------------------------
[0L] KA2DDO>APJYC1,WIDE1-1:=4003.35N/07527.42W? YAAC development<0x0d>
Audio output start error.
Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Audio write error retry count exceeded.
-------------------------------------------------------------------------

Any suggestions as to what went wrong?

Andrew, KA2DDO


Re: can't pick correct device on PTT RIG command with latest source

 

¿ªÔÆÌåÓý


Hello Andrew,

It's VERY strange that Direwolf is choosing /dev/ttyS0 when you've configured /dev/ttyUSB5.? When you start direwolf, are you possibly loading the wrong direwolf.conf file? ? Also, is the "apavlin" user in the dialout Unix group?? Next, regarding your "Error preparing after bad state: Bad address" error, this is a known issue with bleeding edge versions of ALSA.? This is discussed AND fixed per this thread here:

?? /g/direwolf/topic/99527314#8286

--David
KI6ZHD


On 09/17/2023 02:32 PM, Andrew P. wrote:

Greetings.

I just pulled the latest git clone code for hamlib and direwolf (2023-Sep-17 17:00 US/Eastern time), and rebuilt my copy of direwolf on the dev branch. Now I can't have PTT control over my Icom IC-7100 radio. Every time I start up DireWolf, it reports the following:
---------------------------------------------------------------------------------
Dire Wolf version 1.7 (Sep 17 2023) BETA TEST 7
Includes optional support for:  gpsd hamlib cm108-ptt dns-sd
Warning: Could not open 'symbols-new.txt'.
The "new" OVERLAID character information will not be available.

Reading config file /home/apavlin/direwolf.conf
Audio device for both receive and transmit: plughw:1,0  (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 0.
User configuration overriding hamlib CAT control speed to 19200.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Hamlib Rig open error -2: rig_settings_get_path: path=/home/apavlin/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/apavlin/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/apavlin
rig_open: /home/apavlin/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=19200,0x000e
serial_setup: cfsetospeed=19200,0x000e
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig_open: rs->comm_state==0?=0
 1:rig.c(1023):rig_open returning(-2) Invalid configuration

Invalid configuration
-----------------------------------------------------

Note there are long delays between printouts of the "Retrying Hamlib Rig Open" call. Also, the PTT directive in my direwolf.conf file says:

PTT RIG 3070 /dev/ttyUSB5 19200

but the above error messages are complaining about /dev/ttyS0. My system doesn't have a motherboard serial port, and I can access /dev/ttyUSB5 with the rigctl command (although it has other issues). There is no rigctld daemon running on my Fedora Core 37 system, uname reports:
Linux 6.4.15-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep  7 00:23:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

There is only one CHANNEL defined in my direwolf.conf file.

Before I installed a local copy of the latest hamlib, building the latest DireWolf would successfully start and receive packets successfully, but it would fail with dozens of errors trying to transmit (and it still didn't key the transmitter):
------------------------------------------------------------------------
[0L] KA2DDO>APJYC1,WIDE1-1:=4003.35N/07527.42W? YAAC development<0x0d>
Audio output start error.
Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Audio write error retry count exceeded.
-------------------------------------------------------------------------

Any suggestions as to what went wrong?

Andrew, KA2DDO






Re: RPi Direwolf packet station.

 

¿ªÔÆÌåÓý


Hello Mike,

Can you describe what you mean by "local packet services"?? Are you talking about say connected-mode sessions to remote packet BBSes, PBBSes, etc?? If so, do you want to only make outgoing connections or do you want to also support incoming connections?

--David
KI6ZHD



On 09/17/2023 11:06 AM, Mike Berg wrote:

I've got Direwolf running on a Pi3b using a USB soundcard with good results.
Now I'd like to add TNC like functionality so that I can access the local packet services.
I had some great instructions on my Git hub journey using the Direwolf for APRS doc.
I'm looking for suggestions hoping the rest goes as well.
73
Mike N0QBH


can't pick correct device on PTT RIG command with latest source

 

Greetings.

I just pulled the latest git clone code for hamlib and direwolf (2023-Sep-17 17:00 US/Eastern time), and rebuilt my copy of direwolf on the dev branch. Now I can't have PTT control over my Icom IC-7100 radio. Every time I start up DireWolf, it reports the following:
---------------------------------------------------------------------------------
Dire Wolf version 1.7 (Sep 17 2023) BETA TEST 7
Includes optional support for: gpsd hamlib cm108-ptt dns-sd
Warning: Could not open 'symbols-new.txt'.
The "new" OVERLAID character information will not be available.

Reading config file /home/apavlin/direwolf.conf
Audio device for both receive and transmit: plughw:1,0 (channel 0)
Channel 0: 1200 baud, AFSK 1200 & 2200 Hz, A+, 44100 sample rate.
Hamlib determined CAT control serial port rate of 0.
User configuration overriding hamlib CAT control speed to 19200.
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Retrying Hamlib Rig open...
Hamlib Rig open error -2: rig_settings_get_path: path=/home/apavlin/.config/hamlib_settings
rig_settings_load_all: settings_file (/home/apavlin/.config/hamlib_settings): No such file or directory
rig_open: cwd=/home/apavlin
rig_open: /home/apavlin/hamlib_settings does not exist
rig_open: async_data_enable=0, async_data_supported=0
serial_open: /dev/ttyS0
serial_setup: tcgetattr
serial_setup: cfmakeraw
serial_setup: cfsetispeed=19200,0x000e
serial_setup: cfsetospeed=19200,0x000e
serial_setup: data_bits=8
serial_setup: parity=0
serial_setup: Handshake=None
serial_setup: tcsetattr TCSANOW
serial_setup: tcsetattr failed: Input/output error
port_open: serial_open(/dev/ttyS0) status=-2, err=Bad file descriptor
rig_open: rs->comm_state==0?=0
1:rig.c(1023):rig_open returning(-2) Invalid configuration

Invalid configuration
-----------------------------------------------------

Note there are long delays between printouts of the "Retrying Hamlib Rig Open" call. Also, the PTT directive in my direwolf.conf file says:

PTT RIG 3070 /dev/ttyUSB5 19200

but the above error messages are complaining about /dev/ttyS0. My system doesn't have a motherboard serial port, and I can access /dev/ttyUSB5 with the rigctl command (although it has other issues). There is no rigctld daemon running on my Fedora Core 37 system, uname reports:
Linux 6.4.15-100.fc37.x86_64 #1 SMP PREEMPT_DYNAMIC Thu Sep 7 00:23:27 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux

There is only one CHANNEL defined in my direwolf.conf file.

Before I installed a local copy of the latest hamlib, building the latest DireWolf would successfully start and receive packets successfully, but it would fail with dozens of errors trying to transmit (and it still didn't key the transmitter):
------------------------------------------------------------------------
[0L] KA2DDO>APJYC1,WIDE1-1:=4003.35N/07527.42W? YAAC development<0x0d>
Audio output start error.
Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Error preparing after bad state: Bad address
Audio write error retry count exceeded.
-------------------------------------------------------------------------

Any suggestions as to what went wrong?

Andrew, KA2DDO


RPi Direwolf packet station.

Mike Berg
 

I've got Direwolf running on a Pi3b using a USB soundcard with good results.
Now I'd like to add TNC like functionality so that I can access the local packet services.
I had some great instructions on my Git hub journey using the Direwolf for APRS doc.
I'm looking for suggestions hoping the rest goes as well.
73
Mike N0QBH


Re: Direwolf UDP socket input

 

This is direwolf on linux, the distro version for Ubuntu and Fedora (1.6) as well as built recently from dev branch (~1.7). I'm streaming gqrx to UDP port 7355 as in the tutorial. It seems to be working on the gqrx side as I can see the stream in netcat/netstat. And as mentioned, if I then pipe netcat into direwolf STDIN it is at least able to decode DTMF.

For direwolf I am just trying with the basic config for reading UDP socket:
ADEVICE0 udp:7355 default
ARATE 48000
ACHANNELS 1
DTMF

I've also tried just running command-line `direwolf -n 1 -r 48000 -b 16 udp:7355`

As mentioned, adding -a10 to either of these doesn't show any output; it seems to hang on the recv() call in audio.c.


On Thu, Sep 14, 2023 at 7:33?AM WB2OSZ <wb2osz@...> wrote:
The Radio Interface Guide, found here , has information about using gqrx.
gqrx streaming audio is covered here and direwolf is mentioned.

Can you tell us more about the relevant? gqrx and direwolf configuration settings?

73,
John WB2OSZ


Re: Direwolf UDP socket input

 

The Radio Interface Guide, found here , has information about using gqrx.
gqrx streaming audio is covered here and direwolf is mentioned.

Can you tell us more about the relevant? gqrx and direwolf configuration settings?

73,
John WB2OSZ


Direwolf UDP socket input

 

Hello all,

I'm trying to pipe gqrx to direwolf and not having luck with the udp:7355 socket input. It seems to hang on the recv() call; adding -a10 also gives no updates. I tried poking around the code a little but haven't found the issue yet. Any tips?

For now, a workaround is to use netcat to read the UDP port and then pipe that to direwolf STDIN.

Thanks!
Peter


Re: Starting direwolf

 

Thanks Rob and Kevin for your replies. I immediately thought of Kevin's comment when I read Rob's reply, as I have been bit by that several times.

Your answers and some other things I ran into led me to first create .desktop files for direwolf and YAAC. Then I copied them into the .config/autostart folder and everything starts on boot and works great.

Thanks for your help,

Michael WA7SKG


Rob Giuliano via groups.io wrote on 9/11/23 6:36 AM:

Yes - that is VERY important when running from within a cron script.
Sorry for the confusion.? I copied a .desktop file and didn't think it through!
Robert Giuliano
KB8RCO
On Monday, September 11, 2023 at 09:31:19 AM EDT, Kevin <kd9efv@...> wrote:
May I make 1 suggestion, Rob? Use the full path to the config file, not the ~ (tilde) path. IOW,
#! /usr/bin/env bash
/usr/local/bin/direwolf -c /home/<username>/direwolf/direwolf.conf
Or even better, maybe put the .conf file in /etc or a shared folder tree...
--
= = = =
? Kevin? --? KD9EFV


Re: Starting direwolf

 

Yes - that is VERY important when running from within a cron script.
Sorry for the confusion.? I copied a .desktop file and didn't think it through!

Robert Giuliano
KB8RCO



On Monday, September 11, 2023 at 09:31:19 AM EDT, Kevin <kd9efv@...> wrote:


May I make 1 suggestion, Rob? Use the full path to the config file, not the ~ (tilde) path. IOW,
#! /usr/bin/env bash
/usr/local/bin/direwolf -c /home/<username>/direwolf/direwolf.conf
Or even better, maybe put the .conf file in /etc or a shared folder tree...

--
= = = =

? Kevin? --? KD9EFV


Re: Starting direwolf

 

(btw, the suggestion is related to the ability to figure out the path, if it is being run as root in a crontab, or any of a number of other issues, the ~ path doesn't always point to where it 'should'. In root it points to /root/, and not to /home/<username>)
--
= = = =

? Kevin? --? KD9EFV


Re: Starting direwolf

 

May I make 1 suggestion, Rob? Use the full path to the config file, not the ~ (tilde) path. IOW,
#! /usr/bin/env bash
/usr/local/bin/direwolf -c /home/<username>/direwolf/direwolf.conf
Or even better, maybe put the .conf file in /etc or a shared folder tree...

--
= = = =

? Kevin? --? KD9EFV


Re: Starting direwolf

 

I believe most of the Linux distros have moved to using systemd startup files.?
?? It looks like you are trying to get Direwolf to run in the background (no display terminal).
?? Best to try and getting it working on boot within a terminal, then alter the startup to make it background.
?? I might suggest a less complicated startup script - no functions, just start direwolf with a defined configuration
Is your Quadra system running systemd?? If so, I suggest giving that a try.
?? If not,? you might want to create a more simplified script (as mentioned above)

Simplified script (assuming you don't need RTL_FM or other specialty application before Direwolf starts):
#! /usr/bin/env bash
/usr/local/bin/direwolf -c ~/direwolf/direwolf.conf

NOTE:? I have a direwolf directory in my home folder, where I keep different configuration files.? Just to explain the ~/direwolf/direwolf.conf
???????????? Also, removed any check if Direwolf is running.? You could add that later.
-------
Rob KB8RCO
Never listen to an Atom, they make up everything
(from - nerdy science t-shirt my sister bought me)


Starting direwolf

 

I have successfully (I think) installed direwolf on my Quadra. My issue now is starting it. If I try to run the startup script that came with the install it pops up a big error box that goes away before I can read it, then tells me it doesn't start with

========================================
quadra@inovato:~$ ./dw-start.sh
Direwolf in GUI mode start up
DISPLAY=:0
-----------------------
quadra@inovato:~$ ConfigBase::load: Unable to open /etc/xdg/terminator/config ([Errno 2] No such file or directory: '/etc/xdg/terminator/config')

quadra@inovato:~$
========================================

I have no idea where the stuff about "Unable to open /etc/xdg/terminator" is coming from. There is no reference to anything xdg in the script.


Most of the dw-start.sh script makes little sense to me.

I can go into the direwolf folder and simply type direwolf, and it seems to startup and run fine. But I have to leave a terminal window open to do this. Then I have to ctrl-C to stop it when I shut down the computer. Kind of a nuisance.


So, what is the best way to have direwolf start on boot?
I put the recommended crontab of

* * * * * /home/quadra/dw-start.sh >/dev/null 2>&1

but that does not seem to work. I am assuming it is due to the error shown above when I run dw-start.sh from the command line.

I appreciate your time.

--
73,
Michael WA7SKG

"Any day you do not learn one new thing is a wasted day."


Re: Cross Fix to ALSA-LIB and GPIO PTT issues

 

? Finally found the issue with using the GPIO pins on the Wandboard ARM machine. The GPIO pin I expected to use was muxed for use with a second SD drive. That they identified it in the diagrams for external use was the problem. Using a different external pin and re-designating it in the .conf file did the trick!? The 3.0v output drives an opto-isolator to run the PTT on a Yaesu FT-1800 with some current limiting resistors.
Curiously, I discovered I still have the KAM Plus and Yaesu FT270 I used in the 80's.


Re: New Quadra APRS Installation

 

Thanks for your reply, David.

The audio adapters I have look like a thumb drive with a couple jacks on the end. Other than that, I'll have to wait until I find them again to tell you more :-)

I've got two radio options for this project right now, a Radio Shack HTX-242 and an Icom IC-2350. Neither have data ports, so the connection will be via RJ-45 mic jack and external speaker jacks.

I found some info on using the CM108 devices. I just have to find the ones I have to figure out if they will work.

Thanks,
Michael WA7SKG



David Ranch wrote on 9/7/23 8:32 AM:

Hello Michael,

First, the audio interface. This is a no budget setup so something like Signalink is out of the question. I've got a couple cheap USB audio interfaces that have mic in and speaker out jacks. Will those work with direwolf?
Can you give us some details of these "cheap devices"?? If they are what I think they are, they are CM108-based sound devices and should work for audio AND PTT with the addition of a few simple electronic components and some soldering.

Second is PTT. The Quadra has no I/O pins or serial port to trigger the PTT. The radio does not have VOX, which I would not use anyway.
Can you tell us which radio you're planning on using?

Next, is direwolf usable with other digital modes than packet/APRS, like fldigi or WSJT-X?
Direwolf only does AX.25 packet radio, AIS reception, and some DTMF stuff.? Fldigi, WSJT-X, etc are all entirely different programs supporting very different digital? modes.
--David
KI6ZHD


Re: New Quadra APRS Installation

 

¿ªÔÆÌåÓý


Hello Michael,

First, the audio interface. This is a no budget setup so something like Signalink is out of the question. I've got a couple cheap USB audio interfaces that have mic in and speaker out jacks. Will those work with direwolf?

Can you give us some details of these "cheap devices"?? If they are what I think they are, they are CM108-based sound devices and should work for audio AND PTT with the addition of a few simple electronic components and some soldering.


Second is PTT. The Quadra has no I/O pins or serial port to trigger the PTT. The radio does not have VOX, which I would not use anyway.

Can you tell us which radio you're planning on using??


Next, is direwolf usable with other digital modes than packet/APRS, like fldigi or WSJT-X?

Direwolf only does AX.25 packet radio, AIS reception, and some DTMF stuff.? Fldigi, WSJT-X, etc are all entirely different programs supporting very different digital? modes.

--David
KI6ZHD