Read this manual before attempting to install the device!
Failure to observe recommendations included in this manual may be dangerous or cause a violation of the law. The manufacturer will not be held responsible for any loss or damage resulting from not following the instructions of this operating manual.
Pursuant to and in accordance with Article 14 of the Directive 2012/19/EU of the European Parliament on waste electrical and electronic equipment (WEEE), and pursuant to and in accordance with Article 20 of the Directive 2013/56/EU of the European Parliament on batteries and accumulators and waste batteries.
The barred symbol of the rubbish bin shown on the equipment indicates that, at the end of its useful life, the product must be collected separately from other waste.
Please note that the lithium batteries must be removed from the equipment before it is given as waste and disposed separately. To remove the batteries refer to the specifications in the user manual. For additional information and how to carry out disposal, please contact the certified disposal service providers.
The MCF-LW12VOC is a battery powered sensor for indoor applications that reads temperature, relative humidity, pressure, ambient light and IAQ air quality index. The device sends collected data over the LoRaWAN® network. Ideally suited for a wide range of applications such as home buildings, air quality monitoring and energy saving applications.
To ensure correct operation and reliable and consistent measurements, install the MCF-LW12VOC sensor away from direct sunlight and heating sources like radiators, conveyors, TV, lights etc. and far away from doors and windows.
The device must be placed where the LoRaWAN® signal coverage is good (SF = 7 optimal, SF = 12 weak). The sensor must be installed vertically on a wall at about 1.5mt height. It must be at least 30cm away from metal objects, and 1mt away from electronic devices.
To deploy the sensor, download the latest LoRa Tool Android App to setup LoRaWAN credentials and other preferences :
Always validate your settings by reading the NFC data after the sensor has restarted.
The sensor is shipped completely off to prevent battery consumption during storage. It is therefore necessary to carry out a first power-on prior to commissioning.
There are two ways to power on the sensor:
Open the case using a screw driver as follow:
By using a screw driver push button for 1s as follow, moving right:
Close the plastic case. Switch-on is visible by flashing of red and green leds.
In case of long period inactivity, if necessary, is possible to shut-off again the sensor to prevent battery consumption, via downlink or with LoRa Tool App:
This sensor contains lithium battery, which must be disposed of separately.
MCF-LW12VOC is provided with one Li-SOCl2 battery packs:
Code | Description |
---|---|
MCF-1S4PE | 14400mAh battery pack |
This is the estimated battery life (in years) in the worst conditions:
15min reading | 20min reading | 30min reading | |
---|---|---|---|
SF12 | 4,6 | 5,5 | 6,7 |
SF7 | 7,5 | 8,4 | 9,4 |
After the batteries replacement, internal counters need to be resetted.
To perform the operation, you need a unique reset code that must be requested to Angel4Future (please provide the DevEUI of the sensor when you ask for that code):
At the end of the procedure the battery level displays 100%.
Download the latest firmwares available on the smartphone with LoRaTool app:
Update the sensor with LoRaTool:
During the update, do not move the smartphone untill the end message.
On the MCF-LW12CO2E there are two system leds, green and red.
Red light status can be related to the values of bVOC, depending on enabled thresholds.
Period is the interval (in minutes) between one measure and the next one. The sensor sends two measures for every transmission (each one with its own timestamp), so the messages interval is twice the period value. Value can be between 15 and 65535 minutes.
Period interval can be set with App or with downlink command.
The device sends extra reports when the measurement changes in accordance with the set thresholds.
When the sensor is not installed at the sea level, the reading of barometric pressures at other elevations must be compensated. Set the right altitude value with LoRa Tool app:
Value can be from -300 to 3000 meters.
Altitude can also be set with downlink command.
As default, the device expresses the VOC value as IAQ index:
or as ppbv value of a VOC mixture (named bVOC - breath VOC, not biogenic), calibrated as in the table:
Molar fraction | Compound |
---|---|
5 ppm | Ethane |
10 ppm | Isoprene/2-methyl-1,3 Butadiene |
10 ppm | Ethanol |
50 ppm | Acetone |
15 ppm | Carbon Monoxide |
(Carrier gas: Nitrogen)
As default, VOC values can vary from 499 to 65 000ppb (2 bytes).
If needed, VOC readings can be extended up to 16 777 215ppb (equal to 16 777ppm), extended to 3 bytes:
On the MCF-LW12VOC is possible to set 4 thresholds to configure the lights lighting:
Th+ = Threshold High Rising
Th- = Threshold High Falling
Tl+ = Threshold Low Rising
Tl- = Threshold Low Falling
When target values are rising and exceed the positive thesholds, leds change and the device sends an uplink with the new leds status and the latest measures.
When values are falling below the negative thresholds, leds change accordingly and the device sends a new uplink with the new leds status and the latest measures.
Thresholds can be enabled, disabled and set via NFC with LoRa Tool App or with downlinks.
If VOC thresholds are enabled, red led will reflect the relative status.
With downlink is also possible to ask the sensor for the actual leds status.
Air quality can be expressed as IAQ index or ppb, and thresholds unit of measurement will change accordingly.
For IAQ, values can be set from 0 to 500:
When the unit of measurement is ppb, thresholds are expressed in ppm (ppb * 1000):
The device supports the following activations on a LoRaWAN® network:
The device exits factory activated with OTAA ENGINKO mode. On request devices can be shipped aleady activated.
Note: in OTAA AppKey is write only, in reading the field will always be empty, even if set.
Network settings:
please keep “Any” settings. Change it only if Objenious network is used (default_ any).
Network type:
LoRa syncword can be setted as “private”(0x12) instead “public” (0x34), but the NS must be setted accordingly (default: public).
Band:
select the right LoRaWAN® band settings accodingly to country requirements.
DST:
set to change DST (default: none).
No time sync:
set to disable time synchronization request (default: enabled).
Normally sensor asks for a time sync at every power on (uplink starting with 01) or, if enabled, once a week.
If not handled in the right way can cause a unnecessary battery consumption (battery life < 2 years).
Please check chapter 2.1 DATA FRAME FORMAT.
UnConfirmed:
set for unconfirmed uplinks (default: confirmed uplink).
Single join/day:
set for to allow only one join per day (default: multiple join allowed).
The device can be protected by passwords, to avoid unauthorized persons to read data or modify parameters.
As default passwords are equal to 0.
Allowed values range from 0 to 99999999 (only numbers).
To change the passwords, set the new values with the LoRa Tool App:
Once the passwords are setted, to gain access from LoRa Tool to the sensor, open the App:
and set the right values before reading from the device:
To bring back the sensor to factory default and reset the passwords, a reset code must be requested to Angel4Future (please provide the DevEUI of the sensor when you ask for that code).
WIth LoRa Tool App is possible to configure the device using an XML file, instead to manually adjust the parameters (for details about the file format please ask to Angel4Future). This is very useful especially in case of multiple devices configuration.
With “Save” button an XML file with the actual configuration of the sensor will be generated. This is useful to store or clone the configuration, or to send it to Angel4Future's support if needed.
WIth LoRa Tool App is possible to configure many devices in an easy way.
For multi-configuration is needed at least one XML file with the parameters to set.
Settings on this file will be applied to all the sensors.
With an additional XLS file is possible to load different LoRa configuration parameters (Activation Type, AppKey, AppEUI, NetKey, DevAddress, Band, Private option) for each sensor, based on DevEUI.
When the sensor is approached, if one parameter is different from files, the APP will ask you if you want to overwrite.
XLS is prevailing on the XML, so if both files are enabled, if the DevEUI of the device matches one of the DevEUIs in the XLS file, LoRa parameters will be setted from this one.
These configuration can be done in the in the Settings:
For details on files format please ask to Angel4Future.
enginko provides free LoRaWEB online tool, where for each sensor it is possible to find documentation, javascript examples for parsing, downlink generator and uplink decoder:
LoRaWEB Tool (iot.mcf88.cloud/LoRaWeb)
For payload descriptions, uplinks and downlinks format and available commands please refer to this document:
Code | Description |
---|---|
MCF-LW12VOC | enginko LoRaWAN® indoor environmental sensor VOC & LUX EU863-870 |
MCF-LW12VOC-AS | enginko LoRaWAN® indoor environmental sensor VOC & LUX AS920-925 |
MCF-LW12VOC-US | enginko LoRaWAN® indoor environmental sensor VOC & LUX US902-928 |
MCF-LW12VOC-AU | enginko LoRaWAN® indoor environmental sensor VOC & LUX AU915-928 |
Declarations of conformity are available from Angel4Future by sending a request email to sensor@enginko.com.
Angel4Future S.r.l.
Via San Sabino 21 - 70042 MOLA DI BARI (BA) , ITALY
T : +39 080 532 1796
E : info@angel4future.com
W: enginko.com
Rev.1