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