Schneider Electric LUFP9

6. Configuring the Gateway

6.11.2.1. Managing Degraded Modes

Due to the number of hardware elements and software tools used, the following table shows a summary of the

various degraded modes in a DeviceNet application. In this case, this application includes an LUFP9 gateway,

but we will not be including either the master PLC or its scanner:

Event

Desired behaviour DeviceNet PLC:

CPU stop or failure

Disconnection of the

upstream DeviceNet

network (1)

Failure of the

LUFP9 gateway

(2)

Disconnection

of the downstream

Modbus RTU

network (1) (2)

Reset “Offline options for

fieldbus” = “Clear”

Hold

Depending on the

configuration

of the DeviceNet

master

“Offline options for

fieldbus” = “Freeze”

Depending on the configuration

of the Modbus slaves

Outputs

Stop refresh —— “Offline options for

fieldbus” = “No Scanning” ——

Reset —— “Offline options for sub-

network” = “Clear”

Inputs

Hold ——

Depending on the configuration

of the DeviceNet master “Offline options for sub-

network” = “Freeze”

(1) The “Offline options for fieldbus” and “Offline options for sub-network” are described in the next chapter.

(2) The behaviour desired with regard to the outputs should be directly configured on each of the Modbus

slaves. In the case of drives marketed by Schneider Electric, for instance, resetting the outputs is

configured by setting the NTO bit to 0 (communication control), and they are held by setting NTO to 1

(suppression of communication control).

You can also read the user manuals for your master and your DeviceNet scanner to obtain further details about

how to process degraded modes.