Last modified by Mengting Qiu on 2024/04/02 16:54
<
From version < 33.1 >
edited by Xiaoling
on 2022/09/13 09:07
To version < 33.4 >
edited by Xiaoling
on 2022/09/13 09:41
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -62,7 +62,6 @@
62 62  * Supply Voltage: 2.1v ~~ 3.6v
63 63  * Operating Temperature: -40 ~~ 85°C
64 64  
65 -
66 66  (% style="color:#037691" %)**NB-IoT Spec:**
67 67  
68 68  * - B1 @H-FDD: 2100MHz
... ... @@ -74,11 +74,12 @@
74 74  
75 75  
76 76  
77 -== 1.4 Probe Specification ==
78 78  
77 +== 1.4  Probe Specification ==
79 79  
80 -**Leaf Moisture: percentage of water drop over total leaf surface**
81 81  
80 +(% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface**
81 +
82 82  * Range 0-100%
83 83  * Resolution: 0.1%
84 84  * Accuracy: ±3%（0-50%）；±6%（>50%）
... ... @@ -85,8 +85,10 @@
85 85  * IP67 Protection
86 86  * Length: 3.5 meters
87 87  
88 -**Leaf Temperature:**
89 89  
89 +
90 +(% style="color:#037691" %)**Leaf Temperature:**
91 +
90 90  * Range -50℃～80℃
91 91  * Resolution: 0.1℃
92 92  * Accuracy: <±0.5℃(-10℃～70℃)，<±1.0℃ (others)
... ... @@ -93,30 +93,46 @@
93 93  * IP67 Protection
94 94  * Length: 3.5 meters
95 95  
96 -== 1.5 ​Applications ==
97 97  
99 +
100 +
101 +== 1.5 ​ Applications ==
102 +
103 +
98 98  * Smart Agriculture
99 99  
100 -== 1.6 Pin mapping and power on ==
101 101  
107 +
108 +
109 +== 1.6  Pin mapping and power on ==
110 +
111 +
102 102  ​[[image:image-20220907171221-4.png]]
103 103  
104 104  **~ **
105 105  
116 +
106 106  = 2.  Use NLMS01 to communicate with IoT Server =
107 107  
119 +
108 108  == 2.1  How it works ==
109 109  
122 +
110 110  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.
111 111  
112 112  The diagram below shows the working flow in default firmware of NLMS01:
113 113  
127 +
114 114  [[image:image-20220907171221-5.png]]
115 115  
130 +
131 +
116 116  == 2.2 ​ Configure the NLMS01 ==
117 117  
134 +
118 118  === 2.2.1 Test Requirement ===
119 119  
137 +
120 120  To use NLMS01 in your city, make sure meet below requirements:
121 121  
122 122  * Your local operator has already distributed a NB-IoT Network there.
... ... @@ -123,90 +123,118 @@
123 123  * The local NB-IoT network used the band that NLMS01 supports.
124 124  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
125 125  
126 -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
144 +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
127 127  
146 +
128 128  [[image:image-20220907171221-6.png]] ​
129 129  
149 +
150 +
130 130  === 2.2.2 Insert SIM card ===
131 131  
153 +
132 132  Insert the NB-IoT Card get from your provider.
133 133  
134 134  User need to take out the NB-IoT module and insert the SIM card like below:
135 135  
158 +
136 136  [[image:image-20220907171221-7.png]] ​
137 137  
161 +
162 +
138 138  === 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
139 139  
140 -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.
141 141  
142 -**Connection:**
166 +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.
143 143  
144 - USB TTL GND <~-~-~-~-> GND
145 145  
146 - USB TTL TXD <~-~-~-~-> UART_RXD
169 +(% style="color:blue" %)**Connection:**
147 147  
148 - USB TTL RXD <~-~-~-~-> UART_TXD
171 +**~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)**
149 149  
173 +**~ (% style="background-color:yellow" %)USB TTL TXD  <~-~-~-~-> UART_RXD(%%)**
174 +
175 +**~ (% style="background-color:yellow" %)USB TTL RXD  <~-~-~-~-> UART_TXD(%%)**
176 +
177 +
150 150  In the PC, use below serial tool settings:
151 151  
152 -* Baud:  **9600**
153 -* Data bits:** 8**
154 -* Stop bits: **1**
155 -* Parity:  **None**
156 -* Flow Control: **None**
180 +* Baud:  (% style="color:green" %)**9600**
181 +* Data bits:**  (% style="color:green" %)8(%%)**
182 +* Stop bits:  (% style="color:green" %)**1**
183 +* Parity:  (% style="color:green" %)**None**
184 +* Flow Control: (% style="color:green" %)**None**
157 157  
158 -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.
186 +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.
159 159  
160 -​[[image:image-20220907171221-8.png]]
188 +​[[image:image-20220913090720-1.png]]
161 161  
162 -**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]]
163 163  
191 +(% 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]]
192 +
193 +
194 +
164 164  === 2.2.4 Use CoAP protocol to uplink data ===
165 165  
166 -**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/]]
167 167  
168 -**Use below commands:**
198 +(% 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/]]
169 169  
170 -* **AT+PRO=1**   ~/~/ Set to use CoAP protocol to uplink
171 -* **AT+SERVADDR=120.24.4.116,5683   ** ~/~/ to set CoAP server address and port
172 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** ~/~/Set COAP resource path
173 173  
201 +(% style="color:blue" %)**Use below commands:**
202 +
203 +* (% style="color:#037691" %)**AT+PRO=1**          (%%) ~/~/  Set to use CoAP protocol to uplink
204 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
205 +* (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
206 +
174 174  For parameter description, please refer to AT command set
175 175  
176 176  [[image:image-20220907171221-9.png]]
177 177  
178 -After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server.
179 179  
212 +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.
213 +
180 180  [[image:image-20220907171221-10.png]] ​
181 181  
216 +
217 +
182 182  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
183 183  
220 +
184 184  This feature is supported since firmware version v1.0.1
185 185  
186 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
187 -* **AT+SERVADDR=120.24.4.116,5601   ** ~/~/ to set UDP server address and port
188 -* **AT+CFM=1       ** ~/~/If the server does not respond, this command is unnecessary
223 +* (% style="color:#037691" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
224 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5601     ** (%%) ~/~/  to set UDP server address and port
225 +* (% style="color:#037691" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
189 189  
227 +
228 +
190 190  ​ [[image:image-20220907171221-11.png]]
191 191  
231 +
192 192  [[image:image-20220907171221-12.png]]
193 193  
194 194  ​
195 195  
236 +
196 196  === 2.2.6 Use MQTT protocol to uplink data ===
197 197  
239 +
198 198  This feature is supported since firmware version v110
199 199  
200 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
201 -* **AT+SERVADDR=120.24.4.116,1883   ** ~/~/Set MQTT server address and port
202 -* **AT+CLIENT=CLIENT       ** ~/~/Set up the CLIENT of MQTT
203 -* **AT+UNAME=UNAME                               **~/~/Set the username of MQTT
204 -* **AT+PWD=PWD                                        **~/~/Set the password of MQTT
205 -* **AT+PUBTOPIC=PUB                    **~/~/Set the sending topic of MQTT
206 -* **AT+SUBTOPIC=SUB          ** ~/~/Set the subscription topic of MQTT
242 +* (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
243 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
244 +* (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
245 +* (% style="color:#037691" %)**AT+UNAME=UNAME                        **(%%)** **~/~/  Set the username of MQTT
246 +* (% style="color:#037691" %)**AT+PWD=PWD                            **(%%)** **~/~/  Set the password of MQTT
247 +* (% style="color:#037691" %)**AT+PUBTOPIC=PUB                    ** (%%) ~/~/  Set the sending topic of MQTT
248 +* (% style="color:#037691" %)**AT+SUBTOPIC=SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
207 207  
250 +
251 +
208 208  ​ [[image:image-20220907171221-13.png]]
209 209  
254 +
255 +
210 210  [[image:image-20220907171221-14.png]]
211 211  
212 212  ​
... ... @@ -213,41 +213,58 @@
213 213  
214 214  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.
215 215  
262 +
263 +
216 216  === 2.2.7 Use TCP protocol to uplink data ===
217 217  
266 +
218 218  This feature is supported since firmware version v110
219 219  
220 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
221 -* **AT+SERVADDR=120.24.4.116,5600   ** ~/~/ to set TCP server address and port
269 +* (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
270 +* (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  to set TCP server address and port
222 222  
272 +
273 +
223 223  ​ [[image:image-20220907171221-15.png]]
224 224  
276 +
277 +
225 225  [[image:image-20220907171221-16.png]]
226 226  
227 227  ​
228 228  
282 +
229 229  === 2.2.8 Change Update Interval ===
230 230  
285 +
231 231  User can use below command to change the **uplink interval**.
232 232  
233 -* **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hour)
288 +* (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
234 234  
235 -**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).**
236 236  
237 237  
292 +(% 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).**
293 +
294 +
295 +
238 238  == 2.3  Uplink Payload ==
239 239  
298 +
240 240  In this mode, uplink payload includes 87 bytes in total by default.
241 241  
242 242  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.
243 243  
244 -|**Size(bytes)**|**8**|**2**|**2**|1|1|1|2|2|4|2|2|4
245 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Leaf moisture|Leaf Temperature|Time stamp|Leaf Temperature|Leaf moisture|Time stamp  .....
246 246  
304 +(% border="1" style="background-color:#ffffcc; color:green; width:1251px" %)
305 +|(% 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
306 +|(% 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  .....
307 +
247 247  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data.
248 248  
310 +
249 249  [[image:image-20220907171221-17.png]]
250 250  
313 +
251 251  The payload is ASCII string, representative same HEX:
252 252  
253 253  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:
... ... @@ -264,28 +264,40 @@
264 264  * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
265 265  * (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
266 266  
330 +
331 +
332 +
267 267  == 2.4  Payload Explanation and Sensor Interface ==
268 268  
335 +
269 269  === 2.4.1  Device ID ===
270 270  
338 +
271 271  By default, the Device ID equal to the last 15 bits of IMEI.
272 272  
273 -User can use **AT+DEUI** to set Device ID
341 +User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID
274 274  
275 -**Example:**
276 276  
344 +(% style="color:blue" %)**Example**:
345 +
277 277  AT+DEUI=868411056754138
278 278  
279 279  The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
280 280  
350 +
351 +
281 281  === 2.4.2  Version Info ===
282 282  
354 +
283 283  Specify the software version: 0x64=100, means firmware version 1.00.
284 284  
285 285  For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
286 286  
359 +
360 +
287 287  === 2.4.3  Battery Info ===
288 288  
363 +
289 289  Check the battery voltage for NLMS01.
290 290  
291 291  Ex1: 0x0B45 = 2885mV
... ... @@ -292,12 +292,16 @@
292 292  
293 293  Ex2: 0x0B49 = 2889mV
294 294  
370 +
371 +
295 295  === 2.4.4  Signal Strength ===
296 296  
374 +
297 297  NB-IoT Network signal Strength.
298 298  
299 -**Ex1: 0x1d = 29**
300 300  
378 +(% style="color:blue" %)**Ex1: 0x1d = 29**
379 +
301 301  **0**  -113dBm or less
302 302  
303 303  **1**  -111dBm
... ... @@ -308,37 +308,49 @@
308 308  
309 309  **99**    Not known or not detectable
310 310  
390 +
391 +
311 311  === 2.4.5  Leaf moisture ===
312 312  
313 -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**.
314 314  
315 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is
395 +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.
316 316  
317 -**0229(H) = 549(D) /100 = 54.9.**
397 +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
318 318  
399 +(% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**
400 +
401 +
402 +
319 319  === 2.4.6  Leaf Temperature ===
320 320  
321 -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
322 322  
323 -**Example**:
406 +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
324 324  
325 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
408 +(% style="color:blue" %)**Example**:
326 326  
327 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
410 +If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
328 328  
412 +If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
413 +
414 +
415 +
329 329  === 2.4.7  Timestamp ===
330 330  
418 +
331 331  Time stamp : 0x6315537b =1662342011
332 332  
333 333  Convert Unix timestamp to time 2022-9-5 9:40:11.
334 334  
423 +
424 +
335 335  === 2.4.8  Digital Interrupt ===
336 336  
337 -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.
338 338  
428 +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.
429 +
339 339  The command is:
340 340  
341 -**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]])**.**
432 +(% 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]])**.**
342 342  
343 343  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.
344 344  
... ... @@ -348,27 +348,34 @@
348 348  
349 349  0x(01): Interrupt Uplink Packet.
350 350  
442 +
443 +
351 351  === 2.4.9  ​+5V Output ===
352 352  
446 +
353 353  NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
354 354  
355 355  The 5V output time can be controlled by AT Command.
356 356  
357 -**AT+5VT=1000**
451 +(% style="color:blue" %)**AT+5VT=1000**
358 358  
359 359  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
360 360  
361 361  
456 +
362 362  == 2.5  Downlink Payload ==
363 363  
459 +
364 364  By default, NLMS01 prints the downlink payload to console port.
365 365  
366 366  [[image:image-20220907171221-18.png]] ​
367 367  
368 -**Examples:**
369 369  
370 -* **Set TDC**
465 +(% style="color:blue" %)**Examples:**
371 371  
467 +
468 +* (% style="color:#037691" %)**Set TDC**
469 +
372 372  If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
373 373  
374 374  Payload:    01 00 00 1E    TDC=30S
... ... @@ -375,16 +375,23 @@
375 375  
376 376  Payload:    01 00 00 3C    TDC=60S
377 377  
378 -* **Reset**
379 379  
477 +
478 +* (% style="color:#037691" %)**Reset**
479 +
380 380  If payload = 0x04FF, it will reset the NLMS01
381 381  
382 -* **INTMOD**
383 383  
483 +
484 +* (% style="color:#037691" %)**INTMOD**
485 +
384 384  Downlink Payload: 06000003, Set AT+INTMOD=3
385 385  
488 +
489 +
386 386  == 2.6  ​LED Indicator ==
387 387  
492 +
388 388  The NLMS01 has an internal LED which is to show the status of different state.
389 389  
390 390  * 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)
... ... @@ -392,18 +392,26 @@
392 392  * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
393 393  * For each uplink probe, LED will be on for 500ms.
394 394  
395 -== 2.7 Installation ==
396 396  
501 +
502 +
503 +== 2.7  Installation ==
504 +
505 +
397 397  NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
398 398  
508 +
399 399  [[image:image-20220907171221-19.png]]
400 400  
401 -== 2.8 Moisture and Temperature alarm function ==
402 402  
403 -➢ AT Command:
404 404  
405 -AT+ HUMALARM =min,max
513 +== 2.8  Moisture and Temperature alarm function ==
406 406  
515 +
516 +(% style="color:blue" %)**➢ AT Command:**
517 +
518 +(% style="color:#037691" %)**AT+ HUMALARM =min,max**
519 +
407 407  ² When min=0, and max≠0, Alarm higher than max
408 408  
409 409  ² When min≠0, and max=0, Alarm lower than min
... ... @@ -410,8 +410,9 @@
410 410  
411 411  ² When min≠0 and max≠0, Alarm higher than max or lower than min
412 412  
413 -Example:
414 414  
527 +(% style="color:blue" %)**Example:**
528 +
415 415  AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
416 416  
417 417  AT+ TEMPALARM=min,max
... ... @@ -422,41 +422,53 @@
422 422  
423 423  ² When min≠0 and max≠0, Alarm higher than max or lower than min
424 424  
425 -Example:
426 426  
540 +(% style="color:blue" %)**Example:**
541 +
427 427  AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
428 428  
429 429  
430 -== 2.9 Set the number of data to be uploaded and the recording time ==
431 431  
432 -➢ AT Command:
546 +== 2.9  Set the number of data to be uploaded and the recording time ==
433 433  
434 -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)
435 435  
436 -AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
549 +(% style="color:blue" %)**➢ AT Command:**
437 437  
438 -== 2.10 Read or Clear cached data ==
551 +* (% 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)
552 +* (% 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.
439 439  
440 -➢ AT Command:
441 441  
442 -AT+CDP    ~/~/ Read cached data
443 443  
444 -[[image:image-20220907171221-20.png]]
445 445  
557 +== 2.10  Read or Clear cached data ==
446 446  
447 -AT+CDP=0    ~/~/ Clear cached data
448 448  
560 +(% style="color:blue" %)**➢ AT Command:**
449 449  
562 +* (% style="color:#037691" %)**AT+CDP**      (%%) ~/~/  Read cached data
563 +* (% style="color:#037691" %)**AT+CDP=0  ** (%%) ~/~/  Clear cached data
564 +
565 +
566 +
567 +[[image:image-20220907171221-20.png]]
568 +
569 +
570 +
450 450  == 2.11  ​Firmware Change Log ==
451 451  
573 +
452 452  Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
453 453  
454 454  Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
455 455  
578 +
579 +
456 456  == 2.12  ​Battery Analysis ==
457 457  
582 +
458 458  === 2.12.1  ​Battery Type ===
459 459  
585 +
460 460  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.
461 461  
462 462  The battery is designed to last for several years depends on the actually use environment and update interval. 
... ... @@ -469,15 +469,18 @@
469 469  
470 470  [[image:image-20220907171221-21.png]] ​
471 471  
598 +
599 +
472 472  === 2.12.2  Power consumption Analyze ===
473 473  
602 +
474 474  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.
475 475  
476 476  Instruction to use as below:
477 477  
478 -**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/]]
607 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
479 479  
480 -**Step 2: ** Open it and choose
609 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
481 481  
482 482  * Product Model
483 483  * Uplink Interval
... ... @@ -487,26 +487,39 @@
487 487  
488 488  [[image:image-20220907171221-22.jpeg]] ​
489 489  
619 +
490 490  === 2.12.3  ​Battery Note ===
491 491  
622 +
492 492  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.
493 493  
625 +
626 +
494 494  === 2.12.4  Replace the battery ===
495 495  
629 +
496 496  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).
497 497  
632 +
633 +
498 498  = 3. ​ Access NB-IoT Module =
499 499  
636 +
500 500  Users can directly access the AT command set of the NB-IoT module.
501 501  
502 502  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/]] 
503 503  
641 +
504 504  [[image:image-20220907171221-23.png]] ​
505 505  
644 +
645 +
506 506  = 4.  Using the AT Commands =
507 507  
648 +
508 508  == 4.1  Access AT Commands ==
509 509  
651 +
510 510  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]]
511 511  
512 512  AT+<CMD>?  : Help on <CMD>
... ... @@ -517,8 +517,9 @@
517 517  
518 518  AT+<CMD>=?  : Get the value
519 519  
520 -**General Commands**      
521 521  
663 +(% style="color:#037691" %)**General Commands**      
664 +
522 522  AT  : Attention       
523 523  
524 524  AT?  : Short Help     
... ... @@ -560,16 +560,18 @@
560 560  AT+HUMALARM     : Get or Set alarm of PH
561 561  
562 562  
563 -**COAP Management**      
706 +(% style="color:#037691" %)**COAP Management**      
564 564  
565 565  AT+URI            : Resource parameters
566 566  
567 -**UDP Management**
568 568  
711 +(% style="color:#037691" %)**UDP Management**
712 +
569 569  AT+CFM          : Upload confirmation mode (only valid for UDP)
570 570  
571 -**MQTT Management**
572 572  
716 +(% style="color:#037691" %)**MQTT Management**
717 +
573 573  AT+CLIENT               : Get or Set MQTT client
574 574  
575 575  AT+UNAME  : Get or Set MQTT Username
... ... @@ -580,43 +580,62 @@
580 580  
581 581  AT+SUBTOPIC  : Get or Set MQTT subscription topic
582 582  
583 -**Information**          
584 584  
729 +(% style="color:#037691" %)**Information**          
730 +
585 585  AT+FDR  : Factory Data Reset
586 586  
587 587  AT+PWORD  : Serial Access Password
588 588  
735 +
736 +
589 589  = ​5.  FAQ =
590 590  
739 +
591 591  == 5.1 ​ How to Upgrade Firmware ==
592 592  
742 +
593 593  User can upgrade the firmware for 1) bug fix, 2) new feature release.
594 594  
595 595  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]]
596 596  
597 -**Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.**
598 598  
748 +(% style="color:red" %)**Notice, NLMS01 and LLMS01 share the same mother board. They use the same connection and method to update.**
749 +
750 +
751 +
599 599  = 6.  Trouble Shooting =
600 600  
754 +
601 601  == 6.1  ​Connection problem when uploading firmware ==
602 602  
757 +
603 603  **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]]
604 604  
760 +
761 +
605 605  == 6.2  AT Command input doesn't work ==
606 606  
607 -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.
608 608  
765 +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.
766 +
767 +
768 +
609 609  = 7. ​ Order Info =
610 610  
771 +
611 611  Part Number**:** NLMS01
612 612  
774 +
775 +
613 613  = 8.  Packing Info =
614 614  
615 -**Package Includes**:
616 616  
779 +(% style="color:#037691" %)**Package Includes:**
780 +
617 617  * NLMS01 NB-IoT Leaf Moisture Sensor x 1
618 618  
619 -**Dimension and weight**:
783 +(% style="color:#037691" %)**Dimension and weight**:
620 620  
621 621  * Device Size: cm
622 622  * Device Weight: g
... ... @@ -623,8 +623,11 @@
623 623  * Package Size / pcs : cm
624 624  * Weight / pcs : g
625 625  
790 +
791 +
626 626  = 9.  Support =
627 627  
794 +
628 628  * 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.
629 629  * 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]]
630 630  

Applications

Navigation

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