Messages

1

Technical Support / Re: iGrid Dongle - working or not?

« on: August 21, 2025, 09:57:13 am »

OK Chris,

Thanks for getting back to me. Please let me know how you get on.

Any probs, screenshots will help.

Regards

Peter

2

Technical Support / Re: No Igrid connection - Resolved

« on: August 14, 2025, 12:05:11 pm »

Hi Again Judd,

Thanks for the update. Good to know it is now working as intended (and hopefully some clarification for those others reading this).

i will update the thread title to indicate this has now been resolved.

Best Regards

Peter
(Moderator)

3

Technical Support / Re: No Igrid connection

« on: August 13, 2025, 03:49:17 pm »

Posted prior to Judd's Update above ^^^^

Hi again Judd,

Not trying to be 'smart', but If you haven't already done so, I highly recommend having a good read at the full FX instructions, available via this link...

https://www.pilotaware.com/kb/fx/getting-started

I was reading them again myself last night and - despite extensive involvement in FX testing for a considerable period of time prior to its release - I learned (or was reminded of) several important points by doing so. Hence my recommendation.

Please keep us posted as to what you find when you get back to your aircraft.

Best Regards

Peter

4

Technical Support / Re: No Igrid connection

« on: August 12, 2025, 10:48:22 pm »

Hi Judd,

Not sure exactly what is going on here, but you should be aware of the following: -

A Blue iGRID LED indicates that your FX is connected to your cellular hotspot,  but that the device providing the hotspot DOES NOT HAVE A CONNECTION TO THE PilotAware SERVERS. There could be several reasons for this, including lack of accessible cellular masts at the height or location where you are flying, that your data allowance has run out, or that there is some other complication preventing your 'Hotspot Device' communicating with our servers via your chosen mobile network.

