<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<pre style="color: rgb(255, 255, 255); font-style: normal; font-variant-ligatures: normal; font-variant-caps: normal; font-weight: 400; letter-spacing: normal; orphans: 2; text-align: start; text-indent: 0px; text-transform: none; widows: 2; word-spacing: 0px; -webkit-text-stroke-width: 0px; text-decoration-thickness: initial; text-decoration-style: initial; text-decoration-color: initial; overflow-wrap: break-word; white-space: pre-wrap;"><a class="moz-txt-link-freetext" href="https://www.ietf.org/rfc/rfc793.txt">https://www.ietf.org/rfc/rfc793.txt</a>
TRANSMISSION CONTROL PROTOCOL
DARPA INTERNET PROGRAM
PROTOCOL SPECIFICATION
September 1981
It's not the software we're interested in, it's the protocol. Protocols live for decades, when they're written well and implemented effectively. OpenTrac was written with the explicit purpose of taking what we learned from APRS, and other low-bitrate, size-constrained on-air protocols and building a better mousetrap. And, while microcontrollers have gotten more powerful, the most common embedded systems framework at the hobbyist level is still Arduino, introduced in 2006. The javAPRSLib parser library is over 5k Source Lines Of Code and sits at a cool 188kb of source code. I guess, technically, I could put it on an ESP32, but it's a lot more efficient to use on of the 500 SLOC C parsers that's a couple hundred bytes when compiled, on something that will run for a 3 days on a 1000mAh lithium battery.
If Scott's interested, I'd ask him to maybe write something for PSR proposing a revival of OpenTrak. Once I get past my current project, I intend to sit down and really look at the protocol and see what it would take to implement it on more modern microcontrollers. I'm sure I'll have questions and suggestions.
This LoRa stuff, honestly, it's pretty slick. It's robust, it can be run on Ham frequencies, and since we apparently gave up on the whole "proprietary modulation schemes aren't encryption" fight with D-Star (I can taste the bile in my mouth), it wouldn't hurt to embrace it for public service events where a dozen or more trackers are needed. I just got a 5 pack of these (<a class="moz-txt-link-freetext" href="https://heltec.org/project/wireless-tracker/">https://heltec.org/project/wireless-tracker/</a>) for less than $100. Coupled with a 3d printed case and a $8 3000mAh battery, you're tracking 5 key assets at your next public service event for 1/3 the cost of a D-74. Do it with a 433Mhhz LoRa stick, and you're 'providing a service that only licensed hams can provide'.
I started this thread because I got the impression that Bob didn't want non-amateur use of the APRS protocol. If that's not the case, it's all kind of moot. But if it opens the door to discussions of new protocols and new applications of our technology that can serve to keep us relevant, well, that's not a bad thing.
de AB0OO
John
</pre>
<p></p>
<div class="moz-cite-prefix">On 8/13/23 12:19, wa7skg wrote:<br>
</div>
<blockquote type="cite"
cite="mid:cf27bb61-cb84-c701-92d7-a46d1f069e28@wa7skg.com">I'd be
concerned that nothing appears to have been done with OpenTrac in
almost 20 years. Technology moves a lot faster than that. Pretty
much everything that OpenTrac originally addressed has long since
been incorporated into modern APRS clients and protocols.
<br>
<br>
I'd be interested to see what applications currently are
supporting 20 year old software.
<br>
<br>
Michael WA7SKG
<br>
<br>
<br>
Gregg Wonderly wrote on 8/13/23 10:11 AM:
<br>
<blockquote type="cite">We really need to open the door to
investigation of OpenTrac. It provides some much more
consumable structure that avoids the append this string in this
format “design” principals that make APRS difficult to create
parsers for.
<br>
<br>
You’ll find OpenTrac (<a class="moz-txt-link-freetext" href="http://opentrac.org/">http://opentrac.org/</a>) support already in
some popular trackers!
<br>
<br>
Gregg Wonderly
<br>
W5GGW
<br>
<br>
Sent from my iPhone
<br>
</blockquote>
<br>
_______________________________________________
<br>
aprssig mailing list
<br>
<a class="moz-txt-link-abbreviated" href="mailto:aprssig@lists.tapr.org">aprssig@lists.tapr.org</a>
<br>
<a class="moz-txt-link-freetext" href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a>
<br>
</blockquote>
</body>
</html>