Peter Carmichael Posted January 22, 2007 Share Posted January 22, 2007 This will win prizes for the most specialised question of the day... I have access to a Rover T4 test book system. It wants to know a VIN in order to run the correct diagnostics/ECU comms program. We're not going to get anywhere (obviously) with a Caterham VIN. What VIN and what MG model is equivalent for to the various Caterham installations. In particular, I have a 2002 model year VVC that I want to hack/check. In Rover T4 terms, is this equivalent to an MGF? I'm also harvesting VINs, so if anyone has a recent (>2000 model year) MG or Rover running a K-series, can you please blatmail me details of the car model and specification along with the VIN. TIA Link to comment Share on other sites More sharing options...
Rob Walker Posted January 22, 2007 Share Posted January 22, 2007 Peter, I think the vin number is visible through a gap in the black masking through the front windscreen near side. So a walk around your nrearest car park or supermarket should get the number. Rob Link to comment Share on other sites More sharing options...
Peter Carmichael Posted January 22, 2007 Author Share Posted January 22, 2007 Thanks for that Rob, but I think I'll have to "walk around a car park by proxy". The car parks near me don't have many MG-Rovers in them, on account of my current location Link to comment Share on other sites More sharing options...
MartinWoodham Posted January 22, 2007 Share Posted January 22, 2007 😬 😬 😬 😬 Martin Aero'd Roadsports B with a garage slowly filling up with upgrade parts Link to comment Share on other sites More sharing options...
rj Posted January 22, 2007 Share Posted January 22, 2007 Errr... I thought Rover had been sold to the Chinese?? /regin Link to comment Share on other sites More sharing options...
Frying Pan Posted January 22, 2007 Share Posted January 22, 2007 Peter I was involved in the original design of TestBook (on the hardware side) for Rover and Land Rover, and then managed the Land Rover side of things post BMW sell-off for a while. In our implementation, the VIN entry screen didn't do anything useful, and could be ignored (I suspect this is the same for MG Rover as well). On some vehicles, we read the VIN electronically (stored in a number of modules on the vehicle) if we need it. What are you actually trying to do? Expect to see masses of fault codes stored, as there are lots of things the ECU would normally expect to see that aren't fitted (Air con etc.). Some MEMS are flashable, but the low volumes and exclusivity (just about the only in-house developed EMS) mean that the aftermarket tuners have never really bothered to reverse engineer and create bespoke maps. Guy See some pictures of the build here. 11000 miles completed! Edited by - 7heavensoon on 22 Jan 2007 14:52:45 Link to comment Share on other sites More sharing options...
Peter Carmichael Posted January 22, 2007 Author Share Posted January 22, 2007 I was involved in the original design of TestBook (on the hardware side) for Rover and Land Rover, and then managed the Land Rover side of things post BMW sell-off for a while. In our implementation, the VIN entry screen didn't do anything useful, and could be ignored (I suspect this is the same for MG Rover as well). On the implementation I have, it determinese the diagnostics modules that are presented to the user, such as MEMS3/ABS/AIRCON. However, it won't accept an invalid VIN. Rumour has it that it also presents the options for re-flashing the ECU based on VIN selection, but I think it is possible to avoid re-programming an ECU unnecessarily. What are you actually trying to do? On a limited time basis, I am trying to get a VVC Caterham to have "as good emissions as possible" and "conform to EU3 specification as much as possible". Mostly this involves basic things such as fixing leaks in the collector, re-siting the lambda sensor to the collector and fitting a post-catalyst HEGO/lambda sensor. I have this TestBook capability and if I can see that the ECU is reacting inappropriately to its "out of calibration" installation I can maybe arrange to correct some aspect of the physical installation to mitigate this. Expect to see masses of fault codes stored, Basic EOBD reports two fault codes related to the non-fitment as standard of the post-cat lambda sensor. Some MEMS are flashable, but the low volumes and exclusivity (just about the only in-house developed EMS) mean that the aftermarket tuners have never really bothered to reverse engineer and create bespoke maps. I'm not expecting the programmability of an after-market ECU, but I am hoping to get a better idea of the inputs that the ECU is using. Given the above, am I on the right track by seeking a MG/Rover VIN code? Link to comment Share on other sites More sharing options...
Frying Pan Posted January 22, 2007 Share Posted January 22, 2007 I think it is possible to avoid re-programming an ECU unnecessarily - Yes, there is plenty of opportunities to back out before commnecing a download. Basic EOBD reports two fault codes related to the non-fitment as standard of the post-cat lambda sensor. - Sounds about right. EOBD is only interested in emissions related issues, not whether the AC clutch drive is open circuit. Given the above, am I on the right track by seeking a MG/Rover VIN code?I guess so. Can you blatmail your e-mail address - I may be able to send you some generic MEMS info Guy See some pictures of the build here. 11000 miles completed! Link to comment Share on other sites More sharing options...
Frying Pan Posted January 22, 2007 Share Posted January 22, 2007 Peter YHM Guy See some pictures of the build here. 11000 miles completed! Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now