JAERO
JAERO copied to clipboard
Minor fixes and adding more JSON and parsing options
- Fixed typo with
populatepublicvars
- Added generated files
JAERO
andmoc_predefs.h
to git ignore - Added option to only use libacars library to parse downlink ADS messages
- Added option to output JSON format (JSON4) similar to @szpajder 's dumphfdl and dumpvdl2
- libacars decoded messages will exposed as JSON objects if in JSON4 format
- Added settings options for inputting station ID (default is hostname)
Settings Dialog
Example JSON
{ "app": { "name": "JAERO", "ver": "v1.0.4.13" }, "isu": { "acars": { "ack": "!", "arinc622": { "adsc": { "err": false, "tags": [ { "wpt_change_event": { "alt": 36000, "lat": 51.001282, "lon": -30.005379, "nav_redundancy": true, "pos_accuracy_nm": 0.25, "tcas_avail": true, "ts_sec": 742 } }, { "predicted_route": { "next_next_wpt": { "alt": 36000, "lat": 50.999908, "lon": -49.999981 }, "next_wpt": { "alt": 36000, "eta_sec": 3026, "lat": 50.999908, "lon": -40.000019 } } } ] }, "air_addr": ".D-AIHV", "crc_ok": true, "gs_addr": "PIKCPYA", "msg_type": "adsc_msg" }, "blk_id": "7", "flight": "LH424", "label": "B6", "mode": "2", "msg_text": "J30ALH0424/PIKCPYA.ADS.D-AIHV14244487554D88CA0B981D0D2444471C71C8CA0BD2244446E38E48CA0097F3", "reg": "D-AIHV" }, "dst": { "addr": "43", "type": "Ground Earth Station" }, "qno": "07", "refno": "08", "src": { "addr": "3C6516", "type": "Aircraft Earth Station" } }, "station": "jetson", "t": { "sec": 1665545421, "usec": 58000 } }
Nice additions. I'd love to see this happen. Would be good to have the JSON keys match in case, but also to come even closer to @szpajder 's dump format (if possible) overall!
Since we have the app
element that indicates jaero and version, do you think the top level jaero
element is necessary? I suppose since dumpvdl2 has the vdl2
top level element, this matches that.
Since we have the
app
element that indicates jaero and version, do you think the top leveljaero
element is necessary?
Practically speaking, I don't think it's necessary. I put it in just to closer match the dump JSON format
@andermatt64 This is some really great work. Thanks for taking all of our feedback here and on the ADSBX Discord.
Looks good to me! I think you could add
seqno
too.
I tried adding it but the value seems to be always 00
. I suspect it may be a value used internally to reassemble fragmented messages