Table of Contents
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
ACARS (Aircraft Communications Addressing and Reporting System) is a digital data link protocol used to exchange short messages between aircraft and ground stations over VHF radio. This app decodes ACARS frames and displays the extracted fields in a scrolling console.
Settings
- Frequency: Default 131.825 MHz (primary ACARS VHF frequency in Europe and globally). Adjustable via encoder knob or tap for keypad. Other common frequencies include 129.125 MHz and 130.025 MHz depending on region and airline.
- RF Amp (0 or 1): Enables/disables the internal RF amplifier.
- LNA gain (0–40): Low-noise amplifier gain. See Receive Quality Issues.
- VGA gain (0–62): Variable-gain amplifier gain.
- LOG: Checkbox to enable logging to file. When checked, decoded messages are written to
LOGS/ACARS.TXT. The log file is opened automatically on startup; the checkbox controls whether entries are written.
Decoded Message Fields
Each received and CRC-verified ACARS frame is decoded into the following fields, displayed in the console:
- CRC:
OKif the CRC-16/CCITT checksum over the frame matches the two trailing CRC bytes;FAILotherwise. Frames with CRC failures are still displayed but should be treated as potentially corrupt. - Registration: 7-character aircraft registration (tail number), e.g.
D-ABCDorN12345. - Label: 2-character message type code identifying the category of message (e.g. flight plan update, ATIS, position report).
- BlockID: 1-character sequence counter for multi-block messages.
- MsgNum: 3-character message number within the current session.
- FlightID: 6-character flight identifier, typically the IATA flight number.
- Message: Free-text payload of variable length. Content depends on the label type and airline ground system.
A minimum valid frame must be at least 23 bytes (21-byte fixed header + 2 CRC bytes). Frames shorter than this are shown with an error message in the text field instead of decoded content.
Logging
When LOG is enabled, each decoded message is written as a single timestamped entry to LOGS/ACARS.TXT. The file is always opened on launch; entries are only written when the checkbox is active. Settings are saved to rx_acars.ini.
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Start here
Contributors
How to collaborate
Contributing Guidelines
How to ask questions correctly
Hardware
- PortaPack Versions (which one to buy)
- Features
- HackRF Versions
- Description of the hardware
- Enclosure/cases
- Repairs
- Mods
User manual
Intended use and Legality
- Usage cautions
- First steps
- Firmware update procedure
- User interface
- Powering the PortaPack
- Troubleshooting
- Won't boot
- Config Menu
- Firmware upgrade
- Diagnose firmware update in Windows
- Receive Quality Issues
- No TX/RX
- TX Carrier Only
- H2+ speaker modifications
- Dead Coin Cell Battery
- Factory Defaults
- SD card not recognized by PC with the SD-card over USB selected
- DFU overlay
- Full reset
- SolveBoard
- How to Format SDCard
- What if I don't like some of the apps
Applications
- 📥 Receivers
- 📤 Transmitters
- ADS-B(S) TX
- Adult Toys
- APRS TX
- BHT Xy/EP
- BLE TX
- BLESpam
- Burger Pager
- CVS Spam
- EPIRB
- FlipperTX
- GPS Sim
- Hopper
- Jammer
- KeeLoq TX
- Key fob TX
- LGE Tool
- MDC-1200 TX
- Morse TX
- OOK
- OOK Brute
- OOK Editor
- P25 TX
- POCSAG TX
- RDS
- RTTY TX
- SAME TX
- Signal gen
- Soundboard
- Spectrum Painter
- SSTV
- TEDI/LCR
- TouchTunes
- TPMS TX
- 🔄 Transceivers
- 🟡 Recon
- 🔴 Capture
- ▶️ Replay
- 🖲️ Remote
- 🔍 Looking Glass
- 🛠️ Utilities
- 🎮 Games
- ⚙️ Settings
- 💻 HackRF Mode
Misc
Developer Manual
- Compilation of the firmware
- Compile on WSL with ninja
- How to compile on Windows faster with WSL 2
- Using Docker and Kitematic
- Docker command-line reference
- Using Buddyworks and other CI platforms
- Notes for Buddy.Works (and other CI platforms)
- Using ARM on Debian host
- All in one script for ARM on Debian host
- Compile on Arch based distro (exclude Asahi), or other weird distros
- Dev build versions
- Notes About ccache
- Create a custom map
- Code formatting
- PR process
- Description of the Structure
- Software Dev Guides
- Tools
- Research
- UI Screenshots
- Maintaining
- Creating a prod/stable release (Maintainers only)
- Maintaining rules
- Development States Notes
This file contains Unicode characters that might be confused with other characters. If you think that this is intentional, you can safely ignore this warning. Use the Escape button to reveal them.
Note
The wiki is incomplete. Please add content and collaborate.
Important
- This is a public wiki. Everything is visible to everyone. Don't use it for personal notes.
- Avoid linking to external tutorials/articles; they may become outdated or contain false information.