Intermittent GPS dropout on FX

[dperalta]

Got the FX last September and it has been great so far including a great week of flying around France. Recently we have been getting the dreaded "Seeking GPS satellites" error in Skydemon and can see that the GPS status has either gone red, or is green but is cycling through baud rates (presumably hunting for the dongle). Does this indicate a dongle failure?  See video below for an example.

https://youtu.be/3aky6V5AhtY

David

[steveu]

Can the FX unit itself see the sky? You can test by unplugging the external GPS if so, and seeing if the internal GPS performs any better...

Worth looking at the status page on 192.168.1.1 on the FX itself, to see if the GPS has really lost lock?

[dperalta]

Thanks Steve, the FX unit itself is secured behind the panel and under the coaming so probably can't see the sky. The remote GPS antenna is stuck onto the coaming with a clear view of the sky (through the canopy).  In the attached video above you can see the behaviour in the Status page (cycling through baud rates and switching between Int and Ext).

[steveu]

Sorry, missed the video...

It looks like the FX is changing between internal and external GPS antenna.

At the risk of being slapped for being impudent, is the SMA connector for the GPS antenna fully done up and nothing in the cable damaged?

My guess is the FX uses the internal antenna when no external is detected, and a loose or poor connection here could give issues...

A proper PAW person will be along shortly with the right answer...

[dperalta]

All suggestions welcome Kevin :-)
Yes we checked the connections were done up, but I wasn't aware before this thread that there is an internal GPS sensor. I'll do some more testing at the weekend, placing the unit on the coaming and see if that achieves a GPS lock. That will narrow the issue to either the FX unit or the external aerial.

[Admin]

Hi all
External does not indicate remote antenna, it indicates a remote gps source, eg a flarm input providing gps messages
Can you describe your configuration, most importantly what is connected to the rj45 connectors
FX is seeing data and attempting to decode
Thx
Lee

[dperalta]

Hello Lee,
The RJ45 connector is linked to our Powerflarm Core unit. This provides power and we were hoping it would read Flarm traffic but unfortunately not. This setup has been working well since we bought it last September.

I’ve brought the unit home to do some more testing but unfortunately it’s now saying the licence key has expired. I’ve sent an email to support and will retest once get the licence sorted.

[exfirepro]

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