<
From version < 32.1 >
edited by David Huang
on 2022/09/08 09:49
To version < 26.1 >
edited by David Huang
on 2022/09/07 17:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,7 @@
1 -(% style="text-align:center" %)
2 -[[image:image-20220907171221-1.jpeg]]
1 +[[image:image-20220907171221-1.jpeg]]​
3 3  
4 -​
5 5  
6 -{{toc/}}
7 7  
8 -
9 -
10 10  = 1. Introduction =
11 11  
12 12  == 1.1 ​What is NLMS01 Leaf Moisture Sensor ==
... ... @@ -124,9 +124,9 @@
124 124  
125 125  [[image:image-20220907171221-5.png]]
126 126  
127 -== 2.2 ​ Configure the NLMS01 ==
122 +== **2.2 ​ Configure the NLMS01** ==
128 128  
129 -=== 2.2.1 Test Requirement ===
124 +**2.2.1 Test Requirement**
130 130  
131 131  To use NLMS01 in your city, make sure meet below requirements:
132 132  
... ... @@ -138,7 +138,7 @@
138 138  
139 139  [[image:image-20220907171221-6.png]] ​
140 140  
141 -=== 2.2.2 Insert SIM card ===
136 +**2.2.2 Insert SIM card**
142 142  
143 143  Insert the NB-IoT Card get from your provider.
144 144  
... ... @@ -146,7 +146,7 @@
146 146  
147 147  [[image:image-20220907171221-7.png]] ​
148 148  
149 -=== 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
144 +**2.2.3 Connect USB – TTL to NLMS01 to configure it**
150 150  
151 151  User need to configure NLMS01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below.
152 152  
... ... @@ -172,7 +172,7 @@
172 172  
173 173  **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]]
174 174  
175 -=== 2.2.4 Use CoAP protocol to uplink data ===
170 +**2.2.4 Use CoAP protocol to uplink data**
176 176  
177 177  **Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
178 178  
... ... @@ -190,7 +190,7 @@
190 190  
191 191  [[image:image-20220907171221-10.png]] ​
192 192  
193 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
188 +**2.2.5 Use UDP protocol to uplink data(Default protocol)**
194 194  
195 195  This feature is supported since firmware version v1.0.1
196 196  
... ... @@ -204,7 +204,7 @@
204 204  
205 205  ​
206 206  
207 -=== 2.2.6 Use MQTT protocol to uplink data ===
202 +**2.2.6 Use MQTT protocol to uplink data**
208 208  
209 209  This feature is supported since firmware version v110
210 210  
... ... @@ -224,7 +224,7 @@
224 224  
225 225  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.
226 226  
227 -=== 2.2.7 Use TCP protocol to uplink data ===
222 +**2.2.7 Use TCP protocol to uplink data**
228 228  
229 229  This feature is supported since firmware version v110
230 230  
... ... @@ -237,14 +237,15 @@
237 237  
238 238  ​
239 239  
240 -=== 2.2.8 Change Update Interval ===
235 +**2.2.8 Change Update Interval**
241 241  
242 242  User can use below command to change the **uplink interval**.
243 243  
244 -* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hour)
239 +* **AT+TDC=600      ** ~/~/ Set Update Interval to 600s
245 245  
246 -**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).**
241 +**NOTE:**
247 247  
243 +**~1. By default, the device will send an uplink message every 2 hour.**
248 248  
249 249  == 2.3  Uplink Payload ==
250 250  
... ... @@ -261,23 +261,24 @@
261 261  
262 262  The payload is ASCII string, representative same HEX:
263 263  
264 -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:
260 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where:
265 265  
266 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
267 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0
268 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
269 -* (% style="color:red" %)Singal: 0x17 = 23
270 -* (% style="color:blue" %)Mod: 0x01 = 1
271 -* (% style="color:green" %)Interrupt: 0x00= 0
262 +* Device ID: 0xf868411056754138 = f868411056754138
263 +* Version: 0x0064=100=1.0.0
264 +
265 +* BAT: 0x0c78 = 3192 mV = 3.192V
266 +* Singal: 0x17 = 23
267 +* Mod: 0x01 = 1
268 +* Interrupt: 0x00= 0
272 272  * Leaf moisture: 0x0225= 549 = 54.9%
273 273  * Leaf Temperature:0x010B =267=26.7 °C
274 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>https://www.epochconverter.com/]])
271 +* Time stamp : 0x6315537b =1662342011
275 275  * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
276 -* (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
273 +* 8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
277 277  
278 278  == 2.4  Payload Explanation and Sensor Interface ==
279 279  
280 -=== 2.4.1  Device ID ===
277 +**2.4.1  Device ID**
281 281  
282 282  By default, the Device ID equal to the last 15 bits of IMEI.
283 283  
... ... @@ -289,13 +289,13 @@
289 289  
290 290  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
291 291  
292 -=== 2.4.2  Version Info ===
289 +**2.4.2  Version Info**
293 293  
294 294  Specify the software version: 0x64=100, means firmware version 1.00.
295 295  
296 296  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
297 297  
298 -=== 2.4.3  Battery Info ===
295 +**2.4.3  Battery Info**
299 299  
300 300  Check the battery voltage for NLMS01.
301 301  
... ... @@ -303,7 +303,7 @@
303 303  
304 304  Ex2: 0x0B49 = 2889mV
305 305  
306 -=== 2.4.4  Signal Strength ===
303 +**2.4.4  Signal Strength**
307 307  
308 308  NB-IoT Network signal Strength.
309 309  
... ... @@ -319,7 +319,7 @@
319 319  
320 320  **99**    Not known or not detectable
321 321  
322 -=== 2.4.5  Leaf moisture ===
319 +**2.4.5  Leaf** moisture
323 323  
324 324  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**.
325 325  
... ... @@ -327,7 +327,7 @@
327 327  
328 328  **0229(H) = 549(D) /100 = 54.9.**
329 329  
330 -=== 2.4.6  Leaf Temperature ===
327 +**2.4.6  Leaf Temperature**
331 331  
332 332  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
333 333  
... ... @@ -337,13 +337,13 @@
337 337  
338 338  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
339 339  
340 -=== 2.4.7  Timestamp ===
337 +**2.4.7  Timestamp**
341 341  
342 342  Time stamp : 0x6315537b =1662342011
343 343  
344 344  Convert Unix timestamp to time 2022-9-5 9:40:11.
345 345  
346 -=== 2.4.8  Digital Interrupt ===
343 +**2.4.8  Digital Interrupt**
347 347  
348 348  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.
349 349  
... ... @@ -359,7 +359,7 @@
359 359  
360 360  0x(01): Interrupt Uplink Packet.
361 361  
362 -=== 2.4.9  ​+5V Output ===
359 +**2.4.9  ​+5V Output**
363 363  
364 364  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
365 365  
... ... @@ -466,7 +466,7 @@
466 466  
467 467  == 2.12  ​Battery Analysis ==
468 468  
469 -=== 2.12.1  ​Battery Type ===
466 +**2.12.1  ​Battery Type**
470 470  
471 471  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.
472 472  
... ... @@ -480,7 +480,7 @@
480 480  
481 481  [[image:image-20220907171221-21.png]] ​
482 482  
483 -=== 2.12.2  Power consumption Analyze ===
480 +**2.12.2  Power consumption Analyze**
484 484  
485 485  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.
486 486  
... ... @@ -498,11 +498,11 @@
498 498  
499 499  [[image:image-20220907171221-22.jpeg]] ​
500 500  
501 -=== 2.12.3  ​Battery Note ===
498 +**2.12.3  ​Battery Note**
502 502  
503 503  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.
504 504  
505 -=== 2.12.4  Replace the battery ===
502 +**2.12.4  Replace the battery**
506 506  
507 507  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).
508 508  
... ... @@ -516,7 +516,7 @@
516 516  
517 517  = 4.  Using the AT Commands =
518 518  
519 -== 4.1  Access AT Commands ==
516 +**4.1  Access AT Commands**
520 520  
521 521  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]]
522 522  
... ... @@ -552,20 +552,15 @@
552 552  
553 553  AT+SERVADDR  : Server Address
554 554  
555 -AT+APN     : Get or set the APN
556 -
557 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
558 -
559 -AT+DNSCFG  : Get or Set DNS Server
560 -
561 -AT+GETSENSORVALUE   : Returns the current sensor measurement
562 -
563 563  AT+TR      : Get or Set record time"
564 564  
554 +
565 565  AT+NOUD      : Get or Set the number of data to be uploaded
566 566  
557 +
567 567  AT+CDP     : Read or Clear cached data
568 568  
560 +
569 569  AT+TEMPALARM      : Get or Set alarm of temp
570 570  
571 571  AT+HUMALARM     : Get or Set alarm of PH
... ... @@ -599,7 +599,7 @@
599 599  
600 600  = ​5.  FAQ =
601 601  
602 -== 5.1 ​ How to Upgrade Firmware ==
594 +**5.1 ​ How to Upgrade Firmware**
603 603  
604 604  User can upgrade the firmware for 1) bug fix, 2) new feature release.
605 605  
... ... @@ -609,11 +609,11 @@
609 609  
610 610  = 6.  Trouble Shooting =
611 611  
612 -== 6.1  ​Connection problem when uploading firmware ==
604 +**6.1  ​Connection problem when uploading firmware**
613 613  
614 614  **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]]
615 615  
616 -== 6.2  AT Command input doesn't work ==
608 +**6.2  AT Command input doesn't work**
617 617  
618 618  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.
619 619  
... ... @@ -640,3 +640,5 @@
640 640  * 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]]
641 641  
642 642  ​
635 +
636 +
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0