# ACARS + Flightaware

**URL:** <https://discussions.flightaware.com/t/acars-flightaware/85547>\
**Category:** ADS-B Flight Tracking\
**Created:** [November 30, 2022, 10:48am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547 "2022-11-30T10:48:52Z")\
**Posts on this page:** 20\
**Page:** 2

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [May 7, 2023, 3:04pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/22 "2023-05-07T15:04:47Z")

</div>

You can monitor that many but when I checked my spectrum in SDR Sharp there was only 4 active frequencies in Texas or to say within my location. I use both AD2 and DUMPVDL2 on a separate pi3B+

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 7, 2023, 8:41pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/23 "2023-05-07T20:41:52Z")

</div>

Ok, installed acarsdec on RPi that @dvsvejk linked to. Tried it with the four frequencies I listed earlier and seems to work fine – just looking at it on the command line.

Apparently there is a further decoding avalable from a library called libacars – not sure if that goes on RPi or not.

Looking around on the inter webs it seems like messages on ACARS are pretty much free form – i.e. no “standard” was defined by ARINC, so could be lots of different types of messages depending on airline, etc.

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 8, 2023, 1:49am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/24 "2023-05-08T01:49:46Z")

</div>

> [@glennblum](#):
>
> You can monitor that many but when I checked my spectrum in SDR Sharp there was only 4 active frequencies in Texas or to say within my location.

What 4 frequencies do you see ACARS on ?

---

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [May 8, 2023, 2:41am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/25 "2023-05-08T02:41:57Z")

</div>

–freq 131875000  
–freq 131725000  
–freq 131550000  
–freq 131125000  
–freq 131425000

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 8, 2023, 3:03am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/26 "2023-05-08T03:03:32Z")

</div>

Thanks – haven’t noticed ACARS on some of those frequencies here (Southern CA) but should probably try those too.

Edit to add:  
The latest -d command for acarsdec -d shows the following:

```auto
pi@raspberrypi:~ $ acarsdec -d
Acarsdec/acarsserv 3.7 Copyright (c) 2022 Thierry Leconte

Usage: acarsdec [-o lv] [-t time] [-A] [-b 'labels,..'] [-e] [-i station_id] [-n|-j|-N ipaddr:port] [-l logfile [-H|-D]] [-g gain] [-p ppm] -r rtldevicenumber f1 [f2] ... [fN]

 -i stationid : station id used in acarsdec network format.
 -A : don't output uplink messages (ie : only aircraft messages)
 -e : don't output empty messages (ie : _d,Q0, etc ...)
 -b filter : filter output by label (ex: -b "H1:Q0" : only output messages with label H1 or Q0)
 -o lv : output format : 0 : no log, 1 : one line by msg, 2 : full (default) , 3 : monitor , 4 : msg JSON, 5 : route JSON
 -t time : set forget time (TTL) in seconds for monitor mode (default=600s)
 -l logfile : append log messages to logfile (Default : stdout).
 -H : rotate log file once every hour
 -D : rotate log file once every day

 -n ipaddr:port : send acars messages to addr:port on UDP in planeplotter compatible format
 -N ipaddr:port : send acars messages to addr:port on UDP in acarsdec native format
 -j ipaddr:port : send acars messages to addr:port on UDP in acarsdec json format

 -g gain : set rtl gain in db (0 to 49.6; >52 and -10 will result in AGC; default is AGC)
 -p ppm : set rtl ppm frequency correction
 -m rtlMult : set rtl sample rate multiplier: 160 for 2 MS/s or 192 for 2.4 MS/s (default: 160)
 -r rtldevice f1 [f2]...[f16]	: decode from rtl dongle number or S/N rtldevice receiving at VHF frequencies f1 and optionally f2 to f16 in Mhz (ie : -r 0 131.525 131.725 131.825 )
 Up to 16 channels may be simultaneously decoded

```

So now apparently up to 16 frequencies can be specified. Course they can still only span up to 2MHz.

---

<div class="post-metadata">

