Page 1 of 1

Alfa 156 2.4JTD airbag fault code reading problem

Posted: 24 Mar 2010, 20:55
by the patriot
Hi my alfa 156 2.4jtd has a fault bringing on the airbag light, I have a lead and bridged pin 3 & 7 can connect with the engine ECU and airbag ecu.

Problem comes when i try and read the airbag fault codes, i get an error message with the software and it asks me to cancel or continue, if i cancel it shuts down Fiat ECUscan, if it continue i keep getting the same error message.

It just refuses to read the fault codes.

Actuators and data reading works fine.

Ive tried several different model and ECU types, still no joy.

Re loaded the software, check my soldering on the lead and still not able to read the fault codes,

Any suggestions welcome.

Otherwise great software and contribution to follow.


Steven

Re: Alfa 156 2.4JTD airbag fault code reading problem

Posted: 25 Mar 2010, 21:47
by the patriot
Ive looked at this more and the message i get suggests something to do with jitdebugger????

Im no software man so any help in plain english to over come this greatly appreciated..

Regards

Steven

Re: Alfa 156 2.4JTD airbag fault code reading problem

Posted: 26 Mar 2010, 12:37
by alfa156sarajevo
can you tell me the year of your Alfa 156?

Re: Alfa 156 2.4JTD airbag fault code reading problem

Posted: 26 Mar 2010, 22:03
by the patriot
HI there

The car is a 2000 model on w plate

Steven

Re: Alfa 156 2.4JTD airbag fault code reading problem

Posted: 26 Mar 2010, 22:39
by yani
Hi,

I already answered on another topic that this is a software bug. It is fixed in the next relase, which wIll be out soon.

Yani

Re: Alfa 156 2.4JTD airbag fault code reading problem

Posted: 29 Mar 2010, 20:44
by the patriot
yani wrote:Hi,

I already answered on another topic that this is a software bug. It is fixed in the next relase, which wIll be out soon.

Yani

Many thanks Yani

Re: Alfa 156 2.4JTD airbag fault code reading problem

Posted: 08 Apr 2010, 19:57
by the patriot
Alas, Yani i still have the same problem with V2, did you manage to resolve it intime for release?