Modbus Plus Fieldbus Appendix
Modbus Plus Fieldbus Appendix
Revision notes
Preface
The data and illustrations found in this manual are not binding. We reserve the right to modify our products in line
with our policy of continuous product development. The information in this manual is subject to change without
notice and should not be considered as a commitment by HMS Industrial Networks AB.
HMS Industrial Networks AB assumes no responsibility for any errors that may appear in this document.
The product and technology described in this document is patented or patent pending in the following countries:
USA, Canada, Japan, Belgium, Denmark, Finland, France, Greece, Ireland, Italy, Luxemburg, Monaco, Netherlands,
Portugal, Switzerland, Lichtenstein, Spain, United Kingdom, Sweden, Germany, Austria and others.
Table of contents
1 Fieldbus Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.1 Introduction to Modbus Plus. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
1.2 Technical Features for Modbus Plus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
1.3 Related documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
2 Module Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.1 Mechanical Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.2 Protocol & Supported Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
2.3 Physical Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4 Fieldbus data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.4.1 Global data and Point-to-point commands. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.5 Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.6 Application Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
2.7 Dual-Port RAM Memory - DPRAM (Alternative 1) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
2.8 Asynchronous serial interface (Alternative 2) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
3 Installation & Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.1 Fieldbus Connectors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.2 D-SUB connector and Screw terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.3 10 pole 2mm connector. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
3.4 Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.1 Node ID (Address) S1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.4.2 Source ID (Address) S2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
3.5 Indications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
4 Functions & Operation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1 DPRAM Structure of the Modbus Plus Module. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.1 IN/OUT Data Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
4.1.2 Mailbox Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.3 Fieldbus Specific Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
4.1.4 Control Area. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2 Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
4.2.1 Initialization Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
4.3 Data Exchange . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4 Protocol Features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.1 Global Data Base transaction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.4.2 Point-to-point data Modbus commands supported . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5 Data map from the Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
4.5.1 Data to network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
4.5.2 Data from network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
4.6 Point-to-point exception handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
4.7 Routing Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.8 Modbus Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.8.1 Read Holding Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.8.2 Preset Multiple Registers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
4.8.3 Preset Single Register . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
5 Fieldbus Specific Mailbox Commands . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.1 Fieldbus Specific Initialization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
5.2 Alter GDB Source ( SET_GDB_SOURCE ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
5.2.1 Alter Node Address ( SET_NODE_ADDRESS ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
5.2.2 Get Network Statistics ( GET_NETWORK_STATISTICS ) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
1 Fieldbus Introduction
The Modbus Plus is a local area network system designed for industrial control and monitoring applications, devel-
oped by Modicon, Inc. HMS is a member of the ModConnect program for developing Modbus Plus devices.
Technical questions regarding the fieldbus should be addressed to Modicon Inc. at www.modicon.com .
The network enables programmable controllers, host computers and other devices to communicate throughout plants
and substations. Modbus Plus is normally used in industrial automation, to transfer fast data for motor controllers,
MMI, I/O units and other industrial equipment.
The AnyBus-S Modbus Plus module communicates according to the Modbus Plus Protocol. This means that it can
communicate with all Modbus Plus nodes that comply with this protocol, but it does not necessarily mean that all ser-
vices available in the Modbus Plus protocol is supported.
DPRAM
Address & Data bus
2KB Modbus Plus
Rx ANYBUS electronics
Alternative 2
Tx
RTS
SCI
2 Module Overview
This section provides an overview over the module and describes the technical features.
Watchdog LED
Node ID S1
Source ID S2
Indication LED'S
Figure 4: AnyBus-S Modbus Plus Mechanical Overview
DPRAM
Address & Data bus
2KB Modbus Plus
Rx ANYBUS electronics
Alternative 2
Tx
RTS
SCI
10 pole 2 mm Name
1 PE
2 -
3 -
4 -
5 -
6 MBP Line A
7 -
8 -
9 MBP Line B
10 Cable Shield
3.4 Configuration
3.4.1 Node ID (Address) S1
The Node ID on the Modbus Plus node is set before power on. Any change of Node ID during power on is not valid
until next power cycle. The address is set in binary format. The Node address is also configurable with the fieldbus
specific mailbox messages, please see chapter 5.
1 2 3 4 5 6 Function
MSB LSB
ON ON ON ON ON ON Node address set to 1
ON ON ON ON ON OFF Node address set to 2
ON ON ON ON OFF ON Node address set to 3
- - - -
OFF OFF OFF OFF OFF ON Node address set to 63
OFF OFF OFF OFF OFF OFF Node address set to 64
1 2 3 4 5 6 Function
MSB LSB
ON ON ON ON ON ON Source ID address set to 1
ON ON ON ON ON OFF Source ID address set to 2
ON ON ON ON OFF ON Source ID address set to 3
- - - -
OFF OFF OFF OFF OFF ON Source ID address set to 63
OFF OFF OFF OFF OFF OFF Source ID address set to 64
3.5 Indications
The AnyBus-S Modbus Plus module has two fieldbus specific and two standard (stacked) indication LED's mounted
on the circuit board. The functionality of these LED's are described below:
This node has heard a valid packet that has a duplicated-node-address sent
from another node on the network, using the same Node ID.
4 Active solid MBP Init; This LED indicating if the peer interface is initialized
green
OUT area
200h - 3FFh Output data area; 512 Bytes RO
The fast data area of the DPRAM is represented as global data on the Modbus Plus network. The fast data mapped to
the beginning of the area. The slow data area of the DPRAM starts directly after then fast data. This data is accessed
over the Modbus Plus network by using the Modbus commands for point-to-point data transfer.
The application exchanges data with the fieldbus via the DPRAM IN and OUT data areas. Before the module can be
used, the length of the IN and OUT area has to be defined. This is accomplished during initialisation of the module.
AnyBus-S Modbus Plus has the possibility to use both fast data and slow data. The fast global data will be assigned to
I/O data. The parameter data will be the IN/OUT total length minus the cyclic I/O data, for both IN and OUT.
When using only the DPRAM memory (512 Byte):
The IN area of the AnyBus-S Modbus Plus can be configured during initialisation with a size from 0 byte to 512
bytes.
IN cyclic I/O length (7F0h-7F1h)
IN DPRAM length (7F2h-7F3h)
IN total length (7F4h-7F5h)
The OUT area of the AnyBus-S Modbus Plus can be configured during initialisation with a size from 0 byte to 512
bytes.
OUT cyclic I/O length (7F6h-7F7h)
OUT DPRAM length (7F8h-7F9h)
OUT total length (7FAh-7FBh)
If more than 512 byte IN and OUT is required, the extended IN and OUT area can be used in the AnyBus-S Modbus
Plus module.
If the Extended memory is used, there can be up to 2kB IN and OUT. To set 2kB IN/OUT length, the OUT total
length is set to 0x800 (2048 bytes). The extended memory is accessed using mailboxes on the parallel interface, and
is mapped directly to the data area of the serial module. Please see AnyBus-S Design Guide for Parallel interface for
details regarding the Initialisation.
Two types of mailbox commands can be used by the AnyBus-S Modbus Plus, Standard mailbox commands,
described in the AnyBus-S Design Guide, and Fieldbus Specific mailbox commands, described in chapter 5.
4.2 Initialization
Initialisation of the AnyBus-S module in standard format is performed with the ANYBUS_INIT mailbox telegram,
where the sizes of the input/output areas are set.
The AnyBus-S Modbus Plus module uses both I/O data and parameter data. All parameter data will be mapped after
the I/O data, ( "IN/OUT total lengths" minus "IN/OUT I/O data" ) . In the AnyBus-S Modbus Plus, I/O data is the
same as global data and parameter data the same as Modbus point-to-point data commands.
The lengths specified are also checked against their maximum size. If they do not comply, the initialisation will be
rejected.
Note: The time between the initialization command END_INIT and the flag FBRS is set (and displayed to the appli-
cation) in the register, Module Status Register (7E2h-7E3h) is 10 seconds, due to the Modbus Plus peer interface need
this amount of time to be initialized.
If action towards the Modbus Plus is requested as soon the AnyBus Modbus Plus is up and running, we recommend
to monitor the FBRS flag to be able to decide when the network is available for the application.
Note: All access on the Modbus Plus is handled in word format (16- bit word), So initialising any module data area to an odd size is not
recommended due to data consistence.
Example:
To read four words from the "Data to Network" parameter data area, use a Read Holding Registers with start address
40001 and No of register to read set to 4 this will give you the four first global data words.
Example:
To write to the first two words of the "Data from Network" parameter data in the AnyBus module use Preset Multiple
Register with the start register 41057 and No of register set to 2 words.
Note: If the OUT size is set from the application to an odd size there will be one byte that is not accessible from the
fieldbus, to get the contents of the first parameter data you will need to address the next whole new word in the
example below register 41058.
Example: If the module is initialised from the application with the following sizes...
...the first part of the "Data from Network" data map from the fieldbus will look like this:
Code Function
01h Illegal function for the addressed slave
02h Illegal data address within the information field for the addressed slave
03h Illegal data value in the information field for the addressed slave
06h Host side busy, reissue the command later
Exception Response Code 0x06 is not implemented in the AnyBus-S Modbus Plus module.
• If an unknown command is received form the network, this will cause the AnyBus S module to response with
an Exception Response 0x01.
• If a valid command with an address out of range for the AnyBus-S memory area this will cause the AnyBus S
module to response with an Exception Response 0x02.
• If the data for the commands Preset Multiple Register and Read Holding Register is invalid this will cause the
AnyBus module to response with an Exception Response 0x03.
The Exception Response is two bytes, the "Function Code" and the "Exception Code".
To write to node 5 within the same network (no bridging to another network), the five digits Routing Path should be:
5. 2. 0. 0. 0.
5 = Node ID.
2 = Slave Data Path. 1 to 8.
Note: If the Slave Data path is not equal to 1- 8 the module will interpret this as Slave Data Path 8, this mean that you
can have one extra path, routing an extra Modbus Plus network.
Parameter Description
Command initiator Application INIT MODE or RUNTIME MODE
Message Name SET_GDB_SOURCE
Message type 0x02
Command number 0x0001
Fragmented No
Extended header data No extended header data is associated with this command
Message data 4 Bytes. No of Sources, Source address , No of words, Offset within
GDB (in words).
Response message Contains: No of Sources, Source address, No of words, Offset within
GDB .The No of Sources must always be set to0x01.If the source is
producing global data on the network this will be displayed in the
Fieldbus Specific area 0x642. If the SET_GDB_SOURCE mailbox
message is wrong, see error code. If error code 0x0F is displayed see
Extended word 8 for details: 0x0001. I/O length miss match, larger
that the init settings . 0x0002. To many source addresses.
Note: A byte in the FB specific area (address 0x642) will display if the Source is producing global data.
Parameter Description
Command initiator Application INIT MODE
Message Name SET_NODE_ADDRESS
Message type 0x02
Command number 0x0002
Fragmented No
Extended header data No extended header data is associated with this command
Message data 1 Byte : the node address value. Valid data: 1 - 64.
Response message The message data contains the requested node address valueIf the
node address is valid the chosen ID will be displayed in the Fieldbus
Specific area 0x640.If the SET_NODE_ADDRESS mailbox message
is wrong, see error code. If error code 0x0F is displayed see Extended
word 8 for details: 0x0001. Node address is out of range.
Parameter Description
Command initiator Application RUNTIME MODE
Message Name GET_NETWORK_STATISTICS
Message type 0x02
Command number 0x0003
Fragmented No
Extended header data No extended header data is associated with this command
Message data 2 Bytes : length (in bytes) and offset ( in bytes).
Response message The message data contains an length and offset. If the
GET_NETORK_STATISTICS mailbox message is wrong, see error
code. If error code 0x0F is displayed see Extended word 8 for details:
0x0001. Offset + Length is out of range.
Parameter Description
Command initiator Application RUNTIME MODE
Message Name CLEAR_COMM_COUNTERS
Message type 0x02
Command number 0x0004
Fragmented No
Extended header data No extended header data is associated with this command
Message data No data is associated with this command.
Response message No data is associated with this command.
If the CLEAR_COMM_COUNTERS mailbox message is wrong,
see error code.
6 Electrical specification
The table below describes the general pin configuration for the Application interface.
For further information regarding timing and electrical characteristics of the DPRAM, please see Cypress Data Book,
type CY7C136.
7 Module mechanics
This chapter includes drawings of the module for overview and mechanical design.
The drawings describe the standard configuration of the AnyBus-S Modbus Plus module.
The fieldbus interface can be either side or top mounted.
Reverse mounting is not allowed on the 9 pin D-sub connector.
Connectors that are supported by the AnyBus-S Modbus Plus module are:
· 9 pin female D-SUB
· Screw terminal 3.81 mm
· Pluggable screw terminal 3.81 mm
· 10 pole 2.0 mm
For further information regarding the AnyBus-S module, we refer to the AnyBus-S Design Guide.
Note: The AnyBus S Modbus Plus is only supporting the AnyBus S PE hole configuration.
F
F
D
D
Pilefeltsgatan 93-95
C S-302 50 Halmstad C
Tel: +46 (0)35 - 17 29 00
Fax: +46 (0)35 - 17 29 09
UNLESS OTHERWISE SPECIFIED
DIMENSIONS ARE IN
MILLIMETERS. REV.
: 9 8 7 6 5 4 3
29
2001-08-06
DOC. NO ABS-MBP-1.30
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
30
: 9 8 7 6 5 4 3
F
F
DOC. NO ABS-MBP-1.30
E
E
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
15,8
14,2 13,8
15,9 15,9
9,7 8,1
8,5
22,1 D
D
Pilefeltsgatan 93-95
C C
S-302 50 Halmstad
Tel: +46 (0)35 - 17 29 00
Fax: +46 (0)35 - 17 29 09
: 9 8 7 6 5 4 3
F
F
30,8
25,0
9,2
2,9
16,7
4,6
12,6
9,7 5,0 9,7
6,3
3,2
D
D
C
Pilefeltsgatan 93-95
C
S-302 50 Halmstad
Tel: +46 (0)35 - 17 29 00
Fax: +46 (0)35 - 17 29 09
: 9 8 7 6 5 4 3
31
2001-08-06
DOC. NO ABS-MBP-1.30
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
32
: 9 8 7 6 5 4 3
2,0
F
F
37,3
2,0
DOC. NO ABS-MBP-1.30
54,0
0,8
E 3x 3,2 A E
5,8 A
0,75
0
0,9 2,54
6,2
0,8 2,54
12,9
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
14,3 2,0
D
D
1,0
2,0
71,8
86,0 1,6
0
7,0
4,0
55,5
Pilefeltsgatan 93-95
C
S-302 50 Halmstad
C
Tel: +46 (0)35 - 17 29 00
Fax: +46 (0)35 - 17 29 09
: 9 8 7 6 5 4 3
F
F
D D
: 9 8 7 6 5 4 3
33
2001-08-06
DOC. NO ABS-MBP-1.30
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
34
: 9 8 7 6 5 4 3
F
F
DOC. NO ABS-MBP-1.30
E
E
25,0
2,9
9,2
4,6
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
9,8
14,2 13,6
16,1
5,0 9,7
12,6 9,6
D
D
3,2
45,4
62,1
HM S Industrial Networks AB
Pilefeltsgatan 93-95
C
S-302 50 Halmstad C
Tel: +46 (0)35 - 17 29 00
Fax: +46 (0)35 - 17 29 09
: 9 8 7 6 5 4 3
F
F
30,9
16,7
12,2 11,9
10,2
8,1
6,7 5,5
6,0
D
D
Figure 13: AnyBus-S Modbus Plus Straight Front and Side view
6,4 - 12,2 mm
HMS Industrial Networks AB
Pilefeltsgatan 93-95
S-302 50 Halmstad
C C
Tel: +46 (0)35 - 17 29 00
Fax: +46 (0)35 - 17 29 09
: 9 8 7 6 5 4 3
35
2001-08-06
DOC. NO ABS-MBP-1.30
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
36
: 9 8 7 6 5 4 3
F 2,0
F
37,3
DOC. NO ABS-MBP-1.30
2,0
54,0 0,8
E
E
3x 3,2 A
5,8 A
0,75
0
0,9 2,54
6,2
0,8 2,54
FIELDBUS APPENDIX - ANYBUS-S MODBUS PLUS
12,9
14,3
2,0
D
D
0
71,8
2,0
1,0
86,0 1,6
0
HMS Industrial Networks AB
7,0
4,0
Pilefeltsgatan 93-95
55,5
S-302 50 Halmstad
C Tel: +46 (0)35 - 17 29 00 C
Fax: +46 (0)35 - 17 29 09
: 9 8 7 6 5 4 3
8 List of tables
Table 1: Summary technical features . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Table 2: Documents related to this manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Table 3: D-SUB connector and screw terminal . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 4: 10 pole 2 mm connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
Table 5: Switch settings for Node ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 6: Switch settings for Source ID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
Table 7: LED descriptions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Table 8: IN/OUT data area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Table 9: Mailbox Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 10: Fieldbus Specific Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 11: Fieldbus Specific Area Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13
Table 12: Control Area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Table 13: Mailbox message memory layout (ANYBUS_INIT telegram) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Table 14: Data to Network area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Table 15: Data from Network area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
Table 16: Example 2: Data from Network area . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 17: Modbus Exception Response . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Table 18: SET_GDB_SOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 19: Command and response layout: SET_GDB_SOURCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
Table 20: SET_NODE_ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 21: Command and response layout: SET_NODE_ADDRESS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
Table 22: GET_NETWORK_STATISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 23: Command and response layout: GET_NETWORK_STATISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
Table 24: CLEAR_COMM_COUNTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 25: Command and response layout: CLEAR_COMM_COUNTERS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
Table 26: Electrical pin specification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26
9 List of figures
Figure 1: Modbus Plus network overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3
Figure 2: Timing and throughput . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 3: Nodes on a Modbus Plus network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4
Figure 4: AnyBus-S Modbus Plus Mechanical Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Figure 5: AnyBus-S Access methods . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Figure 6: AnyBus-S Modbus Plus LED indication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
Figure 7: AnyBus-S Modbus Plus Angled 3-D view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29
Figure 8: AnyBus-S Modbus Plus Angled Top view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
Figure 9: AnyBus-S Modbus Plus Angled Front and Side view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
Figure 10: AnyBus-S Modbus Plus Angled PCB view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
Figure 11: AnyBus-S Modbus Plus Straight 3-D view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
Figure 12: AnyBus-S Modbus Plus Straight Top view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
Figure 13: AnyBus-S Modbus Plus Straight Front and Side view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35
Figure 14: AnyBus-S Modbus Plus Straight PCB view . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
Phone:___________________________________________________________________________________
E-mail:___________________________________________________________________________________
Comments:
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
Other comments:
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
_________________________________________________________________________________________
Send your comments to: You may also mail or fax your comments: