<
From version < 38.10 >
edited by Xiaoling
on 2022/10/25 16:28
To version < 33.3 >
edited by Xiaoling
on 2022/09/13 09:23
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -13,21 +13,16 @@
13 13  == 1.1 ​ What is NLMS01 Leaf Moisture Sensor ==
14 14  
15 15  
16 -(((
17 17  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.
18 18  
19 19  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.
20 20  
21 21  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.
22 22  
23 -NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
24 24  
25 -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).
26 -
27 -To use NLMS01, user needs to check if there is NB-IoT coverage in local area and with the bands NLMS01 supports. If the local operate support it, user needs to get a (% style="color:blue" %)**NB-IoT SIM card**(%%) from local operator and install NLMS01 to get NB-IoT network connection.
28 -)))
29 -
30 -
31 31  ​[[image:image-20220907171221-2.png]]
32 32  
33 33  
... ... @@ -55,6 +55,7 @@
55 55  (((
56 56  
57 57  
53 +
58 58  
59 59  )))
60 60  
... ... @@ -197,6 +197,8 @@
197 197  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
198 198  * (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
199 199  
196 +
197 +
200 200  For parameter description, please refer to AT command set
201 201  
202 202  [[image:image-20220907171221-9.png]]
... ... @@ -214,9 +214,11 @@
214 214  This feature is supported since firmware version v1.0.1
215 215  
216 216  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
217 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601     ** (%%) ~/~/  to set UDP server address and port
215 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601  ** (%%) ~/~/  to set UDP server address and port
218 218  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
219 219  
218 +
219 +
220 220  ​ [[image:image-20220907171221-11.png]]
221 221  
222 222  
... ... @@ -238,6 +238,8 @@
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 +
241 241  ​ [[image:image-20220907171221-13.png]]
242 242  
243 243  
... ... @@ -258,6 +258,8 @@
258 258  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
259 259  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  to set TCP server address and port
260 260  
263 +
264 +
261 261  ​ [[image:image-20220907171221-15.png]]
262 262  
263 263  
... ... @@ -274,6 +274,8 @@
274 274  
275 275  * (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
276 276  
281 +
282 +
277 277  (% 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).**
278 278  
279 279  
... ... @@ -286,10 +286,11 @@
286 286  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.
287 287  
288 288  
289 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
290 -|=(% 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**
291 -|=(% 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 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %)
296 +|(% style="width:96px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:42px" %)**2**|(% style="width:48px" %)**2**|(% style="width:124px" %)1|(% style="width:58px" %)1|(% style="width:82px" %)1|(% style="width:113px" %)2|(% style="width:134px" %)2|(% style="width:100px" %)4|(% style="width:137px" %)2|(% style="width:110px" %)2|(% style="width:122px" %)4
297 +|(% style="width:96px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:42px" %)Ver|(% style="width:48px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:58px" %)MOD|(% style="width:82px" %)Interrupt|(% style="width:113px" %)Leaf moisture|(% style="width:134px" %)Leaf Temperature|(% style="width:100px" %)Time stamp|(% style="width:137px" %)Leaf Temperature|(% style="width:110px" %)Leaf moisture|(% style="width:122px" %)Time stamp  .....
292 292  
299 +
293 293  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data.
294 294  
295 295  
... ... @@ -298,32 +298,24 @@
298 298  
299 299  The payload is ASCII string, representative same HEX:
300 300  
301 -**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__//(%%)**
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:
302 302  
303 -where:
310 +* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
311 +* (% style="color:blue" %)Version: 0x0064=100=1.0.0
312 +* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
313 +* (% style="color:red" %)Singal: 0x17 = 23
314 +* (% style="color:blue" %)Mod: 0x01 = 1
315 +* (% style="color:green" %)Interrupt: 0x00= 0
316 +* Leaf moisture: 0x0225= 549 = 54.9%
317 +* Leaf Temperature:0x010B =267=26.7 °C
318 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])
319 +* Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
320 +* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
304 304  
305 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138
306 306  
307 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
308 308  
309 -* (% style="color:#037691" %)**BAT:**       (%%)0x0c78 = 3192 mV = 3.192V
310 310  
311 -* (% style="color:#037691" %)**Singal:**(%%)  0x17 = 23
312 312  
313 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
314 -
315 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
316 -
317 -* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9%
318 -
319 -* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C
320 -
321 -* (% style="color:#037691" %)**Time stamp :**   (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])
322 -
323 -* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp :  **(%%)010b0226631550fb
324 -
325 -* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
326 -
327 327  == 2.4  Payload Explanation and Sensor Interface ==
328 328  
329 329  
... ... @@ -332,10 +332,10 @@
332 332  
333 333  By default, the Device ID equal to the last 15 bits of IMEI.
334 334  
335 -User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID
334 +User can use **AT+DEUI** to set Device ID
336 336  
337 337  
338 -(% style="color:blue" %)**Example**:
337 +**Example:**
339 339  
340 340  AT+DEUI=868411056754138
341 341  
... ... @@ -368,9 +368,8 @@
368 368  
369 369  NB-IoT Network signal Strength.
370 370  
370 +**Ex1: 0x1d = 29**
371 371  
372 -(% style="color:blue" %)**Ex1: 0x1d = 29**
373 -
374 374  **0**  -113dBm or less
375 375  
376 376  **1**  -111dBm
... ... @@ -386,11 +386,11 @@
386 386  === 2.4.5  Leaf moisture ===
387 387  
388 388  
389 -Get the moisture of the (% style="color:#037691" %)**Leaf**(%%). The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the Leaf.
387 +Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**.
390 390  
391 -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
389 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is
392 392  
393 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**
391 +**0229(H) = 549(D) /100 = 54.9.**
394 394  
395 395  
396 396  
... ... @@ -397,13 +397,13 @@
397 397  === 2.4.6  Leaf Temperature ===
398 398  
399 399  
400 -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
398 +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
401 401  
402 -(% style="color:blue" %)**Example**:
400 +**Example**:
403 403  
404 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
402 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
405 405  
406 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
404 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
407 407  
408 408  
409 409  
... ... @@ -415,15 +415,14 @@
415 415  Convert Unix timestamp to time 2022-9-5 9:40:11.
416 416  
417 417  
418 -
419 419  === 2.4.8  Digital Interrupt ===
420 420  
421 421  
422 -Digital Interrupt refers to pin (% style="color:#037691" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server.
419 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server.
423 423  
424 424  The command is:
425 425  
426 -(% 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]])**.**
423 +**AT+INTMOD=3 ** ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
427 427  
428 428  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.
429 429  
... ... @@ -442,7 +442,7 @@
442 442  
443 443  The 5V output time can be controlled by AT Command.
444 444  
445 -(% style="color:blue" %)**AT+5VT=1000**
442 +**AT+5VT=1000**
446 446  
447 447  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
448 448  
... ... @@ -456,11 +456,10 @@
456 456  [[image:image-20220907171221-18.png]] ​
457 457  
458 458  
459 -(% style="color:blue" %)**Examples:**
456 +**Examples:**
460 460  
458 +* **Set TDC**
461 461  
462 -* (% style="color:#037691" %)**Set TDC**
463 -
464 464  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
465 465  
466 466  Payload:    01 00 00 1E    TDC=30S
... ... @@ -467,16 +467,12 @@
467 467  
468 468  Payload:    01 00 00 3C    TDC=60S
469 469  
466 +* **Reset**
470 470  
471 -
472 -* (% style="color:#037691" %)**Reset**
473 -
474 474  If payload = 0x04FF, it will reset the NLMS01
475 475  
470 +* **INTMOD**
476 476  
477 -
478 -* (% style="color:#037691" %)**INTMOD**
479 -
480 480  Downlink Payload: 06000003, Set AT+INTMOD=3
481 481  
482 482  
... ... @@ -491,6 +491,9 @@
491 491  * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
492 492  * For each uplink probe, LED will be on for 500ms.
493 493  
486 +
487 +
488 +
494 494  == 2.7  Installation ==
495 495  
496 496  
... ... @@ -504,9 +504,9 @@
504 504  == 2.8  Moisture and Temperature alarm function ==
505 505  
506 506  
507 -(% style="color:blue" %)**➢ AT Command:**
502 +**➢ AT Command:**
508 508  
509 -(% style="color:#037691" %)**AT+ HUMALARM =min,max**
504 +**AT+ HUMALARM =min,max**
510 510  
511 511  ² When min=0, and max≠0, Alarm higher than max
512 512  
... ... @@ -515,7 +515,7 @@
515 515  ² When min≠0 and max≠0, Alarm higher than max or lower than min
516 516  
517 517  
518 -(% style="color:blue" %)**Example:**
513 +**Example:**
519 519  
520 520  AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
521 521  
... ... @@ -528,7 +528,7 @@
528 528  ² When min≠0 and max≠0, Alarm higher than max or lower than min
529 529  
530 530  
531 -(% style="color:blue" %)**Example:**
526 +**Example:**
532 532  
533 533  AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
534 534  
... ... @@ -537,24 +537,24 @@
537 537  == 2.9  Set the number of data to be uploaded and the recording time ==
538 538  
539 539  
540 -(% style="color:blue" %)**➢ AT Command:**
535 +**➢ AT Command:**
541 541  
542 -* (% 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)
543 -* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
537 +**AT+TR=900**  ~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
544 544  
545 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
539 +**AT+NOUD=8**  ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
546 546  
547 -[[image:image-20221009001002-1.png||height="706" width="982"]]
548 548  
549 549  
550 550  == 2.10  Read or Clear cached data ==
551 551  
552 552  
553 -(% style="color:blue" %)**➢ AT Command:**
546 +**➢ AT Command:**
554 554  
555 -* (% style="color:#037691" %)**AT+CDP**      (%%) ~/~/  Read cached data
556 -* (% style="color:#037691" %)**AT+CDP=0  ** (%%) ~/~/  Clear cached data
548 +**AT+CDP**  ~/~/  Read cached data
557 557  
550 +**AT+CDP=0  ** ~/~/  Clear cached data
551 +
552 +
558 558  [[image:image-20220907171221-20.png]]
559 559  
560 560  
... ... @@ -562,9 +562,9 @@
562 562  == 2.11  ​Firmware Change Log ==
563 563  
564 564  
565 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]
560 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
566 566  
567 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
562 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
568 568  
569 569  
570 570  
... ... @@ -595,9 +595,9 @@
595 595  
596 596  Instruction to use as below:
597 597  
598 -(% 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/]]
593 +**Step 1:  **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
599 599  
600 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
595 +**Step 2: ** Open it and choose
601 601  
602 602  * Product Model
603 603  * Uplink Interval
... ... @@ -642,86 +642,86 @@
642 642  
643 643  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]]
644 644  
645 -AT+<CMD>?  :  Help on <CMD>
640 +AT+<CMD>?  : Help on <CMD>
646 646  
647 -AT+<CMD>  Run <CMD>
642 +AT+<CMD>         : Run <CMD>
648 648  
649 -AT+<CMD>=<value>:  Set the value
644 +AT+<CMD>=<value> : Set the value
650 650  
651 -AT+<CMD>=?  Get the value
646 +AT+<CMD>=?  : Get the value
652 652  
653 653  
654 -(% style="color:#037691" %)**General Commands**      
649 +**General Commands**      
655 655  
656 -AT  Attention       
651 +AT  : Attention       
657 657  
658 -AT?  Short Help     
653 +AT?  : Short Help     
659 659  
660 -ATZ  MCU Reset    
655 +ATZ  : MCU Reset    
661 661  
662 -AT+TDC  :  Application Data Transmission Interval
657 +AT+TDC  : Application Data Transmission Interval
663 663  
664 -AT+CFG  :  Print all configurations
659 +AT+CFG  : Print all configurations
665 665  
666 -AT+CFGMOD  :  Working mode selection
661 +AT+CFGMOD           : Working mode selection
667 667  
668 -AT+INTMOD  :  Set the trigger interrupt mode
663 +AT+INTMOD            : Set the trigger interrupt mode
669 669  
670 -AT+5VT  Set extend the time of 5V power  
665 +AT+5VT  : Set extend the time of 5V power  
671 671  
672 -AT+PRO :  Choose agreement
667 +AT+PRO  : Choose agreement
673 673  
674 -AT+RXDL:  Extend the sending and receiving time
669 +AT+RXDL  : Extend the sending and receiving time
675 675  
676 -AT+SERVADDR :  Server Address
671 +AT+SERVADDR  : Server Address
677 677  
678 -AT+APN :  Get or set the APN
673 +AT+APN     : Get or set the APN
679 679  
680 -AT+FBAND :  Get or Set whether to automatically modify the frequency band
675 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
681 681  
682 -AT+DNSCFG : Get or Set DNS Server
677 +AT+DNSCFG  : Get or Set DNS Server
683 683  
684 684  AT+GETSENSORVALUE   : Returns the current sensor measurement
685 685  
686 -AT+TR :  Get or Set record time"
681 +AT+TR      : Get or Set record time"
687 687  
688 -AT+NOUD :  Get or Set the number of data to be uploaded
683 +AT+NOUD      : Get or Set the number of data to be uploaded
689 689  
690 -AT+CDP :  Read or Clear cached data
685 +AT+CDP     : Read or Clear cached data
691 691  
692 -AT+TEMPALARM :  Get or Set alarm of temp
687 +AT+TEMPALARM      : Get or Set alarm of temp
693 693  
694 -AT+HUMALARM :  Get or Set alarm of humidity
689 +AT+HUMALARM     : Get or Set alarm of PH
695 695  
696 696  
697 -(% style="color:#037691" %)**COAP Management**      
692 +**COAP Management**      
698 698  
699 -AT+URI :  Resource parameters
694 +AT+URI            : Resource parameters
700 700  
701 701  
702 -(% style="color:#037691" %)**UDP Management**
697 +**UDP Management**
703 703  
704 -AT+CFM :  Upload confirmation mode (only valid for UDP)
699 +AT+CFM          : Upload confirmation mode (only valid for UDP)
705 705  
706 706  
707 -(% style="color:#037691" %)**MQTT Management**
702 +**MQTT Management**
708 708  
709 -AT+CLIENT  :  Get or Set MQTT client
704 +AT+CLIENT               : Get or Set MQTT client
710 710  
711 -AT+UNAME  : Get or Set MQTT Username
706 +AT+UNAME  : Get or Set MQTT Username
712 712  
713 -AT+PWD  :  Get or Set MQTT password
708 +AT+PWD                  : Get or Set MQTT password
714 714  
715 -AT+PUBTOPIC  Get or Set MQTT publish topic
710 +AT+PUBTOPIC  : Get or Set MQTT publish topic
716 716  
717 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
712 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
718 718  
719 719  
720 -(% style="color:#037691" %)**Information**          
715 +**Information**          
721 721  
722 -AT+FDR :  Factory Data Reset
717 +AT+FDR  : Factory Data Reset
723 723  
724 -AT+PWORD :  Serial Access Password
719 +AT+PWORD  : Serial Access Password
725 725  
726 726  
727 727  
... ... @@ -735,11 +735,10 @@
735 735  
736 736  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]]
737 737  
733 +**Notice, NLMS01** **and LLMS01** **share the same mother board. They use the same connection and method to update.**
738 738  
739 -(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.**
740 740  
741 741  
742 -
743 743  = 6.  Trouble Shooting =
744 744  
745 745  
... ... @@ -753,7 +753,7 @@
753 753  == 6.2  AT Command input doesn't work ==
754 754  
755 755  
756 -In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
750 +In the case if user can see the console output but can't type input to the device. Please check if you already include the **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.
757 757  
758 758  
759 759  
... ... @@ -767,11 +767,11 @@
767 767  = 8.  Packing Info =
768 768  
769 769  
770 -(% style="color:#037691" %)**Package Includes:**
764 +**Package Includes**:
771 771  
772 772  * NLMS01 NB-IoT Leaf Moisture Sensor x 1
773 773  
774 -(% style="color:#037691" %)**Dimension and weight**:
768 +**Dimension and weight**:
775 775  
776 776  * Device Size: cm
777 777  * Device Weight: g
... ... @@ -778,6 +778,9 @@
778 778  * Package Size / pcs : cm
779 779  * Weight / pcs : g
780 780  
775 +
776 +
777 +
781 781  = 9.  Support =
782 782  
783 783  
image-20221009001002-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0