8
« Last Post by exfirepro on June 04, 2025, 02:23:30 pm »
Hi David,
Coming a bit late to this thread (I have been away on holiday). Also looks like Lee hasn't been back on here for a while.
Have you read the thread in Technical Support re FX displaying licence expired after software updates? I suspect his is what is causing that message to appear. The 'fix' is detailed in the other thread. If not, please get in touch with Ashley on the PilotAware Support number mentionned in that thread.
With regard to the lack of traffic info, it is important to be aware of the following: - The current Fx Unit is designed to be installed and operated as a highly efficient 'stand alone' Pilotaware unit or to integrate PilotAware into existing Flarm or Power Flarm installations, by simply connecting it in series between the Flarm or PowerFlarm unit and the Flarm Users' Flarm Display and configuring the relevant output port on the Flarm device to supply the necessary data. This adds the full range of PilotAware functions, including ADSB Rx and Mode-S/3D (MLAT) as well as SkyGRID Airborne Relay and Ground uplinks of data via PilotAWare ATOM ground stations and iGRID to the original Flarm installation, while integrating Flarm targets to the PilotAware display (on your Nav System or via the PilotAware RADAR screen) and at the same time maintains the original Flarm Proximity Alerts on your Flarm device(s).
To allow this 'dual use' FX has its own internal GPS, (with internal and external gps antenna options) and has multiple powering options, including the option to be powered directly from the Flarm Device and receive Traffic and GPS (Navigation) data via the RJ45 'Input' Port.
Having been involved in the development and integration of Flarm with the PilotAware system since 2016, initially via direct data integration from a FlarmMouse (or PowerFlarm), then later via several prototype versions of FX as a combined/stand alone unit, I currently run my FX in series with the output from my PowerMouse, which is set to provide both Flarm Traffic and Navigation (GPS) data to my FX on the appropriate PowerMouse output port. In this configuration, FX automatically takes its power supply from the Flarm unit via the RJ45 cable.
So as you are using your FX in a similar manner from your PowerFlarm Core, you must NOT use either the direct 12 volt or 5 volt USB powering options on the FX. You also need to configure the chosen output port on your PFC to supply either 'Traffic Data' (if you want FX to use its own GPS with either its internal antenna - or if fitted behind the panel, its supplied external GPS antenna), or to supply 'Traffic data plus Navigation Data' if you want FX to use the GPS signal from your PFC. (I suspect this part is the source of your problem). You must also configure both your PFC and FX (plus your transponder if you have one) to all transmit the aircraft's official allocated ICAO HexID (to aid effective integration and prevent 'ghost' images) and ensure that the PFC output port and FX are both configured to use the same Baud Rate (usually 19,200 Baud, though FX should determine the Baud rate from the signal supplied by the PFC).
I hope this helps. If not please get back in touch and let me know.
Best Regards
Peter
Recent Posts