Manual
Table Of Contents
- ENGLISH
- FRANCAIS
- 1 Mise en oeuvre matérielle
- 2 Mise en oeuvre logicielle
- 3 Protocoles Modbus et Ethernet TCP/IP Modbus
- 3.1 Généralités
- 3.2 Exemples d’application
- 3.2.1 Montage
- 3.2.2 Configuration matérielle de l’automate avec PL7 PRO (V4.3 ou supérieure)
- 3.2.3 Exemple de programmation d’une requête pour la station @ 2
- 3.2.4 Configuration de l’automate avec Unity PRO XL V1.0.1
- 3.2.5 Lecture de 5 mots dans l’étiquette à partir de mot %MW 0 de l’étiquette dans la station @ 2
- 4 Diagnostic
- 5 Glossaire
29
Modbus and Ethernet Modbus TCP/IP protocols
English
W916556680111
Ethernet Modbus TCP/IP protocol
Modbus TCP/IP encloses a Modbus frame inside a TCP/IP frame.
The Ethernet network is used as a channel for data exchanges between the
splitter box and other equipment (PLCs, etc).
The splitter box supports up to 8 active sockets. Simultaneous Modbus TCP/IP
requests are automatically queued to the Ositrack compact stations.
Supported requests:
We can differentiate two types of requests:
- the requests addressed to servers,
- the requests addressed to the Modbus client, so to the box itself.
Requests addressed to the Modbus servers
The XGS Z33ETH box is transparent with regard to these requests: they extract
the Modbus request of the TCP/IP frame and send it on the Modbus network.
When it receives the server reply, it returns it to the transmitter by Ethernet after
having inserted it in a TCP/IP frame. All Modbus requests are accepted by the
XGS Z33ETH box, but only the requests supported by the connected servers can
be used. All others will return an exception error code.
For further details concerning the Modbus function supported by the Ositrack
station, refer to the user guide delivered with the compact station
(DIA4ED3051001).
Requests addressed to the Modbus client
The XGS Z33ETH box supports only the identification request (2BH function).
This request will be used principally to read the software version of the box. To
address the box you must use the address 255.
2BH identification requests:
NB : It exists 3 types of identification : "Basic", "Regular", "Extended". The type of
identification is selected by the field value "Read Device ID Code". The 3 types of
identification are supported, but the given reply is identical for the 3 types, and
corresponds to the type of identification "Basic".
Field Length Code (H=Hexadecimal) Remark
Address 1 byte FFH client Adress
Function code 1 byte 2BH -
MEI 1 byte 0EH
Modbus Encapsulated
Interface
Read Device ID
Code
1 byte
01H (BASIC identification)
02H (REGULAR BASIC)
03H (EXTENDED identification)
-
Objet ID 1 byte 00H -