e n g i n k o . s u p p o r t . c e n t e r

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.

• Do not dismantle or modify in any way.
• Avoid mechanical stress
• Do not use any detergent or alcohol to clean the device.
• Do not mount in horizontal position.

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).

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.

This class C device transmits the state of its 16 inputs (12-24Vac/dc) and controls 8 outputs (up to 5A - 230Vac) through the LoRaWAN® network. All these inputs and outputs are galvanically isolated. It can be used for industrial process control, home automation, water treatment, agriculture irrigation and similar applications.

• CPU Cortex M0+
• EEProm 32KB
• Flash 96KB
• Real time clock
• Encryption AES 128 bit
• Class C LoRaWAN® stack EU868, AS923, AU915, US915
• EU868 version CE certified according to 2014/53/EU – Radio Equipment Directive (RED)
• Transmission band (EU version): 868 MHz
• Transmission Power (EU version): 14dBm max
• Power supply 24Vac/dc
• Maximum power consumption 8W
• 16 opto-isolated input AC-DC, range 5-28Vac/dc
• 8 relay output with COM, NO(5Amp@230Vac), NC(3Amp@230Vac)
• USB for node setup ad FW upgrade
• Storage temperature range -20°C ÷+80°C
• Working temperature range -10°C ÷+70°C
• DIN (EN 60715) mounting enclosure, 9 modules

The installation has to be done by a qualified electrician.

The device is intended as subassembly (component).

It is responsibility of the assembler of equipment incorporating to ensure that the overall equipment is safe.

The MCF-LW13MIO must be mounted in vertical position.

The magnetic antenna must be positioned on a metal body. It should preferably be vertical and at least 30 cm away from other metal bodies. The installation must take place in a place where the LoRaWAN® signal coverage is good (SF=7 optimal, SF=12 weak).

Valid range is 24Vac/dc ± 10%
Maximum power consumption: 8W

Connect the power supply to pins 11 and 12 of J3 if ac, pins 11 (+) and 10 (-) if dc.

Power can also be supplied by USB, only for configuration, not for normal use.

Dip Switches must be OFF.

To deploy the sensor, use LoRaWEB online tool, to setup LoRaWAN® credentials and other preferences (only available for Windows®) :

LoRaWEB Tool (iot.mcf88.cloud/LoRaWeb)

Before connect the device the first time, please install LoRaBridge applications and drivers:

https://iot.mcf88.cloud/LoRaWeb/#/download

Validate your settings reading data after the write.

enginko provides user manuals, javascript examples, downlink generator, uplink decoder, different tools and, upon free registration, firmware updates :

Save the new firmware file (.exe) on the PC, run the file, select the USB FW port and start the update:

and waiting for the end message.

As default, the device sends a message every time an input or an output changes.

A downlink with new output status forces the device to send back an unplink with the new status. If the output status is the same of current one, the sensor will not send back any message.

Downlink examples (hex):

Is possible to set a period (in minutes) to receive a recurrent periodic message with the I/O status.

In case of DC input, the positive terminal must be connected to the positive input.

Input can be used as pulse counters (see settings chapter).

If driving an inductive load in AC, a Snubber must be provided in parallel to the contacts formed by a RC resistance network = 100Ohm 2w in series with a 100nF 400Volt polyester capacitor. In the case of a DC-controlled load, an anti-parallel diode must be placed on the load (ex. 1N4007). Each line must be protected with a suitable fuse (FUSE).

The output has pulse capability (minimum pulse duration is 100ms, maximum around 100 minutes), so, instead to send two different commands (one to turn on and one to turn off the ouput), is possible to send a duration command.

As application example, to safely turn on an output, send a ON-pulse command for a defined time (for example, for the maximum allowed interval), and before the expiring time, another ON-pulse command (making a kind of watchdog) if the output still needs to be ON, or a simply OFF command if you want to turn it off.

It is possible to program the device with a weekly calendar, based on day of the week and time, to turn ON and OFF the output at a defined time:

and generate and XLS file that can be downloaded by downlinks:

The sensor is compliant with LoRaWAN® specification 1.0.2, regional 1.0.2b.

The device supports the following activations on a LoRaWAN® network:

1. NONE: sensor not activated
2. OTAA: the JoinEUI and the AppKey not setted, must be written to the device;
3. OTAA MCF88: Over the air activation, fixed keys: JoinEUI = 904e915000000003, AppKey on request;
4. OTAA ENGINKO: Over the air activation, fixed keys: JoinEUI = 904e915000000003, AppKey on request;
5. ABP: requires writing to the device of NwkSkey, AppSkey, DevAddr.

The device exits factory activated with NONE 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).

LoRa Band:
select the right LoRaWAN ® band settings accodingly to country requirements.

Status of the output at power on:
select the status of OUTPUT 1 at power-on (default: off).

I/O reading period [min]:
if different from 0, this is the interval (in minutes) between one I/O messages status and the next one. Value can be between 1 and 255 minutes (default: 0 minutes - disabled). Period interval can be set with LoRaWEB or with downlink command.

Number of counter inputs:
Number of inputs used as pulses counters. Value = 1 means that input 1 is a pulses counter, value = 3 means the fist 3 inputs are pulses counter . (default: 0).

Counters reading period [min]:
if counter enabled, this is the interval (in minutes) between one measure and the next one. The sensor sends one measures for every transmission. Value can be between 1 and 255 minutes (default: 0 minutes).
Period interval can be set with LoRaWEB or with downlink command.

Led working:
enable/disable status led (default: enabled).

Time Sync uplink:
enable/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.

Please check chapter 2.1 DATA FRAME FORMAT.

Confirmed uplinks:
set for confirmed uplinks (default: confirmed uplink).

Single join/day:
set for to allow only one join per day (default: multiple join allowed).

USB:
change USB port function (default: Standard).

Timezone:
set to change DST (default: none).

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 999999999 (only numbers).

To change the passwords, set the new values with LoRaWEB:

Once the passwords are setted, to gain access from LoRaWEB to the sensor, 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 enginko (please provide the DevEUI of the sensor when you ask for that code).

With LoRaWEB 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 enginko). 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 enginko's support if needed.

With LoRaWEB 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.

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:

• Use of the general configuration by file;
• Use of the specific configuration by file.

For details on files format please ask to enginko.

enginko provides, upon free registration, 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:

DATA FRAME FORMAT

Hereby, enginko Srl declares that MCF-LW13MIO complies with the essential requirements and other relevant provisions of Directive 2014/53/EU.

enginko Srl
Via Roma 3 I-28060 Sozzago (NO)
T : +39 0321 15 93 088

E : info@enginko.com
PEC: enginkosrl@legalmail.it
W: enginko.com

rev. 0