SMART ACK Setup
The main function of the SMART ACK setup process is to allocate a Mailbox at the SMART ACK Postmaster holding messages for the SMART ACK Sensor. The setup process is always initiated by the SMART ACK Sensor and uses the following sequence:
SMART ACK Sensor sends a Learn Request telegram to request the allocation of a Mailbox at a SMART ACK Postmaster
SMART ACK Sensor waits for a sufficiently long period (550 ms is used in the standard implementation) to allow the SMART ACK Controller to setup the SMART ACK functionality in a suitable SMART ACK Postmaster. The SMART ACK Postmaster can either be the SMART ACK Controller (Direct Mode) a SMART ACK Repeater (Repeater mode).
SMART ACK Sensor sends a Learn Reclaim telegram to request the response to the Learn Request it has issued
SMART ACK Postmaster responds to the Learn Reclaim telegram with the Learn Acknowledge telegram to inform the SMART ACK Sensor about the result of its Mailbox allocation request
This setup flow is shown below.
SMART ACK Learn Request
The SMART ACK Learn Request is sent from the SMART ACK Sensor to the SMART ACK Controller to request the allocation of a Mailbox at the SMART ACK Postmaster. It is sent as non-repeatable telegram (using STATUS = 0x0F or 0x8F) to ensure that it is only received by a SMART ACK Postmaster with direct (non-repeated) radio connection.
The SMART ACK Learn Request used the following telegram format:
SMART ACK Learn Request Payload
The payload of the SMART ACK Learn Request is 10 byte long and contains the following fields:
Request Code (5 bit)
The Request Code field for a SMART ACK Learn Request issued by a SMART ACK Sensor is set to 0b11111.
If the Learn Request is received by SMART ACK Repeater and forwarded to a SMART ACK Controller (SMART ACK Repeater Mode), then the Request Code field will contain information about the SMART ACK Repeater status to allow the SMART ACK Controller selecting the most suitable SMART ACK Repeater as SMART ACK Postmaster for communication with the SMART ACK Sensor.Manufacturer ID (11 bit)
The Manufacturer ID field identifies the manufacturer of the SMART ACK Sensor. For products from EnOcean GmbH, the Manufacturer ID is 0b000:0000:1011 (00B)EEP (3 byte)
The EEP field identifies the EEP using 1 byte each for RORG, FUNCTION and TYPERSSI (1 byte)
The RSSI field is not used by the SMART ACK Learn Request from the SMART ACK Sensor and therefore set to zero by the SMART ACK Sensor.
If the Learn Request is received by SMART ACK Repeater and forwarded to a SMART ACK Controller (SMART ACK Repeater Mode), then the RSSI field will contain the signal strength with which the SMART ACK Repeater received the SMART ACK Learn Request from the SMART ACK Sensor.Repeater EURID (4 byte)
The Repeater EURID field is not used by the SMART ACK Learn Request from the SMART ACK Sensor and therefore set to zero by the SMART ACK Sensor.
If the Learn Request is received by SMART ACK Repeater and forwarded to a SMART ACK Controller (SMART ACK Repeater Mode), then the Repeater EURID field will contain the EURID (radio address) of the SMART ACK Repeater
SMART ACK Sensor Learn Request Payload Example
The illustration below shows the example payload for a SMART ACK Sensor from EnOcean GmbH wishing to receive SMART ACK Data Telegrams with EEP A5-10-01.
Â
Â