Beckhoff CX-B930 Series, Руководство пользователя

Страница: 41 / 48

Error handling and diagnostics
CXxxxx-M930/B930 41 Version: 1.1
Number Text Description Remedial action / rea-
son
0 No error No error No error
1 PROFINET Device state
machine is in boot mode PROFINET Device State
Machine is still in the
start-up phase Not an error, wait
2 Device not found Device does not reply to
the Identify Request Check connection, device
connected, was the
device called by its correct
name?
3 The stationname is not
unique The station name is not
unique There are two or more
devices in the network
with the same PROFINET
name. A correct
identification cannot take
place.
4 IP could not set IP address could not be
set. The PROFINET device
has rejected the IP
settings for some reason.
Check whether the IP
settings are correct.
5 IP conflict An IP conflict has
occurred in the network. A possible cause is that
several devices have the
same IP address.
6 DCP set was not
successful There was no reply or an
erroneous reply to a DCP
Set. Check connection, device
connected, was the
device called by its correct
name?
7 Watchdog error The connection was
broken off with a
Watchdog error. Check the cycle time,
check the connection, if
necessary increase the
Watchdog factor.
8 Datahold error The connection was
broken off with a Datahold
error. Frame Data status was
invalid for the length of the
DataHoldTimer. Restart
the device if necessary.
9 RTC3: Sync signal could
not be started For IRT only: the Sync
signal could not be
started. Is EtherCAT Sync signal
correct or has Sync0
started?
10 PROFINET Controller has
a link error The PROFINET controller
has no link. Check cable and
connection.
11 The aliasname is not
unique The alias name is not
unique There are two or more
devices in the network
with the same alias name.
This is made up of the
neighborhood information
(PortId.ChassisId). A
correct identification
cannot take place.
12 The automatic name
assignement isn't possible
- wrong device type The automatic name
assignment is not
possible. The expected PROFINET
device is not in the
projected position
(VendorId or DeviceId
does not correspond).
Hence, no automatic
naming and thus no
device start is possible.