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