Jump to content
Click here if you are having website access problems ×

MEMS3 Mapper - Full Support Added for All (Earlier) Rover MEMS ECU Families


revilla

Recommended Posts

Anyone with a pre-MEMS3 K Series Caterham (EU1 or EU2) can now use all of the live diagnostic, live data, live dashboard, fault code, immobiliser pairing and service adjustment features in MEMS3 Mapper. I've add the protocols and setups all of the previous MEMS versions (MEMS2J EU2 VVC still in progress, will be released shortly). All free, other than for the cost of a cheap cable, as always. Here's the page I just posted on my own website ...

Full Support Added for All Rover MEMS ECU Families

Download Link: https://andrewrevill.co.uk/Downloads/MEMS3Tools.zip

As of Version 7.87, MEMS3 Mapper now fully supports all Rover MEMS ECU Families including 1.2 / 1.3 / 1.6 / 1.6 / 2J / 3 / EU4.

Having recently used some other tools when helping people with issues on MEMS 1.9 EU2 cars, and having found them somewhat frustrating and expensive, I decided to add support for all of the earlier families of the Rover MEMS ECU into MEMS3 Mapper. These include the ECUs used on EU2 and earlier Caterhams, SPI Minis etc. (the full range of MEMS3 ECUs for both petrol and diesel were already fully supported). This turns “MEMS3 Mapper” into a true one-stop-shop for all Rover ECU support and maintenance tasks. The earlier ECUs are not OBDII compliant and some of them need a slightly different cable (a 3-pin ROSCO diagnostic cable) but these are also readily available. The earlier ECUs mostly use a different communications protocol (ROSCO “Rover Service Communications” instead of a variant of KWP2000) so all of the ECU interface had to be developed from scratch, but could be integrated into the existing user interface framework. The earlier ECUs are not remappable, however most of the diagnostic capabilities of MEMS3 Mapper can still be used with them and they all support a range of maintenance operations including immobiliser pairing and service adjustments. MEMS3 Mapper fully supports the capabilities provided by each ECU family.

I owe a big “thank you” to James Portman at rovermems.com. James had already done most of the research one the earlier ECUs and had developed some online diagnostic tools for them. He shared all of this with me and actively encouraged and supported my endeavours in this.

ECU Families Now Supported

·         Rover MEMS 1.2 - Used mainly on very early SPI cars without catalytic converters around 1991.

·         Rover MEMS 1.3 - Used mainly on early SPI cars from about 1992 to 1993.

·         Rover MEMS 1.6 - Used mainly on cars with Rover K-Series SPI and some early MPI engines.

·         (Caterham EU2 MPI) Rover MEMS 1.9 MKC EU2 MPI - Used on cars with Rover K-Series EU2 MPI engines.

·         (Caterham EU2 VVC) Rover MEMS 2J MKC EU2 VVC - Used on cars with Rover K-Series EU2 VVC engines and MPI Minis.

·         (Caterham EU3 MPI) Rover/Motorola MEMS3 NNN EU3 MPI with Lucas 5AS / Pektron - Used on cars with Rover K-Series MPI engines from about 2001 onward.

·         Rover/Motorola MEMS3 NNN EU3 MPI with BMW EWS 3.D - Used on Rover 75 / MGZT and Freelander cars with Rover K-Series MPI engines from about 2001 onward.

·         (Caterham EU3 VVC) Rover/Motorola MEMS3 NNN EU3 VVC with Lucas 5AS / Pektron - Used on cars with Rover K-Series VVC engines from about 2001 onward.

·         Rover/Motorola MEMS3 NNX XFW - Extended Firmware custom configuration introduced and supported by MEMS3 Mapper.

·         Rover/Continental MEMS3 NNN EU4 - Used on cars with NAC N-Series engines such as the MG TF LE500.

·         Land Rover/Lucas MEMS3 MSB 10P EU2 - Used mainly on Land Rover Discovery and Defender Td5 cars with the earlier 10P engine from around 1998 to 2002.

·         Land Rover/Lucas MEMS3 NNN 15P EU3 - Used mainly on Land Rover Discovery and Defender Td5 cars with the later 15P engine from around 2002 to 2004.

 

       image018.pngimage020.pngimage022.png

