Page 1 of 1

connecting-disconnecting

Posted: 11 Aug 2010, 20:41
by keedoo
Hi i tryed to use multiecuscan on alfa romeo 156 2.0ts ecu Bosch Motronic ME3.1 (2.0TS SELESPEED) but :
I can connect and read fault codes .... after few seconds it will disconnect any sugestion?
Using VAG-KKL-Interface :?:
:oops:
Thank you

Re: connecting-disconnecting

Posted: 12 Aug 2010, 07:48
by yani
Hi,

Other users also reported that Multiecuscan cannot connect properly to some ME3.1 ECUs with VagCom interface, but works properly with ELM interface.
The ME3.1 that I tested works properly.

Anyway, I will appreciate if someone with this problem wants to help me find and fix the problem.
So, if anyone wants to help I will send him a special version of Multiecuscan that will generate a detailed log file of the communication. This log file will help me fix the problem.

Yani

Re: connecting-disconnecting

Posted: 12 Aug 2010, 09:52
by devc
Hi Yani,
I have found this disconnecting problem on the Me 3.1, Me 1.5.5, Me 7.3.1& Selespeed controllers as well.
I usually lose connection as soon as I select more than one Parameter to read.
The other functions work well and FEC does not disconnect.
I found that by rebooting the laptop helps to solve the problem sometimes.
I would like to help out if I can. I have a fairly large turnover of especially Alfas coming thru my workshop.
I thought it may be a memory problem, but after running task manager at the same time it is definitly not that, or
processor overloading problems.
There is no indication of latency problems. I have also switched of all other running programs and it makes no difference.
I normally use a KKL cable but sometimes my ELM327 v1.3 bluetooth works better.
It may also be the USB power supply to the USB/RS232 chip in the KKL cable being a bit low.
I have not checked that yet. Maybe doubling up on the USB connector may solve the problem.
It will be interesting to see what the problem is.
Regards,
Dev

Re: connecting-disconnecting

Posted: 12 Aug 2010, 10:09
by devc
Sorry me again,
The more I think about it the more I am convinced the problem is the USB power supply from the laptop.
The more data traffic thru the KKL interface the quicker it loose communications.
The AlfaDiag Program suffers from the same problem.
Some laptops are worse than others.
Regards,
Dev.