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