Thread: Constant Amber ACE light - No faults on nanocom

HI, unfortunately nanocom is not the best when it comes to ACE, you should try with a tester with the original protocol(hawkeye, lynx, T4 or autologic)...untill then make sure that the fuse and relay are OK, F15 engine bay and swap relay R14(ACE) with R13(horns) to rule them out,

some questions:

1. did you calibrate the accelerometers?
2. can you read live inputs from the control valves and pressure transducer?
3. is there a serious twirl in the tank with engine running?

Thank you!

Good advice, it has brought me another step along the pipeline to getting it going. There was no ace relay so i put the horn relay into R14 started her up and still had the amber light on. Only, this time I got an error code: 01 - 05 Upper and lower accelerometer signal too different .

The inputs read, upper: -01.42 lower: 001.42. I have calibrated them a couple of times but still have the same readings. Is it possible that i've mounted the upper accelerometer the wrong way, hence having a negative figure but the same number as the lower?

No twirl when the car is running.

first of all prime the pump, open the outlet banjo and turn the pump untill you get flow there, there must be quite serious activity in the tank with engine running or there's not enough pressure in the system... as i said nanocom is unreliable with this especially on fault codes, you should have got ''relay open load'' code without relay... try to read live pressure cos on live data it's usable

Sorry, i misread your twirl question. There is a quite a lot twirl/flow/disturbance in the ace fluid tank when the car is running. I'll get in the live pressure values sometime tomorrow and post them here,

Thanks again.

Okay so at 750rpm dcv1 and 2 read .01 and the pcv reads 0.06.

After rereading the Nanocom ace pdf it says that the accelerometers should only read up to 1.14 because mine are reading +/- 1.42 do you think it's something wrong with the hardware or software?

On my working system the accelerometer readings at idle are between 0.01 - 0.05 both.... on my hawkeye, i'll compare tomorrow with my nanocom to see if there are any differencies, i compared live pressure readings some time ago and those were OK but never went with nanocom further in ACE cos i know it's unreliable especially with fault codes also it failed on a friends car to do a system test and c alibration while hawkeye went happy through them

can you read pressure from the transducer though('pressure sensor' in nanocom)?... you should get between 16 -20 bar at idle... the 'system pressure' and 'residual pressure' are irrelevant while stationary

So, input readings are reliable with nanocom, i compared with hawkeye and they are the same for pressures and accelerometers, removed the relay then unplugged the pressure transducer to see about the fault codes, got ''relay open load'' and ''pressure sensor open circuit'' codes with hawkeye but no code on the relay and ''DCV 1 open circuit'' with nanocom for the transducer... so you can use nanocom for live input readings but better don't rely 100% on the fault codes


also nanocom failed to calibrate and run the ''system test'' while hawkeye did it without probs


though on your's it looks like it is in the good 'region' cos the live readings and fault code too are pointing to the accelerometers... unfortuntely i can't imagine what's the trouble unless the ECU is missbehaveing

Sorry for taking a while to get back on here.

Some weird progress on my end. I was previously been getting no pressure from the transducer. This was kind of expected though because I was getting the accelerometer error.

Here's the weird part. When I park my car on an angle so that the car is pointed on a slight down hill the ACE warning light turns off and the ace works. I've plugged the nanocom in at this stage and the transducer pressure reads at around 19 bar, Upper accelerometer reads 0.01 and lower reads 0.27.

I assume that an accelerometer calibration will fix all this but I've tried this a number of times on a flat surface and the system (a little too quickly) completes the process and the accelerometer readings don't change.

Any ideas?