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