Order Tray | Contact Us | Home | SIG Lists

[aprssig] Object Definition vs third-party traffic?

Bob Bruninga bruninga at usna.edu
Wed Jun 10 15:49:28 UTC 2009


> This in not best method if defining objects!
> Better use Object indeficator ";" and use 
> ham call of originator in packet,
> for example:
>
> call_of_originator>APOBJ:
> ;146.52*!2806.  N/08039.  WrPHG7260 NWS MELBOURNE
>
> In third party this packet should be some like this:
> WX4MLB-3>BEACON:
> }call_of_originator>APOBJ,TCPIP:;146.52>!2806.  N/08039.  > WrPHG7260 NWS MELBOURNE

This is the correct approach, but the format is not correct.  The ;objectnam*DDHHMMzDDMM.mmN/DDDMM.mmW$text is the correct format.  The object name must be 9 bytes (padded with spaces) and the TIME field must be there.

We use the time of 111111z when the time is not important.

Bob, WB4APR
>Possible timestamp should be also present before coordinates...
>
>
>73, Sergej
>uz2hz
>
>
>_______________________________________________
>aprssig mailing list
>aprssig at tapr.org
>https://www.tapr.org/cgi-bin/mailman/listinfo/aprssig



More information about the aprssig mailing list