Re: Question on APRS error messages
Thanks David!
?
I am on an HF BBS frequency. Thanks for the suggestion and I am going to have to dig out the most recent manual and take a look.
?
-Chris
?
On Wed, Dec 4, 2024 at 09:16 PM, David Ranch wrote:
Hello Chris,
Is your packet station on an APRS frequency or a BBS frequency?? If you want to disable the APRS packet repair heuristics, you can add the following "ax25" parameter to your direwolf.conf file:
?? FIX_BITS 0 AX25
Please note that you might want to actually ENABLE the FIX_BITS feature (changing the "0" parameter to one of the valid higher numbers) to improve weak packet decoding at the risk of some incorrect decodes.? See the Direwolf User Manual for more detail.
--David
KI6ZHD
On 12/04/2024 05:29 PM, Christopher Molnar KO4YAW via groups.io wrote:
Hello All!
?
I am seeing the following error messages regarding bad APRS packet segments, but? these are from packet stations and are valid. Is there anyway to turn off, or adjust, APRS error messages?
?
?
[0L] KO4YAW-7>BEACON:KO4YAW: Node: KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 Sysop: Chris
[0L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
[1L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 1
KISS protocol set Persistence = 64, chan 1
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 1
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 1
KISS protocol set FullDuplex = 0, chan 1
N6CTA-7 audio level = 75 ? FX.25 ? 0
[0] N6CTA-7>BEACON:!3405.20N/11748.25WB-1/B -4/C 14.105L DM14 FARPN
Position, BBS or PBBS
Use of "BEACON" in the destination field is obsolete. ?You can help to improve the quality of APRS signals.
Tell the sender (N6CTA-7) to use the proper product identifier from ?
N 34 05.2000, W 117 48.2500
-1/B -4/C 14.105L DM14 FARPN
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
?
?
I also see similar messages with call signs in the same place as BEACON. For example if one station is contacting another.? XXXX>KXXXX-1 there is a message that comes up and says that K is not in the correct place for an APRS packet.
Thanks!
-Chris KO4YAW
?
|
Re: Question on APRS error messages
Hello Chris,
Is your packet station on an APRS frequency or a BBS frequency?? If
you want to disable the APRS packet repair heuristics, you can add
the following "ax25" parameter to your direwolf.conf file:
?? FIX_BITS 0 AX25
Please note that you might want to actually ENABLE the FIX_BITS
feature (changing the "0" parameter to one of the valid higher
numbers) to improve weak packet decoding at the risk of some
incorrect decodes.? See the Direwolf User Manual for more detail.
--David
KI6ZHD
On 12/04/2024 05:29 PM, Christopher
Molnar KO4YAW via groups.io wrote:
toggle quoted message
Show quoted text
Hello All!
?
I am seeing the following error messages regarding bad APRS
packet segments, but? these are from packet stations and are
valid. Is there anyway to turn off, or adjust, APRS error
messages?
?
?
[0L] KO4YAW-7>BEACON:KO4YAW: Node: KO4YAW-7 BBS:
KO4YAW-1 CHAT: KO4YAW-2 Sysop: Chris
[0L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT:
KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
[1L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT:
KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan
0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan
0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan
1
KISS protocol set Persistence = 64, chan 1
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan
1
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 1
KISS protocol set FullDuplex = 0, chan 1
N6CTA-7 audio level = 75 ? FX.25 ? 0
[0]
N6CTA-7>BEACON:!3405.20N/11748.25WB-1/B -4/C 14.105L
DM14 FARPN
Position, BBS or PBBS
Use of "BEACON" in the
destination field is obsolete. ?You can help to improve
the quality of APRS signals.
Tell the sender (N6CTA-7) to
use the proper product identifier from
?
N 34 05.2000, W 117 48.2500
-1/B -4/C 14.105L DM14 FARPN
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan
0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan
0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
?
?
I also see similar messages with call signs in the same place
as BEACON. For example if one station is contacting another.?
XXXX>KXXXX-1 there is a message that comes up and says that K
is not in the correct place for an APRS packet.
Thanks!
-Chris KO4YAW
|
Question on APRS error messages
Hello All!
?
I am seeing the following error messages regarding bad APRS packet segments, but? these are from packet stations and are valid. Is there anyway to turn off, or adjust, APRS error messages?
?
?
[0L] KO4YAW-7>BEACON:KO4YAW: Node: KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 Sysop: Chris
[0L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
[1L] KO4YAW-7>ID:BPQ32 Node:KO4YAW-7 BBS: KO4YAW-1 CHAT: KO4YAW-2 QTH Aurora, CO USA GRID:DM79oq75 <0x0d>
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 1
KISS protocol set Persistence = 64, chan 1
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 1
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 1
KISS protocol set FullDuplex = 0, chan 1
N6CTA-7 audio level = 75 ? FX.25 ? 0
[0] N6CTA-7>BEACON:!3405.20N/11748.25WB-1/B -4/C 14.105L DM14 FARPN
Position, BBS or PBBS
Use of "BEACON" in the destination field is obsolete. ?You can help to improve the quality of APRS signals.
Tell the sender (N6CTA-7) to use the proper product identifier from https://github.com/aprsorg/aprs-deviceid?
N 34 05.2000, W 117 48.2500
-1/B -4/C 14.105L DM14 FARPN
KISS protocol set TXDELAY = 10 (*10mS units = 100 mS), chan 0
KISS protocol set Persistence = 64, chan 0
KISS protocol set SlotTime = 10 (*10mS units = 100 mS), chan 0
KISS protocol set TXtail = 10 (*10mS units = 100 mS), chan 0
KISS protocol set FullDuplex = 0, chan 0
?
?
I also see similar messages with call signs in the same place as BEACON. For example if one station is contacting another.? XXXX>KXXXX-1 there is a message that comes up and says that K is not in the correct place for an APRS packet.
Thanks!
-Chris KO4YAW
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
I found this one:?? It seems to have a bit of documentation and a couple of accessories.?
I ordered one to test.
On Tue, Dec 3, 2024 at 11:37?AM Tobias Bj?rklind via <tobias= [email protected]> wrote: On ebay and aliexpress and similar sites there has recently turned up something called USB2RIG, which looks like a thumb drive with two 3.5mm jacks on one end.
?
e.g.:
?
Has anyone tried one of these?
?
Thanks
Tobias /SM0TGY
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
Hi Gil,
The Digirig (and presumably the usb2rig as well since it seems to be a clone of the digirig) contains in a really tiny package:
- a bus-powered USB Hub
- a C-Media CM-108 USB Sound Card (but without using GPIO pins) for audio in/out
- a FTDI USB RS-232 interface for both logic level and RS-232 serial rig control
It is ideal for mobile operation due to its light weight, compact size, low power consumption and simple wiring (only one USB cable to the computer to provide power, audio and serial interfaces).
For my purposes, I prefer the DRA-series from Masters Communications but I do understand the purpose of the Digirig devices and if I had a radio with rig-control capability would probably want one.
73,
Thomas
KK6FPP
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
I can't seem to figure out what the purpose of this is. It appears to me to be a USB sound card, at which point, as I understand it, you could use vox and be good to go. If this has an output of some sort for dedicated PTT it would seem to be more like a CM108, which combines the sound card and some I/O. What I don't understand is why not use a USB sound card and a CAT interface, then PTT, QSY, etc are all covered.
Hi Jon,
There is a HUGE difference between capabilities listed in a sales/marketing product description and detailed documentation (which would explain how to select those different modes of operation). Keep in mind that the usb2rig is sold without any documentation.
The PCB pictures linked by John, WB2OSZ shows a 3x3 solder pad with pcb-printing sufficient to explain its usage.
While the layout on the PCB differs from the digirig, the 3x3 solder pad is in fact the same as for the digirig version 1.9 (same 3 configuration options).
Also in common with the digirig are two separate 2-pad solder jumpers. The one labeled 3.3V is used to provide power for the isolation circuit of the TX500 from Lab599 (most people will not need that, but some may be confused about that solder pad and 3.3V versus 5V logic levels). The one labeled ATT provides audio input attenuation (20dB in the digirig).
As for PTT, the similarity with the digirig suggests that PTT is driven by RTS on the serial port. Some product descriptions I have seen for the usb2rig mention vox (without being clear whether they expect vox in the radio to be used or whether the usb2rig has an internal vox circuit).
There are no jumpers or solder pads to change behavior of PTT, suggesting that just like the real digirig it is firmly tied to RTS on the serial port.
73,
Thomas
KK6FPP
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
Hi Jon,
There is a HUGE difference between capabilities listed in a sales/marketing product description and detailed documentation (which would explain how to select those different modes of operation). Keep in mind that the usb2rig is sold without any documentation.
The PCB pictures linked by John, WB2OSZ shows a 3x3 solder pad with pcb-printing sufficient to explain its usage.
While the layout on the PCB differs from the digirig, the 3x3 solder pad is in fact the same as for the digirig version 1.9 (same 3 configuration options).
Also in common with the digirig are two separate 2-pad solder jumpers. The one labeled 3.3V is used to provide power for the isolation circuit of the TX500 from Lab599 (most people will not need that, but some may be confused about that solder pad and 3.3V versus 5V logic levels). The one labeled ATT provides audio input attenuation (20dB in the digirig).
As for PTT, the similarity with the digirig suggests that PTT is driven by RTS on the serial port. Some product descriptions I have seen for the usb2rig mention vox (without being clear whether they expect vox in the radio to be used or whether the usb2rig has an internal vox circuit).
There are no jumpers or solder pads to change behavior of PTT, suggesting that just like the real digirig it is firmly tied to RTS on the serial port.
73,
Thomas
KK6FPP
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
This listing has an interior photo with pinouts shown on the PCB.
?
?
The big question is:? Does PTT come from serial port RTS or from a GPIO pin on the USB audio chip?? Maybe selected by jumpers?
?
73,
John WB2OSZ
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
Well, in the description it says this:
"5. VERSATILE SOUND AND SERIAL PORTS: Defines sound input and output, PPT control (USB serial control, non sound), and serial port input and output (default TTL, can be changed to 232) with optional 3.3V voltage output support for LAB599 TX500 and reserve expansion port."
So, sounds like it supports 5 vdc natively and can be utilized for 3.3 vdc.
Sincerely, Jon
Jon Adams, PE, MSEE
Senior Member, IEEE
+1 480.628.6686
On Tue, Dec 3, 2024 at 12:22?PM Thomas Leibold via <leibold= [email protected]> wrote: I agree with Mark that this appears to be a digirig clone, but would like to add the warning that none of the sellers (all the usual suspects at ali express, amazon, ebay) I saw includes detailed documentation which is important for a product like this (which depending on the internal configuration may produce 0 to 3.3V or 0 to 5V or up to +/- 15V on the serial port!).
Depending on how closely the PCB inside matches that of the real digirig, configuring it to match your radio could turn into a guessing game.
73,
Thomas
KK6FPP
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
I agree with Mark that this appears to be a digirig clone, but would like to add the warning that none of the sellers (all the usual suspects at ali express, amazon, ebay) I saw includes detailed documentation which is important for a product like this (which depending on the internal configuration may produce 0 to 3.3V or 0 to 5V or up to +/- 15V on the serial port!).
Depending on how closely the PCB inside matches that of the real digirig, configuring it to match your radio could turn into a guessing game.
73,
Thomas
KK6FPP
|
Re: USB2RIG chinese interface - allegedly soundcard and PTT
This looks like a rip-off of the DigiRig.. (Mostly because it has both audio and serial connections.?
73 de K6EF
toggle quoted message
Show quoted text
On Dec 3, 2024, at 10:37?AM, Tobias Bj?rklind <tobias@...> wrote:
? On ebay and aliexpress and similar sites there has recently turned up something called USB2RIG, which looks like a thumb drive with two 3.5mm jacks on one end.
?
e.g.:
?
Has anyone tried one of these?
?
Thanks
Tobias /SM0TGY
|
USB2RIG chinese interface - allegedly soundcard and PTT
On ebay and aliexpress and similar sites there has recently turned up something called USB2RIG, which looks like a thumb drive with two 3.5mm jacks on one end.
?
e.g.:
?
Has anyone tried one of these?
?
Thanks
Tobias /SM0TGY
|
Re: Radios not taking turns properly in connected mode packet
Edited at 23:13 Eastern Time
?
Sure John,
Both systems are using AGW, the PTT is wired, and persist=63 and slottime=12. They are both manually set, so probably not default.
?
Thomas,
I will get console output with timestamps as soon as I get back to the shack.
?
73,
Matt KQ4RST
|
Re: Radios not taking turns properly in connected mode packet
Hi, You say: As you can see it, starts off really smooth, but eventually the node computer tries to send the same packet 5 times without waiting for acknowledgement. I don't see this because your logfile doesn't show timestamps. In order to see "stepping on each other" it would also be helpful to see the logs from both direwolf instances (for the same timeframe), so that we can tell whether the other station is indeed transmitting or whether it has gone silent. On my computers I'm using the direwolf command line option: -T "%F_%T" which adds date and time to the console output (in your case, just logging the time would be sufficient). 73, Thomas KK6FPP
|
Re: Radios not taking turns properly in connected mode packet
Could you provide more details?
?
(1) is the KISS or AGW interface used between direwolf and the other application?
(2) is the PTT control wired or is VOX being used in a radio?
(3) were PERSIST and SLOTTIME using default or explicit values?
?
73,
John WB2OSZ
|
Radios not taking turns properly in connected mode packet
Hello all,
?
I'm running direwolf and linbpq on one computer and direwolf and QtTermTCP on another computer. The computers have radios between them. I'm trying to access the bpq node with the QtTermTCP. At times, there is a lot of text to be sent over at once. When I connect and start the app that makes the text in linbpq, everything is synced up great, but after a few packets, the radios start stepping on each other's feet.?
?
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(SABM cmd, p=1)
[0L] KQ4RST-7>KQ4RST:(UA res, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(I cmd, n(s)=0, n(r)=0, p=0, pid=0xf0)web<0x0d>
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=0, n(r)=1, p=1, pid=0xf0)*** Connected to WEB ? ? ? ? <0x0d>
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=1, f=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=1, n(r)=1, p=1, pid=0xf0)Hello KQ4RST, welcome to Simple Packet Web - by PE1RRR Versi
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
KQ4RST audio level = 51 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=2, f=1)
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=2, n(r)=1, p=1, pid=0xf0)on 0.2.4, last modified by KQ4RST on 10/04/2024.<0x0d><0x0d>***PLEASE<0x20>
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=3, f=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=3, n(r)=1, p=1, pid=0xf0)USE RESPONSIBLY! NO OBSCENITY OR PECUNIARY INTERESTS!***<0x0d>(yo
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=3, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=4, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=4, f=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=3, n(r)=1, p=1, pid=0xf0)USE RESPONSIBLY! NO OBSCENITY OR PECUNIARY INTERESTS!***<0x0d>(yo
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=4, n(r)=1, p=1, pid=0xf0)ur activity is being logged)<0x0d><0x0d>Current time is 05:02:17<0x0d><0x0d>MAIN
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=4, n(r)=1, p=1, pid=0xf0)ur activity is being logged)<0x0d><0x0d>Current time is 05:02:17<0x0d><0x0d>MAIN
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=4, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(REJ res, n(r)=4, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=5, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(REJ res, n(r)=5, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=5, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=5, f=1)
KQ4RST audio level = 50 ? FX.25 ? __000__
[0.3] KQ4RST>KQ4RST-7:(RR res, n(r)=5, f=1)
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=4, n(r)=1, p=1, pid=0xf0)ur activity is being logged)<0x0d><0x0d>Current time is 05:02:17<0x0d><0x0d>MAIN
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=4, n(r)=1, p=1, pid=0xf0)ur activity is being logged)<0x0d><0x0d>Current time is 05:02:17<0x0d><0x0d>MAIN
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=5, n(r)=1, p=1, pid=0xf0) MENU<0x0d><0x0d>[1] Enter your own web address<0x0d>[2] Enter search terms
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=5, n(r)=1, p=1, pid=0xf0) MENU<0x0d><0x0d>[1] Enter your own web address<0x0d>[2] Enter search terms
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=5, n(r)=1, p=1, pid=0xf0) MENU<0x0d><0x0d>[1] Enter your own web address<0x0d>[2] Enter search terms
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=5, n(r)=1, p=1, pid=0xf0) MENU<0x0d><0x0d>[1] Enter your own web address<0x0d>[2] Enter search terms
[0L] KQ4RST-7>KQ4RST:(I cmd, n(s)=5, n(r)=1, p=1, pid=0xf0) MENU<0x0d><0x0d>[1] Enter your own web address<0x0d>[2] Enter search terms
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(RR cmd, n(r)=1, p=1)
[0L] KQ4RST-7>KQ4RST:(DISC cmd, p=1)
?
?
As you can see it, starts off really smooth, but eventually the node computer tries to send the same packet 5 times without waiting for acknowledgement. I thought it might have something to do with direwolf, so I came here. It seems like the computers just aren't listening/responding to each other after a certain point. Is there anything in the config that might dictate this? Any help would be appreciated.
|
Re: Direwolf won't send APRS messages
Any help would be appreciated…
tell me a wee bit more about the PI setup 1 are you using a window manager (GUI) or on a ‘dumb terminal’? 2 where are you with the power supply for the PI? ?Is it a decent unit that can handle the spikes OK - or is it cheap PSU - how many amps can it deliver?? 3 The PTT press - can you see any indication on the Baofeng that it is transmitting? (I can switch the TX light on on mine) ?or does it all go wrong before the TX signal hits the radio? 4 If you run the program - but without the PTT connected - does it run OK (I appreciate it wont TX) - in which case likely to be interference - get the radio antenna on a flying lead and away from the kit Cant think of anything else for now
My setup: Raspberry PI 4, DireWolf 1.7, DigiRig, Baofeng ? ? Digirig at /dev/ttyUSB0 ? ? card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio] ? ? ? ? Subdevices: 1/1
? ? ? ? Subdevice #0: subdevice #0
? ? ADEVICE ?plughw:1,0
I can? receive messages just fine, and send messages over IGate, but as soon as I turn on PTT, by uncomenting: ? ??PTT /dev/ttyUSB0 RTS
And when direwolf trys?to transmit, I get this:
One or more sometimes many of these messages: [0L] KA7RLV-10>APDW17,WIDE1-1,WIDE2-1:!4817.19NS11722.44W#PHG3040Usk WA US Audio input device 0 error code -32: Broken pipe This is most likely caused by the CPU being too slow to keep up with the audio stream. Use the "top" command, in another command window, to look at CPU usage. This might be a temporary condition so we will attempt to recover a few times before giving up. If using a very slow CPU, try reducing the CPU load by using -P- command line option for 9600 bps or -D3 for slower AFSK .
I have tried?using the -P- option when running direwolf, no real difference.
Sometimes I get this after the other errors: ALSA lib pcm.c:8573:(snd_pcm_recover) cannot recovery from overrun, prepare failed: Input/output error Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Terminating after audio input failure.
|
Re: Direwolf won't send APRS messages
Also move the antenna farther away from the other components.
(Don't use a rubber ducky on top of the radio.)
?
73,
John WB2OSZ
|
Re: Direwolf won't send APRS messages
Possibly RFI interfering with the USB susbsytem.
Try:
- lowering RF power out
- Putting ferrite beads on the cables.
toggle quoted message
Show quoted text
On Nov 26, 2024, at 3:30?PM, Richard Vantrease via groups.io <richvantrease@...> wrote:
? Any help would be appreciated...
My setup: Raspberry PI 4, DireWolf 1.7, DigiRig, Baofeng ? ? Digirig at /dev/ttyUSB0 ? ? card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio] ? ? ? ? Subdevices: 1/1
? ? ? ? Subdevice #0: subdevice #0
? ? ADEVICE ?plughw:1,0
I can? receive messages just fine, and send messages over IGate, but as soon as I turn on PTT, by uncomenting: ? ??PTT /dev/ttyUSB0 RTS
And when direwolf trys?to transmit, I get this:
One or more sometimes many of these messages: [0L] KA7RLV-10>APDW17,WIDE1-1,WIDE2-1:!4817.19NS11722.44W#PHG3040Usk WA US Audio input device 0 error code -32: Broken pipe This is most likely caused by the CPU being too slow to keep up with the audio stream. Use the "top" command, in another command window, to look at CPU usage. This might be a temporary condition so we will attempt to recover a few times before giving up. If using a very slow CPU, try reducing the CPU load by using -P- command line option for 9600 bps or -D3 for slower AFSK .
I have tried?using the -P- option when running direwolf, no real difference.
Sometimes I get this after the other errors: ALSA lib pcm.c:8573:(snd_pcm_recover) cannot recovery from overrun, prepare failed: Input/output error Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Terminating after audio input failure.
|
Direwolf won't send APRS messages
Any help would be appreciated...
My setup: Raspberry PI 4, DireWolf 1.7, DigiRig, Baofeng ? ? Digirig at /dev/ttyUSB0 ? ? card 1: Device [USB Audio Device], device 0: USB Audio [USB Audio] ? ? ? ? Subdevices: 1/1
? ? ? ? Subdevice #0: subdevice #0
? ? ADEVICE ?plughw:1,0
I can? receive messages just fine, and send messages over IGate, but as soon as I turn on PTT, by uncomenting: ? ??PTT /dev/ttyUSB0 RTS
And when direwolf trys?to transmit, I get this:
One or more sometimes many of these messages: [0L] KA7RLV-10>APDW17,WIDE1-1,WIDE2-1:!4817.19NS11722.44W#PHG3040Usk WA US Audio input device 0 error code -32: Broken pipe This is most likely caused by the CPU being too slow to keep up with the audio stream. Use the "top" command, in another command window, to look at CPU usage. This might be a temporary condition so we will attempt to recover a few times before giving up. If using a very slow CPU, try reducing the CPU load by using -P- command line option for 9600 bps or -D3 for slower AFSK .
I have tried?using the -P- option when running direwolf, no real difference.
Sometimes I get this after the other errors: ALSA lib pcm.c:8573:(snd_pcm_recover) cannot recovery from overrun, prepare failed: Input/output error Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Audio input device 0 error code -19: No such device Terminating after audio input failure.
|
Christopher Molnar KO4YAW
Tobias Bj?rklind
iainmaoileoin
Richard Vantrease