Hi?

I have configured 2 channels in my dirwolf.conf. One for HF and one for VHF.

I'm using the dev branch of the Github repository.

My dirwolf.conf looks like this

?

ADEVICE plughw:1,0
ACHANNELS 1

?

ADEVICE1 plughw:2,0
ACHANNELS 1

?

CHANNEL 0
MYCALL F4IKH

IL2PTX 1
MODEM 300 1600:1800 7@30 /4 D
PTT /dev/ttyCOM4 RTS

?

CHANNEL 2
MYCALL F4IKH-2

MODEM 1200
PTT /dev/ttyCOM3 RTS

?

KISSPORT 8001 0
KISSPORT 8002 2

I would like to activate the protocol on channel 0 only with the IL2PTX 1 option but it seems that the option applies to all channels.

I have a Yeasu VX8-GE and an SCS PTCII modem to monitor the VHF and once the option is activated they don't decode anything.

As soon as I deactivate the option, they start decoding again.

?

Is this normal, or do I need to open an issue on Github?

thanks

greetings

Claude

On Oct 13, 2024, at 12:12?PM, Andrew P. <andrewemt@...> wrote:

?Good. So whether or not a digipeater heard you, an I-gate did to forward your packets.

On the other hand, did you configure Direwolf to talk to the APRS-IS, such that the packet was sent directly to the Internet without going over RF? Check the digipeat path of the packet on aprs.fi and see who forwarded your packet to the Internet (and if the packet went through any digipeaters before reaching the I-gate).

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of dameiners@... via groups.io <dameiners@...>
Sent: Sunday, October 13, 2024 1:05 PM
To: [email protected]
Subject: Re: [direwolf] I need help!

I _just_checked aprs.fi, my PBEACON, while location needs tuning, went out!

On Oct 13, 2024, at 11:56?AM, Andrew P. <andrewemt@...> wrote:

?Have you looked at the aprs.fi map for your area to see if there _are_ any digipeaters in your neighborhood? If there aren't any, there won't be anything to hear you. And there are many places in the US with poor or non-existent digipeater coverage. Also, remember that the 2-meter band is more-or-less line-of-sight; if you can't _see_ the digipeater antenna from your station's antenna, you probably won't get through.

I have a problem like that with my QTH on the north side of a hill, such that I can stand in my backyard on the ground and look _down_ at the antennas on my roof. Good thing for me there are digipeaters to the northwest and northeast of me to help me bounce around this chunk of granite.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of dameiners@... via groups.io <dameiners@...>
Sent: Sunday, October 13, 2024 12:42 PM
To: [email protected]
Subject: Re: [direwolf] I need help!

I've attached a screenshot of the DireWolf -dgt startup.

MY APRS Rig is fully outdoors.

I don't see a reply from a digipeater in response to my outgoing packet(s).

I am using Raspberry Pi 64-bit OS (Bookworm) with Pi desktop, 2024-07-04.

I have changed TXDELAY to 50, TXTAIL to 35 and still not getting "out"

My coordinates are for Central Illinois, USA, lat=40^41.47N long=089^28.37W

________________________________
From: [email protected] <[email protected]> on behalf of David Ranch via groups.io <direwolf-groupsio@...>
Sent: Saturday, October 12, 2024 3:30 PM
To: [email protected] <[email protected]>
Subject: Re: [direwolf] I need help!


Hello Doug,

I looked at your .docx file but it doesn't show the output of direwolf starting up. Can you please add that?



I've been running APRS/Dire Wolf mobile tracker successfully since 2020 with the same physical setup. My SD became corrupt and like a dummy, never made a backup.

Hmmm.. bummer. SD cards can die if you don't use good quality cards AND tune the Linux operating system to minimize writes.


I'm trying to get it running again with Dire Wolf 1.8 Development D and having a couple issues:

*
GPS doesn't move within Dire Wolf (stuck at 4041.76N/08928.70) but moves with GPSMON

