FANET messages by the OGN tracker

[acasadoalonso]

This is an example of APRS message generated by the OGN station when it receives a FANET message generated by an OGN tracker

OGN085B5C>OGNFNT,qAS,GETRONIX:/175419h4804.35N\01444.09En !W88! id3F085B5C FNT71 55.0dB

it is not OGNTRK on the tocall ID, it is OGNFNT in the tocall ID, other than that the structure is similar to the FNTxxxxxx messages.

[Meisterschueler]

@acasadoalonso : is there any specification of how these beacons can look like?

[acasadoalonso]

I showed an example above
The syntax is the same that the FNT messages, the only differences is that are originated by OGN trackers OGNxxxxxx and the “tocall” is OGNFNT

[Meisterschueler]

No, this is wrong. We see an APRS position message with timestamp and comment. The comment is the part "id3F085B5C FNT71 55.0dB". The regex for the FNT (position) comment is:
(id(?P<details>[\dA-F]{2})(?P<address>[\dA-F]{6}?)\s?)?(?:(?P<climb_rate>[+-]\d+)fpm)?
See also here:

python-ogn-client/ogn/parser/pattern.py

Line 10 in b0f3333

PATTERN_FANET_POSITION_COMMENT = re.compile(r"""

So the line (more exactly the APRS comment) would not pass the FNT messages parser.

[acasadoalonso]

See the other FANET messages FNT1118C1>OGNFNT,qAS,BelaVista:>191924h Name="FlrmAIC" 26.0dB -12.1kHz FNT1118C1>OGNFNT,qAS,BelaVista:/191929h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 28.8dB -12.3kHz FNT1118C1>OGNFNT,qAS,BelaVista:/191934h3841.98N\00919.39Wn !W57! id3E1118C1 FNT71 26.3dB -12.3kHz FNT1118C1>OGNFNT,qAS,BelaVista:/100207h3841.98N/00919.40Wg !W72! id3E1118C1 FNT71 25.3dB -13.2kHz it looks quite similar correct ??? AC/. Sent from my iPad

…

On 11 Mar 2022, at 23:10, Meisterschueler ***@***.***> wrote:  No, this is wrong. We see an APRS position message with timestamp and comment. The comment is the part "id3F085B5C FNT71 55.0dB". The regex for the FNT (position) comment is: (id(?P<details>[\dA-F]{2})(?P<address>[\dA-F]{6}?)\s?)?(?:(?P<climb_rate>[+-]\d+)fpm)? See also here: https://github.com/glidernet/python-ogn-client/blob/b0f3333fd03a7a48fc46b300c64b003b27950382/ogn/parser/pattern.py#L10 So the line (more exactly the APRS comment) would not pass the FNT messages parser. — Reply to this email directly, view it on GitHub, or unsubscribe. Triage notifications on the go with GitHub Mobile for iOS or Android. You are receiving this because you were mentioned.

[Meisterschueler]

This is correct. They look similar and they have the same undocumented structure. And because of this they also do not pass the parser.

[acasadoalonso]

The format is: Examples: FNT1118C1>OGNFNT,qAS,BelaVista:/191919h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 26.3dB -12.4kHz FNT1118C1>OGNFNT,qAS,BelaVista:>191924h Name="FlrmAIC" 26.0dB -12.1kHz FNT1118C1>OGNFNT,qAS,BelaVista:/191929h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 28.8dB -12.3kHz The *ID* is *FNTxxxxxx* where the xxxxxx is the FANET device ID for FANET devices FNT1118C1 or *OGNyyyyyy* where yyyyyy is the OGN tracker ID for messages generated from OGN trackers devices OGN123456 *The TOCALL is OGNFNT* The *std position parts*: FNT1118C1>OGNFNT,qAS,BelaVista:/191919h3841.98N\00919.39Wn !W68! optionally the *climb rate*: +03fpm plus the *uniqueid*: id3E1118C1 plus the *FANET message FNTxx* where xx is the message ID, FNT71 plus the *signal strength and frequency deviation* 28.8dB -12.3kHz Feel free to reach me or Pawel for further details. AC/.

…

On Sat, Mar 12, 2022 at 12:33 PM Meisterschueler ***@***.***> wrote: This is correct. They look similar and they have the same undocumented structure. And because of this they also do not pass the parser. — Reply to this email directly, view it on GitHub <#107 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB6DYZ2L5BMDZNX56OX57LLU7R6IZANCNFSM5QF2ZBTQ> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you were mentioned.Message ID: ***@***.***>

-- Angel Casado

[acasadoalonso]

The format is: Examples: FNT1118C1>OGNFNT,qAS,BelaVista:/191919h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 26.3dB -12.4kHz FNT1118C1>OGNFNT,qAS,BelaVista:>191924h Name="FlrmAIC" 26.0dB -12.1kHz FNT1118C1>OGNFNT,qAS,BelaVista:/191929h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 28.8dB -12.3kHz The *ID* is *FNTxxxxxx* where the xxxxxx is the FANET device ID for FANET devices FNT1118C1 or *OGNyyyyyy* where yyyyyy is the OGN tracker ID for messages generated from OGN trackers devices OGN123456 *The TOCALL is OGNFNT* The *std position parts*: FNT1118C1>OGNFNT,qAS,BelaVista:/191919h3841.98N\00919.39Wn !W68! optionally the *climb rate*: +03fpm plus the *uniqueid*: id3E1118C1 plus the *FANET message FNTxx* where xx is the message ID, FNT71 plus the *signal strength and frequency deviation* 28.8dB -12.3kHz Feel free to reach me or Pawel for further details. On Sat, Mar 12, 2022 at 7:49 PM Angel Casado ***@***.***> wrote:

…

The format is: Examples: FNT1118C1>OGNFNT,qAS,BelaVista:/191919h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 26.3dB -12.4kHz FNT1118C1>OGNFNT,qAS,BelaVista:>191924h Name="FlrmAIC" 26.0dB -12.1kHz FNT1118C1>OGNFNT,qAS,BelaVista:/191929h3841.98N\00919.39Wn !W68! id3E1118C1 FNT71 28.8dB -12.3kHz The *ID* is *FNTxxxxxx* where the xxxxxx is the FANET device ID for FANET devices FNT1118C1 or *OGNyyyyyy* where yyyyyy is the OGN tracker ID for messages generated from OGN trackers devices OGN123456 *The TOCALL is OGNFNT* The *std position parts*: FNT1118C1> OGNFNT,qAS,BelaVista:/191919h3841.98N\00919.39Wn !W68! optionally the *climb rate*: +03fpm plus the *uniqueid*: id3E1118C1 plus the *FANET message FNTxx* where xx is the message ID, FNT71 plus the *signal strength and frequency deviation* 28.8dB -12.3kHz Feel free to reach me or Pawel for further details. AC/. On Sat, Mar 12, 2022 at 12:33 PM Meisterschueler ***@***.***> wrote: > This is correct. They look similar and they have the same undocumented > structure. And because of this they also do not pass the parser. > > — > Reply to this email directly, view it on GitHub > <#107 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AB6DYZ2L5BMDZNX56OX57LLU7R6IZANCNFSM5QF2ZBTQ> > . > Triage notifications on the go with GitHub Mobile for iOS > <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> > or Android > <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. > > You are receiving this because you were mentioned.Message ID: > ***@***.***> > -- Angel Casado

-- Angel Casado