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