ACE on my 2004 Disco Td5 quit working. No logged faults. Also no leaks, abnormal noise, wobbling, or any other of the traditional ACE failure symptoms. Simply feels as if ACE wasn't there ('passive mode').
Found out that whilst Nanocom can't connect to the ACE ECU with the engine running, I could enter either ACE Read Input or ACE Record Input with ignition on, and then turn the engine on & continue to view or record ACE parameters (though a few times the connection was unexpectedly interrupted). While on 'instrument mode' (Read Input) it is possible to see how the different variables (one at the time) react to body roll while driving, i.e. the upper accelerometer reads negative values when turning left & viceversa. On the other hand if recording data the files come in a .ia8 extension that unfortunately cannot be open with Nanocom's Graph Viewer to analyse the saved information in the same way as fuelling input data, but can be 'played back' with Nanocom's software.
With engine off (note 'playback bar' below data table):
With engine on (idle):
While driving:
Noted the following:
- with engine off, pressure transducer reads about 12 bar (shouldn't be zero?) & residual pressure = 20 bar (also not good, Nanocom manual says it should be zero with engine off)
- with engine on, pressure transducer gives erratical readings between 4 and 30 bar (per RAVE ACE pump is a radial piston type --delivers variable displacement & constant pressure as far as I know-- that works at 135 bar)
- accelerometer readings are slightly miss-calibrated, should read zero with no vehicle movement.
- while driving, Nanocom road speed data does not match actual speed; i.e. the 51 km/h shown here were in real life in the order of 90 km/h -- I suspect this may be a Nanocom related issue (wrong conversion algorithm)
So for starters evidence points at the pressure transducer as the guilty party.
Aparently System Pressure & Residual Pressure are calculated by the ACE ECU. Does any one know what these mean?
Have had Nanocom for almost 2 yrs & never bothered to look at the ACE features, hence lack reference values from when it was functioning properly... If someone has the said figures please share them...
Rgds
Matt
Found out that whilst Nanocom can't connect to the ACE ECU with the engine running, I could enter either ACE Read Input or ACE Record Input with ignition on, and then turn the engine on & continue to view or record ACE parameters (though a few times the connection was unexpectedly interrupted). While on 'instrument mode' (Read Input) it is possible to see how the different variables (one at the time) react to body roll while driving, i.e. the upper accelerometer reads negative values when turning left & viceversa. On the other hand if recording data the files come in a .ia8 extension that unfortunately cannot be open with Nanocom's Graph Viewer to analyse the saved information in the same way as fuelling input data, but can be 'played back' with Nanocom's software.
With engine off (note 'playback bar' below data table):
With engine on (idle):
While driving:
Noted the following:
- with engine off, pressure transducer reads about 12 bar (shouldn't be zero?) & residual pressure = 20 bar (also not good, Nanocom manual says it should be zero with engine off)
- with engine on, pressure transducer gives erratical readings between 4 and 30 bar (per RAVE ACE pump is a radial piston type --delivers variable displacement & constant pressure as far as I know-- that works at 135 bar)
- accelerometer readings are slightly miss-calibrated, should read zero with no vehicle movement.
- while driving, Nanocom road speed data does not match actual speed; i.e. the 51 km/h shown here were in real life in the order of 90 km/h -- I suspect this may be a Nanocom related issue (wrong conversion algorithm)
So for starters evidence points at the pressure transducer as the guilty party.
Aparently System Pressure & Residual Pressure are calculated by the ACE ECU. Does any one know what these mean?
Have had Nanocom for almost 2 yrs & never bothered to look at the ACE features, hence lack reference values from when it was functioning properly... If someone has the said figures please share them...
Rgds
Matt
Last edited:
