Enginebit 17 och 33

gripner · Post by **gripner** » Thu May 04, 2006 11:30 am

Hi all, a quick question

Should i be seeing enginebit 17 and 33 at all a engine useing a narrowband lambda, and ofc megasquirt is set up to use lamda n map

I see it sporadicly and i "think" its connected to when the engine for some reason dies all the sudden.

thanks

Bernard Fife · Post by **Bernard Fife** » Thu May 04, 2006 12:35 pm

gripner,

17 means TPS accel (16) + running (1). 33 means TPS decel (32) + running (1).

So it seems you have your accel enrichment thresholds (either TPSdot or MAPdot) too low, try doubling them.

Lance.

gripner · Post by **gripner** » Thu May 04, 2006 1:53 pm

cool, ill try that, Altho, i was under the impression u dont use TPS stuff like this when useing map and lamvda.

I most likely misundersttod it tho

BottleFed70 · Post by **BottleFed70** » Thu May 04, 2006 1:59 pm

This is where the logging gets confusing.

They label it as "TPS accell" but it should really just be called "Accel".

MAP based accell will also show up as engine code 16.

gripner · Post by **gripner** » Fri May 05, 2006 10:42 am

Thanks for the help so far, unfortunatly it did not make stuff work better.

The engin dies at certain RPMs and when i say die i rly mean dies like the ignition stops working rather then the VE map is messed up.

Atm we running the car on a ve map that it quit "fat" not tho fat tho and the ve-map portrais the engines torq quite good. But still it dies like clockwork if u do a hard accelration at 1800rpm and 4000rpm.

Could it be stuff like we needto improve the shielding on cables from the ignitionsystem that feeds the CPU ?

Just brainstorming here since it kinda make no sence >_<

Thanks