image024.pngimage028.pngimage034.png

image036.pngimage038.pngimage040.png

Diagostic Cables Required

·         MEMS 1.2, 1,3 and 1.6 ECUs normally use a 3-pin ROSCO (Rover Service Communications) cable.


image041.jpg image042.png

These can be purchased here https://shop.jmpe.co.uk/products/rover-3-pin-ecu-diagnostic-connector. Other suppliers may be available online but this cable is tested and known to be working with these ECUs. Rover vehicles will have a corresponding diagnostic connector to plug this into, probably in the engine bay. Non-Rover vehicles may not be fitted with the connector, in which case you will need to wire this cable to the ECU yourself:
 

o   Pin 1 – Signal Ground – ECU Pin 14

o   Pin 2 – ECU Data Out to PC Data In – ECU Pin 10

o   Pin 3 – PC Data Out to ECU Data In – ECU Pin 15
 

·         All other MEMS families normally use a VAG COM KKL 409.1 style OBDII cable.

image043.jpg

These can be found all over the web and on sites such as eBay but I’d recommend this one: https://shop.jmpe.co.uk/products/rover-16-pin-ecu-diagnostic-cable as it is tested and known to be working with these ECUs.

Key Capabilities by ECU Family

Rover MEMS 1.2

·         ROSCO Protocol.

·         3-Pin UART ROSCO Diagnostic Cable.

·         Reading and Saving of Full ROM (Firmware and Map).

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

Rover MEMS 1.3

·         ROSCO Protocol.

·         3-Pin UART ROSCO Diagnostic Cable.

·         Reading and Saving of Full ROM (Firmware and Map).

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

Rover MEMS 1.6

·         ROSCO Protocol.

·         3-Pin UART ROSCO Diagnostic Cable.

·         Reading and Saving of Full ROM (Firmware and Map).

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

Rover MEMS 1.9 EU2 MKC EU2 MPI

·         ROSCO Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading and Saving of Full ROM (Firmware and Map).

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

Rover MEMS 2J MKC EU2 VVC

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading and Viewing of Map.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

Rover/Motorola MEMS3 NNN EU3 MPI with Lucas 5AS / Pektron

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading, Writing, Editing and Viewing of Firmware, Coding and Map.

·         Custom Firmware Patches.

o   Dual Map, Live Switching.

o   Live Mapping.

o   Debugging.

o   CAN Bus Logging.

o   CAN Bus Sniffing.

·         Map and Firmware Wizards.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Freeze Frames.

o   Live Dashboard.

·         VIN and ZCS Coding.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

·         Comprehensive ECU Maintenance Tools.

Rover/Motorola MEMS3 NNN EU3 MPI with BMW EWS 3.D

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading, Writing, Editing and Viewing of Firmware, Coding and Map.

·         Custom Firmware Patches.

o   Dual Map, Live Switching.

o   Live Mapping.

o   Debugging.

o   CAN Bus Logging.

o   CAN Bus Sniffing.

·         Map and Firmware Wizards.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Freeze Frames.

o   Live Dashboard.

·         Clear Adaptations.

·         Service Adjustments.

·         Comprehensive ECU Maintenance Tools.

Rover/Motorola MEMS3 NNN EU3 VVC with Lucas 5AS / Pektron

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading, Writing, Editing and Viewing of Firmware, Coding and Map.

·         Custom Firmware Patches.

o   Dual Map, Live Switching.

o   Live Mapping.

o   Debugging.

o   CAN Bus Logging.

o   CAN Bus Sniffing.

·         Map and Firmware Wizards.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Freeze Frames.

o   Live Dashboard.

·         VIN and ZCS Coding.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

·         Comprehensive ECU Maintenance Tools.

Rover/Motorola MEMS3 NNX XFW

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading, Writing, Editing and Viewing of Firmware, Coding and Map.

·         Custom Firmware Patches.

o   Dual Map, Live Switching.

o   Live Mapping.

o   Debugging.

o   CAN Bus Logging.

o   CAN Bus Sniffing.

·         Map and Firmware Wizards.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Freeze Frames.

o   Live Dashboard.

·         VIN and ZCS Coding.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

·         Comprehensive ECU Maintenance Tools.

