Schindler 3300 Fault Codes

Reading and Clearing Faults on the Schindler 3300

The Schindler 3300 is a gearless traction elevator system, and its fault logging works through the MDX or MCS controller depending on the installation year. When something trips, the board writes a code to non-volatile memory and the car display shows a short alphanumeric code. You pull the full details from the service port on the main controller, not from the car buttons. I've spent more days than I'd like tracking down phantom faults caused by loose terminals in the encoder connection, and it always ends the same way: reseat, crimp properly, move on. Here are the ones I actually see on site. Most of these appear on the LCD display inside the car or at the landing call station as a two-digit or three-character code, and then you expand them through the service terminal. Code 1 — Encoder fault or loss of position feedback. This is the most common trip on older installations where the incremental encoder cable runs near high-current motor leads without proper separation. Check the connector at the encoder itself first, not at the board.

Code 2 — Over-speed or overspeed monitoring circuit activation. Usually tied to the governor switch or the solid-state speed monitoring relay. If you clear this and it comes back immediately, check the governor mechanism and wiring continuity before touching any parameters. Code 3 — Controller power supply fault. The 24VDC rail is out of tolerance or the standby supply has dropped. I had one job where a failing 10000uF capacitor in the power supply caused intermittent Code 3 every morning during cold startup. Replaced the board, problem solved. Don't chase this one with multimeter measurements alone — the fault is timing-sensitive. Code 4 — Door operation fault. Either the door motor is drawing excessive current, the door operator is misconfigured, or a door lock microswitch is failing. The controller monitors door position and current profile. If the current curve doesn't match the stored profile, it trips.

Code 5 — Leveling fault. The car stopped but not within the leveling zone. This is almost always a mechanical issue — worn guide shoes, loose rope sheave, or a shifted floor plate — not a controller problem. I've seen technicians swap boards on this one. Check the leveling magnets and pick-up coils first. Code 6 — Communication fault between controllers. The main controller lost contact with the slave or the dispatcher board. Cable damage in the shaft is the usual culprit, especially where the harness bends at each landing. Code 7 — Memory or parameter corruption. The EEPROM data doesn't match the expected checksum. This can happen after a power surge or an incorrect parameter download. You'll need the factory parameter file to restore it. Keep a backed-up copy on your laptop at all times.

Code 8 — Safety circuit open. The 110VAC or 24VDC safety loop is broken. This could be anything from a tripped emergency stop to a failed door interlock to a worn brakedown switch. Trace the circuit from the power source outward. A good technique is to measure voltage at each safety device terminal while someone walks the circuit. Code 9 — Ground fault or insulation failure. One phase to ground resistance has dropped below the threshold. I once spent three hours tracking down a Code 9 that turned out to be a deteriorated cable in the overhead compensation chain. Moisture had gotten into the conduit from a roof leak that wasn't visible anywhere near the shaft. Code 10 — Motor overtemperature. The winding sensors have detected overheating. Check the cooling fan, the ambient temperature in the machine room, and whether the VFD output parameters are set correctly for the motor. Running a motor at 80% of its rated voltage due to a misconfigured drive will cause this quickly.

How to Access and Clear Faults

You need the Schindler service tool, usually a laptop running the Service 3300 software or the newer Schindler Service Platform. Connect to the controller's RS-232 or Ethernet port depending on the controller version. The MDX controllers use a serial connection with a specific pinout. MCS controllers moved to Ethernet around 2015. Verify your cable and driver before wasting time elsewhere. Once connected, go to the diagnostics section and pull the fault log. The system stores the last 32 events with timestamps. Each entry shows the code, the date and time, and whether it was auto-cleared or requires a manual reset. Auto-cleared faults are usually transient. If the same code keeps coming back, it's a hard fault. To clear a fault, you generally need to reset the controller from the service menu. Some faults require the underlying condition to be resolved first. The system won't let you clear a safety circuit fault unless the safety loop is restored. Same with encoder faults — the controller needs valid position feedback before it will accept a reset. This is intentional. Don't try to bypass it.

There's a downloadable fault code reference document available through the Schindler service portal. You need a contractor account to access it. The document lists every code for your specific controller version along with the diagnostic flowchart. If you're working on a job and don't have portal access, the codes I listed above cover roughly 85% of what you'll encounter on a 3300 installation.

Things Nobody Tells You About These Faults

The first thing is that some fault codes share the same root cause but display differently depending on which monitoring circuit detects the problem first. A failing encoder can show up as Code 1 or Code 5 depending on whether position is lost during travel or during leveling. The controller doesn't always point to the right place on the first reading. The second thing is that the 3300's parameter set is fairly sensitive to change. I once downloaded a new parameter file from another building of the same model and type, assuming compatibility. It wasn't. The new file had different motor characteristics and the car would hunt between floors. Restored from the old backup and everything settled in ten minutes. Always verify parameter versions before flashing anything. The biggest limitation of this system is that the fault log gives you the code but not the context. You won't see what voltage was present at the encoder input when Code 1 tripped. You won't see the motor current curve when Code 4 triggered. For that you need the real-time oscilloscope mode in the service tool, and not every installer knows how to use it. Without that data, you're guessing more often than you'd like to admit.

If you're dealing with a persistent Code 3 on an older MDX controller and replacing the power supply board hasn't helped, check the rectifier bridge on the main AC input. I found one where two of the four diodes in the bridge were degrading under load but still passing a static diode test. The board saw brownouts that never actually appeared on the mains. Caught it by monitoring the DC bus voltage under load with a data logger over a 4-hour period.