![Pepperl+Fuchs IDENT-M System V MVI-F57-2HB12 Manual Download Page 20](http://html1.mh-extra.com/html/pepperl-fuchs/ident-m-system-v-mvi-f57-2hb12/ident-m-system-v-mvi-f57-2hb12_manual_1527667020.webp)
IDENT-M System V • TCP/IP connection
Communication TCP/IP <==> Control interface unit
Zumutbare Änderungen aufgrund technischer Verbesserungen vorbehalten.
Copyright Fuchs, Printed in Germany
Fuchs GmbH • 68301 Mannheim • Telefon (06 21) 7 76-11 11 • Telefax (06 21) 7 76-27-11 11 • Internet http://www.pepperl-fuchs.com
D
a
te
of
is
su
e0
6.
09
.0
1
18
8
Communication TCP/IP <==> Control interface unit
The MVI-F57-2HB12 connecting circuit is designed as a server.
A TCP/IP client sends a command telegram to the TCP/IP server implemented in the
connecting circuit under the IP address that is set in the connecting circuit and Port
1313 with at least 7 bytes and a maximum of 1030 bytes.
The length of the telegram depends on the commands and data quantities to be trans-
ferred.
The telegram consists of a command area and the data area. The data area begins
with byte 7 and can go up to byte 1029.
The command parameters and commands are transferred in byte 0, 1 and byte 2.
Byte 0 contains the antenna. The command to be executed is masked in byte 1 and
2. It consists of two ASCII characters.
The destination address in the data carrier is indicated in bytes 3 and 4, while the
number of bytes to be transferred is specified in bytes 5 and 6.
These specifications refer to commands that require address/data length parameters.
The port through which the TCP/IP connecting circuit can be accessed
is set to
1313
and can
not
be changed.
The length of a request telegram, for example a read command, must
always be identical with the length of the response telegram that is
expected. The length of the request telegram is determined by the com-
mand
plus
the data quantity that is expected.
Data fields that are not required in the response telegram (for example
because the quantity of data sent is greater that the quantity of data that
is expected) are filled out with NULL.
Table 8.1: Telegram structure
Designation
Bit number
7
6
5
4
3
2
1
0
Byte 0
X4
X3
X2
X1
K3
K2
K1
-
Byte 1
Command Character 1 identifier (high byte)
Byte 2
Command Character 2 identifier (low byte)
Byte 3
Destination address high byte
Byte 4
Destination address low byte
Byte 5
Number of bytes high
Byte 6
Number of bytes low
Byte 7
Data
- „ -
- „ -
Byte n
- „ -