Tizzywizzy1uk said:

Yeah, done all this and more.. still stuck. I’ll look it all over again tomorrow

Click to expand...

is it seen by device manager

does it have a yellow exclamation mark

Laptop and computer won’t register the cable at all

screenshot of the device manager might help


is it hiding in the USB tab


I take it we are talking about the USB type cable and not a Bluetooth or wireless type

The cable type. I got in touch with the seller and he said it sounds like a driver problem. I’m still waiting for a response

Meanwhile I borrowed my sons panda, swapped the key barrel, ecu and body ecu and the abs light still came on.
I put my components onto the other panda and everything worked fine, no abs lamp.
So at least the ecu is good.
I’ll check the sensors on the other panda tomorrow and compare them.

Tizzywizzy1uk said:

Because the vehicle is no longer registering any fault codes, would a Multiecuscan find the problem?

Click to expand...

It seems you've been swapping bits and not really looked at the cause of the problem.

The U error codes you say it showed have nothing to do with the ABS they are network errors, may have been wating on the ECU for years to be cleared, the fact that they have not come back means they are not a problem u1600 is a key issue u500 should not exist as it does not have 4 numbers. The thing is it looks like you have been reading the engine ECU and not the ABS ecu.

You will need a program like MultiECUScan to connect to the ABS ECU to see what fault codes that module is recording. If the ABS light is on then the ABS unit will be recording its own errors.

You could well find you've been swapping wheel sensors and there is nothing wrong with them and the ABS ECU has recorded some intermittant fault that needs clearing, or you have a broken wire up from the wheel sensor, who knows but the only way to tell for sure is to get it plugged in and read the ABS errors.

I’ve got some drivers to download for the Multiecuscan tomorrow and check

Have a look at this thread:
https://www.fiatforum.com/panda/352156-fiatecuscan.html
Particularly post #5 . Follow the instructions carefully to set up the computer to talk to MES.
It took me a long time to get it working initially, some time ago now, but since using that sequence it is reliable every time.
(Does need the drivers installed and working of course)

It really is time that MES was made to run on Apple MacOS. It's more work for the developer, because Apple wont let them supply stuff that wont work without a degree in computer science.

There is however the rented version that runs on iPhone iOS, but MES website is not clear if that version has the full function set.

Finally got this sorted... the brand new elm 327 cable turned out to be faulty, the seller sent me a replacement and I plugged it in and it worked straight away.
Fault was rear right sensor. It already had new sensor and I changed the hub for the new one I’d put on the left and still had fault. I tried continuity from rear sensor cable to the abs unit and it showed that both wires were touching. I removed the trim inside the rear seats area and pulled the wire up. Their was an airline crack in it so I fixed the wires and voila.. abs is working.
I did try the sensor test with and without spinning the wheel on the other panda and it showed no reading as well. I think these sensors are different than all the internet blogs and YouTube folks have been saying.could anyone shine a light on this querie?
Thanks for all the assistance and yes multiecuscan would have saved a lot of time and money in the long run.

The sensor pickups look the same as ones I had on a Renault Espace. So I guess Renault use the same sticky-back-plastic mag strip on the bearing seal.

The Renault fault code tells you if it's bearing or sensor -
Fiat will be similar.