A01483 — Topology: Terminal Module not connected

A01483 – Topology: Terminal Module not connected. The drive compares the hardware actually connected (actual topology) with the configured project (target topology). This alarm is raised when the topology comparison detects a Terminal Module that is missing in the actual topology with respect to the target topology — the project expects a Terminal Module that the drive cannot find at the expected connection. The message value names the component concerned: “Component: %1, to %2, %3, connection: %4”. For improved diagnostics (e.g. setpoint/actual value comparison) the commissioning tool offers, where relevant, “Topology --> Topology view”.

• The topology comparison has detected a Terminal Module that is missing in the actual topology with respect to the target topology: the project expects the component, but it is not present in the connected hardware at the expected connection.
• The components involved are therefore either not inserted at the right connection, or the project/parameterization does not match the hardware actually connected.

1. Correct the topology: insert the components involved at the right connection (this corrects the actual topology), or adapt the project/parameterizing in the commissioning tool (this corrects the target topology).
2. Check the 24 V supply voltage.
3. Check the DRIVE-CLiQ cables for interruption and contact problems.
4. Check that the component is working properly.

• The drive stores the alarm value in r2124; it must be interpreted hexadecimal as ddccbbaa hex.
• dd = connection number (%4)
• cc = component number (%3)
• bb = component class (%2)
• aa = component number of the component that has not been inserted (%1)
• The component is described in dd, cc and bb, where the component has not been inserted. The component class and the connection number are described in F01375.

• r2124 (alarm value) — read it hexadecimal as ddccbbaa to identify the connection number, the component number, the component class and the component that has not been inserted for this Terminal Module alarm.

No acknowledgement is required for this alarm. The remedy is to correct the topology itself — either insert the components involved at the right connection or adapt the project/parameterizing in the commissioning tool — as described under checks.