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