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?

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-lw12met [2023/03/14 08:50] – [2.3Power supply] supportadminmanual_mcf-lw12met [2025/02/28 12:46] (current) – [11 Declaration of conformity] supportadmin
Line 11: Line 11:
   * Do not dismantle or modify in any way.   * Do not dismantle or modify in any way.
   * Avoid mechanical stress   * Avoid mechanical stress
-  * The device is not intended to be used as a reference sensor, and enginko Srl will not be held liable for any damage which may result from inaccurate readings.+  * The device is not intended to be used as a reference sensor, and Angel4FutureSrl will not be held liable for any damage which may result from inaccurate readings.
   * Do not use any detergent or alcohol to clean the device.   * Do not use any detergent or alcohol to clean the device.
   * Do not mount in horizontal position.   * Do not mount in horizontal position.
Line 162: Line 162:
 ===== 4 I/O ===== ===== 4 I/O =====
  
-{{ :wiki:manual_mcf-lw13io:status-lw13io.jpg?400 |}} 
  
 As default, the device sends a message every time an input or an output changes. As default, the device sends a message every time an input or an output changes.
Line 191: Line 190:
  
 {{ :wiki:manual_mcf-lw13io:in-lw13io.jpg |}} {{ :wiki:manual_mcf-lw13io:in-lw13io.jpg |}}
- 
-{{::warning.png?40 |}} __**Caution: NIN and NLINE are internally connected.**__\\ 
- 
  
  
Line 213: Line 209:
 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 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 if the output still needs to be ON, or a simply OFF command if you want to turn it off.
  
 +=== 4.2.1 Time schedule ===
  
-****CALENDAR*****+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 221: Line 226:
 Load connected to the same supply of the sensor, connected to the relay output (normally open contact) and digital input driven by a switch: Load connected to the same supply of the sensor, connected to the relay output (normally open contact) and digital input driven by a switch:
  
-{{ :wiki:manual_mcf-lw13io:220v_load_input.jpg?400 |}}  
  
 +{{ :wiki:manual_mcf-lw12met:load230-lw12met.jpg?nolink&400 |}}
  
 Energy monitoring of a load connected to the same supply of the sensor: Energy monitoring of a load connected to the same supply of the sensor:
  
 +{{ :wiki:manual_mcf-lw12met:load-meter-lw12met.jpg?nolink&400 |}}
  
-Energy monitoring of a load connected to the same supply of the sensor driven by the relay(normally open contact:+Energy monitoring of a load connected to the same supply of the sensor driven by the relay (normally open contact):
  
 +{{ :wiki:manual_mcf-lw12met:load-meter-switch-lw12met.jpg?nolink&400 |}}
  
-===== LoRaWAN® network =====+===== LoRaWAN® network =====
  
 The sensor is compliant with LoRaWAN(r) **specification 1.0.2**, **regional 1.0.2b**. The sensor is compliant with LoRaWAN(r) **specification 1.0.2**, **regional 1.0.2b**.
Line 247: Line 254:
 {{ :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 275: Line 282:
  
  
-{{ :wiki:manual_mcf-lw13io:settings-lw13io.jpg?600 |}} 
 **OUT**:\\ **OUT**:\\
 set to force a change of the output (default: off). set to force a change of the output (default: off).
 +
 +{{ :wiki:manual_egk-lw22plg:settings1.jpg?nolink&400 |}}
  
 **DST**:\\ **DST**:\\
Line 313: Line 321:
 **I/O period [min]**:\\ **I/O 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). 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 App or with downlink command.
  
 +{{ :wiki:manual_egk-lw22plg:settings2.jpg?nolink&400 |}}
  
-Period interval can be set with App or with downlink command. 
  
 **Period**:\\ **Period**:\\
Line 373: Line 382:
  
  
-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).
  
 ===== 7 Configuration file =====  ===== 7 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 411: Line 420:
  
  
-For details on files format please ask to enginko.+For details on files format please ask to Angel4Future.
 ===== 8 LoRaWEB Tool ===== ===== 8 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 442: Line 451:
 ===== 11 Declaration of conformity ===== ===== 11 Declaration of conformity =====
  
-Hereby, enginko Srl declares that MCF-LW12MET complies with the essential requirements and other relevant provisions of Directive  2014/53/EU.+Declarations of conformity are available from Angel4Future by sending a request email to sensor@enginko.com..
  
  
 ===== 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. 1