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