Schneider Electric LUFP9

4. Software Implementation of the Gateway

If you are in any doubt over what is displayed, click on the “Upload From Device” button, then on “Start Monitor”. The

RsNetWorx application then starts to read from the gateway the values of the parameters currently displayed.

Click on the “Stop Monitor” button to stop this reading process.

The most important parameters, in the case of the default gateway configuration, are parameters 1 and 2

(periodic transfers between the PLC and the gateway via a periodic connection known as “polled”), 6 and 7

(offset and size of the input data area in the gateway’s input memory), and 18 and 19 (offset and size of the

output data area in the gateway‘s output memory).

If you create or change a configuration using AbcConf (see chapter 6 Configuring the

Gateway, page 40), you should be aware that the values of these parameters should

correspond to the configuration of the data in the gateway’s memory, as defined in AbcConf.

This data corresponds to all of the bytes exchanged with the Modbus slaves via the “Data” or

“Preset Data” fields in the Modbus frames.

You should only check the parameters related to “Input1” and “Output1” areas. The other

parameters, related to “Input2” to “Input6” or to “Output2” to “Output6” areas, are intended for

an advanced use of the gateway, and Schneider Electric refuses to accept responsability for

their use. The operations needed to set the values of these parameters will not be described in

the current guide.

N.B. If a connection is not used, the corresponding EDS parameters are not used by the gateway. This is the

case with “Strobed” and “COS” connections (and EDS parameters nos. 3 to 5) when the default gateway

configuration is used. You can then retain the initial assignment of parameters nos. 1 to 5 to the two default input

and output areas (areas no. 1), because only the “Polled” connection (parameters nos. 1 and 2) will be activated

by the DeviceNet master.

N.B. The value of each “offset” type parameter refers to an offset from the start of the gateway’s input data

memory area or from the start of its output data memory area and not from the start of its physical memory.