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