COMFORT-CO2_Technical_Reference_Manual_APP_2.3.2-1.pdf

<aside> 💡 Applicable to APP versions: >= 2.3.x

</aside>

DOCUMENTATION GUIDE

TABLE OF CONTENTS

• TABLE OF CONTENTS

1. REGISTERS

1.1 Generic registers

1.2 Applicative registers

0 … 65535 | Number of backups (history logs) to be done before sending a frame (thus defining the sending period). The value 0 is equivalent to disabling the periodic mode. | | 308 | 4 | 16 | LED activity | 0x3E6006F | 0 … 0xFFFFFFFF | Default: 0x3E6006F Other values: reserved | | 315 | 1 | 10 | Time zone offset | 0 | -12 … 14 | Defines the Time Zone offset from UTC (in hours). Must be defined for Daylight Saving Time management. | | 316 | 1 | 10 | Daylight Saving Timemanagement | 0 | 0 … 1 | Only applicable for European countries. 0: disabled 1: enabled | | 318 | 1 | 10 | Time stamping |   0 |   0 … 1 | LoRaWAN only If enabled, adds a time stamp in data frames. 0: disabled 1: enabled | | 319 | 1 | 10 | RTCcalibration value | 0 | -100 … 100 | Allows correcting a possible drift of the clock. In tenths of a second per day. | | 320 | 2 | 10 | History period | 1 | 1 … 65535 | Number of readings to be performed before saving in the history logs. The value 1 is equivalent to 1 backup per reading | | 321 | 2 | 10 | Sampling period | 300 (10 min) | 15 … 65535 | 0: no sampling x2 seconds With S320 = 1 and S301 = 2 è 72 TX / Day With S320 = 1 and S301 = 6 è 24 TX / Day | | 322 | 2 | 10 | Alarm repetition period |   0 |   0 … 65535 | If an alarm is active, this register allows the product to send periodically a reminder.   0: no repetition X sampling period (S321) |

0 … 15 | Number of samples to be repeated in the next frame | | 324 | 1 | 10 | Black out duration | 0 | 0 – 12 (h) | 0 è blackout feature disable ≠ 0 è blackout active, duration of daily black out. Unit Hour | | 325 | 1 | 10 | Black out start time | 22 | 0 – 23 (h) | Black out start time. Unit Hour |

1.2.1 Black-out period

The device can daily suspend the sensor acquisition and associated processes, using the blackout parameters. When the blackout interval is entered:

• If a periodic acquisition is in progress (at least one sample has already been acquired), the beginning of the blackout period is postponed till the periodic acquisition is completed and the associated frame has been sent (0x6A).

When the blackout period is in progress:

• All features related to sensors are hold (not managed):
  • Sensor measurements (T/H/CO2) are disabled,
  • Alarm and LED indicator not evaluated/transmitted,
  • Periodic frame not transmitted,
  • Daily statistic does not register any data during the
• The following feature are still active / usable during the blackout interval:
  • Daily transmission is still active but does not consider the blackout period in the calculation.
  • Alarms linked to the connected button or the digital input.
  • Manual calibration via button or downlink with timestamp

Note: when the blackout is activated, the automatic calibration is not working.

1.2.2 CO2 Calibration registers

200-2000 |

= V2.3.0 | 0 ➔ Factory calibration [200-2000] ➔ use as target value when a calibration is performed | | S356 | 2 | 10 |   Automatic calibration period | 1 |   0-65534 |   = V2.3.0 | 0: Automatic calibration deactivated 1: Automatic calibration activated with default period of 180 hours 2-65534: Automatic calibration period in hours | | S357 | 1 | 10 | Start of the calibration by pressing the button | 1 |   0-1 |   = V2.3.2 | 0: Deactivated 1: Activated |

1.3 Alarm registers

1.3.1 Temperature

1.3.2 Humidity

1.3.3 CO2 alarm and QAI indicator

| --- | --- | --- | --- | --- | --- | --- |

Co2 alarm frame and CO2 “led” indicator are updated/evaluated each time a CO2 sensor measurement (sampling) is performed (according to S321 value, sampling period).

Note: CO2 LED indicator is not associated to an alarm frame.

These registers allow to update QAI led repetition period (i.e.: speeding up the led indication or decrease rate to optimize power consumption).

| --- | --- | --- | --- | --- | --- | --- |

1.4 Digital inputs

| --- | --- | --- | --- | --- | --- | --- |

1.5 Radio registers

1.5.1 LoRaWAN Network Registers

| --- | --- | --- | --- |

| --- | --- | --- | --- |

NOTE 1: The “Over The Air Activation” (OTAA) mode uses a JOIN phase before being able to transmit on the network. This mode uses the APP_ EUI (S214 and S215) and APP_KEY (S216 to S219) codes during this phase to create the keys for network communication. Once this phase is completed, the codes APP_sKEY, NWK_sKEY and DEVICE ADDRESS will be present in the corresponding registers. A new JOIN phase is started every time the device exits Command mode, a reset is performed, or the device is turned on.

Codes:

• APP_EUI identifier for global use (provided by default by Adeunis)
• APP_KEY device application key (provided by default by Adeunis)

The “Activation by personalization” (ABP) mode has no JOIN phase; it transmits directly on the network using the codes NWK_sKEY (S222 to S225), APP_sKEY (S226 to S229) and DEVICE ADDRESS (S281) to communicate. Codes:

• NWK_sKEY network session key (provided by LNS)
• APP_KEY applicative session key (provided by LNS)
• DEVICE ADDRESS Address of the device in the network (provided by LNS)

| --- | --- | --- | --- | --- | --- | --- | --- |