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