A50010 — PNCOMM BOARD: Consistency error affecting adjustable parameters

A50010 is raised when the drive tries to activate a new Ethernet configuration and the settings fail the drive's internal consistency check. On the G120 and G120XA it concerns the integrated PROFINET interface, activated with p8925; on the G130 and G150 it concerns the Communication Board Ethernet 20 (CBE20), activated with p8945. The manuals print the message as PROFINET: Consistency error affecting adjustable parameters and, for the CBE20, PNCOMM BOARD: Consistency error affecting adjustable parameters; on the G120C it appears as PROFINET name of station invalid. The outcome is the same in every case: the currently set configuration has not been activated — the drive keeps the configuration that was in effect before. Depending on how the drive is configured, the same condition can also be issued as fault F50010.

• The drive detected a consistency error while activating the configuration of the Ethernet interface — with p8925 for the PROFINET interface (G120, G120XA, G120C) and with p8945 for the CBE20 (G130, G150).
• The settings that are checked together are the station name, the IP address, the standard gateway, the subnet mask and the DHCP mode (p8920 and following for PROFINET, p8940 and following for the CBE20).
• According to the alarm value, the concrete inconsistency is an error in the IP configuration (IP address, subnet mask or standard gateway), an error in the station names, or a conflict between DHCP and a cyclic PROFINET connection in one direction or the other.
• For all alarm values, the currently set configuration has not been activated.

1. Read the alarm value in r2124 and interpret it as a decimal number — it tells you which part of the configuration failed the check.
2. Check the interface configuration: p8920 and following for the PROFINET interface, p8940 and following for the CBE20 — station name, IP address, default gateway, subnet mask, DHCP mode.
3. Correct the parameters that do not fit together; on the G120C the manual points directly at the station name (p8920).
4. Activate the corrected configuration again: p8925 for the PROFINET interface — the G120C manual gives the value p8925 = 2 — and p8945 for the CBE20.
5. Alternatively, reconfigure the station via the "Edit Ethernet node" screen form, for example with the STARTER commissioning software.

• The drive stores the alarm value in r2124; read it as a decimal number.
• 0: general consistency error.
• 1: error in the IP configuration (IP address, subnet mask or standard gateway).
• 2: error in the station names.
• 3: DHCP was not able to be activated, as a cyclic PROFINET connection already exists.
• 4: a cyclic PROFINET connection is not possible as DHCP is activated.
• DHCP stands for Dynamic Host Configuration Protocol.
• For all alarm values: the currently set configuration has not been activated.

• r2124 — alarm value of this message; read it as a decimal number to identify the failed check (0 to 4).
• p8920 — PN name of station: check and correct the PROFINET station name.
• p8921 — PN IP address: check and correct the IP address.
• p8922 — PN default gateway: check and correct the standard gateway.
• p8923 — PN subnet mask: check and correct the subnet mask.
• p8924 — PN DHCP mode: check whether the DHCP setting fits the cyclic PROFINET connection (alarm values 3 and 4).
• p8925 — activates the PROFINET interface configuration after you have corrected the settings; on the G120C activate with p8925 = 2.
• p8940 — CBE20 name of station: station name of the Communication Board Ethernet 20.
• p8941 — CBE20 IP address.
• p8942 — CBE20 default gateway.
• p8943 — CBE20 subnet mask.
• p8944 — CBE20 DHCP mode.
• p8945 — activates the CBE20 interface configuration after correction.

The alarm needs no acknowledgment of its own — it is a report that a configuration activation was rejected. It is cleared by doing what the remedy says: correct the interface parameters and start a new activation with p8925 (PROFINET interface) or p8945 (CBE20). If the drive is configured to raise the condition as fault F50010 instead, the drive does not execute OFF1, OFF2 or OFF3, and the fault is acknowledged immediately once the corrected configuration has been activated.