Updated from FES 2.8 to FES 2.8.2
Car: 159 MJET 16V
Using elm 1.3a (bleutooth) and KKL-USB.
With the ELM: getting connection to everything exept to motor and ABS (did not test proxi-alignment because everything works well)
with KKL-usb: same story: no connection can been made tot motor and ABS
On FES 2.8 everything works fine....
Tried the KKL-cable on (evaluation FES 2.5) other computer: everything works. I can' t test the ELM on the other computer because of no bleutooth on this laptop.
Apparently it is not possible to install a older version of FES... I tried it wit the installer of FES 2.5.....but
I do not have the installer of FES 2.8 anymore, but if 2.5 is not working propely anymore, the same wil happen to FES 2.8.
Yani (or someone else), can you help?
Thanks
FES 2.8.2 no connection possible to Motor and ABS
Re: FES 2.8.2 no connection possible to Motor and ABS
I can ssure you that the problem is not in version 2.8.2 simply because there is absolutely no difference in the engine and ABS connection modules in version 2.8 and 2.8.2.
But you can send me a report after unsuccessfull connection so that I can try to see where the problem is.
But you can send me a report after unsuccessfull connection so that I can try to see where the problem is.
Re: FES 2.8.2 no connection possible to Motor and ABS
Problem is solved.
I do not know what solved the problem, but i've disabled all possible interfaces (settings) except the one that I'm using at the moment.
* For the ELM327 -bluetooth interface, I've chanched the buffer size from minimum to a "intermediate" buffersize (for me it is COM5 & COM6).
* The KKL-usb cable worked again by changing COM3 into COM4. (I do not understand why I had to change it, I remember (not sure-it was a long time ago i've used the kkl-interface) that in the past the kkl-interface worked well on COM3.
It's a bit a strange storry i'm telling, but I hope this is helpfull for someone that have the same problems.
Maybe someone else can explain better what the exact problem was....
I do not know what solved the problem, but i've disabled all possible interfaces (settings) except the one that I'm using at the moment.
* For the ELM327 -bluetooth interface, I've chanched the buffer size from minimum to a "intermediate" buffersize (for me it is COM5 & COM6).
* The KKL-usb cable worked again by changing COM3 into COM4. (I do not understand why I had to change it, I remember (not sure-it was a long time ago i've used the kkl-interface) that in the past the kkl-interface worked well on COM3.
It's a bit a strange storry i'm telling, but I hope this is helpfull for someone that have the same problems.
Maybe someone else can explain better what the exact problem was....