Hi,
I installed the drivers for FTDI chip and reinstalled the driver for the COM port. My Win 10 says that there is no need to change the driver.
I tested on car, but the situation is the same... FES says that ELM327-> ECU connection is not possible
The last resort I have is to try with my old laptop, which I reinstalled and now I have to install all the things back on it.
Here are the tests of the interface made with FES:
Code: Select all
COMMAND: ATZ
RESPONSE:
ELM327 v1.4
>
COMMAND: ATI
RESPONSE: ATI
ELM327 v1.4
>
COMMAND: ATE0
RESPONSE: ATE0
OK
>
COMMAND: ATL0
RESPONSE: OK
>
COMMAND: ATH0
RESPONSE: OK
>
COMMAND: ATSPC
RESPONSE: OK
>
COMMAND: ATS0
RESPONSE: OK
>
COMMAND: ATCAF0
RESPONSE: OK
>
COMMAND: ATCFC0
RESPONSE: OK
>
COMMAND: ATCRA 7B0
RESPONSE: OK
>
COMMAND: ATSH 7B0
RESPONSE: OK
>
COMMAND: ATAT1
RESPONSE: OK
>
COMMAND: ATST41
RESPONSE: OK
>
COMMAND: ATBI
RESPONSE: OK
>
This interface is compatible with ELM 327 1.4! Should connect properly with all CAN modules.
This is the test for the VAG-COM cable:
Code: Select all
VagCom/KKL
Testing latency with 200 bytes of data...
Min latency: 0
Max latency: 2
Testing timers...
(The acceptable tolerance for results is ~5 ms)
System supports high resolution timer.
Testing timer with 1000 ms...
..result: 1001 ms
Testing timer with 250 ms...
..result: 251 ms
Testing timer with 750 ms...
..result: 751 ms
Testing timer with 100 ms...
..result: 101 ms
All seems OK, but I cannot connect to anythig else than the engine and gearbox, with vag-com also am able to connect to ABS
Obviously I can connect only to the modules that use the K line, the others are not reachable.
The only possible thing that might have happened, as I have not used the cable for 6 months, is that during this time I gave it to a friend of mine to use it on a BMW and to another who tried to use in on FORD and may be the cable has been damaged in any way...
Is that possible?