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