Wont idle. No fault codes!

All your other probs if any.
SteveP
Posts: 10
Joined: Sun Mar 23, 2014 6:57 pm
Location: Sunny Slough........... Even seagulls don't fly over here

Re: Wont idle. No fault codes!

Post by SteveP »

Ok update time.

Have had the car at a reputable mechanics. Wiring tested and seems ok. No faults being thrown up. Ecu off and tested. All working ok. All the garage can think now is its a faulty throttle body but its not showing on code reader.. I haven't the money to replace this if it isnt faulty. Does anyone have a 206 1.6l from 2003 or later that would kindly let me try the item. It is a 2 minute job and cannot harm the item at all. This would then show if it is this part. As a single dad I just cannot afford to throw any more money on parts that might not need replacing? Also would a software update show up on an ECU test? Could this be a possibility? Anyone know where i can get one done other than main stealer?

Thanks guys,

Steve

User avatar
gazza82
Posts: 2129
Joined: Sat Apr 23, 2011 8:41 pm
Location: Buckinghamshire, UK

Re: Wont idle. No fault codes!

Post by gazza82 »

Are they sure their reader is compatible? Peugeot's are funny with these and not all generic ones work. One way is to disconnect something and test it shows up an error .. if it doesn't then I wouldn't trust the code reader being used.

Being a 2003 petrol it SHOULD be EOBD compatible ... so newer code readers should be OK ... but it's never definite. We've had one on here recently showing up a cam sensor code when there isn't a cam sensor fitted! :facepalm:
Family Fleet: ex-Cayman Green 206 CC 2.0 LE, Indigo Blue 206 1.4 HDi Hatchback, Subaru BRZ Auto, Alfa Romeo MiTo

SteveP
Posts: 10
Joined: Sun Mar 23, 2014 6:57 pm
Location: Sunny Slough........... Even seagulls don't fly over here

Re: Wont idle. No fault codes!

Post by SteveP »

It's a Snap On live reader I believe! The first mechanic I tried couldn't read it but these other guys were recommended and read all the fault codes first. They've fixed them but still can't find this fault :-(