SM096 - EDC15M (ROVER) - System Help file |
| Version 1.22 |
EDC15M - Known Fitments | ||||||||||||||||||||||||||||||||
Vehicle makes, models and variants known or believed to be using this vehicle system, required diagnostic lead and degree of known compatibility.
|
EDC15M - Physical Details |
![]() |
SM096 - EDC15M - Diagnostic Capabilities (Read Fault Codes) |
| Reads the fault code memory. The ECU can self detect around 88 different problems with itself, its wiring and its associated sensors, storing the respective code if it detects any malfunction or reading outside of predefined acceptable limits. Not all stored faults may cause the fault warning lamp to illuminate. |
SM096 - EDC15M - Diagnostic Capabilities (Clear Fault Codes) |
| This function clears the fault code memory. Failure to clear the fault memory successfully is usually due to the system relogging the fault the moment the fault memory is clear. This indicates that the fault has not been rectified properly and as far as the system is concerned, still exists. The recheck for successful clearing of the fault code memory may be successfully executed but then the system may relog the fault shortly after. |
SM096 - EDC15M - Diagnostic Capabilities (Settings) |
Values, configuration settings, and other stored information which can be read from the ECU, edited and then rewritten back. Read settings can also be stored as a standard HTML page for reference. These pages can then later be reloaded and rewritten back to the ECU. Please note that some values may be read only due to the fact that they are supplied from the ECU's ROM or are internally calculated.
PROGRAMMING RECORDS (Flash type ECUs only)
The ECU has an area of memory allocated for programming history records. Each record, which is a fixed length contains the VIN number, programming date, assembly number, Homologation number and some unused hexadecimal data. Whenever a new record is added, it is placed after the last record and then becomes the active record which diagnostic equipment such as TestBook reads to obtain information about what an ECU is currently programmed with to see if there are any updates required to be programmed into it. It also uses the absence of any records to indicate a new ECU, which is the only time it allows a vehicle configuration change as from then on it uses the last Assembly number to dictate the maps uses to update the ECU with. It does not appear to verify that the actual maps in the ECU are those indicated by the Assembly number shown in the last / Active programming record, or read previous records. It is not diagnostically possible to erase or modify existing programming records. The possible space is limited before the ECU can no longer be updated and must be replaced, which ultimately results in additional ECU sales. It is therefore likely that the ECU may well not accept the programming of all possible spaces.
The page shows the Active Record, which is the actually the last record, is then shown under that and is provided here as a duplicate of the last record simply to save having to scroll to the bottom of a possibly long list to get to the last record and the used Programming Records from 1 to the last one used.
|
SM096 - EDC15M - Diagnostic Capabilities (Inputs) |
Realtime live display of the information the electronic control unit of the selected vehicle system is currently deriving from its input sensors.
|
SM096 - EDC15M - Diagnostic Capabilities (Outputs) |
|
SM096 - EDC15M - Diagnostic Capabilities (Other) |
Choice of functions that can be performed:
|


SM096 - EDC15M (ROVER) - System Help file
EDC15M - Known Fitments
EDC15M - Physical Details
SM096 - EDC15M - Diagnostic Capabilities (Read Fault Codes)