FAQ
List of frequent asked questions
When using USB cable to power Display, the Display is always ON
In the current hardware of Display, when a USB Cable is connected the Display is always ON, the Power Button only affects the battery power path not the USB power path.
The Power Button still shutdowns the display momentarily since the Display does not know it's being powered via USB instead of internal battery and performs the shutdown sequence but it has no effect, the Display turn ON after a couple of seconds of releasing the power button
How long does the battery takes to charge
A full charge cycle from 0% to 100% should take around 3 hours
When charging the Displays never indicates full battery charge
The current Display hardware does not know when the battery charging cycle has ended (does not know that a battery charging cycle is ongoing either).
At the moment, leave the Display charging, a maximum of 3 hours is enough to charge from 0% to 100%.
When accessing the System page, it shows the current battery voltage, when fully charged the voltage difference between charger connected and disconnected should be around 50mV.
Why am I seeing so much Mode-S traffic instead of MLAT
Display only shows what the external data source is sending, in the case for example of Aero-Tracker it is it's responsibility to merge the Mode-S traffic that it may receive with SafeSky data, MLAT traffic detection depends on the aggregator website that is being used to see the data and may not always exists in all aggregators.
The aircraft CallSing shows as ICAxxxxx
This happens when using Aero-Tracker and it hasn't receive the full ADSB messages to associate the ICAO ID to the CallSign
The aircraft CallSign shows as syXXXXXX
This is related to Aero-Tracker configuration option Highlight SafeSky Traffic that may add the sy prefix to some traffic.
Can't connect Display to other traffic sources (like SkyEcho)
At the moment the Display was tested connecting to SafeSky App, Aero-Tracker and SoftRf dongles, testing with other devices is expected in the future depending on being able to get those devices to test.
It should be compatible with other devices that transmit data using GDL90 protocol data on UDP Port 4000, for that the Display needs to be connected to the same WIFI Network has the receiver and have the GDL90 Wifi protocol enabled.
This support is dependent on the data source to send a certain GDL90 messages types, if not all the required messages types are not received it may not show any information.
The Display is not compatible with Sentry device, although it uses a GDL90 like protocol, it uses a proprietary messages type that are not supported.
Does the Display stores logs internally
No, the Display does not store event logs internally for latter troubleshoot, this functionality may be added latter.
At the moment, it possible to log some Display events and received messages using the USB connector, the Display should appear on the PC as a regular Serial Com Port and the user can use a serial terminal software to log the data if necessary to send to FlyData for analyze.
Since this is a USB direct connection to the processor, the Baud Rate selection doesn't matter, but choose a high value if possible, the rest of the serial port configuration should be the defaults (8 Bit Data, 1 Stop Bit, No Parity, No Flow Control).
If possible use a serial terminal software that can add timestamp information to each line received.