Last modified by Mengting Qiu on 2024/04/02 16:54
<
From version < 29.1 >
edited by Edwin Chen
on 2022/09/08 00:20
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.David
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,16 +237,16 @@
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  
241 +**NOTE:**
246 246  
247 -**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).**
243 +**~1. By default, the device will send an uplink message every 2 hour.**
248 248  
249 -
250 250  == 2.3  Uplink Payload ==
251 251  
252 252  In this mode, uplink payload includes 87 bytes in total by default.
... ... @@ -262,23 +262,24 @@
262 262  
263 263  The payload is ASCII string, representative same HEX:
264 264  
265 -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" %)0225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859(%%) where:
260 +0xf86841105675413800640c781701000225010b6315537b010b0226631550fb010e022663154d7701110225631549f1011502246315466b01190223631542e5011d022163153f62011e022163153bde011e022163153859 where:
266 266  
267 -* (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138(%%)
268 -* (% style="color:blue" %)Version: 0x0064=100=1.0.0(%%)
269 -* (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V(%%)
270 -* (% style="color:red" %)Singal: 0x17 = 23(%%)
271 -* (% style="color:blue" %)Mod: 0x01 = 1(%%)
272 -* (% 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
273 273  * Leaf moisture: 0x0225= 549 = 54.9%
274 274  * Leaf Temperature:0x010B =267=26.7 °C
275 275  * Time stamp : 0x6315537b =1662342011
276 276  * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
277 -* (% 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,.......
278 278  
279 279  == 2.4  Payload Explanation and Sensor Interface ==
280 280  
281 -=== 2.4.1  Device ID ===
277 +**2.4.1  Device ID**
282 282  
283 283  By default, the Device ID equal to the last 15 bits of IMEI.
284 284  
... ... @@ -290,13 +290,13 @@
290 290  
291 291  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
292 292  
293 -=== 2.4.2  Version Info ===
289 +**2.4.2  Version Info**
294 294  
295 295  Specify the software version: 0x64=100, means firmware version 1.00.
296 296  
297 297  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
298 298  
299 -=== 2.4.3  Battery Info ===
295 +**2.4.3  Battery Info**
300 300  
301 301  Check the battery voltage for NLMS01.
302 302  
... ... @@ -304,7 +304,7 @@
304 304  
305 305  Ex2: 0x0B49 = 2889mV
306 306  
307 -=== 2.4.4  Signal Strength ===
303 +**2.4.4  Signal Strength**
308 308  
309 309  NB-IoT Network signal Strength.
310 310  
... ... @@ -320,7 +320,7 @@
320 320  
321 321  **99**    Not known or not detectable
322 322  
323 -=== 2.4.5  Leaf moisture ===
319 +**2.4.5  Leaf** moisture
324 324  
325 325  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**.
326 326  
... ... @@ -328,7 +328,7 @@
328 328  
329 329  **0229(H) = 549(D) /100 = 54.9.**
330 330  
331 -=== 2.4.6  Leaf Temperature ===
327 +**2.4.6  Leaf Temperature**
332 332  
333 333  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
334 334  
... ... @@ -338,13 +338,13 @@
338 338  
339 339  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
340 340  
341 -=== 2.4.7  Timestamp ===
337 +**2.4.7  Timestamp**
342 342  
343 343  Time stamp : 0x6315537b =1662342011
344 344  
345 345  Convert Unix timestamp to time 2022-9-5 9:40:11.
346 346  
347 -=== 2.4.8  Digital Interrupt ===
343 +**2.4.8  Digital Interrupt**
348 348  
349 349  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.
350 350  
... ... @@ -360,7 +360,7 @@
360 360  
361 361  0x(01): Interrupt Uplink Packet.
362 362  
363 -=== 2.4.9  ​+5V Output ===
359 +**2.4.9  ​+5V Output**
364 364  
365 365  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
366 366  
... ... @@ -467,7 +467,7 @@
467 467  
468 468  == 2.12  ​Battery Analysis ==
469 469  
470 -=== 2.12.1  ​Battery Type ===
466 +**2.12.1  ​Battery Type**
471 471  
472 472  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.
473 473  
... ... @@ -481,7 +481,7 @@
481 481  
482 482  [[image:image-20220907171221-21.png]] ​
483 483  
484 -=== 2.12.2  Power consumption Analyze ===
480 +**2.12.2  Power consumption Analyze**
485 485  
486 486  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.
487 487  
... ... @@ -499,11 +499,11 @@
499 499  
500 500  [[image:image-20220907171221-22.jpeg]] ​
501 501  
502 -=== 2.12.3  ​Battery Note ===
498 +**2.12.3  ​Battery Note**
503 503  
504 504  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.
505 505  
506 -=== 2.12.4  Replace the battery ===
502 +**2.12.4  Replace the battery**
507 507  
508 508  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).
509 509  
... ... @@ -517,7 +517,7 @@
517 517  
518 518  = 4.  Using the AT Commands =
519 519  
520 -== 4.1  Access AT Commands ==
516 +**4.1  Access AT Commands**
521 521  
522 522  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]]
523 523  
... ... @@ -595,7 +595,7 @@
595 595  
596 596  = ​5.  FAQ =
597 597  
598 -== 5.1 ​ How to Upgrade Firmware ==
594 +**5.1 ​ How to Upgrade Firmware**
599 599  
600 600  User can upgrade the firmware for 1) bug fix, 2) new feature release.
601 601  
... ... @@ -605,11 +605,11 @@
605 605  
606 606  = 6.  Trouble Shooting =
607 607  
608 -== 6.1  ​Connection problem when uploading firmware ==
604 +**6.1  ​Connection problem when uploading firmware**
609 609  
610 610  **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]]
611 611  
612 -== 6.2  AT Command input doesn't work ==
608 +**6.2  AT Command input doesn't work**
613 613  
614 614  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.
615 615  
... ... @@ -636,3 +636,5 @@
636 636  * 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]]
637 637  
638 638  ​
635 +
636 +

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0