29
4. Software Implementation of the Gateway
4.2.6. Configuring Inputs from the Gateway
On the “Input” tab, select the “LUFP9” gateway, then click on the “AutoMap” button. RsNetWorx then
automatically establishes the correspondence between the 32 data bytes (8-bit format) from the gateway and the
corresponding 16 PLC inputs “I:1.1” to “I:1.16” (16-bit format).
Please check that a correspondence between all of the data from the gateway and the PLC inputs “I:1.1” to
“I:1.16” has been established.
The correspondence between the contents of the gateway’s input memory (see chapter 8.2.1 Input Data Memory
Area, page 84) and PLC inputs “I:1.1” to “I:1.16” is given in the following table:
Description
Service PLC input Bit 0......................Bit 7 Bit 8 ...................Bit 15
LUFP9 gateway status word
Managing the downstream
Modbus network I:1.1 (MSB Æ 16#xx••) (LSB Æ 16#••xx)
I:1.2 Value of the motor starter c status register
I:1.3 Value of the motor starter d status register
I:1.4 Value of the motor starter e status register
I:1.5 Value of the motor starter f status register
I:1.6 Value of the motor starter g status register
I:1.7 Value of the motor starter h status register
I:1.8 Value of the motor starter i status register
Periodic communications
—
Monitoring of
TeSys U motor starters
I:1.9 Value of the motor starter j status register
I:1.10 Memory location free Slave no. (16#01-16#08)
I:1.11 Function number (16#03) Number of bytes
read (16#02)
Value of the parameter read
Aperiodic communications
—
Reading the value of a
motor starter parameter (RESPONSE)I:1.12 (MSB Æ 16#xx••) (LSB Æ 16#••xx)
I:1.13 Slave no. (16#01-16#08) F unction no. (16# 06)
Address of the parameter written
I:1.14 (MSB Æ 16#xx••) (LSB Æ 16#••xx)
Value of the parameter written
Aperiodic communications
—
Writing the value of a
motor starter parameter (RESPONSE)I:1.15 (MSB Æ 16#xx••) (LSB Æ 16#••xx)
Aperiodic communications
(“Trigger bytes” for the responses) I:1.16 Read parameter
response counter
Write parameter
response counter