Hi guys, im new to the forum. Im usually found in the vauxhall forums but ive been asked to have a look at my dads W reg (99/00) 1.6lt fiat multipla.

The problem is it sometimes feels like is missfiring. Before he got the car (3 month ago) it was owned by a friend and it had new plugs and coilpack. The gearbox failed in true multipla style and the planet gear broke in half and fell out when the driveshaft was removed. Common issue so im told. A used gearbox was fitted.

While trying to track the issue with the missfire the injectors were checked. 2 of them were giving around 14ohm from memory and 2 were not given any reading. These 2 injectors were replaced with used injectors which were the same part number/colour band as the ones fitted. both replacedments were 14ohm. The car ran alot better but still gives the occasional cough/splutter.

There is a light coming on the dash when it starts spluttering. I need to read the fault codes to see what the ECU thinks is the issue.

So basically my post is regarding what diagnostic code reader will work on this car as its a 99/00 model. Will something like a ELM327 with the red/yellow/red leads work or a VAG interface with pin switch running fiat ecu scan.

Any help you guys can offer will be gratefully received.

I use a a generic VAGCom/KKL cable with Multiecuscan http://www.multiecuscan.net/

Free version is all you need, alternatively try any OBDII fault reader, would say that 99 might be bit early for OBDII, I used an OBDII on my 52 plate Multi and Multiecuscan on the 55 plate.

If your near North London, I'm happy to have a look

Yes its the year thats concerning me. I think it has a Magnetti Marelli IAW-49F engine management system, which from what ive read on the fiatecuscan site its supported by Vagcom/KKL and also ELM327 both without any modifications or crossover cables. This would only cover the engine management and not any of the other modules but I think ill only need the ECU fault codes.

I was just interested on whos got what cables and any recomendations that you all have.

Many thanks for your replay and offer but unfortuantly im northwest UK.

marks152 said:

Hi guys, im new to the forum. Im usually found in the vauxhall forums but ive been asked to have a look at my dads W reg (99/00) 1.6lt fiat multipla.

Click to expand...

Welcome to a decent car forum then

When you say 'misfire' when and when does this happen. The TPS are common on these models and give a jerky almost stuttering sympton.

Can you describe the fault more?

The splutter seems to happen more on acceleration. It idles perfect and revs up ok. Just seems to feel its holding back/missing a bit on acceleration. Its fine at a constant speed. Of course this info is second hand as ive not driven the car myself.

The car had been lay up for 2 years prior to my dad rescueing it from being scrapped due to the gearbox issue. The missfire/running issue was present before the car was parked up 2 years ago and untill then was in use every day. BTW It passed MOT emissions so im sure its nothing to serious. It would just be nice to sort the car for him which is why I think I need to get the codes read.

Regarding the TPS - I can check this with a multimeter as ive got some test data on my laptop for this. Ill probe it at the ECU to confirm there is no issue with the wiring.

Ill give him a ring today and confirm that the info provided is accurate.

if there was a worn or dirty section on the TPS track you would feel it at the same throttle opening however as you say you can check this with a multimeter but it may be easier to do at the sensor itself as it's easy to get access.

Might be worth putting some fuel treatment through it and give it a good blast if it has been sitting for 2 years however as you say the fault was there previous. Have you checked the lambda sensor, done a few of these on the 1.6 engine.

Ill check the TPS with a multimeter and check for a good linear restance change through its range.

Its had about 5 or 6 bottles of redex through it over the last few months. It doesnt really seemed to have helped much.

Ive not looked at the lambda sensor yet but ive got a spare one sat in my shed that i could fit. can you confirm that its a 4 wire zirconia sensor and its a 18mm thread. If so ive got one from my Zafira that can be modded to fit. I know its a good one as ive tested it on my own car. It will probly just need the plug changing. Not too much of a job.

Ive just been looking at the full wiring diagram for the whole engine management system and its really basic so there aint too many things to go wrong thankfully. Im sure Ill have the problem tracked down as soon as i can get some time and have a diagnostic scanner capable of reading the fault codes. At least it MIGHT point me in the right direction. Of course just like any other fault code. It can also lead you up the garden path.

Ive just ordered a Vag com KKL lead and some DIP switches and im going to MODIFY the interface to work on both VAG and FIAT by configuring the switches as required. Ive managed to sort a full registered version of the Fiat ECU Scan software out so im all ready to go. Just awaiting the interface to come.

The interface arrived today which was really quick with it being christmas. Ive opened the interface and found some very poor quality soldering even by my own standards. Pin 16 from the DLC connector was not even soldered onto the board so it would have never works as pin 16 is the 12v+ supply from the car. Ive resoldered 5 or 6 really poor connections so hopefully it might work now. See pic. Ill try it over the next few days and post back my findings.

