Siemens SIMATIC PN/CAN LINK, Operating Instructions Manual

Page: 148 / 170

Diagnostics
11.2 Diagnostic messages to the S7 controller
SIMATIC PN/CAN LINK
Operating Instructions, 03/2022, A5E39895388-AC
147
Mode Module / submodule
for which the
diagnostic information
is signaled
Channel diagnostics error Cause of error and possible solution
Manager,
Slave,
Transparent
CANopen Manager
CANopen Slave
CAN transparent
Internal communication
error detected.
Received and sent CAN messages may have
been lost.
Check for communication problems caused by
EMI. If these can be excluded, there may be a
hardware fault and the module must be
replaced.
Manager Node Error control (heartbeat or
node guarding) signals an
error
No heartbeat message has been received from
the node within the specified time or the node
has not responded to 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.
Manager Node Error control (heartbeat or
node guarding) in
unexpected status
The node signals an unexpected network
status (NMT status).
Signaled NMT status {1:x}.
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.
Manager Node Error when starting: Group
message
Errors were detected when starting the node.
Details are 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.
Manager Node Error when starting: Node is
not responding
The node has not responded to a request (OD
1000) for 30 seconds.
Check whether the node is correctly connected
to the CAN bus and that it is not in "Stopped"
state.
The start operation is continued.
Manager Node Error when starting - Error
{1:x}
-
Manager Node Error when starting - No
response of the error
control (heartbeat or node
guarding)
During startup no heartbeat or node guarding
message was received from this node within
the specified time.
Manager Node Error when starting -
Different device type ID (OD
1000)
The device type ID ({1:x}) of the node differs
from the configured device type ID.
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.
Manager Node Error when starting -
Different Manufacturer ID
(OD 1018.1)
The Manufacturer ID ({1:x}) of the node differs
from the configured Manufacturer ID.
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.