adam/LoRa_APRS_iGate
1
0 Fork 0
mirror of https://github.com/richonguzman/LoRa_APRS_iGate.git synced 2026-10-30 18:41:58 +01:00
Code Issues 55 Packages Projects Releases Wiki Activity

Possible leading zero bug for Callsign designations. #221

New Issue
Closed
opened 2026-10-05 05:51:13 +02:00 by adam · 5 comments
adam commented 2026-10-05 05:51:13 +02:00
Owner
Copy link
Copy source

There may be a leading zero bug for Callsign designations.

I have had an issue that prevented the iGate from processing received packets correctly and proved tricky to identify.

Superficially everything appears to be correctly function however RF packets are not heard.

If you define a callsign to be Callsign-01 rather than Callsign-1 this will result in iGate behaving oddly and not appearing to receive RF packets over the air. Changing from a -01 designation to a -1 designation fully corrects the issue. The callsign structure requires validation on entry.

Therefore leading zeros should probably be prohibited by the callsign input code, or alternatively, permitted and handled correctly within the code. I only tested -00, -01, -02, -03 and -05, all failed. -10 -11 etc. are OK.

I am using the latest iGate software with a Heltek Wireless Tracker board.

Thanks.

There may be a leading zero bug for Callsign designations. I have had an issue that prevented the iGate from processing received packets correctly and proved tricky to identify. Superficially everything appears to be correctly function however RF packets are not heard. If you define a callsign to be Callsign-01 rather than Callsign-1 this will result in iGate behaving oddly and not appearing to receive RF packets over the air. Changing from a -01 designation to a -1 designation fully corrects the issue. The callsign structure requires validation on entry. Therefore leading zeros should probably be prohibited by the callsign input code, or alternatively, permitted and handled correctly within the code. I only tested -00, -01, -02, -03 and -05, all failed. -10 -11 etc. are OK. I am using the latest iGate software with a Heltek Wireless Tracker board. Thanks. <!-- github-sync-id:3458721692 -->
adam closed this issue 2026-10-05 05:51:13 +02:00
adam commented 2026-10-05 05:51:14 +02:00
Author
Owner
Copy link
Copy source

Hi, which are the station not getting heard by this igate?

does this "def" problem appears with the igate calling changed and disappears when it is corrected ?

Hi, which are the station not getting heard by this igate? does this "def" problem appears with the igate calling changed and disappears when it is corrected ? <!-- github-comment-id:3340013886 -->
adam commented 2026-10-05 05:51:14 +02:00
Author
Owner
Copy link
Copy source

I just tried changing my call sign on my Heltec V3 board from N7UV-3 to N7UV-03.

Image

Then, i looked at both the "Received Packets" display and the serial output (via PuTTY). This is what I am seeing:
Image

Interestingly, lora-aprs.live does seem to treat the two callsigns as different. Here's N7UV-03 (which has been around only the past 10 minutes)

Image

And simultaneously, lora-aprs.live shows the last packet from N7UV-3 just before it switched to -03.

Image

and aprs.fi shows the "new" -03 being collected at aprs.fi while -03 is configured to only transmit via RF, and not be connected via the Internet. That shows me that it is transmitting, and is being received by N7UV-40 which is the igate/digi at the house.

FInally, i set up N7UV-03 to be an igate, and here's what I'm seeing on the serial port.

Image

as can be seen, configured as N7UV-03 doesn't change the igate behavior, at least as far as I can see.

Cheers and 73 - Jon N7UV

I just tried changing my call sign on my Heltec V3 board from N7UV-3 to N7UV-03. <img width="838" height="393" alt="Image" src="https://github.com/user-attachments/assets/ebf0f8b9-2c81-441e-aca6-66f184dfdb7f" /> Then, i looked at both the "Received Packets" display and the serial output (via PuTTY). This is what I am seeing: <img width="1263" height="679" alt="Image" src="https://github.com/user-attachments/assets/20ba1314-03e2-4527-a84d-f89de073aaf2" /> Interestingly, lora-aprs.live does seem to treat the two callsigns as different. Here's N7UV-03 (which has been around only the past 10 minutes) <img width="861" height="780" alt="Image" src="https://github.com/user-attachments/assets/621ea784-31f5-4058-af4b-23862a3cd9a8" /> And simultaneously, lora-aprs.live shows the last packet from N7UV-3 just before it switched to -03. <img width="854" height="646" alt="Image" src="https://github.com/user-attachments/assets/db9738a8-ed9f-4061-9180-6c183ac843e3" /> and aprs.fi shows the "new" -03 being collected at aprs.fi while -03 is configured to only transmit via RF, and not be connected via the Internet. That shows me that it is transmitting, and is being received by N7UV-40 which is the igate/digi at the house. FInally, i set up N7UV-03 to be an igate, and here's what I'm seeing on the serial port. <img width="823" height="233" alt="Image" src="https://github.com/user-attachments/assets/3cbfded6-92b7-4827-9c17-c35310840bd3" /> as can be seen, configured as N7UV-03 doesn't change the igate behavior, at least as far as I can see. Cheers and 73 - Jon N7UV <!-- github-comment-id:3340530487 -->
adam commented 2026-10-05 05:51:15 +02:00
Author
Owner
Copy link
Copy source

I will note however that the way trad ax.25 does stuff the SSID is a 4-bit nibble, with values from 0 to 15 decimal (0-F hex). I don't know how the SSID is parsed; it the parser expects the potential of a leading "1" (as in -10, -11... -15) but it doesn't anticipate a leading "0" then there could be an issue.

We really need to rethink how LoRa does the addressing and SSIDs. It's time to move beyond the constraints of old ax.25.

Cheers and 73 - Jon N7UV

I will note however that the way trad ax.25 does stuff the SSID is a 4-bit nibble, with values from 0 to 15 decimal (0-F hex). I don't know how the SSID is parsed; it the parser expects the potential of a leading "1" (as in -10, -11... -15) but it doesn't anticipate a leading "0" then there could be an issue. We really need to rethink how LoRa does the addressing and SSIDs. It's time to move beyond the constraints of old ax.25. Cheers and 73 - Jon N7UV <!-- github-comment-id:3352921502 -->
adam commented 2026-10-05 05:51:16 +02:00
Author
Owner
Copy link
Copy source

SSID should be a numerical character:

03 is not numerical, but 3 is.

SSID should be a numerical character: 03 is not numerical, but 3 is. <!-- github-comment-id:3352960557 -->
adam commented 2026-10-05 05:51:17 +02:00
Author
Owner
Copy link
Copy source

this was added as a "warning" to avoid the "0" in the new pdf manual

this was added as a "warning" to avoid the "0" in the new pdf manual <!-- github-comment-id:3398253218 -->
Sign in to join this conversation.
No Branch/Tag Specified
Labels
No items
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
adam (Adam Wojcieszonek)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: adam/LoRa_APRS_iGate#221