Has there been an update for this or do I have a problem? This IFD-440 is connected to two Dynon HDX screens via the arinc429

With two IFD‘s interconnected, you‘ll get this msg if there is a time discrepancy between the two. My IFD440 loses time between flights and remains wrong on startup until GPS satellite reception has been established for a certain time period (time to retrieve the almanac?). I suspect a battery problem and you might check that on your IFD440.

Have you tried power cycling the affected IFD when you get this advisory to correct the IFD's internal clock? The following is from the IFD PG:

Up until a couple weeks ago, I never had the issue with my 540. Whenever the plane sat for over 2 weeks or so, the 440 would power on with a significantly old date/timestamp (i.e. days or weeks out of date). I always attributed it to a battery issue, because after some running time the 440 date/timestamp would correct itself without any power cycle.

The last time it happened, I tried the (new to me) power cycle resolution suggested in the PG and it worked except that the 440 time was now a couple minutes newer than the 540 so I still got the UTC Mismatch message. I power cycled the 540 as well and it came back with the same time as the 440 ... issue solved.

Just as a thought, it might be that more people are reporting the issue now because the aircraft are flying less and there is a longer gap between power cycles for more aircraft.

I received the UTC mismatch error yesterday for my first flight of the day, the last flight was prior to this was on February 13th and I had powered up the GPS on March 5th to update the database. 

Interesting note on the March 5th database update, My friend did the update for me and sent me a picture to confirm it was completed, the date of the text message on my phone was 12:12pm (UTC -5) but the GPS splash screen said 17:14z, 2 minutes ahead of the cell phone.  I'm going to guess the unit was turned off before it had acquired a GPS signal, but that 2+ minutes might be what triggered the UTC mismatch on the next power up.

just food for thought.....

Jeff

AviSteve wrote: You should rarely, if ever, see that message, so the fact that there is a recent increase in sightings has our attention.  We're actively trying to determine the root cause.

So any thoughts on the time difference displayed vs actual causing the issue?

Any update on this issue?

Best regards,

Chuck

Yes we did find the issue and will take a hardware mod to fix it.  Coordinate an RMA with your dealer to get the unit updated with "Mod 25".

Ugh, ship the unit out... ok, at least the problem was found.

There are two planes that I fly both with IFD440s, my plane has had the error only a handful of times, my friend's plane that I also fly seems to encounter the problem a lot more often.

So I understand how soon (if at all) I ship the units back, my questions are, besides getting the error message is there any degradation/functionality loss or can I simply consider it a nuisance  message?  Looking at the serial number label for my unit (took a picture before it was installed) it was manufactured the 21st week of 2019 and is a Rev:09 unit, there are no mods checked off.  If I send the unit back for Mod 25, what else is done? Are there other MODs that will get performed?  Are there any others that should be done?  I'm assuming the software is also brought up to the current version as well, eg wait for the elusive 10.3.x.x .

-PA

It's a little more than a nuisance message because the time actually is off.  But, if you get a GPS position and then cycle power, the condition should be cleared.  So, it comes down to your tolerance level for dealing with that.

Steve, I just want to make sure I understand the consequences of receiving the UTC mismatch error as you now have me second guessing what I've been doing, the first few times I did cycle the power of the unit but after that when I got the error I would simply acknowledge it and move on, the unit always got a GPS lock and appeared to work correctly.

Are you saying that for the system to work properly I must cycle the power before continuing?

If it is just a time and date issue for processing ADS-B in data then I'm not as concerned since In my case I am feeding traffic and WX to the IFD from an NGT-9000 and I really don't view the traffic or wx on the IFD as I find it a lot more convenient to view the data on the NGT

-PA

We probably could have masked it in software, but the hardware fix was really the right answer.

Steve, so this issue requires an RMA to fix, are we on the hook for some $ to do that or is it going to be done, at our "shipping" expense only?

Thanks, Chris

Best to email warranty@avidyne.com to determine your specific situation.

Well, I guess I have had mine too long. I guess that I will have to just do the restart.

Thanks, Chris

Thanks Steve,

I can't comment as  to why a hardware fix was the better solution than fixing the error in software but I'm guessing the fix had something to do with the timing or powering the RTC (Real Time Clock) as it is more prevalent when the plane sits for a while.

Since my unit is still under warranty for almost 2 more years I will go ahead and plan to have the mod installed.  However since the error doesn't appear to  directly effecting how I use the unit I will probably wait until the plane goes in for annual so I'm not down unnecessarily, and bonus maybe I can take advantage and upgrade to 10.3.x.x at the same time....(Anticipation...)

-PA23

Possibly.  Give tech support a call.  They will be able to check whether your IFD has the mod applied.