Remember to post where u brought this so no one else makes the same mistake and ends up with broken stock

This cable was a Ebay special. Cant grumble for £6 delivered. You get what you pay for im afraid. Ive had a fair bit of experience with vauxhall clone OPCOM interfaces so i know what to expect which is the main reason I opened the interface up to check before plugging it in. Ive seen these silly mistakes made with opcom interfaces. All the dodgey connections have now been fixed but ive not been able to test the interface as i do not have a VW/fiat to test it on. It may complete the test interface if I plugged in into my Zafira. That also uses KWP protocol so therfore uses the same pins.

I was considering bench testing by adding 12+DC to pin 16 and ground pin 4/5 and see if it passes the test interface stage. Im not sure if its would require small voltage to pin 7. I dont want to modify the interface until I know it works correctly on pin 7. I suppose ill have to wait until I can get round to my mum and dads and test it on either the Ugly bug or the Polo

I read the fault codes on my new ELM327, showing it off to a friend who needed their codes looked at, it worked just fine on the multiecuscan software, worked without a hitch, I can't remember if its a 00 or 01 though, so my guess is to just give it a go.

You should find the socket just under the steering wheel there is a little cover to just take off with a flat head.

Hope this helps, I'm sure the ~£10 you spend on a cable wouldn't really go to waste, you can still use it on newer cars :-D



EDIT: Sorry I should of mentioned (during all my ramblings) that it was a 1.9 JTD Multipla, but yeah, can't remember the year. Also check your leads they may be dying, sounds like that is the only thing that hasn't been replaced

Cheers for the input guys. Im confident that if the interface works that it will connect with the ECU and hopefully show me a code or 2. Ill probly clear any codes first and see what comes back. Im sure there will be some old codes stored when when the coilpack was cracked and the leads were arcing.

If the lead doesnt work at all then its not the end of the world. £6 down the drain. I spend more than that on a mcdonalds breaky and im sure i can use parts from inside it for future projects/interface repairs.

The lead works perfect on the VW polo so ive just modified it to work with pins 1,3,7 & 9 on the fiat.

Ill update the thread once ive read the fault codes.

Ive just tried to read the fault codes from the bug and it wont connect with the ECU on pin 7. Ive connected to the ABS and Airbag without issue. Ive tested the interface on another car and it connects to the ECU without issue so the problems with the bug rather than the interface.

Any idea's

Im just wondering if its a software issue as i was using MultiECUscan1.2r. Ive managed to get a copy of fiatECUscan1.6 and its saying that the engine management system is experimental. See screenshot. So maybe i need to scan it again using this software instead of mutliecuscan1.2r.

marks152 said:

Ive just tried to read the fault codes from the bug and it wont connect with the ECU on pin 7. Ive connected to the ABS and Airbag without issue. Ive tested the interface on another car and it connects to the ECU without issue so the problems with the bug rather than the interface.

Any idea's

Im just wondering if its a software issue as i was using MultiECUscan1.2r. Ive managed to get a copy of fiatECUscan1.6 and its saying that the engine management system is experimental. See screenshot. So maybe i need to scan it again using this software instead of mutliecuscan1.2r.

Click to expand...

Hi Marks,

Any update on this yet? Symptoms seem similar to my wife's 2000/W 1.6 (including historic gearbox issue). At the moment I have a warning light and cylinder 4 does not seem to be firing. This started with a misfire and the light coming on, at which time I determined that cylinders 2 and 4 were contributing less to the action than 1 and 3 and that 4 was the weakest. I replaced the plug to no effect and the coil to little.
Earlier this week I tried swapping the battery and this cleared the fault and the light. I took the battery to Halfords and they diagnosed two bad cells. I fitted the new one and the car was much better for a couple of days.
My son got a Bluetooth OBD2 reader for Christmas that works on his 02/Y Punto, but isn't giving any reading on the Multi. I'm going to try it in my 156 later, but that's even older, so I'm not confident.
I'm using the Torque Pro Android application. The device has a led to indicate that it is picking up power.

Any ideas on the fault and why the battery should have contributed? I'm wondering whether it's a bad connection that was exacerbated by low voltage from the battery, or the battery drawing too much current trying to charge.

Any ideas on the device?

T14086 said:

if there was a worn or dirty section on the TPS track you would feel it at the same throttle opening however as you say you can check this with a multimeter but it may be easier to do at the sensor itself as it's easy to get access.

Might be worth putting some fuel treatment through it and give it a good blast if it has been sitting for 2 years however as you say the fault was there previous. Have you checked the lambda sensor, done a few of these on the 1.6 engine.

Click to expand...

Where is tps sensor located

on throttle body

Just got one from d.a motors 25 quid gonna fit it later does it have to be torque tight ? If so how tight and by all accounts its built in to the body and u can't actually remove it