What a Control Module Actually Does
A MINI control module is a small, specialised computer with one job. Understanding the loop it runs — input, decision, output, feedback — explains what a stored fault does and does not prove.
In plain language
The modules in your MINI are small computers, each responsible for one area of the car: the engine, the brakes, the lights, the climate control, the doors and locks. They are not general-purpose computers. Each one reads its own sensors and switches, listens to messages from the others, decides what should happen, and switches the circuits it is responsible for.
The important part is the last step: after commanding something, a module checks whether it actually happened. When the answer is no, it stores a fault. That fault records what the module observed — not what caused it.
What the customer sees
A warning light, a function that has stopped working, or a message in the instrument cluster. Often the module that shows you the message is not the module with the problem; the cluster is largely a display for information produced elsewhere.
What the module is doing
Running its loop continuously: reading inputs, converting them into values it can work with, applying its software, commanding its outputs and monitoring the result. Alongside that it monitors its own supply, its own temperature and the health of the messages it expects from other modules on the network.
What a technician tests
Whether the module has what it needs before deciding whether the module is at fault: supply, ground, correct configuration, valid inputs and the messages it expects to receive. Then whether the command it issued reached the load, and whether the load responded. A module that correctly reports a circuit fault is doing its job.
The technical detail
A typical module contains input protection and voltage regulation, a processor, memory, analogue-to-digital conversion for its sensor inputs, one or more communication controllers and transceivers, and output-driver circuits for the loads it operates.
Inputs. Sensors and switches wired directly to the module, plus messages received from other modules over the vehicle networks. Both are inputs, and a missing network message can disable a function just as effectively as a disconnected sensor.
Decisions. The software applies the vehicle's configuration — its coding — to those inputs. Coding is part of the input set: a module whose stored configuration does not match the vehicle can behave incorrectly while every wire and sensor is intact.
Outputs. The processor's command is a low-current logic signal. A driver stage does the actual switching, and modern drivers include current sensing, thermal protection and fault detection. That protection is why a module will often shut a circuit down and record a fault rather than damage itself.
Feedback. After switching an output, the module looks for evidence that the physical result occurred: a lamp drawing current, a motor moving, a pressure changing. The absence of that evidence is what most output-side fault codes actually record.
Fault memory. Stored faults carry context — whether the condition is present now or was recorded earlier, and often the operating conditions at the time. A control-unit fault is a broad category that calls for manufacturer-specific diagnosis; it is not a verdict on the module itself.
Modules you may see on a MINI scan report
Not every MINI has every module here. Equipment, market, production date and chassis all change the list, and a scan tool showing a module family is not proof that the module is fitted. Use this as a guide to what each name is responsible for.
-
Car Access System CAS
- Key recognition and immobiliser authorisation
- Start-request logic and power-mode control
- Terminal control for switched supply groups
- Selector and interlock inputs where equipped
-
Digital Motor Electronics DME / ECM
- Fuel, ignition, throttle and valve timing as equipped
- Emissions monitoring and cooling strategy
- Torque coordination with the transmission and stability systems
The F56 scan shows the DME consuming wheel speed, vehicle speed, yaw rate, steering angle, braking torque, driving-dynamics status and vehicle-mass estimates from DSC/ICM. The engine controller is a consumer of chassis data, not an island.
-
Electronic Transmission Control EGS / TCM
- Automatic transmission control where equipped
- Selector and torque coordination with the DME
- Shift strategy using wheel speed, standstill status, road inclination and driving mode
In the F56 scan the transmission controller records missing wheel-speed, standstill, inclination, steering-angle, braking-torque and driving-mode messages — it does not shift in isolation.
-
Dynamic Stability Control DSC / ABS
- Wheel-speed measurement, anti-lock braking, traction and stability control
- Publishing vehicle-motion data to the rest of the vehicle
DSC, with ICM on later cars, is the vehicle's major producer of motion data: wheel speed, vehicle speed, yaw rate, longitudinal acceleration, steering angle, standstill status, road inclination, braking torque, driving-dynamics mode and tyre status.
-
Integrated Chassis Management ICM
- Coordinating driving-dynamics functions
- Providing motion and driving-mode data alongside DSC
Scan-tool text frequently names the transmitter as ICM/DSC together. Treat that as the chassis-dynamics source in general rather than as proof of which unit is fitted.
-
Electromechanical Power Steering EPS
- Steering assistance and steering status
- Steering-angle reference and initialisation
The F56 scan pairs missing speed, steering-torque and driving-mode messages with a steering-angle initialisation fault: assistance can be affected by communication or initialisation while the steering motor is healthy.
-
Junction Box Electronics and gateway group JBE / JBBF / KGM
- Network gateway between bus systems
- Electrical distribution and fusing
- Selected body functions, wipers and rain/light sensor handling
-
Footwell Module FRM
- Exterior and interior lighting control
- Lamp-circuit monitoring and bulb-outage detection
- Selected door and window functions
-
Body Domain Controller BDC
- Vehicle wake-up and power-mode management
- Body electrical functions and interior lighting over LIN
- Start/stop button input processing
- Terminal 30B and Terminal 30F management, battery protection
- Rain, light, solar and condensation sensor communication
The BDC coordinates functions that earlier MINI architectures distributed across CAS, JBE and FRM. It is a centralisation of responsibilities, not a one-for-one replacement of each of those modules.
-
Central Gateway Module ZGM
- Routing messages between network domains
- Diagnostic access to the vehicle's networks
- Sleep and power-down coordination, including terminal reset requests
In the F56 scan the ZGM records power-down, terminal-reset and terminal-deactivation requests due to prevented sleeping — this is the module that documents why a car did not go to sleep, which is where parasitic-drain work starts.
-
Steering Column Switch Cluster SZL
- Steering-column stalk inputs
- Multifunction steering-wheel data
- Steering-angle sensing on cars where it is housed here
-
Instrument Panel KOMBI / IC
- Speed, distance and driving-dynamics display
- Warning lamps, Check Control messages and tyre-status display
- Service and status information
The cluster is primarily a display and communication module. Most of what it shows originates elsewhere, so a cluster full of warnings is usually reporting other modules' problems.
-
Integrated Automatic Heating and Air Conditioning IHKA
- Climate-control logic, blower and temperature control
- Flap and motor operation, often over a local network
- Using solar, speed and driving-mode information from other modules
An HVAC fault code frequently names data that arrives from elsewhere — vehicle speed from DSC/ICM, solar-sensor status from the BDC — rather than a failure of the climate panel.
-
Crash Safety Module ACSM / MRS / SRS
- Restraint deployment logic and impact sensing
- Seat-occupancy and belt monitoring
- Consuming vehicle speed and dynamics data
Restraint circuits are pyrotechnic. Follow the manufacturer's disabling procedure before probing anything in this system. On the scanned F56 the ACSM communicates over FlexRay.
-
Tyre Pressure Monitoring RDC
- Tyre-pressure monitoring and tyre-status reporting
-
Parking Manoeuvring Assistant PMA
- Ultrasonic sensing for parking assistance
- Using vehicle speed, wheel-distance data, steering angle and stability status
The F56 scan shows a local ultrasonic sensor circuit fault alongside missing chassis messages — a good reminder that a local component fault and a network fault can be present at the same time and are separate repairs.
-
All-Round Vision Camera TRSVC
- Surround-view image processing
- Predicted-path overlays using vehicle speed and steering angle
-
Frontal Light Electronics FLEL / FLER
- Local control of an advanced headlamp unit, left and right separately
- Beam adjustment, lamp operation and fault monitoring
- Holding its own coding
Because each headlamp has its own electronics, coding faults and undervoltage are recorded per side — as they are in the scanned F56.
-
Roof Function Centre FZD
- Sunroof operation and roof-area switches
- Roof-mounted electronics
- Initialisation and normalisation of the roof drive
Its faults show how mechanical initialisation and electrical supply interact: a drive that lost its supply also loses the normalisation it needs before it will operate.
-
Sunroof Control SHD
- Sunroof control where equipped
-
Satellite Tuner SDARS
- Satellite radio reception where equipped
-
Display, radio and media group CIC / CCC / CHAMP / M-ASK / RAD / HU-H
- Display, radio, media and navigation functions depending on equipment
- Gateway functions to the infotainment domain on some vehicles
These labels vary widely by equipment and production date. A tool listing all of them has not proved that all of them are installed.
-
Hi-Fi Amplifier AMP
- Audio amplification where the hi-fi option is fitted
-
Active Sound Design ASD
- Engine-sound enhancement through the audio system where equipped
-
Touchbox TBX
- Touch-sensitive controller input where equipped
-
Controller CON
- Rotary controller input for the infotainment system
Combined scan-tool labels such as CAS/FEM/BDC or JBE/JBE2/JBBF/KGM are tool taxonomy. They describe the families a tool can address, not proof that every named module is installed in the vehicle being scanned.
Why this matters when something goes wrong
Every fault code is written from one module's point of view. "No message from another module" is stored by the receiver, not the transmitter, so the code names the module that noticed the silence rather than the module or wiring that caused it. Following those codes literally leads you to the wrong end of the car.
The same applies to output faults. A module reporting that a circuit did not respond has told you about the circuit — supply, connector, load, ground and the driver, in that order of likelihood — and has not told you which of those is at fault. Working the module's loop from its inputs through to its feedback is what turns a stored code into a diagnosis.