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