Technical Howto reset abs and brake light on a 06 panda dynamic
Currently reading:
Technical Howto reset abs and brake light on a 06 panda dynamic
Hi.
Do you man swirching off the Warning:Error light on dashboard?
Best way is to plug into the OBD Port..
Read the Error Report.
Check the fault is now fixed
Clear the Error from ECU: body computer
The light should then go off.
If you SEARCH the error code on here.. you will get a better understanding of the situation.
Charlie
- Joined
- Sep 14, 2009
- Messages
- 19,492
- Points
- 3,294
ABS warning lights don't just happen. You need to find the problem and correct it.
See https://www.multiecuscan.net/
You will need an OBD connection cable and windows laptop. The basic version is free but the full version (adequate for personal use) is about £50.
See https://www.multiecuscan.net/
You will need an OBD connection cable and windows laptop. The basic version is free but the full version (adequate for personal use) is about £50.
Of what?
The warning light tells you you still have a fault, which you need to remedy if you want the light to go out. They don't 'latch' on.
For your own safety get it fixed as it's likely the EBD won't be working as well.
For your own safety get it fixed as it's likely the EBD won't be working as well.
Last edited:
I found the fault code will still be stored until cleared, but the lamp will go off if the fault doesn't recur.
Thanks for clarifying.
Only ABS issue I have had..
Blown fuse.. punto sporting.
The Forum saved me A LOT of grief
Only ABS issue I have had..
Blown fuse.. punto sporting.
The Forum saved me A LOT of grief
- Joined
- Sep 14, 2009
- Messages
- 19,492
- Points
- 3,294
On my Punto the airbag light came on when the under seat connection failed. Connection fixed, no more warning light, but the code was recorded in the ECU.
ABS will be the same, but there are so many more things to raise faults and be logged in the ECU. Unless you want to replace stuff on trial and error (at great expense) you need to know what the fault is. Simply ignoring it is a bad idea.
(1) Cars these days have such poor brake pedal feel, you will be locked up and spinning off the road before you know it.
(2) The insurance might have some uncomfortable questions about why the car was in use with faulty brakes.
The above advice is all good stuff. If you've had a dashboard warning light illuminated you're going to have a DTC (diagnostic trouble code) stored. You need to read it with a code reader or scanner. In my humble opinion you won't get better (for home use) than the Multiecuscan package.
I splashed out on the multiplexed version of Multiecuscan (MES). It was not cheap but I find it very handy because you can do a whole vehicle scan - all systems - in one go and very quickly. It's my standard starting point each time I service the cars. Once I know what the ECU thinks is the problem - if there is one - I find the solution, very broadly, falls into two courses of action. If it's a sensor or actuator type thing then it's usually sortable without too much hassle. - notice I don't say cheaply - (although you have to remember that the ECU is only telling you that something is not as it's expecting it to be. If, like MES, your device then makes predictions to help you, just remember they are only suggestions. It may say an ABS sensor is not providing a signal. Just remember it's as likely to be a connector with internally corroded pins or a broken wire as the sensor itself! You need to really think about the whole system. On the other hand you may get an error reporting an actual ECU itself. Although not common (in my experience ECU's are pretty reliable) I've had this on both my SEAT/Skoda cars (for which I use VCDS) and The Fiats (Multiecuscan). The first time I serviced the Punto it showed up an ABS ECU module fault and Becky, the Panda, showed U1703 instrument cluster control unit and U1700 Body comp control unit. Those U codes frightened me, never seen them before! Neither car was bought from a Fiat organisation and I suspect neither had been scanned in ages. Becky had four other DTC's stored! In these situations there is nothing I can do to check out an actual ECU so removing it and sending it away to a specialist is my only option. But, as mentioned above, you need to eliminate the connected ancillaries first. So, carefully, remove all related plugs and connections and inspect for damaged pins and corrosion then reconnect them. Just unplugging and reconnecting is often enough to reestablish a dodgy pathway. I also like to spray lightly with switch/contact cleaner (NOT something like WD40!) and, again with care, plug and unplug the connector a few times to "wipe" the touching contact surfaces then a light smear of Contralube 770 will keep it protected. Then fire every thing up, clear the fault codes - I always keep a copy for reference, and go for a wee drive. recheck and see if the faults have come back. So far I've never actually had to send an ECU away because the codes have always gone away after doing the above!
I splashed out on the multiplexed version of Multiecuscan (MES). It was not cheap but I find it very handy because you can do a whole vehicle scan - all systems - in one go and very quickly. It's my standard starting point each time I service the cars. Once I know what the ECU thinks is the problem - if there is one - I find the solution, very broadly, falls into two courses of action. If it's a sensor or actuator type thing then it's usually sortable without too much hassle. - notice I don't say cheaply - (although you have to remember that the ECU is only telling you that something is not as it's expecting it to be. If, like MES, your device then makes predictions to help you, just remember they are only suggestions. It may say an ABS sensor is not providing a signal. Just remember it's as likely to be a connector with internally corroded pins or a broken wire as the sensor itself! You need to really think about the whole system. On the other hand you may get an error reporting an actual ECU itself. Although not common (in my experience ECU's are pretty reliable) I've had this on both my SEAT/Skoda cars (for which I use VCDS) and The Fiats (Multiecuscan). The first time I serviced the Punto it showed up an ABS ECU module fault and Becky, the Panda, showed U1703 instrument cluster control unit and U1700 Body comp control unit. Those U codes frightened me, never seen them before! Neither car was bought from a Fiat organisation and I suspect neither had been scanned in ages. Becky had four other DTC's stored! In these situations there is nothing I can do to check out an actual ECU so removing it and sending it away to a specialist is my only option. But, as mentioned above, you need to eliminate the connected ancillaries first. So, carefully, remove all related plugs and connections and inspect for damaged pins and corrosion then reconnect them. Just unplugging and reconnecting is often enough to reestablish a dodgy pathway. I also like to spray lightly with switch/contact cleaner (NOT something like WD40!) and, again with care, plug and unplug the connector a few times to "wipe" the touching contact surfaces then a light smear of Contralube 770 will keep it protected. Then fire every thing up, clear the fault codes - I always keep a copy for reference, and go for a wee drive. recheck and see if the faults have come back. So far I've never actually had to send an ECU away because the codes have always gone away after doing the above!
- Joined
- Sep 14, 2009
- Messages
- 19,492
- Points
- 3,294
I was impressed when the Renault Espace had an ABS light. The code told me Sensor fault right front. Sure enough the sensor cable was damaged. Had it been the magnetic ring the code would have been different e.g. ABS No signal right front.
Pretty good TBH.
But some things can give very strange error messages because the ECU has responded to erroneous or out of range inputs. Weak batteries can throw up all sorts of rubbish. My favourite was a VW TDI 1.9 where the technician swore blind the EGR valve had failed when the real problem was a blown turbo hose.
Pretty good TBH.
But some things can give very strange error messages because the ECU has responded to erroneous or out of range inputs. Weak batteries can throw up all sorts of rubbish. My favourite was a VW TDI 1.9 where the technician swore blind the EGR valve had failed when the real problem was a blown turbo hose.
Ok.. different to my experience.
I damaged to wiring to airbag isolator switch.. I broke the plug.. so took no diagnosing
Replaced plug.. but light remained. Thats when I bought my MES.. due to buy another .. as there is a whole new build generation of FIATs it cannot communicate with
- Joined
- Sep 14, 2009
- Messages
- 19,492
- Points
- 3,294
