Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,15 +3,8 @@ 1 - 2 - 3 3 (% style="text-align:center" %) 4 4 [[image:image-20220907171221-1.jpeg]] 5 5 6 6 7 7 8 - 9 - 10 - 11 - 12 - 13 13 {{toc/}} 14 14 15 15 ... ... @@ -16,24 +16,20 @@ 16 16 17 17 = 1. Introduction = 18 18 12 + 19 19 == 1.1 What is NLMS01 Leaf Moisture Sensor == 20 20 21 21 22 -((( 23 23 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. 24 24 25 25 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. 26 26 27 27 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. 28 28 29 -NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 30 30 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 - 37 37 [[image:image-20220907171221-2.png]] 38 38 39 39 ... ... @@ -40,6 +40,7 @@ 40 40 [[image:image-20220907171221-3.png]] 41 41 42 42 32 + 43 43 == 1.2 Features == 44 44 45 45 ... ... @@ -60,6 +60,7 @@ 60 60 ((( 61 61 62 62 53 + 63 63 64 64 ))) 65 65 ... ... @@ -73,14 +73,13 @@ 73 73 74 74 (% style="color:#037691" %)**NB-IoT Spec:** 75 75 76 -* 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 67 +* - B1 @H-FDD: 2100MHz 68 +* - B3 @H-FDD: 1800MHz 69 +* - B8 @H-FDD: 900MHz 70 +* - B5 @H-FDD: 850MHz 71 +* - B20 @H-FDD: 800MHz 72 +* - B28 @H-FDD: 700MHz 82 82 83 - 84 84 == 1.4 Probe Specification == 85 85 86 86 ... ... @@ -100,13 +100,11 @@ 100 100 * IP67 Protection 101 101 * Length: 3.5 meters 102 102 103 - 104 104 == 1.5 Applications == 105 105 106 106 107 107 * Smart Agriculture 108 108 109 - 110 110 == 1.6 Pin mapping and power on == 111 111 112 112 ... ... @@ -114,8 +114,10 @@ 114 114 115 115 **~ ** 116 116 105 + 117 117 = 2. Use NLMS01 to communicate with IoT Server = 118 118 108 + 119 119 == 2.1 How it works == 120 120 121 121 ... ... @@ -127,8 +127,10 @@ 127 127 [[image:image-20220907171221-5.png]] 128 128 129 129 120 + 130 130 == 2.2 Configure the NLMS01 == 131 131 123 + 132 132 === 2.2.1 Test Requirement === 133 133 134 134 ... ... @@ -144,6 +144,7 @@ 144 144 [[image:image-20220907171221-6.png]] 145 145 146 146 139 + 147 147 === 2.2.2 Insert SIM card === 148 148 149 149 ... ... @@ -155,6 +155,7 @@ 155 155 [[image:image-20220907171221-7.png]] 156 156 157 157 151 + 158 158 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 159 159 160 160 ... ... @@ -186,6 +186,7 @@ 186 186 (% 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]] 187 187 188 188 183 + 189 189 === 2.2.4 Use CoAP protocol to uplink data === 190 190 191 191 ... ... @@ -198,6 +198,8 @@ 198 198 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%) ~/~/ to set CoAP server address and port 199 199 * (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 200 200 196 + 197 + 201 201 For parameter description, please refer to AT command set 202 202 203 203 [[image:image-20220907171221-9.png]] ... ... @@ -208,6 +208,7 @@ 208 208 [[image:image-20220907171221-10.png]] 209 209 210 210 208 + 211 211 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 212 212 213 213 ... ... @@ -214,9 +214,11 @@ 214 214 This feature is supported since firmware version v1.0.1 215 215 216 216 * (% style="color:#037691" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 217 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 215 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 218 218 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 219 219 218 + 219 + 220 220 [[image:image-20220907171221-11.png]] 221 221 222 222 ... ... @@ -224,6 +224,7 @@ 224 224 225 225 226 226 227 + 227 227 === 2.2.6 Use MQTT protocol to uplink data === 228 228 229 229 ... ... @@ -237,6 +237,8 @@ 237 237 * (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 238 238 * (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 239 239 241 + 242 + 240 240 [[image:image-20220907171221-13.png]] 241 241 242 242 ... ... @@ -248,6 +248,7 @@ 248 248 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. 249 249 250 250 254 + 251 251 === 2.2.7 Use TCP protocol to uplink data === 252 252 253 253 ... ... @@ -256,6 +256,8 @@ 256 256 * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 257 257 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 258 258 263 + 264 + 259 259 [[image:image-20220907171221-15.png]] 260 260 261 261 ... ... @@ -272,9 +272,12 @@ 272 272 273 273 * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 274 274 281 + 282 + 275 275 (% 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).** 276 276 277 277 286 + 278 278 == 2.3 Uplink Payload == 279 279 280 280 ... ... @@ -282,10 +282,12 @@ 282 282 283 283 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. 284 284 285 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:517px" %) 286 -|(% 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** 287 -|(% 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 ..... 288 288 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 + 289 289 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 290 290 291 291 ... ... @@ -294,44 +294,36 @@ 294 294 295 295 The payload is ASCII string, representative same HEX: 296 296 297 - **0x__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__//(%%)**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: 298 298 299 -where: 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,....... 300 300 301 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 302 302 303 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 304 304 305 -* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 306 306 307 -* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 308 308 309 -* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 310 - 311 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 312 - 313 -* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 314 - 315 -* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 316 - 317 -* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 318 - 319 -* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 320 - 321 -* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 322 - 323 - 324 324 == 2.4 Payload Explanation and Sensor Interface == 325 325 328 + 326 326 === 2.4.1 Device ID === 327 327 328 328 329 329 By default, the Device ID equal to the last 15 bits of IMEI. 330 330 331 -User can use (% style="color:#037691" %)**AT+DEUI**(%%)to set Device ID334 +User can use **AT+DEUI** to set Device ID 332 332 333 333 334 - (% style="color:blue" %)**Example**:337 +**Example:** 335 335 336 336 AT+DEUI=868411056754138 337 337 ... ... @@ -338,6 +338,7 @@ 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 340 344 + 341 341 === 2.4.2 Version Info === 342 342 343 343 ... ... @@ -346,6 +346,7 @@ 346 346 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 347 347 348 348 353 + 349 349 === 2.4.3 Battery Info === 350 350 351 351 ... ... @@ -356,14 +356,14 @@ 356 356 Ex2: 0x0B49 = 2889mV 357 357 358 358 364 + 359 359 === 2.4.4 Signal Strength === 360 360 361 361 362 362 NB-IoT Network signal Strength. 363 363 370 +**Ex1: 0x1d = 29** 364 364 365 -(% style="color:blue" %)**Ex1: 0x1d = 29** 366 - 367 367 **0** -113dBm or less 368 368 369 369 **1** -111dBm ... ... @@ -375,28 +375,31 @@ 375 375 **99** Not known or not detectable 376 376 377 377 383 + 378 378 === 2.4.5 Leaf moisture === 379 379 380 380 381 -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.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**. 382 382 383 -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**(%%)is389 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is 384 384 385 - (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**391 +**0229(H) = 549(D) /100 = 54.9.** 386 386 387 387 394 + 388 388 === 2.4.6 Leaf Temperature === 389 389 390 390 391 -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 **(%%)is398 +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 392 392 393 - (% style="color:blue" %)**Example**:400 +**Example**: 394 394 395 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C402 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 396 396 397 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C404 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 398 398 399 399 407 + 400 400 === 2.4.7 Timestamp === 401 401 402 402 ... ... @@ -408,11 +408,11 @@ 408 408 === 2.4.8 Digital Interrupt === 409 409 410 410 411 -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.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. 412 412 413 413 The command is: 414 414 415 - (% style="color:blue" %)**AT+INTMOD=3 **(%%)~/~/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]])**.** 416 416 417 417 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. 418 418 ... ... @@ -423,6 +423,7 @@ 423 423 0x(01): Interrupt Uplink Packet. 424 424 425 425 434 + 426 426 === 2.4.9 +5V Output === 427 427 428 428 ... ... @@ -430,29 +430,24 @@ 430 430 431 431 The 5V output time can be controlled by AT Command. 432 432 433 - (% style="color:blue" %)**AT+5VT=1000**442 +**AT+5VT=1000** 434 434 435 435 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 436 436 437 437 447 + 438 438 == 2.5 Downlink Payload == 439 439 440 440 441 441 By default, NLMS01 prints the downlink payload to console port. 442 442 443 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 444 -|=(% 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)** 445 -|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 446 -|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 447 -|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 453 +[[image:image-20220907171221-18.png]] 448 448 449 - 450 450 451 - (% style="color:blue" %)**Examples:**456 +**Examples:** 452 452 458 +* **Set TDC** 453 453 454 -* (% style="color:#037691" %)**Set TDC** 455 - 456 456 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 457 457 458 458 Payload: 01 00 00 1E TDC=30S ... ... @@ -459,19 +459,16 @@ 459 459 460 460 Payload: 01 00 00 3C TDC=60S 461 461 466 +* **Reset** 462 462 463 - 464 -* (% style="color:#037691" %)**Reset** 465 - 466 466 If payload = 0x04FF, it will reset the NLMS01 467 467 470 +* **INTMOD** 468 468 469 - 470 -* (% style="color:#037691" %)**INTMOD** 471 - 472 472 Downlink Payload: 06000003, Set AT+INTMOD=3 473 473 474 474 475 + 475 475 == 2.6 LED Indicator == 476 476 477 477 ... ... @@ -483,6 +483,8 @@ 483 483 * For each uplink probe, LED will be on for 500ms. 484 484 485 485 487 + 488 + 486 486 == 2.7 Installation == 487 487 488 488 ... ... @@ -492,12 +492,13 @@ 492 492 [[image:image-20220907171221-19.png]] 493 493 494 494 498 + 495 495 == 2.8 Moisture and Temperature alarm function == 496 496 497 497 498 - (% style="color:blue" %)**➢ AT Command:**502 +**➢ AT Command:** 499 499 500 - (% style="color:#037691" %)**AT+ HUMALARM =min,max**504 +**AT+ HUMALARM =min,max** 501 501 502 502 ² When min=0, and max≠0, Alarm higher than max 503 503 ... ... @@ -506,7 +506,7 @@ 506 506 ² When min≠0 and max≠0, Alarm higher than max or lower than min 507 507 508 508 509 - (% style="color:blue" %)**Example:**513 +**Example:** 510 510 511 511 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 512 512 ... ... @@ -519,51 +519,100 @@ 519 519 ² When min≠0 and max≠0, Alarm higher than max or lower than min 520 520 521 521 522 - (% style="color:blue" %)**Example:**526 +**Example:** 523 523 524 524 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 525 525 526 526 531 + 527 527 == 2.9 Set the number of data to be uploaded and the recording time == 528 528 529 529 530 - (% style="color:blue" %)**➢ AT Command:**535 +**➢ AT Command:** 531 531 532 -* (% 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) 533 -* (% 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. 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) 534 534 535 - The di agram belowexplainsthe relationshipbetweenTR, NOUD,andTDCmore clearly**:**539 +**AT+NOUD=8** ~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 536 536 537 -[[image:image-20221009001002-1.png||height="706" width="982"]] 538 538 539 539 540 540 == 2.10 Read or Clear cached data == 541 541 542 542 543 - (% style="color:blue" %)**➢ AT Command:**546 +**➢ AT Command:** 544 544 545 -* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 546 -* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 548 +**AT+CDP** ~/~/ Read cached data 547 547 550 +**AT+CDP=0 ** ~/~/ Clear cached data 551 + 552 + 548 548 [[image:image-20220907171221-20.png]] 549 549 550 550 556 + 551 551 == 2.11 Firmware Change Log == 552 552 553 553 554 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/ qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]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]] 555 555 556 -Upgrade Instruction: [[Upgrade Firmware>> ||anchor="H5.1200BHowtoUpgradeFirmware"]]562 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 557 557 558 558 559 -== 2.12 Battery & Power Consumption == 560 560 566 +== 2.12 Battery Analysis == 561 561 562 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 563 563 564 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].569 +=== 2.12.1 Battery Type === 565 565 566 566 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 + 567 567 = 3. Access NB-IoT Module = 568 568 569 569 ... ... @@ -575,97 +575,101 @@ 575 575 [[image:image-20220907171221-23.png]] 576 576 577 577 631 + 578 578 = 4. Using the AT Commands = 579 579 634 + 580 580 == 4.1 Access AT Commands == 581 581 582 582 583 583 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]] 584 584 585 -AT+<CMD>? : 640 +AT+<CMD>? : Help on <CMD> 586 586 587 -AT+<CMD> :Run <CMD>642 +AT+<CMD> : Run <CMD> 588 588 589 -AT+<CMD>=<value>: 644 +AT+<CMD>=<value> : Set the value 590 590 591 -AT+<CMD>=? :Get the value646 +AT+<CMD>=? : Get the value 592 592 593 593 594 - (% style="color:#037691" %)**General Commands**649 +**General Commands** 595 595 596 -AT :Attention651 +AT : Attention 597 597 598 -AT? :Short Help653 +AT? : Short Help 599 599 600 -ATZ :MCU Reset655 +ATZ : MCU Reset 601 601 602 -AT+TDC : 657 +AT+TDC : Application Data Transmission Interval 603 603 604 -AT+CFG : 659 +AT+CFG : Print all configurations 605 605 606 -AT+CFGMOD : 661 +AT+CFGMOD : Working mode selection 607 607 608 -AT+INTMOD : 663 +AT+INTMOD : Set the trigger interrupt mode 609 609 610 -AT+5VT :Set extend the time of 5V power665 +AT+5VT : Set extend the time of 5V power 611 611 612 -AT+PRO :Choose agreement667 +AT+PRO : Choose agreement 613 613 614 -AT+RXDL :Extend the sending and receiving time669 +AT+RXDL : Extend the sending and receiving time 615 615 616 -AT+SERVADDR :Server Address671 +AT+SERVADDR : Server Address 617 617 618 -AT+APN :Get or set the APN673 +AT+APN : Get or set the APN 619 619 620 -AT+FBAND :Get or Set whether to automatically modify the frequency band675 +AT+FBAND : Get or Set whether to automatically modify the frequency band 621 621 622 -AT+DNSCFG : Get or Set DNS Server 677 +AT+DNSCFG : Get or Set DNS Server 623 623 624 624 AT+GETSENSORVALUE : Returns the current sensor measurement 625 625 626 -AT+TR : 681 +AT+TR : Get or Set record time" 627 627 628 -AT+NOUD : 683 +AT+NOUD : Get or Set the number of data to be uploaded 629 629 630 -AT+CDP : 685 +AT+CDP : Read or Clear cached data 631 631 632 -AT+TEMPALARM : 687 +AT+TEMPALARM : Get or Set alarm of temp 633 633 634 -AT+HUMALARM : humidity689 +AT+HUMALARM : Get or Set alarm of PH 635 635 636 636 637 - (% style="color:#037691" %)**COAP Management**692 +**COAP Management** 638 638 639 -AT+URI : 694 +AT+URI : Resource parameters 640 640 641 641 642 - (% style="color:#037691" %)**UDP Management**697 +**UDP Management** 643 643 644 -AT+CFM : 699 +AT+CFM : Upload confirmation mode (only valid for UDP) 645 645 646 646 647 - (% style="color:#037691" %)**MQTT Management**702 +**MQTT Management** 648 648 649 -AT+CLIENT : 704 +AT+CLIENT : Get or Set MQTT client 650 650 651 -AT+UNAME : Get or Set MQTT Username 706 +AT+UNAME : Get or Set MQTT Username 652 652 653 -AT+PWD 708 +AT+PWD : Get or Set MQTT password 654 654 655 -AT+PUBTOPIC :Get or Set MQTT publish topic710 +AT+PUBTOPIC : Get or Set MQTT publish topic 656 656 657 -AT+SUBTOPIC :Get or Set MQTT subscription topic712 +AT+SUBTOPIC : Get or Set MQTT subscription topic 658 658 659 659 660 - (% style="color:#037691" %)**Information**715 +**Information** 661 661 662 -AT+FDR :Factory Data Reset717 +AT+FDR : Factory Data Reset 663 663 664 -AT+PWORD :Serial Access Password719 +AT+PWORD : Serial Access Password 665 665 666 666 722 + 667 667 = 5. FAQ = 668 668 725 + 669 669 == 5.1 How to Upgrade Firmware == 670 670 671 671 ... ... @@ -673,12 +673,13 @@ 673 673 674 674 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]] 675 675 733 +**Notice, NLMS01** **and LLMS01** **share the same mother board. They use the same connection and method to update.** 676 676 677 -(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 678 678 679 679 680 680 = 6. Trouble Shooting = 681 681 739 + 682 682 == 6.1 Connection problem when uploading firmware == 683 683 684 684 ... ... @@ -685,18 +685,14 @@ 685 685 **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]] 686 686 687 687 746 + 688 688 == 6.2 AT Command input doesn't work == 689 689 690 690 691 -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.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. 692 692 693 693 694 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 695 695 696 - 697 -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]]//**. 698 - 699 - 700 700 = 7. Order Info = 701 701 702 702 ... ... @@ -703,14 +703,15 @@ 703 703 Part Number**:** NLMS01 704 704 705 705 760 + 706 706 = 8. Packing Info = 707 707 708 708 709 - (% style="color:#037691" %)**Package Includes:**764 +**Package Includes**: 710 710 711 711 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 712 712 713 - (% style="color:#037691" %)**Dimension and weight**:768 +**Dimension and weight**: 714 714 715 715 * Device Size: cm 716 716 * Device Weight: g ... ... @@ -718,6 +718,8 @@ 718 718 * Weight / pcs : g 719 719 720 720 776 + 777 + 721 721 = 9. Support = 722 722 723 723
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content