Recent Posts

Pages: [1] 2 3 ... 10
1
PilotAware and FLARM have been working together to discuss how their products will converge in future developments to ensure full interoperability between the two systems.
Today's press announcement confirms our intent to work together for both Future and legacy products.

https://www.pilotaware.com/post/flarm-and-pilotaware-cooperate-to-enhance-aircraft-safety-through-interoperable-solutions

We both believe that this is a significant step forward in aviation safety for manned and unmanned aircraft.

Let us know what you think!

Post on your favourite Forum
2
Technical Support / Re: Dead Rosetta - SD card slot has come adrift - Updated
« Last Post by JCurtis on April 15, 2024, 03:26:54 pm »
Good luck, Peter!

The Pi is (at least) a 6-layer PCB, so you may need to pre-heat it a little to make life easier.  You will need a good flux when removing the cardholder and gentle lifting until it becomes free.  Clean the pads to get them as smooth as possible. Flux and solder wick are all you need.

Any lead-free solder paste should be OK for the replacement.  Personally, I use a SAC305 paste for manual assembly work, specifically SK P2-5 SAC306 88.5 20-30 T4 from SolderKing, made in the UK :-).

Out of interest, do they still use Molex 1040310811 cardholders?

3
Technical Support / Re: Dead Rosetta - SD card slot has come adrift
« Last Post by exfirepro on April 15, 2024, 03:09:47 pm »
Follow-up For Information

I asked Graham to send me the old board so I could examine it - never having come across this fault before. I have it sitting here in front of me as I type - thanks Graham.

The following is simply a statement of what I found and should not be taken as implying any negligence or inappropriate action by Graham - simply a cautionary tale for us all. It could easily have happened by the projecting end of the microSD card catching on something at any time when the unit was being fitted or removed from the plane, or from any bag it might have been carried in.

You should be able to see from Graham's earlier photo that the card slot comprises a thin stainless steel 'cover' into which is clipped a plastic 'inner', which forms the card mount itself and contains the contacts to link the card to the board. The two parts are held together during construction by very small moulded clips at each corner of the plastic liner. The card slot also contains a fine 'reed microswitch' inside the right-hand side at the back - which closes when a card is installed, telling the board that a card is present. The whole unit (including the 4 case mounting points, 8 separate card contact fingers and the 2 switch contacts) is then surface mounted onto the PCB during manufacture as a single unit.

Unfortunately, this one looks like it must have experienced downwards pressure being applied to the projecting card end at some point, which has dislodged the stainless steel cover from the plastic clips and broken the casing away from the PCB, though the printed circuit board itself looks intact (i.e. the damage hasn't pulled the tracks off the board). The reed switch has, however, become twisted and distorted (probably simply by trying to reinsert a card after the case had unknowingly sprung apart). Unfortunately this means that the only practical 'repair' will be to remove and replace the 'card slot' as a unit.

As an exercise, I have now obtained a replacement card slot and tracked down a friend with the necessary temperature controlled heat-gun equipped solder station to carry out the repair. Now I just need to find the time to give it a go.

Best Regards

Peter
4
Technical Support / Re: Dead Rosetta - SD card slot has come adrift
« Last Post by grahambaker on April 15, 2024, 02:06:44 pm »
Just to bring this to a close - the Pi transplant worked like new on Friday when I finally had the chance to test it in the air :)

Side benefit - all the USB ports, and more importantly the power socket, are nice and snug on their respective plugs.
5
General Discussion / Re: Aircrew.co.uk and PilotAware Playback Sites
« Last Post by BobD on April 12, 2024, 03:16:48 pm »
Thanks to James Rose (ex of aircrew) https://playback.pilotaware.com/playback/ is now back up and running.

Thanks James !
6
Technical Support / Re: Problem Receiving FLARM with Rosetta (in France)
« Last Post by exfirepro on April 11, 2024, 08:39:37 am »
Further Update added Thursday Morning at 08.27(UK time)

Hi Guy,

Reflecting on this again in the morning, when I've had a cup of tea and my brain has woken up a bit, the sudden drops in altitude on the track profiles almost certainly reflect drops in connectivity  - either between your phone and available cell towers on your mobile network or between your PilotAware and local ATOM, OGN or other sites, though the reasons for these drops can be complex and warrant further investigation.

I will send you a PM.

Regards

Peter
7
Technical Support / Re: Problem Receiving FLARM with Rosetta (in France)
« Last Post by exfirepro on April 10, 2024, 11:24:21 pm »
The Saga Continues!

I had previously disregarded checking via the Ground Station Replay Tool for 6th April as there was no data reported in the PilotAware database for that date - presumably due to the previously reported server issues.

Wrong decision  ::) !

