The link above doesn't work for me - not sure why !
interface is showing on Com 3 - FES is set to use Com 3.
Interface test ( Ctrl+f11 or f10, can't remember which at the mo ) seems to work - it pulls up the data page anyway.
When the interface is connected to the car however it still fails for communicate with the ECU. Red TX lamp illuminates when plugged into USB - then intensifies in brightness when plugged into car. Other lights scroll through once then go out. When 'connect' is clicked, one of the amber lights flashes once or twice then goes out. None of the other lights do anything.
FES has been set up according to the instructions on the FES website, interface drivers were installed as per interface manufacturers instructions from the disk supplied with the cable.
Cable has been plugged in and unplugged and wiggled about several times and goes fully home.
FES detects the correct interface when the TEST function is used, however, it gives a 'Latency too high' message. I have reduce the latency via Device Manager to the lowest possible setting, unticked the 'Higher Latency' box in FES settings, set baud rates to 9600 in both FES and Windows (although the interface says 38400 on the back) but I still get the Latency Too High message.
FES detects the correct interface when the 'Scan For Interfaces' function is used.
FES 'scan' (f11) for ECU produces an empty box with no information in it.
FES 'connect' (f10) attempts to connect then produces 'cannot communicate with ECU - check connection and com port settings'
Garage I took car to last week had problems getting their diagnostic machine to connect to ECU also - took half a dozen or more attempts before it would work.
I think either dodgy cable or, as has been mentioned, dodgy OBD socket on car - this seems more likely due to the problems the garage had.
What is the easiest way to get the OBD socket off the car to check/resolder ? I am pretty good with the old iron !