--- title: "EnOcean EEP device drivers" canonical: "https://docs.cuesystem.com/space/CVCHELP/522682457/EnOcean%20EEP%20device%20drivers" format: markdown --- > Macro (toc) --- # Introduction These objects can represent virtual EnOcean devices in the CVC project. The virtual EnOcean devices can transmit telegrams, listen to EnOcean communication traffic, and react to specific telegrams. EnOcean device communication and its functions are described in the **EnOcean Equipment Profile** (EEP). Manufacturers of controlled devices provide the full EEP description, or it is available from [www.enocean.com](http://www.enocean.com).  The EEP profile is a Hex number divided into three parts, so it is mainly written with ”-” character to separate these parts:   RORG-Function-Type   (For example, EEP: A5-07-01 …profile for EnOcean Occupancy sensor.. )  The EEP profile number belongs to the main characteristic of each device driver.  The EnOcean telegrams sent from a transmitter are mostly sent with the sender ID. This ID is considered to be unique in the EnOcean installation. The listeners can listen to all the EnOcean traffic and select the commands they are about to follow according to the sender ID. The commissioning in EnOcean systems mostly means making the listeners ”know” the IDs of senders, which they should react to. This is done by the so-called EnOcean Teach or Learn process. There is a great variety of possibilities for how EnOcean can do this process. EEP defines the type of Teach-Learn process, but variations can also exist.   There are available plugins for each virtual EnOcean device object which are enabling to send out teaching telegrams from Transmitter virtual devices, while for Listener virtual devices, the plugins serve as recipients who can Learn IDs from external transmitters.  The EnOcean channel of the CUE controller can send telegrams with 128 different IDs. The available ID pool for the channel is 128 consequent values starting from the BaseID value. For all EnOcean Transmitter virtual devices, the ID is specified as   ID = BaseID + IDoffset. Where the IDoffset (in range 0-127) is defined in the properties of the device object instance.  IDoffset must be set by the programmer in CVC Configuration. Very important is that the IDoffset property must be set, so the final ID is always unique in one EnOcean installation!  If there would be an attempt to send an outgoing telegram with an ID not belonging to range BaseID to (BaseID+127),  then the telegram will be sent using the original ChipID, which is unique for each EnOcean transmitting chip and can not be changed! (Note that the BaseID is always mod 128 value in range &HFF800000 to &HFFFFFF80 while ChipID can be of any other value.) More info about EnOcean ID and BaseID can be found at [www.enocean.com](http://www.enocean.com).  The BaseID and ChipID are the basic channel information that can be read from the application by channel command: GetChannelInfo()  There are available two basic types of EnOcean device objects in CVC:  - Transmitters - Listeners ### Transmitter - Objects are using the ID from the available pool of IDs based on BaseID as described above and can send appropriate radio telegram types corresponding to their EEP. - These drivers are equipped with a plugin that allows to Teach other EnOcean devices to be commanded by telegrams from this transmitter. ### Listener - Objects can receive EnOcean telegrams of types appropriate to device EEP. The listener is always receiving only telegrams from specific EnOcean device, which ID is set in the ”ID to Listen” device property. When the telegram from such device ID is received, this EnOcean device object can react (- in most cases, it is a raising event). - The Listeners are equipped with plugins allowing them to Learn its ”ID to Listen” value using the standard Teach-Learn EnOcean process. > 📝 #### Listener important notes:  > 📝 > 📝 1. Listener events are generated only from commands coming from external EnOcean devices (the channel is not receiving its own telegrams – including telegrams transmitted by other device object installed on the same EnOcean channel). > 📝 2. Events are generated only from telegrams with appropriate ID and compliant EEP profile! # Device Plugins The main purpose of EnOcean device plugins are:   1. enable to use standard EnOcean Teach/Learn procedures to obtain or set information about actual EnOcean devices IDs 2. test functionality of communication with appropriate EnOcean external equipment > 📝 The plugins need to cooperate with real hardware; thus, the EnOcean device plugin application can run only when the controller with the EnOcean port is connected. To start the EnOcean device plugin: 1. Open CVC project 2. Go to the tab Configuration. 3. Right-click the EnOcean device object instance 4. Select Plugin. # Properties, Functions & EnOcean Equipment Profiles > Macro (children) --- ---