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