<div dir="auto"><div>APRS could continue to function for those devices as a multimode network. If the digipeaters and igates evolved to decode more efficient encodings and higher bitrates in addition to the standard 1200 baud ax25 then legacy devices could still transmit just fine while newer devices and those with strong signals could use modes that would use up less airtime. Even if digipeaters digipeated everything as 1200baud ax25 it would increase the capacity of the network, evolve the infrastructure and encourage manufacturers to support newer modes.</div><div dir="auto"><br></div><div dir="auto">Even just adding 9600baud to the mix would have advantages. </div><div dir="auto"><br></div><div dir="auto">-Jess</div><div dir="auto">K5LLI<br><br><div class="gmail_quote" dir="auto"><div dir="ltr" class="gmail_attr">On Sun, Feb 13, 2022, 11:30 PM Randy Hall <<a href="mailto:aa6rh@socorad.io">aa6rh@socorad.io</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr">Hey guys, I love the blue sky nature of this. Seriously. I use Direwolf for a couple of big footprint digi/igate sites, and I'm hugely excited about M17 as a data and digital voice mode.<div><br></div><div>But there is a ridiculous amount of installed hardware that only speaks 1200 baud AX.25 AFSK packet, and it needs to be comprehended in whatever vision we might create.</div><div><br></div><div>That isn't to say the physical layer definition shouldn't be expansive to include and accommodate many different OTA modes. But physical layer is just part of it.</div><div><br></div><div>As for OpenTrac, I tried visiting <a href="http://opentrac.net/" target="_blank" rel="noreferrer">http://opentrac.net/</a> and was visited with a "site down" notification. Is the site meant to be offline?</div><div><br></div><div>--R<br clear="all"><div><div dir="ltr" data-smartmail="gmail_signature"><div dir="ltr"><div><i>--</i></div><i><b>Randy AA6RH</b></i><div><i><a href="mailto:aa6rh@socorad.io" target="_blank" rel="noreferrer">aa6rh@socorad.io</a></i></div><div><i>Grid Square: CM88pl</i></div><div><i><a href="https://www.qrz.com/db/aa6rh" target="_blank" rel="noreferrer">QRZ Profile</a><br></i></div><div><i>Sonoma County DMR: <a href="https://brandmeister.network/?page=lh&jsonquery=%7B%22condition%22%3A%22AND%22%2C%22rules%22%3A%5B%7B%22id%22%3A%22DestinationID%22%2C%22field%22%3A%22DestinationID%22%2C%22type%22%3A%22integer%22%2C%22input%22%3A%22text%22%2C%22operator%22%3A%22equal%22%2C%22value%22%3A%2231707%22%7D%5D%7D" target="_blank" rel="noreferrer">BrandMeister 31707</a></i></div></div></div></div><br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 13, 2022 at 9:28 PM Mobilinkd LLC <<a href="mailto:mobilinkd@gmail.com" target="_blank" rel="noreferrer">mobilinkd@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr">I helped define the M17 data modes, which includes a raw packet mode. M17 uses 4-FSK modulation with FEC. There is experimental firmware available for the Mobilinkd TNC3 and NucleoTNC that will do M17 packet mode. I've had an M17 APRS repeater up at times in Chicago.<div><br></div><div>Data modes on M17 approaches 5kbps throughput. It uses 4800 symbols/sec, 9600bps, with a slightly punctured convolutional code.<br><div><br></div><div><a href="https://m17project.org/" target="_blank" rel="noreferrer">https://m17project.org/</a></div><div><div><br clear="all"><div><div dir="ltr">Kind Regards,<br><br>Rob Riggs WX9O<br>Mobilinkd LLC<br></div></div><br></div></div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Sun, Feb 13, 2022 at 10:54 PM Gregg Wonderly <<a href="mailto:gregg@wonderly.org" target="_blank" rel="noreferrer">gregg@wonderly.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="auto">OpenTrac is an even better idea and more extensible and more easily processed than APRS packets! Let’s really take a moment to reflect on what it could mean to start with a better solution end to end!<div><br></div><div>Gregg<br><br><div dir="ltr">Sent from my iPhone</div><div dir="ltr"><br><blockquote type="cite">On Feb 13, 2022, at 6:32 PM, John Langner WB2OSZ <<a href="mailto:wb2osz@comcast.net" target="_blank" rel="noreferrer">wb2osz@comcast.net</a>> wrote:<br><br></blockquote></div><blockquote type="cite"><div dir="ltr"><div><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The AX.25 and APRS protocol specifications say nothing<u></u><u></u></p><p class="MsoNormal"> at all about modems.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The reason that we are using 1200 bps is because early <u></u><u></u></p><p class="MsoNormal">packet radio developers, in Canada, in the late 1970s, happened <u></u><u></u></p><p class="MsoNormal">to acquire a pile of old Bell 202 modems for 75 cents each.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">The method that we use for 9600 bps was developed in<u></u><u></u></p><p class="MsoNormal">the late 1980s. It has been widely implemented but won't<u></u><u></u></p><p class="MsoNormal">work with the microphone and speaker connections because<u></u><u></u></p><p class="MsoNormal">the audio processing distorts the signal and limits the bandwidth.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">In the early 1990s, multiple TNC vendors produced products capable<u></u><u></u></p><p class="MsoNormal">of 2400 bps: MFJ-2400, AEA PK232-2400, Kantronics KPC-2400.<u></u><u></u></p><p class="MsoNormal">Maybe if other vendors had offered the same we would all be using<u></u><u></u></p><p class="MsoNormal">2400 bps today.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">With the shift from hardware modems to software modems,<u></u><u></u></p><p class="MsoNormal">the possibilities are endless. Upgrades are easy. <u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Two methods of Forward Error Correction are currently being used:<u></u><u></u></p><p><span>(1)<span style="font:7pt "Times New Roman""> </span></span>FX.25 which is completely interoperable with original AX.25.<u></u><u></u></p><p><span>(2)<span style="font:7pt "Times New Roman""> </span></span>IL2P which has less overhead but is not compatible.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">Better alternatives are available today for those who want to use <u></u><u></u></p><p class="MsoNormal">them. The problem is trying to convince most of the installed base<u></u><u></u></p><p class="MsoNormal">to break free of a precedent set more than 40 years ago.<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p><p class="MsoNormal">73,<u></u><u></u></p><p class="MsoNormal">John WB2OSZ<u></u><u></u></p><p class="MsoNormal"><u></u> <u></u></p></div><span>_______________________________________________</span><br><span>aprssig mailing list</span><br><span><a href="mailto:aprssig@lists.tapr.org" target="_blank" rel="noreferrer">aprssig@lists.tapr.org</a></span><br><span><a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" target="_blank" rel="noreferrer">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a></span><br></div></blockquote></div></div>_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org" target="_blank" rel="noreferrer">aprssig@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="noreferrer noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</blockquote></div>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org" target="_blank" rel="noreferrer">aprssig@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="noreferrer noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</blockquote></div>
_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@lists.tapr.org" target="_blank" rel="noreferrer">aprssig@lists.tapr.org</a><br>
<a href="http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org" rel="noreferrer noreferrer" target="_blank">http://lists.tapr.org/mailman/listinfo/aprssig_lists.tapr.org</a><br>
</blockquote></div></div></div>