So as I research this, APRS has a whole bunch of different standards. They couldn't just use one and stick to it could they? Oh no! And what's more, the standards themselves have a further bunch of caveats and sub-standards.
Coding something to deal with all of this would be a challenging nightmare in a high level language like C#, but in C? Low level embedded C for that matter that has no real advanced string manipulation? It would take a team of dozens months.
I don't even know where to begin, I think MIC-E is the dominant standard so I'm going to use that and completely IGNORE everything else. I don't have the damn time. Maybe I'll add other standards in the future, but there's NO WAY I'm locking myself in here for six months to do it all at once, NO WAY!
So in short, you won't get anything out of received APRS unless it's encoded for MIC-E, and you will transmit MIC-E encoded packets, which you better hope who you are transmitting to understands. And all caveats and fringe cases will be ignored, like early beta units or Kenwood sets that thought they'd take their own approach. A line has to be drawn under the insanity and a firm "NO!" delivered.
</rant>
Bernhard Behling
2025-10-28 17:36:08 +0000 UTCSteven Pinkham
2025-10-13 16:58:32 +0000 UTCR.D.M.
2025-10-11 22:22:06 +0000 UTC