Version 124.1 by David Huang on 2022/09/08 16:38
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
21 == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22
23 (((
24
25
26 (((
27 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*.
28 )))
29
30 (((
31 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.
32 )))
33
34 (((
35 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 )))
37
38 (((
39 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).
40 )))
41
42 (((
43
44 )))
45
46 (((
47 ~* make sure you have NB-IoT coverage locally.
48 )))
49
50
51 )))
52
53 [[image:1657348284168-431.png]]
54
55
56
57 == 1.2 ​ Features ==
58
59
60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 * Monitor Temperature & Humidity via SHT31
62 * AT Commands to change parameters
63 * Uplink on periodically
64 * Downlink to change configure
65 * IP66 Waterproof Enclosure
66 * Ultra-Low Power consumption
67 * AT Commands to change parameters
68 * Micro SIM card slot for NB-IoT SIM
69 * 8500mAh Battery for long term use
70
71 == 1.3  Specification ==
72
73
74 (% style="color:#037691" %)**Common DC Characteristics:**
75
76 * Supply Voltage: 2.1v ~~ 3.6v
77 * Operating Temperature: -40 ~~ 85°C
78
79 (% style="color:#037691" %)**NB-IoT Spec:**
80
81 * - B1 @H-FDD: 2100MHz
82 * - B3 @H-FDD: 1800MHz
83 * - B8 @H-FDD: 900MHz
84 * - B5 @H-FDD: 850MHz
85 * - B20 @H-FDD: 800MHz
86 * - B28 @H-FDD: 700MHz
87
88 (% style="color:#037691" %)**Battery:**
89
90 * Li/SOCI2 un-chargeable battery
91 * Capacity: 8500mAh
92 * Self Discharge: <1% / Year @ 25°C
93 * Max continuously current: 130mA
94 * Max boost current: 2A, 1 second
95
96 == ​1.4  Applications ==
97
98
99 * Smart Buildings & Home Automation
100 * Logistics and Supply Chain Management
101 * Smart Metering
102 * Smart Agriculture
103 * Smart Cities
104 * Smart Factory
105
106 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
107 ​
108
109
110
111 == 1.5  Pin Definitions & Switch ==
112
113
114 N95S31B use the mother board from NBSN95 which as below.
115
116
117 [[image:image-20220709144723-1.png]]
118
119
120
121 === 1.5.1 Jumper JP2 ===
122
123
124 Power on Device when put this jumper.
125
126
127
128 === 1.5.2 BOOT MODE / SW1 ===
129
130
131 (((
132 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.
133 )))
134
135 (((
136 2) Flash: work mode, device starts to work and send out console output for further debug
137 )))
138
139
140
141 === 1.5.3 Reset Button ===
142
143
144 Press to reboot the device.
145
146
147
148 === 1.5.4 LED ===
149
150
151 It will flash:
152
153 1. When boot the device in flash mode
154 1. Send an uplink packet
155
156 = 2.  Use N95S31B to communicate with IoT Server =
157
158
159 == 2.1  How it works ==
160
161
162 (((
163 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.
164 )))
165
166
167 (((
168 The diagram below shows the working flow in default firmware of N95S31B:
169 )))
170
171 (((
172
173 )))
174
175 [[image:1657520100595-569.png]]
176
177 (((
178
179 )))
180
181
182 == 2.2 ​ Configure the N95S31B ==
183
184
185 === 2.2.1  Power On N95S31B ===
186
187
188 [[image:image-20220709150546-2.png]]
189
190
191
192 === 2.2.1 Test Requirement ===
193
194
195 (((
196 To use N95S31B in your city, make sure meet below requirements:
197 )))
198
199 * (((
200 Your local operator has already distributed a NB-IoT Network there.
201 )))
202 * (((
203 The local NB-IoT network used the band that N95S31B supports.
204 )))
205 * (((
206 Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
207 )))
208
209 (((
210 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
211 )))
212
213 (((
214 N95S31B supports different communication protocol such as :
215 )))
216
217 (((
218 * (((
219 CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
220 )))
221 * (((
222 raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
223 )))
224 * (((
225 MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
226 )))
227 * (((
228 TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
229 )))
230
231 (((
232 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.
233 )))
234
235
236 )))
237
238 [[image:1657350625843-586.png]]
239
240
241
242 === 2.2.3  Insert SIM card ===
243
244
245 (((
246 Insert the NB-IoT Card get from your provider.
247 )))
248
249 (((
250 User need to take out the NB-IoT module and insert the SIM card like below:
251 )))
252
253
254 [[image:1657351240556-536.png]]
255
256
257
258 === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
259
260
261 (((
262 (((
263 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.
264
265
266 )))
267 )))
268
269 [[image:1657351312545-300.png]]
270
271
272 **Connection:**
273
274 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
275
276 (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
277
278 (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
279
280
281 In the PC, use below serial tool settings:
282
283 * Baud:  (% style="color:green" %)**9600**
284 * Data bits:** (% style="color:green" %)8(%%)**
285 * Stop bits: (% style="color:green" %)**1**
286 * Parity:  (% style="color:green" %)**None**
287 * Flow Control: (% style="color:green" %)**None**
288
289 (((
290 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.
291 )))
292
293 [[image:1657329814315-101.png]]
294
295
296 (((
297 (% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
298 )))
299
300
301
302 === 2.2.5  Use CoAP protocol to uplink data ===
303
304
305 (% 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/]]**
306
307
308 (((
309 **Use below commands:**
310 )))
311
312 * (((
313 (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
314 )))
315 * (((
316 (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
317 )))
318 * (((
319 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
320 )))
321
322 (((
323
324
325 For parameter description, please refer to AT command set
326 )))
327
328 [[image:1657352146020-183.png]]
329
330
331 (((
332 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.
333 )))
334
335 [[image:1657352185396-303.png]]
336
337
338
339 === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
340
341
342 * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
343 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
344 * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
345
346 [[image:1657352391268-297.png]]
347
348
349 [[image:1657352403317-397.png]]
350
351
352
353 === 2.2.7  Use MQTT protocol to uplink data ===
354
355
356 N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
357
358 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
359 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
360 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
361 * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
362 * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
363 * (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
364 * (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
365
366 [[image:1657352634421-276.png]]
367
368
369 [[image:1657352645687-385.png]]
370
371
372 (((
373 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.
374 )))
375
376
377 (((
378 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.
379 )))
380
381
382
383 === 2.2.8  Use TCP protocol to uplink data ===
384
385
386 This feature is supported since firmware version v110
387
388 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
389 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
390
391 [[image:1657352898400-901.png]]
392
393
394 [[image:1657352914475-252.png]]
395
396
397
398 === 2.2.9  Change Update Interval ===
399
400
401 User can use below command to change the (% style="color:green" %)**uplink interval**.
402
403 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
404
405 (((
406
407 )))
408
409 (% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
410
411 **By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
412
413
414 == 2.3  Uplink Payload ==
415
416
417 (((
418 N95S31B 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.
419 )))
420
421
422 (((
423 For example:
424 )))
425
426 (((
427 (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
428 )))
429
430
431 (((
432 The uplink payloads are composed in  ASCII String. For example:
433 )))
434
435 (((
436 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
437 )))
438
439 (((
440 0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
441 )))
442
443
444 (((
445 (% style="color:red" %)**NOTE:**
446 )))
447
448 (% style="color:red" %)
449 1. (((
450 **All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
451 )))
452 1. (((
453 **By default, the device will send an uplink message every 1 hour.**
454
455
456
457
458 )))
459
460 === 2.3.1  Payload Analyze ===
461
462
463 N95S31B uplink payload includes in total 21 bytes
464
465
466 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
467 |=(% style="width: 60px;" %)(((
468 **Size(bytes)**
469 )))|=(% 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**
470 |(% 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" %)(((
471 (((
472 Reserve/ Same as NBSN95 CFGMOD=1
473 )))
474
475 (((
476 No function here.
477 )))
478 )))|(% style="width:77px" %)(((
479 (((
480 [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
481 )))
482
483 (((
484 By SHT31
485 )))
486 )))|(% style="width:80px" %)(((
487 (((
488 [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
489 )))
490
491 (((
492 By SHT31
493 )))
494 )))
495
496 (((
497
498
499 (((
500 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
501 )))
502 )))
503
504
505 [[image:1657354294009-643.png]]
506
507
508 The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
509
510 * Device ID: 0x724031607457 = 724031607457
511 * Version: 0x006e=110=1.1.0
512
513 * BAT: 0x0ccd = 3277 mV = 3.277V
514 * Signal: 0x1b = 27
515 * Model: 0x01 = 1
516 * 0x00dc000ccc= reserve, ignore in N95S31B
517 * Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
518 * Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
519
520 (((
521
522 )))
523
524 (((
525 (% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
526 )))
527
528 In this mode, uplink payload includes 91 bytes in total by default.
529
530 Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
531
532 |**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4
533 |**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp .....
534
535 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
536
537 [[image:image-20220908154949-1.png]]
538
539 The payload is ASCII string, representative same HEX:
540
541 0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
542
543 * (% style="color:red" %) Device ID: f868411056758782 = f868411056758782
544 * (% style="color:blue" %) Version: 0x000c=120=1.2
545 * (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V
546 * (% style="color:red" %) Singal: 0x0c = 12
547 * (% style="color:blue" %) Mod: 0x01 = 1
548 * TemDS18B20: 0x0000= 0 = 0
549 * (% style="color:green" %)Interrupt: 0x00= 0
550 * (% style="color:green" %)adc: 0x0030= 48
551 * SHTTEM: 0x0114= 276 = 27.6
552 * SHTHUM:0x0231 =561=56.1%
553 * (% style="color:red" %) Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
554 * (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
555 * 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
556
557 === 2.3.2  Device ID ===
558
559
560 (((
561 By default, the Device ID equal to the last 6 bytes of IMEI.
562 )))
563
564 (((
565 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
566 )))
567
568 (((
569 **Example:**
570 )))
571
572 (((
573 AT+DEUI=A84041F15612
574 )))
575
576 (((
577 The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
578
579
580 )))
581
582 (% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:**
583
584
585 By default, the Device ID equal to the last 15 bits of IMEI.
586
587 User can use **AT+DEUI** to set Device ID
588
589 **Example:**
590
591 AT+DEUI=868411056754138
592
593
594 === 2.3.3  Version Info ===
595
596
597 (((
598 These bytes include the hardware and software version.
599 )))
600
601 (((
602 Higher byte: Specify hardware version: always 0x00 for N95S31B
603 )))
604
605 (((
606 Lower byte: Specify the software version: 0x6E=110, means firmware version 110
607 )))
608
609 (((
610
611 )))
612
613 (((
614 For example: 0x00 6E: this device is N95S31B with firmware version 110.
615 )))
616
617 (((
618
619 )))
620
621
622 === 2.3.4  Battery Info ===
623
624
625 (((
626 Ex1: 0x0B45 = 2885mV
627 )))
628
629 (((
630 Ex2: 0x0B49 = 2889mV
631 )))
632
633
634
635 === 2.3.5  Signal Strength ===
636
637
638 (((
639 NB-IoT Network signal Strength.
640 )))
641
642 (((
643 **Ex1: 0x1d = 29**
644 )))
645
646 (((
647 (% style="color:blue" %)**0**(%%)  -113dBm or less
648 )))
649
650 (((
651 (% style="color:blue" %)**1**(%%)  -111dBm
652 )))
653
654 (((
655 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
656 )))
657
658 (((
659 (% style="color:blue" %)**31**  (%%) -51dBm or greater
660 )))
661
662 (((
663 (% style="color:blue" %)**99**   (%%) Not known or not detectable
664 )))
665
666
667
668 === 2.3.6  Temperature & Humidity ===
669
670
671 The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
672
673 [[image:image-20220709161741-3.png]]
674
675
676 Convert the read byte to decimal and divide it by ten.
677
678
679 **Example:**
680
681 Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
682
683 Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
684
685
686
687 == 2.4  Downlink Payload ==
688
689
690 By default, N95S31B prints the downlink payload to console port.
691
692 [[image:image-20220709100028-1.png]]
693
694
695 (((
696 (% style="color:blue" %)**Examples:**
697 )))
698
699 (((
700
701 )))
702
703 * (((
704 (% style="color:blue" %)**Set TDC**
705 )))
706
707 (((
708 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
709 )))
710
711 (((
712 Payload:    01 00 00 1E    TDC=30S
713 )))
714
715 (((
716 Payload:    01 00 00 3C    TDC=60S
717 )))
718
719 (((
720
721 )))
722
723 * (((
724 (% style="color:blue" %)**Reset**
725 )))
726
727 (((
728 If payload = 0x04FF, it will reset the N95S31B
729 )))
730
731
732 * (% style="color:blue" %)**INTMOD**
733
734 (((
735 Downlink Payload: 06000003, Set AT+INTMOD=3
736 )))
737
738
739 == 2.5 Humidity and Temperature alarm function ==
740
741 ➢ AT Command:
742
743 AT+ SHHUM=min,max
744
745 ² When min=0, and max≠0, Alarm higher than max
746
747 ² When min≠0, and max=0, Alarm lower than min
748
749 ² When min≠0 and max≠0, Alarm higher than max or lower than min
750
751 Example:
752
753 AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
754
755
756 AT+ SHTEMP=min,max
757
758 ² When min=0, and max≠0, Alarm higher than max
759
760 ² When min≠0, and max=0, Alarm lower than min
761
762 ² When min≠0 and max≠0, Alarm higher than max or lower than min
763
764 Example:
765
766 AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
767
768 == 2.6 Set the number of data to be uploaded and the recording time ==
769
770 ➢ AT Command:
771
772 AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
773
774 AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
775
776 == 2.7 Read or Clear cached data ==
777
778 ➢ AT Command:
779
780 AT+CDP ~/~/ Read cached data
781
782 [[image:image-20220908163102-2.png]]
783
784 AT+CDP=0 ~/~/ Clear cached data
785
786 == 2.8  ​Battery Analysis ==
787
788
789 === 2.8.1  ​Battery Type ===
790
791
792 (((
793 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.
794 )))
795
796 (((
797 The battery is designed to last for several years depends on the actually use environment and update interval. 
798 )))
799
800 (((
801 The battery related documents as below:
802 )))
803
804 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
805 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
806 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
807
808 (((
809 [[image:image-20220709101450-2.png]]
810 )))
811
812
813
814 === 2.8.2  Power consumption Analyze ===
815
816
817 (((
818 The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
819 )))
820
821 (((
822
823 )))
824
825
826 === 2.8.3  ​Battery Note ===
827
828
829 (((
830 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.
831 )))
832
833
834
835 === 2.8.4  Replace the battery ===
836
837
838 (((
839 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.
840 )))
841
842
843 (((
844 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).
845 )))
846
847
848
849 = 3. ​ Access NB-IoT Module =
850
851
852 (((
853 Users can directly access the AT command set of the NB-IoT module.
854 )))
855
856 (((
857 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/]] 
858
859
860 )))
861
862 [[image:1657333200519-600.png]]
863
864
865
866 = 4.  Using the AT Commands =
867
868
869 == 4.1  Access AT Commands ==
870
871
872 See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
873
874
875 AT+<CMD>?  : Help on <CMD>
876
877 AT+<CMD>         : Run <CMD>
878
879 AT+<CMD>=<value> : Set the value
880
881 AT+<CMD>=?  : Get the value
882
883
884 (% style="color:#037691" %)**General Commands**(%%)      
885
886 AT  : Attention       
887
888 AT?  : Short Help     
889
890 ATZ  : MCU Reset    
891
892 AT+TDC  : Application Data Transmission Interval
893
894 AT+CFG  : Print all configurations
895
896 AT+CFGMOD           : Working mode selection
897
898 AT+INTMOD            : Set the trigger interrupt mode
899
900 AT+5VT  : Set extend the time of 5V power  
901
902 AT+PRO  : Choose agreement
903
904 AT+WEIGRE  : Get weight or set weight to 0
905
906 AT+WEIGAP  : Get or Set the GapValue of weight
907
908 AT+RXDL  : Extend the sending and receiving time
909
910 AT+CNTFAC  : Get or set counting parameters
911
912 AT+SERVADDR  : Server Address
913
914 AT+TR      : Get or Set record time
915
916 AT+APN     : Get or set the APN
917
918 AT+FBAND   : Get or Set whether to automatically modify the frequency band
919
920 AT+DNSCFG  : Get or Set DNS Server
921
922 AT+GETSENSORVALUE   : Returns the current sensor measurement
923
924 AT+NOUD      : Get or Set the number of data to be uploaded
925
926 AT+CDP     : Read or Clear cached data
927
928 AT+SHTEMP: Get or Set alarm of temp
929
930 AT+SHHUM: Get or Set alarm of moisture
931
932 (% style="color:#037691" %)**COAP Management**      
933
934 AT+URI            : Resource parameters
935
936
937 (% style="color:#037691" %)**UDP Management**
938
939 AT+CFM          : Upload confirmation mode (only valid for UDP)
940
941
942 (% style="color:#037691" %)**MQTT Management**
943
944 AT+CLIENT               : Get or Set MQTT client
945
946 AT+UNAME  : Get or Set MQTT Username
947
948 AT+PWD                  : Get or Set MQTT password
949
950 AT+PUBTOPIC  : Get or Set MQTT publish topic
951
952 AT+SUBTOPIC  : Get or Set MQTT subscription topic
953
954
955 (% style="color:#037691" %)**Information**          
956
957 AT+FDR  : Factory Data Reset
958
959 AT+PWORD  : Serial Access Password
960
961
962
963 = ​5.  FAQ =
964
965
966 == 5.1 ​ How to Upgrade Firmware ==
967
968
969 (((
970 User can upgrade the firmware for 1) bug fix, 2) new feature release.
971 )))
972
973 (((
974 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]]
975 )))
976
977 (((
978
979
980 (((
981 (% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
982 )))
983 )))
984
985
986
987 = 6.  Trouble Shooting =
988
989
990 == 6.1  ​Connection problem when uploading firmware ==
991
992
993 (((
994 **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]]
995 )))
996
997 (% class="wikigeneratedid" %)
998 (((
999
1000 )))
1001
1002
1003 == 6.2  AT Command input doesn't work ==
1004
1005
1006 (((
1007 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.
1008
1009
1010 )))
1011
1012
1013 = 7. ​ Order Info =
1014
1015
1016 Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
1017
1018
1019 (% class="wikigeneratedid" %)
1020 (((
1021
1022 )))
1023
1024 = 8.  Packing Info =
1025
1026 (((
1027
1028
1029 (% style="color:#037691" %)**Package Includes**:
1030
1031 * N95S31B NB-IoT Temperature and Humidity Sensor
1032 * External antenna x 1
1033 )))
1034
1035 (((
1036
1037
1038 (% style="color:#037691" %)**Dimension and weight**:
1039
1040 * Device Size: 13.0 x 5 x 4.5 cm
1041 * Device Weight: 150g
1042 * Package Size / pcs : 14.0 x 8x 5 cm
1043 * Weight / pcs : 180g
1044 )))
1045
1046 (((
1047
1048
1049
1050
1051 )))
1052
1053 = 9.  Support =
1054
1055
1056 * 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.
1057 * 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]]

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0