[aprsspec] Telemetry Protocol

[Ev Tupis]

If we're willing to accept two generic telemetry data sets identified as either {ET (Extensible Telemetry) or {BT (Basic Telemetry) and realize that such generic formats can fit just about anything that we could push through the APRS data strem (both RF and Internet), then our job is done. :)

On the other hand, I decided to test fly this thought, using PropNET data.

Applying this to a PropNET dataset, we start out with how things are presently conveyed through the PropNET Internet stream:

KF6XA>HY,W6CGH,TCPIP*:[DM13jo]PHG340087/^5751{PSDM13br0000000-0050-16JSP2106}

Reformatting it to comply with an Extensible Telemetry model:

KF6XA>TEL,W6CGH,TCPIP*:{ET,PROPNET,BAND,HY,DXQTH,DM13JO,DXPHG,340087,DXCRC,5751,MYQTH,DM13BR,RXSECAGE,0,RELFREQ,-50,RXIMD,-16,VERS,JSP2106

In the above case, the data set is identified as PROPNET and each field is individually identified and the next data element is the field value.

Alternatively, applying this same data to a Basic Telemetry model:

KF6XA>TEL,W6CGH,TCPIP*:{BT,PROPNET,HY,DM13JO,340087,5751,DM13BR,0,-50,-16,JSP2106

In this case, the data set is identified as PROPNET.  That is all that needs to be identified, because someone somewhere has already mapped all of the data fields to the PROPNET ID (knowing what data belongs in what field).

Ev, W2EV


      ____________________________________________________________________________________
Luggage? GPS? Comic books? 
Check out fitting gifts for grads at Yahoo! Search
http://search.yahoo.com/search?fr=oni_on_mail&p=graduation+gifts&cs=bz