F01325 — Topology: Component number not present in target topology

F01325 — Topology: Component number not present in target topology — is raised when the component configured in a parameter is not present in the target topology. The manuals for G130, G150, S120 and S150 describe the code identically and name p0121 and p0131 as example parameters in which such a component number can be configured. The fault value in r0949 identifies the configured component number the drive cannot find, and the message value displays the same component number.

• A component number configured in a parameter (for example p0121 or p0131) refers to a component that is not present in the target topology.

1. Read the fault value in r0949 and interpret it as a decimal number — it contains the configured component number that is not present in the target topology.
2. Check the parameters in which component numbers are configured, for example p0121 (power unit component number) and p0131 (motor component number), for an entry that references this component number.
3. Establish consistency between the topology and the DO configuration, so that every component number configured in a parameter corresponds to a component present in the target topology.
4. Acknowledge the fault immediately after the configuration has been corrected.

• Message value: Component number: %1 — the drive enters the number of the configured component here.
• Fault value: r0949, interpreted as a decimal number, contains the configured component number that is not present in the target topology.

• p0121 — Power unit component number (PU comp_no): one of the parameters that can hold the component number missing from the target topology; check its setting for this code.
• p0131 — Motor component number (Mot comp_no): another example of a parameter that can configure the missing component number; check its setting for this code.
• r0949 — fault value: read it as a decimal number to identify the configured component number the drive cannot find in the target topology.

The fault requires an immediate acknowledgement. It triggers no automatic response from the drive — it signals an error in the configuration — so once the topology and the DO configuration have been made consistent, acknowledging the fault immediately is all that is needed to clear it.