IFM Ecomat 300 AC1375, Руководство по эксплуатации устройства

Страница: 491 / 523

ifm Device manual AS-i M4 Gateway Profibus DPV1 (AC1375, AC1376) 2012-02-23
Troubleshooting AS-i master command errors – error codes M01...M44
491
Error message Cause(s) Remedy
New address only stored temporarily
During the readdressing of a slave the new
address could not be written to the slave because
the slave is no longer detected on the AS-i bus.
Possible causes:
1. Double addressing. 
M04
M08
2. Major bus interference. ► Remove the cause of the interference.
M09 Extended ID1 temporarily stored
While writing the "ID Code 1" to the slave the
code could not be written to the slave because the
slave is no longer detected on the AS-i bus.
Possible causes:

Double addressing.

Major bus interference.

M08
M10 Slave not in LAS
The master detects that a slave has not been
activated.
Possible causes:
The slave profile in the projection data is not
identical with the profile of the detected slave and
the master is in the "Protected Mode".
► Switch master to the operating mode
"Projection mode":

How to switch the operating modes for
the AS-i master. ( → page 117 )
► Check and replace slave.
► Reproject slaves:
[Menu] > [Quick Setup]:

Finish configuration ( → page 128 )
Slave data invalid
This error message has a multiple meaning and
thus depends on the requested command:
1. Readdressing of the slave
Address 32 = 0B was indicated as target
address. Address 0B is not valid.
► Indicate valid address.
M11
2. Write parameters
The attempt has been made to write a value
greater than 7
hex
to an A/B slave, ID=A
hex
.
► Indicate valid value.
Sequence failure
During the transfer according to the "7.4 slave
protocol" the master detected an error in the triple
sequence of the slave.
Possible causes:
1. Interference on the bus. ► Remove the cause of the interference.
M12
2. Software error in the AS-i slave. ► Contact AS-i specialist or manufacturer.
M13 Timeout during sequence transmission
(for gateway: reserved)
During the transfer to the "7.4 Slave protocol" the
master detected a timeout in the communication
with the operating system.
Possible cause:

Long PLC cycle which slows down the
transfer of the individual 7.4 segments from
the operating system or PLC to the master to
an unacceptable degree: t > 1 sec.

If this case occurs, the master will end the
7.4 transfer started last and will again enter
into normal data exchange with the
respective slave.
► Shorten cycle by optimising the PLC
program.
► Avoid program loops and complex
arithmetic operations.