You may find it helpful to take a look at a paper I did for the TAPR Digital Communications Conference: <br><br><font size="2"><a href="http://www.tnc-x.com/dcc.doc"><font face="Arial, Helvetica, sans-serif"><i>PIC-et
Radio: How to Send AX.25 UI Frames Using Inexpensive PIC Microprocessors</i></font></a></font><br><br>(<a href="http://www.tnc-x.com/dcc.doc">www.tnc-x.com/dcc.doc</a>)<br><br>It goes over most of this stuff in some detail. The bytes you have before the address are the 7E flags. In addition, you'll find that many TNC's idle during the TXDelay period using 00's instead of 7E's. With NRZI it does not matter which state you start in. Zero's are represented by a change of state, it doesn't matter whether they are low to high or high to low. There is no data scrambler with 1200 baud packet, but there is with 9600 baud packet. <br>
<br>Almost every developer I've ever talked about this (including me) has said at one time or another that this or that feature "seems to be a poor choice." I've occasionally run across items that I didn't think really conformed to the standard. You pretty much have to get over that if you want to play in this sand
box. The standard is what it is and at this point it has become so
institutionalized that it's not going to change. <br><br>John W2FS<br><br><div class="gmail_quote">On Thu, Sep 16, 2010 at 4:44 AM, Derek Love <span dir="ltr"><<a href="mailto:DLove@app-tech.co.uk">DLove@app-tech.co.uk</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">Thanks for the info guys, maybe I should be a bit more specific.<br>
<br>
I have the APRS 2.0 spec, I know about HDLC, NRZI, byte reversal, bit<br>
stuffing, CRC/FCS generation and stop/start (7E) flags.<br>
<br>
However, I come from a PMR / Data radio environment, so my first questions<br>
are:<br>
What's the preamble sequence and length?<br>
What's the sync sequence and length?<br>
<br>
The preamble is usually a 1100 sequence of 16 or 24 bits to allow the RF<br>
sections to settle down and the receiving modem to set its levels up. The<br>
Sync sequence is usually 16 or 24 bits carefully chosen so they don't<br>
correlate well with Gaussian noise so that false detects are minimised.<br>
<br>
So far as I can see, there is no mention at all of a preamble and the only<br>
sync sequence I can see is the 7E start flag, which seems to be a very poor<br>
choice?<br>
<br>
I can't see any specification for which state the NRZI coding process should<br>
be started with either......<br>
<br>
I have also found a reference to a data scrambler somewhere, but no<br>
indication if it's part of the standard or not.<br>
<font color="#888888"><br>
Derek Love<br>
G7ORK<br>
</font><div class="im"><br>
<br>
-----Original Message-----<br>
From: Curt, WE7U [mailto:<a href="mailto:curt.we7u@gmail.com">curt.we7u@gmail.com</a>]<br>
Sent: 15 September 2010 22:48<br>
To: TAPR APRS Mailing List<br>
Cc: Derek Love<br>
Subject: Re: [aprssig] ARPS physical layer<br>
<br>
<br>
<br>
There's a byte-wise CRC16 algorithm that was published in an IEEE<br>
magazine in the late 70's or early 80's that I used when I wrote<br>
assembly for decoding packets in '84 or '85. Worth checking out if<br>
you're writing code.<br>
<br>
--<br>
Curt, WE7U. <<a href="http://www.eskimo.com/%7Earcher" target="_blank">http://www.eskimo.com/~archer</a>><br>
APRS: Where it's at! <<a href="http://www.xastir.org" target="_blank">http://www.xastir.org</a>><br>
Lotto: A tax on people who are bad at math. - unknown<br>
Windows: Microsoft's tax on computer illiterates. - WE7U.<br>
The world DOES revolve around me: I picked the coordinate system!"<br>
<br>
<br>
</div><div><div></div><div class="h5">Registered Office- Oval Park. Hatfield Road. Langford. Maldon. CM9 6WG<br>
Registered in England and Wales. Registered No. 02847065. VAT No. 368 6007 36<br>
</div></div><br>_______________________________________________<br>
aprssig mailing list<br>
<a href="mailto:aprssig@tapr.org">aprssig@tapr.org</a><br>
<a href="https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig" target="_blank">https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig</a><br>
<br></blockquote></div><br>