hi Yani
I have a doblo 2008 1.3 multijet
I have an ebay elm 3.27 interface 1.4
I am using your registered software
When I test interface with at commands they are all ok
But it notes latency too high
When I read available modules on the doblo 1.3 multijet it identifies the engine ecu,body computer and dashboard computer
When I try to connect to engine ecu..I get the red box "connection elm 327 to ecu failure"
If I connect to the doblo 1.3 jtd (same engine iso number) then connection is ok and I can read parameters and reset oil change etc
So what is the problem with the 1.3 multijet connection.
Help please
elm 327 to ecu connection failed
Re: elm 327 to ecu connection failed
There is no problem here. Doblo 1.3 JTD is the correct selection for your car.
Although it is listed as JTD, it is actually a multijet.
Although it is listed as JTD, it is actually a multijet.
Re: elm 327 to ecu connection failed
Thanks for your reply.
My doblo is the 1.3 multijet 85 bhp 16 valve version
There doesn't appear to be a 1.3 jtd doblo listed by fiat
What is the difference between the 1.3 jtd and the 1.3 multijet 16valve in your listings ??
My doblo is the 1.3 multijet 85 bhp 16 valve version
There doesn't appear to be a 1.3 jtd doblo listed by fiat
What is the difference between the 1.3 jtd and the 1.3 multijet 16valve in your listings ??
Re: elm 327 to ecu connection failed
The difference is the type of platform. One of them is based on Fiat Punto and uses the same CAN network model while the other is based on Grande Punto and uses its CAN network model. The two CAN networks are completely different and use different data formats and speeds... So, the diagnostics is different.
The JTD in the list is for Doblo type 119 and type 223. The MJET is for Doblo type 152 and type 263.
The JTD in the list is for Doblo type 119 and type 223. The MJET is for Doblo type 152 and type 263.
Re: elm 327 to ecu connection failed
Thanks for reply
So given that the doblo 1.3 mjet 16 and the doblo 1.3 jtd are on different platforms with different formats and data speeds.
Your ecuscan software and the elm 327 interface should be able to communicate with both of them.
So why does it fail with one of them..??
So given that the doblo 1.3 mjet 16 and the doblo 1.3 jtd are on different platforms with different formats and data speeds.
Your ecuscan software and the elm 327 interface should be able to communicate with both of them.
So why does it fail with one of them..??
Re: elm 327 to ecu connection failed
Hí all ,
My elm327 is 1.3a , between pins 6 and 14 the resistance is 40 OHM , some problem with this ?
My elm327 is 1.3a , between pins 6 and 14 the resistance is 40 OHM , some problem with this ?
-
- Posts: 870
- Joined: 12 Feb 2010, 09:03
- Location: EU, Germany
Re: elm 327 to ecu connection failed
@ istnag
Did you tried to test it with KKL interface?
I do not know is this going to be helpful but when I work on the older cars who have old 3 pin connector I am always using KKL 409 interface and it was working just fine...
Did you tried to test it with KKL interface?
I do not know is this going to be helpful but when I work on the older cars who have old 3 pin connector I am always using KKL 409 interface and it was working just fine...
Coded Keys & CODE card for Alfa Romeo, Fiat and Lancia cars
-
- Posts: 870
- Joined: 12 Feb 2010, 09:03
- Location: EU, Germany
Re: elm 327 to ecu connection failed
Ah those drivers can really make man go crazy...
A month ago I also had to reinstall all drivers and chose new comports + restart laptop few times...
A month ago I also had to reinstall all drivers and chose new comports + restart laptop few times...
Coded Keys & CODE card for Alfa Romeo, Fiat and Lancia cars