direwolf

History

wb2osz 5a54179c97 more work on mic-e device id.		2024-02-16 02:52:28 +00:00
..
CMakeLists.txt	Use tocalls.yaml rather than tocalls.txt which is no longer maintained.	2023-12-23 15:57:03 +00:00
README.txt	more work on mic-e device id.	2024-02-16 02:52:28 +00:00
symbols-new.txt	Update tocalls.txt and symbols-new.txt	2022-02-21 16:30:03 +00:00
symbolsX.txt	reshape the repository moving objects to folders based on subject	2019-11-09 08:26:01 +01:00
tocalls.yaml	more work on mic-e device id.	2024-02-16 02:52:28 +00:00

README.txt

tocalls.yaml contains the encoding for the device/system/software
identifier which created the packet.
Knowing what generated the packet is very useful for troubleshooting.
TNCs, digipeaters, and IGates must not change this. 

For MIC-E format, well... it's complicated.
See  Understanding-APRS-Packets.pdf.   Too long to repeat here.

For all other packet types, the AX.25 destination, or "tocall" field
contains a code for what generated the packet.
This is of the form AP????.    For example, APDW18 for direwolf 1.8.

The database of identifiers is currently maintained by Hessu, OH7LZB.

You can update your local copy by running:

wget https://raw.githubusercontent.com/aprsorg/aprs-deviceid/main/tocalls.yaml