- Posts
- 58,170
- Location
- Preston Lancs.
Okay, so when I say 'spliced in' I connected directly to the ecu connector, to cut out any possibility of a break in the wiring between the ECU and the ODB port.
When connected via the ODB I get nothing back over the serial connection, just 'PP' (which I think indicates a communications timeout).
When connected directly to the ECU I get something back, a stream of 80 / 28 messages which according to the EAS unlock documentation indicate that the serial port is connected correctly, but can't sync with the ECU.
The dash beeps and shows 35Mph when you connect and the ecu power cycles true, I expected that, but it then continues to beep every couple of seconds which is the bit I don't think is expected.
I've now removed the ECU entirely and have successfully raised the car by Jumpering various pins on the connector, so proved that the compressor and valve block work fine. The backs drop overnight, so I'm guessing the rear air bags are due for replacement, but I'll check that with a soapy spray bottle.
I suspect the problem with communication is down to my laptop (I run linux, so have to run the EAS unlock suite in a VM, I think this is buggering the communications) but it definitely doesn't connect at all via the ODB port and does via the ECU pins.
I think I'm just going to make my own ECU so I can connect to it over wifi, get rid of the self levelling and generally make it a bit more transparent and easy to see what's going on.
As said earlier get everything back to standard and start from that. You are making things more complicated than they need to be.