Battery condition and ECU / EZK performance.
07-13-2014, 05:12 AM
#1
Pro
Thread Starter
Battery condition and ECU / EZK performance.
Hi All.
Moi left a door ajar for 48 hours and really flattened the battery. I mean 'flattened'
Yes - I kow this is a big no no but manure happens.
OK. Put on charge with a Z-tek charger. As it happens it was there for three days. Unintended.
Right. Today - off we went for a Sunday drive. Whoa!!!
In my 2 years of ownership I've not experienced such engine responsiveness, smoothness, and all round power delivery as I enjoyed today. WOW.
))
OK:
My question: apart from likley improved ignition energy, could the better battery condition (de-sulphated = lower internal resistance) contribute to less 'electrical noise' on the 12V rails supplying the ECU / EZK brains, thus enhancing their performance?
Maybe John Speake has data on this?
In any case I welcome all contributions.
Thanks.
UpFixen.
Moi left a door ajar for 48 hours and really flattened the battery. I mean 'flattened'
Yes - I kow this is a big no no but manure happens.
OK. Put on charge with a Z-tek charger. As it happens it was there for three days. Unintended.
Right. Today - off we went for a Sunday drive. Whoa!!!
In my 2 years of ownership I've not experienced such engine responsiveness, smoothness, and all round power delivery as I enjoyed today. WOW.
))OK:
My question: apart from likley improved ignition energy, could the better battery condition (de-sulphated = lower internal resistance) contribute to less 'electrical noise' on the 12V rails supplying the ECU / EZK brains, thus enhancing their performance?
Maybe John Speake has data on this?
In any case I welcome all contributions.
Thanks.
UpFixen.
07-13-2014, 06:02 AM
#2
Rennlist Member
I suspect that the battery volts were so low that you effectively reset all the fuelling adaptations that are stored in SRAM in the LH ECU. These can get out of kilter sometimes. The contents of the SRAM are cleared if the battery is disconnected.
Similarly, the EZK can stored what it thinks are suspect signals from the knock sensors and these will retard the ignition by 6deg. Porsche recognised this problem (false noise events) and did introduce a software mod that cleared the fault codes in the EZK SRAM every 50 ignition on/off cycles. But I'm not sure how well that works.
I've had quite a few cars here with an knock fault code stored, but when the code was cleared with the tester, and the car run again, the code did not re-appear and of course the car ran much better. A quick battery reset (just a few seconds) will clear all stored fault codes in all the diagnosable ECUs, except the airbag controller.
Similarly, the EZK can stored what it thinks are suspect signals from the knock sensors and these will retard the ignition by 6deg. Porsche recognised this problem (false noise events) and did introduce a software mod that cleared the fault codes in the EZK SRAM every 50 ignition on/off cycles. But I'm not sure how well that works.
I've had quite a few cars here with an knock fault code stored, but when the code was cleared with the tester, and the car run again, the code did not re-appear and of course the car ran much better. A quick battery reset (just a few seconds) will clear all stored fault codes in all the diagnosable ECUs, except the airbag controller.
07-13-2014, 06:30 AM
#3
Pro
Thread Starter
I suspect that the battery volts were so low that you effectively reset all the fuelling adaptations that are stored in SRAM in the LH ECU. These can get out of kilter sometimes. The contents of the SRAM are cleared if the battery is disconnected.
Similarly, the EZK can stored what it thinks are suspect signals from the knock sensors and these will retard the ignition by 6deg. Porsche recognised this problem (false noise events) and did introduce a software mod that cleared the fault codes in the EZK SRAM every 50 ignition on/off cycles. But I'm not sure how well that works.
I've had quite a few cars here with an knock fault code stored, but when the code was cleared with the tester, and the car run again, the code did not re-appear and of course the car ran much better. A quick battery reset (just a few seconds) will clear all stored fault codes in all the diagnosable ECUs, except the airbag controller.
Similarly, the EZK can stored what it thinks are suspect signals from the knock sensors and these will retard the ignition by 6deg. Porsche recognised this problem (false noise events) and did introduce a software mod that cleared the fault codes in the EZK SRAM every 50 ignition on/off cycles. But I'm not sure how well that works.
I've had quite a few cars here with an knock fault code stored, but when the code was cleared with the tester, and the car run again, the code did not re-appear and of course the car ran much better. A quick battery reset (just a few seconds) will clear all stored fault codes in all the diagnosable ECUs, except the airbag controller.
))So I would imagine that would equate to a 'battery reset'.
Whichever way it worked out the performance today was WHEEEEEEE ...