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