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