beautypg.com

10 monitoring, 1 interruption of ethercat communication, Monitoring – Lenze E84AYCET EtherCAT MCI module User Manual

Page 82

background image

10

Monitoring

10.1

Interruption of EtherCAT communication

82

Lenze · E84AYCET communication module (EtherCAT) · Communication Manual · DMS 5.0 EN · 05/2013 · TD17

_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _

10

Monitoring

10.1

Interruption of EtherCAT communication

An interruption of the EtherCAT communication in the "Operational" state, e.g. due to cable break

of failure of the EtherCAT master, is detected by the slave.
The response to an interrupted communication is triggered by settings in the Monitoring tab:

• During the initialisation of the EtherCAT communication, the sync manager watchdog

monitoring time determined in the master is transferred to the slave.
If the slave does not receive any valid process data in the "Operational" status, the setting in

C13885

is taken as a basis for the process data:

• Value ’0’: The data sent last by the master are used.
• Value ’1’: PDOs are set to the value '0'.

After the watchdog monitoring time has elapsed, the slave changes to the "Safe operational"

state (see

C13861

) and the green LED BS is activated (see

Fieldbus status displays

( 86)

).

There is no response in the slave.

• In order that a response is triggered in the slave, you have to set a

Reaction on

communication failure (

C13880/1

).

• The response is delayed if you set an internal

monitoring time (

C13881

) in addition.

In the Lenze setting (

C13881

= 0), no delay is set.

The monitoring time elapses as soon as the "Operational" state is exited. (See 1.).
After the monitoring time has elapsed, the response set is executed with the error message

"

Operational status quit [0x01bc8131]

"

( 95)

.