diamondaviators.net

I am currently running ver .22. However, when the G1000 was previously updated to ver .19, the engine time was reset to zero (inadvertantly or not, I do not know as I did not own the airplane at that time). There is a logbook entry that states that the software was updated to ver .19 at xxx hrs. So now, I have to add xxx hrs to the current time shown on the G1000.

I called Garmin and they said the G1000 "tach time" time cannot be changed. My Garmin dealer called (when I upgraded to ver .22) and was told the same thing.

If what Garmin is telling me is correct, it seems to me that every G1000 DA40 that was upgraded to ver .19 would have this issue?

Has anyone else had this problem and/or does anyone know how to fix it?

Thanks,

Tim

I know our '04' DA40 was upgraded from .08 to .12 to .19 to .22 without any changes to the G1000 "Total Time in Service" (tach time) value. I'm guessing somebody screwed up the s/w upgrade... Seems like Garmin could write a tool to "fix" the value if they wanted to, but I've never seen any such tool.

Rick wrote:I know our '04' DA40 was upgraded from .08 to .12 to .19 to .22 without any changes to the G1000 "Total Time in Service" (tach time) value. I'm guessing somebody screwed up the s/w upgrade... Seems like Garmin could write a tool to "fix" the value if they wanted to, but I've never seen any such tool.

Ditto.

Tim H wrote: If what Garmin is telling me is correct, it seems to me that every G1000 DA40 that was upgraded to ver .19 would have this issue?

Has anyone else had this problem and/or does anyone know how to fix it? Thanks, Tim

Tim, the exact same thing happened to me. But in my case it involved a swap of the MFD/PFD. Diamond and Garmin can fix it although it is an arduous process. Your fuel sender will have to be re-calibrated too. Send me a PM and I will send you the entire e-mail thread including the contact names at Diamond. Jeff Owen was very helpful in getting me the correct info to start the ball rolling.

Nigel.

Has anyone else who experienced this been able to get it fixed? We ran into this after replacing the MFD in 2019. I reached out to Nigel but it seems he's no longer active on the forum. I'm going to SouthTec next week but Glenn isn't too sure whether or not he can do anything about it. I'd love to provide him with pointers if possible.

The tach shouldn’t have reset, there was apparently a glitch during the update. More annoyingly, I once replaced a display because the old one burned up and when the new display went it suddenly the tach jumped by thousands of hours, so we had to estimate the total time and subtract an arbitrary number from then on.

There is a software card that tries to recover a lost tach time from the display/config module. IIRC it’s a five minute process. I don’t think it’s guaranteed to work though, I guess it depends on exactly how it was “lost”

Wow, that does sound frustrating. Tach time resets on the VM-1000 are a piece of cake, taking 2 minutes max.