DTC's & EEHACK

Printable View

02-22-2019
Terminal_Crazy

DTC's & EEHACK

I've frequently had odd DTC's appear/disappear in the past & generally turn off any I don't need.

I've swapped PCM's recently and this one can run the fans at high speed, the previous only ran them at slow speed.

Now I'm getting these dtc's obviously the fans are kicking in full, noisey & cooling the car.

I've flashed with EEHack 4.7 & Kur4o's recent 4.92 and fans are coming on at 70C (car was still warm)

I've been getting
43d knock sensor which checks out OK with volt meter.
LT4 filter swapped back in, still has fault.

99 Tach output
Both are switched off. NO DTC's show up in EEHack.

I ran Gary Dougs Scan94-95 and that still shows the DTC 99 as active and won't clear.
------
I dicked about with the tune zeroing the timer delay for fan tach output and got different DTC's... fan 1 dtc 77 & CCP/electrical fault (missed the no, EEHACK crashed)
---
I don't suspect a mechanical or wiring issue as such.
PCM Knock sensor voltages checked out OK.

Alternator is 14.01
Body terminals on inner wing 13.8
PCM shows ecm input voltage as 13.1

I'll reflash with an earlier tune that doesn't show the fault.

I've also had 97 vss fault occasionally pop up.

Any thoughts?

TIA
Mitch
02-22-2019
Stroked 388

I've not gotten any DTC with kur4o eehack patch all has been good with multiple uploads so far.
02-24-2019
Terminal_Crazy

I've been reading up on the DTC's to see what's common about them

DTC Codes
43 Knock sensor Output D22 : PCM puts out 5V, sensor pulls it 2.5V DTC SET = >4.1V Open <0.78V sensor Grouned
72 VSS Input A32 : ****** CHECK CALIBRATION ID

97 VSS Output B 8 :DTC SET wrong voltage for 26seconds on CKT 817
99 Tach Output A13 :DTC SET wrong voltage for 26seconds on CKT 121

I've no common socket, 97 & 99 both mention wrong Voltage although this is the 2nd PCM that I've had codes on.

DTC 72 VSS mentions to check Calibration ID

*** CALIBRATION ID T-Side E-SideModule2
Stock M6 Z28 = 16209461 16209314 16209313
Burkhardt PCM (auto = 16209491 16209320 16209319

If I change from a Manual PCM to an auto & reflash with the same .bin, that should be correct?

TIA
Mitch
02-27-2019
Terminal_Crazy

Update: It seems to be the tune.

OK guys,
It does appear to be the tune that was out rather than any version of EEHack

Reflashed the last tune with EEHack and both fans kicked on below 30C without any DTC's showing up.
Reflashed with a much earlier one that didn't show any DTC's that i'd noted and that seemed to run OK.

Compared & altered a few things, nothing of much note, However, I found

167ba : Max RPM for 0 bpw must be same with 167b4
167b4 : Max rpm for 0 bpw
set slightly different
Although these WERE NOT the same on the working .bin either

So it looks like this is the MAX RPM I can wind this motor unles Kur4o can do his magic here.

15d20 : Max RPM for spark adv calc can be set much higher.

I'll give it a run when I get a mo.

Mitch
03-21-2019
Terminal_Crazy

Update:

Nope I have/had a wiring Issue.
Knock sensor DTC 43D flashing on & off
Knock counts clocking over & over.

I've spent 2 days chasing this down.
Removed the PCM & checked Voltages & Ohmage on everything, checked out fine.
Replace PCM , EEHack count goes mental, Fans on FULL etc
Removed & tested. OK
Replaced goes mental.

Ran fine with PCM hanging out.

I removed the PCM over a dozen times today.
Every time I replaced it the knock counts re appeared.

I know there IS a problem in the Knock Sensor cable now, just need to replace it.

Oh the joys.
Mitch
03-21-2019
steveo

sounds odd, a DTC 43 shouldn't clear itself until next reset. in such a failure condition the ECM should pull (by default) 9 degrees of timing advance across the board and ignore any further knock counts. the code shouldn't flash on and off.

if you suspect a fault why not just pull the whole harness and load test every wire back to the ECM while you flex it a bit. it'll only take a few hours including re&re of the harness. a paper clip is a perfectly good probe for the ECM pins. you might have a bad ground splice or something, but also if one wire is damaged it's possible there are others next door.
03-21-2019
Terminal_Crazy

Quote:

Originally Posted by steveo

sounds odd, a DTC 43 shouldn't clear itself until next reset. in such a failure condition the ECM should pull (by default) 9 degrees of timing advance across the board and ignore any further knock counts. the code shouldn't flash on and off.

There is a timer at 2807 to clear error 43 set at 50.00 (presume seconds)
Fault code would go off pretty much as soon as I pulled the PCM out the bracket.
Of course as soon as I pulled it, the fault disappeared.
Knock counts could ramp up about 1-2000 counts each second
43 &/or 43D would flash up. Timing would pull ( 5 in my tune) then decay.
then it'd all go away for minutes.

When I connected to the PCM this morning the DTC's appeared before starting the car

Quote:

if you suspect a fault why not just pull the whole harness and load test every wire back to the ECM while you flex it a bit. it'll only take a few hours including re&re of the harness. a paper clip is a perfectly good probe for the ECM pins. you might have a bad ground splice or something, but also if one wire is damaged it's possible there are others next door.

That's a job for next week :-)

Big thanks Steveo for EEHack, I probably wouldn't have found it without.
Big thanks also to Gary Doug as well for his Scan9495 software if he's around on here.

Mitch