[yellowfin]

Terry, could you give more details on the alternative anti-rattle? I was looking in the forum, but did not find much. Before I got new turbos, I used it on the stockers, it dramatically improved rattle, but maybe a tad more lag.
Does it override DWP? Under which circumstances recommended, any pros and cons?
Thanks

[Terry @ BMS]

It's documented somewhere, feature is a few years old. Holds WG open at low throttle then returns to normal at 20% input or something along those lines. Works for some, not all.

[yellowfin]

Originally Posted by Terry @ BMS

It's documented somewhere, feature is a few years old. Holds WG open at low throttle then returns to normal at 20% input or something along those lines. Works for some, not all.

Ok, thanks. Quite surprising that it did not create more lag than it did.
Then again, my WG's might have been so worn out that they did not really open at 0 wgdc. Glad those times are over

[mistawall]

G5_ISO_32_5

1) Setup JB4 to automatically change itself to map0 if a flashing device is connected to the OBDII port. Upon switching to map0 it will flash the turn signal indicators to alert the user.
2) Added battery reset and register (when installing a new battery) under the menu 1/7 adaption resets.

So by setting it to 1/7 after installing a new battery will take care of the coding it needs?

[Terry @ BMS]

Correct, 1/7 is battery reset. On the latest firmware we moved the rest of them to 1/4.

[Hidden_man]

Hi ,

I'm from Australia and i updated to the ISO_32_8 firmware and now i keep getting codes for having ******* *********?

I read that this update got rid of autoclear for US cars? But mine shows as Australian in the JB4 setting and doesnt clear the codes?

Can you help me out?

Thanks

[vwetish]

Either upload older firmware or do BEF.

[Hidden_man]

Originally Posted by vwetish

Either upload older firmware or do BEF.

I am running with the newest BEF already and still get the codes for ******* **'s.

Is there anywhere i can download the older firmware? Cant seem to find it anywhere?

[Terry @ BMS]

Originally Posted by Hidden_man

Hi ,

I'm from Australia and i updated to the ISO_32_8 firmware and now i keep getting codes for having ******* *********?

I read that this update got rid of autoclear for US cars? But mine shows as Australian in the JB4 setting and doesnt clear the codes?

Can you help me out?

Thanks

Outside the USA you can select passive delete from the WMI settings page.

[greyshadow]

whats the diffrence between the

G5_ISO_32_9.hex

vs.

G5_ISO_32_9_T1.hex

Which one would we use for newest update? also do we have to redownload interface off the main post?

[milfriez]

Originally Posted by greyshadow

whats the diffrence between the

G5_ISO_32_9.hex

vs.

G5_ISO_32_9_T1.hex

Which one would we use for newest update? also do we have to redownload interface off the main post?

I came here to ask the same exact question. When i tried to flash, mine failed. I had everything set to defaults and only on battery power as suggested. and on Map 0.


On another note -- Terry the new FUD for WG's is a GODSEND!!! Dude, I cannot thank you enough. I'm not sure what all changed in that algorithm but my car idles better, better low-throttle drive-ability, no surging, barely any rattle at all, and boost feels like it even comes on a tiny bit faster.

I assume with all these changes, its probably pointing to my turbos being the culprit all along to my issues. (Which I sort of assumed). But this at least has given me new hope that I can at least get along until it's Pure Stg2 time.

THANK YOU TERRY!

[ratapeludismo]

With firmware G5_ISO_32_9.hex I had misfire cylinder 5 and 6.
I thought they were my coils and was willing to buy new..
After updating to G5_ISO_32_9_T1.hex these faults have not gone out again.
Thanks Terry for the update !!

[Terry @ BMS]

Highest number is the newest update. We document changes in the post with the firmware if we want to document them. Firmware can't "fail" and any firmware we posted we've reasonably tested. Generally when problems come up you're doing something wrong or setting something wrong, so if you need help with it, take advantage of the support forum.

[ratapeludismo]

Originally Posted by Terry @ BMS

Highest number is the newest update. We document changes in the post with the firmware if we want to document them.

Terry you should remove the firmware from the list; G5_ISO_32_9.hex Does not work well and fails.
The T1 works perfectly.

[Terry @ BMS]

The difference between the firmware has nothing to do with whatever problem your specific car is having with misfire codes.

[milfriez]

Originally Posted by Terry @ BMS

Highest number is the newest update. We document changes in the post with the firmware if we want to document them.

Kinda confused about this. Unless I'm missing something, all i'm seeing is updates on 32_5. Then there are 3 different firmware versions. I know I tried 32_9 and it failed on my car. Should I just move to one of the next ones and try again?

The last thing I want to do is to brick the JB4, unless there is a fail-safe built in that if the upgrade doesn't complete to revert to old?

[Terry @ BMS]

Not sure where your confusion is. Firmware is posted at the bottom of this post: http://www.n54tech.com/forums/showpo...68&postcount=2

There are 3 versions posted currently. The latest and we leave a couple previous up "just in case". 32_9_T1 is the latest. If you have a problem with the latest firmware and need help you're welcome to create a thread in the support forum with details for assistance, or email in.

[erwan35]

Just to be clear. Theres no more auto delete codes? Been 9months havent catch up.

[erwan35]

I am currently on 32.5 firmware. Its been 9months since i last followed this forum. Do i still have to set duty bias to 0 in order to upload the new firmware?

[THE BEAST]

Updating firmware. I have never zero'd anything out while updating. Are we supposed to 0 out duty bias BEFORE updating firmware and AFTER its updated, reset settings to the values I had ?

[mike082802]

updated from 32.8 to G5_ISO_32_9_T1.hex and trims for bank 2 under avg ignition no longer working. tried a few times and nothing. disconnected the app and restarted the phone a few times and nothing.

[Terry @ BMS]

It moved to its own spot, update interface.

[Terry @ BMS]

Originally Posted by THE BEAST

Updating firmware. I have never zero'd anything out while updating. Are we supposed to 0 out duty bias BEFORE updating firmware and AFTER its updated, reset settings to the values I had ?

No you don't need to change them at all. The note is for people updating from years old firmware for the first time.

[mike082802]

Originally Posted by Terry @ BMS

It moved to its own spot, update interface.

Guess Donny has to update the mobile app, or i just have to Lug my laptop outside. Thanks

[Terry @ BMS]

Ah, yes email him for the BETA app if its not posted yet. Also grab the T2 JB4 firmware I found a little bug in the dedicated bank2 logging on T1 I fixed this morning.