Disk'O ride faults & won't start — checking HMI/PLC/IO
The Disk'O — a spin-and-swing ride by Zamperla — runs on industrial control (PLC + HMI + drive/VFD + angle/position sensors). When it won't start, stops mid-cycle, or the HMI shows a fault, it is mostly HMI/PLC/I-O/drive/sensor or comms — the NON-safety parts. That is what DeepDebug supports.
⚠️ Safety boundary (read first): rides carry people = safety-critical. We do NOT alter/bypass safety systems (safety PLC/Pilz, brake interlocks, zoning). Safety parts must go through the formal channel: park authorization + proper inspection/certification. This article covers only the non-safety control side.
Quick note: a ride usually has two layers — the operational control (PLC/HMI/drive/sensor, runs the ride) and a separate safety layer (safety PLC, brakes, E-stop). A “won't release/won't run” can be reported by the operational layer, but the safety layer may also be holding it — distinguish them correctly.
Common faults (non-safety side)
- HMI — black/frozen screen, no status shown, lost app.
- PLC fault — fault LED, won't enter the cycle, lost step.
- Dead I/O module — bad input/output channel → wrong operational signal.
- Drive / VFD (e.g. KEB) — overcurrent/overheat fault, won't reach speed.
- Angle/position sensor — dirty, misaligned, failed → stops because position isn't confirmed.
Disk'O down with guests waiting?
Send: ride model, the HMI/PLC/drive code-LEDs, panel photos. Get a quick localization (operational side).
Troubleshooting approach
- Read the root alarm on the HMI Find the first alarm by time; distinguish operational-layer from safety-layer reports.
- Is the HMI/PLC alive? Check power, run/fault LEDs; if the HMI is dead → inspect 24V, the memory card (rescue/clone).
- Check I/O Read the relevant I/O channel states; swap/replace a suspect dead channel.
- Read the drive fault Note the VFD/servo code; check overload, cooling, feedback.
- Check sensors Clean/align the angle-position sensors; check the signal wiring.
- If it's the safety layer → STOP, don't self-handle; route to the formal channel (the park's safety team + an authorized inspection body).
When to call an expert
Imported rides, distant OEM, slow/expensive support — yet HMI/PLC/I-O/drive/comms faults can be handled remotely and fast. DeepDebug supports exactly this operational side to reopen the ride sooner; safety always goes to the formal channel.
Send a fault — get a diagnosis
Strong on control & comms. Safety: via the formal channel.