A01382 — Topology: Sensor Module incorrectly inserted

A01382 is an alarm raised by the drive's topology comparison: a Sensor Module has been found in the actual topology — the hardware as it is physically inserted — at a connection that does not match the target topology configured in the project. The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. The alarm text itself names the component and the connection involved.

• The topology comparison has detected a Sensor Module in the actual topology that has been incorrectly inserted with respect to the target technology — the module stands at a connection that the target topology does not expect.

1. Identify the component and connection from the alarm value (see below); under "Topology --> Topology view" the commissioning software/tool offers, where relevant, improved diagnostics capability (e.g. setpoint/actual value comparison).
2. Insert the components involved at the right connection (correct the actual topology).
3. Alternatively, adapt the project/parameterization in the commissioning software/tool (correct the target topology).
4. Use p9904 to remove the topology error automatically.

The alarm value is stored in r2124 and must be interpreted as hexadecimal, in the pattern ddccbbaa hex. The alarm text shows Component: %1, to %2, %3, connection: %4; the placeholders are the parts of the alarm value:

• dd = connection number (%4)
• cc = component number (%3)
• bb = component class (%2)
• aa = component number of the incorrectly inserted component (%1)

The component involved is described in dd, cc and bb, where the component involved is incorrectly inserted. Component class and connection number are described in F01375.

• r2124 — alarm value of this alarm; read it in hexadecimal (ddccbbaa) to identify the connection number, the component number, the component class and the component number of the incorrectly inserted Sensor Module.
• p9904 — Topology comparison acknowledge differences (Topo_compare ackn); removes the topology error automatically, one of the three ways the remedy lists for adapting topologies.

This alarm requires no acknowledgement. While the topology error exists, the drive system is no longer booted and the drive control (closed-loop) cannot be enabled; the error is removed by one of the steps above.