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.

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.

This device can remotely acquire the accounting data, as EVADTS file, from any vending machine. It can be connected by DDCMP or DEX interface, as well as printer port for other devices. This device can send alarms or triggered events via LoRaWAN® and manage price changes.

MCF-LW06VMC is available with DIN rail option (MCF-DIN105):

• CPU Cortex M4
• RTC
• EEProm 32KB
• Flash 1MB
• Encryption AES 128 bit
• LiPo 800mAh rechargeable battery
• Class A LoRaWAN® stack EU868, AS923, AU915, US915
• USB On The Go
• IoT node setup ad firmware upgrade via USB interface
• Energy harvesting enabled from RS232 data channels
• Optional power supply 10÷36Vdc
• Storage temperature range -20°C ÷ +80°C
• Working temperature range -10°C ÷ +70°C
• Dimensions L x H X P: 81 x 60 x 24mm

Please refer to following connections:

Power can also be supplied by USB.

Please refer to following connections:

Modbus data lines:

Optional Power supply:

Power can also be supplied by USB.

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). Use the provided clip to hold the antenna connector in place, as in the picture:

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 applicarions and drivers:

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

Validate your settings reading data after the write.

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

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.

Period is the interval (in minutes) between one measure and the next one. The sensor sends one measures for every transmission. Value can be between 15 and 65535 minutes (default: 30 minutes).

Period interval can be set with App or with downlink command.

Baudrate [bps]:
set the baudrate for the serial line (defalt = off).

Parity:
set the Modbus frame parity.

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

Time sync uplink:
set to disable time synchronization request (default: enabled).

Normally sensor asks for a time sync at every power on (uplink starting with 01) or once a week. If no or wrong reply received, it will retry after 1 week.

If not handled in the right way can generate unnecessary traffic on the network.

Please check chapter 2.1 DATA FRAME FORMAT.

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

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

LED working:
Set OFF to turn off the diagnostic led.

USB:
Internal use.

Press Check to verify the correct communication betweet the LoRaWAN® interface and the slave(s).

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 = 904e915000000002, AppKey on request;
4. OTAA ENGINKO: Over the air activation, fixed keys: JoinEUI = 904e915000000002, 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).

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

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.

For payload descriptions, uplinks and downlinks format and available commands please refer to this document:

DATA FRAME FORMAT

For payload descriptions, uplinks and downlinks format and available commands please refer to this document:

DATA FRAME FORMAT

Modbus RTU is based on an RS485 bus: TIA/EIA-485 (RS-485) is a single differential balanced line (half duplex).

• It provides a robust communication interface which is inherently noise tolerant since it uses differential as opposed to ground referenced signals.
• It can be cheaply deployed & the cabling is simple, a single pair of wires plus a ground wire.
• Up to 32 devices can be daisy-chained together in a network.

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

This device complies with part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) This device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation.

This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications. However, there is no guarantee that interference will not occur in a particular installation. If this equipment does cause harmful interference to radio or television reception, which can be determined by turning the equipment off and on, the user is encouraged to try to correct the interference by one or more of the following measures:

• Reorient or relocate the receiving antenna.
• Increase the separation between the equipment and receiver.
• Connect the equipment into an outlet on a circuit different from that to which the receiver is connected.
• Consult the dealer or an experienced radio/TV technician for help.

Any changes or modifications not expressly approved by the party responsible for compliance could void the user’s authority to operate this equipment.

Contains FCC ID: 2AWAL409810

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