Synetica enLink IAQ Wireless Indoor Air Quality Monitor User Guide
- June 5, 2024
- Synetica
Table of Contents
enLink IAQ Wireless Indoor Air Quality Monitor
User Guide
enLink IAQ
Wireless Indoor Air Quality Monitor
- LoRa long range wireless
- Satisfies the accuracy and range requirements for the IWBI WELL v2 standard.
- Battery or externally powered
- Built-in sensor options for:
- Temperature (°C)
- Carbon Dioxide (CO2 )*
- Barometric Pressure (Pa)*
- Particles PM 1, 2.5, 4, 10*
- Humidity (%RH)
- Sound (dB)*
- Volatile Organic Compounds (VOCs)*
- Ozone*
The enLink IAQ wireless Air Quality Monitor is a precision instrument that accurately measures up to 8 key environmental parameters including Temperature, Humidity, VOCs, Carbon Dioxide, and Particulate Matter (PM1, PM 2.5, PM4 & PM10), Sound Level, Barometric Pressure and Ozone. enLink IAQ is a precision instrument and satisfies the accuracy and range requirements for IWBI WELL v2 certification. Readings are transmitted to the cloud using long- range LoRa wireless, where the data can be displayed and analyzed. A built-in USB port allows all parameters including air quality data, wireless signal strength, and wireless network configuration to be viewed and set using simple menus via any USB-enabled host such as a PC or Mac.
Features
- Multiple sensor options*
- Lora long-range wireless
- Frequency Range 863-870MHz*
- Frequency Range 902-928MHz*
- Up to +18dBm Tx Power
- Built-in USB port for configuration
- Battery or externally powered
- CE compliant
- RoHS compliant
- Made in the UK
*Model dependent
Introduction
LoRa devices can be configured using OTAA (Over-the-Air-Activation) or ABP (Activation-by-Personalisation). OTAA is the most secure way to connect a device to the LoRa network. In OTAA, the device performs a Join-procedure with the network, during which a dynamic DevAddr (device address) is assigned and security keys are negotiated with the device. ABP allows you to set the DevAddr as well as the security keys in the module. This is simpler than OTAA as there is no Join the procedure, however, it is less secure than OTAA. This guide will illustrate using OTAA as it is the most secure and flexible method. The OTAA configuration requires the following parameters to be correctly set:
- DevEUI: End-device Identifier. It is unique for every device and is set at device manufacture.
- AppEUI / JoinEUI
- Application Identifier. Used to identify the end application.
- AppKey: Application key. Used to create the session keys.
Note: In LoRaWAN 1.1, AppEUI was renamed to JoinEUI.
For many applications Synetica can supply enLink AQ units with the above
parameters pre-configured, so providing the LoRa gateway has the matching keys
the join process will happen automatically once the enLink AQ unit is in
wireless range and switched on.
The DevEUI is always set at device manufacture and is unique. The device
AppEUI and AppKey can easily be set via the USB connection if required and the
process is detailed later in this document.
To get started with enLink IAQ wireless sensor, follow these steps:
1. Setup using Multitech Conduit® AEP
MultiTech’s Conduit is a leading configurable, manageable, and scalable LoRa
gateway and can be quickly and easily configured to create a LoRaWAN network
with enLink LoRa devices.
To enable LoRa devices to connect to the Conduit the AppEUI and AppKey must be
changed to match those of the enLink devices.
For Multitech Conduit units running V1.6.4/1.7.0, follow the process below.
Detailed instructions can be found on the Multitech
Web Site (www.multitech.net).
Logon to the Conduit and select LoRaWAN -> Network Settings
Set the Mode to Network Server, then set the Channel Plan required and set the
Mask to 00FF as shown below.
Next, select the Key Management menu and set the AppEUI and AppKey. Ensure
that these match the enLink devices you want to join the LoRa network.
Once the keys are set, select Submit. The Conduit will prompt to Save and
Restart. The settings will not take effect until the Conduit has restarted.
Once the unit has restarted you are ready to join enLink devices to the
network.
The Conduit gateway is now ready to receive devices onto the network. On the
Conduit, select LoRaWAN -> Devices as shown below. This screen shows details
of devices that have joined the network, when they joined and when the last
message was received from them. As you add devices to the network, this is
where they will appear. 
2. Join enLink devices to the LoRa network
enLink devices in wireless range and with the correct AppEUI and AppKey
settings will automatically join the LoRa network when they are first powered
up. 
The unique DevEUI is printed on all enLink devices and is also present in the
QR code. The DevEUI can be used to identify the device once joined to the
network.
To power, the device ON, install batteries and slide the power switch to BATT
or apply external power (12V-24V DC) to the unit and slide the power switch to
EXT.
Once powered ON, the enLink device will send a Join
request message to the Conduit. The Status LED will blink RED as shown below
whilst the Join process is taking place. Depending on factors such as signal
strength, RF interference etc the Join process may take several seconds to
complete. 
When the device has successfully joined the network the Mode LED will blink
GREEN for several seconds to show that the Join has been completed. The LED’s
will then switch off to conserve the batteries.
Devices that have Joined the network appear in the Conduit LoRaWAN – > Devices
menu as shown previously.
3. Setting / changing the enLink LoRa keys
For many applications, Synetica can supply enLink IAQ units with the LoRa
AppEUI and AppKey parameters pre-configured to your requirements, whereby if
the LoRa gateway has matching keys the join process will happen automatically
once the enLink IAQ unit is in wireless range and powered on.
The DevEUI is always set at device manufacture and is unique. The device
AppEUI and AppKey can easily be set via the USB connection as detailed below.
Once the cover is removed, connect a micro USB cable to the enLink unit. There
are two USB connectors on the enLink IAQ, so be sure to connect to the correct
USB port as shown in the image below. The device will attach to a COM port on
your PC.
Using a terminal program (e.g. Teraterm
https://ttssh2.osdn.jp/) connect to the COM port used by the enLink device.
To verify which COM port is being used, check the Windows™ Device Manager (In
Windows – Click the Start button, type device manager into the search box and
tap Device Manager on the menu.) Expand the Ports (Com & LPT) menu as shown
below. 
In your terminal program press the Enter key. An enLink summary screen will
appear as shown below. The default password is the last four digits of the
displayed DevEUI, in the screen below this is fba3.
The screen below will show the enLink Main Menu options. Enter Q to enter the
Quick Start Menu.
The QuickStart Menu contains only the parameters that normally need to be
configured to setup the device and join the LoRa network.
From the Quick Start Menu, you can change the AppEUI and AppKey.
From the Quick Start Settings Menu, access the AppEUI setting by entering e.
Enter the 16 characters AppEUI using numbers and letters a to f. Do not
include spaces or any other characters. Pressing S will enter the default
AppEUI which you can then edit. Press Enter when the key is correctly entered
to return to the QuickStart Settings Menu.
From the Quick Start Settings Menu access the AppKey setting by entering k.
Enter the 32 character Appkey using numbers and letters a to f. Do not include
spaces or any other characters. Pressing S will enter the default AppKey which
you can then edit. Press Enter when the key is correctly entered to return to
the QuickStart Settings Menu. 
Press X from the Quick Start Settings Menu to return to the enLink Main menu.
The header will show Reboot Required as shown below. The new key
settings will not take effect until the enLink device is restarted. Enter r to
reboot followed by OK. The device will restart with the entered AppEUI and
AppKey and attempt to join the LoRa network.
Check the Conduit LoRaWAN -> Devices menu detailed previously to verify that
the enLink device has joined successfully.
Live Menu
enLink IAQ incorporates a live data screen that shows all readings and device
status for easy data validation. To enter the Live status screen, from the
Main Menu enter c for Configure Device followed by d for Live readings
display. A screen similar to the one below will show. The sensors will vary
according to the enLink IAQ model and the installed sensors. 
Configuration Menu
The enLink IAQ configuration menu allows you to view current sensor readings
and also to change various functions of their behavior such as calibration
data. To enter the Configure Device menu press c from the main menu. A screen
similar to the one below will show. The exact parameters shown will vary
according to the I AQ model and sensors fitted.
CO2 Sensor Auto Calibration Configuration
To view and set CO2 sensor calibration information, enter c and the screen
below will show.
Please see the table below for information on each menu item.
| Menu Item | Description / details |
|---|---|
| Last/Minimum Reading | Shows the last CO2 value read and the minimum CO2 value |
read since the last auto-calibration.
Next Auto-Cal due| Shows when the next autocalibration routine will occur
Last Auto-Cal result| Shows the value of the last auto-calibration result.
Used internally by the sensor.
Calibration Success| This shows the total number of successful auto
calibrations since the device was powered up.
Out-of-bounds Ignored| Shows the number of times that auto-calibration did not
run due to the Out Of Bounds setting.
E – Enable/Disable Auto-Cal| Enables or disables the auto-calibration routine.
T – Set Target CO2 Level| This is the known CO2 corresponding to the minimum
value the sensor has read since power-up or last calibration. It is normally
‘fresh air’ or the lowest level when the building is unoccupied overnight or
at weekends. Typically this is 400 — 450 ppm.
K – Set to Known CO2 Level| This will re-calibrate the zero point of the
sensor to a known gas concentration. The sensor should be placed in this gas
concentration and allowed to stabilize.
This command runs in the background and will take 8 to 10 seconds to complete.
As an example, fresh air is typically around 400 — 450 ppm.
0 – Out-of-bounds check| The Out-of-bounds value is used to ignore the
calibration if the minimum value the sensor has read is not within a sensible
range of the target concentration level.
So, if the target concentration level is 400, the Out-of-bounds value is ±50
and the minimum reading is 451 (or more), the calibration routine is ignored.
I – Initial Interval| It is possible for the first auto-calibration to take
place more quickly than the regular auto-calibration events. This can be
useful to stabilize the readings quickly after installation.
R – Regular Interval| This is the standard calibration interval, it is set to
8 days by default to accommodate a week-long period where the minimum sensed
CO2 level should have fallen to background levels.
The CO2 sensor needs to be exposed to fresh, clean air periodically for the
auto calibration to be successful. Most occupied areas are unoccupied for some
time during a week-long period, typically at night, or at the weekend and
therefore the auto-calibration runs every 8 days by default. Background CO2
levels are typically around 400-450 ppm, if
the background CO2 level is known to be a different value then this can be set
in the “Set Target CO2 Level” parameter If a unit is placed in an area where
the CO2 level may not fall below a certain level, e.g. 450ppm, during the
calibration interval then the “Out-of-bounds check” parameter can be set so
that the auto-calibration routine does not run. As an example, if an area is
continuously occupied for a long period and the minimum CO2 reading does not
fall below, say 450ppm, then it is undesirable to run the autocalibration
routine based on a target of 400ppm. In this case, if the “Set Target CO2
Level” is set to 400ppm and the “Out-of-bounds check” value is set to +/-50
ppm then the autocalibration routine will not run unless the minimum read
value falls below 451ppm in the interval.
Particulate Sensor Configuration
To view and set Particulate sensor information, enter p and the screen
below will show.
Menu item f sets the particulate sensor fan run time. The default is 8 seconds
and is the recommended setting for most applications. The fan run time may be
extended for certain applications, however, this will have an impact on the
battery life of the unit.
The particulate sensor has a self-cleaning function which runs the fan at high
speed to clean away any dust build-up in the measurement chamber. By default,
this cleaning cycle operates every 7 days but may be changed if required.
Reducing the cleaning interval will have a detrimental effect on battery life.
Technical Support
For technical assistance, please visit the downloads section of our website at www.synetica.net or email us at support@synetica.net