This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| manual_mcf-lw12met [2023/03/14 10:22] – [4.2 Output] supportadmin | manual_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 |
| * 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 209: | 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 === | ||
| - | 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 | + | 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 |
| {{ : | {{ : | ||
| - | {{ : | + | {{ : |
| and generate and XLS file that can be downloaded by downlinks: | and generate and XLS file that can be downloaded by downlinks: | ||
| - | {{ : | + | {{ : |
| Line 236: | Line 237: | ||
| {{ : | {{ : | ||
| - | ===== 4 LoRaWAN® network ===== | + | ===== 5 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 253: | Line 254: | ||
| {{ : | {{ : | ||
| - | 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 281: | Line 282: | ||
| - | {{ : | ||
| **OUT**:\\ | **OUT**:\\ | ||
| set to force a change of the output (default: off). | set to force a change of the output (default: off). | ||
| + | |||
| + | {{ : | ||
| **DST**:\\ | **DST**:\\ | ||
| Line 319: | 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. | ||
| + | {{ : | ||
| - | Period interval can be set with App or with downlink command. | ||
| **Period**: | **Period**: | ||
| Line 379: | Line 382: | ||
| - | To bring back the sensor to factory default and reset the passwords, a reset code must be requested to enginko | + | To bring back the sensor to factory default and reset the passwords, a reset code must be requested to Angel4Future |
| ===== 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 " | + | With " |
| Line 417: | 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 | + | Angel4Future |
| [[https:// | [[https:// | ||
| Line 448: | 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 | + | Declarations |
| ===== 12 Contacts ===== | ===== 12 Contacts ===== | ||
| - | **enginko Srl** \\ | + | **Angel4Future S.r.l.** \\ |
| - | Via Roma 3 I-28060 Sozzago | + | 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: |
| - | W: | + | |
| ---- | ---- | ||
| - | rev. 0 | + | rev. 1 |