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