Looking again at the Groundstation Replay Tool with this new information, I can track your aircraft on PilotAware and Cellular heading south-west towards LFLG from just north of Tencin - reporting at that point on screen as at ~ 5000ft, though your virtual radar 'profile' clearly shows your height as 6000ft plus - but with significant altitude fluctuations*. You are reporting from the same point as connected to the LFLG ATOM as you passed over Laval and Saint Mury-Monteymond, then LFLG lost contact with your PilotAware briefly (probably due to terrain) as you passed south of Lac de Freydieres. It picked you up again very briefly as you crossed the D111 Route de Chamrousse for the first time, then seems to have lost contact with you again (on PilotAware) a few seconds later at 10.04 as you were about to cross the Route de Chamrousse for the second time. Your track, however continues via cellular all the way to your landing at Gap Tallard at 10.32.

* at this time of night, I can't remember what the reason for that is - might be a GPS or Baro issue - perhaps Lee can advise.

I  then see you again (via Cellular) taking off from Gap at 13.05 and can follow you all the way back to your landing at Chambery - mainly on cellular, except for a few small breaks in cellular signal from where you pop back up on PilotAware at 13.20 as you pass over the ridge into the valley south of Grenoble and you then drop out of P3i contact again at 13.24 very near the point at which LFLG first picked you up on P3i on your outward flight. Your track then continues (on Cellular only) all the way back to Chambery.

This means that your PilotAware and iGRID were both working as expected during both flights on 6th April, and confirms that PAW uplink is limited along that route (due to terrain) to the area between Tenom and La Petoune de Belledonne and along the Grenoble Valley in close proximity to the only existing ATOM Station at LFLG - which is exactly as I would expect.

Not sure how I can see the aircraft at Gap on 7th April via a Cellular report, though this looks like a genuine report. I guess it must be a glitch in the data.

The (Cellular) reports I see from your aircraft on the ground at Chambery on 8th April are obviously from when you were looking for the local gliders. The only reason I can think of for not seeing any would be that the local OGN station(s), the gliders themselves, or both, hadn't yet updated their software to the new Flarm Protocol, so they weren't 'visible, or available for uplink locally via iGRID.

This now makes much more sense  :)

Best Regards

Peter

8
Technical Support / Re: Problem Receiving FLARM with Rosetta (in France)
« Last Post by DY691 on April 10, 2024, 07:29:35 pm »
Thank you for your efforts
My flight on the 6th was to Gap ...not the 7th as it was a Sunday and the restaurant is closed on Sundays...
I can confirm that the following days were ground tests.
hoping that Lee will find an explanation
Thanks again
Guy
9
Technical Support / Re: Problem Receiving FLARM with Rosetta (in France)
« Last Post by exfirepro on April 10, 2024, 06:50:28 pm »
Postscript:

This is a very puzzling case  ???

Nothing showing on the database for any mode from 38533C from 6th April.

You say that the flights on 7th and 8th April were 'not really flights but ground tests at LFLE (Chambery)' - so I wouldn't expect to find any reports of reception for either of those dates from PWLFLG2 (Grenoble) at 40Km away, which is consistent with my comment that the only reports for those dates were Cellular.

Looking on the PilotAware Playback Site https://playback.pilotaware.com/playback/groundstations/  (...which is based on data collected by the PilotAware ATOM-GRID Network and via iGRID Cellular connection), your aircraft 'pops up' (via its cellular signal) on the ground at Gap Tallard at 16:17 (UTC ?) on 20240407 - a long way from Chambery!! It seems to remain there on the ground at Gap Tallard for about 2 minutes before disappearing 'offline' and I can find no other reports from it that day. In order to get there, by air, you would (presumably) have flown from Chambery right past Grenoble, yet there is no PAW (or ADSB) report on the database from PWLFLG2 to report such a flight. (That is explained by your comments, sent while I was investigating and typing this response, but why would your aircraft show up at Gap Tallard in the first place?)

The next time I can find your aircraft is the following day (20240408), reporting very briefly - again via cellular, but for a few seconds only, back at Chambery at 09:40 UTC before disappearing and reappearing (again via Cellular) apparently heading north past Pontcharra at 09:45. Your comment about the ground tests would explain the unit popping up on the ground at Chambery, but why would it reappear 5 minutes later about 10Km away at Pontcharra - unless that is something to do with the cellular masts that your phone was connecting to during your ground tests.

For completeness, I have just logged in directly to the ATOM at LFLG and it appears to be working normally, reporting both ADSB and Flarm traffic - as I would expect it to.

Hopefully Lee can throw some light on what may be going on.

Best Regards and Bonne Soiree

Peter
10
Technical Support / Re: Problem Receiving FLARM with Rosetta (in France)
« Last Post by DY691 on April 10, 2024, 06:09:17 pm »
Hello Peter
My last flight near the LFLG satation was on 6 April. I passed almost vertically over the LFLG field at 6500ft to the south at 1002 UTC and passed north again at 6500ft almost vertically over the LFLG field at 1323 UTC.
the distance as the crow flies between LFLE and LFLG is 40km but there is a lot of relief between them
I think that the flights on 7 and 8 April were not really flights but ground tests at LFLE to see if I was receiving gliders flying within 5km of my position ... unfortunately no gliders were reported...
Thanks for your help
Have a nice evening
Guy
Pages: [1] 2 3 ... 10