It is also possible that recent updates in the iPadOS firmware of your Ipad Mini 6 might now preclude the iPad providing a hotspot via its 4/5G connection while simultaneously processing data received from Pilotaware via its internal WiFi. I deliberately don't use my Sim Equipped iPad Mini to provide the hotspot for my FX - preferring instead to take the hotspot from my Galaxy S23 phone, so I can't say if that is the case or not (and I can't test it for a while as I am due to go into hospital in a few days - sorry).

In addition IIRC, (though this might have changed since iGRID was first introduced), the system was designed to limit data use by automatically restricting iGRID where you already have a solid connection to one or more ATOM Stations and are already receiving all relevant data via the Ground Uplink from the ATOM(s).

While the presence of a GPS lock is essential for determining the position of your PilotAware - PilotAware will not for example transmit its own position and can't report the positions of other traffic if it doesn't know exactly where it is itself - I'm not aware of what effect a lack of GPS position would have on iGRID, though I can see that this might preclude uplink of data if the PilotAware effectively doesn't know where it is. But you say that you are getting a GPS lock - so this should be academic in your case.

i will, however, make some further enquiries and get back to you.

Best Regards

Peter

5

Technical Support / Re: iGrid Dongle - working or not?

« on: August 12, 2025, 09:57:24 pm »

Hi Chris,

You say that you have a Hotspot configured, but the screenshots are telling me that there is no Hotspot available to your Rosetta. Was the hotspot definitely turned on on the relevant device (presumably your phone - unless you are saying that you have a sim in your Galaxy Note 3 Tablet - sorry, your post is very unclear on that point).

Did you check the settings on the PAW Network Screen to make sure the 4/5G Hotspot was on and being seen by your Rosetta and to make sure your Rosetta could connect to it?

Can you post screenshots of the network screen to show what is going on please.

Best Regards

Peter

6

General Discussion / Re: USB Cigarette Lighter Adaptor

« on: June 04, 2025, 02:44:42 pm »

Hi Dave,

I echo the recommendation posted by Steve. That Anker adapter is good on both 12 and 24 volt systems

Just a few words of warning as you say you have been experiencing voltage issues throughout April with the official lead and recommended power pack...

1. It may just be that your power pack is getting 'tired',  but check that you don't have a defective cable or a faulty microUSB connection at the PAW power input socket. You can do this by powering up the unit then gently wiggling the cable while observing the RED Power LED (below the P3i 869MHz antenna on Rosetta -visible (with some difficulty) through the ventilation slots above and to the side of the microUSB socket), or at the bottom left end of the ventilated rear panel on the PAW Classic. This LED MUST remain solid red - any sign of dropouts indicates a cable or socket fault. If you need to replace the cable make sure you use the recommended one (available from the shop on pilotaware.com). Socket faults are a bit more complicated. In this case, let me know and I will advise further.

2. Assuming the above test is OK, you can go ahead with using the Anker socket but beware of plugging a second device - especially a power hungry 'low charge level' phone or tablet into the 'spare' USB port on the adapter or you will be back to square 1.

Hope this helps

Best Regards

Peter

7

Technical Support / Re: Intermittent GPS dropout on FX

« 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

 

8

Technical Support / Re: Permanent mounting of a Rosetta in a C42

« on: June 03, 2025, 05:32:04 pm »

Hi Phil,

I just took a look at the 'Fixed Installations' Forum, - which is worth a look in any case for general awareness - but there isn't a specific post there for the C42.

The 'traditional' mounting position in a C42 for a PAW Classic/Rosetta/or FX (with supplied directly attached antennas and internal GPS), is on top of the coaming just in front of the centre struts, with power and feed out (audio or transponder feed) cables going down through the coaming. You are correct that the units were often mounted using velcro or similar - which, in my experience (I have been installing and using PilotAware in its various iterations in many different aircraft types since prototype development began way back in 2015), has always been perfectly adequate to retain the units in place, though I can't say I have ever actually tested a purely velcro installation to 9x the unit weight. Remember of course that there are (or at least were when I last looked) different test requirements for different directions of pull.

In practice, both Rosetta and FX have a standard 1/4" 'tripod' thread incorporated into the underside of the casing. This can be used to attach the unit to any appropriate part of the aircraft structure using an appropriately sized screw. Just speak to your inspector to make sure they are happy with your chosen location and mounting solution. Also be aware that if you are NOT mounting the unit 'right way up' you should replace the internal GPS with a (remotely located) GPS 'mouse' with a good clear view of the sky.

In addition to the 1/4" 'tripod' mount, FX also has 2 x 5mm threaded holes to allow additional mounting options. Just make sure that in both cases the screws you choose aren't too long - they should provide a solid mount without 'bottoming out' in the mounting hole(s).

In all cases, I would advise using PilotAware's external antenna kits as these significantly improve range and reliability of signal - even in flexwings and other fibreglass or fabric-covered aircraft. These antennas should be mounted on the underside of the aircraft (on a metal ground plane unless the aircraft is metal skinned) and kept away from transponder antennas to avoid potential interference.

If you need any further advice please don't hesitate to ask.

Best Regards

Peter

9

Technical Support / Re: Pilotaware FX claims licence expired after firmware update

« on: June 03, 2025, 04:50:25 pm »

Hi All,

As Ash has stated above, an Automatic or Manual software update, followed by an Auto or Hard restart (switch the unit off, then on again AFTER the update has completed downloading) should fix this issue, provided the unit gets a full GPS fix (so might not work immediately if the unit is indoors or in a metal hangar).

I have updated the Thread Title accordingly.

Best Regards
Peter
(Moderator)

10

General Discussion / Re: SD Shows ICAO code rather than Aircraft Reg - See Technical Support Forum

« on: June 03, 2025, 03:18:39 pm »

To avoid confusing duplication with the thread of the same title posted by the same OP in 'Technical Support', I have now locked this thread.

Peter Robertson
Moderator

11

General Discussion / MOVED: New FX user questions

« on: June 03, 2025, 03:09:05 pm »

This topic has been moved to Technical Support.

http://forum.pilotaware.com/index.php?topic=2401.0

12

Technical Support / Re: Internal antenna orientation

« on: April 21, 2025, 10:59:02 am »

So for the avoidance of doubt:

- while all pictures on the website and in the instructions you linked to, show the horns of the di-pole pointing left and right (i.e., horizontal orientation)

- the intended, correct way is for the horns to point up and down. And therefore the cable to exit antenna assy to the side.

Correct?

Hi Tim,

Correct!

If two polarised antennas are not in the same orientation, that will result in a loss of signal between them. The loss of signal can be up to 3dB (i.e.50%)with antennas at 90 degrees to each other e.g. one vertical and the other horizontal. The standard orientation for VHF comms and UHF nav and EC antennas used in aviation (and in practice most mobile communications) is Vertical, so we should ensure that our antennas meet this as closely as possible* and take the 'hit' when our aircraft are in a turn (in reality this is only a significant issue if doing aerobatics).

* In practice mounting the antennas completely vetical is not always possible and antennas are then usually fitted to match the slope of the window for example, accepting that there will be some degree of loss - though if 'as near to vertical as possible' this should be minimal.

Hope this clarifies the situation.

Best Regards
Peter

13

General Discussion / Re: Map of ATOM stations

« on: April 21, 2025, 10:02:33 am »

Hi Tony,

There is no 'publicly available' site to see current status of ATOM sites.

Playing your track back  via the groundstation playback tool, however, shows the ATOM stations which have reported your flight (during the flight) by the green connecting lines between your aircraft andd each individual reporting station. If you have the flight tracks (downloaded from Classic or Rosetta), you can also view these via https://playback.pilotaware.com/playback/

In addition, you can also view site status 'live' via display screens at many airfield sites - such as the one in the clubroom/cafe at Popham, or by installing and running your own ATOM site (which gives you access to your own display as a station maintainer).

As a system Admin, I have access to all ATOM sites, and have attached a screenshot taken a few minutes ago from the site at Solent (which shows a few sites (including Popham) currently down for less than 3 days (yellow markers). If down for more than 3 days, these markers change to red and eventually disappear iof the site is not reinstated. The system automatically advises station maintainers if and when their site(s) go down for any extended period, but we have minimal influence as to how long it takes for the site to be reinstated.

Hope this helps

Best Regards
Peter

14

General Discussion / Re: Map of ATOM stations

« on: April 08, 2025, 10:27:05 am »

Hi Tony,

Thee isn't a simple readily available map of ATOM sites, but if you let me know what area you usually fly in, I can print an post a screenshot of that area for you.

Best Regards

Peter

15

Technical Support / Re: Volume too quiet

« on: March 10, 2025, 11:36:57 pm »

Hi Marioair,

Is PAW team willing / able to publish stats on what proportion of detections are Mode C/A bearing less.  This might sway me to using SD audio.

As you know, we had this discussion a year ago here...  http://forum.pilotaware.com/index.php/topic,2348.msg24310.html#msg24310

I can't give any precise figures, but in the intervening year, numbers of aircraft emitting solely pure Mode-C, or emitting solely Mode-S in areas where this is unlikely to be triangulated and uplinked via ATOM, SkyGRID or iGRID have further reduced significantly to the point where I hardly ever see bearingless target alerts these days.

Don't get me wrong, I would still prefer that FX detect and report at least bearingless Mode-S, where out of ground station or triangulation range, but I am told this just isn't possible with the current chipsets used in FX. I live in hope that this function will be re-introduced in a future version as more powerful and effective chipsets become available. In the meantime, however, I am prepared to take the risk for the additional efficiency and reliability benefits of the completely in-house developed FX (used with SkyDemon audio alerts).

Best Regards

Peter