GPS failure

Nope, didn't fix it for mine.

I haven't had any recent GPS issues.

Just curious, for the people that were having GPS problems before 10.1 - have those problems been resolved? Did 10.1 fix the GPS lock problem?

I had multiple failures on 5/26/15. I've downloaded th logs and sent them to techsupport@avidyne.com. Is that sufficient or should I send them to a particular tech?

Gene

Thanks Steve. So a yellow GPS indication without active flight plan leg is fine as long as there is no CAS message.

The colour of the the Nav Source State (GPS) isn't a sure indicator of lack of GPS lock (will be yellow if no active leg programmed, often the case on the ground after startup). So the GPS lock needs to be confirmed by reviewing the Aux/Sys/Select GPS page (or indirectly via a quick "direct to" somewhere to force the state to green).

What is/are the status(es) on the GPS page that indicate GPS lock? SBAS Nav would seem to qualify. Are there others? The PG doesn't indicate the various possible values of this field. Other than this, it would seem that GPS lock would need to be deduced from sum of the various quality indicators on the page (Nav mode, HAL, VAL, Position, HPL/VPL, GPS alt, satellite signals, etc).


Edited by chflyer - 26 May 2015 at 4:26pm

Add me to the list of people who have had GPS fail to acquire at start-up.  I restarted the unit in flight and it was able to acquire.

Eventually my IFD540 lost all ability to maintain a lock on the GPS satellites.  I had to resort to using my backup IFR GPS, a Garmin 430W.

comancheguy wrote: So, Simpson emailed me about the right knob push changing between heading/track/north up.     I verified on my flights over the weekend and to the avionics shop on Monday, that pushing the right knob DOES in fact switch between the views.  (Duh! Operator error).    Not sure how I missed that.  I suspect, that the setup page setting is the default view (heading up or track up)?

Edited by oskrypuch - 12 May 2015 at 11:20pm

So, Simpson emailed me about the right knob push changing between heading/track/north up.  

I sent my logs in.  I got an email from sergio about it.   I will reply to him, as well.   I see no difference at ALL between setting track up or heading up.  Nothing changes when I select either one.  There is no option for North up that I can find.  This may be operator error, but I can't figure it out.  

Back when my box was faulting on the ground, I would occasionally see a short in-air loss too. I would notice it because I would get an IFD540 CAS alert for the stormscope (or was it traffic), because it uses heading.

Edited by oskrypuch - 06 May 2015 at 12:28pm

I had a similar issue for a few seconds in air

ksdoc wrote: Until just recently, all of my failures have been while airborne. Some within 30 minutes, others after several hours of flight.

Edited by MysticCobra - 06 May 2015 at 7:12am

ddgates wrote: I cancelled this weekend when both 540s didn't acquire GPS lock (my cell phone had lock). I too hope that 10.1 fixes this.

David,

We were waiting on your logs to confirm.  Did you have a chance to grab and send them yet?

comancheguy wrote: When i departed, I had the same old issue where the heading was correct, but the plane was pointing the wrong way.  This is NOT a track up vs Heading up vs north up issue.   Very disorienting to look over at the box at 200' and see RED all over from the FLTA stuff, and the airplane pointing back at the runway vs at my heading.

I've been away from this for too long.  Are the Avidyne tech support guys on this one?

comancheguy wrote: Well, My karma just bit me.  Taxiing out for a business trip, my 540 lost GPS signal and didn't reacquire when I was ready to launch.  Power cycle and it came back.

Not karma, just a software issue that we induced.

Next in line:  My IFD540 recently started exhibiting this behavior as well.  On a recent flight of less than an hour, my unit lost and re-acquired GPS signal about a dozen times.  Very irritating to say the least!

I cancelled this weekend when both 540s didn't acquire GPS lock (my cell phone had lock).

I too hope that 10.1 fixes this. 

Until just recently, all of my failures have been while airborne. Some within 30 minutes, others after several hours of flight.

Software fix to address a hardware change.

Well, that is very good news.

AviJake wrote: We believe we had a major breakthrough on this issue this week.   Another day or three of testing to be completely sure but we think we finally found the root cause of the I/O card initialization issue.    A little ferrite bead was added to the board a while ago to suppress some excessive noise in the electric circuit.  This little devil changed the timing of the circuit just enough and just subtle enough to screw up the I/O board initialization which absolutely manifests itself in the behavior some folks are seeing. We will verify the fix is a solid fix and then determine how we roll it in.

Any updates on this AviJake?

Yes it was an Avidyne tray and yes they know.  The tray was sent back to Avidyne for replacement.