**Author:** ![dvsvejk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dvsvejk/32/137267_2.png) [@dvsvejk](https://discussions.flightaware.com/u/dvsvejk)\
**Post date:** [May 8, 2023, 5:36am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/27 "2023-05-08T05:36:06Z")

</div>

While listed as optional, adding libacars is a nice to have. After installing, you will need to re-compile acarsdec.

> **[GitHub - szpajder/libacars: A library for decoding various ACARS message...](https://github.com/szpajder/libacars)**
>
> A library for decoding various ACARS message payloads - GitHub - szpajder/libacars: A library for decoding various ACARS message payloads

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 8, 2023, 5:42am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/28 "2023-05-08T05:42:25Z")

</div>

> [@dvsvejk](#):
>
> While listed as optional, adding libacars is a nice to have. After installing, you will need to re-compile acarsdec.

Yeah, I was wondering about that. Can I just compile acarsdec again and install again without uninstalling anything?

---

<div class="post-metadata">

**Author:** ![dvsvejk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dvsvejk/32/137267_2.png) [@dvsvejk](https://discussions.flightaware.com/u/dvsvejk)\
**Post date:** [May 8, 2023, 5:51am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/29 "2023-05-08T05:51:50Z")

</div>

After installing libacars navigate to the build directory for acarsdec and re-run the compile commands - you should see a message where it detects libacars when running cmake.

```auto
cmake .. -Drtl=ON
make
sudo make install

```

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 8, 2023, 5:06pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/30 "2023-05-08T17:06:48Z")

</div>

Ok, installed libacars. Now get messages like:

```auto
[#1 (F:130.025 L:-22.5 E:0) 08/05/2023 16:55:39.067 --------------------------------
Mode : 2 Label : H1 Id : 8 Nak
Aircraft reg: N586NW Flight id: NW0725
No: D65B
Sublabel: DF
Reassembly: complete
*WXRN32469W1155281650200-16323903600
N32466W1155801651186-13524003900
N32461W1160361652171-09824103000
N32457W1160911653155-06525002300
N32453W1161461654141-03025002000
N32449W1162021655126-01525002000

```

Looks like weather and waypoints.  
Need to do some reading on what this all means.

---

<div class="post-metadata">

**Author:** ![oblivian](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/oblivian/32/135708_2.png) [@oblivian](https://discussions.flightaware.com/u/oblivian)\
**Post date:** [May 9, 2023, 12:49am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/31 "2023-05-09T00:49:48Z")

</div>

Very little on acars here. More on vdl2

But what was, was engineering updates - long strings of garbage. Weather/atis updates

And Jetstar use to send last 5 positions when going past waypoints/periodically - Presumably for the ground time arrival calcs etc

Every so often wheelchair requests or rugby scores for crew airborne 😉

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 9, 2023, 1:14am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/32 "2023-05-09T01:14:36Z")

</div>

> [@oblivian](#):
>
> More on vdl2

What vdl2 decoder do you use? Also what frequencies do you see vdl2 messages on. Tnx.

---

<div class="post-metadata">

**Author:** ![dvsvejk](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/dvsvejk/32/137267_2.png) [@dvsvejk](https://discussions.flightaware.com/u/dvsvejk)\
**Post date:** [May 9, 2023, 8:34am UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/33 "2023-05-09T08:34:01Z")

</div>

You likely already have all the required dependencies installed on your Pi running acarsdec, so it would simply be a matter of cloning the repository and compiling dumpvdl2.

> **[GitHub - szpajder/dumpvdl2: VDL Mode 2 message decoder and protocol analyzer](https://github.com/szpajder/dumpvdl2)**
>
> VDL Mode 2 message decoder and protocol analyzer. Contribute to szpajder/dumpvdl2 development by creating an account on GitHub.

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 9, 2023, 4:34pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/34 "2023-05-09T16:34:50Z")

</div>

Ok, thanks. And I see the default frequency is 136.975 MHz. I’ll try that.

By the way, I serialized the dongles for dump1090 and acars, however, when dump1090-fa starts up, it picks the wrong dongle. I do have the serial number of the 1090 dongle in the file `/etc/default/dump1090-fa`. But It looks like dump1090-fa picks the dongle based on ID number i.e. ID=0 rather than on serial number. Do other people have this problem?

---

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [May 9, 2023, 4:45pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/35 "2023-05-09T16:45:03Z")

</div>

dumpvdl2 --rtlsdr 1 --gain 48 --correction 0 136650000 136975000 136800000 136700000

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 9, 2023, 6:19pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/36 "2023-05-09T18:19:48Z")

</div>

Wow, more activity on vdl2 than on Plain Old Acars. I was concerned I might not see as much because the data rate is about 11 dB higher on vdl2 therefore requiring at least that much more signal.

---

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [May 9, 2023, 6:55pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/37 "2023-05-09T18:55:15Z")

</div>

Sorry about my reply above. That is the basic command line for the DUMPVDL2 decoder I have. On my PC I have SDR# installed with a NooElec SMART rtlsdr and what I did was tune to 135.500 mhz and watch the waterfall activity and noted which frequencies were in use in my area. Then added them to my decoder command.

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 9, 2023, 7:41pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/38 "2023-05-09T19:41:23Z")

</div>

What do you use for an antenna ?

---

<div class="post-metadata">

**Author:** ![glennblum](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/glennblum/32/113376_2.png) [@glennblum](https://discussions.flightaware.com/u/glennblum)\
**Post date:** [May 9, 2023, 8:46pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/39 "2023-05-09T20:46:47Z")

</div>

A cheap amazon dual band outdoor ham radio antenna. The only good antennas I do use for is ADSB and my 2 meter /70cm operation when I want to talk.

---

<div class="post-metadata">

**Author:** ![jimMerk2](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/jimmerk2/32/137167_2.png) [@jimMerk2](https://discussions.flightaware.com/u/jimMerk2)\
**Post date:** [May 9, 2023, 9:21pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/40 "2023-05-09T21:21:45Z")

</div>

Ok as I mentioned earlier I just have a 1/2 wave dipole now mounted in a closet upstairs. I am amazed at how much traffic I can see with that and just the dongle (mainly on 136.65 MHz).

I wonder if this could be integrated with the SkyAware map to show aircraft that are currently transmitting vdl2 messages. However, I know FlightAware people ( e.g. obj) are adverse to doing things like that because of security reasons.

---

<div class="post-metadata">

**Author:** ![MC130E](https://sea1.discourse-cdn.com/flex019/user_avatar/discussions.flightaware.com/mc130e/32/137074_2.png) [@MC130E](https://discussions.flightaware.com/u/MC130E)\
**Post date:** [May 9, 2023, 10:56pm UTC](https://discussions.flightaware.com/t/acars-flightaware/85547/41 "2023-05-09T22:56:56Z")

</div>

> [@jimMerk2](#):
>
> I serialized the dongles for dump1090 and acars, however, when dump1090-fa starts up, it picks the wrong dongle. I do have the serial number of the 1090 dongle in the file `/etc/default/dump1090-fa`. But It looks like dump1090-fa picks the dongle based on ID number i.e. ID=0 rather than on serial number. Do other people have this problem?

Jim,

dump1090-fa can handle either the device number, or the serial number. Either way, the command option is called “device” which is what you might have noticed.

From the dump1090-fa --help

* * *

## pi@raspberrypi:~ $ dump1090-fa --help

| dump1090 ModeS Receiver dump1090-fa 8.2 |

| build options: ENABLE\_RTLSDR ENABLE\_BLADERF ENABLE\_HACKRF ENABLE\_LIMESDR |
| --- |
| –device-type Select SDR type (default: rtlsdr) |

```
  rtlsdr-specific options (use with --device-type rtlsdr)

```

–device \<index|serial\> select device by index or serial number

* * *

–device 0, 1, 2, … would be device number

–device xxxxxx would be serial number, which is always more reliable.

* * *

Some programs use different --labels for device and serial. FA uses the same for both. Just avoid serial numbers that could look like device numbers when programming.

-Dan

[Previous page](https://discussions.flightaware.com/t/acars-flightaware/85547.md?page=1)

[Next page](https://discussions.flightaware.com/t/acars-flightaware/85547.md?page=3)
