A01386 — Topology: DRIVE-CLiQ component incorrectly inserted

The drive's topology comparison has detected a DRIVE-CLiQ component in the actual topology that has been inserted incorrectly with respect to the target topology — the component sits at a connection the project does not expect. The message value names the component and the connection concerned. While the alarm is present, The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled.

• A DRIVE-CLiQ component is inserted in the actual topology at a connection that does not match the target topology.

1. Insert the components involved at the right connection, so the actual topology matches the target topology.
2. Alternatively, adapt the project/parameterization in the commissioning software so the target topology matches the components as they are actually inserted.
3. Alternatively, remove the topology error automatically with p9904.

Under "Topology --> Topology view" the commissioning software offers improved diagnostics capability where relevant, for example a setpoint/actual value comparison.

• Message value: Component: %1, to %2, %3, connection: %4 — the drive fills in the component concerned and the connection at which it is incorrectly inserted.
• The alarm value is stored in r2124 and is to be interpreted hexadecimal: ddccbbaa hex.
• dd = connection number (%4)
• cc = component number (%3)
• bb = component class (%2)
• aa = component number of the incorrectly inserted component (%1)
• dd, cc and bb describe the component where the component involved is incorrectly inserted; component class and connection number are described in F01375.

• r2124 — alarm value: read it hexadecimal as ddccbbaa to identify the connection, the component class, the component number and the incorrectly inserted component.
• p9904 — Topology comparison acknowledge differences (Topo_compare ackn): used to remove this topology error automatically, as an alternative to re-inserting the component or adapting the project.

There is no acknowledgment step for this alarm: it ends when the difference between the actual and the target topology has been eliminated — by re-inserting the component at the right connection, by adapting the project/parameterization, or by removing the topology difference automatically with p9904, so that the drive system boots and closed-loop drive control can be enabled again.