Aprs tracker using Baofeng 5RH pro can't be digitized on vpdigi

[Gethub-prog]

Aprs using Baofeng 5RH pro can't be digitized on vpdigi, raw packets come in, but can't be digitized... I don't know if this is from the Baofeng firmware or from vpdigi

[sq8vps]

Hi,
What do you mean by "digitized"? Are incoming packets decoded and displayed in the "monitor" mode? Does the DCD LED turn on? Have you tried adjusting the volume?
If I remember correctly, Baofengs might have some weird audio filtering potentially distorting packets, however I'm also sure I was able to receive packets with Direwolf and UV-82.

[Gethub-prog]

Thank you for responding, sorry for the typo, I mean digipeated.. yes, the problem seems to be from the Baofeng firmware, not only on the vpdigi, on other digi models it is also not digipeated.

Once again, thank you and apologize.. I really like the vpdigi, it's cheap and works well.

pls close this issue

[sq8vps]

Ok, let me understand...
The packets are not digipeated, but are they received at all? Can you see the packets being decoded in "monitor" or "KISS" mode? If so, there is a problem with your digipeater configuration that we can solve if you provide a screenshot/copy of your current configuration ("print" command in "config" mode). This might as well help us if you are not receiving any packets at all.

[Gethub-prog]

It's true that Baofeng packets are visible in monitor mode. Even though they're not digipeated, if I use another tracker on the same path, they are digipeated

Sorry, I can't provide screenshots of the configuration or the monitor mode display yet. Maybe I'll upload them another time.

[Gethub-prog]

Later I will make a audio recording from the beacon, so you can try it.

[sq8vps]

Ok, so you are receiving packets just fine and packets from one tracker are digipeated correctly, while packets from another tracker with the same path are not digipeated at all, right?
Then, it seems like there is a problem with this tracker, or at least there is some weird incompability between VP-Digi and the tracker.
Please provide me with the current VP-Digi configuration and the packet which is not being digipeated. It would be also great to see the configuration of this "incompatible" tracker.

[Gethub-prog]

OK, please give me 1 hour to upload the configuration and screenshot. I will try the vpdigi that is at my home, because the active one has been installed on the mountain.

[Gethub-prog]

this is my config

Modem: AFSK Bell 202 1200 Bd 1200/2200 Hz
Callsign: YH3NPX-1
Destination: APNV01
TXDelay (ms): 300
TXTail (ms): 30
Quiet time (ms): 300
USB: default mode: KISS
UART1: 9600 baud, default mode: KISS
UART2: 9600 baud, default mode: KISS
DAC type: PWM
Flat audio input: no
Beacon 0: On, Iv: 5, Dl: 1, WIDE2-1, !0742.81S/11342.25E#DIGIPEATER BESUKI
Beacon 1: Off, Iv: 0, Dl: 0, no path,
Beacon 2: Off, Iv: 0, Dl: 0, no path,
Beacon 3: Off, Iv: 0, Dl: 0, no path,
Beacon 4: Off, Iv: 0, Dl: 0, no path,
Beacon 5: Off, Iv: 0, Dl: 0, no path,
Beacon 6: Off, Iv: 0, Dl: 0, no path,
Beacon 7: Off, Iv: 0, Dl: 0, no path,
Digipeater: On
Alias WIDE: On, max: 2, rep: 3, traced, unfiltered
Alias : Off, max: 0, rep: 0, untraced, unfiltered
Alias : Off, max: 0, rep: 0, untraced, unfiltered
Alias : Off, max: 0, rep: 0, untraced, unfiltered
Alias -0: Off, untraced, unfiltered
Alias -0: Off, untraced, unfiltered
Alias -0: Off, untraced, unfiltered
Alias -0: Off, untraced, unfiltered
Anti-duplicate buffer hold time (s): 5
Callsign filter type: blacklist
Callsign filter list: 0 entries
KISS monitor: Off
Allow non-APRS frames: Off
FX.25 protocol: Off
FX.25 TX: Off

[Gethub-prog]

This is a recording from the UV5RH PRO beacon with firmware v2 from my friend. https://drive.google.com/file/d/15_ZjaMN2Pm8oDP2-MfjUP9JvZTFMxQ_g/view?usp=drive_link

[Gethub-prog]

If use the Baofeng type UV5RM PRO with firmware v1, it will be able to be decoded and digipeated very well. and this link for recorded audio https://drive.google.com/file/d/17okxJkEeBcMQm_SCRKqJqe9dSFn83gDd/view?usp=drive_link

[sq8vps]

The problem is that the "firmware v2" does not strictly adhere to AX.25 specification. While the reserved bits (5 and 6) should be normally set to one in all SSIDs (see section 3.12), the transmitted packets have it set to zero (res):

The AX.25 specification says (about reserved bits in SSID):

They may be used in an agreed-upon manner in individual networks. When not implemented, they are set to one.

I don't think it is agreed-upon in APRS that these are set to zero, so we should rather stick with the default and set them to one.

Currently my digipeater code just assumes that these bits are set to one and subtracts them (and in this case it results in the integer overflow), while it would be much better to mask them.

I'll fix the code in the next release and let you know when it's done. Please ask author of the Baofeng firmware to set reserved bits in SSID to one.

[Gethub-prog]

okay TNX, de YC3BVG