The EnOcean interface is a global protocol standard for communication via radio or in some cases via RS485. Most devices draw their energy from the environment and therefore do not require a battery.
There are many different gateways for communication. In principle, all devices with the EnOcean Serial Protocol 3 (ESP3) are compatible. Communication can take place via USB, RS232, RS485 or over TCP/IP.
Note: When purchasing, please note the radio frequency applicable in your country.
| Name | Type |
|---|---|
| USB 300, USB 400J, USB 500U | |
| Antcas Bridge* or ser2net |
*This product is currently not available.
The base address can currently only be changed externally via the Dolphin View software. You can find the software at:
https://www.enocean.com/en/product/dolphinview/
Warning: The base address of a device can be changed only 10 times.
After adding the gateway, devices can be added in the Installation. Each sensor and actuator is manually created and possibly learned. It is recommended to create a folder structure to facilitate clarity.
After creation, the id of the device can be set. If a gateway is active, for example, the button can be recognized by pressing it several times. For sending a telegram, the
id_send is set for actuators. A maximum of 127 outgoing channels can be used per gateway.
Some sensors support multiple EEP types. These can be selected under the constant typ. If a type is missing, please contact Support.
Note: Multiple telegrams should not be placed on one application input. Instead, use an OR function block with multiple different input variables.
To teach an actuator, a LRN-telegram can be sent. The best way to do this is by using the monitor. To send the telegram, you must send TRUE to the interface.