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