Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
<
edited by Mengting Qiu
on 2024/04/02 16:54
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, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.ting - Content
-
... ... @@ -1,8 +1,15 @@ 1 + 2 + 1 1 (% style="text-align:center" %) 2 2 [[image:image-20220907171221-1.jpeg]] 3 3 4 4 5 5 8 + 9 + 10 + 11 + 12 + 6 6 {{toc/}} 7 7 8 8 ... ... @@ -9,20 +9,24 @@ 9 9 10 10 = 1. Introduction = 11 11 12 - 13 13 == 1.1 What is NLMS01 Leaf Moisture Sensor == 14 14 15 15 22 +((( 16 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 17 18 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 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. 24 24 29 +NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 25 25 31 +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). 32 + 33 +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. 34 +))) 35 + 36 + 26 26 [[image:image-20220907171221-2.png]] 27 27 28 28 ... ... @@ -29,7 +29,6 @@ 29 29 [[image:image-20220907171221-3.png]] 30 30 31 31 32 - 33 33 == 1.2 Features == 34 34 35 35 ... ... @@ -50,7 +50,6 @@ 50 50 ((( 51 51 52 52 53 - 54 54 55 55 ))) 56 56 ... ... @@ -64,12 +64,12 @@ 64 64 65 65 (% style="color:#037691" %)**NB-IoT Spec:** 66 66 67 -* -B1 @H-FDD: 2100MHz68 -* -B3 @H-FDD: 1800MHz69 -* -B8 @H-FDD: 900MHz70 -* -B5 @H-FDD: 850MHz71 -* -B20 @H-FDD: 800MHz72 -* -B28 @H-FDD: 700MHz76 +* B1 @H-FDD: 2100MHz 77 +* B3 @H-FDD: 1800MHz 78 +* B8 @H-FDD: 900MHz 79 +* B5 @H-FDD: 850MHz 80 +* B20 @H-FDD: 800MHz 81 +* B28 @H-FDD: 700MHz 73 73 74 74 == 1.4 Probe Specification == 75 75 ... ... @@ -102,10 +102,8 @@ 102 102 103 103 **~ ** 104 104 105 - 106 106 = 2. Use NLMS01 to communicate with IoT Server = 107 107 108 - 109 109 == 2.1 How it works == 110 110 111 111 ... ... @@ -117,10 +117,8 @@ 117 117 [[image:image-20220907171221-5.png]] 118 118 119 119 120 - 121 121 == 2.2 Configure the NLMS01 == 122 122 123 - 124 124 === 2.2.1 Test Requirement === 125 125 126 126 ... ... @@ -136,7 +136,6 @@ 136 136 [[image:image-20220907171221-6.png]] 137 137 138 138 139 - 140 140 === 2.2.2 Insert SIM card === 141 141 142 142 ... ... @@ -148,7 +148,6 @@ 148 148 [[image:image-20220907171221-7.png]] 149 149 150 150 151 - 152 152 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 153 153 154 154 ... ... @@ -180,7 +180,6 @@ 180 180 (% style="color:red" %)**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]] 181 181 182 182 183 - 184 184 === 2.2.4 Use CoAP protocol to uplink data === 185 185 186 186 ... ... @@ -193,8 +193,6 @@ 193 193 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 194 194 * (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 195 195 196 - 197 - 198 198 For parameter description, please refer to AT command set 199 199 200 200 [[image:image-20220907171221-9.png]] ... ... @@ -205,7 +205,6 @@ 205 205 [[image:image-20220907171221-10.png]] 206 206 207 207 208 - 209 209 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 210 210 211 211 ... ... @@ -212,11 +212,8 @@ 212 212 This feature is supported since firmware version v1.0.1 213 213 214 214 * (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 215 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 216 -* (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 214 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 217 217 218 - 219 - 220 220 [[image:image-20220907171221-11.png]] 221 221 222 222 ... ... @@ -224,7 +224,6 @@ 224 224 225 225 226 226 227 - 228 228 === 2.2.6 Use MQTT protocol to uplink data === 229 229 230 230 ... ... @@ -238,8 +238,6 @@ 238 238 * (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 239 239 * (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 240 240 241 - 242 - 243 243 [[image:image-20220907171221-13.png]] 244 244 245 245 ... ... @@ -251,7 +251,6 @@ 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 253 253 254 - 255 255 === 2.2.7 Use TCP protocol to uplink data === 256 256 257 257 ... ... @@ -260,8 +260,6 @@ 260 260 * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 261 261 * (% style="color:#037691" %)**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 267 ... ... @@ -278,12 +278,9 @@ 278 278 279 279 * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 280 280 281 - 282 - 283 283 (% style="color:red" %)**NOTE: By default, the device will send an uplink message every 2 hour. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 284 284 285 285 286 - 287 287 == 2.3 Uplink Payload == 288 288 289 289 ... ... @@ -291,12 +291,10 @@ 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 281 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:517px" %) 282 +|(% style="background-color:#4f81bd; color:white; width:50px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:20px" %)**2**|(% style="background-color:#4f81bd; color:white; width:20px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**1**|(% style="background-color:#4f81bd; color:white; width:30px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**2**|(% style="background-color:#4f81bd; color:white; width:50px" %)**4**|(% style="background-color:#4f81bd; color:white; width:50px" %)**2**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:37px" %)**4** 283 +|(% 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 ..... 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 302 ... ... @@ -305,36 +305,43 @@ 305 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:293 +**0x (% style="color:red" %)__f868411056754138__ (% style="color:blue" %)__0064 __ (% style="color:green" %)__0c78__ (% style="color:#00b0f0" %)__17__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__00__ (% style="color:#a14d07" %)__0225 __ (% style="color:#0020b0" %) __010b__ (% style="color:#420042" %)__6315537b__ (% style="color:#663300" %)//__010b0226631550fb__ __010e022663154d77 01110225631549f1 011502246315466b 01190223631542e5 011d022163153f62 011e022163153bde 011e022163153859__//(%%)** 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 316 -* Leaf moisture: 0x0225= 549 = 54.9% 317 -* Leaf Temperature:0x010B =267=26.7 °C 318 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 319 -* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 320 -* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 295 +where: 321 321 297 +* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 322 322 299 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 323 323 301 +* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 324 324 303 +* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 325 325 326 - ==2.4Payload ExplanationandSensorInterface==305 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 327 327 307 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 328 328 309 +* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 310 + 311 +* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 312 + 313 +* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 314 + 315 +* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 316 + 317 +* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 318 + 319 +== 2.4 Payload Explanation and Sensor Interface == 320 + 329 329 === 2.4.1 Device ID === 330 330 331 331 332 332 By default, the Device ID equal to the last 15 bits of IMEI. 333 333 334 -User can use **AT+DEUI** to set Device ID 326 +User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID 335 335 336 336 337 -**Example :**329 +(% style="color:blue" %)**Example**: 338 338 339 339 AT+DEUI=868411056754138 340 340 ... ... @@ -341,7 +341,6 @@ 341 341 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 342 342 343 343 344 - 345 345 === 2.4.2 Version Info === 346 346 347 347 ... ... @@ -350,7 +350,6 @@ 350 350 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 351 351 352 352 353 - 354 354 === 2.4.3 Battery Info === 355 355 356 356 ... ... @@ -361,14 +361,14 @@ 361 361 Ex2: 0x0B49 = 2889mV 362 362 363 363 364 - 365 365 === 2.4.4 Signal Strength === 366 366 367 367 368 368 NB-IoT Network signal Strength. 369 369 370 -**Ex1: 0x1d = 29** 371 371 360 +(% style="color:blue" %)**Ex1: 0x1d = 29** 361 + 372 372 **0** -113dBm or less 373 373 374 374 **1** -111dBm ... ... @@ -380,31 +380,28 @@ 380 380 **99** Not known or not detectable 381 381 382 382 383 - 384 384 === 2.4.5 Leaf moisture === 385 385 386 386 387 -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**.376 +Get the moisture of the (% style="color:#037691" %)**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. 388 388 389 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 378 +For example, if the data you get from the register is (% style="color:#037691" %)**__0x05 0xDC__**(%%), the moisture content in the (% style="color:#037691" %)**Leaf**(%%) is 390 390 391 -**0229(H) = 549(D) /100 = 54.9.** 380 +(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 392 392 393 393 394 - 395 395 === 2.4.6 Leaf Temperature === 396 396 397 397 398 -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 **is386 +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 (% style="color:#037691" %)**__0x09 0xEC__**(%%), the temperature content in the (% style="color:#037691" %)**Leaf **(%%)is 399 399 400 -**Example**: 388 +(% style="color:blue" %)**Example**: 401 401 402 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 390 +If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 403 403 404 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 392 +If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 405 405 406 406 407 - 408 408 === 2.4.7 Timestamp === 409 409 410 410 ... ... @@ -416,11 +416,11 @@ 416 416 === 2.4.8 Digital Interrupt === 417 417 418 418 419 -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. 406 +Digital Interrupt refers to pin (% style="color:#037691" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server. 420 420 421 421 The command is: 422 422 423 -**AT+INTMOD=3 ** ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 410 +(% style="color:blue" %)**AT+INTMOD=3 ** (%%) ~/~/ (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.** 424 424 425 425 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 426 426 ... ... @@ -431,7 +431,6 @@ 431 431 0x(01): Interrupt Uplink Packet. 432 432 433 433 434 - 435 435 === 2.4.9 +5V Output === 436 436 437 437 ... ... @@ -439,24 +439,29 @@ 439 439 440 440 The 5V output time can be controlled by AT Command. 441 441 442 -**AT+5VT=1000** 428 +(% style="color:blue" %)**AT+5VT=1000** 443 443 444 444 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 445 445 446 446 447 - 448 448 == 2.5 Downlink Payload == 449 449 450 450 451 451 By default, NLMS01 prints the downlink payload to console port. 452 452 453 -[[image:image-20220907171221-18.png]] 438 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 439 +|=(% style="width: 183px; background-color:#4F81BD;color:white" %)**Downlink Control Type**|=(% style="width: 55px; background-color:#4F81BD;color:white" %)FPort|=(% style="width: 93px; background-color:#4F81BD;color:white" %)**Type Code**|=(% style="width: 179px; background-color:#4F81BD;color:white" %)**Downlink payload size(bytes)** 440 +|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 441 +|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 442 +|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 454 454 444 + 455 455 456 -**Examples:** 446 +(% style="color:blue" %)**Examples:** 457 457 458 -* **Set TDC** 459 459 449 +* (% style="color:#037691" %)**Set TDC** 450 + 460 460 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 461 461 462 462 Payload: 01 00 00 1E TDC=30S ... ... @@ -463,16 +463,19 @@ 463 463 464 464 Payload: 01 00 00 3C TDC=60S 465 465 466 -* **Reset** 467 467 458 + 459 +* (% style="color:#037691" %)**Reset** 460 + 468 468 If payload = 0x04FF, it will reset the NLMS01 469 469 470 -* **INTMOD** 471 471 472 -Downlink Payload: 06000003, Set AT+INTMOD=3 473 473 465 +* (% style="color:#037691" %)**INTMOD** 474 474 467 +Downlink Payload: 06000003, Set AT+INTMOD=3 475 475 469 + 476 476 == 2.6 LED Indicator == 477 477 478 478 ... ... @@ -483,9 +483,6 @@ 483 483 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 484 484 * For each uplink probe, LED will be on for 500ms. 485 485 486 - 487 - 488 - 489 489 == 2.7 Installation == 490 490 491 491 ... ... @@ -495,13 +495,12 @@ 495 495 [[image:image-20220907171221-19.png]] 496 496 497 497 498 - 499 499 == 2.8 Moisture and Temperature alarm function == 500 500 501 501 502 -**➢ AT Command:** 492 +(% style="color:blue" %)**➢ AT Command:** 503 503 504 -**AT+ HUMALARM =min,max** 494 +(% style="color:#037691" %)**AT+ HUMALARM =min,max** 505 505 506 506 ² When min=0, and max≠0, Alarm higher than max 507 507 ... ... @@ -510,7 +510,7 @@ 510 510 ² When min≠0 and max≠0, Alarm higher than max or lower than min 511 511 512 512 513 -**Example:** 503 +(% style="color:blue" %)**Example:** 514 514 515 515 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 516 516 ... ... @@ -523,100 +523,51 @@ 523 523 ² When min≠0 and max≠0, Alarm higher than max or lower than min 524 524 525 525 526 -**Example:** 516 +(% style="color:blue" %)**Example:** 527 527 528 528 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 529 529 530 530 531 - 532 532 == 2.9 Set the number of data to be uploaded and the recording time == 533 533 534 534 535 -**➢ AT Command:** 524 +(% style="color:blue" %)**➢ AT Command:** 536 536 537 -**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) 526 +* (% style="color:#037691" %)**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) 527 +* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 538 538 539 - **AT+NOUD=8**~/~/The deviceuploads8 setsofrecorded databy default.Upto32setsofrecorddatacan be uploaded.529 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 540 540 531 +[[image:image-20221009001002-1.png||height="706" width="982"]] 541 541 542 542 543 543 == 2.10 Read or Clear cached data == 544 544 545 545 546 -**➢ AT Command:** 537 +(% style="color:blue" %)**➢ AT Command:** 547 547 548 -**AT+CDP** ~/~/ Read cached data 539 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 540 +* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 549 549 550 -**AT+CDP=0 ** ~/~/ Clear cached data 551 - 552 - 553 553 [[image:image-20220907171221-20.png]] 554 554 555 555 556 - 557 557 == 2.11 Firmware Change Log == 558 558 559 559 560 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/ 1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]548 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]] 561 561 562 -Upgrade Instruction: [[Upgrade Firmware>> path:#H5.1200BHowtoUpgradeFirmware]]550 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 563 563 564 564 553 +== 2.12 Battery & Power Consumption == 565 565 566 -== 2.12 Battery Analysis == 567 567 556 +NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 568 568 569 - === 2.12.1 BatteryType===558 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 570 570 571 571 572 -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. 573 - 574 -The battery is designed to last for several years depends on the actually use environment and update interval. 575 - 576 -The battery related documents as below: 577 - 578 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 579 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 580 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 581 - 582 -[[image:image-20220907171221-21.png]] 583 - 584 - 585 - 586 -=== 2.12.2 Power consumption Analyze === 587 - 588 - 589 -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. 590 - 591 -Instruction to use as below: 592 - 593 -**Step 1: **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 594 - 595 -**Step 2: ** Open it and choose 596 - 597 -* Product Model 598 -* Uplink Interval 599 -* Working Mode 600 - 601 -And the Life expectation in difference case will be shown on the right. 602 - 603 -[[image:image-20220907171221-22.jpeg]] 604 - 605 - 606 -=== 2.12.3 Battery Note === 607 - 608 - 609 -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. 610 - 611 - 612 - 613 -=== 2.12.4 Replace the battery === 614 - 615 - 616 -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). 617 - 618 - 619 - 620 620 = 3. Access NB-IoT Module = 621 621 622 622 ... ... @@ -628,101 +628,92 @@ 628 628 [[image:image-20220907171221-23.png]] 629 629 630 630 631 - 632 632 = 4. Using the AT Commands = 633 633 634 - 635 635 == 4.1 Access AT Commands == 636 636 637 637 638 638 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]] 639 639 640 -AT+<CMD>? 579 +AT+<CMD>? : Help on <CMD> 641 641 642 -AT+<CMD> :Run <CMD>581 +AT+<CMD> : Run <CMD> 643 643 644 -AT+<CMD>=<value> 583 +AT+<CMD>=<value>: Set the value 645 645 646 -AT+<CMD>=? :Get the value585 +AT+<CMD>=? : Get the value 647 647 648 648 649 -**General Commands** 588 +(% style="color:#037691" %)**General Commands** 650 650 651 -AT :Attention590 +AT : Attention 652 652 653 -AT? :Short Help592 +AT? : Short Help 654 654 655 -ATZ 594 +ATZ : MCU Reset 656 656 657 -AT+TDC 596 +AT+TDC : Application Data Transmission Interval 658 658 659 -AT+CFG 598 +AT+CFG : Print all configurations 660 660 661 -AT+CFGMOD 600 +AT+CFGMOD : Working mode selection 662 662 663 -AT+INTMOD 602 +AT+INTMOD : Set the trigger interrupt mode 664 664 665 -AT+5VT 604 +AT+5VT : Set extend the time of 5V power 666 666 667 -AT+PRO 606 +AT+PRO : Choose agreement 668 668 669 -AT+RXDL :Extend the sending and receiving time608 +AT+RXDL: Extend the sending and receiving time 670 670 671 -AT+SERVADDR 610 +AT+SERVADDR : Server Address 672 672 673 -AT+APN :Get or set the APN612 +AT+APN : Get or set the APN 674 674 675 -AT+FBAND :Get or Set whether to automatically modify the frequency band614 +AT+FBAND : Get or Set whether to automatically modify the frequency band 676 676 677 -AT+DNSCFG 616 +AT+DNSCFG : Get or Set DNS Server 678 678 679 679 AT+GETSENSORVALUE : Returns the current sensor measurement 680 680 681 -AT+TR 620 +AT+TR : Get or Set record time" 682 682 683 -AT+NOUD 622 +AT+NOUD : Get or Set the number of data to be uploaded 684 684 685 -AT+CDP 624 +AT+CDP : Read or Clear cached data 686 686 687 -AT+TEMPALARM 626 +AT+TEMPALARM : Get or Set alarm of temp 688 688 689 -AT+HUMALARM PH628 +AT+HUMALARM : Get or Set alarm of humidity 690 690 691 691 692 -**COAP Management** 631 +(% style="color:#037691" %)**COAP Management** 693 693 694 -AT+URI 633 +AT+URI : Resource parameters 695 695 696 696 697 -** UDPManagement**636 +(% style="color:#037691" %)**MQTT Management** 698 698 699 -AT+C FMUploadconfirmationmode(onlyvalid for UDP)638 +AT+CLIENT : Get or Set MQTT client 700 700 640 +AT+UNAME : Get or Set MQTT Username 701 701 702 - **MQTTManagement**642 +AT+PWD : Get or Set MQTT password 703 703 704 -AT+ CLIENTclient644 +AT+PUBTOPIC : Get or Set MQTT publish topic 705 705 706 -AT+U NAME:Get or Set MQTTUsername646 +AT+SUBTOPIC : Get or Set MQTT subscription topic 707 707 708 -AT+PWD : Get or Set MQTT password 709 709 710 - AT+PUBTOPIC: GetSetMQTT publish topic649 +(% style="color:#037691" %)**Information** 711 711 712 -AT+ SUBTOPIC: GetSetMQTTsubscription topic651 +AT+FDR : Factory Data Reset 713 713 653 +AT+PWORD : Serial Access Password 714 714 715 -**Information** 716 716 717 -AT+FDR : Factory Data Reset 718 - 719 -AT+PWORD : Serial Access Password 720 - 721 - 722 - 723 723 = 5. FAQ = 724 724 725 - 726 726 == 5.1 How to Upgrade Firmware == 727 727 728 728 ... ... @@ -730,13 +730,12 @@ 730 730 731 731 Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] 732 732 733 -**Notice, NLMS01** **and LLMS01** **share the same mother board. They use the same connection and method to update.** 734 734 666 +(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 735 735 736 736 737 737 = 6. Trouble Shooting = 738 738 739 - 740 740 == 6.1 Connection problem when uploading firmware == 741 741 742 742 ... ... @@ -743,14 +743,30 @@ 743 743 **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]] 744 744 745 745 746 - 747 747 == 6.2 AT Command input doesn't work == 748 748 749 749 750 -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. 680 +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 (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 751 751 752 752 683 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 753 753 685 + 686 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 687 + 688 + 689 +== 6.4 Possible reasons why the device is unresponsive: == 690 + 691 + 692 +1. Check whether the battery voltage is lower than 2.8V 693 +2. Check whether the jumper of the device is correctly connected 694 + 695 +[[image:image-20240330175629-2.png]] 696 +3. Check whether the switch here of the device is at the ISP(The switch can operate normally only when it is in RUN) 697 + 698 + 699 +[[image:image-20240330175554-1.png]] 700 + 754 754 = 7. Order Info = 755 755 756 756 ... ... @@ -757,15 +757,14 @@ 757 757 Part Number**:** NLMS01 758 758 759 759 760 - 761 761 = 8. Packing Info = 762 762 763 763 764 -**Package Includes** :710 +(% style="color:#037691" %)**Package Includes:** 765 765 766 766 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 767 767 768 -**Dimension and weight**: 714 +(% style="color:#037691" %)**Dimension and weight**: 769 769 770 770 * Device Size: cm 771 771 * Device Weight: g ... ... @@ -772,9 +772,6 @@ 772 772 * Package Size / pcs : cm 773 773 * Weight / pcs : g 774 774 775 - 776 - 777 - 778 778 = 9. Support = 779 779 780 780
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content
- image-20240330175554-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +445.4 KB - Content
- image-20240330175629-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Bei - Size
-
... ... @@ -1,0 +1,1 @@ 1 +445.4 KB - Content