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