Skip to Content
Version 38.13 by Xiaoling on 2023/04/04 09:49
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20220907171221-1.jpeg]]
3
4 ​
5
6 {{toc/}}
7
8
9
10 = 1.  Introduction =
11
12
13 == 1.1 ​ What is NLMS01 Leaf Moisture Sensor ==
14
15
16 (((
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
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
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.
22
23 NLMS01 supports different uplink methods include (% style="color:blue" %)**TCP,MQTT,UDP and CoAP  **(%%)for different application requirement.
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 ​[[image:image-20220907171221-2.png]]
32
33
34 ​ [[image:image-20220907171221-3.png]]
35
36
37 == ​1.2  Features ==
38
39
40 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
41 * Monitor Leaf moisture
42 * Monitor Leaf temperature
43 * Moisture and Temperature alarm function
44 * Monitor Battery Level
45 * Uplink on periodically
46 * Downlink to change configure
47 * IP66 Waterproof Enclosure
48 * IP67 rate for the Sensor Probe
49 * Ultra-Low Power consumption
50 * AT Commands to change parameters
51 * Micro SIM card slot for NB-IoT SIM
52 * 8500mAh Battery for long term use
53
54 (((
55
56
57
58 )))
59
60 == 1.3  Specification ==
61
62
63 (% style="color:#037691" %)**Common DC Characteristics:**
64
65 * Supply Voltage: 2.1v ~~ 3.6v
66 * Operating Temperature: -40 ~~ 85°C
67
68 (% style="color:#037691" %)**NB-IoT Spec:**
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
76
77
78
79 == 1.4  Probe Specification ==
80
81
82 (% style="color:#037691" %)**Leaf Moisture: percentage of water drop over total leaf surface**
83
84 * Range 0-100%
85 * Resolution: 0.1%
86 * Accuracy: ±3%（0-50%）；±6%（>50%）
87 * IP67 Protection
88 * Length: 3.5 meters
89
90 (% style="color:#037691" %)**Leaf Temperature:**
91
92 * Range -50℃～80℃
93 * Resolution: 0.1℃
94 * Accuracy: <±0.5℃(-10℃～70℃)，<±1.0℃ (others)
95 * IP67 Protection
96 * Length: 3.5 meters
97
98
99
100 == 1.5 ​ Applications ==
101
102
103 * Smart Agriculture
104
105
106
107 == 1.6  Pin mapping and power on ==
108
109
110 ​[[image:image-20220907171221-4.png]]
111
112 **~ **
113
114 = 2.  Use NLMS01 to communicate with IoT Server =
115
116 == 2.1  How it works ==
117
118
119 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.
120
121 The diagram below shows the working flow in default firmware of NLMS01:
122
123
124 [[image:image-20220907171221-5.png]]
125
126
127 == 2.2 ​ Configure the NLMS01 ==
128
129 === 2.2.1 Test Requirement ===
130
131
132 To use NLMS01 in your city, make sure meet below requirements:
133
134 * Your local operator has already distributed a NB-IoT Network there.
135 * The local NB-IoT network used the band that NLMS01 supports.
136 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137
138 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
139
140
141 [[image:image-20220907171221-6.png]] ​
142
143
144 === 2.2.2 Insert SIM card ===
145
146
147 Insert the NB-IoT Card get from your provider.
148
149 User need to take out the NB-IoT module and insert the SIM card like below:
150
151
152 [[image:image-20220907171221-7.png]] ​
153
154
155 === 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
156
157
158 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.
159
160
161 (% style="color:blue" %)**Connection:**
162
163 **~ (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND(%%)**
164
165 **~ (% style="background-color:yellow" %)USB TTL TXD  <~-~-~-~-> UART_RXD(%%)**
166
167 **~ (% style="background-color:yellow" %)USB TTL RXD  <~-~-~-~-> UART_TXD(%%)**
168
169
170 In the PC, use below serial tool settings:
171
172 * Baud:  (% style="color:green" %)**9600**
173 * Data bits:**  (% style="color:green" %)8(%%)**
174 * Stop bits:  (% style="color:green" %)**1**
175 * Parity:  (% style="color:green" %)**None**
176 * Flow Control: (% style="color:green" %)**None**
177
178 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.
179
180 ​[[image:image-20220913090720-1.png]]
181
182
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
185
186 === 2.2.4 Use CoAP protocol to uplink data ===
187
188
189 (% 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/]]
190
191
192 (% style="color:blue" %)**Use below commands:**
193
194 * (% style="color:#037691" %)**AT+PRO=1**          (%%) ~/~/  Set to use CoAP protocol to uplink
195 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%) ~/~/  to set CoAP server address and port
196 * (% style="color:#037691" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
197
198 For parameter description, please refer to AT command set
199
200 [[image:image-20220907171221-9.png]]
201
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 [[image:image-20220907171221-10.png]] ​
206
207
208 === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
209
210
211 This feature is supported since firmware version v1.0.1
212
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+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
216
217 ​ [[image:image-20220907171221-11.png]]
218
219
220 [[image:image-20220907171221-12.png]]
221
222 ​
223
224 === 2.2.6 Use MQTT protocol to uplink data ===
225
226
227 This feature is supported since firmware version v110
228
229 * (% style="color:#037691" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
230 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
231 * (% style="color:#037691" %)**AT+CLIENT=CLIENT       ** (%%) ~/~/  Set up the CLIENT of MQTT
232 * (% style="color:#037691" %)**AT+UNAME=UNAME                        **(%%)** **~/~/  Set the username of MQTT
233 * (% style="color:#037691" %)**AT+PWD=PWD                            **(%%)** **~/~/  Set the password of MQTT
234 * (% style="color:#037691" %)**AT+PUBTOPIC=PUB                    ** (%%) ~/~/  Set the sending topic of MQTT
235 * (% style="color:#037691" %)**AT+SUBTOPIC=SUB          ** (%%) ~/~/  Set the subscription topic of MQTT
236
237 ​ [[image:image-20220907171221-13.png]]
238
239
240
241 [[image:image-20220907171221-14.png]]
242
243 ​
244
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
247
248 === 2.2.7 Use TCP protocol to uplink data ===
249
250
251 This feature is supported since firmware version v110
252
253 * (% style="color:#037691" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
254 * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600   ** (%%) ~/~/  to set TCP server address and port
255
256 ​ [[image:image-20220907171221-15.png]]
257
258
259
260 [[image:image-20220907171221-16.png]]
261
262 ​
263
264
265 === 2.2.8 Change Update Interval ===
266
267
268 User can use below command to change the **uplink interval**.
269
270 * (% style="color:#037691" %)**AT+TDC=7200      ** (%%) ~/~/ Set Update Interval to 7200s (2 hour)
271
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
274
275 == 2.3  Uplink Payload ==
276
277
278 In this mode, uplink payload includes 87 bytes in total by default.
279
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
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  .....
286
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
289
290 [[image:image-20220907171221-17.png]]
291
292
293 The payload is ASCII string, representative same HEX:
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__//(%%)**
296
297 where:
298
299 * (% style="color:#037691" %)**Device ID:**(%%) 0xf868411056754138 = f868411056754138
300
301 * (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0
302
303 * (% style="color:#037691" %)**BAT:**       (%%)0x0c78 = 3192 mV = 3.192V
304
305 * (% style="color:#037691" %)**Singal:**(%%)  0x17 = 23
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 == 2.4  Payload Explanation and Sensor Interface ==
324
325 === 2.4.1  Device ID ===
326
327
328 By default, the Device ID equal to the last 15 bits of IMEI.
329
330 User can use (% style="color:#037691" %)**AT+DEUI**(%%) to set Device ID
331
332
333 (% style="color:blue" %)**Example**:
334
335 AT+DEUI=868411056754138
336
337 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
338
339
340 === 2.4.2  Version Info ===
341
342
343 Specify the software version: 0x64=100, means firmware version 1.00.
344
345 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
346
347
348 === 2.4.3  Battery Info ===
349
350
351 Check the battery voltage for NLMS01.
352
353 Ex1: 0x0B45 = 2885mV
354
355 Ex2: 0x0B49 = 2889mV
356
357
358 === 2.4.4  Signal Strength ===
359
360
361 NB-IoT Network signal Strength.
362
363
364 (% style="color:blue" %)**Ex1: 0x1d = 29**
365
366 **0**  -113dBm or less
367
368 **1**  -111dBm
369
370 **2...30** -109dBm... -53dBm
371
372 **31**   -51dBm or greater
373
374 **99**    Not known or not detectable
375
376
377 === 2.4.5  Leaf moisture ===
378
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.
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
383
384 (% style="color:blue" %)**0229(H) = 549(D) /100 = 54.9.**
385
386
387 === 2.4.6  Leaf Temperature ===
388
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
391
392 (% style="color:blue" %)**Example**:
393
394 If payload is **0105H**: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
395
396 If payload is **FF7EH**: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
397
398
399 === 2.4.7  Timestamp ===
400
401
402 Time stamp : 0x6315537b =1662342011
403
404 Convert Unix timestamp to time 2022-9-5 9:40:11.
405
406
407 === 2.4.8  Digital Interrupt ===
408
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 The command is:
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]])**.**
415
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
418 Example:
419
420 0x(00): Normal uplink packet.
421
422 0x(01): Interrupt Uplink Packet.
423
424
425 === 2.4.9  ​+5V Output ===
426
427
428 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
429
430 The 5V output time can be controlled by AT Command.
431
432 (% style="color:blue" %)**AT+5VT=1000**
433
434 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
435
436
437 == 2.5  Downlink Payload ==
438
439
440 By default, NLMS01 prints the downlink payload to console port.
441
442 [[image:image-20220907171221-18.png]] ​
443
444
445 (% style="color:blue" %)**Examples:**
446
447
448 * (% style="color:#037691" %)**Set TDC**
449
450 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
451
452 Payload:    01 00 00 1E    TDC=30S
453
454 Payload:    01 00 00 3C    TDC=60S
455
456
457
458 * (% style="color:#037691" %)**Reset**
459
460 If payload = 0x04FF, it will reset the NLMS01
461
462
463
464 * (% style="color:#037691" %)**INTMOD**
465
466 Downlink Payload: 06000003, Set AT+INTMOD=3
467
468
469 == 2.6  ​LED Indicator ==
470
471
472 The NLMS01 has an internal LED which is to show the status of different state.
473
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)
475 * Then the LED will be on for 1 second means device is boot normally.
476 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
477 * For each uplink probe, LED will be on for 500ms.
478
479
480
481 == 2.7  Installation ==
482
483
484 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
485
486
487 [[image:image-20220907171221-19.png]]
488
489
490 == 2.8  Moisture and Temperature alarm function ==
491
492
493 (% style="color:blue" %)**➢ AT Command:**
494
495 (% style="color:#037691" %)**AT+ HUMALARM =min,max**
496
497 ² When min=0, and max≠0, Alarm higher than max
498
499 ² When min≠0, and max=0, Alarm lower than min
500
501 ² When min≠0 and max≠0, Alarm higher than max or lower than min
502
503
504 (% style="color:blue" %)**Example:**
505
506 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
507
508 AT+ TEMPALARM=min,max
509
510 ² When min=0, and max≠0, Alarm higher than max
511
512 ² When min≠0, and max=0, Alarm lower than min
513
514 ² When min≠0 and max≠0, Alarm higher than max or lower than min
515
516
517 (% style="color:blue" %)**Example:**
518
519 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
520
521
522 == 2.9  Set the number of data to be uploaded and the recording time ==
523
524
525 (% style="color:blue" %)**➢ AT Command:**
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.
529
530 The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
531
532 [[image:image-20221009001002-1.png||height="706" width="982"]]
533
534
535 == 2.10  Read or Clear cached data ==
536
537
538 (% style="color:blue" %)**➢ AT Command:**
539
540 * (% style="color:#037691" %)**AT+CDP**      (%%) ~/~/  Read cached data
541 * (% style="color:#037691" %)**AT+CDP=0  ** (%%) ~/~/  Clear cached data
542
543 [[image:image-20220907171221-20.png]]
544
545
546 == 2.11  ​Firmware Change Log ==
547
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]]
550
551 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
552
553
554 == 2.12 Battery & Power Consumption ==
555
556
557 NLMS01 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
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/]] .
560
561
562 = 3. ​ Access NB-IoT Module =
563
564
565 Users can directly access the AT command set of the NB-IoT module.
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/]] 
568
569
570 [[image:image-20220907171221-23.png]] ​
571
572
573 = 4.  Using the AT Commands =
574
575 == 4.1  Access AT Commands ==
576
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]]
579
580 AT+<CMD>?  :  Help on <CMD>
581
582 AT+<CMD>  :  Run <CMD>
583
584 AT+<CMD>=<value>:  Set the value
585
586 AT+<CMD>=?  :  Get the value
587
588
589 (% style="color:#037691" %)**General Commands**      
590
591 AT  :  Attention       
592
593 AT?  :  Short Help     
594
595 ATZ  :  MCU Reset    
596
597 AT+TDC  :  Application Data Transmission Interval
598
599 AT+CFG  :  Print all configurations
600
601 AT+CFGMOD  :  Working mode selection
602
603 AT+INTMOD  :  Set the trigger interrupt mode
604
605 AT+5VT  :  Set extend the time of 5V power  
606
607 AT+PRO :  Choose agreement
608
609 AT+RXDL:  Extend the sending and receiving time
610
611 AT+SERVADDR :  Server Address
612
613 AT+APN :  Get or set the APN
614
615 AT+FBAND :  Get or Set whether to automatically modify the frequency band
616
617 AT+DNSCFG : Get or Set DNS Server
618
619 AT+GETSENSORVALUE   : Returns the current sensor measurement
620
621 AT+TR :  Get or Set record time"
622
623 AT+NOUD :  Get or Set the number of data to be uploaded
624
625 AT+CDP :  Read or Clear cached data
626
627 AT+TEMPALARM :  Get or Set alarm of temp
628
629 AT+HUMALARM :  Get or Set alarm of humidity
630
631
632 (% style="color:#037691" %)**COAP Management**      
633
634 AT+URI :  Resource parameters
635
636
637 (% style="color:#037691" %)**UDP Management**
638
639 AT+CFM :  Upload confirmation mode (only valid for UDP)
640
641
642 (% style="color:#037691" %)**MQTT Management**
643
644 AT+CLIENT  :  Get or Set MQTT client
645
646 AT+UNAME  : Get or Set MQTT Username
647
648 AT+PWD  :  Get or Set MQTT password
649
650 AT+PUBTOPIC  :  Get or Set MQTT publish topic
651
652 AT+SUBTOPIC :  Get or Set MQTT subscription topic
653
654
655 (% style="color:#037691" %)**Information**          
656
657 AT+FDR :  Factory Data Reset
658
659 AT+PWORD :  Serial Access Password
660
661
662 = ​5.  FAQ =
663
664 == 5.1 ​ How to Upgrade Firmware ==
665
666
667 User can upgrade the firmware for 1) bug fix, 2) new feature release.
668
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
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 = 6.  Trouble Shooting =
676
677 == 6.1  ​Connection problem when uploading firmware ==
678
679
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
682
683 == 6.2  AT Command input doesn't work ==
684
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 = 7. ​ Order Info =
690
691
692 Part Number**:** NLMS01
693
694
695 = 8.  Packing Info =
696
697
698 (% style="color:#037691" %)**Package Includes:**
699
700 * NLMS01 NB-IoT Leaf Moisture Sensor x 1
701
702 (% style="color:#037691" %)**Dimension and weight**:
703
704 * Device Size: cm
705 * Device Weight: g
706 * Package Size / pcs : cm
707 * Weight / pcs : g
708
709
710
711 = 9.  Support =
712
713
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 * 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
717 ​