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