on downlink - to decode ARINC-622 ATS messages other than ADS-C (which is decoded with JAERO built-in decoder)
This patch causes JAERO to use libacars more extensively. In particular:
on uplink - to decode all ACARS applications (be it ARINC-622 or not). Essentially, the whole ACARS message text together with the message label is passed to libacars, hoping that it would be able to do something with it.
on downlink - to decode all ACARS applications (be it ARINC-622 or not), except ADS-C, which is still decoded the old way.
Having this change in place, whatever new ACARS application becomes supported in libacars, it will be decoded straight away, without any JAERO code modifications. It will be just a matter of replacing libacars.dll (or libacars.so) with the new, more capable version.
As an example - ACARS downlink messages with label SA:
The latest libacars code from unstable branch has a decoder for this type, but JAERO won't call it, so the message will still be printed undecoded, even if the latest libacars is installed. With this patch applied, it looks as follows:
16:56:44 25-12-18 AES:AA6BC0 GES:44 2 .N77022 ! SA 6 Flight UA998
S90AUA09980L2133238HS
Media Advisory, version 0:
Link VDL2 lost at 13:32:38 UTC
Available links: HF, Default SATCOM
Currently, JAERO uses libacars API:
This patch causes JAERO to use libacars more extensively. In particular:
Having this change in place, whatever new ACARS application becomes supported in libacars, it will be decoded straight away, without any JAERO code modifications. It will be just a matter of replacing libacars.dll (or libacars.so) with the new, more capable version.
As an example - ACARS downlink messages with label SA:
The latest libacars code from unstable branch has a decoder for this type, but JAERO won't call it, so the message will still be printed undecoded, even if the latest libacars is installed. With this patch applied, it looks as follows:
Please apply. Thanks.