Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.David - Content
-
... ... @@ -1,41 +1,31 @@ 1 -(% style="text-align:center" %) 2 -[[image:image-20220907171221-1.jpeg]] 1 +[[image:image-20220907171221-1.jpeg]] 3 3 4 - 5 5 6 -{{toc/}} 7 7 5 +**~1. Introduction** 8 8 7 +**1.1 What is NLMS01 **Leaf Moisture Sensor 9 9 10 - =1.Introduction=9 +The Dragino NLMS01 is a **NB-IOT Leaf Moisture Sensor** for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 11 11 11 +NLMS01 detects leaf's** moisture and temperature **use FDR method, it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 12 12 13 -== 1.1 What is NLMS01 Leaf Moisture Sensor == 14 - 15 - 16 -The Dragino NLMS01 is a (% style="color:blue" %)**NB-IOT Leaf Moisture Sensor**(%%) for IoT of Agriculture. It is designed to measure the leaf moisture and temperature, so to send to the platform to analyze the leaf status such as : watering, moisturizing, dew, frozen. The probe is IP67 waterproof. 17 - 18 -NLMS01 detects leaf's(% style="color:blue" %)** moisture and temperature use FDR method**(%%), it senses the dielectric constant cause by liquid over the leaf surface, and cover the value to leaf moisture. The probe is design in a leaf shape to best simulate the real leaf characterizes. The probe has as density as 15 leaf vein lines per centimeter which make it can senses small drop and more accuracy. 19 - 20 20 NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 21 -\\NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement.22 -\\NLMS01 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method).23 -\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%)from local operator and install NLMS01 to get NB-IoT network connection.14 +\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP **for different application requirement. 15 +\\NLMS01 is powered by **8500mAh Li-SOCI2 battery**, It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 16 +\\To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a **NB-IoT SIM card** from local operator and install NLMS01 to get NB-IoT network connection 24 24 25 - 26 26 [[image:image-20220907171221-2.png]] 27 27 28 - 29 29 [[image:image-20220907171221-3.png]] 30 30 22 +**1.2 Features** 31 31 32 - 33 -== 1.2 Features == 34 - 35 - 36 36 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 37 37 * Monitor Leaf moisture 38 -* Monitor Leaf temperature 26 + 27 +* Monitor Leaf temperature 28 + 39 39 * Moisture and Temperature alarm function 40 40 * Monitor Battery Level 41 41 * Uplink on periodically ... ... @@ -47,22 +47,14 @@ 47 47 * Micro SIM card slot for NB-IoT SIM 48 48 * 8500mAh Battery for long term use 49 49 50 -((( 51 - 40 +**1.3 Specification** 52 52 42 +**Common DC Characteristics:** 53 53 54 - 55 -))) 56 - 57 -== 1.3 Specification == 58 - 59 - 60 -(% style="color:#037691" %)**Common DC Characteristics:** 61 - 62 62 * Supply Voltage: 2.1v ~~ 3.6v 63 63 * Operating Temperature: -40 ~~ 85°C 64 64 65 - (% style="color:#037691" %)**NB-IoT Spec:**47 +**NB-IoT Spec:** 66 66 67 67 * - B1 @H-FDD: 2100MHz 68 68 * - B3 @H-FDD: 1800MHz ... ... @@ -71,10 +71,10 @@ 71 71 * - B20 @H-FDD: 800MHz 72 72 * - B28 @H-FDD: 700MHz 73 73 74 - ==1.4==56 +**1.4 Probe Specification** 75 75 76 76 77 - (% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface**59 +**Leaf Moisture: percentage of water drop over total leaf surface** 78 78 79 79 * Range 0-100% 80 80 * Resolution: 0.1% ... ... @@ -82,7 +82,7 @@ 82 82 * IP67 Protection 83 83 * Length: 3.5 meters 84 84 85 - (% style="color:#037691" %)**Leaf Temperature:**67 +**Leaf Temperature:** 86 86 87 87 * Range -50℃~80℃ 88 88 * Resolution: 0.1℃ ... ... @@ -90,40 +90,30 @@ 90 90 * IP67 Protection 91 91 * Length: 3.5 meters 92 92 93 - ==1.5 ==75 +**~ 1.5 Applications** 94 94 95 - 96 96 * Smart Agriculture 97 97 98 - ==1.6==79 +**1.6 Pin mapping and power on** 99 99 100 - 101 101 [[image:image-20220907171221-4.png]] 102 102 103 103 **~ ** 104 104 85 +**2. Use NLMS01 to communicate with IoT Server** 105 105 106 - =2.Use NLMS01 tocommunicatewith IoT Server =87 +**2.1 How it works** 107 107 108 - 109 -== 2.1 How it works == 110 - 111 - 112 112 The NLMS01 is equipped with a NB-IoT module, the pre-loaded firmware in NLMS01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NLMS01. 113 113 114 114 The diagram below shows the working flow in default firmware of NLMS01: 115 115 116 - 117 117 [[image:image-20220907171221-5.png]] 118 118 95 +**2.2 Configure the NLMS01** 119 119 97 +**2.2.1 Test Requirement** 120 120 121 -== 2.2 Configure the NLMS01 == 122 - 123 - 124 -=== 2.2.1 Test Requirement === 125 - 126 - 127 127 To use NLMS01 in your city, make sure meet below requirements: 128 128 129 129 * Your local operator has already distributed a NB-IoT Network there. ... ... @@ -130,120 +130,90 @@ 130 130 * The local NB-IoT network used the band that NLMS01 supports. 131 131 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 132 132 133 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will use (%style="color:#037691" %)**CoAP(120.24.4.116:5683)**(%%)or raw(%style="color:#037691" %)**UDP(120.24.4.116:5601)** or(%%)(% style="color:#037691"%)**MQTT(120.24.4.116:1883)**(%%)or(% style="color:#037691" %)**TCP(120.24.4.116:5600)**(%%)protocol to send data to the test server105 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NLMS01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server 134 134 135 - 136 136 [[image:image-20220907171221-6.png]] 137 137 109 +**2.2.2 Insert SIM card** 138 138 139 - 140 -=== 2.2.2 Insert SIM card === 141 - 142 - 143 143 Insert the NB-IoT Card get from your provider. 144 144 145 145 User need to take out the NB-IoT module and insert the SIM card like below: 146 146 147 - 148 148 [[image:image-20220907171221-7.png]] 149 149 117 +**2.2.3 Connect USB – TTL to NLMS01 to configure it** 150 150 119 +User need to configure NLMS01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below. 151 151 152 - === 2.2.3ConnectUSB – TTL toNLMS01 to configure it ===121 +**Connection:** 153 153 123 + USB TTL GND <~-~-~-~-> GND 154 154 155 - Userneed to configure NLMS01 via serial port to set the (% style="color:#037691" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USBtoTTLadaptertoconnect to NLMS01 and useATCommands to configure it, as below.125 + USB TTL TXD <~-~-~-~-> UART_RXD 156 156 127 + USB TTL RXD <~-~-~-~-> UART_TXD 157 157 158 -(% style="color:blue" %)**Connection:** 159 - 160 -**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)** 161 - 162 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 163 - 164 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 165 - 166 - 167 167 In the PC, use below serial tool settings: 168 168 169 -* Baud: (% style="color:green" %)**9600**170 -* Data bits:** (% style="color:green" %)8(%%)**171 -* Stop bits: (% style="color:green" %)**1**172 -* Parity: (% style="color:green" %)**None**173 -* Flow Control: (% style="color:green" %)**None**131 +* Baud: **9600** 132 +* Data bits:** 8** 133 +* Stop bits: **1** 134 +* Parity: **None** 135 +* Flow Control: **None** 174 174 175 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%)to access AT Command input.137 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input. 176 176 177 -[[image:image-202209 13090720-1.png]]139 +[[image:image-20220907171221-8.png]] 178 178 141 +**Note: the valid AT Commands can be found at: **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 179 179 180 - (% style="color:red" %)**Note:thevalid AT Commandscan befoundat: **(%%)[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]143 +**2.2.4 Use CoAP protocol to uplink data** 181 181 145 +**Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 182 182 147 +**Use below commands:** 183 183 184 -=== 2.2.4 Use CoAP protocol to uplink data === 149 +* **AT+PRO=1** ~/~/ Set to use CoAP protocol to uplink 150 +* **AT+SERVADDR=120.24.4.116,5683 ** ~/~/ to set CoAP server address and port 151 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path 185 185 186 - 187 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]] 188 - 189 - 190 -(% style="color:blue" %)**Use below commands:** 191 - 192 -* (% style="color:#037691" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 193 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 194 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 195 - 196 - 197 - 198 198 For parameter description, please refer to AT command set 199 199 200 200 [[image:image-20220907171221-9.png]] 201 201 157 +After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 202 202 203 -After configure the server address and (% style="color:#037691" %)**reset the device**(%%) (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server. 204 - 205 205 [[image:image-20220907171221-10.png]] 206 206 161 +**2.2.5 Use UDP protocol to uplink data(Default protocol)** 207 207 208 - 209 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 210 - 211 - 212 212 This feature is supported since firmware version v1.0.1 213 213 214 -* (% style="color:#037691" %)**AT+PRO=2 **(%%)~/~/215 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601(%%)~/~/216 -* (% style="color:#037691" %)**AT+CFM=1 **(%%)~/~/165 +* **AT+PRO=2 ** ~/~/ Set to use UDP protocol to uplink 166 +* **AT+SERVADDR=120.24.4.116,5601 ** ~/~/ to set UDP server address and port 167 +* **AT+CFM=1 ** ~/~/If the server does not respond, this command is unnecessary 217 217 218 - 219 - 220 220 [[image:image-20220907171221-11.png]] 221 221 222 - 223 223 [[image:image-20220907171221-12.png]] 224 224 225 225 226 226 175 +**2.2.6 Use MQTT protocol to uplink data** 227 227 228 -=== 2.2.6 Use MQTT protocol to uplink data === 229 - 230 - 231 231 This feature is supported since firmware version v110 232 232 233 -* (% style="color:#037691" %)**AT+PRO=3 **(%%)~/~/234 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883 **(%%)~/~/235 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT **(%%)~/~/236 -* (% style="color:#037691" %)**AT+UNAME=UNAME **(%%)** **~/~/237 -* (% style="color:#037691" %)**AT+PWD=PWD **(%%)** **~/~/238 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB **(%%)~/~/239 -* (% style="color:#037691" %)**AT+SUBTOPIC=SUB **(%%)179 +* **AT+PRO=3 ** ~/~/Set to use MQTT protocol to uplink 180 +* **AT+SERVADDR=120.24.4.116,1883 ** ~/~/Set MQTT server address and port 181 +* **AT+CLIENT=CLIENT ** ~/~/Set up the CLIENT of MQTT 182 +* **AT+UNAME=UNAME **~/~/Set the username of MQTT 183 +* **AT+PWD=PWD **~/~/Set the password of MQTT 184 +* **AT+PUBTOPIC=NSE01_PUB **~/~/Set the sending topic of MQTT 185 +* **AT+SUBTOPIC=NSE01_SUB ** ~/~/Set the subscription topic of MQTT 240 240 241 - 242 - 243 243 [[image:image-20220907171221-13.png]] 244 244 245 - 246 - 247 247 [[image:image-20220907171221-14.png]] 248 248 249 249 ... ... @@ -250,83 +250,63 @@ 250 250 251 251 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 252 252 195 +**2.2.7 Use TCP protocol to uplink data** 253 253 254 - 255 -=== 2.2.7 Use TCP protocol to uplink data === 256 - 257 - 258 258 This feature is supported since firmware version v110 259 259 260 -* (% style="color:#037691" %)**AT+PRO=4 **(%%)~/~/261 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 **(%%)~/~/199 +* **AT+PRO=4 ** ~/~/ Set to use TCP protocol to uplink 200 +* **AT+SERVADDR=120.24.4.116,5600 ** ~/~/ to set TCP server address and port 262 262 263 - 264 - 265 265 [[image:image-20220907171221-15.png]] 266 266 267 - 268 - 269 269 [[image:image-20220907171221-16.png]] 270 270 271 271 272 272 208 +**2.2.8 Change Update Interval** 273 273 274 -=== 2.2.8 Change Update Interval === 275 - 276 - 277 277 User can use below command to change the **uplink interval**. 278 278 279 -* (% style="color:#037691" %)**AT+TDC=7200 **(%%)~/~/ Set Update Interval to7200s(2 hour)212 +* **AT+TDC=600 ** ~/~/ Set Update Interval to 600s 280 280 214 +**NOTE:** 281 281 216 +**~1. By default, the device will send an uplink message every 2 hour.** 282 282 283 - (% style="color:red" %)**NOTE: By default, the device will send an uplink message every2hour.EachUplinkInclude 8 set of records in this 2 hour (15 minute interval/ record).**218 +**2.3 Uplink Payload** 284 284 285 - 286 - 287 -== 2.3 Uplink Payload == 288 - 289 - 290 290 In this mode, uplink payload includes 87 bytes in total by default. 291 291 292 292 Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 293 293 224 +|**Size(bytes)**|**8**|**2**|**2**|**1**|**1**|1|2|2|2|4 225 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Soil PH|Time stamp ..... 294 294 295 -(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 296 -|(% style="width:96px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:42px" %)**2**|(% style="width:48px" %)**2**|(% style="width:124px" %)1|(% style="width:58px" %)1|(% style="width:82px" %)1|(% style="width:113px" %)2|(% style="width:134px" %)2|(% style="width:100px" %)4|(% style="width:137px" %)2|(% style="width:110px" %)2|(% style="width:122px" %)4 297 -|(% style="width:96px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:42px" %)Ver|(% style="width:48px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:58px" %)MOD|(% style="width:82px" %)Interrupt|(% style="width:113px" %)Leaf moisture|(% style="width:134px" %)Leaf Temperature|(% style="width:100px" %)Time stamp|(% style="width:137px" %)Leaf Temperature|(% style="width:110px" %)Leaf moisture|(% style="width:122px" %)Time stamp ..... 298 - 299 - 300 300 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 301 301 302 - 303 303 [[image:image-20220907171221-17.png]] 304 304 305 - 306 306 The payload is ASCII string, representative same HEX: 307 307 308 -0x (% style="color:red" %)f868411056754138(% style="color:blue" %)0064(% style="color:green" %)0c78(% style="color:red" %)17(% style="color:blue" %)01(% style="color:green" %)00(% style="color:blue" %)**0225010b6315537b**010b0226631550fb**010e022663154d77**01110225631549f1**011502246315466b**01190223631542e5**011d022163153f62**011e022163153bde**011e022163153859**(%%)****where:233 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where: 309 309 310 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 311 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0 312 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 313 -* (% style="color:red" %)Singal: 0x17 = 23 314 -* (% style="color:blue" %)Mod: 0x01 = 1 315 -* (% style="color:green" %)Interrupt: 0x00= 0 235 +* Device ID: 0xf868411056754138 = f868411056754138 236 +* Version: 0x0064=100=1.0.0 237 + 238 +* BAT: 0x0c78 = 3192 mV = 3.192V 239 +* Singal: 0x17 = 23 240 +* Mod: 0x01 = 1 241 +* Interrupt: 0x00= 0 316 316 * Leaf moisture: 0x0225= 549 = 54.9% 317 317 * Leaf Temperature:0x010B =267=26.7 °C 318 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])244 +* Time stamp : 0x6315537b =1662342011 319 319 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 320 -* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......246 +* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 321 321 248 +**2.4 Payload Explanation and Sensor Interface** 322 322 250 +**2.4.1 Device ID** 323 323 324 - 325 - 326 -== 2.4 Payload Explanation and Sensor Interface == 327 - 328 -=== 2.4.1 Device ID === 329 - 330 330 By default, the Device ID equal to the last 15 bits of IMEI. 331 331 332 332 User can use **AT+DEUI** to set Device ID ... ... @@ -337,13 +337,13 @@ 337 337 338 338 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 339 339 340 - ===2.4.2 Version Info===262 +**2.4.2 Version Info** 341 341 342 342 Specify the software version: 0x64=100, means firmware version 1.00. 343 343 344 344 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 345 345 346 - ===2.4.3 Battery Info===268 +**2.4.3 Battery Info** 347 347 348 348 Check the battery voltage for NLMS01. 349 349 ... ... @@ -351,7 +351,7 @@ 351 351 352 352 Ex2: 0x0B49 = 2889mV 353 353 354 - ===2.4.4 Signal Strength===276 +**2.4.4 Signal Strength** 355 355 356 356 NB-IoT Network signal Strength. 357 357 ... ... @@ -367,7 +367,7 @@ 367 367 368 368 **99** Not known or not detectable 369 369 370 - ===2.4.5 Leaf moisture===292 +**2.4.5 Leaf** moisture 371 371 372 372 Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**. 373 373 ... ... @@ -375,7 +375,7 @@ 375 375 376 376 **0229(H) = 549(D) /100 = 54.9.** 377 377 378 - ===2.4.6 Leaf Temperature===300 +**2.4.6 Leaf Temperature** 379 379 380 380 Get the temperature in the **Leaf**. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the **Leaf**. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the **Leaf **is 381 381 ... ... @@ -385,13 +385,13 @@ 385 385 386 386 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 387 387 388 - ===2.4.7 Timestamp===310 +**2.4.7 Timestamp** 389 389 390 390 Time stamp : 0x6315537b =1662342011 391 391 392 392 Convert Unix timestamp to time 2022-9-5 9:40:11. 393 393 394 - ===2.4.8 Digital Interrupt===316 +**2.4.8 Digital Interrupt** 395 395 396 396 Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 397 397 ... ... @@ -407,7 +407,7 @@ 407 407 408 408 0x(01): Interrupt Uplink Packet. 409 409 410 - ===2.4.9 +5V Output===332 +**2.4.9 +5V Output** 411 411 412 412 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 413 413 ... ... @@ -418,7 +418,7 @@ 418 418 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 419 419 420 420 421 - ==2.5 Downlink Payload==343 +**2.5 Downlink Payload** 422 422 423 423 By default, NLMS01 prints the downlink payload to console port. 424 424 ... ... @@ -442,7 +442,7 @@ 442 442 443 443 Downlink Payload: 06000003, Set AT+INTMOD=3 444 444 445 - ==2.6 LED Indicator==367 +**2.6 LED Indicator** 446 446 447 447 The NLMS01 has an internal LED which is to show the status of different state. 448 448 ... ... @@ -451,13 +451,13 @@ 451 451 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 452 452 * For each uplink probe, LED will be on for 500ms. 453 453 454 - ==2.7 Installation==376 +**2.7 Installation** 455 455 456 456 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 457 457 458 458 [[image:image-20220907171221-19.png]] 459 459 460 - ==2.8 Moisture and Temperature alarm function==382 +**2.8 Moisture and Temperature alarm function** 461 461 462 462 ➢ AT Command: 463 463 ... ... @@ -486,15 +486,16 @@ 486 486 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 487 487 488 488 489 - ==2.9 Set the number of data to be uploaded and the recording time==411 +**2.9 Set the number of data to be uploaded and the recording time** 490 490 491 491 ➢ AT Command: 492 492 493 493 AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 494 494 417 + 495 495 AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 496 496 497 - ==2.10 Read or Clear cached data==420 +**2.10 Read or Clear cached data** 498 498 499 499 ➢ AT Command: 500 500 ... ... @@ -506,15 +506,15 @@ 506 506 AT+CDP=0 ~/~/ Clear cached data 507 507 508 508 509 - ==2.11Firmware Change Log==432 +**2.8 Firmware Change Log** 510 510 511 511 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 512 512 513 513 Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 514 514 515 - ==2.12Battery Analysis==438 +**2.9 Battery Analysis** 516 516 517 - ===2.12.1 Battery Type===440 +**2.9.1 Battery Type** 518 518 519 519 The NLMS01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 520 520 ... ... @@ -528,7 +528,7 @@ 528 528 529 529 [[image:image-20220907171221-21.png]] 530 530 531 - ===2.12.2 Power consumption Analyze===454 +**2.9.2 Power consumption Analyze** 532 532 533 533 Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 534 534 ... ... @@ -546,15 +546,15 @@ 546 546 547 547 [[image:image-20220907171221-22.jpeg]] 548 548 549 - ===2.12.3 Battery Note===472 +**2.9.3 Battery Note** 550 550 551 551 The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased. 552 552 553 - ===2.12.4 Replace the battery===476 +**2.9.4 Replace the battery** 554 554 555 555 The default battery pack of NLMS01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 556 556 557 - =3. Access NB-IoT Module=480 +**3. Access NB-IoT Module** 558 558 559 559 Users can directly access the AT command set of the NB-IoT module. 560 560 ... ... @@ -562,9 +562,9 @@ 562 562 563 563 [[image:image-20220907171221-23.png]] 564 564 565 - =4. Using the AT Commands=488 +**4. Using the AT Commands** 566 566 567 - ==4.1 Access AT Commands==490 +**4.1 Access AT Commands** 568 568 569 569 See this link for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]] 570 570 ... ... @@ -600,20 +600,15 @@ 600 600 601 601 AT+SERVADDR : Server Address 602 602 603 -AT+APN : Get or set the APN 604 - 605 -AT+FBAND : Get or Set whether to automatically modify the frequency band 606 - 607 -AT+DNSCFG : Get or Set DNS Server 608 - 609 -AT+GETSENSORVALUE : Returns the current sensor measurement 610 - 611 611 AT+TR : Get or Set record time" 612 612 528 + 613 613 AT+NOUD : Get or Set the number of data to be uploaded 614 614 531 + 615 615 AT+CDP : Read or Clear cached data 616 616 534 + 617 617 AT+TEMPALARM : Get or Set alarm of temp 618 618 619 619 AT+HUMALARM : Get or Set alarm of PH ... ... @@ -645,9 +645,9 @@ 645 645 646 646 AT+PWORD : Serial Access Password 647 647 648 - =5. FAQ=566 +**5. FAQ** 649 649 650 - ==5.1 How to Upgrade Firmware==568 +**5.1 How to Upgrade Firmware** 651 651 652 652 User can upgrade the firmware for 1) bug fix, 2) new feature release. 653 653 ... ... @@ -655,21 +655,21 @@ 655 655 656 656 **Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.** 657 657 658 - =6. Trouble Shooting=576 +**6. Trouble Shooting** 659 659 660 - ==6.1 Connection problem when uploading firmware==578 +**6.1 Connection problem when uploading firmware** 661 661 662 662 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 663 663 664 - ==6.2 AT Command input doesn't work==582 +**6.2 AT Command input doesn't work** 665 665 666 666 In the case if user can see the console output but can't type input to the device. Please check if you already include the **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string. 667 667 668 - =7. Order Info=586 +**7. Order Info** 669 669 670 670 Part Number**:** NLMS01 671 671 672 - =8. Packing Info=590 +**8. Packing Info** 673 673 674 674 **Package Includes**: 675 675 ... ... @@ -682,9 +682,12 @@ 682 682 * Package Size / pcs : cm 683 683 * Weight / pcs : g 684 684 685 -= 9. Support = 686 686 604 +**9. Support** 605 + 687 687 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 688 688 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 689 689 690 690 610 + 611 +
- image-20220913090720-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -224.9 KB - Content