Bonne Apres-midi, Guy,
Hmm!
No PW ATOM at LFLE unfortunately.
Looking again at your original post, together with the 'error' reports on the 'Logging Screen', and the fact that both the 'P3i' and the 'Barometer' are reporting as 'Unavailable' on the 'Home' screen, there could be a connection between these and your lack of Flarm uplinks via P3i - especially if you have been flying within range of LFLG.
The P3i transceiver and the barometric pressure cell are both mounted on the PilotAware 'Bridge' and if, for example, the unit isn't getting a '3D' GPS fix (which yours says it was - at least at the time you took the screenshots), or the GNSS altitude (GPS based altitude) doesn't match the reported barometric altitude within defined limits
or no barometric altitude is available due for example to a software issue or a defective Baro Module -
the Bridge won't transmit P3i, which in turn won't trigger the LFLG ATOM into 'Uplink Mode', so you won't get their Flarm data -except potentially via iGRID, though that still might not report if the system hasn't been able to calculate
your altitude. That would certainly account for you not receiving Flarm Uplinks from LFLG.
Unfortunately, the only easy way to tell if your Rosetta is transmitting is to check it locally against another Pilotaware, or run it near a local ground station and get me to check the database afterwards to see if its transmissions have been received.
Although this could, as I have said, indicate a Bridge fault, the Bridge is usually extremely reliable and if it isn't working, it is much more likely to be due to a corruption of the software such as due to a defective microSD card, so before thinking about replacing the Bridge, it would be worth carrying out a few simple tests as follows...
Firstly, (with the unit powered down) check that the MicroSD card is fully seated in its slot (between the two antenna connectors). It is a simple slide out - and push carefully back in. If you can then connect your Rosetta to a monitor (or TV screen) via the Rosetta's HDMI socket, power up the Rosetta and check that it runs right through the 'boot' sequence without showing any obvious errors on the monitor. You don't need to read everything - just look for any obvious error messages. If the boot sequence gets to the point where the screen stops and reports 'Login' that is the sequence finished and the unit should now be running. You should now be able to 'log in' to the PAW WiFi and check if the P3i and Barometer are still reporting 'Unavailable' or if they have gone green.
If necessary repeat the test by rebooting the unit outside with a clear view of the sky so it can get a good view of GPS satellites - then log in to the PAW WiFi with your phone or tablet and check again.
If there is still a problem, the next thing to try would be to load a new copy of the latest PAW software -available from
https://pilotaware.lode.co.uk - and preferably loading it onto a new microSD card. If necessary, I can talk you through this process if we get to that point.
If the P3i and Barometer are still 'Unavailable' after loading new software, I would suggest returning your unit to PilotAware Support for full investigation, but try the simple tests first and let us see how we get on.
Best Regards
Peter
p.s. Let me know when you have read this, and I will split this discussion off into a new thread and leave Lee's original thread for issues directly related to the Flarm Protocol Update.
