DRIVE-CLiQ is the nervous system of an S120: control unit, infeed, motor modules, encoders and sensor modules all hang on it, and the control unit knows the expected wiring. That knowledge is a feature until someone re-plugs cables freestyle.
How the topology behaves
At boot, the control unit compares actual topology against the projected one. Matching: normal start. Divergent: topology fault, and the lineup stays down until reality and project agree again. The comparison depth is adjustable (p9906 and friends) — but loosening it to “make the fault go away” converts a wiring error into a runtime mystery. Keep comparison strict; fix the wiring.
Practical rules we enforce:
- Wire by the generated topology plan and label both cable ends. The plan from Startdrive is the truth; the panel builder gets it printed.
- Respect the port hierarchy — components daisy-chain, hubs (DMC20) extend where stars are needed, and encoder modules sit close to their axis.
- Mind cable limits: standard DRIVE-CLiQ cables have length limits per segment (check the current spec per component); marginal lengths plus drag chains equal sporadic communication faults that look like ghosts.
Component replacement
Like-for-like replacement is painless if firmware versions cooperate: the control unit can update components automatically (deliberately enabled) or refuse mismatched ones. After replacing, verify the component is accepted, run the topology comparison clean, and archive — the new serial numbers are now part of the machine’s identity.
FAQ
Can I hot-plug DRIVE-CLiQ? Officially no. Power down the lineup for re-plugging; the connectors and the topology comparison both prefer it.
Random one-axis communication faults — where first? The cable and connector of that axis, then its sensor module, then EMC around the segment (shield continuity, parallel runs with motor cables).
Zone Otomasyon builds and services S120 lineups with topology documentation as standard. S120 expertise.