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-lw06485 [2023/05/29 07:33] – external edit 127.0.0.1manual_mcf-lw06485 [2025/02/28 12:37] (current) – [12 Declaration of conformity] supportadmin
Line 136: Line 136:
  
  
-enginko provides, upon free registration,  user manuals, javascript examples, downlink generator, uplink decoder, firmware updates and different tools :+Angel4Future provides user manuals, javascript examples, downlink generator, uplink decoder, firmware updates and different tools :
  
  
Line 195: Line 195:
 __**Note:**__\\ __**Note:**__\\
 when saving these parameters, the system asks if you want to save only or to save and load the Modbus configuration file. when saving these parameters, the system asks if you want to save only or to save and load the Modbus configuration file.
-==== 4.2.2 Registers map configuration ====+==== 4.2.2 Registers map configuration ====
  
 Basic configuration is made through an .XLS file containing, for every row, the parameters of the register(s) to be read or write. Basic configuration is made through an .XLS file containing, for every row, the parameters of the register(s) to be read or write.
  
-{{ :wiki:manual_mcf-lw06485:conf_table.jpg? |}}+{{  :wiki:manual_mcf-lw06485:conf_table.jpg  }}
  
 Template file can be downloaded here: Template file can be downloaded here:
Line 205: Line 205:
 [[https://s3-eu-west-1.amazonaws.com/public.mcf88.cloud/LoRaWeb/Documents/Modbus_configuration.xls|Modbus configuration file template]] [[https://s3-eu-west-1.amazonaws.com/public.mcf88.cloud/LoRaWeb/Documents/Modbus_configuration.xls|Modbus configuration file template]]
  
-File can be uploaded via USB or sent with LoRaWAN(r) dowlinks.+File can be uploaded via USB or sent with LoRaWAN® dowlinks.
  
-Due to the radio regulation, the amount of data that the interface can send  during a period of time can vary, and depends also from duty cycle, spreading factor and data rate.+Due to the radio regulation, the amount of data that the interface can send during a period of time can vary, and depends also from duty cycle, spreading factor and data rate.
  
-For example, with EU868 band, the MCF-LW06485 can send from 1KB (SF = 12)  to 30KB (SF = 7) every hour. +For example, with EU868 band, the MCF-LW06485 can send from 1KB (SF = 12) to 30KB (SF = 7) every hour. In case of periodic transmission, you have to set the reading period related to the amount of data you have to send for every reading from the slaves.
-In case of periodic transmission, you have to set the reading period related to the amount of data you have to send for every reading from the slaves.+
  
 +=== 4.2.3 Configuration file format ===
  
- +**Label:** \\
-=== 4.2.3 Configuration file format === +
- +
- +
- +
-**Label:**\\+
 mnemonic label of the register.\\ mnemonic label of the register.\\
 +**Modbus address:** \\
 +slave address (expressed as decimal value)
  
-**Modbus address:**\\ +**Modbus function:** \\ 
-slave address (expressed as decimal value) +^ Function Code ^ Register Type ^
  
-**Modbus function:**\\ +|1  |Read Coil  
-^ Function Code  ^ Register Type                     ^ +|2  |Read Discrete Input  
-| 1              | Read Coil                         +|3  |Read Holding Registers  
-| 2              | Read Discrete Input               +|4  |Read Input Registers  
-| 3              | Read Holding Registers            +|5  |Write Single Coil  
-| 4              | Read Input Registers              +|6  |Write Single Holding Register  
-| 5              | Write Single Coil                 +|15  |Write Multiple Coils  
-| 6              | Write Single Holding Register     +|16  |Write Multiple Holding Registers  |
-| 15             | Write Multiple Coils              +
-| 16             | Write Multiple Holding Registers  |+
  
-**Dec address:**\\+**Dec address:** \\
 register starting address (expressed as decimal value), without offset. register starting address (expressed as decimal value), without offset.
  
-__Note:__\\+__Note:__ \\
 please check [[#modbus_rtu_basicsregisters_addressing|Modbus addressing]] please check [[#modbus_rtu_basicsregisters_addressing|Modbus addressing]]
-  
  
-**Modbus length:**\\+**Modbus length:** \\
 lenght (in word) of the register to be read or write.\\ lenght (in word) of the register to be read or write.\\
 __Attention:__ in case of "Write Single Coil", length must be 1, and data 00 (disable) or 01 (enable).\\ __Attention:__ in case of "Write Single Coil", length must be 1, and data 00 (disable) or 01 (enable).\\
 In case of "Write Multiple Coils", Length is the number of coils, and data must be n byte long, with n = (length + 7) / 8. In case of "Write Multiple Coils", Length is the number of coils, and data must be n byte long, with n = (length + 7) / 8.
  
- +**Data:** \\
-**Data:**\\+
 in case of write command, data to be write, hexadecimal values formatted as string.\\ in case of write command, data to be write, hexadecimal values formatted as string.\\
-__Always use  ‘ (single quote) before the digits).__+__Always use ‘ (single quote) before the digits).__
  
-**Baudrate (bps):**\\+**Baudrate (bps):** \\
 serial line baudrate, __only needed if different from the settings in LoRaWEB__.\\ serial line baudrate, __only needed if different from the settings in LoRaWEB__.\\
 Allowed values: 1200, 2400, 4800, 9600, 19200. 38400, 57600, 115200. Allowed values: 1200, 2400, 4800, 9600, 19200. 38400, 57600, 115200.
  
-**Parity/stop:**\\+**Parity/stop:** \\
 serial line parity/stop, __only needed if different from the settings in LoRaWEB__.\\ serial line parity/stop, __only needed if different from the settings in LoRaWEB__.\\
 Allowed values: 8-n-1, 8-n-2, 8-e-1, 8- o -1 for none, even or odd Allowed values: 8-n-1, 8-n-2, 8-e-1, 8- o -1 for none, even or odd
  
 +__**Examples:**__ \\
 +reading a 2 byte holding register, starting from address 10001 of slave 1
  
 +^Label  ^Modbus address  ^Modbus function  ^Dec address  ^Modbus length  ^Data  ^Baudrate (bps)  ^Parity/stop  |
 +|Input status  |1  |3  |10001  |1  |       |
  
-__**Examples:**__\\ +writing a 2 byte holding register (with value 1000h), starting from address 53 of slave 2:
-reading a 2 byte holding register, starting from address 10001 of slave 1+
  
-^ Label          ^ Modbus address  ^ Modbus function  ^ Dec address  ^ Modbus length  ^ Data  ^ Baudrate (bps)  ^ Parity/stop  ^ +^Label  ^Modbus address  ^Modbus function  ^Dec address  ^Modbus length  ^Data  ^Baudrate (bps)  ^Parity/stop  | 
-Input status               3                10001        | 1                                                 |+|Analog output 1|2  |6  |53  |1  |1000      |
  
 +=== 4.2.4 Configuration with LoraWEB (via USB)  ===
  
-writing a 2 byte holding register (with value 1000h), starting from address 53 of slave 2: +To upload the new configuration file (.XLSselect "Save configuration" button:
-^ Label   ^ Modbus address  ^ Modbus function  ^ Dec address  ^ Modbus length  ^ Data  ^ Baudrate (bps)  ^ Parity/stop +
-| Analog output 1 | 2               | 6                | 53           | 1              | 1000  |                              |+
  
-=== 4.2.4 Configuration with downlinks ===+{{ :wiki:manual_mcf-lw06485:save.jpg?&800 |}}
  
-{{ :wiki:manual_mcf-lw06485:mtod.jpg?nolink&400 |}}+and then "Upload and Save":
  
 +{{ :wiki:manual_mcf-lw06485:upload.jpg?nolink&600 |}}
 +
 +then select the file to be loaded.
 +
 +__The file must be closed before this operation__.
 +
 +=== 4.2.5 Configuration with downlinks ===
 +
 +{{  :wiki:manual_mcf-lw06485:mtod.jpg?nolink&400  }}
  
 **MODBUS to Downlink converter**:\\ **MODBUS to Downlink converter**:\\
 convert the .XLS configuration file in one or more downlink payload to be sent to the device instead using USB port-. convert the .XLS configuration file in one or more downlink payload to be sent to the device instead using USB port-.
  
-{{ :wiki:manual_mcf-lw06485:converter.jpg?nolink&400 |}} +{{  :wiki:manual_mcf-lw06485:converter.jpg?nolink&400  }}
  
 **Temporary Downlink**:\\ **Temporary Downlink**:\\
 the configuration file is executed and then discarded. the configuration file is executed and then discarded.
- 
  
 **Configuration Downlink**:\\ **Configuration Downlink**:\\
 the configuration file is saved in memory and executed periodically. the configuration file is saved in memory and executed periodically.
 +
  
 ==== 4.3 Other settings ==== ==== 4.3 Other settings ====
Line 357: Line 360:
 {{ :wiki:loraweb:loraweb_lora.jpg?direct&600 |}} {{ :wiki:loraweb:loraweb_lora.jpg?direct&600 |}}
  
-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 401: Line 404:
  
  
-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).
  
 ===== 8 General configuration file =====  ===== 8 General configuration file =====
  
-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 +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 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 433: Line 436:
  
  
-For details on files format please ask to enginko.+For details on files format please ask to Angel4Future.
  
 ===== 9 Payload ===== ===== 9 Payload =====
Line 557: Line 560:
 ===== 12 Declaration of conformity ===== ===== 12 Declaration of conformity =====
  
-Hereby, enginko Srl declares that MCF-LW06485 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.
  
 ===== 13 FCC compliance for MCF-LW06485-US ===== ===== 13 FCC compliance for MCF-LW06485-US =====
Line 576: Line 579:
 ===== 14 Contacts ===== ===== 14 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.1+rev.2