Chapter 5 CP 240 - EnOcean
Manual VIPA System 200V
5-14
HB97E - CP - Rev. 11/30
Overview of the EnOcean telegrams
The following table shows the general structure of an EnOcean telegram.
Send and receive telegrams have the same structure. They only differ in
the ID.
Bit 7
Bit 0
0xA5
0x5A
These bytes are automatically created at
transmission and hidden at reception.
0x0B
0x6B
ORG
DataBytes3
DataBytes2
DataBytes1
DataBytes0
IDBytes3*
IDBytes2*
IDBytes1*
IDBytes0*
Status
0x0B: ID for reception telegram
0x06: ID for send telegram
See table
supported ORG formats
Data from a sensor res. to an actuator
ID of the transceiver module. With SET_IDBASE
you may alter the ID up to 10 times.
Status information of the according sensor
Checksum
Is automatically created at transmission and hidden
at reception.
*
)
During transmission the actual ID base of the module replaces the ID base in the
telegram.
At the following pages all telegrams are listed that are supported by the CP
240 EnOcean. This description has been taken directly out of the
documentation by courtesy of EnOcean.
Note!
Please regard that the first two synchronization bytes and the Checksum of
received telegrams are not stored in the CP 240. At transmission, the
11Byte user data are automatically supplemented with these bytes to a
total size of 14Byte.
General structure
General
Summary of Contents for CP 240 RS232
Page 1: ...Manual VIPA System 200V CP Order No VIPA HB97E_CP Rev 11 30...
Page 2: ...L...
Page 14: ...Chapter 1 Basics Manual VIPA System 200V 1 6 HB97E CP Rev 11 30...
Page 126: ...Chapter 5 CP 240 EnOcean Manual VIPA System 200V 5 32 HB97E CP Rev 11 30...
Page 144: ...Chapter 6 CP 240 M Bus Manual VIPA System 200V 6 18 HB97E CP Rev 11 30...
Page 148: ...Index Manual VIPA System 200V A 4 HB97E CP Rev 11 30 M Stich...
