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

Applications

Navigation

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