General Immobiliser Problem FiatECUscan

Currently reading:
General Immobiliser Problem FiatECUscan

Seamas111

New member
Joined
Jun 29, 2011
Messages
11
Points
2
Location
Brockley, SE4
Hi all,

I have a similar problem to frankiebateman with my Punto x reg 2000 (see below).

I have started a new thread as I would like to try a diagnostic using the software mentioned in the above thread (FiatECUscan). I think I have an ok grasp of what I need to do but need some guidance on some(most) specifics.

For example; what kind of cable do I need to connect my laptop and the ECU (ODB1 or 2)? Where would I get it? Also, where would I plug it in!?

Would love to give this a shot, so if anyone has a spare moment to hold my hand it would be greatly appreciated!

Oh yeah a little background; Car was intermitttentley not starting, thought I had narrowed it down to starter motor or loose connection somewhere. Then on sunday it wouldn't start at all and the immobiliser light is on (orange key).

Thanks in anticipation,
(y)
 
Last edited:
So, gleaning everything I can from these very useful forum pages;

I think I need an ODB2 cable (potentially a 3 pin fiat adaptor as well) plus FiatECUscan. This should, be as far as I can tell, compatable for my Punto 1.2 8v X-reg (2000). Don't know the ECU model at the mo but will find out.

Anyone see anything wrong with this?
 
i;d be popping the cowling off around the bottom part of the Steering wheel - and have a look for the Antenna wire that surrounds the Ignition barrell and Make sure its not snagged and snapped its cable and that its nice tight and secure

If the Yellow/orange Key Code Light is on = Immboliser Activated
And your car WONT start - unless you happen to have the key code card, which at that point you can override it and start it
But if you stall or Switch it off, the code will have to input again an again and again


As for the Fiat Ecu Scan
The mk2 Punto uses OBDII (obd2)

As for What Type of Cable
Anything thats a KKL/VagCom Will work for ECU and Immboliser

Check the fiat Ecu Scan Website :)

ziggy
 
Thanks for the reply Ziggy,

I will try your suggestion re. wiring. Will the diagnostic tell me if there is no signal being transmitted by the ariel?

Of course like most people, I don't have the code for the immobiliser (or red key).:( So yeah it aint gonna start unless I can figure out why the chip in the key and immobiliser aren't talking to each other....

I'll check out the FiatECUscan website properly. And order what I need.

Thanks again for your help.
 
Last edited:
When I had issues like this, advice I was given was to take off and clean the earth strap that lives on top of the throttle body.

Touch wood, I haven't had any more bother since :)
 
Your X plate will have an EOBD 16-pin diagnostics socket so no need for the three-pin adapter. Check out my guide:

https://www.fiatforum.com/punto-gui...eset-ecu-airbag-errors-mk2-tenner-laptop.html

I don't think that you can sort immobiliser problems with this approach though. The diagnostics is all well and good for ECU and airbags (and electric steering if you get and ELM-based lead and paid-for software) but immobilisers are a whole new "can of worms".

red.
 
Hi all,

I have a similar problem to frankiebateman with my Punto x reg 2000 (see below).

I have started a new thread as I would like to try a diagnostic using the software mentioned in the above thread (FiatECUscan). I think I have an ok grasp of what I need to do but need some guidance on some(most) specifics.

For example; what kind of cable do I need to connect my laptop and the ECU (ODB1 or 2)? Where would I get it? Also, where would I plug it in!?

Would love to give this a shot, so if anyone has a spare moment to hold my hand it would be greatly appreciated!

Oh yeah a little background; Car was intermitttentley not starting, thought I had narrowed it down to starter motor or loose connection somewhere. Then on sunday it wouldn't start at all and the immobiliser light is on (orange key).

Thanks in anticipation,
(y)

Mind if i ask where you based , exactly what car it is, how old etc, would certainely help. On occasions disconnecting and reconnecting body computer sorts ,
 
Last edited:
the Immbo Tells the engine ECU whats wrong :)
So connecting to the ECU tell you Engine and Immbo Faults :)

Hence why you have replace the Immbo And Ecu when doing a lock change

Anyway - Get the fault code
And yes the F.e.s will tell you whats going wrong
Ie No Signal detected, or Weak / Broken signal or incorrect signal for instance

Ziggy
 
Thanks for all the advice and info guys,

Have checked the wiring to antenna and seems fine, cheers Ziggy.

Haven't got to the earth strap on the throttle housing yet but will check that also. Am I right in thinking that when I remove air box from top of engine to get to the throttle housing I can disconnect body computer from there?

Have located ECU connection point, I assume it's the 16 pin connection at the bottom centre of the interior fuse box?

