qAO substring is misplaced in IS-packet, when string contains a ":" #19

Closed
opened 2026-10-05 05:28:05 +02:00 by adam · 9 comments
Owner

Hi, when the string representation of the coordinates contains a ":", the placement of the "qAO"+Callsign substring is inserted at the wrong place in the IS-outputstream, which results in wrong coordinates placed at the other side of the planet.

Generated packet:
DG0UHK-9>APLC13,qAS,DB0BWL-1:!/3z,qAO,DB0BWL-1:`Q6(D>=BQLoRa-APRSCube

Should be:
DG0UHK-9>APLC13,qAS,DB0BWL-1:!/3z:`Q6(D>=BQLoRa-APRSCube,qAO,DB0BWL-1

Problem here:
https://github.com/richonguzman/LoRa_APRS_iGate/blob/79e88bb03fc1255952885a9c675dffeec10fae2d/src/aprs_is_utils.cpp#L79

Hi, when the string representation of the coordinates contains a ":", the placement of the "qAO"+Callsign substring is inserted at the wrong place in the IS-outputstream, which results in wrong coordinates placed at the other side of the planet. Generated packet: ``DG0UHK-9>APLC13,qAS,DB0BWL-1:!/3z,qAO,DB0BWL-1:`Q6(D>=BQLoRa-APRSCube`` Should be: ``DG0UHK-9>APLC13,qAS,DB0BWL-1:!/3z:`Q6(D>=BQLoRa-APRSCube,qAO,DB0BWL-1`` Problem here: https://github.com/richonguzman/LoRa_APRS_iGate/blob/79e88bb03fc1255952885a9c675dffeec10fae2d/src/aprs_is_utils.cpp#L79 <!-- github-sync-id:2083201140 -->
adam closed this issue 2026-10-05 05:28:05 +02:00
Author
Owner

hi, can you link me where to gather information about having qAS and qAO at the same packet?

this is new to me

hi, can you link me where to gather information about having qAS and qAO at the same packet? this is new to me <!-- github-comment-id:1893542001 -->
Author
Owner
I got it from here: https://aprs.fi/?c=raw&call=DG0UHK-9&limit=500&view=normal (login needed) ![image](https://github.com/richonguzman/LoRa_APRS_iGate/assets/5630762/6d97f42a-0065-4db4-833e-a938a91fab7b) <!-- github-comment-id:1893554586 -->
Author
Owner

Same packet via syslog:
Jan 12 14:43:37 nat.db0bwl.ampr.org ESP32 LoRa [APRS] - DB0BWL-1 - LoRa Rx - GPS - DG0UHK-9 / APLC13 / _ / -104dBm / -17.50dB / 434Hz / 52.45038N / 10.82962E / 9.0km
btw, im using firmware version 2023.12.07 in which you changed to packet.indexOf(":`")) and then changed it back later.
maybe that bug is already gone in newer versions?

Same packet via syslog: `Jan 12 14:43:37 nat.db0bwl.ampr.org ESP32 LoRa [APRS] - DB0BWL-1 - LoRa Rx - GPS - DG0UHK-9 / APLC13 / _ / -104dBm / -17.50dB / 434Hz / 52.45038N / 10.82962E / 9.0km ` btw, im using firmware version 2023.12.07 in which you changed to ``packet.indexOf(":`"))`` and then changed it back later. maybe that bug is already gone in newer versions? <!-- github-comment-id:1893559816 -->
Author
Owner

the change or not of. ":´" shouldn't affect the other packets

the really strange thing is that syslog is doing its job nicely but the upload into aprs-is is faulty with this.

besides the "qAS" that is not being produced by my/this firmware...

will need to dig a little more about it

the change or not of. ":´" shouldn't affect the other packets the really strange thing is that syslog is doing its job nicely but the upload into aprs-is is faulty with this. besides the "qAS" that is not being produced by my/this firmware... will need to dig a little more about it <!-- github-comment-id:1893653870 -->
Author
Owner

As you see (received by DO2DE-10) one packet before and after our incident, the string representation of the GPS-coordinates contains an :, at which position our qAO-String was misplaced into.
I got that error also 1 or 2 times before, some weeks ago from the same tracker. At roughly the same position on his way to work.

Maybe the other qAS-thing is a consequential error because the whole string was interpreted the wrong way (like the coordinates, too), and inserted by APRS.fi itself afterwards. So i would recommend to focus on the : 😁

As you see (received by DO2DE-10) one packet before and after our incident, the string representation of the GPS-coordinates contains an `:`, at which position our qAO-String was misplaced into. I got that error also 1 or 2 times before, some weeks ago from the same tracker. At roughly the same position on his way to work. Maybe the other qAS-thing is a consequential error because the whole string was interpreted the wrong way (like the coordinates, too), and inserted by APRS.fi itself afterwards. So i would recommend to focus on the `:` 😁 <!-- github-comment-id:1893715044 -->
Author
Owner

as I see is something with APLC13 tocall (which I presume is APRSCube)

maybe I miss some packet decofication of it that my FW is not filtering right the packet payload, will check it out

as I see is something with APLC13 tocall (which I presume is APRSCube) maybe I miss some packet decofication of it that my FW is not filtering right the packet payload, will check it out <!-- github-comment-id:1893974954 -->
Author
Owner

I think this is a different issue. Note the :` is a MIC-E encoded paket. We also have seen the issue that sometimes it is appened as comment.
Please update to the latest version as it should be solved. I currently test MIC-E and no problems at all.

I think this is a different issue. Note the :` is a MIC-E encoded paket. We also have seen the issue that sometimes it is appened as comment. Please update to the latest version as it should be solved. I currently test MIC-E and no problems at all. <!-- github-comment-id:1894404885 -->
Author
Owner

the fix was added as the packet upload process was fixed

the fix was added as the packet upload process was fixed <!-- github-comment-id:1962982509 -->
Author
Owner

Sorry i forgot to come back here to confirm that updating the firmware has completely fixed that problem.
Thanks!

Sorry i forgot to come back here to confirm that updating the firmware has completely fixed that problem. Thanks! <!-- github-comment-id:1962984638 -->
Sign in to join this conversation.
No labels
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#19