User Ratings

★★★★★
★★★★
★★★
★★
8
0
0
0
0
ease 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
features 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
design 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 4 / 5
support 1 of 5 2 of 5 3 of 5 4 of 5 5 of 5 5 / 5

Rate This Project

Login To Rate This Project

User Reviews

  • Try to run it on Xubuntu 16.04.2 as Alsa only. Managed to compile it without the RTL, Airspy en File features. Solved this message by copying the variable init to top of acarsdec.c acarsdec.c:(.text.startup+0xf7): undefined reference to `gain' Now i get this message: Alsa cannot set sample format (Invalid argument) Any thoughts appreciated.

  • Works as designed on an RPi3. Had to edit Makefile as noted in the docs. Actually decoding 6 channels and the CPU looks like it could handle more. Yay! :)

  • Works perfect on the Raspberry. Thanks a lot for that tool, made me totally happy. But I would like to ask if it is somehow possible to view/log the messages in the raw format? I really would need that one.

  • This is a great tool. One question if it encounters a secure or signed ACARS message how would it show one of those messages?

  • Excellent work Thierry! Works great on my Raspberry Pi. I have put a version on my GitHub that extends the code to send data to PlanePlotter over UDP. Unfortunately I can't put a link here, but you should be able to find it by searching for acarsdec on GitHub.com. My version also tweaks the gain control of an RTL SDR (by calling rtlsdr_set_agc_mode).

    1 user found this review helpful.
  • Thierry I would echo David's review, seems very good on two frequencies, three overload the CPU on a Raspberry Pi. If use of the GPU could take some load off the CPU, that would be good. I also would suggest a TCP socket output for the data. This would enable use with Virtual Radar Server as well as Planeplotter. I will try to set up a Atom based machine over the weekend and trial it on that. Cheers Jon

    1 user found this review helpful.
  • Working well here on a Raspberry Pi, although that CPU limits you to two frequencies before overload sets in. It would be most helpful to see TCP output of the messages (so that programs like Plane Plotter can access the data), and if someone could take advantage of the GPU functions on the RPi to reduce CPU load that would be a major step forward. I made a Noddy's guide for the RPi here: www.satsignal.eu/raspberry-pi/acars-decoder.html Later: Thierry tells me that he has significant performance enhancements for the Raspberry Pi version (30% CPU with 3 active frequencies), and that he has UDP output to the existing Plane Plotter standard working. Makes a good program even better!

    1 user found this review helpful.
  • Works for me. Built on Crunchbang Statler. Decoding nicely from an AOR-8600mk2 via a Signalink-USB. I hacked it slightly to print tm_sec in the message timestamp, as the timestamp only showed hrs:mins.