corsasport.co.uk
  Not logged in [Login - Register]  
You Are Not Registered Or Not Logged In  

Corsa Sport » Message Board » General Chat » Question for a friend


New Topic
New Poll 		  Subscribe | Add to Favourites

You are not logged in and may not post or reply to messages. Please log in or create a new account or mail us about fixing an existing one - register@corsasport.co.uk

There are also many more features available when you are logged in such as private messages, buddy list, location services, post search and more.


Author Question for a friend
Mistamist
Member
Registered: 16th Jul 03
Location: Gillingham, Kent
User status: Offline
14th Mar 04 at 21:33   View User's Profile U2U Member Reply With Quote
My mate is putting a new engine in his veccy, its a 1.6 8v at the moment, and he is just changing it for a newer one with less miles.

What he wants to know is: THe current milage on the dash is 132k odd, the new engine had done 50k, it has a digital odometer, is the data stored in the clocks itself or the ECU?

If its in the clocks i take its just a basic swap of clocks needed to get the true milage of the engine.

If its in the ecu can he use the ecu from the donor car?
Adam-D
Member
Registered: 11th May 02
Location: Cheshire
User status: Offline
14th Mar 04 at 21:38   View User's Profile U2U Member Reply With Quote
milage is on the car not the engine
Mistamist
Member
Registered: 16th Jul 03
Location: Gillingham, Kent
User status: Offline
14th Mar 04 at 21:46   View User's Profile U2U Member Reply With Quote
thats what i told him, but he wants it showing the milage of the engine, i dunno bout the legalities of this but who cares its not my car
M4tt
Member
Registered: 18th Apr 03
Location: Potters Bar
User status: Offline
14th Mar 04 at 21:56   View User's Profile U2U Member Reply With Quote
its not legal, i bet he wou;dn't want to change the milage on clocks if the new engine had more miles on than the previous.

 
New Topic
New Poll

Corsa Sport » Message Board » General Chat » Question for a friend 23 database queries in 0.0076230 seconds