This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
| manual_mcf-lw13io [2023/05/29 07:33] – external edit 127.0.0.1 | manual_mcf-lw13io [2025/11/06 15:37] (current) – [10 Declaration of conformity] supportadmin | ||
|---|---|---|---|
| Line 178: | Line 178: | ||
| ==== 3.2 Output ==== | ==== 3.2 Output ==== | ||
| - | |||
| - | |||
| |Contact mode |SPDT | | |Contact mode |SPDT | | ||
| Line 186: | Line 184: | ||
| |Max. current | |Max. current | ||
| - | {{ : | + | {{ : |
| 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 === | + | === 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: | 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: | and generate and XLS file that can be downloaded by downlinks: | ||
| - | {{ : | + | {{ : |
| ==== 3.3 Wiring examples ==== | ==== 3.3 Wiring examples ==== | ||
| Line 230: | Line 229: | ||
| {{ : | {{ : | ||
| - | 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 323: | Line 322: | ||
| - | 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 |
| ===== 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 " | + | With " |
| Line 361: | 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 | + | Angel4Future |
| [[https:// | [[https:// | ||
| Line 389: | Line 387: | ||
| |MCF-LW13IO-AU | enginko LoRaWAN(r) wireless actuator | |MCF-LW13IO-AU | enginko LoRaWAN(r) wireless actuator | ||
| - | ===== 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 | ||
| ===== 11 FCC compliance for MCF-LW13IO-US ===== | ===== 11 FCC compliance for MCF-LW13IO-US ===== | ||
| Line 411: | Line 410: | ||
| ===== 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. 1 | + | |
| + | |||
| + | rev. 2 | ||