Version 30.1 by Edwin Chen on 2022/09/08 00:23
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 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.
16
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.
18
19 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.
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
23
24 ​[[image:image-20220907171221-2.png]]
25
26 ​ [[image:image-20220907171221-3.png]]
27
28 == ​1.2 Features ==
29
30 * (((
31 NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
32 )))
33 * (((
34 Monitor Leaf moisture
35 )))
36
37 * (((
38 Monitor Leaf temperature
39 )))
40
41 * (((
42 Moisture and Temperature alarm function
43 )))
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 )))
71
72 == 1.3  Specification ==
73
74 **Common DC Characteristics:**
75
76 * Supply Voltage: 2.1v ~~ 3.6v
77 * Operating Temperature: -40 ~~ 85°C
78
79 **NB-IoT Spec:**
80
81 * - B1 @H-FDD: 2100MHz
82 * - B3 @H-FDD: 1800MHz
83 * - B8 @H-FDD: 900MHz
84 * - B5 @H-FDD: 850MHz
85 * - B20 @H-FDD: 800MHz
86 * - B28 @H-FDD: 700MHz
87
88 == 1.4 Probe Specification ==
89
90
91 **Leaf Moisture: percentage of water drop over total leaf surface**
92
93 * Range 0-100%
94 * Resolution: 0.1%
95 * Accuracy: ±3%（0-50%）；±6%（>50%）
96 * IP67 Protection
97 * Length: 3.5 meters
98
99 **Leaf Temperature:**
100
101 * Range -50℃～80℃
102 * Resolution: 0.1℃
103 * Accuracy: <±0.5℃(-10℃～70℃)，<±1.0℃ (others)
104 * IP67 Protection
105 * Length: 3.5 meters
106
107 == 1.5 ​Applications ==
108
109 * Smart Agriculture
110
111 == 1.6 Pin mapping and power on ==
112
113 ​[[image:image-20220907171221-4.png]]
114
115 **~ **
116
117 = 2.  Use NLMS01 to communicate with IoT Server =
118
119 == 2.1  How it works ==
120
121 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.
122
123 The diagram below shows the working flow in default firmware of NLMS01:
124
125 [[image:image-20220907171221-5.png]]
126
127 == 2.2 ​ Configure the NLMS01 ==
128
129 === 2.2.1 Test Requirement ===
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 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
138
139 [[image:image-20220907171221-6.png]] ​
140
141 === 2.2.2 Insert SIM card ===
142
143 Insert the NB-IoT Card get from your provider.
144
145 User need to take out the NB-IoT module and insert the SIM card like below:
146
147 [[image:image-20220907171221-7.png]] ​
148
149 === 2.2.3 Connect USB – TTL to NLMS01 to configure it ===
150
151 User need to configure NLMS01 via serial port to set the **Server Address** / **Uplink Topic** to define where and how-to uplink packets. NLMS01 support AT Commands, user can use a USB to TTL adapter to connect to NLMS01 and use AT Commands to configure it, as below.
152
153 **Connection:**
154
155 USB TTL GND <~-~-~-~-> GND
156
157 USB TTL TXD <~-~-~-~-> UART_RXD
158
159 USB TTL RXD <~-~-~-~-> UART_TXD
160
161 In the PC, use below serial tool settings:
162
163 * Baud:  **9600**
164 * Data bits:** 8**
165 * Stop bits: **1**
166 * Parity:  **None**
167 * Flow Control: **None**
168
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.
170
171 ​[[image:image-20220907171221-8.png]]
172
173 **Note: the valid AT Commands can be found at:  **[[**https:~~/~~/www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0**>>url:https://www.dropbox.com/sh/351dwor6joz8nwh/AADn1BQaAAxLF_QMyU8NkW47a?dl=0]]
174
175 === 2.2.4 Use CoAP protocol to uplink data ===
176
177 **Note: if you don't have CoAP server, you can refer this link to set up one: **[[**http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
178
179 **Use below commands:**
180
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
184
185 For parameter description, please refer to AT command set
186
187 [[image:image-20220907171221-9.png]]
188
189 After configure the server address and **reset the device** (via AT+ATZ ), NLMS01 will start to uplink sensor values to CoAP server.
190
191 [[image:image-20220907171221-10.png]] ​
192
193 === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
194
195 This feature is supported since firmware version v1.0.1
196
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
200
201 ​ [[image:image-20220907171221-11.png]]
202
203 [[image:image-20220907171221-12.png]]
204
205 ​
206
207 === 2.2.6 Use MQTT protocol to uplink data ===
208
209 This feature is supported since firmware version v110
210
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
218
219 ​ [[image:image-20220907171221-13.png]]
220
221 [[image:image-20220907171221-14.png]]
222
223 ​
224
225 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
226
227 === 2.2.7 Use TCP protocol to uplink data ===
228
229 This feature is supported since firmware version v110
230
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
233
234 ​ [[image:image-20220907171221-15.png]]
235
236 [[image:image-20220907171221-16.png]]
237
238 ​
239
240 === 2.2.8 Change Update Interval ===
241
242 User can use below command to change the **uplink interval**.
243
244 * **AT+TDC=7200      ** ~/~/ Set Update Interval to 7200s (2 hour)
245
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).**
247
248
249 == 2.3  Uplink Payload ==
250
251 In this mode, uplink payload includes 87 bytes in total by default.
252
253 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.
254
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  .....
257
258 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NLMS01 uplink data.
259
260 [[image:image-20220907171221-17.png]]
261
262 The payload is ASCII string, representative same HEX:
263
264 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:
265
266 * (% style="color:red" %)Device ID: 0xf868411056754138 = f868411056754138
267 * (% style="color:blue" %)Version: 0x0064=100=1.0.0
268 * (% style="color:green" %)BAT: 0x0c78 = 3192 mV = 3.192V
269 * (% style="color:red" %)Singal: 0x17 = 23
270 * (% style="color:blue" %)Mod: 0x01 = 1
271 * (% style="color:green" %)Interrupt: 0x00= 0
272 * Leaf moisture: 0x0225= 549 = 54.9%
273 * Leaf Temperature:0x010B =267=26.7 °C
274 * Time stamp : 0x6315537b =1662342011
275 * Leaf Temperature, Leaf moisture,Time stamp : 010b0226631550fb
276 * (% style="color:blue" %)8 sets of recorded data: Leaf Temperature, Leaf moisture,Time stamp : 010e022663154d77,.......
277
278 == 2.4  Payload Explanation and Sensor Interface ==
279
280 === 2.4.1  Device ID ===
281
282 By default, the Device ID equal to the last 15 bits of IMEI.
283
284 User can use **AT+DEUI** to set Device ID
285
286 **Example:**
287
288 AT+DEUI=868411056754138
289
290 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
291
292 === 2.4.2  Version Info ===
293
294 Specify the software version: 0x64=100, means firmware version 1.00.
295
296 For example: 0x00 64 : this device is NLMS01 with firmware version 1.0.0.
297
298 === 2.4.3  Battery Info ===
299
300 Check the battery voltage for NLMS01.
301
302 Ex1: 0x0B45 = 2885mV
303
304 Ex2: 0x0B49 = 2889mV
305
306 === 2.4.4  Signal Strength ===
307
308 NB-IoT Network signal Strength.
309
310 **Ex1: 0x1d = 29**
311
312 **0**  -113dBm or less
313
314 **1**  -111dBm
315
316 **2...30** -109dBm... -53dBm
317
318 **31**   -51dBm or greater
319
320 **99**    Not known or not detectable
321
322 === 2.4.5  Leaf moisture ===
323
324 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**.
325
326 For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the **Leaf** is
327
328 **0229(H) = 549(D) /100 = 54.9.**
329
330 === 2.4.6  Leaf Temperature ===
331
332 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
333
334 **Example**:
335
336 If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/10 = 26.1 °C
337
338 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/10 = -12.9 °C
339
340 === 2.4.7  Timestamp ===
341
342 Time stamp : 0x6315537b =1662342011
343
344 Convert Unix timestamp to time 2022-9-5 9:40:11.
345
346 === 2.4.8  Digital Interrupt ===
347
348 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.
349
350 The command is:
351
352 **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]])**.**
353
354 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.
355
356 Example:
357
358 0x(00): Normal uplink packet.
359
360 0x(01): Interrupt Uplink Packet.
361
362 === 2.4.9  ​+5V Output ===
363
364 NLMS01 will enable +5V output before all sampling and disable the +5v after all sampling. 
365
366 The 5V output time can be controlled by AT Command.
367
368 **AT+5VT=1000**
369
370 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.** **
371
372
373 == 2.5  Downlink Payload ==
374
375 By default, NLMS01 prints the downlink payload to console port.
376
377 [[image:image-20220907171221-18.png]] ​
378
379 **Examples:**
380
381 * **Set TDC**
382
383 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
384
385 Payload:    01 00 00 1E    TDC=30S
386
387 Payload:    01 00 00 3C    TDC=60S
388
389 * **Reset**
390
391 If payload = 0x04FF, it will reset the NLMS01
392
393 * **INTMOD**
394
395 Downlink Payload: 06000003, Set AT+INTMOD=3
396
397 == 2.6  ​LED Indicator ==
398
399 The NLMS01 has an internal LED which is to show the status of different state.
400
401 * 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)
402 * Then the LED will be on for 1 second means device is boot normally.
403 * After NLMS01 join NB-IoT network. The LED will be ON for 3 seconds.
404 * For each uplink probe, LED will be on for 500ms.
405
406 == 2.7 Installation ==
407
408 NLMS01 probe has two sides. The side without words are the sense side. Please be ware when install the sensor.
409
410 [[image:image-20220907171221-19.png]]
411
412 == 2.8 Moisture and Temperature alarm function ==
413
414 ➢ AT Command:
415
416 AT+ HUMALARM =min,max
417
418 ² When min=0, and max≠0, Alarm higher than max
419
420 ² When min≠0, and max=0, Alarm lower than min
421
422 ² When min≠0 and max≠0, Alarm higher than max or lower than min
423
424 Example:
425
426 AT+ HUMALARM =50,60 ~/~/ Alarm when moisture lower than 50.
427
428 AT+ TEMPALARM=min,max
429
430 ² When min=0, and max≠0, Alarm higher than max
431
432 ² When min≠0, and max=0, Alarm lower than min
433
434 ² When min≠0 and max≠0, Alarm higher than max or lower than min
435
436 Example:
437
438 AT+ TEMPALARM=20,30 ~/~/ Alarm when temperature lower than 20.
439
440
441 == 2.9 Set the number of data to be uploaded and the recording time ==
442
443 ➢ AT Command:
444
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)
446
447 AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
448
449 == 2.10 Read or Clear cached data ==
450
451 ➢ AT Command:
452
453 AT+CDP    ~/~/ Read cached data
454
455 [[image:image-20220907171221-20.png]]
456
457
458 AT+CDP=0    ~/~/ Clear cached data
459
460
461 == 2.11  ​Firmware Change Log ==
462
463 Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0>>url:https://www.dropbox.com/sh/1zmcakvbkf24f8x/AACmq2dZ3iRB9F1nVWeEB9Moa?dl=0]]
464
465 Upgrade Instruction: [[Upgrade Firmware>>path:#H5.1200BHowtoUpgradeFirmware]]
466
467 == 2.12  ​Battery Analysis ==
468
469 === 2.12.1  ​Battery Type ===
470
471 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.
472
473 The battery is designed to last for several years depends on the actually use environment and update interval. 
474
475 The battery related documents as below:
476
477 * [[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
478 * [[Lithium-Thionyl Chloride Battery datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
479 * [[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
480
481 [[image:image-20220907171221-21.png]] ​
482
483 === 2.12.2  Power consumption Analyze ===
484
485 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.
486
487 Instruction to use as below:
488
489 **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/]]
490
491 **Step 2: ** Open it and choose
492
493 * Product Model
494 * Uplink Interval
495 * Working Mode
496
497 And the Life expectation in difference case will be shown on the right.
498
499 [[image:image-20220907171221-22.jpeg]] ​
500
501 === 2.12.3  ​Battery Note ===
502
503 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.
504
505 === 2.12.4  Replace the battery ===
506
507 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).
508
509 = 3. ​ Access NB-IoT Module =
510
511 Users can directly access the AT command set of the NB-IoT module.
512
513 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/]] 
514
515 [[image:image-20220907171221-23.png]] ​
516
517 = 4.  Using the AT Commands =
518
519 == 4.1  Access AT Commands ==
520
521 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]]
522
523 AT+<CMD>?  : Help on <CMD>
524
525 AT+<CMD>         : Run <CMD>
526
527 AT+<CMD>=<value> : Set the value
528
529 AT+<CMD>=?  : Get the value
530
531 **General Commands**      
532
533 AT  : Attention       
534
535 AT?  : Short Help     
536
537 ATZ  : MCU Reset    
538
539 AT+TDC  : Application Data Transmission Interval
540
541 AT+CFG  : Print all configurations
542
543 AT+CFGMOD           : Working mode selection
544
545 AT+INTMOD            : Set the trigger interrupt mode
546
547 AT+5VT  : Set extend the time of 5V power  
548
549 AT+PRO  : Choose agreement
550
551 AT+RXDL  : Extend the sending and receiving time
552
553 AT+SERVADDR  : Server Address
554
555 AT+TR      : Get or Set record time"
556
557
558 AT+NOUD      : Get or Set the number of data to be uploaded
559
560
561 AT+CDP     : Read or Clear cached data
562
563
564 AT+TEMPALARM      : Get or Set alarm of temp
565
566 AT+HUMALARM     : Get or Set alarm of PH
567
568
569 **COAP Management**      
570
571 AT+URI            : Resource parameters
572
573 **UDP Management**
574
575 AT+CFM          : Upload confirmation mode (only valid for UDP)
576
577 **MQTT Management**
578
579 AT+CLIENT               : Get or Set MQTT client
580
581 AT+UNAME  : Get or Set MQTT Username
582
583 AT+PWD                  : Get or Set MQTT password
584
585 AT+PUBTOPIC  : Get or Set MQTT publish topic
586
587 AT+SUBTOPIC  : Get or Set MQTT subscription topic
588
589 **Information**          
590
591 AT+FDR  : Factory Data Reset
592
593 AT+PWORD  : Serial Access Password
594
595 = ​5.  FAQ =
596
597 == 5.1 ​ How to Upgrade Firmware ==
598
599 User can upgrade the firmware for 1) bug fix, 2) new feature release.
600
601 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]]
602
603 **Notice, **NLMS01 **and **NLMS01 **share the same mother board. They use the same connection and method to update.**
604
605 = 6.  Trouble Shooting =
606
607 == 6.1  ​Connection problem when uploading firmware ==
608
609 **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]]
610
611 == 6.2  AT Command input doesn't work ==
612
613 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.
614
615 = 7. ​ Order Info =
616
617 Part Number**:** NLMS01
618
619 = 8.  Packing Info =
620
621 **Package Includes**:
622
623 * NLMS01 NB-IoT Leaf Moisture Sensor x 1
624
625 **Dimension and weight**:
626
627 * Device Size: cm
628 * Device Weight: g
629 * Package Size / pcs : cm
630 * Weight / pcs : g
631
632 = 9.  Support =
633
634 * 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.
635 * 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]]
636
637 ​

Applications

Navigation

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