I'm not sure what those coordinates are supposed to be. Maybe you meant 40.417600, 89.287000 (the middle of China). Anyway, this could be a matter of permissions. Are you using gpsd with direwolf? When you're doing testing with Direwolf, are you doing this OUTSIDE with a clear shot of the sky? A lot of inexpensive GPSes just won't get a good lock w/o exceptional signal levels. Btw, if you're using the gpsd approach with direwolf, you should be able to run tools like cgps/xgps/etc while direwolf is also running. With that parallel view, you can confirm if you have good GPS lock, the location is correct, the time is correct, etc.



* Not getting digipeated

I believe the issues are related but can't find the common denominator.

What makes you think your station isn't getting digipeted? Not showing up on an APRS-IS map? If so, that would be expected as you need to first send your location to APRS-IS before it will believe other data coming from your station. You can work around this by sending a PBEACON with a static location just as a test.



Dire Wolf launches without error using -dgt

Please show us all of that startup detail.


I've attached the script that I'm using to create my new installation for reference.

Few things in here:
- Which version of Raspberry Pi OS are you installing? The GUI desktop or the Lite version with no GUI?

- The use of the "pi" username is deprecated. Please use something else like "doug" or whatever

- Do NOT remove PulseAudio. You will damage the resulting OS install. Things might continue to work for Direwold since it can use ALSA directly but the GUI environment might have permanent issues.

- Your TXDELAY is way too fast. Is this your radio ( )? If so, that's an SDR based radio and most of those radios are very slow.. as such, I recommend to START at a setting of "45" meaning 450ms to properly key up and be stable on-frequency before the packet audio tones start getting played. The final tuning might need more/less delay depending on how your radio actually performs. You also might need more TXTAIL time as well.


Using the overlay file system can really help minimize writes to the SD card but it can become a major PITA when you want to do OS updates, etc. Your choice but if you want to see a less invasive list of hardening, see:



--David
KI6ZHD

On Oct 13, 2024, at 11:56?AM, Andrew P. <andrewemt@...> wrote:

?Have you looked at the aprs.fi map for your area to see if there _are_ any digipeaters in your neighborhood? If there aren't any, there won't be anything to hear you. And there are many places in the US with poor or non-existent digipeater coverage. Also, remember that the 2-meter band is more-or-less line-of-sight; if you can't _see_ the digipeater antenna from your station's antenna, you probably won't get through.

I have a problem like that with my QTH on the north side of a hill, such that I can stand in my backyard on the ground and look _down_ at the antennas on my roof. Good thing for me there are digipeaters to the northwest and northeast of me to help me bounce around this chunk of granite.

Andrew, KA2DDO

________________________________________
From: [email protected] <[email protected]> on behalf of dameiners@... via groups.io <dameiners@...>
Sent: Sunday, October 13, 2024 12:42 PM
To: [email protected]
Subject: Re: [direwolf] I need help!

I've attached a screenshot of the DireWolf -dgt startup.

MY APRS Rig is fully outdoors.

I don't see a reply from a digipeater in response to my outgoing packet(s).

I am using Raspberry Pi 64-bit OS (Bookworm) with Pi desktop, 2024-07-04.

I have changed TXDELAY to 50, TXTAIL to 35 and still not getting "out"

My coordinates are for Central Illinois, USA, lat=40^41.47N long=089^28.37W

________________________________
From: [email protected] <[email protected]> on behalf of David Ranch via groups.io <direwolf-groupsio@...>
Sent: Saturday, October 12, 2024 3:30 PM
To: [email protected] <[email protected]>
Subject: Re: [direwolf] I need help!


Hello Doug,

I looked at your .docx file but it doesn't show the output of direwolf starting up. Can you please add that?



I've been running APRS/Dire Wolf mobile tracker successfully since 2020 with the same physical setup. My SD became corrupt and like a dummy, never made a backup.

Hmmm.. bummer. SD cards can die if you don't use good quality cards AND tune the Linux operating system to minimize writes.


I'm trying to get it running again with Dire Wolf 1.8 Development D and having a couple issues:

