Siemens Simatic Operating Instructions Manual page 105

Mode Module /
submodule for which
the diagnostic infor-
mation is signaled
Manager Node
Manager Node
Manager Node
Manager Node
Manager Node
Manager Node
Manager Node
Manager Node
Manager Node
Manager Node
SIMATIC PN/CAN LINK
Operating Instructions, 03/2018, A5E39895388-AB
Channel diagnostics Cause of error and possible solution
error
Error control (heart- No heartbeat message has been received from the node
beat or node guarding) within the specified time or the node has not responded to
signals an error a node guarding request within the set monitoring time. If
the message occurred during startup, the start procedure
is repeated for all nodes. In all other cases the reaction
configured under "Reaction to failure of node" is executed.
Error control (heart- The node signals an unexpected network status (NMT
beat or node guarding) status).
in unexpected status
Signaled NMT status {1:x}.
If the message occurred during startup, the start proce-
dure is repeated for all nodes. In all other cases the reac-
tion configured under "Reaction to failure of node" is
executed.
Error when starting: Errors were detected when starting the node. Details are
Group message output in one or more additional diagnostic messages.
Depending on the "Node is mandatory on the network"
setting, the node is restarted or all nodes are restarted.
Error when starting: The node has not responded to a request (OD 1000) for
Node is not respond- 30 seconds.
ing Check whether the node is correctly connected to the CAN
bus and that it is not in "Stopped" state.
The start operation is continued.
Error when starting - -
Error {1:x}
Error when starting - During startup no heartbeat or node guarding message
No response of the was received from this node within the specified time.
error control (heartbeat
or node guarding)
Error when starting - The device type ID ({1:x}) of the node differs from the
Different device type configured device type ID.
ID (OD 1000) Check whether the correct device is connected and the
right EDS file was loaded. If the device type ID is 0, the ID
could not be read by the device.
Error when starting - The Manufacturer ID ({1:x}) of the node differs from the
Different Manufacturer configured Manufacturer ID.
ID (OD 1018.1) Check whether the correct device is connected and the
right EDS file was loaded. If the Manufacturer ID is 0, the
ID could not be read by the device.
Error when starting - The product code ({1:x}) of the node differs from the con-
Different product code figured product code.
(OD 1018.2) Check whether the correct device is connected and the
right EDS file was loaded. If the product code is 0, the
code could not be read by the device.
Error when starting - The version number ({1:d}.{2:d}) of the node differs from
Different version num- the configured version number.
ber (OD 1018.3) Check whether the correct device is connected and the
right EDS file was loaded. If the version number is 0, it
could not be read by the device.
10.2 Diagnostic messages to the S7 controller
Diagnostics
103