Rollinthunda
Member
I do get the 35 slow and beeps yes it’s a tall black one the pic of it is about 12 posts up.
Datatek
Well-Known Member
So the EAS system is aware that diagnostics have been connected. Being lazy, personally I would get a spare relay to eliminate that.
I will dig my cable out this evening (when it's cooler), and check all the serial port settings, although I heard the software sets the rate when starting, so it should not matter.
The three delay values will depend on the Laptop you are using. Defaults usually work, but I have had similar issues with other serial console devices. Not gonna explain in detail here, but if anyone is interested it's about "inter-packet delays", where the data rate is correct, but the gaps are wrong.
Check mine with Laptop & EAS Unlock this morning. Here's what should happen:
Serial Port is configured for 9600 baud, 8 bit, 1 stop bit & no parity.
EAS Unlock Initialise sequence:
EAS Unlock Good Idle:
- Plugged in diagnostic cable to car.
- Connect FTDI USB-Serial to diagnostic cable - get 3 beeps & 35mph message.
- Connect USB to Laptop - another 3 beeps.
- Start EAS-Unlock, and select correct comm port (mine doesn't remember the correct port, but changes depending on what USB socket !!)
- Click Initialise and it connects - sequence is shown in screenshot below.
Serial Port is configured for 9600 baud, 8 bit, 1 stop bit & no parity.
EAS Unlock Initialise sequence:
EAS Unlock Good Idle:
Rollinthunda
Member
I will run through the process again hopefully tomorrow night and post my comparison (obviously I don’t get good idle just red) and PP in the RX
Rollinthunda
Member
Ok definitely does the beeps and definitely hear the relay clicking on and off every time I initialise
Rollinthunda
Member
I’m hoping to go see a guy this weekend who has a T4 diagnostics machine…. He said it “May” enter the eas in a slightly different way to the RSW program? Anyone know if this sounds plausible????
Datatek
Well-Known Member
The basics should be the same but worth a try.
Rollinthunda
Member
Datatek
Well-Known Member
So, you have some corroded pins on the connectors or broken wires., just have to identify the connectors and wires.
+1 on bad connector or ground wire. Also wondering if you have fusebox issues ?
At least T4 is telling you more, although I suspect T4 is reporting related symptoms as well as the actual root cause. It probably failing to start communications, hence reporting likely problems !!
At least T4 is telling you more, although I suspect T4 is reporting related symptoms as well as the actual root cause. It probably failing to start communications, hence reporting likely problems !!
- F24 & F44 are the power feeds to the Delay Relay. C118 pin6 = relay ground
- Any one of these impact the delay relay, which T4 is grouping as the same issue.
- If the relay is toggling when you start communications, then it's more likely the ECU connections, check the relay passes 12V to ECU.
- F33 = 12V feed to diagnostic socket.
- This is required for Nanocom power, but maybe not for T4 or EAS Unlock ?
- Check the fuse & wires anyway.
- C117 Pin 18 on ECU, goes via splice S110 to ground.
- ECU might not be powered on? - hence all the problems above.
Rollinthunda
Member
Ok…. I have bridged serial comms received and serial comms transmit straight from odb2 to very near eas ecu to rule out wire breaks in those 2 . I don’t know how to check whether 12 volts are going from relay to ecu. And where does c117/8 (the black wire from pin 18) actually earth on the vehicle as I’ve tried tracing it but it disappears into the loom under dash?
Rollinthunda
Member
Oh and checked all fuses they’re good
Datatek
Well-Known Member
You need more than Tx & Rx, you need the RTS signal to activate the EAS relay.
@Rollinthunda The EAS ECU ground goes via splice S110 (no idea where that is) to E154 in engine bay.
Rollinthunda
Member
Rollinthunda
Member
Ok cleaned the earth still no joy,, I have a question being as I’ve just ordered another 2nd hand eas ecu before my airbag let go the air suspension was in full working order would the suspension be in full working order if the eas ecu was dead?
Datatek
Well-Known Member
It doesn't need OBD comms for the EAS to work
Rollinthunda
Member
Right then!!!! Received replacement eas ecu, plugged it in, connected laptop and as soon as I fired up the eas unlock program the vehicle cleared faults and proceeded to raise, this is before even pressing initialise, however when initialising program still get pp in the comms and tbh the vehicle seems to be riding really high on std height mode and just seems to be behaving a little odd suspension wise. Should I now plug the old unit back in maybe?
Datatek
Well-Known Member
The new ECU probably did not have any faults recorded, it cannot clear faults all on it's own nor can the EAS unlock program clear faults if there is no comms.
A height calibration will need to be done with the new ECU as it will hold the settings for a different car.
No comms may still be down to the driver you are using in Windows if you are using a USB to serial adaptor or the adaptor itself. I certainly sounds like your old ECU is faulty but no harm in putting it back if you want to, it will still have the faults recorded that it had before you unplugged it.
