Hi all,

Well, my Abarth has been running really well lately and I'm loving it Only a couple of niggles that I'm going to get sorted out at some time... not massively serious but on the list to for the future...

1) An annoying squeek which I think is the air-con belt automatic tensioner appears when the engine warms up.
2) The Selespeed clutch control when cold isn't the best but certainly not as bad as other Selespeed owners report with their kangarooing. I'm thinking a Selespeed re-learn on Examiner should sort it as the clutch is probably just halfway through it's life at 45k miles and needs to find it's biting point again.
3) Wheels desperately need a re-furb... been quoted £250 for all four wheels with a total shot blast and re-paint in either anthracite or the original shadow silver... can't decide on which yet

I bought an OBD2 CAN reader the other day to keep an eye on the health of the car and I've noticed that I've got a U1601 error which I cleared and then re-appeared as a pending fault. Apparently this is a "CAN Line Error".

My question is... what does this mean? How serious is it? And what do we think it could be?

Cheers guys!

Greggers said:

I bought an OBD2 CAN reader the other day to keep an eye on the health of the car and I've noticed that I've got a U1601 error which I cleared and then re-appeared as a pending fault. Apparently this is a "CAN Line Error".

My question is... what does this mean? How serious is it? And what do we think it could be?

Click to expand...

Almost certain thats a key problem (recognition) if your having no problems I'd be inclined (at present) to ignore it.

T14086 said:

Almost certain thats a key problem (recognition) if your having no problems I'd be inclined (at present) to ignore it.

Click to expand...

Cheers T for the speedy reply, matey!

Right, well the key that I'm using isn't an original for the car, it's one i got off ebay to replace my knackered old key. I swapped out the blade and RFID from one to the other and all seems to work fine, so can't think why the error should occur.

Maybe I'll try turning the RFID around to see if it makes any difference... not that it should...