Nistune Forums

my ka will run great, but randomly goes int limp in mode and throws code 0. when this happens. consult wont connect.

This is a concern. How often is this occuring? What is the ECUID shown in NIStune and what is the ID on the case of your ECU?

Where are you reading 'code 0' from?

response from PL
[quote]They don’t go into limp mode without a good reason. When they do it’s normal for Consult to die – I think that’s pretty standard across all ECU’s that have a limp mode.

Usually they will only go into limp if something drastic has happened – ie: code has crashed due to daughterboard hardware/firmware fault. Nearly always a “mechanicalâ€

I can't help but think Nissan must have had an intelligence failure when they decided to stop consult working if in limp mode. I cant follow the logic!

Nissan: "Right people, we have added consult to help you diagnose ECU problems"
People "Yay sounds great"
Nissan "But it wont work if there's a serious error"
People "What?!"

haha

ECU Limp mode runs from another chip on the ECU using logic circuits only.

It only uses it when the main processor (which does consult commands also via its SCI) is dead

It basically for each CAS input injects a set pulsewidth amount of fuel without even looking at the MAF input. Which makes it run upto about 2000rpm before leaning out

Learn something new every day. I didn't know it was such a low level type of auto protection recovery. I am impressed now

sorry for the long replie fixed the problem.

sorry for the long replie fixed the problem.

What did the problem end up being?

Bad ECM. I Fried ECM circuit while wiring Z32 maf. I found the burnt circurt and soldered it back together.
It worked, but Im pretty sure thats what caused the problem.