EnOcean radio receivers Q.SRC and Q.STC
Unidirectional EnOcean receiver Q.SRC
|Datasheet||Unidirectional EnOcean receiver Q.SRC|
Bidirectional EnOcean tranceiver Q.STC
|Datasheet||Bidirectional EnOcean tranceiver Q.STC|
Manual : EnOcean FBox Library
|Manual||26-882||Manual : EnOcean FBox Library|
Good to know
Please note that the EnOcean receivers from Omnio (Q.)APG03U-RS485-Eno and (Q.)APG03B-RS485-Eno are no products sold by Saia-Burgess Controls AG (despite the fact they are listed in some documents such as the price list).
For furhter information please refer to FAQ 101508.
Communication / EnOcean
What is new in the EnOcean library 2.6.147? (FAQ #101765)
With PG5 2.0.220 the EnOcean FBox library version 2.6.147 is delivered.
This FAQ lists the main modifications to this FBox library.
EnOcean library 2.6.147 (March 2012)
- New FBox "EOR 7x0 EVC":
An FBox for the EnOcean gateway from Sensortec has been added
- FBox "Receive Any":
The data outputs D0..D3 were labelled incorrectly (Data0 instead of Data3 etc.)
EnOcean library 2.6.130 (May 2011)
- New FBox:
An FBox for the Thermokon SRC-Ethernet gateway has been added
- New FBox "EOR 7x0 EVC":
What does the EnOcean function "live check" exactly do? (FAQ #101577)
Even if the FBoxes are called "bidirectional" EnOcean, the communication is always unidirectional. "Bidirectional" only means that the device is also able to send data. Therefore it's not possible to actively query a device, for example the one from a window contact.
For that reason some devices re-transmit the last telegram after a specific time (some kind of "alive"-telegram). By this telegram the FBox can indicate that the device is still available (or that it is no longer available, if there is no telegram received within the specified time).
In the interface FBox can be setup a "LifeCheck turn around". In this specified time a retransmission of a telegram from the remote device is expected. If there's no reception, the specific FBox of the device indicates "Offline". £
Choose this "LifeCheck turn around" two times longer than the device-defined retransmission time (which can be found in the specification notes of the device).
Are the EnOcean receivers APG03U/B-RS485-Eno supported by the FBox library? (FAQ #101508)
Yes, the EnOcean radio receivers from Omnio, APG03U-RS485-Eno (unidirectional version) and APG03B-RS485-Eno (bidirectional version) are supported by the FBox library for EnOcean from Saia-Burgess Controls AG.
Points to be considered when using the Omnio radio receivers
The expreiences during the pilot phase have shown that:
- It is important to use the EnOcean ID filter of the Omnio receivers
- In dependance of the version of the receiver, an according FBox version is to be selected (sending Acknowledge telegrams or not, see FAQ 101453)
- It is not possible to mix receivers from Omnio and Thermokon on the same RS485 bus.
Can I order the Omnio receivers from Saia-Burgess Controls AG?
No, please order these devices from Omnio directly as Saia-Burgess Controls AG is no longer able to provide these products (unfortunately these products are still listed in the price list for 2010/11).
Why is the reaction to a signal from an EnOcean sensor very slow? (FAQ #101453)
In case a version of an Omnio receiver or transceiver which requires "Acknowledge telegrams" has been used, the reaction to signals from EnOcean sensors can be very slow in case the wrong FBox is used.
The reaction to a signal from an Enocean sensor is very slow (the change of state of the sensor is recognized in the Fupla program after more than a second). In the installation an Omnio receiver/transceiver (gateway) produced before September 2009 or after July 2010 is used.
The EnOcean receiver and tranceiver from Omnio which have been produced before September 2009 and after July 2010 do require an acknowledge telegram from the PCD. As the PCD is not sending this ACK teleram, the receiver will repeat the telegram it received from the EnOcean device 3 times (with a retry time of several 100ms) before it will forward the next telegram.
In order to solve this problem, please use the FBox "OM APG03B-RS485 ACK" (see screenshot below). This FBox will send the ACK telegrams for all telegrams received.
In order to use this FBox, the following minimum FBox library versions are to be used:
- PG5 2.0: 2.6.125 or later
- PG5 1.4: 2.5.125 or later
Why does the communication between a PCD and an Omnio "RS232/485 to EnOcean" converter not work? (FAQ #101174)
Due to incompatible communication parameters used by the Omnio "RS232/485 to EnOcean" converters the FBox library version 1.0.0 is not working in every situation with the converter from Omnio.
The communication between a PCD and an Omnio “RS232/485 to EnOcean” converter does not work with the EnOcean FBox library version 1.0.0.
The communication protocol/parameters which is used by the Omnio "RS232/485 to EnOcean" converter is not the same as for other "RS232/485 to EnOcean" converters (e.g. the one from Thermokon).
Since the EnOcean F-Box Library 1.0.20 the FBox "EnOcean Init" does feature an adjust parameter called "manufacturer". This selection will then adapt the communication protocol of the PCD.
How to connect an RS-485 EnOcean device to the PCD? (FAQ #101106)
On the PCD the bus has the lables D and /D, and EnOcean devices do have lable A and B. How should they be connected together?
RS 485 Bus Terminal:
EnOcean A = PCD /D
EnOcean B = PCD D