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