*
GPS doesn't move within Dire Wolf (stuck at 4041.76N/08928.70) but moves with GPSMON

I'm not sure what those coordinates are supposed to be. Maybe you meant 40.417600, 89.287000 (the middle of China). Anyway, this could be a matter of permissions. Are you using gpsd with direwolf? When you're doing testing with Direwolf, are you doing this OUTSIDE with a clear shot of the sky? A lot of inexpensive GPSes just won't get a good lock w/o exceptional signal levels. Btw, if you're using the gpsd approach with direwolf, you should be able to run tools like cgps/xgps/etc while direwolf is also running. With that parallel view, you can confirm if you have good GPS lock, the location is correct, the time is correct, etc.



* Not getting digipeated

I believe the issues are related but can't find the common denominator.

What makes you think your station isn't getting digipeted? Not showing up on an APRS-IS map? If so, that would be expected as you need to first send your location to APRS-IS before it will believe other data coming from your station. You can work around this by sending a PBEACON with a static location just as a test.



Dire Wolf launches without error using -dgt

Please show us all of that startup detail.


I've attached the script that I'm using to create my new installation for reference.

Few things in here:
- Which version of Raspberry Pi OS are you installing? The GUI desktop or the Lite version with no GUI?

- The use of the "pi" username is deprecated. Please use something else like "doug" or whatever

- Do NOT remove PulseAudio. You will damage the resulting OS install. Things might continue to work for Direwold since it can use ALSA directly but the GUI environment might have permanent issues.

- Your TXDELAY is way too fast. Is this your radio ( )? If so, that's an SDR based radio and most of those radios are very slow.. as such, I recommend to START at a setting of "45" meaning 450ms to properly key up and be stable on-frequency before the packet audio tones start getting played. The final tuning might need more/less delay depending on how your radio actually performs. You also might need more TXTAIL time as well.


Using the overlay file system can really help minimize writes to the SD card but it can become a major PITA when you want to do OS updates, etc. Your choice but if you want to see a less invasive list of hardening, see:



--David
KI6ZHD

?

Thank you for the very detailed explanation.? The digirig is also used for FT8 and WSJT-x and there are no issues with CAT (rig control) or Audio (Decoding) with this radio.? I didn't think of the polarity being the possible culprit.? So, when I get home, I will configure to? PTT COM5 -RTS.? I also use the radio with FLDIGI and connect with FLRIG.? The radio is also set in? DIG mode so maybe I will try PKT mode instead.? I am getting there.

If WSJT-X and Flrig/Fldigi are working, then there is no reason why Direwolf can't be made to work (of course, only one application at a time).? How do you have WSJTX / Flrig configured?


?? - PTT
????? - serial port?? If so, which serial port?? What speed?? Any unique parameters enabled?

????? - GPIO pin? which GPIO pin?? What speed?? Any unique parameters enabled?

????? - CAT control?? If so, the direwolf? v1.7 binary for Windows does NOT support CAT control and requires to be re-compiled.? CAT control on Direwolf really doesn't offer anything else other than PTT support but if you want to try this approach, see which provides a link to a compiled binary with Hamlib v4.5.5 support from an enduser


Also, which Digirig hardware device version do you have?? They are up to version v1.9 as they had multiple issues with various PTT options be it from the serial port control lines, the CM108 GPIO pin, etc.? also.. how have you soldered the PTT control pads?

?
?? --
?? Starting from revision 1.5 Digirig features an open-collector switch controlled by RTS signal of the serial port to do exactly that. Many popular digital mode software applications recognize RTS signal as one of the PTT options. More information on PTT switch this can be found in this post: VHF/UHF Digital Modes with budget HTs.

In Digirig 1.5 there are two line drivers available as options: one for PTT, another for CW key if required.

Stating from Digirig 1.6 there is one PTT driver line permanently available on audio TRRS socket as second ring. It is independent from serial CAT and accessible in all configurations. This allows sharing of the same Digirig unit between CAT capable radios and HTs reliant on hardware PTT signal.
?? --


--David