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
-
... ... @@ -9,24 +9,20 @@ 9 9 10 10 = 1. Introduction = 11 11 12 + 12 12 == 1.1 What is NLMS01 Leaf Moisture Sensor == 13 13 14 14 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. 21 21 22 -NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP **(%%)for different application requirement. 23 23 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 - 30 30 [[image:image-20220907171221-2.png]] 31 31 32 32 ... ... @@ -33,6 +33,7 @@ 33 33 [[image:image-20220907171221-3.png]] 34 34 35 35 32 + 36 36 == 1.2 Features == 37 37 38 38 ... ... @@ -53,6 +53,7 @@ 53 53 ((( 54 54 55 55 53 + 56 56 57 57 ))) 58 58 ... ... @@ -66,14 +66,16 @@ 66 66 67 67 (% style="color:#037691" %)**NB-IoT Spec:** 68 68 69 -* 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 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 75 75 76 76 75 + 76 + 77 77 == 1.4 Probe Specification == 78 78 79 79 ... ... @@ -85,6 +85,8 @@ 85 85 * IP67 Protection 86 86 * Length: 3.5 meters 87 87 88 + 89 + 88 88 (% style="color:#037691" %)**Leaf Temperature:** 89 89 90 90 * Range -50℃~80℃ ... ... @@ -94,6 +94,8 @@ 94 94 * Length: 3.5 meters 95 95 96 96 99 + 100 + 97 97 == 1.5 Applications == 98 98 99 99 ... ... @@ -100,6 +100,8 @@ 100 100 * Smart Agriculture 101 101 102 102 107 + 108 + 103 103 == 1.6 Pin mapping and power on == 104 104 105 105 ... ... @@ -107,8 +107,10 @@ 107 107 108 108 **~ ** 109 109 116 + 110 110 = 2. Use NLMS01 to communicate with IoT Server = 111 111 119 + 112 112 == 2.1 How it works == 113 113 114 114 ... ... @@ -120,8 +120,10 @@ 120 120 [[image:image-20220907171221-5.png]] 121 121 122 122 131 + 123 123 == 2.2 Configure the NLMS01 == 124 124 134 + 125 125 === 2.2.1 Test Requirement === 126 126 127 127 ... ... @@ -137,6 +137,7 @@ 137 137 [[image:image-20220907171221-6.png]] 138 138 139 139 150 + 140 140 === 2.2.2 Insert SIM card === 141 141 142 142 ... ... @@ -148,6 +148,7 @@ 148 148 [[image:image-20220907171221-7.png]] 149 149 150 150 162 + 151 151 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 152 152 153 153 ... ... @@ -179,6 +179,7 @@ 179 179 (% 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]] 180 180 181 181 194 + 182 182 === 2.2.4 Use CoAP protocol to uplink data === 183 183 184 184 ... ... @@ -201,6 +201,7 @@ 201 201 [[image:image-20220907171221-10.png]] 202 202 203 203 217 + 204 204 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 205 205 206 206 ... ... @@ -210,6 +210,8 @@ 210 210 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 211 211 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 212 212 227 + 228 + 213 213 [[image:image-20220907171221-11.png]] 214 214 215 215 ... ... @@ -217,6 +217,7 @@ 217 217 218 218 219 219 236 + 220 220 === 2.2.6 Use MQTT protocol to uplink data === 221 221 222 222 ... ... @@ -230,6 +230,8 @@ 230 230 * (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 231 231 * (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 232 232 250 + 251 + 233 233 [[image:image-20220907171221-13.png]] 234 234 235 235 ... ... @@ -241,6 +241,7 @@ 241 241 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. 242 242 243 243 263 + 244 244 === 2.2.7 Use TCP protocol to uplink data === 245 245 246 246 ... ... @@ -249,6 +249,8 @@ 249 249 * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 250 250 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 251 251 272 + 273 + 252 252 [[image:image-20220907171221-15.png]] 253 253 254 254 ... ... @@ -265,9 +265,12 @@ 265 265 266 266 * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 267 267 290 + 291 + 268 268 (% 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).** 269 269 270 270 295 + 271 271 == 2.3 Uplink Payload == 272 272 273 273 ... ... @@ -276,8 +276,8 @@ 276 276 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. 277 277 278 278 279 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:520px" %)280 -|(% style="width: 50px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:20px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:50px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**4**304 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 305 +|(% 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 281 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 ..... 282 282 283 283 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data. ... ... @@ -288,34 +288,26 @@ 288 288 289 289 The payload is ASCII string, representative same HEX: 290 290 291 - **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__//(%%)**316 +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: 292 292 293 -where: 318 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138 319 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0 320 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V 321 +* (% style="color:red" %)Singal: 0x17 = 23 322 +* (% style="color:blue" %)Mod: 0x01 = 1 323 +* (% style="color:green" %)Interrupt: 0x00= 0 324 +* Leaf moisture: 0x0225= 549 = 54.9% 325 +* Leaf Temperature:0x010B =267=26.7 °C 326 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]]) 327 +* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb 328 +* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,....... 294 294 295 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 296 296 297 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 298 298 299 -* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 300 300 301 -* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 302 - 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 317 == 2.4 Payload Explanation and Sensor Interface == 318 318 335 + 319 319 === 2.4.1 Device ID === 320 320 321 321 ... ... @@ -331,6 +331,7 @@ 331 331 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 332 332 333 333 351 + 334 334 === 2.4.2 Version Info === 335 335 336 336 ... ... @@ -339,6 +339,7 @@ 339 339 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 340 340 341 341 360 + 342 342 === 2.4.3 Battery Info === 343 343 344 344 ... ... @@ -349,6 +349,7 @@ 349 349 Ex2: 0x0B49 = 2889mV 350 350 351 351 371 + 352 352 === 2.4.4 Signal Strength === 353 353 354 354 ... ... @@ -368,6 +368,7 @@ 368 368 **99** Not known or not detectable 369 369 370 370 391 + 371 371 === 2.4.5 Leaf moisture === 372 372 373 373 ... ... @@ -378,6 +378,7 @@ 378 378 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 379 379 380 380 402 + 381 381 === 2.4.6 Leaf Temperature === 382 382 383 383 ... ... @@ -390,6 +390,7 @@ 390 390 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 391 391 392 392 415 + 393 393 === 2.4.7 Timestamp === 394 394 395 395 ... ... @@ -398,6 +398,7 @@ 398 398 Convert Unix timestamp to time 2022-9-5 9:40:11. 399 399 400 400 424 + 401 401 === 2.4.8 Digital Interrupt === 402 402 403 403 ... ... @@ -416,6 +416,7 @@ 416 416 0x(01): Interrupt Uplink Packet. 417 417 418 418 443 + 419 419 === 2.4.9 +5V Output === 420 420 421 421 ... ... @@ -428,6 +428,7 @@ 428 428 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 429 429 430 430 456 + 431 431 == 2.5 Downlink Payload == 432 432 433 433 ... ... @@ -460,6 +460,7 @@ 460 460 Downlink Payload: 06000003, Set AT+INTMOD=3 461 461 462 462 489 + 463 463 == 2.6 LED Indicator == 464 464 465 465 ... ... @@ -470,6 +470,9 @@ 470 470 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 471 471 * For each uplink probe, LED will be on for 500ms. 472 472 500 + 501 + 502 + 473 473 == 2.7 Installation == 474 474 475 475 ... ... @@ -479,6 +479,7 @@ 479 479 [[image:image-20220907171221-19.png]] 480 480 481 481 512 + 482 482 == 2.8 Moisture and Temperature alarm function == 483 483 484 484 ... ... @@ -511,6 +511,7 @@ 511 511 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 512 512 513 513 545 + 514 514 == 2.9 Set the number of data to be uploaded and the recording time == 515 515 516 516 ... ... @@ -519,9 +519,7 @@ 519 519 * (% 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) 520 520 * (% 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. 521 521 522 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 523 523 524 -[[image:image-20221009001002-1.png||height="706" width="982"]] 525 525 526 526 527 527 == 2.10 Read or Clear cached data == ... ... @@ -532,25 +532,75 @@ 532 532 * (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 533 533 * (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 534 534 565 + 566 + 535 535 [[image:image-20220907171221-20.png]] 536 536 537 537 570 + 538 538 == 2.11 Firmware Change Log == 539 539 540 540 541 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/ qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]574 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]] 542 542 543 -Upgrade Instruction: [[Upgrade Firmware>> ||anchor="H5.1200BHowtoUpgradeFirmware"]]576 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]] 544 544 545 545 546 -== 2.12 Battery & Power Consumption == 547 547 580 +== 2.12 Battery Analysis == 548 548 549 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 550 550 551 - [[**BatteryInfo & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]].583 +=== 2.12.1 Battery Type === 552 552 553 553 586 +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. 587 + 588 +The battery is designed to last for several years depends on the actually use environment and update interval. 589 + 590 +The battery related documents as below: 591 + 592 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 593 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 594 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 595 + 596 +[[image:image-20220907171221-21.png]] 597 + 598 + 599 + 600 +=== 2.12.2 Power consumption Analyze === 601 + 602 + 603 +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. 604 + 605 +Instruction to use as below: 606 + 607 +(% 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/]] 608 + 609 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 610 + 611 +* Product Model 612 +* Uplink Interval 613 +* Working Mode 614 + 615 +And the Life expectation in difference case will be shown on the right. 616 + 617 +[[image:image-20220907171221-22.jpeg]] 618 + 619 + 620 +=== 2.12.3 Battery Note === 621 + 622 + 623 +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. 624 + 625 + 626 + 627 +=== 2.12.4 Replace the battery === 628 + 629 + 630 +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). 631 + 632 + 633 + 554 554 = 3. Access NB-IoT Module = 555 555 556 556 ... ... @@ -562,97 +562,101 @@ 562 562 [[image:image-20220907171221-23.png]] 563 563 564 564 645 + 565 565 = 4. Using the AT Commands = 566 566 648 + 567 567 == 4.1 Access AT Commands == 568 568 569 569 570 570 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]] 571 571 572 -AT+<CMD>? : 654 +AT+<CMD>? : Help on <CMD> 573 573 574 -AT+<CMD> :Run <CMD>656 +AT+<CMD> : Run <CMD> 575 575 576 -AT+<CMD>=<value>: 658 +AT+<CMD>=<value> : Set the value 577 577 578 -AT+<CMD>=? :Get the value660 +AT+<CMD>=? : Get the value 579 579 580 580 581 581 (% style="color:#037691" %)**General Commands** 582 582 583 -AT :Attention665 +AT : Attention 584 584 585 -AT? :Short Help667 +AT? : Short Help 586 586 587 -ATZ :MCU Reset669 +ATZ : MCU Reset 588 588 589 -AT+TDC : 671 +AT+TDC : Application Data Transmission Interval 590 590 591 -AT+CFG : 673 +AT+CFG : Print all configurations 592 592 593 -AT+CFGMOD : 675 +AT+CFGMOD : Working mode selection 594 594 595 -AT+INTMOD : 677 +AT+INTMOD : Set the trigger interrupt mode 596 596 597 -AT+5VT :Set extend the time of 5V power679 +AT+5VT : Set extend the time of 5V power 598 598 599 -AT+PRO :Choose agreement681 +AT+PRO : Choose agreement 600 600 601 -AT+RXDL :Extend the sending and receiving time683 +AT+RXDL : Extend the sending and receiving time 602 602 603 -AT+SERVADDR :Server Address685 +AT+SERVADDR : Server Address 604 604 605 -AT+APN :Get or set the APN687 +AT+APN : Get or set the APN 606 606 607 -AT+FBAND :Get or Set whether to automatically modify the frequency band689 +AT+FBAND : Get or Set whether to automatically modify the frequency band 608 608 609 -AT+DNSCFG : Get or Set DNS Server 691 +AT+DNSCFG : Get or Set DNS Server 610 610 611 611 AT+GETSENSORVALUE : Returns the current sensor measurement 612 612 613 -AT+TR : 695 +AT+TR : Get or Set record time" 614 614 615 -AT+NOUD : 697 +AT+NOUD : Get or Set the number of data to be uploaded 616 616 617 -AT+CDP : 699 +AT+CDP : Read or Clear cached data 618 618 619 -AT+TEMPALARM : 701 +AT+TEMPALARM : Get or Set alarm of temp 620 620 621 -AT+HUMALARM : humidity703 +AT+HUMALARM : Get or Set alarm of PH 622 622 623 623 624 624 (% style="color:#037691" %)**COAP Management** 625 625 626 -AT+URI : 708 +AT+URI : Resource parameters 627 627 628 628 629 629 (% style="color:#037691" %)**UDP Management** 630 630 631 -AT+CFM : 713 +AT+CFM : Upload confirmation mode (only valid for UDP) 632 632 633 633 634 634 (% style="color:#037691" %)**MQTT Management** 635 635 636 -AT+CLIENT : 718 +AT+CLIENT : Get or Set MQTT client 637 637 638 -AT+UNAME : Get or Set MQTT Username 720 +AT+UNAME : Get or Set MQTT Username 639 639 640 -AT+PWD 722 +AT+PWD : Get or Set MQTT password 641 641 642 -AT+PUBTOPIC :Get or Set MQTT publish topic724 +AT+PUBTOPIC : Get or Set MQTT publish topic 643 643 644 -AT+SUBTOPIC :Get or Set MQTT subscription topic726 +AT+SUBTOPIC : Get or Set MQTT subscription topic 645 645 646 646 647 647 (% style="color:#037691" %)**Information** 648 648 649 -AT+FDR :Factory Data Reset731 +AT+FDR : Factory Data Reset 650 650 651 -AT+PWORD :Serial Access Password733 +AT+PWORD : Serial Access Password 652 652 653 653 736 + 654 654 = 5. FAQ = 655 655 739 + 656 656 == 5.1 How to Upgrade Firmware == 657 657 658 658 ... ... @@ -664,8 +664,10 @@ 664 664 (% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 665 665 666 666 751 + 667 667 = 6. Trouble Shooting = 668 668 754 + 669 669 == 6.1 Connection problem when uploading firmware == 670 670 671 671 ... ... @@ -672,6 +672,7 @@ 672 672 **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]] 673 673 674 674 761 + 675 675 == 6.2 AT Command input doesn't work == 676 676 677 677 ... ... @@ -678,12 +678,7 @@ 678 678 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. 679 679 680 680 681 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 682 682 683 - 684 -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]]//**. 685 - 686 - 687 687 = 7. Order Info = 688 688 689 689 ... ... @@ -690,6 +690,7 @@ 690 690 Part Number**:** NLMS01 691 691 692 692 775 + 693 693 = 8. Packing Info = 694 694 695 695 ... ... @@ -704,6 +704,8 @@ 704 704 * Package Size / pcs : cm 705 705 * Weight / pcs : g 706 706 790 + 791 + 707 707 = 9. Support = 708 708 709 709
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content