F01360 — Topology: Actual topology not permissible

F01360 means that the drive has detected an actual topology that is not permissible — the components actually connected, and the way they are arranged, do not form a valid configuration. The manuals describe this fault identically for every family listed, so the information below applies to all of them. The fault value in r0949 identifies the preliminary component concerned and one of eleven fault causes. While the fault is present the drive system does not boot, and in this state the drive control (closed-loop) cannot be enabled.

• Too many components were connected: more than the permissible maximum of 199 components at the Control Unit, too many components of a particular type, or too many components of a particular type on a single line.
• A component with an unknown component type is connected.
• An inadmissible combination is installed: ALM with BLM, ALM with SLM, or BLM with SLM.
• An expansion module (CX32, or NX10 or NX15) is not directly connected to a permitted Control Unit.
• A component is connected to a Control Unit that is not permitted for this purpose.
• A component is connected to a Control Unit with out-of-date firmware.

1. Read the fault value in r0949 hexadecimal as ccccbbaa: aa gives the fault cause, cccc the preliminary component number of the component concerned.
2. Cause 1: change the configuration and connect less than 199 components to the Control Unit.
3. Cause 2: remove the component with the unknown component type.
4. Causes 3 to 5: establish a valid combination, because ALM with BLM, ALM with SLM and BLM with SLM are illegal.
5. Causes 6 and 7: connect the expansion module directly to a permitted Control Unit.
6. Cause 8: remove the component or use a permissible component.
7. Cause 9: upgrade the firmware of the Control Unit to a later version.
8. Causes 10 and 11: reduce the number of components.
9. Acknowledge the fault once the actual topology is permissible.

The drive enters the fault value in r0949; interpret it hexadecimal as ccccbbaa hex: cccc = preliminary component number, bb = no significance, aa = fault cause. The message value is shown as: Fault cause: %1, preliminary component number: %2. The manual decodes aa as follows:

• 01 hex = 1 dec: Too many components were detected at the Control Unit. A maximum of 199 components is permissible.
• 02 hex = 2 dec: The component type of a component is not known.
• 03 hex = 3 dec: It is illegal to combine ALM and BLM.
• 04 hex = 4 dec: It is illegal to combine ALM and SLM.
• 05 hex = 5 dec: It is illegal to combine BLM and SLM.
• 06 hex = 6 dec: A CX32 was not directly connected to a permitted Control Unit.
• 07 hex = 7 dec: An NX10 or NX15 was not directly connected to a permitted Control Unit.
• 08 hex = 8 dec: A component was connected to a Control Unit that is not permitted for this purpose.
• 09 hex = 9 dec: A component was connected to a Control Unit with out-of-date firmware.
• 0A hex = 10 dec: Too many components of a particular type detected.
• 0B hex = 11 dec: Too many components of a particular type detected on a single line.

• r0949 — fault value: read the fault cause (aa) and the preliminary component number (cccc) for this fault here, interpreting the value hexadecimal as ccccbbaa.

The note for this fault states: The drive system is no longer booted. In this state, the drive control (closed-loop) cannot be enabled. The topology must therefore be corrected first, following the remedy for the fault cause shown in r0949. Once the detected actual topology is permissible, acknowledge the fault immediately; the drive system boots again and the drive control (closed-loop) can be enabled.