Support for Destination Address Digipeating #70

Closed
opened 2026-10-05 05:33:39 +02:00 by adam · 1 comment
Owner

Hello, the T-Echo firmware by cfr34k (https://github.com/cfr34k/t-echo-lora-aprs) encodes the digi path via the destination field.

For example APLETK-1 should translate to digipeating the same as WIDE1-1, as specified in http://www.aprs.org/doc/APRS101.PDF , page 15, "Generic APRS Digipeater Path"

However this is not followed in this firmware. Please can support be added to allow this type of digipeating.

Using this format decreases the length of the packet and will help with decoding errors and congestion.

Thanks,
Dayle M0OUE

Hello, the T-Echo firmware by cfr34k (https://github.com/cfr34k/t-echo-lora-aprs) encodes the digi path via the destination field. For example `APLETK-1` should translate to digipeating the same as `WIDE1-1`, as specified in http://www.aprs.org/doc/APRS101.PDF , page 15, "Generic APRS Digipeater Path" However this is not followed in this firmware. Please can support be added to allow this type of digipeating. Using this format decreases the length of the packet and will help with decoding errors and congestion. Thanks, Dayle M0OUE <!-- github-sync-id:2298860820 -->
adam closed this issue 2026-10-05 05:33:39 +02:00
Author
Owner

This feature is generally considered to be obsolete.
Discussion here: https://groups.io/g/APRS/topic/106911039#msg2836

73,
John WB2OSZ

This feature is generally considered to be obsolete. Discussion here: https://groups.io/g/APRS/topic/106911039#msg2836 73, John WB2OSZ <!-- github-comment-id:2206371870 -->
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#70