-
Notifications
You must be signed in to change notification settings - Fork 14
receiving data
Holger Will edited this page Oct 20, 2015
·
3 revisions
you receive telegrams by listening for the "data" event. The enocean protocol is designed, in a way that prevents you from knowing what exact type of package you are looking at.
From any random telegram you can see the RORG (Radio ORGanization Number). The first 3 are the most common.
| Telegram | RORG | ORG | Descritption |
|---|---|---|---|
| RPS | F6 | 05 | Repeated Switch Communication (1 Byte) |
| 1BS | D5 | 06 | 1 Byte Communication |
| 4BS | A5 | 07 | 4 Byte Communication |
| VLD | D2 | =RORG | Variable Length Data |
| MSC | D1 | =RORG | Manufacturer Specific Communication |
| ADT | A6 | =RORG | Adressing Destination Telegram |
| SM_LRN_REQ | C6 | =RORG | Smart Ack Learn Request |
| SM_LRN_ANS | C7 | =RORG | Smart Ack Learn Answer |
| SM_REC | A7 | =RORG | Smart Ack Reclaim |
| SYS_EX | C5 | =RORG | Remote Management |
| SEC | 30 | =RORG | Secure telegram |
| SEC_ENCAPS | 31 | =RORG | Secure telegram with R-ORG encapsulation |
To know the content of a telegram, you have to know its EEP (Enocean Equipment Protocol). The EEP is send whith the teach-in telegrams. But you can as well just provide the EEP yourself if you know it.