It appears to be getting worse. I also tried writing a new bin from scratch onto the nvram with no effect.
Connected up a noid to injector plug and no blinking at crank just solid power on. Wondering if the injector driver could be sticking on. It did return to blinking state after a minute but would stick on once the engine started and gave it a small rev.
Peeled back the tape and took a closer look at the wiring for the injector earth's from ecu and there has been some repairs with a smaller gauge wire used.
Now wondering if this could be loading on the injector driver causing it to break down. I did swap out the ecu and it improved but perhaps only until it became damaged as well?
As anyone struck any issues where injector wiring has caused an issue like this?
Turbo 304 massive over fuel event
Re: Turbo 304 massive over fuel event
Shorted coolant temp sensor?
According to chemistry, alcohol is a solution...
Re: Turbo 304 massive over fuel event
I'll check it out when I get back in the shed. From memory coolant temp looked as expected in tunerpro. Would this cause a full open injector condition or just very rich?
Re: Turbo 304 massive over fuel event
Used to see a few of these when VN's where much newer. Would randomly short and cause a flood situation.
According to chemistry, alcohol is a solution...
- vlad01
- Posts: 8123
- Joined: Mon Oct 08, 2012 6:41 pm
- cars: VP I S
VP I executive
VP II executive
VP II executive #2
VR II executive - Location: Kyneton, Vic
Re: Turbo 304 massive over fuel event
Yeah they read like -40c in TP when that happens. But like you said, if it looks fine in TP, unlikely that, and certainly not something that would give 100% DC on the injectors. I am pretty sure the tune won't have something that gives 100% DC anyway.
With drivers, they rarely would fault as intermittent, normally permanent short to ground or permanent open circuit. But upstream passive components that are degradated can exhibit a temp or run time type of intermittent faulting, such as caps and resistors for examples, semiconductors like mentioned are dead or not, rarely do they behave like this.
Very odd if it where the ECUs all failing like this too. So I think it could be some other electrical fault or cause elsewhere.
Have you checked the battery voltage? Perhaps the alternator when it warms up does some weird thing like mega overvolting which could in principle make the ECU lose it's marbles.
With drivers, they rarely would fault as intermittent, normally permanent short to ground or permanent open circuit. But upstream passive components that are degradated can exhibit a temp or run time type of intermittent faulting, such as caps and resistors for examples, semiconductors like mentioned are dead or not, rarely do they behave like this.
Very odd if it where the ECUs all failing like this too. So I think it could be some other electrical fault or cause elsewhere.
Have you checked the battery voltage? Perhaps the alternator when it warms up does some weird thing like mega overvolting which could in principle make the ECU lose it's marbles.
I'm the director of VSH (Vlad's Spec Holden), because HSV were doing it ass about.
Re: Turbo 304 massive over fuel event
It's very hard to "see" the pulses/flashing of the noid light when a shorted coolant temp sensor occurs because the light gets so bright.
According to chemistry, alcohol is a solution...
Re: Turbo 304 massive over fuel event
I would also look at the MAP sensor and wiring.
According to chemistry, alcohol is a solution...
Re: Turbo 304 massive over fuel event
Thanks guys for all the good info. I ended up finding a small section of loom melted at the rear of the RH bank. Must have been sitting too close to the back of the head and caused a ground to one of the negative injector wires. Funny as I checked for continuity to ground on the circuit initially and then moved on. But I guess that's why they call it intermittent. Looks like i should have heatsheilded that one after all. Thanks again for all the input from members it is greatly appreciated.
Re: Turbo 304 massive over fuel event
Thank you for advising back the problem found. It'll be good info stored in the memory bank (myself and others too)