<
From version < 38.13 >
edited by Xiaoling
on 2023/04/04 09:49
To version < 33.2 >
edited by Xiaoling
on 2022/09/13 09:14
>
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  
... ... @@ -34,6 +34,7 @@
34 34  ​ [[image:image-20220907171221-3.png]]
35 35  
36 36  
32 +
37 37  == ​1.2  Features ==
38 38  
39 39  
... ... @@ -54,6 +54,7 @@
54 54  (((
55 55  
56 56  
53 +
57 57  
58 58  )))
59 59  
... ... @@ -67,15 +67,13 @@
67 67  
68 68  (% style="color:#037691" %)**NB-IoT Spec:**
69 69  
70 -* B1 @H-FDD: 2100MHz
71 -* B3 @H-FDD: 1800MHz
72 -* B8 @H-FDD: 900MHz
73 -* B5 @H-FDD: 850MHz
74 -* B20 @H-FDD: 800MHz
75 -* 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
76 76  
77 -
78 -
79 79  == 1.4  Probe Specification ==
80 80  
81 81  
... ... @@ -95,15 +95,11 @@
95 95  * IP67 Protection
96 96  * Length: 3.5 meters
97 97  
98 -
99 -
100 100  == 1.5 ​ Applications ==
101 101  
102 102  
103 103  * Smart Agriculture
104 104  
105 -
106 -
107 107  == 1.6  Pin mapping and power on ==
108 108  
109 109  
... ... @@ -111,8 +111,10 @@
111 111  
112 112  **~ **
113 113  
105 +
114 114  = 2.  Use NLMS01 to communicate with IoT Server =
115 115  
108 +
116 116  == 2.1  How it works ==
117 117  
118 118  
... ... @@ -124,8 +124,10 @@
124 124  [[image:image-20220907171221-5.png]]
125 125  
126 126  
120 +
127 127  == 2.2 ​ Configure the NLMS01 ==
128 128  
123 +
129 129  === 2.2.1 Test Requirement ===
130 130  
131 131  
... ... @@ -141,6 +141,7 @@
141 141  [[image:image-20220907171221-6.png]] ​
142 142  
143 143  
139 +
144 144  === 2.2.2 Insert SIM card ===
145 145  
146 146  
... ... @@ -152,6 +152,7 @@
152 152  [[image:image-20220907171221-7.png]] ​
153 153  
154 154  
151 +
155 155  === 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
156 156  
157 157  
... ... @@ -183,6 +183,7 @@
183 183  (% 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]]
184 184  
185 185  
183 +
186 186  === 2.2.4 Use CoAP protocol to uplink data ===
187 187  
188 188  
... ... @@ -195,6 +195,8 @@
195 195  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
196 196  * (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
197 197  
196 +
197 +
198 198  For parameter description, please refer to AT command set
199 199  
200 200  [[image:image-20220907171221-9.png]]
... ... @@ -205,6 +205,7 @@
205 205  [[image:image-20220907171221-10.png]] ​
206 206  
207 207  
208 +
208 208  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
209 209  
210 210  
... ... @@ -211,9 +211,11 @@
211 211  This feature is supported since firmware version v1.0.1
212 212  
213 213  * (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
214 -* (% 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
215 215  * (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
216 216  
218 +
219 +
217 217  ​ [[image:image-20220907171221-11.png]]
218 218  
219 219  
... ... @@ -221,6 +221,7 @@
221 221  
222 222  ​
223 223  
227 +
224 224  === 2.2.6 Use MQTT protocol to uplink data ===
225 225  
226 226  
... ... @@ -234,6 +234,8 @@
234 234  * (% style="color:#037691" %)**AT+PUBTOPIC=PUB                    ** (%%) ~/~/  Set the sending topic of MQTT
235 235  * (% style="color:#037691" %)**AT+SUBTOPIC=SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
236 236  
241 +
242 +
237 237  ​ [[image:image-20220907171221-13.png]]
238 238  
239 239  
... ... @@ -245,6 +245,7 @@
245 245  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.
246 246  
247 247  
254 +
248 248  === 2.2.7 Use TCP protocol to uplink data ===
249 249  
250 250  
... ... @@ -253,6 +253,8 @@
253 253  * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
254 254  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  to set TCP server address and port
255 255  
263 +
264 +
256 256  ​ [[image:image-20220907171221-15.png]]
257 257  
258 258  
... ... @@ -269,9 +269,12 @@
269 269  
270 270  * (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
271 271  
281 +
282 +
272 272  (% 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).**
273 273  
274 274  
286 +
275 275  == 2.3  Uplink Payload ==
276 276  
277 277  
... ... @@ -280,10 +280,11 @@
280 280  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.
281 281  
282 282  
283 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
284 -|=(% 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**
285 -|=(% 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  .....
286 286  
299 +
287 287  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data.
288 288  
289 289  
... ... @@ -292,62 +292,46 @@
292 292  
293 293  The payload is ASCII string, representative same HEX:
294 294  
295 -**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:
296 296  
297 -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,.......
298 298  
299 -* (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138
300 300  
301 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
302 302  
303 -* (% style="color:#037691" %)**BAT:**       (%%)0x0c78 = 3192 mV = 3.192V
304 304  
305 -* (% style="color:#037691" %)**Singal:**(%%)  0x17 = 23
306 306  
307 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
308 -
309 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
310 -
311 -* (% style="color:#037691" %)**Leaf moisture:**(%%) 0x0225= 549 = 54.9%
312 -
313 -* (% style="color:#037691" %)**Leaf Temperature: **(%%)0x010B =267=26.7 °C
314 -
315 -* (% style="color:#037691" %)**Time stamp :**   (%%)0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])
316 -
317 -* (% style="color:#037691" %)**Leaf Temperature, Leaf moisture,Time stamp :  **(%%)010b0226631550fb
318 -
319 -* (% style="color:#037691" %)**8 sets of recorded data: **(%%)Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
320 -
321 -
322 -
323 323  == 2.4  Payload Explanation and Sensor Interface ==
324 324  
325 325  === 2.4.1  Device ID ===
326 326  
327 -
328 328  By default, the Device ID equal to the last 15 bits of IMEI.
329 329  
330 -User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID
332 +User can use **AT+DEUI** to set Device ID
331 331  
334 +**Example:**
332 332  
333 -(% style="color:blue" %)**Example**:
334 -
335 335  AT+DEUI=868411056754138
336 336  
337 337  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
338 338  
339 -
340 340  === 2.4.2  Version Info ===
341 341  
342 -
343 343  Specify the software version: 0x64=100, means firmware version 1.00.
344 344  
345 345  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
346 346  
347 -
348 348  === 2.4.3  Battery Info ===
349 349  
350 -
351 351  Check the battery voltage for NLMS01.
352 352  
353 353  Ex1: 0x0B45 = 2885mV
... ... @@ -354,15 +354,12 @@
354 354  
355 355  Ex2: 0x0B49 = 2889mV
356 356  
357 -
358 358  === 2.4.4  Signal Strength ===
359 359  
360 -
361 361  NB-IoT Network signal Strength.
362 362  
358 +**Ex1: 0x1d = 29**
363 363  
364 -(% style="color:blue" %)**Ex1: 0x1d = 29**
365 -
366 366  **0**  -113dBm or less
367 367  
368 368  **1**  -111dBm
... ... @@ -373,45 +373,37 @@
373 373  
374 374  **99**    Not known or not detectable
375 375  
376 -
377 377  === 2.4.5  Leaf moisture ===
378 378  
372 +Get the moisture of the **Leaf**. The value range of the register is 300-1000(Decimal), divide this value by 100 to get the percentage of moisture in the **Leaf**.
379 379  
380 -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.
374 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is
381 381  
382 -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
376 +**0229(H) = 549(D) /100 = 54.9.**
383 383  
384 -(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**
385 -
386 -
387 387  === 2.4.6  Leaf Temperature ===
388 388  
380 +Get the temperature in the **Leaf**. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the **Leaf**. For example, if the data you get from the register is **__0x09 0xEC__**, the temperature content in the **Leaf **is
389 389  
390 -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
382 +**Example**:
391 391  
392 -(% style="color:blue" %)**Example**:
384 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
393 393  
394 -If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
386 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
395 395  
396 -If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
397 -
398 -
399 399  === 2.4.7  Timestamp ===
400 400  
401 -
402 402  Time stamp : 0x6315537b =1662342011
403 403  
404 404  Convert Unix timestamp to time 2022-9-5 9:40:11.
405 405  
406 -
407 407  === 2.4.8  Digital Interrupt ===
408 408  
396 +Digital Interrupt refers to pin **GPIO_EXTI**, and there are different trigger methods. When there is a trigger, the NLMS01 will send a packet to the server.
409 409  
410 -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.
411 -
412 412  The command is:
413 413  
414 -(% 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]])**.**
400 +**AT+INTMOD=3 ** ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
415 415  
416 416  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.
417 417  
... ... @@ -421,15 +421,13 @@
421 421  
422 422  0x(01): Interrupt Uplink Packet.
423 423  
424 -
425 425  === 2.4.9  ​+5V Output ===
426 426  
427 -
428 428  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
429 429  
430 430  The 5V output time can be controlled by AT Command.
431 431  
432 -(% style="color:blue" %)**AT+5VT=1000**
416 +**AT+5VT=1000**
433 433  
434 434  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
435 435  
... ... @@ -436,17 +436,14 @@
436 436  
437 437  == 2.5  Downlink Payload ==
438 438  
439 -
440 440  By default, NLMS01 prints the downlink payload to console port.
441 441  
442 442  [[image:image-20220907171221-18.png]] ​
443 443  
427 +**Examples:**
444 444  
445 -(% style="color:blue" %)**Examples:**
429 +* **Set TDC**
446 446  
447 -
448 -* (% style="color:#037691" %)**Set TDC**
449 -
450 450  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
451 451  
452 452  Payload:    01 00 00 1E    TDC=30S
... ... @@ -453,22 +453,16 @@
453 453  
454 454  Payload:    01 00 00 3C    TDC=60S
455 455  
437 +* **Reset**
456 456  
457 -
458 -* (% style="color:#037691" %)**Reset**
459 -
460 460  If payload = 0x04FF, it will reset the NLMS01
461 461  
441 +* **INTMOD**
462 462  
463 -
464 -* (% style="color:#037691" %)**INTMOD**
465 -
466 466  Downlink Payload: 06000003, Set AT+INTMOD=3
467 467  
468 -
469 469  == 2.6  ​LED Indicator ==
470 470  
471 -
472 472  The NLMS01 has an internal LED which is to show the status of different state.
473 473  
474 474  * When power on, NLMS01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
... ... @@ -476,24 +476,18 @@
476 476  * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
477 477  * For each uplink probe, LED will be on for 500ms.
478 478  
454 +== 2.7 Installation ==
479 479  
480 -
481 -== 2.7  Installation ==
482 -
483 -
484 484  NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
485 485  
486 -
487 487  [[image:image-20220907171221-19.png]]
488 488  
460 +== 2.8 Moisture and Temperature alarm function ==
489 489  
490 -== 2.8  Moisture and Temperature alarm function ==
462 + AT Command:
491 491  
464 +AT+ HUMALARM =min,max
492 492  
493 -(% style="color:blue" %)**➢ AT Command:**
494 -
495 -(% style="color:#037691" %)**AT+ HUMALARM =min,max**
496 -
497 497  ² When min=0, and max≠0, Alarm higher than max
498 498  
499 499  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -500,9 +500,8 @@
500 500  
501 501  ² When min≠0 and max≠0, Alarm higher than max or lower than min
502 502  
472 +Example:
503 503  
504 -(% style="color:blue" %)**Example:**
505 -
506 506  AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
507 507  
508 508  AT+ TEMPALARM=min,max
... ... @@ -513,193 +513,201 @@
513 513  
514 514  ² When min≠0 and max≠0, Alarm higher than max or lower than min
515 515  
484 +Example:
516 516  
517 -(% style="color:blue" %)**Example:**
518 -
519 519  AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
520 520  
521 521  
522 -== 2.9  Set the number of data to be uploaded and the recording time ==
489 +== 2.9 Set the number of data to be uploaded and the recording time ==
523 523  
491 +➢ AT Command:
524 524  
525 -(% style="color:blue" %)**➢ AT Command:**
493 +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)
526 526  
527 -* (% 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)
528 -* (% 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.
495 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
529 529  
530 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
497 +== 2.10 Read or Clear cached data ==
531 531  
532 -[[image:image-20221009001002-1.png||height="706" width="982"]]
499 +➢ AT Command:
533 533  
501 +AT+CDP    ~/~/ Read cached data
534 534  
535 -== 2.10  Read or Clear cached data ==
503 +[[image:image-20220907171221-20.png]]
536 536  
537 537  
538 -(% style="color:blue" %)**➢ AT Command:**
506 +AT+CDP=0    ~/~/ Clear cached data
539 539  
540 -* (% style="color:#037691" %)**AT+CDP**      (%%) ~/~/  Read cached data
541 -* (% style="color:#037691" %)**AT+CDP=0  ** (%%) ~/~/  Clear cached data
542 542  
543 -[[image:image-20220907171221-20.png]]
509 +== 2.11  ​Firmware Change Log ==
544 544  
511 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
545 545  
546 -== 2.11  Firmware Change Log ==
513 +Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
547 547  
515 +== 2.12  ​Battery Analysis ==
548 548  
549 -Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0>>https://www.dropbox.com/sh/qdc3js2iu1vlipx/AACMHI3CvVb8g7YQMrIHY673a?dl=0]]
517 +=== 2.12.1  ​Battery Type ===
550 550  
551 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
519 +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.
552 552  
521 +The battery is designed to last for several years depends on the actually use environment and update interval. 
553 553  
554 -== 2.12 Battery & Power Consumption ==
523 +The battery related documents as below:
555 555  
525 +* [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
526 +* [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
527 +* [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
556 556  
557 -NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
529 +[[image:image-20220907171221-21.png]]
558 558  
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/]] .
531 +=== 2.12.2  Power consumption Analyze ===
560 560  
533 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
561 561  
562 -= 3. ​ Access NB-IoT Module =
535 +Instruction to use as below:
563 563  
537 +**Step 1:  **Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
564 564  
565 -Users can directly access the AT command set of the NB-IoT module.
539 +**Step 2: ** Open it and choose
566 566  
567 -The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
541 +* Product Model
542 +* Uplink Interval
543 +* Working Mode
568 568  
545 +And the Life expectation in difference case will be shown on the right.
569 569  
570 -[[image:image-20220907171221-23.png]] ​
547 +[[image:image-20220907171221-22.jpeg]] ​
571 571  
549 +=== 2.12.3  ​Battery Note ===
572 572  
573 -= 4.  Using the AT Commands =
551 +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.
574 574  
575 -== 4.1  Access AT Commands ==
553 +=== 2.12.4  Replace the battery ===
576 576  
555 +The default battery pack of NLMS01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
577 577  
578 -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]]
557 += 3. Access NB-IoT Module =
579 579  
580 -AT+<CMD>?  Help on <CMD>
559 +Users can directly access the AT command set of the NB-IoT module.
581 581  
582 -AT+<CMD>  Run <CMD>
561 +The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
583 583  
584 -AT+<CMD>=<value>:  Set the value
563 +[[image:image-20220907171221-23.png]] ​
585 585  
586 -AT+<CMD>= :  Get the value
565 += 4.  Using the AT Commands =
587 587  
567 +== 4.1  Access AT Commands ==
588 588  
589 -(% style="color:#037691" %)**General Commands**      
569 +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]]
590 590  
591 -AT  Attention       
571 +AT+<CMD>?  : Help on <CMD>
592 592  
593 -AT?  :  Short Help     
573 +AT+<CMD>         : Run <CMD>
594 594  
595 -AT MCU Reset    
575 +AT+<CMD>=<value> : Set the value
596 596  
597 -AT+TD Application Data Transmission Interval
577 +AT+<CMD>=?  : Get the value
598 598  
599 -AT+CFG  :  Print all configurations
579 +**General Commands**      
600 600  
601 -AT+CFGMOD  Working mode selection
581 +AT  : Attention       
602 602  
603 -AT+INTMOD  Set the trigger interrupt mode
583 +AT?  : Short Help     
604 604  
605 -AT+5VT  Set extend the time of 5V power  
585 +ATZ  : MCU Reset    
606 606  
607 -AT+PRO :  Choose agreement
587 +AT+TDC  : Application Data Transmission Interval
608 608  
609 -AT+RXDL:  Extend the sending and receiving time
589 +AT+CFG  : Print all configurations
610 610  
611 -AT+SERVADDR :  Server Address
591 +AT+CFGMOD           : Working mode selection
612 612  
613 -AT+APN :  Get or set the APN
593 +AT+INTMOD            : Set the trigger interrupt mode
614 614  
615 -AT+FBAND :  Get or Set whether to automatically modify the frequency band
595 +AT+5VT  : Set extend the time of 5V power  
616 616  
617 -AT+DNSCFG : Get or Set DNS Server
597 +AT+PRO  : Choose agreement
618 618  
619 -AT+GETSENSORVALUE   : Returns the current sensor measurement
599 +AT+RXD : Extend the sending and receiving time
620 620  
621 -AT+TR :  Get or Set record time"
601 +AT+SERVADDR  : Server Address
622 622  
623 -AT+NOUD :  Get or Set the number of data to be uploaded
603 +AT+AP    : Get or set the APN
624 624  
625 -AT+CDP :  Read or Clear cached data
605 +AT+FBAN  : Get or Set whether to automatically modify the frequency band
626 626  
627 -AT+TEMPALARM :  Get or Set alarm of temp
607 +AT+DNSCFG  : Get or Set DNS Server
628 628  
629 -AT+HUMALARM :  Get or Set alarm of humidity
609 +AT+GETSENSORVALUE   : Returns the current sensor measurement
630 630  
611 +AT+TR      : Get or Set record time"
631 631  
632 -(% style="color:#037691" %)**COAP Management**      
613 +AT+NOUD      : Get or Set the number of data to be uploaded
633 633  
634 -AT+URI :  Resource parameters
615 +AT+CDP     : Read or Clear cached data
635 635  
617 +AT+TEMPALARM      : Get or Set alarm of temp
636 636  
637 -(% style="color:#037691" %)**UDP Management**
619 +AT+HUMALARM     : Get or Set alarm of PH
638 638  
639 -AT+CFM :  Upload confirmation mode (only valid for UDP)
640 640  
622 +**COAP Management**      
641 641  
642 -(% style="color:#037691" %)**MQTT Management**
624 +AT+URI            : Resource parameters
643 643  
644 -AT+CLIENT  :  Get or Set MQTT client
626 +**UDP Management**
645 645  
646 -AT+UNAME  : Get or Set MQTT Username
628 +AT+CF         : Upload confirmation mode (only valid for UDP)
647 647  
648 -AT+PWD  :  Get or Set MQTT password
630 +**MQTT Management**
649 649  
650 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
632 +AT+CLIENT               : Get or Set MQTT client
651 651  
652 -AT+SUBTOPIC :  Get or Set MQTT subscription topic
634 +AT+UNAME  : Get or Set MQTT Username
653 653  
636 +AT+PWD                  : Get or Set MQTT password
654 654  
655 -(% style="color:#037691" %)**Information**          
638 +AT+PUBTOPIC  : Get or Set MQTT publish topic
656 656  
657 -AT+FDR :  Factory Data Reset
640 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
658 658  
659 -AT+PWORD :  Serial Access Password
642 +**Information**          
660 660  
644 +AT+FDR  : Factory Data Reset
661 661  
646 +AT+PWORD  : Serial Access Password
647 +
662 662  = ​5.  FAQ =
663 663  
664 664  == 5.1 ​ How to Upgrade Firmware ==
665 665  
666 -
667 667  User can upgrade the firmware for 1) bug fix, 2) new feature release.
668 668  
669 669  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]]
670 670  
656 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.**
671 671  
672 -(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.**
673 -
674 -
675 675  = 6.  Trouble Shooting =
676 676  
677 677  == 6.1  ​Connection problem when uploading firmware ==
678 678  
679 -
680 680  **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]]
681 681  
682 -
683 683  == 6.2  AT Command input doesn't work ==
684 684  
666 +In the case if user can see the console output but can't type input to the device. Please check if you already include the **ENTER** while sending out the command. Some serial tool doesn't send **ENTER** while press the send key, user need to add ENTER in their string.
685 685  
686 -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.
687 -
688 -
689 689  = 7. ​ Order Info =
690 690  
691 -
692 692  Part Number**:** NLMS01
693 693  
694 -
695 695  = 8.  Packing Info =
696 696  
674 +**Package Includes**:
697 697  
698 -(% style="color:#037691" %)**Package Includes:**
699 -
700 700  * NLMS01 NB-IoT Leaf Moisture Sensor x 1
701 701  
702 -(% style="color:#037691" %)**Dimension and weight**:
678 +**Dimension and weight**:
703 703  
704 704  * Device Size: cm
705 705  * Device Weight: g
... ... @@ -706,11 +706,8 @@
706 706  * Package Size / pcs : cm
707 707  * Weight / pcs : g
708 708  
709 -
710 -
711 711  = 9.  Support =
712 712  
713 -
714 714  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
715 715  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
716 716  
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