SPN 6713 FMI 16: Meaning and Fix
SPN 6713 FMI 16 indicates the VGT actuator’s embedded software identification value is reporting above the normal operating range defined by the ECM calibration dataset. This fault commonly appears after an ECM reflash or actuator replacement when the new component’s firmware version does not match the engine control unit’s expected software ID parameter. On Bosch-equipped diesel platforms such as MAN TGX or Mercedes-Benz Actros, technicians frequently encounter this code immediately post-actuator swap without performing the required software synchronization procedure.
Common Symptoms
- Reduced Turbo Response: VGT vane positioning becomes erratic or sluggish, causing noticeable turbocharger lag during acceleration under load.
- Derate Mode Activation: ECM enforces a torque limitation strategy, reducing engine output by up to 25% to protect turbocharger mechanical components.
- Boost Pressure Deviation: Actual boost pressure deviates significantly from ECM-commanded targets, triggering secondary boost-related fault codes simultaneously.
- Persistent MIL Illumination: Malfunction indicator lamp remains active across multiple key cycles even after fault code clearing attempts without actuator reprogramming.
Probable Causes
- Actuator Firmware Mismatch: Replacement VGT actuator carries a software version incompatible with the ECM’s stored calibration ID reference table.
- Incomplete ECM Reflash: An aborted or partial ECM reprogramming session left corrupted software ID parameters within the turbocharger actuator control module.
- CAN Bus Data Corruption: Electromagnetic interference or damaged J1939 data lines caused erroneous software ID frames to be written to the actuator EEPROM.
- Unauthorized Tuning Modification: Third-party chip tuning or remapping altered the ECM’s expected software ID threshold values beyond factory-defined operational boundaries.
Advanced Technical Analysis
The ECM continuously monitors the VGT actuator’s software identification register via a dedicated J1939 PGN handshake during each ignition cycle. When the returned software ID value exceeds the upper threshold defined in the engine calibration dataset, FMI 16 is flagged. Bosch MSB actuator platforms transmit this ID over a private CAN segment at 250 kbps. A single out-of-range reading is insufficient to set the fault; most OEM calibrations require consecutive abnormal readings across a debounce window.
Electrically, the VGT actuator communicates with the ECM through a bidirectional LIN or CAN interface depending on the platform. Signal integrity issues such as increased line resistance above 3 ohms or supply voltage drops below 10.5V can cause the actuator microcontroller to report corrupted software ID data. Technicians must measure supply voltage directly at the actuator connector under cranking load conditions. MAN factory procedures specify a maximum voltage drop of 0.5V across the actuator supply harness before condemning the actuator itself.
When FMI 16 is active, the ECM transitions the VGT control loop into a defined safe-state fallback position, typically holding vanes at a fixed intermediate angle corresponding to approximately 60% closure. This prevents uncontrolled boost overpressure while maintaining marginal engine operability. Mercedes-Benz OM471 calibration files define this fallback as a torque reduction to 75% of rated output. The engine will not exit derate until the software ID parameter returns within the acceptable range and a successful fault healing cycle is completed.
Long-term diagnostic strategy requires using OEM-level tooling such as DAVIE for DAF, MAN-cats II, or Mercedes-Benz XENTRY to read the exact software ID value reported by the actuator and compare it against the ECM’s expected value table. Workshops frequently encounter this fault on fleets where actuators are sourced from aftermarket suppliers lacking proper firmware pre-loading. Preventive practice includes always ordering actuators with confirmed software version compatibility and performing a mandatory actuator initialization routine post-installation to synchronize ID registers with the ECM calibration dataset.
Step-by-Step Troubleshooting Guide
- Read Actuator Software ID: Connect OEM diagnostic tool and retrieve the exact software ID value reported by the VGT actuator for direct comparison against ECM calibration tables.
- Inspect Harness Integrity: Measure resistance and voltage drop across the VGT actuator supply and CAN/LIN communication lines to eliminate electrical faults before software diagnosis.
- Perform Actuator Initialization: Execute the manufacturer-prescribed actuator programming or synchronization routine using DAVIE, MAN-cats II, or XENTRY after any hardware replacement procedure.
- Verify ECM Calibration Version: Confirm the ECM holds the latest approved calibration file; reflash using OEM software if version mismatch with actuator firmware is identified.