Bobcat M2302 (23-02) Fault Code: Starter Relay Error On
Also shown on the panel as 23-02
Starter Relay Error On · ai-assisted, editor-reviewed · Last updated 2026-07-13
TL;DR
M2302, shown on the panel as 23-02, sets when Bobcat's gateway controller sees voltage on the starter feedback wire (8250 or 3560, depending on model) when it did not command the starter relay on. It points to a wiring short, a stuck relay, a bad starter solenoid, or a gateway controller problem. The code is self resetting once the condition clears.
Medium severity. M2302 does not by itself stop the machine from running once started, but it signals a starting-circuit fault that can cause unexpected starter engagement or no-start conditions. Treat it as a diagnose-soon issue rather than an emergency shutdown, unless the starter is actually engaging on its own, which turns this into an immediate stop-and-inspect situation.
What does Bobcat error code M2302 mean?
,M2302 is Bobcat's Starter Relay Error On code, also shown as panel code 23-02. It is set by the gateway controller, which monitors the starter circuit for correct behavior every time the key switch or run/enter switch is on.
The starter relay normally sends battery voltage out to the starter solenoid on wire 8200 only when the controller commands it. The starter then sends a feedback signal back to the gateway controller on wire 8250 or wire 3560 (the exact wire depends on model) to confirm the solenoid engaged. M2302 triggers when the controller sees voltage on that feedback wire without having commanded the relay, which tells it something in the circuit is energized when it should not be.
This matters because an uncommanded signal on the starter feedback circuit can mean the starter is receiving power it should not have, a wire is shorted to a voltage source, or the relay or solenoid itself is stuck or failing internally. Any of these can lead to unexpected starter engagement, a no-start condition, or premature starter wear.
Common causes of M2302
- Relay output wire 8200 or the feedback wire (8250 or 3560, depending on model) shorted to supply voltage
- Faulty starter relay
- Faulty starter solenoid
- Gateway controller fault
- Moisture, corrosion, or pushed-back pins in the gateway controller connectors, starter relay connectors, starter solenoid connectors, engine harness, or mainframe harness
- Intermittent fault not present at time of testing: possible loose connections, corrosion, pushed-back pins, the controller, the wiring harness, or a combination of these
How to troubleshoot Bobcat M2302: first checks
- Confirm the key switch or run/enter switch is on, since that is the condition under which the controller checks this circuit
- Inspect the starter relay and starter solenoid connectors, and the gateway controller connectors, for moisture, corrosion, or pushed-back pins
- Visually and physically check the engine harness and mainframe harness for chafing, pinched wiring, or damage near wire 8200 and the feedback wire (8250 or 3560)
- Test relay output wire 8200 and the feedback wire for an unexpected short to supply voltage
- Check the starter relay and starter solenoid for correct operation, since either can cause this feedback fault if they stick or fail internally
- If the code is not active during testing, treat it as intermittent and focus on connection points, since loose connections, corrosion, and pushed-back pins are the most common intermittent causes
How the code clears
M2302 is self resetting. No separate clearing step is listed. Once the wiring, relay, solenoid, or controller issue causing the uncommanded feedback voltage is repaired, the code should clear on its own without a manual reset procedure.
Affected models and serial ranges
M2302 appears in our records across 16 Bobcat models. Match your machine by model and serial number.
| Model | Serial ranges |
|---|---|
| S510 | SN A3NJ11001-99999, SN A3NK11001-99999, SN ATZC11001-ATZC99999 |
| S530 | SN A7TV11001-99999, SN ATZD11001-99999 |
| S550 | SN A3NK11001-A3NL99999, SN A3NM11001-99999 |
| S570 | SN A7U711001-799999, SN A7U811001-899999 |
| S590 | SN ANMN11001-99999, SN ANMP11001-99999 |
| S630 | SN A3NT12370-99999, SN A3NU11001-11111, SN A3NU11112-99999 |
| S650 | SN A3NV11001-13098, SN A3NV13099-99999, SN A3NW11001-11248, SN A3NW11249-99999 |
| S750 | SN A3P211001-299999 |
| S770 | SN A3P411001-99999 |
| T550 | SN A7UJ11001-AJZV12276 |
| T590 | SN ALJU11001-999999, SN B37811001-999999, SN B3Z711001-999999 |
| T630 | SN A7PU11001-11663, SN A7PU11664-99999 |
| T650 | SN A3P012214-099999, SN A3P111242-199999 |
| T750 | SN ANKA11001-A99999 |
| T770 | SN A3P811001-899999, SN A3P911001-999999 |
| T870 | SN A3PG11001-99999, SN A3PH11001-99999 |
Frequently asked questions
What does Bobcat code M2302 mean?
It means the gateway controller detected voltage on the starter feedback wire (8250 or 3560 depending on model) when it had not commanded the starter relay on. It is a starter circuit integrity fault, not a direct engine fault.
What is the panel display number for M2302?
It shows on the panel as 23-02.
Can I keep operating the machine with M2302 active?
There is no listed lockout tied to this code, but since it involves the starting circuit, it is best to have it diagnosed promptly. If you notice the starter engaging unexpectedly, stop and have it inspected right away.
Do I need to manually clear M2302?
No. The code is self resetting once the underlying condition is no longer present. No separate clearing procedure is listed.
Which Bobcat machines can show M2302?
It applies across models including the S510, S530, S550, S570, S590, S630, S650, S750, S770, T550, T590, T630, T650, T750, and T770, and T870.
Is M2302 caused by a bad starter or a wiring problem?
It can be either. Bobcat lists a shorted relay output or feedback wire, a faulty starter relay, a faulty starter solenoid, a gateway controller fault, or connector corrosion and pushed-back pins as possible causes, so both wiring and component failures need to be checked.
Why does M2302 come and go instead of staying on?
Intermittent starter feedback faults are usually tied to loose connections, corrosion, or pins pushed back in connectors rather than a fully failed component. If the code is not active during testing, focus your inspection on connection points first.