Plugin name 'sidebar.BROKEN' is not a valid plugin name, only the characters a-z and 0-9 are allowed. Maybe the plugin has been installed in the wrong directory?

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

Trace: › manual_mcf-lw12ter

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
manual_mcf-lw13io [2022/01/25 10:30] – [3.1 Input] supportadminmanual_mcf-lw13io [2025/11/06 15:37] (current) – [10 Declaration of conformity] supportadmin
Line 15: Line 15:
  
 === Disposal information for users === === Disposal information for users ===
-{{:wiki:manual_mcf-LW12TERWP:1200px-weee_symbol_vectors.svg.png?50 |}}**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). **+{{:wiki:manual_mcf-LW12CO2E:1200px-weee_symbol_vectors.svg.png?50 |}}**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.  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. 
Line 124: Line 124:
 ==== 2.6 Firmware update====  ==== 2.6 Firmware update====
  
-Save the firmware file (.FW) on the smartphone, and upload it with LoraTool App:+Download the latest firmwares available on the smartphone with LoRaTool app: 
 + 
 +{{ :wiki:manual_egk-lw20w00:update_firmwares.jpg?direct&400 |}} 
 + 
 +{{ :wiki:manual_egk-lw22plg:fwdownload.jpg?nolink&400 |}} 
 + 
 +{{ :wiki:manual_egk-lw22plg:fwdownload1.jpg?nolink&400 |}} 
 + 
 +Update the sensor with LoRaTool:
  
 {{ :wiki:manual_mcf-lw13io:upload.jpg?400 |}} {{ :wiki:manual_mcf-lw13io:upload.jpg?400 |}}
Line 152: Line 160:
 ==== 3.1 Input ==== ==== 3.1 Input ====
  
-|Off voltage  |0÷2Vac 50/60Hz  | +| Off voltage                 | 0÷2Vac 50/60Hz  | 
-|On Voltage  |> 8Vac 50/60Hz  | +| On Voltage                  | > 8Vac 50/60Hz  | 
-|Maximum input voltage  |250Vac 50/60Hz  | +| Maximum input voltage       | 250Vac 50/60Hz  | 
-|Input current  |3mA typ  | +| Input current               | 5mA typ         | 
-|Max frequency (as counter)|2 Hz  | +| Max frequency (as counter)  | 2 Hz            | 
-|Optoinsulation  |NONE  |+| Optoinsulation              | NONE            |
  
  
Line 165: Line 173:
  
  
-Input can be used as pulse counters (see seetings chapter).+ 
 +Input can be used as pulse counters (see settings chapter).
  
  
 ==== 3.2 Output ==== ==== 3.2 Output ====
- 
- 
  
 |Contact mode  |SPDT  | |Contact mode  |SPDT  |
Line 177: Line 184:
 |Max. current  |8A  | |Max. current  |8A  |
  
-{{ :wiki:manual_mcf-lw13io:out-lw13io.jpg?300 |}}+{{  :wiki:manual_mcf-lw13io:out-lw13io.jpg?300  }}
  
 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.\\ 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. 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.
 +
 +=== 3.2.1 Time schedule ===
 +
 +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:
 +
 +{{  :wiki:manual_mcf-lw12met:calendar.jpg?nolink&400  }}
 +
 +{{  :wiki:manual_mcf-lw12met:time-schedule.jpg?direct&800  }}
 +
 +and generate and XLS file that can be downloaded by downlinks:
 +
 +{{  :wiki:manual_mcf-lw12met:calendar_table.jpg?direct&600  }}
  
  
Line 210: Line 229:
 {{ :wiki:manual_mcf-lw12co2e:activation1_0.jpg?400 |}} {{ :wiki:manual_mcf-lw12co2e:activation1_0.jpg?400 |}}
  
-The device exits factory activated with **NONE** mode.+The device exits factory activated with **OTAA ENGINKO** mode.
 On request devices can be shipped aleady activated. On request devices can be shipped aleady activated.
  
Line 253: Line 272:
 Normally sensor asks for a time sync at every power on (uplink starting with 01) or, if enabled, once a week. 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 of "DATA FRAME FORMAT" document.+Please check chapter 2.1 [[data_frame_format| DATA FRAME FORMAT]].
 ----- -----
  
Line 303: Line 322:
  
  
-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).+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).
  
 ===== 6 Configuration file =====  ===== 6 Configuration file =====
  
-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 enginko). This is very useful especially in  +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.
-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 "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.
  
  
Line 328: Line 346:
 When the sensor is approached, if one parameter is different from files, the APP will ask you if you want to overwrite. 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 is in the XLS file, LoRa parameters will be setted from this one.+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: These configuration can be done in the in the Settings:
Line 341: Line 359:
  
  
-For details on files format please ask to enginko.+For details on files format please ask to Angel4Future.
 ===== 7 LoRaWEB Tool ===== ===== 7 LoRaWEB Tool =====
  
-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:+Angel4Future provides free **LoRaWEB** online tool,  where for each sensor it is possible to find documentation, javascript examples for parsing, downlink generator and uplink decoder:
  
 [[https://iot.mcf88.cloud/LoRaWeb/#/configuration|LoRaWEB Tool]] [[https://iot.mcf88.cloud/LoRaWeb/#/configuration|LoRaWEB Tool]]
Line 369: Line 387:
 |MCF-LW13IO-AU |  enginko LoRaWAN(r) wireless actuator  AU915-928  | |MCF-LW13IO-AU |  enginko LoRaWAN(r) wireless actuator  AU915-928  |
  
-===== 10 Declaration of conformity =====+===== 10 Declaration of conformity ===== 
 + 
 +Declarations of conformity are available from Angel4Future by sending a request email to sensors@enginko.com.
  
-Hereby, enginko Srl declares that MCF-LW13IO complies with the essential requirements and other relevant provisions of Directive  2014/53/EU. 
  
 ===== 11 FCC compliance for MCF-LW13IO-US ===== ===== 11 FCC compliance for MCF-LW13IO-US =====
Line 391: Line 410:
 ===== 12 Contacts ===== ===== 12 Contacts =====
  
-**enginko Srl** \\  +**Angel4Future S.r.l.** \\  
-Via Roma 3  I-28060 Sozzago (NO) \\  +Via San Sabino 21 - 70042 MOLA DI BARI (BA) , ITALY \\  
-T  :    +39 0321 15 93 088 \\  +T  :    +39 080 532 1796 \\  
  
-E  :    info@enginko.com  \\  +E  :    info@angel4future.com  \\ 
-PEC: enginkosrl@legalmail.it \\ +
 W:     enginko.com \\  W:     enginko.com \\ 
  
 ---- ----
  
-rev. 0+ 
 + 
 +rev. 2
Last modified: 2023/05/29 07:33