Radarcape:User Services and Interfaces

Introduction to Radarcape Services and Interfaces

A Radarcape offers several services to a user, either for direct use or use with second level software.

All services can be used in parallel, only limited by the processing power of the Radarcape.

High Level Interfaces

High level interfaces are such which are for direct use by the operator without using special ADS-B software.

• Aircraft List

This is a list of the aircraft that currently are in your neighbourhood. For displaying you need nothing more than a web browser. The table can be sorted by any kind of column, like time, ICAO ID, altitude and more. It refreshes itself after a configurable time. Omit time and delete time are configurable as well.

For details see Software Features - Aircraft Table.

• 2D Map Output

Nothing else than a simple web browser and an internet connection is needed in order to display 2D maps originated directly from the Radarcape's aircraft list. The same display may be known from other application SW. This display is ideal for quick remote observation.

For details see Software Features - 2D Display.

• KML output (3D display)

This output is designed for the use of KML capable readers like for example Google Earth. For the same aircraft that are displayed in the list, a 3D display of their tracks is generated. The display refreshes itself, which will result in a live display.

For details see Software Features - 3D Data KML Output.

• Web configuration

Configuration of various items is handled by a web interface. There are no longer DIP switches available. Still the FPGA configuration can be overwritten by high level software. The web interface is password protected, default password is "radarcape"

For details see Radarcape Configuration.

Medium Level Interfaces

Medium level interfaces are to be used by software.

• Port 30003 data

Port 30003 is a decoded interface in comma separated format which contains pre-decoded values. As the encoding of Mode-S and ADS-B messages is not so simple, this is the easiest way how second level software can access the data that is received by the Radarcape. The only bottleneck of this interface is its inefficieny with respect to processing power and data handling, so if you can avoid, please do.

For details see Software Features - Port 30003 Service.

• deltadb.txt web page

Similar to Port 30003, deltadb.txt can deliver pre-decoded data. It is serviced by the internal web server, so requestors will receive a list of changes in the aircraft list which have either happend since the last request or a time that can be given as parameter.

For details see Software Features - DeltaDB Service.

Low Level Interfaces

There is plenty of SW availabe that can decode Mode-AC, Mode-S and ADS-B by itself. For these, the Radarcape provides raw data in different qualities and quantitites:

• TCP port 10002

raw data as it is received by the FPGA board, includes all errors, broken frames and more. DF-11, DF-17 and DF-18 are CRC prechecked if selected in the configuration.

• TCP port 10003

Mode-AC, Mode-S and ADS-B raw data but all frame types in Mode-S/ADS-B have passed CRC checking. This is the recommended port if you want to route full data through a slow speed network connection.

• TCP port 10004

Mode-S DF-11, DF-17 and DF-18 only, all frame types prechecked. This is recommended in case that you only are interested in locatable aircraft and don't need every possible update.

• TCP port 10005

Mode-S frames of non-ADSB aircraft only. This is a special port for streaming multilateration clients.

For details see Software Features - Data Streaming to Network.

Build-in Feeders

The Radarcape comes with a pre-installed feeders for the platforms Flightradar24, PlanePlotter, Planefinder, and FlightAware. You may enter your private sharing key that you got from them in the configuration dialogue. The service can be disabled in the configuration menue.

For details see:

• Flightradar24 Feeder
• Planeplotter Feeder
• Planefinder Feeder
• FlightAware Feeder