Multiecuscan

I have a mk2 punto 1.9D and using the demo version i can't seem to connect to the airbag ecu.. now i'm unsure if the problem is with the actual ecu or the vagcom interface.. reply is always no ecu response..

using vagcom cable 409.1 with a wire shorting pin 7 to pin 3, FES can find the interface and passes the test button test.. any ideias?

When you say mk2, what year is the car, and which model are you selecting in the software?

car is year 2000 so it's not eobd/obd2 yet..

software has my specific model, punto '99 1.9D

i did allow FES to send something concerning the failed connection... don't know what use it has though..


EDIT:

i was with a friend today who has a full version of FES he bought when he had a fiat but no longer has the interface..
installed my vagcom cable on his computer and updated FES to the latest version, tests run great but still no connection to either airbags or engine ecu (DCU3F), according to the list the engine ecu requires a stock vagcom cable to read..

now i know i can access everything on the Bosch kts570 diagnostic unit except the airbags so the problem has to be with my interface..

my cable is identical to the one posted here viewtopic.php?f=5&t=255&start=70#p7021 by thugusher..

i'm starting to think FES has something wrong.. tested it on a 2001 punto 1.9jtd and it connected fine with engine and airbags using my interface..

tested again on mine and even though i'm using a demo it still tries to connect to the engine ecu (it's red so not supposed to in the demo) and gives the same "no ecu response" as the airbags..

definitely something is wrong with FES and the 1.9D car..

found someone near me with a working full version and all 3 interfaces, tested them on my car and same symptoms, a friends car that is exactly the same as mine but a month newer also had the same symptoms.. gives no ecu response on any ecu, same setup works fine on a 1.9jtd of the same year...

oddly enough it does work on the 1.9D doblo of the same year...

Try with different setting for "KWP2000 Timings" (it is in Options > Interfaces)....
Other users have tested the program on the same Punto 1.9D and it connects fine.

yani wrote:Try with different setting for "KWP2000 Timings" (it is in Options > Interfaces)....
Other users have tested the program on the same Punto 1.9D and it connects fine.

tried it will all settings, even ticking the latency box has no effect.. always gives the same no ecu response message, even with the interface disconnected from the car..

so 2 interfaces, one laptop running xp with full version of FES and mine running win 7 and demo version.. interfaces look the same internally (appears to be same circuit) and both work fine on a JTD but not on 2 1.9D..

odd thing is mine gives the same no ecu response when i try to connect to the engine ecu which is red, i thought red functions were disabled in the demo version..

led on both interfaces lights up when connected to the car and both pass the test, voltage is correct on obd socket and airbag ecu socket.

scan (F11) says scanning till the bar is full and says completed with no change on anything..

this is the result of the interface test on mine, the other gives the same results..



the only result a bit off is the first where it returns 1014ms..

both laptops are dual core, mine is I5 his is a t7300 (2ghz)..

elm interface connects to everything except airbags as it's supposed to, problem seems to be kkl specific..

reason the bosch unit wouldn't connect to the airbags was simple, the airbag ecu is dead.. probably the same reason FES wouldn't work, it should work on the engine ecu though since the xp laptop has a registered version.. will update..

The issue is so critical. Try with different setting for "KWP2000 Timings" (it is in Options > Interfaces)....
Other users have tested the program on the same Punto 1.9D and it connects fine.