A01420 — Topology: Component different

The drive reports “Topology: Component different” when the topology comparison has detected differences between the actual topology and the target topology stored in the electronic rating plate. The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. The component class named in the alarm value is described in F01375. Under “Topology --> Topology view” the commissioning tool offers improved diagnostics where relevant, for example a setpoint/actual value comparison.

• The component actually connected is not the component that the target topology in the electronic rating plate expects.
• The difference can concern the component type, the article number, the manufacturer or the number of connections.
• On a multi-component slave, the wrong subcomponent (index) can be connected — for example a Double Motor Module at X201 instead of X200 — or only a part of the slave is set to “deactivate and not available”.
• An NX10 or NX15 can be connected where the project expects a CX32.

1. Read the alarm value in r2124 (interpreted hexadecimal, see below) to identify the component number, the expected and the actual component class, and the difference; the component classes are described in F01375.
2. Open “Topology --> Topology view” in the commissioning tool; where relevant it offers improved diagnostics capability such as a setpoint/actual value comparison.
3. Correct the mismatch in one of two ways: connect the expected component (this corrects the actual topology) or adapt the project/parameterization in the commissioning tool (this corrects the target topology).
4. If required, adapt the comparison level of the topology comparison: parameterize it for all components in p9906, or for one component in p9907 and p9908.

• The drive stores the alarm value in r2124 and it is interpreted hexadecimal as ddccbbaa hex: aa = component number (%1), bb = component class of the target topology (%2), cc = component class of the actual topology (%3), dd = difference (%4). The message value therefore reads: Component: %1, target: %2, actual: %3, difference: %4.
• dd = 01 hex = 1 dec: Different component type.
• dd = 02 hex = 2 dec: Different article number.
• dd = 03 hex = 3 dec: Different manufacturer.
• dd = 04 hex = 4 dec: For a multi-component slave, the incorrect subcomponent (index) is connected (e.g. Double Motor Module X201 instead of X200) — or only a part of a multi-component slave is set to “deactivate and not available”.
• dd = 05 hex = 5 dec: NX10 or NX15 used instead of CX32.
• dd = 06 hex = 6 dec: NX10 or NX15 used instead of CX32.
• dd = 07 hex = 7 dec: Different number of connections.

• r2124 — alarm value: holds ddccbbaa hex for this alarm; read it to identify the component and the type of difference.
• p9906 — comparison stage of the topology comparison for all components: parameterize this to adapt the comparison level for all components.
• p9907 — comparison stage of the topology comparison for the component number: parameterize this to adapt the comparison level for one component.
• p9908 — comparison stage of the topology comparison for a component: parameterize this to adapt the comparison level for one component.

This alarm requires no acknowledgement. The mismatch itself has to be removed: either connect the component the project expects or adapt the project/target topology in the commissioning tool. While the condition exists, the drive system is no longer booted, so the drive control (closed-loop) cannot be enabled.