I have now downloaded FiatECUscan and ordered an VAG COM USB DIAGNOSTIC CABLE 409.1 OBD2 II. Should arrive for the weekend so I'll hopefully be posting some codes here soon.

Thanks for the link to your thread Red.

My car is a 1.2 8v x-reg Punto, year 2000. She's great little car when she decides to run :D I'm based in Southeast London at the mo.

Thanks again for all the help,
 
these keys dont normally go off unless damaged so i await your reply sunday
not convinced its immobilisor see:confused:

No keys dont your right
Unless your mate decided to hook 240v up to the battery


anyway another story

If you get the fault code - im going to possibly assume its still going to be the antenna, its a item that does fail in some cars from time to time to be honest
its not rare, but not common, just a few stories here and there

But a Fault code will reveal alll

Ziggy
 
Mk 2 Punto does not have the red key.

The original code cards were thrown away by Fiat UK when the cars were sold. Who knows why, they are normal issue anywhere else in EU..
 
Hi guys,

So I ran a diagnostic on the ECU. Its a bit of an essay, error codes at bottom but please do read whole post for some context:

First off I kept getting "Connection failed. No ecu response" when trying to connect to the ECU. Checked com ports/latency etc and all good.

Noticed that Relay T09 (One off the Fuel Injection relays, in engine bay fuse box) was clicking on/off constantly (several times per second) when ignition was in MAR position. I tried changing the T09 relay (swapped it with a heater fan relay) but got the same result, constant clicking and "Connection failed. No ecu response." when trying to connect to the ECU.

I then removed relay T09 and left it empty and I managed to connect to the ECU immediately. Subsequent connection attempts were sometimes successful with relay T09 re-inserted and it would stop clicking as soon as connection was made. Then other times it would only connect if I removed relay T09. Anyone got any ideas about this?

Secondly, when I managed to connect to ECU: I got "Invalid ISO Code" error once connected. I used the "FIAT Punto '99 1.2 8V MM IAW 59F EOBD Injection" profile in the FiatECUscan menu as this was the closest fit to my car (Punto 2000 1.2 8V MM IAW 59F) but not a perfect match. I only had a choice of the '99 or '03. I tried the '03 profile and got the same ISO error.

However, I still got connected to the ECU this way and got some error codes:

P0105 - MAP/BARO Pressure (1) Signal High - Stored - Light on
U1601 - CAN messages TX - Invalid Signal - Stored - Light On
P0230 - Fuel Pump (1) - No signal - Fatal - Light on

The last one (P0230-fuel pump) I am assuming is because relay T09 is still unplugged. Correct?

So can anyone interpret these error codes? I think U1601 is probably the culprit, can't read key or something like that right? What does that mean in practical terms?

Any advice would be greatly appreciated, thanks in anticipation :)
 
I do too get the invalid ISO code, its because the software doesn't know your ECU code, but is still able to read it

if the Fuel pump - no relay = No Power = fault
u1601 - could be the Immbo NOT seeing the key
105 - no idea

Eitherway - Make a note and reset them
See what happens when you put pump back in and try to start it

ziggy
 
u1601 is not a key problem, its as described a CAN message error

The electronic system is a network and CAN is the protocol (defining how each should talk to each other) u1601 mean invalid/missing instruction(s) or corrupt data.

I would reset all faults then remove the lead off the battery, wait 10 mins or so, then disconnect the enginge ecu and all the leads from the front/back of the body computer ( internal fusebox ) then reattach all the leads followed by the battery, then see if things have improved.
 
Hi guys,

I cleared errors and they all come back as stored again.

I can now connect without taking fuel pump relay out but relay is still clicking like crazy when I turn key to mar. And obviously the key code light doesn't go out.

I haven't disconnected everything as you suggest Paul. I'll do that now.

How would I check that the ECU is earthed properly? I tried running a temporary crude earth from throttle housing where ECU is attached to car body (which didn't solve anything) but was wondering if there is a better way?

Cheers,
 
Just attach a lead to the metal on the ecu or throttlebody and the other side to the battery -
 
Hi all,

Well turns out my previous attempts at earthing the ECU weren't any good :eek:

Earthed to the bat -ve as you suggested Paul and code light went out and engine turned over!

Haven't actually got it running yet though as my crude earth kept vibrating loose but pretty sure a proper earth will solve it.

Has anyone ran an extra earth from their ECU/throttle body? Is it best to earth to the bat -ve or the body? What kind of cable should I use?

Also, where is the existing earth from the ECU hiding? shaun200765 mentioned an earth strap on top of the throttle body but I couldn't find it? (maybe that is the problem lol)

Thanks again for everyone's help, it is very much appreciated.
 
Back
Top