Garmin 430W/530W 5.10 Update.

[BigTex]

If anyone is thinking of taking the latest update (5.10) for their GTN430W/530W and use the FOB feature I'd hold off taking it. It appears that you are no longer able to set FOB. As soon as you enter it, it clears it out.

Unfortunately I had mine updated before finding this out! Over on Beechtalk there's a long thread where Garmin came on the forum and acknowledged the bug and said it would be fixed with the next release scheduled for late this year... Ugh.

[BobAustin]

What is the "FOB" feature ?

[BigTex]

Fuel On Board setting.

[flyboy0681]

Interesting. Two releases ago on the GTN series a bug in the software prevented the fuel flow from registering, rendering all of the fuel utilities useless. It has since been fixed.

[Piloto]

If anyone is thinking of taking the latest update (5.10) for their GTN430W/530W and use the FOB feature I'd hold off taking it. It appears that you are no longer able to set FOB. As soon as you enter it, it clears it out.

Unfortunately I had mine updated before finding this out! Over on Beechtalk there's a long thread where Garmin came on the forum and acknowledged the bug and said it would be fixed with the next release scheduled for late this year... Ugh.

Thanks for the tip. Mine still 3.1 and never seen a problem with it. 

 

José

[yvesg]

My work is software testing. I always wait a few weeks (or months) before getting the latest and greatest software for my personal stuff. Few software teams go into the trouble of re-testing everything after they add new stuff in order to find any regressions. Most use a risk based approach.

Yves

[KSMooniac]

It is done by an avionics shop.

Sent from my ADR6425LVW using Tapatalk

[flyboy0681]

It is done by an avionics shop.

Sadly, even the GTN series has to be upgraded by a shop.

[kortopates]

I have the 5.1 firmware update and do NOT have the FOB problem. I suspect it's because there are a few different protocol options that can be used to configure your fuel monitoring device to communicate with the GPS and probably the bug is limited to a specific protocol.

Sent from my iPhone using Tapatalk

[BigTex]

I have the 5.1 firmware update and do NOT have the FOB problem. I suspect it's because there are a few different protocol options that can be used to configure your fuel monitoring device to communicate with the GPS and probably the bug is limited to a specific protocol.

Sent from my iPhone using Tapatalk

Do you have fuel flow tied into your 430W?

[kortopates]

Do you have fuel flow tied into your 430W?

Yes, both 430Ws

Sent from my iPhone using Tapatalk

[BigTex]

Interesting... So you can set your FOB and it sticks?

[Oscar Avalle]

Well, I have an PFD Aspen, 430W and a GTN 750, tied to a 795 and a JPI 830 with fuel flow, TCAS and WX500 stormscope. After quite a while I have been able to make everything work and talk to each other!

 

Although I always believe that it is great to have the latest software running, I think that for a while I will leave everything untouched and not upgrade anything unless there is a very compelling reason to do so in terms of functionallity or safety.

 

I try to learn from my mistakes. (not always...)

 

Oscar

[BigTex]

Right there with you Oscar.  Mine was really old and I wanted to update the terrain DB requiring a firmware upgrade. I also wanted some of the latest fixes to their ADS-B integration.  I should of known better being in the software business but before the upgrade, things worked great... now, not so much.  

[kortopates]

Interesting... So you can set your FOB and it sticks?

Not quite, my JPI 830 provides current FOB to the 430Ws and constantly keeps it up to date while the 430Ws provide ETA of my final destination to the JPI so that tell me how much of a fuel reserve I have at my destination. Or I could go to a 430 fuel planning page for that info and more.

The bug that Oscar reported broke the interface between the JPI and the 430w. I suspect Oscar's JPI may have been using the default protocol which provides fuel remaining at next waypoint since a different protocol is used to provide fuel remaining at the final destination and that protocol does not have the issue Oscar reported.

Sent from my iPhone using Tapatalk

[kortopates]

BigTex, my apologies for apparently confusing whom reported the bug. I had thought it was Oscar earlier, but probably not and I had forgotten you were the OP having the issue. Also I think I misunderstood your original issue or perhaps heard elsewhere that the JPI interface to Garmin for FOB info had been broken by the update. From re-reading your post, I understand you don't have anything connected to your 430W to provide FOB and manually set it? If so, what I did will be of no help to you.

Regardless though, IMHO, if your using your Garmin for approaches the 5.1 update is well worth the sacrifice of loosing FOB till the next release - I wouldn't hesitate for a second.

 

Incidentally, Oscar had me worried about the EDM firmware upgrade (in another thread), but I had no issue there either - thankfully.

[Oscar Avalle]

BigTex, my apologies for apparently confusing whom reported the bug. I had thought it was Oscar earlier, but probably not and I had forgotten you were the OP having the issue. Also I think I misunderstood your original issue or perhaps heard elsewhere that the JPI interface to Garmin for FOB info had been broken by the update. From re-reading your post, I understand you don't have anything connected to your 430W to provide FOB and manually set it? If so, what I did will be of no help to you.

Regardless though, IMHO, if your using your Garmin for approaches the 5.1 update is well worth the sacrifice of loosing FOB till the next release - I wouldn't hesitate for a second.

 

Incidentally, Oscar had me worried about the EDM firmware upgrade (in another thread), but I had no issue there either - thankfully.

 

Well you were not to far off. I had a problem upgrading my JPI to 3.43 and posted about it. I was able to fix the problem by downgrading to 3.35. Go figure...