
AN00174-001 Modbus TCP Fieldbus Option for MotiFlex e100.doc
2
22
2 of
of of
of 22
2222
22
A wide range of fieldbus modules are available (contact your local Baldor office or distributor for a
full list):
• Carrier card: OPT-MF-030
• DeviceNet: OPT-FB-001 (Anybus AB6201)
• PROFIBUS DP-V1: OPT-FB-002 (Anybus AB6200)
• EtherNet/IP: OPT-FB-004 (Anybus AB6214)
• Modbus/TCP: OPT-FB-005 (Anybus AB6213)
• PROFINET IO: OPT-FB-006 (Anybus AB6215)
Separate application notes are available on setting up these alternative Fieldbus Options.
Modbus/TCP Function Codes
The Modbus/TCP Fieldbus Option supports the following Modbus function codes:
• 1 - Read Coils
• 2 - Read Discrete Inputs
• 3 - Read holding Registers
• 4 - Read Input Registers
• 5 - Write Single Coil
• 6 - Write Single Register
• 15 - Write Multiple Coils
• 16 - Write Multiple Registers
• 23 - Read/Write Multiple Registers
• 43 - Read Device Identification
Modbus/TCP Register Implementations
The Modbus/TCP Holding (4x) Registers are mapped as follows:
Modbus Register Range Contents
0000 – 00FF hex (0 to 255 dec) Read Process Data (data written by PLC)
0100 – 01FF hex (256 to 511 dec) Write Process Data (data read by PLC)
0210 – FFFF hex (528 to 65535 dec) Application Data Instances (ADIs)
The Modbus/TCP Input (3x) Registers are mapped as follows:
Modbus Register Range Contents
0000 – 00FF hex (0 to 255 dec) Write Process Data (e.g. Input register 0 is
mapped to Modbus Register 0100 hex)
The Modbus/TCP Discrete Input (1x) Registers are mapped as follows:
Modbus Register Range Contents
0000 – 0FFF hex (0 to 4095 dec) Write Process Data (e.g. Discrete Input
register 0 is mapped to Modbus Register 0100
hex)
The Modbus/TCP Discrete Output (0x) Registers are mapped as follows:
Modbus Register Range Contents
0000 – 0FFF hex (0 to 4095 dec) Read Process Data (e.g. Discrete Output
register 0 is mapped to Modbus Register 0000
hex)
Komentarze do niniejszej Instrukcji