11
1. Introduction
ÖEach LUFP9 gateway is shipped pre-configured so as to make it easier to operate and the factory settings
can be used as a basis for a configuration which will best meet the user’s expectations. The typical
operations applicable to this default configuration are described in chapter 6 Configuring the Gateway,
page 40.
The DeviceNet network is totally separate from the Modbus network. The frames on a network are not directly
“translated” by the gateway to generate frames on the other network. Instead, the exchanges between the content
of the gateway’s memory and the Modbus slaves make up a system which is independent of the one which is
entrusted with managing the exchanges between this same memory and the DeviceNet master.
So the user must ensure that the size of the DeviceNet data corresponds to the size of the memory used for the
Modbus exchanges, because the gateway configures its DeviceNet exchanges on the basis of the memory used
by the Modbus frames.
The two synopses which follow illustrate the independent management of each of the two networks:

— Managing Gateway

↔

Modbus slaves exchanges —

Slave
A
Command A1
Quer
y
A1RQ
• • • Data
(
Out
)
• • •
Frame →
Response A1AQ
• • • Data
(
In
)
• • •
Frame →
Slave B
Command B1
Quer
y
B1RQ
• • • Data
(
Out
)
• • •
Frame →
Response B1AQ
• • • Data
(
In
)
• • •
Frame →
–
–
–
–
–
–
–
–
ABC Configurator Configuration of
Modbus exchanges
by the user

LUFP9 gateway

0x0000
0x01FF
:
Input
memory
:
0x0200
0x03FF
:
Output
memory
:
:
Managing
exchanges with the
Modbus slaves
Slave A Slave B

Modbus network

Transfer of the configuration