ELM327 V. 1.5 “COMMAND: ATZ / Connection timeout” issue
Posted: 27 Aug 2013, 22:14
Hello Everybody,
hope anybody can help me about the “COMMAND: ATZ / Connection timeout” error message Multiecuscan 1.6 (free) version is throwing during my software evaluation attempt. My car is a LANCIA Ypsilon 1.3 JTD D.F.N (robotized gear shift) and the interface is a Bluetooth ELM327 V.1.5 (from Hong Kong).
Please consider the following steps I made so far:
1) Tested the interface with Torque app from Android tablet and everything was OK beside the fact I was not able to reset the service message and therefore I needed to refer to a more specific software like MES;
2) Using a notebook installed with Windows 7 64 bit and an external Bluetooth dongle I tried to install the Bluesoleil 3.2 drivers which came with the interface but immediately realized that this version was not compatible with my 64 bit Windows O.S. and therefore immediately switched to a more recent and officially compatible BlueSoleil 6.0 version which was in fact able to properly instance the Bluetooth device a couple of COM ports;
3) So I preventively managed to apply the interface mod by removing the “121” resistor as already described many times in the dedicated thread on the present same forum;
4) Then I managed to reconfigure both new COM ports setting the “Bits per second” parameter to 115.200 (as per MES manual in the case of Bluetooth devices) and lowering the two buffer related parameter to the “1” value;
5) The same (COM port reconfiguration operation) was applied to the additional COM port which was created when I searched for a new Bluetooth peripheral (the ELM327 interface) from the Bluetooth Devices window in Windows 7, which was in fact immediately successful;
6) Pairing and connection opening operations were both successful when performed from the dedicated O.S. Bluetooth window;
7) So moving to the MES application unfortunately I found that the “Scan For Interfaces” functionality is not able to automatically configure any kind of interface;
8) Also forcing the configuration to the correct parameters (ELM 27 1.3+ Bluetooth / COM 6 / 115200) ad testing it just always gives me: “COMMAND: ATZ / Connection timeout”;
9) BTW, as already read many times in different threads on this same forum I tried to update the COM port driver with the one download from the FTDIHIP site but it seems not to be compatible with the virtual COM port driver installed by the Bluesoleil installation package;
10) FYI, I already managed to try different combination of COM ports and relevant connection speeds without any luck even if some of the leds on the interface appear to blink during the connection attempts. One thing I noticed is that when I successfully pair and connect the interface in Windows and then move to MES to try to do the same (e.g. pushing the “Scan For Interfaces” button ) apparently the connection in Windows drops, but I’m not sure whether this is correct or not.
Any clue on how I can fix the issue?
Any help would be highly appreciated and recognized.
Thanks,
Matteo / Italy
hope anybody can help me about the “COMMAND: ATZ / Connection timeout” error message Multiecuscan 1.6 (free) version is throwing during my software evaluation attempt. My car is a LANCIA Ypsilon 1.3 JTD D.F.N (robotized gear shift) and the interface is a Bluetooth ELM327 V.1.5 (from Hong Kong).
Please consider the following steps I made so far:
1) Tested the interface with Torque app from Android tablet and everything was OK beside the fact I was not able to reset the service message and therefore I needed to refer to a more specific software like MES;
2) Using a notebook installed with Windows 7 64 bit and an external Bluetooth dongle I tried to install the Bluesoleil 3.2 drivers which came with the interface but immediately realized that this version was not compatible with my 64 bit Windows O.S. and therefore immediately switched to a more recent and officially compatible BlueSoleil 6.0 version which was in fact able to properly instance the Bluetooth device a couple of COM ports;
3) So I preventively managed to apply the interface mod by removing the “121” resistor as already described many times in the dedicated thread on the present same forum;
4) Then I managed to reconfigure both new COM ports setting the “Bits per second” parameter to 115.200 (as per MES manual in the case of Bluetooth devices) and lowering the two buffer related parameter to the “1” value;
5) The same (COM port reconfiguration operation) was applied to the additional COM port which was created when I searched for a new Bluetooth peripheral (the ELM327 interface) from the Bluetooth Devices window in Windows 7, which was in fact immediately successful;
6) Pairing and connection opening operations were both successful when performed from the dedicated O.S. Bluetooth window;
7) So moving to the MES application unfortunately I found that the “Scan For Interfaces” functionality is not able to automatically configure any kind of interface;
8) Also forcing the configuration to the correct parameters (ELM 27 1.3+ Bluetooth / COM 6 / 115200) ad testing it just always gives me: “COMMAND: ATZ / Connection timeout”;
9) BTW, as already read many times in different threads on this same forum I tried to update the COM port driver with the one download from the FTDIHIP site but it seems not to be compatible with the virtual COM port driver installed by the Bluesoleil installation package;
10) FYI, I already managed to try different combination of COM ports and relevant connection speeds without any luck even if some of the leds on the interface appear to blink during the connection attempts. One thing I noticed is that when I successfully pair and connect the interface in Windows and then move to MES to try to do the same (e.g. pushing the “Scan For Interfaces” button ) apparently the connection in Windows drops, but I’m not sure whether this is correct or not.
Any clue on how I can fix the issue?
Any help would be highly appreciated and recognized.
Thanks,
Matteo / Italy