Comment on page
Combine RealTraffic and LiveTraffic for real live traffic
RealTraffic of Inside Systems Pty Ltd "consolidates data from multiple international ADS-B and multilateration networks to obtain information about other airplanes near the position of your (simulated) aircraft – in realtime, live! ..., it then injects this traffic so you can fly with it, or follow it."
"Please download the software and test whether it does what you want it to prior to purchasing a license. During the demonstration time the software is fully functional! If it doesn’t work during the demo, it won’t work after purchasing a license!"
From LiveTraffic's point of view, RealTraffic is just another channel feeding tracking data. LiveTraffic and its author are not affiliated with Inside Systems and don't receive any money or other means of kickback from Inside Systems.
RealTraffic receives tracking data from multiple networks and then broadcasts this data in consolidated form into your local network where it can be picked up from software like LiveTraffic, PSXSeecon, or Foreflight. This broadcasted data also includes weather information of the nearest weather station, which primarily is required for converting barometric altitude readings to geometric altitude.
To learn about the simulator's current position, RealTraffic connects into LiveTraffic, which triggers LiveTraffic to send regular position updates back to RealTraffic. RealTraffic then sends the traffic in a 100nm radius around this current position.
While all this might sound a bit tricky it is all well encapsulated in the implementations of both LiveTraffic and RealTraffic. It just affects configurations and status displays a bit.
There are 3 steps to do:
- 1.Install RealTraffic and verify, „Spotter Mode“ is working
- 2.In RealTraffic, change Simulator in use to „LiveTraffic“ and shut down.
- 3.In LiveTraffic, enable the new channel RealTraffic, then start up the RealTraffic app again.
If you installed it correctly then you should be able to see tracking data right within RealTraffic, i.e. even without starting X-Plane / LiveTraffic. The so-called "Spotter Mode" allows you to tell RealTraffic a location for which it then starts showing traffic:
- 1.Set Simulator in use to "Spotter Mode", and
- 2.select an airport of interest from the drop down Select airport (when the drop down is open then typing on the keyboard searches within the list)
RealTraffic in Spotter Mode to verify RealTraffic's operation
If you have trouble getting this far, i.e. you don't see traffic in Spotter Mode, then you won't see anything in LiveTraffic either. Seeing traffic in Spotter Mode is a precondition for successful setup. In case of issues up to here I ask you to check out "Fault finding / debugging instructions" at Inside Systems.
Change Simulator in use to "LiveTraffic".
This is the configuration to be used for sending traffic to LiveTraffic:
RealTraffic configured for use with LiveTraffic, using LT's current position and heading
Note that RealTraffic shows current traffic around your current location as soon as it knows that location...but not earlier. So X-Plane / LiveTraffic need to be connected, see below:
- 1.Startup X-Plane with LiveTraffic.
- 2.In LiveTraffic open Settings > Input Channels > RealTraffic.
- 3.Enable RealTraffic and OpenSky Network Master Data, disable the other channels (OpenSky and ADS-B Exchange) for the moment (you may re-enable them later after you confirmed RealTraffic to work) The Traffic Port setting should read
49005, the port RealTraffic publishes its data on. (Historically, there was a fallback option to use
49003, but since RealTraffic 9.1.206 this option no longer exists.)
- 4.Ensure Show Live Aircrafts is enabled so that LiveTraffic wants to show planes.
- 5.Status below RealTraffic will switch to "Waiting for RealTraffic..." after a moment (screenshot below).
- 7.LiveTraffic is now receiving tracking data and will displaying the first planes after the usual buffering period has passed.
Settings > Input Channels > RealTraffic, waiting for connection
In normal operations it should not matter if LiveTraffic or RealTraffic starts first. Both should connect to each other. If LiveTraffic keeps reporting "Waiting for RealTraffic..." or "Connected passively..." over more than a minute try switching RealTraffic's Simulator in use to Spotter Mode and then back to LiveTraffic mode, or even restart the RealTraffic app.
The Traffic Port setting determines the UDP port LiveTraffic listens to for incoming traffic data. Use
49005, on which RealTraffic publishes the highest-quality data. Touch this only carefully, see Technical Details below.
If you change the Traffic Port you need to briefly disabled, then re-enable Show Live Aircraft, ie. LiveTraffic's "main" switch, for the new port to become effective.
When you set up X-Plane to use a specific date/time of the year, then LiveTraffic sends this date/time to RealTraffic, so RealTraffic can provide you with the correct historic traffic at that point in time. By default, the time is adjusted for the buffering period, so that eventually the displayed traffic matches up exactly with time in the sim. You configure if the time is sent and if it is corrected for the buffering time in the drop down box Simulator Time Control.
In the RealTraffic app, you must activate the option Simulator controls time offset in RealTraffic's Advanced Settings.
The RealTraffic app displays the time offset in use and if it is controlled by the simulator or not.
If in RealTraffic, the Simulator controls time offset option is disabled, then the RealTraffic app supports to go back in time by use of its time slider and date selector:
Time Slider and Date Selector in RealTraffic app
RealTraffic status text informing of "historic traffic" from some time ago
When you change X-Plane's simulated time, or RealTraffic's time slider while traffic is already displayed in LiveTraffic, then expect some unrealistic plane movements to happen while LiveTraffic adapts to the changed plane positions.
If other channels provide real-time data in parallel then expect inconsistencies between these two sets of planes. For example, the "historic" planes and the real-time planes may collide or take-off / land in opposite directions.
The following details might come in handy when analyzing network issues, e.g. when different application seem to get in conflict:
- TCP/10474 is a direct TCP link from RealTraffic to LiveTraffic: LiveTraffic has to open a TCP port (10747 by default) to which RealTraffic connects. Once established, LiveTraffic then periodically sends its current location via this link back to RealTraffic so that RealTraffic can filter and send the traffic data of that area.
- That port number is configurable in RealTraffic's UI, called Simulator Port, standard is 10747
- In LiveTraffic, it can also be configured, but only by directly editing the preferences file (while X-Plane is shut down!)
<X-Plane>/Output/preferences/LiveTraffic.prf. The relevant entry islivetraffic/channel/real_traffic/listen_port 10747
- UDP/49005 is the port traffic is received on. This port can be configured in LiveTraffic (see above). In release prior to 9.1.206, RealTraffic had published up to three formats in parallel, but since then only RTTFC is published any longer:
- 49002: ForeFlight format
XTRAFFICPSX(no longer in use),
- 49003: extended format
AITFC(no longer in use),
- 49005: RealTraffic format
RTTFC(only format actively published by RealTraffic and hence LiveTraffic's default).
- UDP/49004 is the port on which RealTraffic periodically sends weather data (necessary to convert baroemtric altitudes).
There would be errors written to
Log.txtif data arrives on these UDP ports that LiveTraffic doesn't understand, ie. if they don't comply with RealTraffic's formats ("RealTraffic: Discarded invalid message"). Such errors would happen if some other device sends other data on
4while LiveTraffic listens. These messages wouldn't do any harm to LiveTraffic except for
Log.txtoutput. But they do indicate a network conflict that should be solved.
Last modified 6mo ago