Had a problem with seat belt light staying on with my Seicento so thought that if I covered up the LCD it would take away the aggravation.
So, I removed the instrument panel and covered up the small tunnel that the LCD shines down - this works.

However, now I have a new problem - lost all mileage information and clock no longer shows.

How can I fix this ?

Many thanks for any information.

hi have you plugged the electrical plugs back in properly ?

paul

definatly sounds like a loose connection

Thanks for your quick reply. Have checked and rechecked the plug ins, wiggled the wires ( such that you can ) and nothing. The actual screen display for the mileage and time does light up and all other of the usual lights come on when the ignition key is turned and they go out when engine is started. Have tried pressing the clock time adjuster on the left side but this does nothing.

Any other ideas ?

im guessing then this is a mk2 sei and its all ran off the ecu so its probably a thing you need to go to fiat for... however try unplugging the battery for 15 mins and see what happens when you plug it back in

Thanks - will try that. I had to put a new ECU on last August as it was mis-firing, but that was quite straight forward and car immediately ran perfectly. The car is a Seicento Sporting 1108cc - first registered May 2001

Disconnecting the battery didn't help. Just drove the car for a few miles to see if the mileage and clock came on but no luck. Where would the memory chip for mileage/clock be ? I don't suppose it can be in the ECU as the one I put on last August was brand new and it obvioulsy picked up the mileage info. from somewhere.

Any more ideas. Thanks

I've got 3 sets of clocks for my mk2 and they all show different mileage if I connect them to my car so the chip has to be in the clocks. Have you checked all the little pins in the plugs? All it could take is 1 pin to be slightly not seated right.
Where about are ya? Could try a spare set of clocks, see if the problems in your clocks or somewhere else.

Thanks everyone for your help. Turned out to be a connection on the mother board - didn't put it back together tight enough.