Bobcat W3223 (32-23) Fault Code: ACS Controller Not Calibrated
Also shown on the panel as 32-23 · Also called ACS (AHC) Calibration Required, ACS controller Not Calibrated
ACS Controller Not Calibrated · ai-assisted, editor-reviewed · Last updated 2026-07-13
TL;DR
W3223 (panel form 32-23) sets when a new or replaced ACS controller has no stored calibration data. It shows up on Bobcat skid-steer and compact track loader models including S510, S530, S550, S570, S590, S630, S650, S750, S770, T550, T590, T630, T650, T750, and T770, T870. It is not a failure of the system itself, it is a controller telling you it has never been calibrated.
Medium severity. W3223 does not indicate active damage or a live sensor fault. It means the ACS (advanced control system) controller is running without calibration data, which can affect how the machine responds to hand and foot controls until calibration is completed.
What does Bobcat error code W3223 mean?
W3223 is set only on a new ACS controller that has not completed a successful calibration. The calibration values that tell the controller how to interpret handle and foot control inputs are stored inside the ACS controller itself. If that data is missing or was never written, the controller flags this code.
This code is expected the first time a new ACS controller, actuator, handle sensor, or foot sensor is installed. It is part of the setup process, not necessarily a sign of a wiring or component failure, though wiring and connector problems can also prevent calibration from completing or from being retained.
Running the actuator test in Bobcat diagnostic software is the preferred way to calibrate the ACS system. That test both exercises the actuators and writes the calibration data the controller needs to clear this code.
Common causes of W3223
- ACS controller needs calibration (most common cause, especially on a newly installed controller).
- Calibration procedure was attempted but not completed successfully.
- A new actuator, handle sensor, foot sensor, or ACS controller was installed and has not yet been calibrated.
- Moisture, corrosion, or pushed-back pins in the ACS controller connectors, the diagnostic tool/ACD connector, the ACS harness, or the AWS/SJC harness.
- Intermittent cases: if the code is not active at the time of testing, the exact cause may not be identifiable right away. Possible contributors include loose connections, corrosion, pushed-back pins, the controller itself, the wire harness, or a combination of these.
How to troubleshoot Bobcat W3223: first checks
- Confirm the key switch is in the run/enter (on) position, since that is the condition required for the code to be checked and cleared.
- Inspect all ACS controller connectors, the diagnostic tool/ACD connector, the ACS harness, and the AWS/SJC harness for moisture, corrosion, or pins that have been pushed back out of their sockets.
- If a new actuator, handle sensor, foot sensor, or ACS controller was recently installed, treat W3223 as expected and proceed straight to calibration rather than chasing it as a fault.
- Run the actuator test in Bobcat diagnostic software. This is the preferred method to calibrate the ACS system and is what actually clears the underlying condition.
- If the code is intermittent and not present during testing, recheck all connections for looseness or corrosion since intermittent codes often trace back to marginal connections rather than a failed part.
How the code clears
Cycle power to clear the code once the calibration procedure has been completed successfully. There is no separate reset procedure listed beyond completing calibration (via the actuator test in diagnostic software) and cycling power.
Affected models and serial ranges
W3223 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-99999 |
| 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 A39511001-99999, 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 W3223 mean?
It means the ACS controller, the system that manages the joystick and pedal controls, has not completed a successful calibration. The calibration data lives inside the controller, and until it is written, the code stays active.
Is W3223 dangerous to keep driving with?
It is not described as an active safety fault, but an uncalibrated ACS controller can affect how consistently the machine responds to hand and foot inputs. It should be resolved before relying on normal operation.
How do I clear W3223 for good?
Run the actuator test in Bobcat diagnostic software, which is the preferred way to calibrate the ACS controller, then cycle the key power. That combination is what clears the code once the calibration is stored.
Why did this code appear right after I replaced a part?
A new actuator, handle sensor, foot sensor, or ACS controller will not have calibration data yet, so W3223 setting after that kind of replacement is expected. It should clear once you complete the calibration procedure.
The code comes and goes, what should I check?
Intermittent W3223 codes are often tied to loose connections, corrosion, or pushed-back pins in the ACS controller connectors, the ACS harness, or the AWS/SJC harness. Inspect those connections carefully even if the code is not active when you check.
Does the key switch position matter for this code?
Yes. The condition for the code to be evaluated is the key switch in the run/enter (on) position. Testing with the key off will not reflect the actual code status.