Last modified by Mengting Qiu on 2024/04/02 16:54
<
From version < 33.3 >
edited by Xiaoling
on 2022/09/13 09:23
To version < 32.1 >
edited by David Huang
on 2022/09/08 09:49
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -7,62 +7,76 @@
7 7  
8 8  
9 9  
10 -= 1.  Introduction =
10 += 1. Introduction =
11 11  
12 +== 1.1 ​What is NLMS01 Leaf Moisture Sensor ==
12 12  
13 -== 1.1 ​ What is NLMS01 Leaf Moisture Sensor ==
14 14  
15 +The Dragino NLMS01 is a **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.
15 15  
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 +NLMS01 detects leaf's** 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.
17 17  
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 -
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.
20 +\\NLMS01 supports different uplink methods include **TCP,MQTT,UDP and CoAP  **for different application requirement.
21 +\\NLMS01 is powered by  **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)
22 +\\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 **NB-IoT SIM card** from local operator and install NLMS01 to get NB-IoT network connection
24 24  
25 -
26 26  ​[[image:image-20220907171221-2.png]]
27 27  
28 -
29 29  ​ [[image:image-20220907171221-3.png]]
30 30  
28 +== ​1.2 Features ==
31 31  
30 +* (((
31 +NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
32 +)))
33 +* (((
34 +Monitor Leaf moisture
35 +)))
32 32  
33 -== ​1.2  Features ==
37 +* (((
38 + Monitor Leaf temperature
39 +)))
34 34  
35 -
36 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
37 -* Monitor Leaf moisture
38 -* Monitor Leaf temperature
39 -* Moisture and Temperature alarm function
40 -* Monitor Battery Level
41 -* Uplink on periodically
42 -* Downlink to change configure
43 -* IP66 Waterproof Enclosure
44 -* IP67 rate for the Sensor Probe
45 -* Ultra-Low Power consumption
46 -* AT Commands to change parameters
47 -* Micro SIM card slot for NB-IoT SIM
48 -* 8500mAh Battery for long term use
49 -
50 -(((
51 -
52 -
53 -
54 -
41 +* (((
42 +Moisture and Temperature alarm function
55 55  )))
44 +* (((
45 +Monitor Battery Level
46 +)))
47 +* (((
48 +Uplink on periodically
49 +)))
50 +* (((
51 +Downlink to change configure
52 +)))
53 +* (((
54 +IP66 Waterproof Enclosure
55 +)))
56 +* (((
57 +IP67 rate for the Sensor Probe
58 +)))
59 +* (((
60 +Ultra-Low Power consumption
61 +)))
62 +* (((
63 +AT Commands to change parameters
64 +)))
65 +* (((
66 +Micro SIM card slot for NB-IoT SIM
67 +)))
68 +* (((
69 +8500mAh Battery for long term use
70 +)))
56 56  
57 57  == 1.3  Specification ==
58 58  
74 +**Common DC Characteristics:**
59 59  
60 -(% style="color:#037691" %)**Common DC Characteristics:**
61 -
62 62  * Supply Voltage: 2.1v ~~ 3.6v
63 63  * Operating Temperature: -40 ~~ 85°C
64 64  
65 -(% style="color:#037691" %)**NB-IoT Spec:**
79 +**NB-IoT Spec:**
66 66  
67 67  * - B1 @H-FDD: 2100MHz
68 68  * - B3 @H-FDD: 1800MHz
... ... @@ -71,10 +71,10 @@
71 71  * - B20 @H-FDD: 800MHz
72 72  * - B28 @H-FDD: 700MHz
73 73  
74 -== 1.4  Probe Specification ==
88 +== 1.4 Probe Specification ==
75 75  
76 76  
77 -(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface**
91 +**Leaf Moisture: percentage of water drop over total leaf surface**
78 78  
79 79  * Range 0-100%
80 80  * Resolution: 0.1%
... ... @@ -82,7 +82,7 @@
82 82  * IP67 Protection
83 83  * Length: 3.5 meters
84 84  
85 -(% style="color:#037691" %)**Leaf Temperature:**
99 +**Leaf Temperature:**
86 86  
87 87  * Range -50℃～80℃
88 88  * Resolution: 0.1℃
... ... @@ -90,40 +90,30 @@
90 90  * IP67 Protection
91 91  * Length: 3.5 meters
92 92  
93 -== 1.5 ​ Applications ==
107 +== 1.5 ​Applications ==
94 94  
95 -
96 96  * Smart Agriculture
97 97  
98 -== 1.6  Pin mapping and power on ==
111 +== 1.6 Pin mapping and power on ==
99 99  
100 -
101 101  ​[[image:image-20220907171221-4.png]]
102 102  
103 103  **~ **
104 104  
105 -
106 106  = 2.  Use NLMS01 to communicate with IoT Server =
107 107  
108 -
109 109  == 2.1  How it works ==
110 110  
111 -
112 112  The NLMS01 is equipped with a NB-IoT module, the pre-loaded firmware in NLMS01 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NLMS01.
113 113  
114 114  The diagram below shows the working flow in default firmware of NLMS01:
115 115  
116 -
117 117  [[image:image-20220907171221-5.png]]
118 118  
119 -
120 -
121 121  == 2.2 ​ Configure the NLMS01 ==
122 122  
123 -
124 124  === 2.2.1 Test Requirement ===
125 125  
126 -
127 127  To use NLMS01 in your city, make sure meet below requirements:
128 128  
129 129  * Your local operator has already distributed a NB-IoT Network there.
... ... @@ -130,120 +130,90 @@
130 130  * The local NB-IoT network used the band that NLMS01 supports.
131 131  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
132 132  
133 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NLMS01 will use(% style="color:#037691" %)** CoAP(120.24.4.116:5683) **(%%)or raw(% style="color:#037691" %)** UDP(120.24.4.116:5601)** or(%%) (% style="color:#037691" %)**MQTT(120.24.4.116:1883)**(%%)or (% style="color:#037691" %)**TCP(120.24.4.116:5600)**(%%)protocol to send data to the test server
137 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NLMS01 will use CoAP(120.24.4.116:5683) or raw UDP(120.24.4.116:5601) or MQTT(120.24.4.116:1883)or TCP(120.24.4.116:5600)protocol to send data to the test server
134 134  
135 -
136 136  [[image:image-20220907171221-6.png]] ​
137 137  
138 -
139 -
140 140  === 2.2.2 Insert SIM card ===
141 141  
142 -
143 143  Insert the NB-IoT Card get from your provider.
144 144  
145 145  User need to take out the NB-IoT module and insert the SIM card like below:
146 146  
147 -
148 148  [[image:image-20220907171221-7.png]] ​
149 149  
150 -
151 -
152 152  === 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
153 153  
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.
154 154  
155 -User need to configure NLMS01 via serial port to set the (% style="color:#037691" %)**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.
153 +**Connection:**
156 156  
155 + USB TTL GND <~-~-~-~-> GND
157 157  
158 -(% style="color:blue" %)**Connection:**
157 + USB TTL TXD <~-~-~-~-> UART_RXD
159 159  
160 -**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)**
159 + USB TTL RXD <~-~-~-~-> UART_TXD
161 161  
162 -**~ (% style="background-color:yellow" %)USB TTL TXD  <~-~-~-~-> UART_RXD(%%)**
163 -
164 -**~ (% style="background-color:yellow" %)USB TTL RXD  <~-~-~-~-> UART_TXD(%%)**
165 -
166 -
167 167  In the PC, use below serial tool settings:
168 168  
169 -* Baud:  (% style="color:green" %)**9600**
170 -* Data bits:**  (% style="color:green" %)8(%%)**
171 -* Stop bits:  (% style="color:green" %)**1**
172 -* Parity:  (% style="color:green" %)**None**
173 -* Flow Control: (% style="color:green" %)**None**
163 +* Baud:  **9600**
164 +* Data bits:** 8**
165 +* Stop bits: **1**
166 +* Parity:  **None**
167 +* Flow Control: **None**
174 174  
175 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
169 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NLMS01. NLMS01 will output system info once power on as below, we can enter the **password: 12345678** to access AT Command input.
176 176  
177 -​[[image:image-20220913090720-1.png]]
171 +​[[image:image-20220907171221-8.png]]
178 178  
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]]
179 179  
180 -(% 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]]
181 -
182 -
183 -
184 184  === 2.2.4 Use CoAP protocol to uplink data ===
185 185  
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/]]
186 186  
187 -(% style="color:red" %)**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/]]
179 +**Use below commands:**
188 188  
181 +* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
182 +* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
183 +* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
189 189  
190 -(% style="color:blue" %)**Use below commands:**
191 -
192 -* (% style="color:#037691" %)**AT+PRO=1**          (%%) ~/~/  Set to use CoAP protocol to uplink
193 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
194 -* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
195 -
196 -
197 -
198 198  For parameter description, please refer to AT command set
199 199  
200 200  [[image:image-20220907171221-9.png]]
201 201  
189 +After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server.
202 202  
203 -After configure the server address and (% style="color:#037691" %)**reset the device**(%%) (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server.
204 -
205 205  [[image:image-20220907171221-10.png]] ​
206 206  
207 -
208 -
209 209  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
210 210  
211 -
212 212  This feature is supported since firmware version v1.0.1
213 213  
214 -* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
215 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601  ** (%%) ~/~/  to set UDP server address and port
216 -* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
197 +* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
198 +* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
199 +* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
217 217  
218 -
219 -
220 220  ​ [[image:image-20220907171221-11.png]]
221 221  
222 -
223 223  [[image:image-20220907171221-12.png]]
224 224  
225 225  ​
226 226  
227 -
228 228  === 2.2.6 Use MQTT protocol to uplink data ===
229 229  
230 -
231 231  This feature is supported since firmware version v110
232 232  
233 -* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
234 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
235 -* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
236 -* (% style="color:#037691" %)**AT+UNAME=UNAME                        **(%%)** **~/~/  Set the username of MQTT
237 -* (% style="color:#037691" %)**AT+PWD=PWD                            **(%%)** **~/~/  Set the password of MQTT
238 -* (% style="color:#037691" %)**AT+PUBTOPIC=PUB                    ** (%%) ~/~/  Set the sending topic of MQTT
239 -* (% style="color:#037691" %)**AT+SUBTOPIC=SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
211 +* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
212 +* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
213 +* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
214 +* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
215 +* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
216 +* **AT+PUBTOPIC=PUB                    **~/~/Set the sending topic of MQTT
217 +* **AT+SUBTOPIC=SUB          ** ~/~/Set the subscription topic of MQTT
240 240  
241 -
242 -
243 243  ​ [[image:image-20220907171221-13.png]]
244 244  
245 -
246 -
247 247  [[image:image-20220907171221-14.png]]
248 248  
249 249  ​
... ... @@ -250,59 +250,41 @@
250 250  
251 251  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.
252 252  
253 -
254 -
255 255  === 2.2.7 Use TCP protocol to uplink data ===
256 256  
257 -
258 258  This feature is supported since firmware version v110
259 259  
260 -* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
261 -* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  to set TCP server address and port
231 +* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
232 +* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
262 262  
263 -
264 -
265 265  ​ [[image:image-20220907171221-15.png]]
266 266  
267 -
268 -
269 269  [[image:image-20220907171221-16.png]]
270 270  
271 271  ​
272 272  
273 -
274 274  === 2.2.8 Change Update Interval ===
275 275  
276 -
277 277  User can use below command to change the **uplink interval**.
278 278  
279 -* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
244 +* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hour)
280 280  
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).**
281 281  
282 282  
283 -(% 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).**
284 -
285 -
286 -
287 287  == 2.3  Uplink Payload ==
288 288  
289 -
290 290  In this mode, uplink payload includes 87 bytes in total by default.
291 291  
292 292  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.
293 293  
255 +|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
256 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Time stamp|Leaf Temperature|Leaf moisture|Time stamp  .....
294 294  
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  .....
298 -
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 -
303 303  [[image:image-20220907171221-17.png]]
304 304  
305 -
306 306  The payload is ASCII string, representative same HEX:
307 307  
308 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:
... ... @@ -319,21 +319,14 @@
319 319  * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
320 320  * (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
321 321  
322 -
323 -
324 -
325 -
326 326  == 2.4  Payload Explanation and Sensor Interface ==
327 327  
328 -
329 329  === 2.4.1  Device ID ===
330 330  
331 -
332 332  By default, the Device ID equal to the last 15 bits of IMEI.
333 333  
334 334  User can use **AT+DEUI** to set Device ID
335 335  
336 -
337 337  **Example:**
338 338  
339 339  AT+DEUI=868411056754138
... ... @@ -340,20 +340,14 @@
340 340  
341 341  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
342 342  
343 -
344 -
345 345  === 2.4.2  Version Info ===
346 346  
347 -
348 348  Specify the software version: 0x64=100, means firmware version 1.00.
349 349  
350 350  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
351 351  
352 -
353 -
354 354  === 2.4.3  Battery Info ===
355 355  
356 -
357 357  Check the battery voltage for NLMS01.
358 358  
359 359  Ex1: 0x0B45 = 2885mV
... ... @@ -360,11 +360,8 @@
360 360  
361 361  Ex2: 0x0B49 = 2889mV
362 362  
363 -
364 -
365 365  === 2.4.4  Signal Strength ===
366 366  
367 -
368 368  NB-IoT Network signal Strength.
369 369  
370 370  **Ex1: 0x1d = 29**
... ... @@ -379,11 +379,8 @@
379 379  
380 380  **99**    Not known or not detectable
381 381  
382 -
383 -
384 384  === 2.4.5  Leaf moisture ===
385 385  
386 -
387 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**.
388 388  
389 389  For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is
... ... @@ -390,11 +390,8 @@
390 390  
391 391  **0229(H) = 549(D) /100 = 54.9.**
392 392  
393 -
394 -
395 395  === 2.4.6  Leaf Temperature ===
396 396  
397 -
398 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
399 399  
400 400  **Example**:
... ... @@ -403,19 +403,14 @@
403 403  
404 404  If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
405 405  
406 -
407 -
408 408  === 2.4.7  Timestamp ===
409 409  
410 -
411 411  Time stamp : 0x6315537b =1662342011
412 412  
413 413  Convert Unix timestamp to time 2022-9-5 9:40:11.
414 414  
415 -
416 416  === 2.4.8  Digital Interrupt ===
417 417  
418 -
419 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.
420 420  
421 421  The command is:
... ... @@ -430,11 +430,8 @@
430 430  
431 431  0x(01): Interrupt Uplink Packet.
432 432  
433 -
434 -
435 435  === 2.4.9  ​+5V Output ===
436 436  
437 -
438 438  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
439 439  
440 440  The 5V output time can be controlled by AT Command.
... ... @@ -444,15 +444,12 @@
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 -
451 451  By default, NLMS01 prints the downlink payload to console port.
452 452  
453 453  [[image:image-20220907171221-18.png]] ​
454 454  
455 -
456 456  **Examples:**
457 457  
458 458  * **Set TDC**
... ... @@ -471,11 +471,8 @@
471 471  
472 472  Downlink Payload: 06000003, Set AT+INTMOD=3
473 473  
474 -
475 -
476 476  == 2.6  ​LED Indicator ==
477 477  
478 -
479 479  The NLMS01 has an internal LED which is to show the status of different state.
480 480  
481 481  * 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)
... ... @@ -483,26 +483,18 @@
483 483  * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
484 484  * For each uplink probe, LED will be on for 500ms.
485 485  
406 +== 2.7 Installation ==
486 486  
487 -
488 -
489 -== 2.7  Installation ==
490 -
491 -
492 492  NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
493 493  
494 -
495 495  [[image:image-20220907171221-19.png]]
496 496  
412 +== 2.8 Moisture and Temperature alarm function ==
497 497  
414 +➢ AT Command:
498 498  
499 -== 2.8  Moisture and Temperature alarm function ==
416 +AT+ HUMALARM =min,max
500 500  
501 -
502 -**➢ AT Command:**
503 -
504 -**AT+ HUMALARM =min,max**
505 -
506 506  ² When min=0, and max≠0, Alarm higher than max
507 507  
508 508  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -509,9 +509,8 @@
509 509  
510 510  ² When min≠0 and max≠0, Alarm higher than max or lower than min
511 511  
424 +Example:
512 512  
513 -**Example:**
514 -
515 515  AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
516 516  
517 517  AT+ TEMPALARM=min,max
... ... @@ -522,53 +522,41 @@
522 522  
523 523  ² When min≠0 and max≠0, Alarm higher than max or lower than min
524 524  
436 +Example:
525 525  
526 -**Example:**
527 -
528 528  AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
529 529  
530 530  
441 +== 2.9 Set the number of data to be uploaded and the recording time ==
531 531  
532 -== 2.9  Set the number of data to be uploaded and the recording time ==
443 +➢ AT Command:
533 533  
445 +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)
534 534  
535 -**➢ AT Command:**
447 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
536 536  
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)
449 +== 2.10 Read or Clear cached data ==
538 538  
539 -**AT+NOUD=8**  ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
451 +➢ AT Command:
540 540  
453 +AT+CDP    ~/~/ Read cached data
541 541  
542 -
543 -== 2.10  Read or Clear cached data ==
544 -
545 -
546 -**➢ AT Command:**
547 -
548 -**AT+CDP**  ~/~/  Read cached data
549 -
550 -**AT+CDP=0  ** ~/~/  Clear cached data
551 -
552 -
553 553  [[image:image-20220907171221-20.png]]
554 554  
555 555  
458 +AT+CDP=0    ~/~/ Clear cached data
556 556  
460 +
557 557  == 2.11  ​Firmware Change Log ==
558 558  
559 -
560 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]]
561 561  
562 562  Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
563 563  
564 -
565 -
566 566  == 2.12  ​Battery Analysis ==
567 567  
568 -
569 569  === 2.12.1  ​Battery Type ===
570 570  
571 -
572 572  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.
573 573  
574 574  The battery is designed to last for several years depends on the actually use environment and update interval. 
... ... @@ -581,11 +581,8 @@
581 581  
582 582  [[image:image-20220907171221-21.png]] ​
583 583  
584 -
585 -
586 586  === 2.12.2  Power consumption Analyze ===
587 587  
588 -
589 589  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.
590 590  
591 591  Instruction to use as below:
... ... @@ -602,39 +602,26 @@
602 602  
603 603  [[image:image-20220907171221-22.jpeg]] ​
604 604  
605 -
606 606  === 2.12.3  ​Battery Note ===
607 607  
608 -
609 609  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.
610 610  
611 -
612 -
613 613  === 2.12.4  Replace the battery ===
614 614  
615 -
616 616  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).
617 617  
618 -
619 -
620 620  = 3. ​ Access NB-IoT Module =
621 621  
622 -
623 623  Users can directly access the AT command set of the NB-IoT module.
624 624  
625 625  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/]] 
626 626  
627 -
628 628  [[image:image-20220907171221-23.png]] ​
629 629  
630 -
631 -
632 632  = 4.  Using the AT Commands =
633 633  
634 -
635 635  == 4.1  Access AT Commands ==
636 636  
637 -
638 638  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]]
639 639  
640 640  AT+<CMD>?  : Help on <CMD>
... ... @@ -645,7 +645,6 @@
645 645  
646 646  AT+<CMD>=?  : Get the value
647 647  
648 -
649 649  **General Commands**      
650 650  
651 651  AT  : Attention       
... ... @@ -693,12 +693,10 @@
693 693  
694 694  AT+URI            : Resource parameters
695 695  
696 -
697 697  **UDP Management**
698 698  
699 699  AT+CFM          : Upload confirmation mode (only valid for UDP)
700 700  
701 -
702 702  **MQTT Management**
703 703  
704 704  AT+CLIENT               : Get or Set MQTT client
... ... @@ -711,7 +711,6 @@
711 711  
712 712  AT+SUBTOPIC  : Get or Set MQTT subscription topic
713 713  
714 -
715 715  **Information**          
716 716  
717 717  AT+FDR  : Factory Data Reset
... ... @@ -718,49 +718,32 @@
718 718  
719 719  AT+PWORD  : Serial Access Password
720 720  
721 -
722 -
723 723  = ​5.  FAQ =
724 724  
725 -
726 726  == 5.1 ​ How to Upgrade Firmware ==
727 727  
728 -
729 729  User can upgrade the firmware for 1) bug fix, 2) new feature release.
730 730  
731 731  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]]
732 732  
733 -**Notice, NLMS01** **and LLMS01** **share the same mother board. They use the same connection and method to update.**
608 +**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.**
734 734  
735 -
736 -
737 737  = 6.  Trouble Shooting =
738 738  
739 -
740 740  == 6.1  ​Connection problem when uploading firmware ==
741 741  
742 -
743 743  **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]]
744 744  
745 -
746 -
747 747  == 6.2  AT Command input doesn't work ==
748 748  
749 -
750 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.
751 751  
752 -
753 -
754 754  = 7. ​ Order Info =
755 755  
756 -
757 757  Part Number**:** NLMS01
758 758  
759 -
760 -
761 761  = 8.  Packing Info =
762 762  
763 -
764 764  **Package Includes**:
765 765  
766 766  * NLMS01 NB-IoT Leaf Moisture Sensor x 1
... ... @@ -772,12 +772,8 @@
772 772  * Package Size / pcs : cm
773 773  * Weight / pcs : g
774 774  
775 -
776 -
777 -
778 778  = 9.  Support =
779 779  
780 -
781 781  * 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.
782 782  * 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]]
783 783  
image-20220913090720-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -224.9 KB
Content

Applications

Navigation

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