Table of Contents
With this app you can receive real-time ADS-B used for air traffic control.
Functionality
Select a received aircraft and more detail will be shown. Select "Show on map" to see the aircraft location. ADS-B operates on 978 to 1090 MHz. Even a short antenna attached directly to the Portapack will receive ADS-B when the receive preamp is enabled ("1" displayed).
Map
For map functionality a world map must be loaded on the SD card. The map image and other SD card content is available from the portapack-mayhem github download page. The map can be zoomed in or out by moving the cursor down to the map region and turning the encoder dial (resolution is still limited by the map file, but zooming in helps to separate overlapping plane icons, and zooming out may help if you have really good reception). The map position can also be changed by modifying the latitude and longitude values.
Airlines
Log into microSD
The ADSB RX app will log each frame including the following columns:
- (YEAR MONTH DAY HOUR MIN SEC)
- (RAW PACKET IN HEX)
- ICAO: (ICAO)
- (CALLSIGN)
- Alt: (ALTITUDE)
- Lat: (LATITUDE)
- Lon: (LONGITUDE)
Example:
20171103100227 8DADBEEFDEADBEEFDEADBEEFDEADBEEF ICAO:nnnnnn callsign Alt:nnnnnn Latnnn.nn Lonnnn.nn
Screenshots
Main ADS-B View. In the columns, the ICAO/Call column will show the Callsign if known, otherwise the ICAO. The Lvl field is the Altitude in 100's of feet. Spd is the speed in mph. Amp is the signal strength, which may be increasing/decreasing depending on whether the plane is getting closer. Hit is the number of packets received from the same plane, and age is the number of seconds since the last packet was received.
Aircraft View. The altitude is in feet, and the speed is in mph.
Map View. The map can be zoomed in or out by moving the cursor down to the map area and then turning the encoder dial.
A/C Details
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.
How to collaborate
How to ask questions correctly
User manual
- First steps
- Usage cautions
- Intended use and Legality
- Features
- PortaPack Versions (which one to buy)
- HackRF Versions
- Firmware update procedure
- Description of the hardware
- 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
- Applications
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)
- 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
Hardware Hacks
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.