Firmware Update?

[Mcstiff]

Whats this about an update which may help with trigger errors? I'm running 1.1.95 and once and a while get an error under load only.

[Marc]

1.2.11, set auditrigger divide by N, N = 9 on the primary trigger page.
number of teeth: 30
first trigger tooth: 0
next trigger tooth: 6
angular width of tooth: 24

double check your zero-timing with a timing light.

also, your trigger reference tooth table becomes:
0
6
12
18
24

[Mcstiff]

I'll check it out!

[amd is the best]

1.2.11, set auditrigger divide by N, N = 9 on the primary trigger page.
number of teeth: 30
first trigger tooth: 0
next trigger tooth: 6
angular width of tooth: 24

double check your zero-timing with a timing light.

also, your trigger reference tooth table becomes:
0
6
12
18
24

What would the settings be for the 3B (unless this is for 3B or they are the same)?

Thanks!

[Mcstiff]

I'm thinking they should be the same.

[amd is the best]

I'm thinking they should be the same.

Is your car AAN or 7A/3B?

I could be VERY wrong, but I assumed the two used different trigger settings because the 7A/3B use a 135 tooth main trigger and the AAN uses a 60-2.

[Marc]

I'm thinking they should be the same.

Is your car AAN or 7A/3B?

I could be VERY wrong, but I assumed the two used different trigger settings because the 7A/3B use a 135 tooth main trigger and the AAN uses a 60-2.

aan and 3b trigger exactly the same. they both use 135 tooth main trigger.

yes, same settings as posted above.

[Mcstiff]

I'm thinking they should be the same.

Is your car AAN or 7A/3B?

7a, + LS coils, using the dizzy as a cam trigger like an earily AAN

[amd is the best]

I'm thinking they should be the same.

Is your car AAN or 7A/3B?

I could be VERY wrong, but I assumed the two used different trigger settings because the 7A/3B use a 135 tooth main trigger and the AAN uses a 60-2.

aan and 3b trigger exactly the same. they both use 135 tooth main trigger.

yes, same settings as posted above.

Thanks for clearing that up Marc.

I'm thinking they should be the same.

Is your car AAN or 7A/3B?

7a, + LS coils, using the dizzy as a cam trigger like an earily AAN

Thanks man. Identical to mine, just 3B of course.

[Mcstiff]

1.2.11, set auditrigger divide by N, N = 9 on the primary trigger page.
number of teeth: 30
first trigger tooth: 0
next trigger tooth: 6
angular width of tooth: 24

double check your zero-timing with a timing light.

also, your trigger reference tooth table becomes:
0
6
12
18
24

Mark, I'm getting a validation error for "next trigger" thoughts?

v3.3_u003657-A-2013.03.26-22.09.47_EVENING_New_FW.vemscfg

(12.55 KiB) Downloaded 1351 times

[Marc]

1.2.11, set auditrigger divide by N, N = 9 on the primary trigger page.
number of teeth: 30
first trigger tooth: 0
next trigger tooth: 6
angular width of tooth: 24

double check your zero-timing with a timing light.

also, your trigger reference tooth table becomes:
0
6
12
18
24

Mark, I'm getting a validation error for "next trigger" thoughts?

v3.3_u003657-A-2013.03.26-22.09.47_EVENING_New_FW.vemscfg

you need to update to a 1.2.x firmware for these settings to work (use 1.2.11).

the config you attached is still 1.1.95, which is why validation is failing.

[DuBistS4]

Marc what is the best firmware to use currently? I am still on 1.1.95 becuase at the time it was the most stable.

[Mcstiff]

you need to update to a 1.2.x firmware for these settings to work (use 1.2.11).

the config you attached is still 1.1.95, which is why validation is failing.

Thanks, I forgot I have to translate it during the update.

[Marc]

Marc what is the best firmware to use currently? I am still on 1.1.95 becuase at the time it was the most stable.

it still is the most stable and recommended firmware. However, if you have any troubles with trigger errors (usually they will come up around 5k rpm or so if you have them), 1.2.11 resolves them when moving to divide by 9 with the above settings.

[DuBistS4]

My firmware update tool doesnt show 1.2.11 for some reason

[Marc]

My firmware update tool doesnt show 1.2.11 for some reason

you can either update your vemstune to the latest stable, or you can download 1.2.11 by using the "firmware web tool", from the tools menu.

[Mcstiff]

Finally updated. Looks like basically everything came across, had to take a few degrees out of my zero timing / TDC after sensor. We'll see how tomorrow goes.

[Mcstiff]

Well, I spoke too soon. For some reason my WBO2 is not working. I thought it just needed recalibration but it is not heating...

Otherwise, my false trigger errors are gone and idle is much better!

[Marc]

Well, I spoke too soon. For some reason my WBO2 is not working. I thought it just needed recalibration but it is not heating...

Otherwise, my false trigger errors are gone and idle is much better!

go to your wideband page and select the dropdown to fill with defaults for the heater.

[pilihp2]

I used to have a weird 2% throttle bounce and its gone now. I'm sold.

[Mcstiff]

I used to have a weird 2% throttle bounce and its gone now. I'm sold.

Yeah, I had some of that solved as well.

Well, I spoke too soon. For some reason my WBO2 is not working. I thought it just needed recalibration but it is not heating...

Otherwise, my false trigger errors are gone and idle is much better!

go to your wideband page and select the dropdown to fill with defaults for the heater.

Marc, I was using "default" which matches my old settings. If I choose "WBO2-Heater-PID" it changes integral limit from 128 to 129 and nothing else.

[pilihp2]

Scratch that. Weird rev thing is better but still not gone.

[carl]

Have you tried moving up the overrun fuel cut a few rpms? Lets say 2200 rpm ish and move (in idle settings) the tps value threshold to a lower value? I had this issue too, bouncing revs when feathering the throttle. Tps sensor wouldn't read any changes yet throttle was slightly open, so it would cut the fuel when the rpms would exceed the threshold. Turns out the tps sensor resolution isn't all that great. Anyways, that was my issue.

In same boat for wideband, readings not working atm, not sure why, still haven't tried recal tho. I do have a narrowband connected also in aan harness maybe that doesn't help.

[DuBistS4]

Just uploaded 1.2.11 and my idle vacuum is much weaker. The engine runs smoothe and their are no validation errors. idle vac. is at 48kpa before it was at 42kpa. Timing is the same, what else a i missing?

[Marc]

Just uploaded 1.2.11 and my idle vacuum is much weaker. The engine runs smoothe and their are no validation errors. idle vac. is at 48kpa before it was at 42kpa. Timing is the same, what else a i missing?

if you changed to the divby9 setup, you need to recheck your ignition timing. your vac might be different because now your base timing is off.