John Deere Engines SPN2000FMI13 Fault Code: Security Violation
Also called Incorrect ECU for Application
Security Violation · ai-assisted, editor-reviewed · Last updated 2026-07-13
TL;DR
SPN2000FMI13 (also written DTC 2000.13 or DTC 002000.13) sets when the engine ECU decides that it, or another controller on the machine, is not the correct part for that specific machine. The engine will still start, but the ECU limits it to low idle only until the mismatch is resolved.
High severity. The engine will start but is locked to low idle speed only, so the machine cannot do productive work until this is fixed. It is not an immediate safety emergency, but it stops operation and should be diagnosed before the next work shift.
What does John Deere Engines error code SPN2000FMI13 mean?
SPN2000FMI13 is a security/configuration check, not a sensor failure. Every time the ignition is turned on, all the controllers on the machine talk to each other over the CAN network and confirm that each one is the correct part for that specific machine build. This is John Deere's way of preventing a controller from a different machine or configuration from running the engine incorrectly.
When the ECU decides that it, or some other controller on the machine, does not match what is expected, it sets this security violation code. The response is deliberately restrictive: the ECU will allow the engine to start, but will only allow low idle engine speed, so the operator cannot put the machine to work until the mismatch is sorted out.
This code almost always points to a parts or programming issue rather than a wiring or sensor fault. It commonly shows up right after a controller has been replaced, reflashed, or swapped between machines.
Common causes of SPN2000FMI13
- Improper controller installed, meaning a controller that is not the correct part number for this specific machine is present somewhere on the network
- A controller was recently replaced and the correct replacement part was not installed or not properly matched to the machine
- Other active or stored CAN-related fault codes on one or more controllers that are interfering with the security check between controllers
How to troubleshoot John Deere Engines SPN2000FMI13: first checks
- If any controller on the machine was just replaced, verify that the correct controller part number was installed for this machine and application
- Confirm that all controllers on the machine are the correct part numbers specified for this particular machine configuration
- Check every controller on the CAN network for active or stored CAN-related diagnostic trouble codes, since these can trigger or accompany the security violation
- If CAN-related codes are found on any controller, follow the diagnostic procedure for that specific code before continuing
- Note that the engine will only run at low idle while this code is active, so plan the diagnosis in a safe, stationary location rather than trying to move the machine
How the code clears
No separate clearing step is listed. Once the correct controller part numbers are confirmed and any related CAN diagnostic trouble codes are resolved, the security violation should clear on its own during the next key cycle. For the full diagnostic procedure, check the application-specific technical manual for this machine.
Frequently asked questions
What does SPN 2000 FMI 13 mean on a John Deere engine?
It means the engine ECU has determined that it, or another controller on the machine, is not the correct controller for that specific machine. It is described as a security violation, checked every time the ignition is turned on.
Can I still drive or run the machine with this code active?
The engine will start, but the ECU will only allow low idle engine speed. You will not be able to work the machine normally until the underlying controller mismatch is fixed.
Why did this code appear right after I replaced a controller?
This is one of the most common triggers. If a controller was just replaced, double check that the exact correct part number was installed for this machine. An incorrect or mismatched replacement controller is a listed cause.
Is SPN 2000 FMI 13 a wiring problem or a sensor problem?
No. It is a controller identity and security check issue, not a wiring or sensor fault. The fix involves confirming correct controller part numbers and checking for CAN-related codes, not testing sensor circuits.
What is DTC 2000.13 or DTC 002000.13, is it the same as SPN 2000 FMI 13?
Yes, these are just different ways John Deere manuals label the same fault: SPN 2000 with FMI 13. You may see it written as SPN 2000 FMI 13, DTC 2000.13, or DTC 002000.13 depending on the manual.
What should I check first if I see this code but no controllers were recently replaced?
Check all controllers on the machine for active or stored CAN-related diagnostic trouble codes. If any are present, follow the diagnostic procedure for that specific CAN code, since it may be causing or accompanying the security violation.