Festo Электроцилиндр - Manual (Page 110)

B Control via Ethernet (CVE)
110 Festo – GDCP-CMMO-ST-EA-SY-EN – 1301a – English
B.1.2 CVE protocol
Access to CMMO-ST data is effected via CVE objects. A CVE object always has a unique index that
enables identification of the object.
A number of CVE objects are listed in section B.3. Only the objects listed there may be used.
Caution
Personal injury and damage to property
Accidentally writing over undocumented objects can result in unpredictable behaviour
of the drive.
• Only use the objects listed in appendix B.3.
Each object has one of the data types listed in Tab. B.1. The byte order is little endian.
Read object
In order to read a CVE object, a request must be sent to the CMMO-ST in accordance with Tab. B.2. This
sends back a response Tab. B.3.
Write object:
In order to write a CVE object, a request must be sent to the CMMO-ST corresponding to Tab. B.4. This
sends back a response Tab. B.5.
As both directions concern an endless TCP data stream, the individual messages must be filtered out.
Strict compliance with the message length is required for this.
Data types
Value Type Bytes Description Range of values
0x00 – – Unknown data type –
0x01 – – – –
0x02 UINT32 4 32 bit unsigned integer 0 … 4294967295
0x03 UINT16 2 16 bit unsigned integer 0 … 65535
0x04 UINT08 1 8 bit unsigned integer 0 … 255
0x05 – – – –
0x06 SINT32 4 32 bit signed integer – 2147483647 … 2147483647
0x07 SINT16 2 16 bit signed integer – 32767 … 32767
0x08 SINT08 1 8 bit signed integer – 127 … 127
Tab. B.1 Data types