Changes for page NLMS01-NB-IoT Leaf Moisture Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:54
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 3 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - 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,16 +64,13 @@ 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 - 75 - 76 - 77 77 == 1.4 Probe Specification == 78 78 79 79 ... ... @@ -93,17 +93,11 @@ 93 93 * IP67 Protection 94 94 * Length: 3.5 meters 95 95 96 - 97 - 98 - 99 99 == 1.5 Applications == 100 100 101 101 102 102 * Smart Agriculture 103 103 104 - 105 - 106 - 107 107 == 1.6 Pin mapping and power on == 108 108 109 109 ... ... @@ -111,10 +111,8 @@ 111 111 112 112 **~ ** 113 113 114 - 115 115 = 2. Use NLMS01 to communicate with IoT Server = 116 116 117 - 118 118 == 2.1 How it works == 119 119 120 120 ... ... @@ -126,10 +126,8 @@ 126 126 [[image:image-20220907171221-5.png]] 127 127 128 128 129 - 130 130 == 2.2 Configure the NLMS01 == 131 131 132 - 133 133 === 2.2.1 Test Requirement === 134 134 135 135 ... ... @@ -145,7 +145,6 @@ 145 145 [[image:image-20220907171221-6.png]] 146 146 147 147 148 - 149 149 === 2.2.2 Insert SIM card === 150 150 151 151 ... ... @@ -157,7 +157,6 @@ 157 157 [[image:image-20220907171221-7.png]] 158 158 159 159 160 - 161 161 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 162 162 163 163 ... ... @@ -189,7 +189,6 @@ 189 189 (% 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]] 190 190 191 191 192 - 193 193 === 2.2.4 Use CoAP protocol to uplink data === 194 194 195 195 ... ... @@ -212,7 +212,6 @@ 212 212 [[image:image-20220907171221-10.png]] 213 213 214 214 215 - 216 216 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 217 217 218 218 ... ... @@ -222,8 +222,6 @@ 222 222 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 223 223 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 224 224 225 - 226 - 227 227 [[image:image-20220907171221-11.png]] 228 228 229 229 ... ... @@ -231,7 +231,6 @@ 231 231 232 232 233 233 234 - 235 235 === 2.2.6 Use MQTT protocol to uplink data === 236 236 237 237 ... ... @@ -256,7 +256,6 @@ 256 256 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. 257 257 258 258 259 - 260 260 === 2.2.7 Use TCP protocol to uplink data === 261 261 262 262 ... ... @@ -265,8 +265,6 @@ 265 265 * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 266 266 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 267 267 268 - 269 - 270 270 [[image:image-20220907171221-15.png]] 271 271 272 272 ... ... @@ -283,12 +283,9 @@ 283 283 284 284 * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 285 285 286 - 287 - 288 288 (% 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).** 289 289 290 290 291 - 292 292 == 2.3 Uplink Payload == 293 293 294 294 ... ... @@ -296,11 +296,10 @@ 296 296 297 297 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. 298 298 282 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:517px" %) 283 +|(% 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** 284 +|(% 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 ..... 299 299 300 -(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 301 -|(% 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 302 -|(% 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 ..... 303 - 304 304 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. 305 305 306 306 ... ... @@ -309,27 +309,34 @@ 309 309 310 310 The payload is ASCII string, representative same HEX: 311 311 312 -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:294 +**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__//(%%)** 313 313 314 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 315 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0 316 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 317 -* (% style="color:red" %)Singal: 0x17 = 23 318 -* (% style="color:blue" %)Mod: 0x01 = 1 319 -* (% style="color:green" %)Interrupt: 0x00= 0 320 -* Leaf moisture: 0x0225= 549 = 54.9% 321 -* Leaf Temperature:0x010B =267=26.7 °C 322 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 323 -* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 324 -* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 296 +where: 325 325 298 +* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 326 326 300 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 327 327 302 +* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 328 328 304 +* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 329 329 330 - ==2.4Payload ExplanationandSensorInterface==306 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 331 331 308 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 332 332 310 +* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9% 311 + 312 +* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C 313 + 314 +* (% style="color:#037691" %)**Time stamp :** (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 315 + 316 +* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp : **(%%)010b0226631550fb 317 + 318 +* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 319 + 320 +== 2.4 Payload Explanation and Sensor Interface == 321 + 333 333 === 2.4.1 Device ID === 334 334 335 335 ... ... @@ -345,7 +345,6 @@ 345 345 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 346 346 347 347 348 - 349 349 === 2.4.2 Version Info === 350 350 351 351 ... ... @@ -354,7 +354,6 @@ 354 354 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 355 355 356 356 357 - 358 358 === 2.4.3 Battery Info === 359 359 360 360 ... ... @@ -365,7 +365,6 @@ 365 365 Ex2: 0x0B49 = 2889mV 366 366 367 367 368 - 369 369 === 2.4.4 Signal Strength === 370 370 371 371 ... ... @@ -385,7 +385,6 @@ 385 385 **99** Not known or not detectable 386 386 387 387 388 - 389 389 === 2.4.5 Leaf moisture === 390 390 391 391 ... ... @@ -396,7 +396,6 @@ 396 396 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 397 397 398 398 399 - 400 400 === 2.4.6 Leaf Temperature === 401 401 402 402 ... ... @@ -409,7 +409,6 @@ 409 409 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 410 410 411 411 412 - 413 413 === 2.4.7 Timestamp === 414 414 415 415 ... ... @@ -418,7 +418,6 @@ 418 418 Convert Unix timestamp to time 2022-9-5 9:40:11. 419 419 420 420 421 - 422 422 === 2.4.8 Digital Interrupt === 423 423 424 424 ... ... @@ -437,7 +437,6 @@ 437 437 0x(01): Interrupt Uplink Packet. 438 438 439 439 440 - 441 441 === 2.4.9 +5V Output === 442 442 443 443 ... ... @@ -450,14 +450,18 @@ 450 450 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 451 451 452 452 453 - 454 454 == 2.5 Downlink Payload == 455 455 456 456 457 457 By default, NLMS01 prints the downlink payload to console port. 458 458 459 -[[image:image-20220907171221-18.png]] 439 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %) 440 +|=(% 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)** 441 +|(% style="width:183px" %)TDC (Transmit Time Interval)|(% style="width:55px" %)Any|(% style="width:93px" %)01|(% style="width:146px" %)4 442 +|(% style="width:183px" %)RESET|(% style="width:55px" %)Any|(% style="width:93px" %)04|(% style="width:146px" %)2 443 +|(% style="width:183px" %)INTMOD|(% style="width:55px" %)Any|(% style="width:93px" %)06|(% style="width:146px" %)4 460 460 445 + 461 461 462 462 (% style="color:blue" %)**Examples:** 463 463 ... ... @@ -483,7 +483,6 @@ 483 483 Downlink Payload: 06000003, Set AT+INTMOD=3 484 484 485 485 486 - 487 487 == 2.6 LED Indicator == 488 488 489 489 ... ... @@ -494,10 +494,6 @@ 494 494 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 495 495 * For each uplink probe, LED will be on for 500ms. 496 496 497 - 498 - 499 - 500 - 501 501 == 2.7 Installation == 502 502 503 503 ... ... @@ -507,7 +507,6 @@ 507 507 [[image:image-20220907171221-19.png]] 508 508 509 509 510 - 511 511 == 2.8 Moisture and Temperature alarm function == 512 512 513 513 ... ... @@ -540,7 +540,6 @@ 540 540 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 541 541 542 542 543 - 544 544 == 2.9 Set the number of data to be uploaded and the recording time == 545 545 546 546 ... ... @@ -549,10 +549,11 @@ 549 549 * (% 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) 550 550 * (% 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. 551 551 530 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 552 552 532 +[[image:image-20221009001002-1.png||height="706" width="982"]] 553 553 554 554 555 - 556 556 == 2.10 Read or Clear cached data == 557 557 558 558 ... ... @@ -561,12 +561,9 @@ 561 561 * (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 562 562 * (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 563 563 564 - 565 - 566 566 [[image:image-20220907171221-20.png]] 567 567 568 568 569 - 570 570 == 2.11 Firmware Change Log == 571 571 572 572 ... ... @@ -575,61 +575,14 @@ 575 575 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 576 576 577 577 554 +== 2.12 Battery & Power Consumption == 578 578 579 -== 2.12 Battery Analysis == 580 580 557 +NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 581 581 582 - === 2.12.1 BatteryType===559 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 583 583 584 584 585 -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. 586 - 587 -The battery is designed to last for several years depends on the actually use environment and update interval. 588 - 589 -The battery related documents as below: 590 - 591 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 592 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 593 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 594 - 595 -[[image:image-20220907171221-21.png]] 596 - 597 - 598 - 599 -=== 2.12.2 Power consumption Analyze === 600 - 601 - 602 -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. 603 - 604 -Instruction to use as below: 605 - 606 -(% style="color:blue" %)**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/]] 607 - 608 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 609 - 610 -* Product Model 611 -* Uplink Interval 612 -* Working Mode 613 - 614 -And the Life expectation in difference case will be shown on the right. 615 - 616 -[[image:image-20220907171221-22.jpeg]] 617 - 618 - 619 -=== 2.12.3 Battery Note === 620 - 621 - 622 -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. 623 - 624 - 625 - 626 -=== 2.12.4 Replace the battery === 627 - 628 - 629 -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). 630 - 631 - 632 - 633 633 = 3. Access NB-IoT Module = 634 634 635 635 ... ... @@ -641,101 +641,97 @@ 641 641 [[image:image-20220907171221-23.png]] 642 642 643 643 644 - 645 645 = 4. Using the AT Commands = 646 646 647 - 648 648 == 4.1 Access AT Commands == 649 649 650 650 651 651 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]] 652 652 653 -AT+<CMD>? 580 +AT+<CMD>? : Help on <CMD> 654 654 655 -AT+<CMD> :Run <CMD>582 +AT+<CMD> : Run <CMD> 656 656 657 -AT+<CMD>=<value> 584 +AT+<CMD>=<value>: Set the value 658 658 659 -AT+<CMD>=? :Get the value586 +AT+<CMD>=? : Get the value 660 660 661 661 662 662 (% style="color:#037691" %)**General Commands** 663 663 664 -AT :Attention591 +AT : Attention 665 665 666 -AT? :Short Help593 +AT? : Short Help 667 667 668 -ATZ 595 +ATZ : MCU Reset 669 669 670 -AT+TDC 597 +AT+TDC : Application Data Transmission Interval 671 671 672 -AT+CFG 599 +AT+CFG : Print all configurations 673 673 674 -AT+CFGMOD 601 +AT+CFGMOD : Working mode selection 675 675 676 -AT+INTMOD 603 +AT+INTMOD : Set the trigger interrupt mode 677 677 678 -AT+5VT 605 +AT+5VT : Set extend the time of 5V power 679 679 680 -AT+PRO 607 +AT+PRO : Choose agreement 681 681 682 -AT+RXDL :Extend the sending and receiving time609 +AT+RXDL: Extend the sending and receiving time 683 683 684 -AT+SERVADDR 611 +AT+SERVADDR : Server Address 685 685 686 -AT+APN :Get or set the APN613 +AT+APN : Get or set the APN 687 687 688 -AT+FBAND :Get or Set whether to automatically modify the frequency band615 +AT+FBAND : Get or Set whether to automatically modify the frequency band 689 689 690 -AT+DNSCFG 617 +AT+DNSCFG : Get or Set DNS Server 691 691 692 692 AT+GETSENSORVALUE : Returns the current sensor measurement 693 693 694 -AT+TR 621 +AT+TR : Get or Set record time" 695 695 696 -AT+NOUD 623 +AT+NOUD : Get or Set the number of data to be uploaded 697 697 698 -AT+CDP 625 +AT+CDP : Read or Clear cached data 699 699 700 -AT+TEMPALARM 627 +AT+TEMPALARM : Get or Set alarm of temp 701 701 702 -AT+HUMALARM PH629 +AT+HUMALARM : Get or Set alarm of humidity 703 703 704 704 705 705 (% style="color:#037691" %)**COAP Management** 706 706 707 -AT+URI 634 +AT+URI : Resource parameters 708 708 709 709 710 710 (% style="color:#037691" %)**UDP Management** 711 711 712 -AT+CFM 639 +AT+CFM : Upload confirmation mode (only valid for UDP) 713 713 714 714 715 715 (% style="color:#037691" %)**MQTT Management** 716 716 717 -AT+CLIENT 644 +AT+CLIENT : Get or Set MQTT client 718 718 719 -AT+UNAME 646 +AT+UNAME : Get or Set MQTT Username 720 720 721 -AT+PWD 648 +AT+PWD : Get or Set MQTT password 722 722 723 -AT+PUBTOPIC 650 +AT+PUBTOPIC : Get or Set MQTT publish topic 724 724 725 -AT+SUBTOPIC :Get or Set MQTT subscription topic652 +AT+SUBTOPIC : Get or Set MQTT subscription topic 726 726 727 727 728 728 (% style="color:#037691" %)**Information** 729 729 730 -AT+FDR :Factory Data Reset657 +AT+FDR : Factory Data Reset 731 731 732 -AT+PWORD 659 +AT+PWORD : Serial Access Password 733 733 734 734 735 - 736 736 = 5. FAQ = 737 737 738 - 739 739 == 5.1 How to Upgrade Firmware == 740 740 741 741 ... ... @@ -747,10 +747,8 @@ 747 747 (% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 748 748 749 749 750 - 751 751 = 6. Trouble Shooting = 752 752 753 - 754 754 == 6.1 Connection problem when uploading firmware == 755 755 756 756 ... ... @@ -757,7 +757,6 @@ 757 757 **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]] 758 758 759 759 760 - 761 761 == 6.2 AT Command input doesn't work == 762 762 763 763 ... ... @@ -764,7 +764,24 @@ 764 764 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. 765 765 766 766 689 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 767 767 691 + 692 +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]]//**. 693 + 694 + 695 +== 5.3 Possible reasons why the device is unresponsive: == 696 + 697 + 698 +1. Check whether the battery voltage is lower than 2.8V 699 +2. Check whether the jumper of the device is correctly connected 700 + 701 +[[image:image-20240330175629-2.png]] 702 +3. Check whether the switch here of the device is at the ISP(The switch can operate normally only when it is in RUN) 703 + 704 + 705 +[[image:image-20240330175554-1.png]] 706 + 768 768 = 7. Order Info = 769 769 770 770 ... ... @@ -771,7 +771,6 @@ 771 771 Part Number**:** NLMS01 772 772 773 773 774 - 775 775 = 8. Packing Info = 776 776 777 777 ... ... @@ -786,9 +786,6 @@ 786 786 * Package Size / pcs : cm 787 787 * Weight / pcs : g 788 788 789 - 790 - 791 - 792 792 = 9. Support = 793 793 794 794
- 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