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