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, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -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 15 +((( 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 22 +NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 25 25 24 +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). 25 + 26 +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. 27 +))) 28 + 29 + 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,13 +64,14 @@ 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: 700MHz69 +* B1 @H-FDD: 2100MHz 70 +* B3 @H-FDD: 1800MHz 71 +* B8 @H-FDD: 900MHz 72 +* B5 @H-FDD: 850MHz 73 +* B20 @H-FDD: 800MHz 74 +* B28 @H-FDD: 700MHz 73 73 76 + 74 74 == 1.4 Probe Specification == 75 75 76 76 ... ... @@ -90,11 +90,13 @@ 90 90 * IP67 Protection 91 91 * Length: 3.5 meters 92 92 96 + 93 93 == 1.5 Applications == 94 94 95 95 96 96 * Smart Agriculture 97 97 102 + 98 98 == 1.6 Pin mapping and power on == 99 99 100 100 ... ... @@ -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,9 @@ 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 210 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 216 216 * (% style="color:#037691" %)**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 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 ... ... @@ -292,11 +292,10 @@ 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 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" %)4297 -|(% 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 ..... 279 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 280 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:60px" %)**1**|(% style="width:20px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**4**|(% style="width:50px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**4** 281 +|=(% 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 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,46 +305,61 @@ 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:291 +**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,....... 293 +where: 321 321 295 +* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 322 322 297 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 323 323 299 +* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 324 324 301 +* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 325 325 303 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 304 + 305 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 306 + 307 +* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 308 + 309 +* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 310 + 311 +* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 312 + 313 +* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 314 + 315 +* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 316 + 317 + 326 326 == 2.4 Payload Explanation and Sensor Interface == 327 327 328 328 === 2.4.1 Device ID === 329 329 322 + 330 330 By default, the Device ID equal to the last 15 bits of IMEI. 331 331 332 -User can use **AT+DEUI** to set Device ID 325 +User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID 333 333 334 -**Example:** 335 335 328 +(% style="color:blue" %)**Example**: 329 + 336 336 AT+DEUI=868411056754138 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 334 + 340 340 === 2.4.2 Version Info === 341 341 337 + 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 342 + 346 346 === 2.4.3 Battery Info === 347 347 345 + 348 348 Check the battery voltage for NLMS01. 349 349 350 350 Ex1: 0x0B45 = 2885mV ... ... @@ -351,12 +351,15 @@ 351 351 352 352 Ex2: 0x0B49 = 2889mV 353 353 352 + 354 354 === 2.4.4 Signal Strength === 355 355 355 + 356 356 NB-IoT Network signal Strength. 357 357 358 -**Ex1: 0x1d = 29** 359 359 359 +(% style="color:blue" %)**Ex1: 0x1d = 29** 360 + 360 360 **0** -113dBm or less 361 361 362 362 **1** -111dBm ... ... @@ -367,37 +367,45 @@ 367 367 368 368 **99** Not known or not detectable 369 369 371 + 370 370 === 2.4.5 Leaf moisture === 371 371 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 374 - Forexample,if thedatayou getfromthe register is**__0x050xDC__**, themoisture content in the**Leaf** is375 +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. 375 375 376 - **0229(H)= 549(D)/100=54.9.**377 +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 377 377 379 +(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 380 + 381 + 378 378 === 2.4.6 Leaf Temperature === 379 379 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 382 - **Example**:385 +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 383 383 384 - Ifpayload is 0105H:((0x0105 & 0x8000)>>15 === 0),temp= 0105(H)/10 = 26.1 °C387 +(% style="color:blue" %)**Example**: 385 385 386 -If payload is FF7EH: ((FF7E& 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 =-12.9°C389 +If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C 387 387 391 +If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 392 + 393 + 388 388 === 2.4.7 Timestamp === 389 389 396 + 390 390 Time stamp : 0x6315537b =1662342011 391 391 392 392 Convert Unix timestamp to time 2022-9-5 9:40:11. 393 393 401 + 394 394 === 2.4.8 Digital Interrupt === 395 395 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 405 +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. 406 + 398 398 The command is: 399 399 400 -**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]])**.** 409 +(% 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]])**.** 401 401 402 402 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. 403 403 ... ... @@ -407,13 +407,15 @@ 407 407 408 408 0x(01): Interrupt Uplink Packet. 409 409 419 + 410 410 === 2.4.9 +5V Output === 411 411 422 + 412 412 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 413 413 414 414 The 5V output time can be controlled by AT Command. 415 415 416 -**AT+5VT=1000** 427 +(% style="color:blue" %)**AT+5VT=1000** 417 417 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,14 +420,17 @@ 420 420 421 421 == 2.5 Downlink Payload == 422 422 434 + 423 423 By default, NLMS01 prints the downlink payload to console port. 424 424 425 425 [[image:image-20220907171221-18.png]] 426 426 427 -**Examples:** 428 428 429 - ***Set TDC**440 +(% style="color:blue" %)**Examples:** 430 430 442 + 443 +* (% style="color:#037691" %)**Set TDC** 444 + 431 431 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 432 432 433 433 Payload: 01 00 00 1E TDC=30S ... ... @@ -434,16 +434,22 @@ 434 434 435 435 Payload: 01 00 00 3C TDC=60S 436 436 437 -* **Reset** 438 438 452 + 453 +* (% style="color:#037691" %)**Reset** 454 + 439 439 If payload = 0x04FF, it will reset the NLMS01 440 440 441 -* **INTMOD** 442 442 458 + 459 +* (% style="color:#037691" %)**INTMOD** 460 + 443 443 Downlink Payload: 06000003, Set AT+INTMOD=3 444 444 463 + 445 445 == 2.6 LED Indicator == 446 446 466 + 447 447 The NLMS01 has an internal LED which is to show the status of different state. 448 448 449 449 * When power on, NLMS01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) ... ... @@ -451,18 +451,23 @@ 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 == 455 455 475 +== 2.7 Installation == 476 + 477 + 456 456 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor. 457 457 480 + 458 458 [[image:image-20220907171221-19.png]] 459 459 460 -== 2.8 Moisture and Temperature alarm function == 461 461 462 - ➢ATCommand:484 +== 2.8 Moisture and Temperature alarm function == 463 463 464 -AT+ HUMALARM =min,max 465 465 487 +(% style="color:blue" %)**➢ AT Command:** 488 + 489 +(% style="color:#037691" %)**AT+ HUMALARM =min,max** 490 + 466 466 ² When min=0, and max≠0, Alarm higher than max 467 467 468 468 ² When min≠0, and max=0, Alarm lower than min ... ... @@ -469,8 +469,9 @@ 469 469 470 470 ² When min≠0 and max≠0, Alarm higher than max or lower than min 471 471 472 -Example: 473 473 498 +(% style="color:blue" %)**Example:** 499 + 474 474 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50. 475 475 476 476 AT+ TEMPALARM=min,max ... ... @@ -481,201 +481,199 @@ 481 481 482 482 ² When min≠0 and max≠0, Alarm higher than max or lower than min 483 483 484 -Example: 485 485 511 +(% style="color:blue" %)**Example:** 512 + 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 == 516 +== 2.9 Set the number of data to be uploaded and the recording time == 490 490 491 -➢ AT Command: 492 492 493 - AT+TR=900~/~/The unit isseconds, andthe default is to record dataonce every 900 seconds.(Theminimum canbe set to 180 seconds)519 +(% style="color:blue" %)**➢ AT Command:** 494 494 495 -AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 521 +* (% 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) 522 +* (% 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. 496 496 497 - ==2.10 ReadorClearcacheddata==524 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 498 498 499 - ➢ AT Command:526 +[[image:image-20221009001002-1.png||height="706" width="982"]] 500 500 501 -AT+CDP ~/~/ Read cached data 502 502 503 - [[image:image-20220907171221-20.png]]529 +== 2.10 Read or Clear cached data == 504 504 505 505 506 - AT+CDP=0~/~/ Clearcacheddata532 +(% style="color:blue" %)**➢ AT Command:** 507 507 534 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 535 +* (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 508 508 509 - == 2.11 FirmwareChangeLog==537 +[[image:image-20220907171221-20.png]] 510 510 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 - UpgradeInstruction:[[UpgradeFirmware>>path:#H5.1200BHowtoUpgradeFirmware]]540 +== 2.11 Firmware Change Log == 514 514 515 -== 2.12 Battery Analysis == 516 516 517 - ===2.12.1Battery Type===543 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]] 518 518 519 - The NLMS01 batteryisacombinationof an 8500mAh Li/SOCI2 Batteryanda SuperCapacitor. The battery is none-rechargeable battery typewith a low dischargerate(<2% per year). This type of battery is commonly used in IoT devices such aswatermeter.545 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 520 520 521 -The battery is designed to last for several years depends on the actually use environment and update interval. 522 522 523 - Thebatteryrelateddocuments as below:548 +== 2.12 Battery & Power Consumption == 524 524 525 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 526 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 527 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 528 528 529 - [[image:image-20220907171221-21.png]]551 +NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 530 530 531 - ===2.12.2Powerconsumption Analyze===553 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 532 532 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 535 - Instructionto useas below:556 += 3. Access NB-IoT Module = 536 536 537 -**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/]] 538 538 539 - **Step2:**Openit andchoose559 +Users can directly access the AT command set of the NB-IoT module. 540 540 541 -* Product Model 542 -* Uplink Interval 543 -* Working Mode 561 +The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 544 544 545 -And the Life expectation in difference case will be shown on the right. 546 546 547 -[[image:image-20220907171221-2 2.jpeg]] 564 +[[image:image-20220907171221-23.png]] 548 548 549 -=== 2.12.3 Battery Note === 550 550 551 - TheLi-SICObattery isdesigned for small current / longperiod application. It is not good to use ahigh current,short period transmit method.Therecommended minimum period for use of this battery is 5 minutes. If you use a shorter periodtime to transmitLoRa, then the battery life may be decreased.567 += 4. Using the AT Commands = 552 552 553 -== =2.12.4Replacethebattery===569 +== 4.1 Access AT Commands == 554 554 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.AccessNB-IoT Module=572 +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]] 558 558 559 - Users can directly access theATcommandsetoftheNB-IoTmodule.574 +AT+<CMD>? : Help on <CMD> 560 560 561 - TheATommandsetcanrefertheBC35-G NB-IoT ModuleATCommand: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]576 +AT+<CMD> : Run <CMD> 562 562 563 - [[image:image-20220907171221-23.png]]578 +AT+<CMD>=<value>: Set the value 564 564 565 -= 4.UsingtheAT Commands =580 +AT+<CMD>=? : Get the value 566 566 567 -== 4.1 Access AT Commands == 568 568 569 - Seethislink for detail: [[https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]583 +(% style="color:#037691" %)**General Commands** 570 570 571 -AT +<CMD>?: Helpon<CMD>585 +AT : Attention 572 572 573 -AT +<CMD>: Run <CMD>587 +AT? : Short Help 574 574 575 -AT +<CMD>=<value>: Setthe value589 +ATZ : MCU Reset 576 576 577 -AT+ <CMD>=?Get thevalue591 +AT+TDC : Application Data Transmission Interval 578 578 579 - **GeneralCommands**593 +AT+CFG : Print all configurations 580 580 581 -AT : Attention595 +AT+CFGMOD : Working mode selection 582 582 583 -AT ?:ShortHelp597 +AT+INTMOD : Set the trigger interrupt mode 584 584 585 -AT Z: MCU Reset599 +AT+5VT : Set extend the time of 5V power 586 586 587 -AT+ TDCApplicationData TransmissionInterval601 +AT+PRO : Choose agreement 588 588 589 -AT+ CFG: Printallconfigurations603 +AT+RXDL: Extend the sending and receiving time 590 590 591 -AT+ CFGMODWorkingmodeelection605 +AT+SERVADDR : Server Address 592 592 593 -AT+ INTMOD:Setthetriggerinterruptmode607 +AT+APN : Get or set the APN 594 594 595 -AT+ 5VT:Set extendthetimeof5V power609 +AT+FBAND : Get or Set whether to automatically modify the frequency band 596 596 597 -AT+ PRO: Chooseagreement611 +AT+DNSCFG : Get or Set DNS Server 598 598 599 -AT+R XDLExtendthesendingandreceivingtime613 +AT+GETSENSORVALUE : Returns the current sensor measurement 600 600 601 -AT+ SERVADDR:ServerAddress615 +AT+TR : Get or Set record time" 602 602 603 -AT+ APN:Get orset theAPN617 +AT+NOUD : Get or Set the number of data to be uploaded 604 604 605 -AT+ FBAND:GetorSet whetherto automatically modify thefrequency band619 +AT+CDP : Read or Clear cached data 606 606 607 -AT+ DNSCFGDNSServer621 +AT+TEMPALARM : Get or Set alarm of temp 608 608 609 -AT+ GETSENSORVALUE:Returnsthecurrentsensoreasurement623 +AT+HUMALARM : Get or Set alarm of humidity 610 610 611 -AT+TR : Get or Set record time" 612 612 613 - AT+NOUD: GetSetthenumber of datato be uploaded626 +(% style="color:#037691" %)**COAP Management** 614 614 615 -AT+ CDP: ReadorClearcached data628 +AT+URI : Resource parameters 616 616 617 -AT+TEMPALARM : Get or Set alarm of temp 618 618 619 - AT+HUMALARM: GetSetalarmof PH631 +(% style="color:#037691" %)**UDP Management** 620 620 633 +AT+CFM : Upload confirmation mode (only valid for UDP) 621 621 622 -**COAP Management** 623 623 624 - AT+URI: Resourceparameters636 +(% style="color:#037691" %)**MQTT Management** 625 625 626 - **UDPManagement**638 +AT+CLIENT : Get or Set MQTT client 627 627 628 -AT+ CFMUploadconfirmationmode(onlyvalid forUDP)640 +AT+UNAME : Get or Set MQTT Username 629 629 630 - **MQTTManagement**642 +AT+PWD : Get or Set MQTT password 631 631 632 -AT+ CLIENTclient644 +AT+PUBTOPIC : Get or Set MQTT publish topic 633 633 634 -AT+U NAME:Get or Set MQTTUsername646 +AT+SUBTOPIC : Get or Set MQTT subscription topic 635 635 636 -AT+PWD : Get or Set MQTT password 637 637 638 - AT+PUBTOPIC: GetSetMQTT publish topic649 +(% style="color:#037691" %)**Information** 639 639 640 -AT+ SUBTOPIC: GetSetMQTTsubscription topic651 +AT+FDR : Factory Data Reset 641 641 642 - **Information**653 +AT+PWORD : Serial Access Password 643 643 644 -AT+FDR : Factory Data Reset 645 645 646 -AT+PWORD : Serial Access Password 647 - 648 648 = 5. FAQ = 649 649 650 650 == 5.1 How to Upgrade Firmware == 651 651 660 + 652 652 User can upgrade the firmware for 1) bug fix, 2) new feature release. 653 653 654 654 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]] 655 655 656 -**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.** 657 657 666 +(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 667 + 668 + 658 658 = 6. Trouble Shooting = 659 659 660 660 == 6.1 Connection problem when uploading firmware == 661 661 673 + 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 676 + 664 664 == 6.2 AT Command input doesn't work == 665 665 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 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. 681 + 682 + 683 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 684 + 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 + 668 668 = 7. Order Info = 669 669 691 + 670 670 Part Number**:** NLMS01 671 671 694 + 672 672 = 8. Packing Info = 673 673 674 -**Package Includes**: 675 675 698 +(% style="color:#037691" %)**Package Includes:** 699 + 676 676 * NLMS01 NB-IoT Leaf Moisture Sensor x 1 677 677 678 -**Dimension and weight**: 702 +(% style="color:#037691" %)**Dimension and weight**: 679 679 680 680 * Device Size: cm 681 681 * Device Weight: g ... ... @@ -682,8 +682,10 @@ 682 682 * Package Size / pcs : cm 683 683 * Weight / pcs : g 684 684 709 + 685 685 = 9. Support = 686 686 712 + 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
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content