A01900 — PB/PN: Configuration telegram error

A01900 — titled PB/PN: Configuration telegram error in the S120/S150 and G130/G150 manuals and PROFIBUS: Configuration telegram error on the G120, G120C and G120XA — appears when a controller tries to open a connection with a configuring telegram the drive cannot accept: what the master offers does not fit the drive as it is currently configured. The drive stores an alarm value in r2124, to be read as a decimal number, that names the exact mismatch. The same condition can also be issued as a fault, depending on how the drive is configured.

• A controller attempts to establish a connection using a configuring telegram that does not match the drive's configuration — every manual describes the code with this one trigger.
• Which part of the telegram is rejected is told by the alarm value: the S120/S150 and G130/G150 manuals describe the complete set, values 1 through 257 plus 500 to 503.
• The G120 and G120XA manuals list only what their interfaces can produce — 2, 3 and 211, plus 501 and 502 for PROFIsafe on the G120.

1. Check the bus configuration on both ends: on the master and on the drive (slave) side.
2. Alarm value 1 or 2: check the list of drive objects with process data exchange in p0978. An entry 0 at p0978[x] takes every following drive object in the list out of the process data exchange.
3. Alarm value 2: compare the number of data words configured for input and output with what the drive object provides.
4. Alarm value 211: make sure the offline version is not newer than the online version.
5. Alarm values 223 and 500: check the settings in p8839 and p8815, look for a CBE20 that is inserted but not configured, and make sure only one PZD interface runs in clock synchronism or with PROFIsafe.
6. Alarm value 255 or 256: check the configured drive objects and the configured telegram.
7. Alarm value 257: check the number of data words for output and input of the complete device.
8. Alarm value 501: check the PROFIsafe address in p9610; the G120 manual adds the F-DI enable in p9501.
9. Alarm value 502: check the PROFIsafe telegram set in p60022 and p9611; the G120 manual again names the F-DI enable in p9501.

The message value %1 carries the alarm value; the drive stores it in r2124, to be read as a decimal number.

• 1 — more drive objects connected than the device is configured for; the process-data drive objects and their sequence are in p0978.
• 2 — too many PZD data words for output or input to one drive object; the number of indices in r2050/p2051 sets the limit.
• 3 — an uneven number of bytes for input or output.
• 4 — setting data for synchronization not accepted; the manual refers to A01902 for details.
• 211 — unknown parameterizing block.
• 223 — the clock synchronization set in p8815[0] is not permissible — more than one PZD interface runs in clock synchronism.
• 253 — PN Shared Device: an illegal mixed configuration of PROFIsafe and PZD.
• 254 — PN Shared Device: a slot/subslot is assigned twice.
• 255 — PN: the configured drive object and the existing drive object do not match.
• 256 — PN: the configured telegram cannot be set.
• 257 — PN Shared Device: too many PZD data words for output or input in the overall device.
• 500 — illegal PROFIsafe configuration on the interface set in p8815[1] — more than one PZD interface is operated with PROFIsafe.
• 501 — PROFIsafe parameter error, e.g. a wrong F_dest.
• 502 — the PROFIsafe telegram does not match.
• 503 — the PROFIsafe connection is rejected until an isochronous connection exists (p8969).

Any other value is meant only for internal Siemens troubleshooting.

• r2124 — alarm value: read it here as a decimal number to find the matching entry above.
• p0978 — list of the drive objects: it defines which drive objects exchange process data and in which sequence; check it for values 1 and 2.
• r2050 / p2051 — PZD receive and send words of the interface: their number of indices sets how many PZD words a drive object accepts (value 2).
• p8815 — PZD functionality selection of the interfaces: index [0] is the setting checked for clock synchronism (223), index [1] the one checked for PROFIsafe (500).
• p8839 — hardware assignment of the PZD interfaces: check it together with p8815 when 223 or 500 comes up.
• p8969 — PROFIsafe wait for clock synchronization: value 503 is raised while no isochronous connection exists.
• p9610 — PROFIsafe address of the Control Unit: check the set address for value 501.
• p60022 / p9611 — PROFIsafe telegram selection: check the set telegram for value 502.
• p9501 — enable of the safety functions: on the G120, check here that the F-DI is enabled for values 501 and 502.

No acknowledgement is needed for the alarm: correct the bus configuration so that the configuring telegram matches, and the message clears by itself once the controller reconnects. If the drive is set up to raise the same condition as a fault, acknowledge that fault before restarting. The manuals describe no further restart step for this code.