Radarcape:Software Features Major2
Major 2 Related Pages
General notes for new software releases
- All new Radarcape firmware packages have been tested thoroughly, but since Radarcape is an open system we never can now all status of devices that run on your side. In case of updating problems, please consider updating your device manually using the debian package or flashing it first back to a fallback image, as described in Radarcape:DebianSupport#Debian_Installation.
- Especially when operating your Radarcape remotely from your own location, be aware that the update may crash and you need to have a fallback strategy, a 2nd port for commands, and maybe the watchdog retrigger script running or at hands: Radarcape:Watchdog. It is highly recommended in such situations that you update first some local devices in order to proof it will work remotely, too.
For updating, please use the built-in web service menu: Settings -> Software Maintenance -> Radarcape Software Update. The latest software version automatically should be displayed there.
Radarcape Software Bugfixes Version 181213.1005.02 (Major Release 2)
- fix application crash when nmap scans network
- aircaftlist.json: lla field now outputs null when not initialized (instead of -1)
- Configuration: FPGA setting to format AVR brought back on web interface
- GPS Status does not display correctly in case of hardware fault
- Downgrade package installation improved
Debian Jessie direct download link: http://www.modesbeast.com/resources/radarcaped-AAA-181213.1004.02.deb
Debian Jessie MD5SUM file link: http://www.modesbeast.com/resources/radarcaped-AAA-181213.1004.024d.md5sum
This release is not available for Angstrom based Radarcapes
Radarcape Software Features Version 181213.1000.02 (Major Release 2)
- New Features:
- Decoding of Flarm PFLAA frames on UDP input port 50001
Note: PFLAA must have absolute LAT/LON values and not X/Y offset location for this feature.
- Decoding of Flarm PFLAA frames on UDP input port 50001
- Improvements and Changes:
- Config file now only records non-default parameters
- Software type and version are now displayed separately.
Type is "AAA" for a standard Radarcape with Debian 8 Jessie.
- Data corruption on JSON over UDP and TCP 30002 output.
- Bug causing error message "PPS/Time reference configuration error"
- KML output swapped LAT/LON
- Use default ports for network streams
- Wrong ntp time output
- Flightradar24 in some cases is not accessible because their IP V6 address is not accessible. This is a misconfiguration on Flightradar24 side which we cannot influence. Please ask [email protected] for advise.
- Some users reported Flightradar24 has lost their user login key. Please contact [email protected] in case that the feeder cannot connect to their server.
Debian Jessie direct download link: http://www.modesbeast.com/resources/radarcaped-AAA-181213.1000.02.deb
Debian Jessie MD5SUM file link: http://www.modesbeast.com/resources/radarcaped-AAA-181213.1000.024d.md5sum
This release is not available for Angstrom based Radarcapes
Radarcape Software Features Version 181116.1000.02 (Major Release 2)
This version is obsolete because of a bug in UDP streaming output. Replaced by version 181213.1000.02
- New Features:
- Ground Speed, Vertical Rate and True Track are now also displayed for AC without ADS-B, when interrogated from a Mode-S ground radar.
- Synthetic fields "external temperature", "wind speed" and "wind direction" added to aircraft list. Available when a ADS-B aircraft is under EHS ground radar.
- When aircraft is interrogated from ATC radar we obtain a ground speed vector (GPS speed and track), and a airspeed vector (true airspeed and heading). After magnetic declination correction wind is equal to the difference between this two vectors.
- Outside temperature is similarly calculated after determining speed of sound by relation of MACH and TAS reported.
- Altitude displayed for all Mode-S aircraft
- Aircraft list columns can be configured
- Enable and disable column
- Sorting of empty fields to the bottom or top
- Setting is saved in local browser, so multiple displays are possible
- Clear text name of origin and destination airport with a clickable link
- Receiver performance statistics
- last 5 minutes, last 24h and last 30 days
- Receiver range display
- for 3 different altitudes
- GNSS (GPS) status has got a graphic display of visible satellites over the last 24h
- Security features
- disable remote control of FPGA and GPS via TCP ports (moved to the security configuration)
- IPv6 support for feeders and streams
- Improvements and Changes:
- MLAT Key entering procedure has changed: Client ID is part of the key file
- Improved CPU load when retrieving aircraftlist.json
- Improved connection to external Open Glider Net Flarm receiver
- fixed JSON bug when loading aircraftlist.json with parameter select=locs
- fixed clicking on longitude link opens gmap with preselected aircraft
- fixed filtering of the available location sources
- fixed up and then crash when feeding to FR24
- fixed non-display of Gmap 2D map
This release is not available for Angstrom.
Radarcape Software Features Version 171213.1000.02 (Major Release 2)
- Radarcape is now able to displays FLARM located aircraft from two different sources:
- multiple local Raspberry-Pi based OGN receiver data can be read with UDP push interface (instructions provided online).
- connection to OGN server.
- 2D Map filters provide selective display of ADS-B, Jetvision MLAT, FlightAware MLAT, local FLARM and OGN Server data.
- Extended symbols for aircraft and FLARM, unknown type is a triangle, no longer A320.
- Ground traffic is displayed with a car symbol.
- Improved FPGA decoder for very strong signals (aircraft approximation <200m).
- Improved speed when accessing JSON data.
- GPS: Disable GPS jamming filter, now just 1 satellite instead of 4 is sufficient for a GPS signal.
- Show data of tracked aircraft overall and with different sources in aircraft list and maps.
Radarcape Software Features Version radarcaped-170521.1100.02 (Major Release 2)
Since May 2017 we provide Major Release 2. Currently this page describes the differences to Software Features of Major 1. All features of Major 1 are still included into Major 2, however some, for example the JSON lists and KML output, with some changes or enhancements.
Listed here are a lot of add-ons and enhancements. Please read across Radarcape:Software_Features for a first overview. See more about installations in the bottom.
You can identifiy our Major 2 release with a ".02", ".02D" or ".02A" at the end of the version string while Major 1 is ".01", ".01D", ".01A" or nothing.
How to perform update
It is strongly recommended to update to the latest version of Major 1 before updating to Major 2.
Until now the update has been done on some 50 devices without problems or assistance, most of them even remote. However, if your device is in a barely accessible, remote location or otherwise not easy to handle if something fails, please wait until some more experience was gained. We do not take over guarantee that it works in any strange situation.
If you want to update, simply go to the Settings - Software Maintenance and overwrite the default version given with the string
and then press submit. Thats it.
This is a brief summary of all new features.
We now have our own multilateration network operating stable with very good results.
- high precision location of Mode-S and ADS-B aircraft
- independent from any other sources, one shot position estimation
- update rate to clients 1/sec (if raw data is available)
- latency app. 1.5 seconds on client side
New features within Radarcape web interface
- New responsive web design optimized for web browsers on desktop, tablets and mobile devices
- Aircraft list can be sorted for any column
- Openlayers based maps
- ATC-Scope professional map style
- Filters for the 2D maps and KML output, e.g. altitude, type, flight, ICAO hex id, registration. Some of them with wildcards.
New features within Radarcape software
- Aircaft location and flight data are stored and accessible separately for ADS-B, Jetvision MLAT and other location sources
- Radarcape is now able to support native piAware from FlightAware in the background as fully featured feeder and can read back MLAT results in order to display them in aircraft list, 2D maps and KML output
- Full performance feeder for Opensky Network
- PiAware from FlightAware can be loaded into the background as a full performance feeder for their network.
- Automatic update of flight route and aircraft type (basestation) database
- BDS register data (Extdata) free of extra charges
- Signal level available converted to dBm
Sharing groups (to come)
- Several Radarcapes can be combined into a sharing network
Support for Planeplotter Mobile
- PPm can be used to display single Radarcape or sharing groups data through local connection or connection using our MLAT server
2 Channel Radarcape
- Antenna Diversity
- Dual Antenna systems
- for verification purposes, a buffered video out of the demodulated Mode-A/C and Mode-S signal is provided on a back side SMB or SMC connector
Changed License Conditions
With Major 2 firmware, we are introducing 3 classes of software licenses. Major 1 software (versions yymmdd.hhmm.01) are not affected by this change.
For private users, there are no changes, they can use the Radarcape in their private environment as always before! With Major 2 release, the license type is shown in the browser title. Default license type is "non commercial".
For business purposes, when using Major 2 release, you need a commercial license key in case you use our Radarcape to generate commercial value (excluding value generated by using the built in feeders). For non profit organisations it is further free without a payable license. Please contact Jetvision support for a feature key.
The feature key key is available also in the shop, please provide your Status - System: Download TXT file with your request.
This license is for using the Radarcape with Major 2 software for OEM purposes. This license key allows to customize the browser interface, use own logos and style sheets. Radarcape and all interface data can be used for business purposes in a customized environment.
The feature key is available also in the shop, please provide your Status - System: Download TXT file with your request.
Jetvision Multilateration Server
High precision location estimation for any Mode-S and ADS-B aircraft
- High precision MLAT results returning location, speed, track and vertical rate
- MLAT results are ditributed within a private sharing group
- Very low latency: Results are returned once per second with an latency of app. 1.5sec.
- No need for ADS-B aircraft as calibration references
- High accuracy for even a single position estimation, enhanced with a highly sophisticated, self adapting Kalman filter.
- MLAT results can be calculated for ADS-B aircraft, for example to verify their actual position or in case of spoofing
- Client/Server connection uses a control channel secured by SSL on TCP, and in parallel an UDP channel for raw data transmission
- intrusion avoidance
- allow access control
MLAT server provides JSON, Port 30003 and JSON streaming services in the same way and format as every Radarcape
- Any software which reads Radarcape data can read a combination of several on the server
Private sharing groups
- Provides services for sharing of data from multiple Radarcape among each other and sharing group data on any web based desktop or mobile device
Web interface to the server (commercial)
- Access to flight data of all connected Radarcapes including ADS-B data and BDS registers (commercial)
- Client status monitoring provided as JSON files
- XML configuration file for sharing groups
MLAT Server operational modes
- Public Jetvision Mlat server
- Jetvision Dedicated Mlat server, closed network
- Licensed operation on a private server provided by operator
Flexible hardware platform
- Written in native C++, our MLAT server can operate on any Linux platform on x86, amd64 or even ARM. (on special request and charges only)
Radarcape Software Features
Sharing Groups (planned)
- A number of Radarcapes can be combined through our server forming a sharing group, e.g. for wide area supervision or local hot spot precision observation.
- Radarcape MLAT results are shared within such a Sharing Group (third party sources are not)
Filters for 2D or KML
- Altitude, Type (with wildcard), and more
- Fleetwatch Filter:
- Filtering for ICAO HEX ID or registration (wildcards permitted)
FlightAware no compromise feed including multilateration results
- FlightAware sharing supported with no compromises
- MLAT results from FlightAware feeder can be read back into the Radarcape in addition to MLAT results from Radarcape network. The border of aircraft symbols indicates the source
- black: ADS-B
- red: Jetvision MLAT
- green: FlightAware MLAT
Location and flight paths of different sources are stored and output separately
- ADS-B, Radarcape-MLAT, FlightAware-MLAT and Sharing Group results may be observed separately
- These data are also available within the JSON data outputs
- A new field was added to aircraftlist.json which contains the location, altitude, heading, speed and vertical rate for each of the location sources
New feeder for Opensky Network
- Opensky network feeder with no compromises
How to install is explained in the Settings - Radarcape Feeder Settings - Opensky Network page
Automatic update of routes and aircraft type database
- Flightroutes database and basestation database are updated automatically (internet connection required), however manual update is still possible.
- Manual upload service for systems without internet
GPS data is provided to Chrony or NTPD
- The Radarcape becomes a stratum 1 time server
Optimized TCP streams
- In order to decrease network load, network streams became buffered
Signal level in dBm
- The signal level at the antenna connector is indicated in dBm
(note that this is not foreseen for measurement purposes)
Second-of-Day mode selectable
The value range of the second-of-day field in the GPS timestamp is selectable, the current setting is reported in status frame
- legacy mode: value range is 1…86400
- true UTC mode: value range is 0 … 86399
Status Frame 0x34 contents were extended with GPS and UTC information
- Status frames are triggered by 1PPS pulse when GPS timestamps are selected and triggered randomly in case of legacy 12MHz timestamps.
- Status frames contain a valid timestamp
- The signal level value is zero
Byte #0 of the message part contains a mirror of the FPGA switch settings. These settings have direct effect on the raw data ports 10002-10006 and indirect effect due to eventually missing or differently available data to the high level functions:
|Bit 0:||Data output mode
(port 10002 only)
|Bit 1:||Raw data frame types||DF11, DF17 and DF18 only||no pre-filtering|
|Bit 2:||Timestamps within AVR format||enabled||disabled|
|Bit 3:||not used|
|Bit 4:||Timestamp mode||GPS||Legacy 12MHz|
|Bit 5:||FPGA/USB handshake||disabled||enabled|
|Bit 6:||1 bit forward error
|Bit 7:||Mode-A/C decoding||enabled||disabled|
Byte #1 of the message part in GPS timestamp mode contains the offset of the nanosecond timer at the 1PPS event in units of 15.625ns. Normal value range is -3 … +3.
Byte #2 of the message part contains information about GPS
|Bit 0:||Antenna status||good||fail|
|Bit 1:||Tracking at least
|Bit 2:||Tracking at least
|Bit 3:||Time value base||UTC time||GPS time|
|Bit 7:||Daysec value range||0 ... 86399||1 ... 86400|
New responsive web design
- Optimized for web browsers, mobile devices and tablets
Configuration and filters stored in local browser
- Filters are provided for serval properties, like altitude, hex code, registration and type (with wildcards), speed, and more
- Views and filters from different browsers and devices can have individual settings, e.g. different map styles and filters
Openlayers Map introduced in parallel to Google Maps
- Supports different map styles based on gmap and Openlayers
- Border of aircraft symbols and color of tracks shows the source of data
- Black: ADS-B
- Red: Radarcape-MLAT
- Green: FlightAware
- Track is colored by source or altitude (partly implemented)
- Professional Radar map style
- providing only navigatorial data
- free of unwanted map contents
- Track and vector displayed of each aircraft
- border color is data source: black=ADS-B, red=Radarcape MLAT green=FlightAware MLAT
- fill style blue=climbing, yellow: leveling, brown=ascending
KML output for 3D external viewers
- KML output has got 3 filter banks within the Radarcapes, which can be selected in a KML browser separately or even in parallel. Unlike the 2D maps, common KML browsers like Google Earth do not permit adding user specific menues, so this way was choosen. However, these filters are updated without the need of reloading in the KML browser, just submit the new filter and it applies at the next reload.
KML output provides aircrafts in different colors:
- Outer rim:
- Black: localized by ADS-B
- Red: Jetvision MLAT location
- Green: FlightAware MLAT location
- Inner color:
- Yellow: no change in altitude
- Brown: descending
- Blue: Climbing
The color of the track is selected by altitude, and ground tracks are colored in yellow.
Chrony and NTPD Support
Radarcape software provides interfaces for Chrony and NTPD so they can access the GPS data properly. With these, Radarcape becomes a Stratum 1 NTP standard.
Changed Output Formats
In case that the changed output formats are causing impacts with any 3rd level software that we were not aware of, please contact us in order to find the best suitable solution.
JSON files can be controlled by a number of parameters
|vpn||float||View point north limit||X||-||-|
|vps||float||View point south limit||X||-||-|
|vpw||float||View point west limit||X||-||-|
|vpe||float||View point east limit||X||-||-|
|select||avail locs bds||avail: only list of available ICAO
locs: output all available location sources as array
bds: output some selected BDS registers
|knownposonly||0 .or. 1||Output only aircraft with known position||X||-||-|
|since||unix-time||Output since of those which got updates since <unix-time>||X||-||X|
|tracklength||integer||Track length in seconds||-||X||-|
|src||a .or. m .or. f||Override automatich location selection:
a: ADS-B, m: Jetvision MLAT, f: FlightAware MLAT
|lookback||integer||deltadb.txt: Time in seconds from now to history which data is output
flightpath.json: track length
|altitude.from||integer||Minimum altitude in ft||X||-||-|
|altitude.to||integer||Maximum altitude in ft||X||-||-|
|icao||integer||Element of the ICAO Hex ID or registration filter
multiple of it can be provided
automatically detects if HEX or Registration
CSV input capable
|type||string||Element of the aircraft type filter
multiple elements are accumulated
CSV input capable
|flight||string||Element of the flight ID filter
multiple elements are accumulated
CSV input cabpable
- The location, altitude, track, vrate and speed given for the aircraft in the base level follows a priority: ADS-B -> Radarcape-MLAT -> FlightAware MLAT, whichever has provided more results during the last 5 seconds
- The values of the currently three location sources (ADS-B, Radarcape-MLAT, FlightAware-MLAT) can be requested in a separate array with an additional URL parameter &select=loc. Each of them contains a field "tsz" for its track length. Base level elements "tsa" and "tsz" were removed
- Value "dbm" was added, which contains the signal level at the antenna connector in dBm. Note: This is not for measurement purposes
- The values itself are formatted as their native data type (integer, string, float). No longer for example floats as a string. Unknown values are marked as JSON 'null'
- removed without replacement
- now outputs a JSON array with the capability to request several flight paths in one call
- used with parameter "&icao=<hex>" will return the flight path by default priority ranking ADS-B -> Jetvision MLAT -> FlightAware MLAT, an additional parameter "&src=<char>" with char either 'a', 'm' or 'f' will select the flight path from selected location source
- parameter "&icao=<hex>" may be either repeated or either be filled with a comma separated list (e.g. <hex1, hex2>) to request several flight paths
- instead of <hex> it may also contain registratioin, this can be mixed, so for example these are valid requests: &icao=3f1234,D-AQUI or &icao=3f1234&icoa=d-aqui. Using registration requires a loaded aircraft type database and the presence of the aircraft in this database.
- contains information about own location and some more
deltadb.csv / deltadb.txt
- parameter "&loc=" was removed, own location can be read within mapinfo.json
UDP Output and Formats
- The configuration of all UDP ports was separated from General settings into a streaming output configuration page
- A new UDP format which contains a periodic output of changed data in the same format as aircraftlist.json is now provided.
The time interval between each output can be configured.