Rover/Continental MEMS3 NNN EU4

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading, Writing, Editing and Viewing of Firmware and Map.

·         Custom Firmware Patches.

o   Dual Map, Live Switching.

o   Live Mapping.

o   Debugging.

o   CAN Bus Logging.

o   CAN Bus Sniffing.

·         Map and Firmware Wizards.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Freeze Frames.

o   Live Dashboard.

·         VIN and ZCS Coding.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

·         Comprehensive ECU Maintenance Tools.

Land Rover/Lucas MEMS3 MSB 10P EU2

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading and Viewing of Map.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

Land Rover/Lucas MEMS3 NNN 15P EU3

·         Rover/BMW Protocol.

·         KWP2000 Protocol.

·         OBDII-Style K-Line Diagnostic Cable.

·         Reading, Writing, Editing and Viewing of Firmware, Coding and Map.

·         Custom Firmware Patches.

o   Dual Map, Live Switching.

o   CAN Bus Logging.

·         Map and Firmware Wizards.

·         Live Diagnostics

o   Live Data.

o   Live Fault Codes.

o   Live Dashboard.

·         VIN and ZCS Coding.

·         Immobiliser Pairing & Status.

·         Clear Adaptations.

·         Service Adjustments.

·         Comprehensive ECU Maintenance Tools.

 

 

Edited by revilla
  • Like 5
Link to comment
Share on other sites

For MEMS3, you can distinguish a SuperSport ECU by looking at the VE table (basically a model of the air flow into the engine). The SuperSport curve (surface) is a very different shape because of the different engine breathing. There are plenty of examples of SuperSport maps in the library on my website so it's easy to compare an unknown with a couple of those and see which it looks like. Even if remapped by Kmaps it won't be that far different that you wouldn't recognise it.

For MEMS1.9 my tool doesn't give you the ability to display the map visually as the table structure is just so different to MEMS3 (I may add something that converts them just for display purposes at some point). But it does let you read the map (full ROM) data and save it to a file and I have got a little table extractor program I wrote that will find the tables in there and then you can graph them in Excel. The resolution of the tables is a lot lower (byte not word) but other than for rounding errors, the EU2 and EU3 SuperSport VE tables are identical.

That will confirm whether you have a SuperSport map or not. To confirm whether you have SuperSport cams is then easy - because a SuperSport engine on a regular map or a regular engine on a  SuperSport map will run with the mixture so far wrong it's pretty obvious (I've had to diagnose a couple of where that was the problem and they really weren't happy). So if it runs nicely, then cams match the map.

In terms of Miker7's thread ... I was sitting in a pub with him last week with ECUs out on the table. I really know how to enjoy myself LOL. I have a copy of his map, I'll try to post a comparison up on here in a bit to show what it is.

Link to comment
Share on other sites

Examples below of Miker7's VE table, a stock 1600 SuperSport VE table and a stock 1600 RoadSport VE table. I've spun them round so you can see the shape of the edge that corresponds to the RPM range at full MAP. This gives a pretty good idea of the shape of the torque curve of the engine. As you can see, the RoadSport starts to roll off at higher RPM where the SuperSport continues to climb, as expected.

From this Miker7's is clearly a 1600 SuperSport ECU (the engine capacity scalar used in the air flow calcualtions is set to 1588cc). It's slightly different to the stock SuperSport because it's been remapped, but it's the same basic shape and quite different to the RoadSport.

Miker7's VE Table:

image.png.ba35c51115c522d65ef0892437c50f4c.png

Example of a Stock 1600 SuperSport VE Table:

image.png.c671bcab24f9485c3073fd104ba4a9af.png

Example of Stock 1600 RoadSport VE Table:

image.png.cfed19fc5ec388210f109b490284c4fb.png

Link to comment
Share on other sites

18 hours ago, revilla said:

In terms of Miker7's thread ... I was sitting in a pub with him last week with ECUs out on the table. I really know how to enjoy myself LOL. I have a copy of his map, I'll try to post a comparison up on here in a bit to show what it is.

And thats not a euphemism before any bright spark comments  - and yes, we really are the life and sole of the party.

I'll comment about my SuperSport conundrum on my thread to stop taking up this one.

Link to comment
Share on other sites

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 account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...