ProSoft Technology 5202-DFNT-MCM4 - Manual (Page 23)

MCM Protocol Configuration MCM ♦ ProLinx Gateway
Driver Manual Modbus Master/Slave
ProSoft Technology, Inc.
Page 23 of 80
October 16, 2009
3.1.19 Bit Input Offset
0 TO 3999
When the port is configured as a slave, this parameter specifies the internal
database address to use as the zero address or starting point for binary Input
Status data. Input Status data is read-only data, requested by Modbus Function
Code 2 commands (Read Input Status). For example, if this parameter is set to
150 and a Function Code 2 command is received requesting Input Status
address 0 (virtual Modbus Address 10001 or 100001), the data returned in the
response will be the bit value at register 150, bit 0 in the gateway's database.
3.1.20 Word Input Offset
0 TO 3999
When the port is configured as a slave, this parameter specifies the internal
database address to use as the zero address or starting point for Input Register
(16-bit integer) data. Input Register data is read-only data, requested by Modbus
Function Code 4 commands (Read Input Registers). For example, if this
parameter is set to 500 and a Function Code 4 command is received requesting
Input Register address 0 (virtual Modbus address 30001 or 300001), the data
returned in the response will be the value at register 500 in the gateway's
database.
3.1.21 Output Offset
0 TO 3999
When the port is configured as a slave, this parameter specifies the internal
database address to use as the zero address or starting point for binary output
Coil data. Coil data is read by Modbus Function Code 1 commands (Read Coils)
and written by Function Codes 5 (Force Single Coil) or Function Code 15 (Force
Multiple Coils). For example, if this parameter is set to 50 and a Function Code 1
command is received requesting Coil address 0 (virtual Modbus Coil address
00001 or 000001), the data returned in the response will be the value at register
50, bit 0 in the gateway's database.