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