5
Operation
52
Festo – EXCM-30/-40-...-PF-EN – 1603 – English
5.5.3
CVE protocol
Access to the data of the controller is through CVE objects. A CVE object always has a unique index that
enables identification of the object.
Note
A series of CVE objects is listed in the appendix (
è
In the following, the notation xxx.y (object index.object subindex) is used for CVE ob
jects.
Caution
Personal injury and material damage
Inadvertent writing to non-documented objects can result in unforeseeable behaviour of
the planar surface gantry.
Use only objects listed in the appendix (
è
Each CVE object has one of the following listed data types (
è
The byte sequence is Little Endian, that is, the lowest-value byte first.
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. 5.12 Data types
Read object
To read a CVE object, a request corresponding to Tab. 5.13 must be sent to the controller. This sends
back a response corresponding to Tab. 5.14.
Write object
To write a CVE object, a request corresponding to Tab. 5.15 must be sent to the controller. This sends