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
-
... ... @@ -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,15 +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 76 == 1.4 Probe Specification == 77 77 78 78 ... ... @@ -84,7 +84,6 @@ 84 84 * IP67 Protection 85 85 * Length: 3.5 meters 86 86 87 - 88 88 (% style="color:#037691" %)**Leaf Temperature:** 89 89 90 90 * Range -50℃~80℃ ... ... @@ -93,15 +93,11 @@ 93 93 * IP67 Protection 94 94 * Length: 3.5 meters 95 95 96 - 97 - 98 98 == 1.5 Applications == 99 99 100 100 101 101 * Smart Agriculture 102 102 103 - 104 - 105 105 == 1.6 Pin mapping and power on == 106 106 107 107 ... ... @@ -109,10 +109,8 @@ 109 109 110 110 **~ ** 111 111 112 - 113 113 = 2. Use NLMS01 to communicate with IoT Server = 114 114 115 - 116 116 == 2.1 How it works == 117 117 118 118 ... ... @@ -124,10 +124,8 @@ 124 124 [[image:image-20220907171221-5.png]] 125 125 126 126 127 - 128 128 == 2.2 Configure the NLMS01 == 129 129 130 - 131 131 === 2.2.1 Test Requirement === 132 132 133 133 ... ... @@ -143,7 +143,6 @@ 143 143 [[image:image-20220907171221-6.png]] 144 144 145 145 146 - 147 147 === 2.2.2 Insert SIM card === 148 148 149 149 ... ... @@ -155,7 +155,6 @@ 155 155 [[image:image-20220907171221-7.png]] 156 156 157 157 158 - 159 159 === 2.2.3 Connect USB – TTL to NLMS01 to configure it === 160 160 161 161 ... ... @@ -187,7 +187,6 @@ 187 187 (% 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]] 188 188 189 189 190 - 191 191 === 2.2.4 Use CoAP protocol to uplink data === 192 192 193 193 ... ... @@ -210,7 +210,6 @@ 210 210 [[image:image-20220907171221-10.png]] 211 211 212 212 213 - 214 214 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 215 215 216 216 ... ... @@ -220,7 +220,6 @@ 220 220 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 221 221 * (% style="color:#037691" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 222 222 223 - 224 224 [[image:image-20220907171221-11.png]] 225 225 226 226 ... ... @@ -228,7 +228,6 @@ 228 228 229 229 230 230 231 - 232 232 === 2.2.6 Use MQTT protocol to uplink data === 233 233 234 234 ... ... @@ -242,7 +242,6 @@ 242 242 * (% style="color:#037691" %)**AT+PUBTOPIC=PUB ** (%%) ~/~/ Set the sending topic of MQTT 243 243 * (% style="color:#037691" %)**AT+SUBTOPIC=SUB ** (%%) ~/~/ Set the subscription topic of MQTT 244 244 245 - 246 246 [[image:image-20220907171221-13.png]] 247 247 248 248 ... ... @@ -254,7 +254,6 @@ 254 254 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. 255 255 256 256 257 - 258 258 === 2.2.7 Use TCP protocol to uplink data === 259 259 260 260 ... ... @@ -263,7 +263,6 @@ 263 263 * (% style="color:#037691" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 264 264 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port 265 265 266 - 267 267 [[image:image-20220907171221-15.png]] 268 268 269 269 ... ... @@ -280,11 +280,9 @@ 280 280 281 281 * (% style="color:#037691" %)**AT+TDC=7200 ** (%%) ~/~/ Set Update Interval to 7200s (2 hour) 282 282 283 - 284 284 (% 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).** 285 285 286 286 287 - 288 288 == 2.3 Uplink Payload == 289 289 290 290 ... ... @@ -292,11 +292,10 @@ 292 292 293 293 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. 294 294 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 ..... 295 295 296 -(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %) 297 -|(% 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 298 -|(% 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 - 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,25 +305,34 @@ 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: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__//(%%)** 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,....... 296 +where: 321 321 298 +* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138 322 322 300 +* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 323 323 324 - ==2.4Payload Explanation and SensorInterface==302 +* (% style="color:#037691" %)**BAT:** (%%)0x0c78 = 3192 mV = 3.192V 325 325 304 +* (% style="color:#037691" %)**Singal:**(%%) 0x17 = 23 326 326 306 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 307 + 308 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 309 + 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 + 327 327 === 2.4.1 Device ID === 328 328 329 329 ... ... @@ -339,7 +339,6 @@ 339 339 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 340 340 341 341 342 - 343 343 === 2.4.2 Version Info === 344 344 345 345 ... ... @@ -348,7 +348,6 @@ 348 348 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0. 349 349 350 350 351 - 352 352 === 2.4.3 Battery Info === 353 353 354 354 ... ... @@ -359,7 +359,6 @@ 359 359 Ex2: 0x0B49 = 2889mV 360 360 361 361 362 - 363 363 === 2.4.4 Signal Strength === 364 364 365 365 ... ... @@ -379,7 +379,6 @@ 379 379 **99** Not known or not detectable 380 380 381 381 382 - 383 383 === 2.4.5 Leaf moisture === 384 384 385 385 ... ... @@ -390,7 +390,6 @@ 390 390 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.** 391 391 392 392 393 - 394 394 === 2.4.6 Leaf Temperature === 395 395 396 396 ... ... @@ -403,7 +403,6 @@ 403 403 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C 404 404 405 405 406 - 407 407 === 2.4.7 Timestamp === 408 408 409 409 ... ... @@ -412,7 +412,6 @@ 412 412 Convert Unix timestamp to time 2022-9-5 9:40:11. 413 413 414 414 415 - 416 416 === 2.4.8 Digital Interrupt === 417 417 418 418 ... ... @@ -431,7 +431,6 @@ 431 431 0x(01): Interrupt Uplink Packet. 432 432 433 433 434 - 435 435 === 2.4.9 +5V Output === 436 436 437 437 ... ... @@ -444,14 +444,18 @@ 444 444 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** ** 445 445 446 446 447 - 448 448 == 2.5 Downlink Payload == 449 449 450 450 451 451 By default, NLMS01 prints the downlink payload to console port. 452 452 453 -[[image:image-20220907171221-18.png]] 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 454 454 445 + 455 455 456 456 (% style="color:blue" %)**Examples:** 457 457 ... ... @@ -477,7 +477,6 @@ 477 477 Downlink Payload: 06000003, Set AT+INTMOD=3 478 478 479 479 480 - 481 481 == 2.6 LED Indicator == 482 482 483 483 ... ... @@ -488,8 +488,6 @@ 488 488 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds. 489 489 * For each uplink probe, LED will be on for 500ms. 490 490 491 - 492 - 493 493 == 2.7 Installation == 494 494 495 495 ... ... @@ -499,7 +499,6 @@ 499 499 [[image:image-20220907171221-19.png]] 500 500 501 501 502 - 503 503 == 2.8 Moisture and Temperature alarm function == 504 504 505 505 ... ... @@ -532,7 +532,6 @@ 532 532 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20. 533 533 534 534 535 - 536 536 == 2.9 Set the number of data to be uploaded and the recording time == 537 537 538 538 ... ... @@ -541,8 +541,11 @@ 541 541 * (% 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) 542 542 * (% 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. 543 543 530 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 544 544 532 +[[image:image-20221009001002-1.png||height="706" width="982"]] 545 545 534 + 546 546 == 2.10 Read or Clear cached data == 547 547 548 548 ... ... @@ -551,11 +551,9 @@ 551 551 * (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 552 552 * (% style="color:#037691" %)**AT+CDP=0 ** (%%) ~/~/ Clear cached data 553 553 554 - 555 555 [[image:image-20220907171221-20.png]] 556 556 557 557 558 - 559 559 == 2.11 Firmware Change Log == 560 560 561 561 ... ... @@ -564,61 +564,14 @@ 564 564 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 565 565 566 566 554 +== 2.12 Battery & Power Consumption == 567 567 568 -== 2.12 Battery Analysis == 569 569 557 +NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 570 570 571 - === 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/]] . 572 572 573 573 574 -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. 575 - 576 -The battery is designed to last for several years depends on the actually use environment and update interval. 577 - 578 -The battery related documents as below: 579 - 580 -* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 581 -* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 582 -* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 583 - 584 -[[image:image-20220907171221-21.png]] 585 - 586 - 587 - 588 -=== 2.12.2 Power consumption Analyze === 589 - 590 - 591 -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. 592 - 593 -Instruction to use as below: 594 - 595 -(% 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/]] 596 - 597 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 598 - 599 -* Product Model 600 -* Uplink Interval 601 -* Working Mode 602 - 603 -And the Life expectation in difference case will be shown on the right. 604 - 605 -[[image:image-20220907171221-22.jpeg]] 606 - 607 - 608 -=== 2.12.3 Battery Note === 609 - 610 - 611 -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. 612 - 613 - 614 - 615 -=== 2.12.4 Replace the battery === 616 - 617 - 618 -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). 619 - 620 - 621 - 622 622 = 3. Access NB-IoT Module = 623 623 624 624 ... ... @@ -630,101 +630,97 @@ 630 630 [[image:image-20220907171221-23.png]] 631 631 632 632 633 - 634 634 = 4. Using the AT Commands = 635 635 636 - 637 637 == 4.1 Access AT Commands == 638 638 639 639 640 640 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]] 641 641 642 -AT+<CMD>? 580 +AT+<CMD>? : Help on <CMD> 643 643 644 -AT+<CMD> :Run <CMD>582 +AT+<CMD> : Run <CMD> 645 645 646 -AT+<CMD>=<value> 584 +AT+<CMD>=<value>: Set the value 647 647 648 -AT+<CMD>=? :Get the value586 +AT+<CMD>=? : Get the value 649 649 650 650 651 651 (% style="color:#037691" %)**General Commands** 652 652 653 -AT :Attention591 +AT : Attention 654 654 655 -AT? :Short Help593 +AT? : Short Help 656 656 657 -ATZ 595 +ATZ : MCU Reset 658 658 659 -AT+TDC 597 +AT+TDC : Application Data Transmission Interval 660 660 661 -AT+CFG 599 +AT+CFG : Print all configurations 662 662 663 -AT+CFGMOD 601 +AT+CFGMOD : Working mode selection 664 664 665 -AT+INTMOD 603 +AT+INTMOD : Set the trigger interrupt mode 666 666 667 -AT+5VT 605 +AT+5VT : Set extend the time of 5V power 668 668 669 -AT+PRO 607 +AT+PRO : Choose agreement 670 670 671 -AT+RXDL :Extend the sending and receiving time609 +AT+RXDL: Extend the sending and receiving time 672 672 673 -AT+SERVADDR 611 +AT+SERVADDR : Server Address 674 674 675 -AT+APN :Get or set the APN613 +AT+APN : Get or set the APN 676 676 677 -AT+FBAND :Get or Set whether to automatically modify the frequency band615 +AT+FBAND : Get or Set whether to automatically modify the frequency band 678 678 679 -AT+DNSCFG 617 +AT+DNSCFG : Get or Set DNS Server 680 680 681 681 AT+GETSENSORVALUE : Returns the current sensor measurement 682 682 683 -AT+TR 621 +AT+TR : Get or Set record time" 684 684 685 -AT+NOUD 623 +AT+NOUD : Get or Set the number of data to be uploaded 686 686 687 -AT+CDP 625 +AT+CDP : Read or Clear cached data 688 688 689 -AT+TEMPALARM 627 +AT+TEMPALARM : Get or Set alarm of temp 690 690 691 -AT+HUMALARM PH629 +AT+HUMALARM : Get or Set alarm of humidity 692 692 693 693 694 694 (% style="color:#037691" %)**COAP Management** 695 695 696 -AT+URI 634 +AT+URI : Resource parameters 697 697 698 698 699 699 (% style="color:#037691" %)**UDP Management** 700 700 701 -AT+CFM 639 +AT+CFM : Upload confirmation mode (only valid for UDP) 702 702 703 703 704 704 (% style="color:#037691" %)**MQTT Management** 705 705 706 -AT+CLIENT 644 +AT+CLIENT : Get or Set MQTT client 707 707 708 -AT+UNAME 646 +AT+UNAME : Get or Set MQTT Username 709 709 710 -AT+PWD 648 +AT+PWD : Get or Set MQTT password 711 711 712 -AT+PUBTOPIC 650 +AT+PUBTOPIC : Get or Set MQTT publish topic 713 713 714 -AT+SUBTOPIC :Get or Set MQTT subscription topic652 +AT+SUBTOPIC : Get or Set MQTT subscription topic 715 715 716 716 717 717 (% style="color:#037691" %)**Information** 718 718 719 -AT+FDR :Factory Data Reset657 +AT+FDR : Factory Data Reset 720 720 721 -AT+PWORD 659 +AT+PWORD : Serial Access Password 722 722 723 723 724 - 725 725 = 5. FAQ = 726 726 727 - 728 728 == 5.1 How to Upgrade Firmware == 729 729 730 730 ... ... @@ -736,10 +736,8 @@ 736 736 (% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.** 737 737 738 738 739 - 740 740 = 6. Trouble Shooting = 741 741 742 - 743 743 == 6.1 Connection problem when uploading firmware == 744 744 745 745 ... ... @@ -746,7 +746,6 @@ 746 746 **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]] 747 747 748 748 749 - 750 750 == 6.2 AT Command input doesn't work == 751 751 752 752 ... ... @@ -753,7 +753,12 @@ 753 753 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. 754 754 755 755 689 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 756 756 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 + 757 757 = 7. Order Info = 758 758 759 759 ... ... @@ -760,7 +760,6 @@ 760 760 Part Number**:** NLMS01 761 761 762 762 763 - 764 764 = 8. Packing Info = 765 765 766 766 ... ... @@ -775,7 +775,6 @@ 775 775 * Package Size / pcs : cm 776 776 * Weight / pcs : g 777 777 778 - 779 779 = 9. Support = 780 780 781 781
- image-20221009001002-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content