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