Version 65.16 by Xiaoling on 2022/07/08 15:52
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20220606151504-2.jpeg||height="554" width="554"]]
3
4
5
6
7
8
9
10
11
12
13
14 **Table of Contents:**
15
16 {{toc/}}
17
18
19
20
21
22
23
24 = 1.  Introduction =
25
26 == 1.1 ​ What is LoRaWAN Soil Moisture & EC Sensor ==
27
28 (((
29
30
31 (((
32 Dragino NSE01 is an (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory.
33 )))
34
35 (((
36 It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
37 )))
38
39 (((
40 The wireless technology used in NSE01 allows the device to send data at a low data rate and reach ultra-long distances, providing ultra-long-distance spread spectrum Communication.
41 )))
42
43 (((
44 NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
45 )))
46
47
48 )))
49
50 [[image:1654503236291-817.png]]
51
52
53 [[image:1657245163077-232.png]]
54
55
56
57 == 1.2 ​ Features ==
58
59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 * Monitor Soil Moisture
61 * Monitor Soil Temperature
62 * Monitor Soil Conductivity
63 * AT Commands to change parameters
64 * Uplink on periodically
65 * Downlink to change configure
66 * IP66 Waterproof Enclosure
67 * Ultra-Low Power consumption
68 * AT Commands to change parameters
69 * Micro SIM card slot for NB-IoT SIM
70 * 8500mAh Battery for long term use
71
72 == 1.3  Specification ==
73
74
75 (% style="color:#037691" %)**Common DC Characteristics:**
76
77 * Supply Voltage: 2.1v ~~ 3.6v
78 * Operating Temperature: -40 ~~ 85°C
79
80 (% style="color:#037691" %)**NB-IoT Spec:**
81
82 * - B1 @H-FDD: 2100MHz
83 * - B3 @H-FDD: 1800MHz
84 * - B8 @H-FDD: 900MHz
85 * - B5 @H-FDD: 850MHz
86 * - B20 @H-FDD: 800MHz
87 * - B28 @H-FDD: 700MHz
88
89 Probe(% style="color:#037691" %)** Specification:**
90
91 Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
92
93 [[image:image-20220708101224-1.png]]
94
95
96
97 == ​1.4  Applications ==
98
99 * Smart Agriculture
100
101 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
102 ​
103
104 == 1.5  Pin Definitions ==
105
106
107 [[image:1657246476176-652.png]]
108
109
110
111 = 2.  Use NSE01 to communicate with IoT Server =
112
113 == 2.1  How it works ==
114
115
116 (((
117 The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 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 NSE01.
118 )))
119
120
121 (((
122 The diagram below shows the working flow in default firmware of NSE01:
123 )))
124
125 [[image:image-20220708101605-2.png]]
126
127 (((
128
129 )))
130
131
132
133 == 2.2 ​ Configure the NSE01 ==
134
135
136 === 2.2.1 Test Requirement ===
137
138
139 (((
140 To use NSE01 in your city, make sure meet below requirements:
141 )))
142
143 * Your local operator has already distributed a NB-IoT Network there.
144 * The local NB-IoT network used the band that NSE01 supports.
145 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
146
147 (((
148 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
149 )))
150
151
152 [[image:1657249419225-449.png]]
153
154
155
156 === 2.2.2 Insert SIM card ===
157
158 (((
159 Insert the NB-IoT Card get from your provider.
160 )))
161
162 (((
163 User need to take out the NB-IoT module and insert the SIM card like below:
164 )))
165
166
167 [[image:1657249468462-536.png]]
168
169
170
171 === 2.2.3 Connect USB – TTL to NSE01 to configure it ===
172
173 (((
174 (((
175 User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
176 )))
177 )))
178
179
180 **Connection:**
181
182 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
183
184 (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
185
186 (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
187
188
189 In the PC, use below serial tool settings:
190
191 * Baud:  (% style="color:green" %)**9600**
192 * Data bits:** (% style="color:green" %)8(%%)**
193 * Stop bits: (% style="color:green" %)**1**
194 * Parity:  (% style="color:green" %)**None**
195 * Flow Control: (% style="color:green" %)**None**
196
197 (((
198 Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
199 )))
200
201 [[image:image-20220708110657-3.png]]
202
203 (((
204 (% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
205 )))
206
207
208
209 === 2.2.4 Use CoAP protocol to uplink data ===
210
211 (% 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/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
212
213
214 **Use below commands:**
215
216 * (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
217 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
218 * (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
219
220 For parameter description, please refer to AT command set
221
222 [[image:1657249793983-486.png]]
223
224
225 After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
226
227 [[image:1657249831934-534.png]]
228
229
230
231 === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
232
233 This feature is supported since firmware version v1.0.1
234
235
236 * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
237 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
238 * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
239
240 [[image:1657249864775-321.png]]
241
242
243 [[image:1657249930215-289.png]]
244
245
246
247 === 2.2.6 Use MQTT protocol to uplink data ===
248
249 This feature is supported since firmware version v110
250
251
252 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
253 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
254 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
255 * (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
256 * (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
257 * (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
258 * (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
259
260 [[image:1657249978444-674.png]]
261
262
263 [[image:1657249990869-686.png]]
264
265
266 (((
267 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.
268 )))
269
270
271
272 === 2.2.7 Use TCP protocol to uplink data ===
273
274 This feature is supported since firmware version v110
275
276
277 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
278 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
279
280 [[image:1657250217799-140.png]]
281
282
283 [[image:1657250255956-604.png]]
284
285
286
287 === 2.2.8 Change Update Interval ===
288
289 User can use below command to change the (% style="color:green" %)**uplink interval**.
290
291 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
292
293 (((
294 (% style="color:red" %)**NOTE:**
295 )))
296
297 (((
298 (% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
299 )))
300
301
302
303 == 2.3  Uplink Payload ==
304
305 In this mode, uplink payload includes in total 18 bytes
306
307 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
308 |=(% style="width: 60px;" %)(((
309 **Size(bytes)**
310 )))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1**
311 |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
312
313 (((
314 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
315 )))
316
317
318 [[image:image-20220708111918-4.png]]
319
320
321 The payload is ASCII string, representative same HEX:
322
323 0x72403155615900640c7817075e0a8c02f900 where:
324
325 * Device ID: 0x 724031556159 = 724031556159
326 * Version: 0x0064=100=1.0.0
327
328 * BAT: 0x0c78 = 3192 mV = 3.192V
329 * Singal: 0x17 = 23
330 * Soil Moisture: 0x075e= 1886 = 18.86  %
331 * Soil Temperature:0x0a8c =2700=27 °C
332 * Soil Conductivity(EC) = 0x02f9 =761 uS /cm
333 * Interrupt: 0x00 = 0
334
335
336
337
338 == 2.4  Payload Explanation and Sensor Interface ==
339
340
341 === 2.4.1  Device ID ===
342
343 (((
344 By default, the Device ID equal to the last 6 bytes of IMEI.
345 )))
346
347 (((
348 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
349 )))
350
351 (((
352 **Example:**
353 )))
354
355 (((
356 AT+DEUI=A84041F15612
357 )))
358
359 (((
360 The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
361 )))
362
363
364
365 === 2.4.2  Version Info ===
366
367 (((
368 Specify the software version: 0x64=100, means firmware version 1.00.
369 )))
370
371 (((
372 For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
373 )))
374
375
376
377 === 2.4.3  Battery Info ===
378
379 (((
380 Check the battery voltage for LSE01.
381 )))
382
383 (((
384 Ex1: 0x0B45 = 2885mV
385 )))
386
387 (((
388 Ex2: 0x0B49 = 2889mV
389 )))
390
391
392
393 === 2.4.4  Signal Strength ===
394
395 (((
396 NB-IoT Network signal Strength.
397 )))
398
399 (((
400 **Ex1: 0x1d = 29**
401 )))
402
403 (((
404 (% style="color:blue" %)**0**(%%)  -113dBm or less
405 )))
406
407 (((
408 (% style="color:blue" %)**1**(%%)  -111dBm
409 )))
410
411 (((
412 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
413 )))
414
415 (((
416 (% style="color:blue" %)**31**  (%%) -51dBm or greater
417 )))
418
419 (((
420 (% style="color:blue" %)**99**   (%%) Not known or not detectable
421 )))
422
423
424
425 === 2.4.5  Soil Moisture ===
426
427 (((
428 (((
429 Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
430 )))
431 )))
432
433 (((
434 (((
435 For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
436 )))
437 )))
438
439 (((
440
441 )))
442
443 (((
444 (% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
445 )))
446
447
448
449 === 2.4.6  Soil Temperature ===
450
451 (((
452 Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
453 )))
454
455 (((
456 **Example**:
457 )))
458
459 (((
460 If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
461 )))
462
463 (((
464 If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
465 )))
466
467
468
469 === 2.4.7  Soil Conductivity (EC) ===
470
471 (((
472 Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
473 )))
474
475 (((
476 For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
477 )))
478
479 (((
480 Generally, the EC value of irrigation water is less than 800uS / cm.
481 )))
482
483 (((
484
485 )))
486
487 (((
488
489 )))
490
491 === 2.4.8  Digital Interrupt ===
492
493 (((
494 Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
495 )))
496
497 (((
498 The command is:
499 )))
500
501 (((
502 (% 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]])**.**
503 )))
504
505
506 (((
507 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.
508 )))
509
510
511 (((
512 Example:
513 )))
514
515 (((
516 0x(00): Normal uplink packet.
517 )))
518
519 (((
520 0x(01): Interrupt Uplink Packet.
521 )))
522
523
524
525 === 2.4.9  ​+5V Output ===
526
527 (((
528 NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
529 )))
530
531
532 (((
533 The 5V output time can be controlled by AT Command.
534 )))
535
536 (((
537 (% style="color:blue" %)**AT+5VT=1000**
538 )))
539
540 (((
541 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
542 )))
543
544
545
546 == 2.5  Downlink Payload ==
547
548 By default, NSE01 prints the downlink payload to console port.
549
550 [[image:image-20220708133731-5.png]]
551
552
553 (((
554 (% style="color:blue" %)**Examples:**
555 )))
556
557 (((
558
559 )))
560
561 * (((
562 (% style="color:blue" %)**Set TDC**
563 )))
564
565 (((
566 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
567 )))
568
569 (((
570 Payload:    01 00 00 1E    TDC=30S
571 )))
572
573 (((
574 Payload:    01 00 00 3C    TDC=60S
575 )))
576
577 (((
578
579 )))
580
581 * (((
582 (% style="color:blue" %)**Reset**
583 )))
584
585 (((
586 If payload = 0x04FF, it will reset the NSE01
587 )))
588
589
590 * (% style="color:blue" %)**INTMOD**
591
592 Downlink Payload: 06000003, Set AT+INTMOD=3
593
594
595
596 == 2.6  ​LED Indicator ==
597
598 (((
599 The NSE01 has an internal LED which is to show the status of different state.
600
601
602 * When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
603 * Then the LED will be on for 1 second means device is boot normally.
604 * After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
605 * For each uplink probe, LED will be on for 500ms.
606 )))
607
608
609
610
611 == 2.7  Installation in Soil ==
612
613 __**Measurement the soil surface**__
614
615 Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
616
617 [[image:1657259653666-883.png]] ​
618
619
620 (((
621
622
623 (((
624 Dig a hole with diameter > 20CM.
625 )))
626
627 (((
628 Horizontal insert the probe to the soil and fill the hole for long term measurement.
629 )))
630 )))
631
632 [[image:1654506665940-119.png]]
633
634 (((
635
636 )))
637
638
639 == 2.8  ​Firmware Change Log ==
640
641
642 Download URL & Firmware Change log
643
644 [[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
645
646
647 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648
649
650
651 == 2.9  ​Battery Analysis ==
652
653 === 2.9.1  ​Battery Type ===
654
655
656 The NSE01 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.
657
658
659 The battery is designed to last for several years depends on the actually use environment and update interval. 
660
661
662 The battery related documents as below:
663
664 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
665 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
666 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
667
668 (((
669 [[image:image-20220708140453-6.png]]
670 )))
671
672
673
674 === 2.9.2  Power consumption Analyze ===
675
676 (((
677 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.
678 )))
679
680
681 (((
682 Instruction to use as below:
683 )))
684
685 (((
686 (% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
687 )))
688
689
690 (((
691 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
692 )))
693
694 * (((
695 Product Model
696 )))
697 * (((
698 Uplink Interval
699 )))
700 * (((
701 Working Mode
702 )))
703
704 (((
705 And the Life expectation in difference case will be shown on the right.
706 )))
707
708 [[image:image-20220708141352-7.jpeg]]
709
710
711
712 === 2.9.3  ​Battery Note ===
713
714 (((
715 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.
716 )))
717
718
719
720 === 2.9.4  Replace the battery ===
721
722 (((
723 The default battery pack of NSE01 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).
724 )))
725
726
727
728 = 3. ​ Access NB-IoT Module =
729
730 (((
731 Users can directly access the AT command set of the NB-IoT module.
732 )))
733
734 (((
735 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/]] 
736 )))
737
738 [[image:1657261278785-153.png]]
739
740
741
742 = 4.  Using the AT Commands =
743
744 == 4.1  Access AT Commands ==
745
746 See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
747
748
749 AT+<CMD>?  : Help on <CMD>
750
751 AT+<CMD>         : Run <CMD>
752
753 AT+<CMD>=<value> : Set the value
754
755 AT+<CMD>=?  : Get the value
756
757
758 (% style="color:#037691" %)**General Commands**(%%)      
759
760 AT  : Attention       
761
762 AT?  : Short Help     
763
764 ATZ  : MCU Reset    
765
766 AT+TDC  : Application Data Transmission Interval
767
768 AT+CFG  : Print all configurations
769
770 AT+CFGMOD           : Working mode selection
771
772 AT+INTMOD            : Set the trigger interrupt mode
773
774 AT+5VT  : Set extend the time of 5V power  
775
776 AT+PRO  : Choose agreement
777
778 AT+WEIGRE  : Get weight or set weight to 0
779
780 AT+WEIGAP  : Get or Set the GapValue of weight
781
782 AT+RXDL  : Extend the sending and receiving time
783
784 AT+CNTFAC  : Get or set counting parameters
785
786 AT+SERVADDR  : Server Address
787
788
789 (% style="color:#037691" %)**COAP Management**      
790
791 AT+URI            : Resource parameters
792
793
794 (% style="color:#037691" %)**UDP Management**
795
796 AT+CFM          : Upload confirmation mode (only valid for UDP)
797
798
799 (% style="color:#037691" %)**MQTT Management**
800
801 AT+CLIENT               : Get or Set MQTT client
802
803 AT+UNAME  : Get or Set MQTT Username
804
805 AT+PWD                  : Get or Set MQTT password
806
807 AT+PUBTOPIC  : Get or Set MQTT publish topic
808
809 AT+SUBTOPIC  : Get or Set MQTT subscription topic
810
811
812 (% style="color:#037691" %)**Information**          
813
814 AT+FDR  : Factory Data Reset
815
816 AT+PWORD  : Serial Access Password
817
818
819
820 = ​5.  FAQ =
821
822 == 5.1 ​ How to Upgrade Firmware ==
823
824
825 (((
826 User can upgrade the firmware for 1) bug fix, 2) new feature release.
827 )))
828
829 (((
830 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>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
831 )))
832
833 (((
834 (% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
835 )))
836
837
838
839 = 6.  Trouble Shooting =
840
841 == 6.1  ​Connection problem when uploading firmware ==
842
843
844 (% class="wikigeneratedid" %)
845 (((
846 (% style="font-size:14px" %)**Please see: **(%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting||style="background-color: rgb(255, 255, 255); font-size: 14px;"]]
847 )))
848
849
850
851 == 6.2  AT Command input doesn't work ==
852
853 (((
854 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.
855 )))
856
857
858
859 = 7. ​ Order Info =
860
861
862 Part Number**:** (% style="color:#4f81bd" %)**NSE01**
863
864
865 (% class="wikigeneratedid" %)
866 (((
867
868 )))
869
870 = 8.  Packing Info =
871
872 (((
873
874
875 (% style="color:#037691" %)**Package Includes**:
876
877
878 * NSE01 NB-IoT Soil Moisture & EC Sensor x 1
879 * External antenna x 1
880 )))
881
882 (((
883
884
885 (% style="color:#037691" %)**Dimension and weight**:
886
887
888 * Size: 195 x 125 x 55 mm
889 * Weight:   420g
890 )))
891
892 (((
893
894
895
896
897 )))
898
899 = 9.  Support =
900
901 * 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.
902 * 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]]

Applications

Navigation

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