standard USB-A. Perhaps Datatek you sell the adapters? I got the cable and cd from you a while back :)
The adaptors have proved to be a bit of a minefield, I have bought more than one that claimed to be a full RS232 implementation only to find out that it did not support RTS/DTS so I don't sell them. I always used the Prolific adaptor but Win 10 no longer supports the Prolific driver so I had to buy an FTDI adaptor for my Win 10 tablet.
I will look and see what I can find on the net.
Found this:- https://www.ebay.co.uk/itm/39407854...Ml47%2F0XTFCyg%3D%3D|ampid:PL_CLK|clp:2047675
It states it supports remote wake up so it should work but no guarantees.
 
Last edited:
Thanks Datatek! The cable off ebay has a long delivery date so I ordered the US232R-10-BULK off a local seller. I emailed the guys at FTDI and this is the response I got. Hopefully it will come in the next couple of days so that I can do some tinkering over the holidays. Hopefully it will help someone else should they find this thread. I will report back whether it works.


I am Kieran from the FTDI support team.




We have a number of USB to RS232 adaptor cables, with most of them supporting RTS/DTS.




Have a look at USB-RS232-WE-5000-BT_0.0, this is a USB to UART cable with RS232 level UART signals and supports RTS/DTS. You should also have a look at US232R-10-BULK. This is a USB to RS232 adaptor cable with TXD/RXD LEDs, and also supports RTS/DTS.
 
Thanks Datatek! The cable off ebay has a long delivery date so I ordered the US232R-10-BULK off a local seller. I emailed the guys at FTDI and this is the response I got. Hopefully it will come in the next couple of days so that I can do some tinkering over the holidays. Hopefully it will help someone else should they find this thread. I will report back whether it works.


I am Kieran from the FTDI support team.




We have a number of USB to RS232 adaptor cables, with most of them supporting RTS/DTS.




Have a look at USB-RS232-WE-5000-BT_0.0, this is a USB to UART cable with RS232 level UART signals and supports RTS/DTS. You should also have a look at US232R-10-BULK. This is a USB to RS232 adaptor cable with TXD/RXD LEDs, and also supports RTS/DTS.
FTDI are very helpful, I have a lead with TX/RX LED's, looks very pretty when in operation;)
Don't forget to install the driver before you plug in the adaptor.:)
 
Cable arrived yesterday, I installed and downloaded the drivers before plugging in the adapter. But alas still can´t get the software to communicate. The FTDI driver is selected, definitely not just a generic MS one.

The car seems to register a connection however, as soon as I plug into computer then Windows beeps to acknowledge a USB plugged in. The P38 flashes up "slow: 55kph", the LED lights all light up. And importantly the car stop dancing up and down. Compressor is totally silent and valves don´t click. As soon as I unplug the laptop the compressor springs back up to life and valves start clicking.

These are the errors I got in this order:
For example where is the EAS Tools Drop Down Menu?

upload_2022-12-23_11-58-33.png

upload_2022-12-23_11-58-12.png


upload_2022-12-23_11-57-33.png
 
Check what port number is assigned to the FTDI driver. In this example its Com-4.

Then in EASunlock, select that port.

upload_2022-12-23_11-15-46.png



upload_2022-12-23_11-14-36.png
 
Success with connecting! The com port needed setting, didn´t realise the "EAS Setup" was clickable. Anyway, here are my readings...
I am no expert, but the values under "calibrate" look to be off. Faults seem to indicate a few errors with the valves. I have a new spare valve block from Kurt, should I put that in? Front right height is showing a "0", the guy that was working on the car mentioned it needed a new sensor... and I ordered two new ones for the front and he replaced them. They were genuine LR and I bought them off Craddock.

What are your thoughts?

upload_2022-12-23_15-54-38.png

upload_2022-12-23_15-55-1.png

upload_2022-12-23_15-55-28.png
 
You have not got a good connection, there is no green "Good Idle" in the status button, it says no idle which equals no communication,
so those faults are meaningless other than as another indication that you have no valid comms.
 
I am no eggsquirt but have muddled through with the RSW. Your last pic isnt good did you press the "get" button to find the readings cos something is all wrong to me. but its been a while since I had to use it.

At least you got in now:).

J
 
I am no eggsquirt but have muddled through with the RSW. Your last pic isnt good did you press the "get" button to find the readings cos something is all wrong to me. but its been a while since I had to use it.

At least you got in now:).

J
No point in pressing the Get button, he doesn't have Good Idle so there is no communication.:)
 
You have not got a good connection, there is no green "Good Idle" in the status button, it says no idle which equals no communication,
so those faults are meaningless other than as another indication that you have no valid comms.
Oh dear, any ideas why that could be? Or is it just a case of keep trying?
 
Apart from Com5 the others all come up with an error. Weird thing is if I click "manual message" or "fault message" under the functions tab then it pops up as "good idle" and becomes green for a split second
 
In Device Manager, check the Port Settings. Make sure it's set like this.

You can also try increasing the Idle Delay slightly, but do it in small increments such as 100 or 125.


upload_2022-12-23_16-2-43.png
 
In Device Manager, check the Port Settings. Make sure it's set like this.

You can also try increasing the Idle Delay slightly, but do it in small increments such as 100 or 125.


View attachment 280311
Port settings are exactly those. Tx buffer responds with FF values. But the Rx buffer is 80. According to the troubleshooting guide should also be FF
 
TX is showing what the software is sending. It's the RX values that need to be correct, so the software then shows "good idle". Have you checked the connection from the Diagnostic Port to the ECU, especially the left footwell connections ?

Once it actually connects properly, the TX will show a steady stream. Then when you click the various things like Read Faults or Get Values, the TX will change to a few transmit bytes for each command.
 

Similar threads