Loading AI tools
Electronic control system for Rover car engines From Wikipedia, the free encyclopedia
The Modular Engine Management System, or MEMS, is an electronic control system used on engines in passenger cars built by Rover Group in the 1990s. As its name implies, it was adaptable for a variety of engine management demands, including electronically controlled carburetion as well as single- and multi-point fuel injection (both with and without electronic ignition control). The abbreviations "SPi" and "MPi" refer to the single-point and multi-point injection configurations, respectively.[1]
MEMS 1.6 units, one with its cover removed | |
| Manufacturer | Rover Group / Motorola |
|---|---|
| Type | Electronic automobile engine management |
| Release date | 1989 |
In 1985, Rover Group made the decision to develop a new electronic engine management system in-house, and from its inception, the system was intended to be flexible enough for use with future engine designs. It was also intended to improve quality and reliability and to consume less power and occupy less underbonnet space than previous engine management systems.[2] The system first became available in 1989, when it was fitted to the Austin Montego 2.0L. Over the next seven years, the system appeared on cars across Rover's model lineup, including the Mk VI and Mk VII Mini and the MG F / MG TF. It was also paired with Rover engines used by other marques, such as the Lotus Elise and several Caterham models using the Rover K-series engine.[3]
The ECU design was a joint venture between Rover and Motorola Automotive and Industrial Electronics Group (AIEG), who were responsible for the ECU manufacturing. The software run on the ECU was designed and written by Rover Group engineers. The "Modular" characteristic of the ECU was represented in the hardware design, which featured a common core with multiple optional add-on modules. In 1990, these modular features included the following:[2]
The processor in the ECU is an Intel 8096 running at 12 MHz and featuring 8KB of on-chip ROM for storage of code and data and 232 bytes of general-purpose RAM. The main connector is a 36-pin TE Connectivity 344108 ("Econoseal"), and its mating connector (used in the wiring harness) is a TE Connectivity 344111. On earlier versions of the system, a MAP sensor was internal to the ECU, requiring that an inlet manifold vacuum line be run to the ECU enclosure. In MEMS 1.6 and 1.9, this MAP sensor is the Motorola 5141550T02,[4] and the vacuum line feeding it passes through a vapor trap to prevent admission of fuel vapor into the ECU.[5]
An analogous system for engines with a carburettor was developed at the same time as MEMS. This system was known as "ERIC", which stands for "Electronically Regulated Ignition and Carburetion".[1] The development of the MEMS and ERIC systems became the first in-house units for ignition and fuel-control, areas which had previously been undertaken by Lucas Engine Management Systems, a division of Lucas Industries. While the development of MEMS and ERIC occurred at the same time, there was no commonality between the two systems - while MEMS used an Intel micro-controller, the ERIC system used the Motorola 68HC11 device; the development of MEMS used a PC based toolset, while that of ERIC used a Unix based toolset; the two teams working on MEMS and ERIC were totally independent.[citation needed]
Like other electronic engine management systems, MEMS reads data from a number of sensors and computes an appropriate fueling rate and ignition advance/retard. The ECU samples engine speed, manifold absolute pressure, coolant temperature, intake air temperature, throttle position, and battery voltage. Base values for the fueling and ignition timing are each retrieved from a three-dimensional map, and certain sensor values are applied as correction factors, for example, to enrich fueling during wide-throttle acceleration or on cold startup. The MEMS firmware also features a limp-home capability (referred to in the literature as "limited operating strategy") that will substitute a nominal value for any non-operative sensor.[1]
Crankshaft position and speed are determined by input signals generated by poles in a magnetic reluctance disc. The system may be run in either open-loop or closed-loop mode (with the latter requiring a lambda sensor). Additional features include an engine speed limiter, overrun fuel cut-off, startup fuel enrichment (both during cranking and after startup), and fueling compensation for battery voltage. Some operating parameters are learned by the ECU over time, such as the optimal IAC valve position for a stable idle. This accommodates slight differences in engine wear and tune between different engines.[6]
Among the different revisions of MEMS were the following:
Because it was designed before industry-wide on-board diagnostics were standardized, early versions of MEMS use a proprietary diagnostics protocol and signaling scheme. This protocol is known as ROSCO, which is an abbreviation for Rover Service Communications.[8] On earlier cars, the diagnostic port used a circular three-pin connector (type 172202 manufactured by TE Connectivity), where later cars switched to the standardized 16-pin ISO J1962 connector type.
When the system detects a fault, a corresponding fault code is stored in the ECU's non-volatile memory. Fault codes may only be cleared by commanding the ECU via the diagnostic port. Testing of MEMS equipped cars was originally possible with the "COBEST", "Microcheck", and "Microtune" test equipment provided to Rover dealerships and service centers.[6][9] The Rover TestBook system later became available to provide similar functionality as well.[2]
There are now various open and closed source applications for PC and mobile phones in order to interact with these ECUs, rather than having to purchase an old Testbook tool.
Seamless Wikipedia browsing. On steroids.
Every time you click a link to Wikipedia, Wiktionary or Wikiquote in your browser's search results, it will show the modern Wikiwand interface.
Wikiwand extension is a five stars, simple, with minimum permission required to keep your browsing private, safe and transparent.
