Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 130.18 >
edited by Xiaoling
on 2023/12/14 10:57
To version < 118.1 >
edited by Xiaoling
on 2022/07/11 14:15
>
Change comment: Uploaded new attachment "1657520100595-569.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual
Content
... ... @@ -19,6 +19,8 @@
19 19  
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 +(((
23 +
22 22  
23 23  (((
24 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*.
... ... @@ -37,16 +37,22 @@
37 37  )))
38 38  
39 39  (((
42 +
43 +)))
44 +
45 +(((
40 40  ~* make sure you have NB-IoT coverage locally.
41 41  )))
42 42  
49 +
50 +)))
43 43  
44 44  [[image:1657348284168-431.png]]
45 45  
46 46  
55 +
47 47  == 1.2 ​ Features ==
48 48  
49 -
50 50  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
51 51  * Monitor Temperature & Humidity via SHT31
52 52  * AT Commands to change parameters
... ... @@ -58,6 +58,7 @@
58 58  * Micro SIM card slot for NB-IoT SIM
59 59  * 8500mAh Battery for long term use
60 60  
69 +
61 61  == 1.3  Specification ==
62 62  
63 63  
... ... @@ -68,12 +68,12 @@
68 68  
69 69  (% style="color:#037691" %)**NB-IoT Spec:**
70 70  
71 -* B1 @H-FDD: 2100MHz
72 -* B3 @H-FDD: 1800MHz
73 -* B8 @H-FDD: 900MHz
74 -* B5 @H-FDD: 850MHz
75 -* B20 @H-FDD: 800MHz
76 -* B28 @H-FDD: 700MHz
80 +* - B1 @H-FDD: 2100MHz
81 +* - B3 @H-FDD: 1800MHz
82 +* - B8 @H-FDD: 900MHz
83 +* - B5 @H-FDD: 850MHz
84 +* - B20 @H-FDD: 800MHz
85 +* - B28 @H-FDD: 700MHz
77 77  
78 78  (% style="color:#037691" %)**Battery:**
79 79  
... ... @@ -83,9 +83,9 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
95 +
86 86  == ​1.4  Applications ==
87 87  
88 -
89 89  * Smart Buildings & Home Automation
90 90  * Logistics and Supply Chain Management
91 91  * Smart Metering
... ... @@ -99,47 +99,43 @@
99 99  
100 100  == 1.5  Pin Definitions & Switch ==
101 101  
102 -
103 103  N95S31B use the mother board from NBSN95 which as below.
104 104  
105 -
106 106  [[image:image-20220709144723-1.png]]
107 107  
108 108  
109 109  === 1.5.1 Jumper JP2 ===
110 110  
111 -
112 112  Power on Device when put this jumper.
113 113  
114 114  
121 +
115 115  === 1.5.2 BOOT MODE / SW1 ===
116 116  
117 -
118 118  (((
119 -**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.
125 +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.
120 120  )))
121 121  
122 122  (((
123 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
129 +2) Flash: work mode, device starts to work and send out console output for further debug
124 124  )))
125 125  
126 126  
133 +
127 127  === 1.5.3 Reset Button ===
128 128  
129 -
130 130  Press to reboot the device.
131 131  
132 132  
139 +
133 133  === 1.5.4 LED ===
134 134  
135 -
136 136  It will flash:
137 137  
138 -1.  When boot the device in flash mode
144 +1. When boot the device in flash mode
145 +1. Send an uplink packet
139 139  
140 -2.  Send an uplink packet
141 141  
142 -
143 143  = 2.  Use N95S31B to communicate with IoT Server =
144 144  
145 145  == 2.1  How it works ==
... ... @@ -158,14 +158,16 @@
158 158  
159 159  )))
160 160  
161 -[[image:1657520100595-569.png]]
166 +[[image:1657350248151-650.png]]
162 162  
163 163  (((
164 164  
165 165  )))
166 166  
172 +
167 167  == 2.2 ​ Configure the N95S31B ==
168 168  
175 +
169 169  === 2.2.1  Power On N95S31B ===
170 170  
171 171  
... ... @@ -172,7 +172,7 @@
172 172  [[image:image-20220709150546-2.png]]
173 173  
174 174  
175 -=== 2.2.2 Test Requirement ===
182 +=== 2.2.1 Test Requirement ===
176 176  
177 177  
178 178  (((
... ... @@ -221,9 +221,9 @@
221 221  [[image:1657350625843-586.png]]
222 222  
223 223  
231 +
224 224  === 2.2.3  Insert SIM card ===
225 225  
226 -
227 227  (((
228 228  Insert the NB-IoT Card get from your provider.
229 229  )))
... ... @@ -236,29 +236,26 @@
236 236  [[image:1657351240556-536.png]]
237 237  
238 238  
246 +
239 239  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
240 240  
241 -
242 242  (((
243 243  (((
244 244  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.
245 -
246 -
247 247  )))
248 248  )))
249 249  
250 250  [[image:1657351312545-300.png]]
251 251  
257 +**Connection:**
252 252  
253 -(% style="color:blue" %)**Connection:**
259 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
254 254  
255 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
261 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
256 256  
257 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
263 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
258 258  
259 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
260 260  
261 -
262 262  In the PC, use below serial tool settings:
263 263  
264 264  * Baud:  (% style="color:green" %)**9600**
... ... @@ -273,18 +273,17 @@
273 273  
274 274  [[image:1657329814315-101.png]]
275 275  
276 -
277 277  (((
278 -(% 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]]**
281 +(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
279 279  )))
280 280  
281 281  
285 +
282 282  === 2.2.5  Use CoAP protocol to uplink data ===
283 283  
288 +(% 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/]]
284 284  
285 -(% 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/]]**
286 286  
287 -
288 288  (((
289 289  **Use below commands:**
290 290  )))
... ... @@ -293,10 +293,10 @@
293 293  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
294 294  )))
295 295  * (((
296 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
299 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
297 297  )))
298 298  * (((
299 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
302 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
300 300  )))
301 301  
302 302  (((
... ... @@ -315,6 +315,7 @@
315 315  [[image:1657352185396-303.png]]
316 316  
317 317  
321 +
318 318  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
319 319  
320 320  
... ... @@ -328,18 +328,18 @@
328 328  [[image:1657352403317-397.png]]
329 329  
330 330  
335 +
331 331  === 2.2.7  Use MQTT protocol to uplink data ===
332 332  
333 -
334 334  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
335 335  
336 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
337 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
338 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
339 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
340 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
341 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
342 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
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
343 343  
344 344  [[image:1657352634421-276.png]]
345 345  
... ... @@ -346,19 +346,19 @@
346 346  
347 347  [[image:1657352645687-385.png]]
348 348  
349 -
350 350  (((
351 351  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.
352 352  )))
353 353  
357 +
354 354  (((
355 355  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.
356 356  )))
357 357  
358 358  
363 +
359 359  === 2.2.8  Use TCP protocol to uplink data ===
360 360  
361 -
362 362  This feature is supported since firmware version v110
363 363  
364 364  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -370,9 +370,9 @@
370 370  [[image:1657352914475-252.png]]
371 371  
372 372  
377 +
373 373  === 2.2.9  Change Update Interval ===
374 374  
375 -
376 376  User can use below command to change the (% style="color:green" %)**uplink interval**.
377 377  
378 378  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -381,20 +381,13 @@
381 381  
382 382  )))
383 383  
384 -(((
385 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
386 -)))
387 387  
388 -(((
389 -(% 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).**
390 -)))
391 391  
392 -
393 393  == 2.3  Uplink Payload ==
394 394  
395 395  
396 396  (((
397 -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.
394 +NBSN95 has different working mode for the connections of different type 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.
398 398  )))
399 399  
400 400  
... ... @@ -403,7 +403,7 @@
403 403  )))
404 404  
405 405  (((
406 - (% 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.
403 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
407 407  )))
408 408  
409 409  
... ... @@ -426,25 +426,23 @@
426 426  
427 427  (% style="color:red" %)
428 428  1. (((
429 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
426 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
430 430  )))
431 431  1. (((
432 -**By default, the device will send an uplink message every 1 hour.**
433 -
434 -
435 -
429 +By default, the device will send an uplink message every 1 hour.
436 436  )))
437 437  
432 +
438 438  === 2.3.1  Payload Analyze ===
439 439  
440 -==== 2.3.1.1  Before Firmware v1.2 ====
435 +N95S31B uplink payload includes in total 21 bytes
441 441  
442 442  
443 -N95S31B uplink payload includes in total 21 bytes.
444 -
445 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
446 -|=(% style="width: 50px;background-color:#D9E2F3" %)**Size(bytes)**|=(% style="width: 45px;background-color:#D9E2F3" %)**6**|=(% style="width: 25px;background-color:#D9E2F3" %)2|=(% style="width: 25px;background-color:#D9E2F3" %)**2**|=(% style="width: 65px;background-color:#D9E2F3" %)**1**|=(% style="width: 50px;background-color:#D9E2F3" %)1|=(% style="width: 120px;background-color:#D9E2F3" %)5|=(% style="width: 70px;background-color:#D9E2F3" %)**2**|=(% style="width: 70px;background-color:#D9E2F3" %)**2**
447 -|(% 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" %)(((
438 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
439 +|=(% style="width: 60px;" %)(((
440 +**Size(bytes)**
441 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
442 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
448 448  (((
449 449  Reserve/ Same as NBSN95 CFGMOD=1
450 450  )))
... ... @@ -452,7 +452,7 @@
452 452  (((
453 453  No function here.
454 454  )))
455 -)))|(% style="width:102px" %)(((
450 +)))|(% style="width:77px" %)(((
456 456  (((
457 457  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
458 458  )))
... ... @@ -460,7 +460,7 @@
460 460  (((
461 461  By SHT31
462 462  )))
463 -)))|(% style="width:81px" %)(((
458 +)))|(% style="width:80px" %)(((
464 464  (((
465 465  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
466 466  )))
... ... @@ -471,8 +471,6 @@
471 471  )))
472 472  
473 473  (((
474 -
475 -
476 476  (((
477 477  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
478 478  )))
... ... @@ -482,86 +482,29 @@
482 482  [[image:1657354294009-643.png]]
483 483  
484 484  
485 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
478 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
486 486  
487 -**where:**
480 +* Device ID: 0x724031607457 = 724031607457
481 +* Version: 0x006e=110=1.1.0
488 488  
489 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
483 +* BAT: 0x0ccd = 3277 mV = 3.277V
484 +* Signal: 0x1b = 27
485 +* Model: 0x01 = 1
486 +* 0x00dc000ccc= reserve, ignore in N95S31B
487 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
488 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
490 490  
491 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
492 -
493 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
494 -
495 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
496 -
497 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
498 -
499 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
500 -
501 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
502 -
503 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
504 -
505 505  (((
506 506  
492 +)))
507 507  
494 +(((
508 508  
509 509  )))
510 510  
511 -==== 2.3.1.2 Since Firmware v1.2 ====
512 512  
513 -
514 -In this mode, uplink payload includes 91 bytes in total by default.
515 -
516 -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.
517 -
518 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
519 -|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:55px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:35px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:20px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:30px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**4**
520 -|(% 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 .....
521 -
522 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
523 -
524 -
525 -[[image:image-20220908154949-1.png]]
526 -
527 -
528 -The payload is ASCII string, representative same HEX:
529 -
530 -**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__ **
531 -
532 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
533 -
534 -**where:**
535 -
536 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
537 -
538 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
539 -
540 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
541 -
542 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
543 -
544 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
545 -
546 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
547 -
548 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
549 -
550 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
551 -
552 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
553 -
554 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
555 -
556 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
557 -
558 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
559 -
560 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
561 -
562 562  === 2.3.2  Device ID ===
563 563  
564 -
565 565  (((
566 566  By default, the Device ID equal to the last 6 bytes of IMEI.
567 567  )))
... ... @@ -568,12 +568,10 @@
568 568  
569 569  (((
570 570  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
571 -
572 -
573 573  )))
574 574  
575 575  (((
576 -(% style="color:blue" %)**Example:**
510 +**Example:**
577 577  )))
578 578  
579 579  (((
... ... @@ -581,37 +581,23 @@
581 581  )))
582 582  
583 583  (((
584 -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.
585 -
586 -
518 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
587 587  )))
588 588  
589 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
590 590  
591 591  
592 -By default, the Device ID equal to the last 15 bits of IMEI.
593 -
594 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
595 -
596 -
597 -(% style="color:blue" %)**Example:**
598 -
599 -AT+DEUI=868411056754138
600 -
601 -
602 602  === 2.3.3  Version Info ===
603 603  
604 -
605 605  (((
606 606  These bytes include the hardware and software version.
607 607  )))
608 608  
609 609  (((
610 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B
530 +Higher byte: Specify hardware version: always 0x00 for N95S31B
611 611  )))
612 612  
613 613  (((
614 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
534 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
615 615  )))
616 616  
617 617  (((
... ... @@ -626,9 +626,9 @@
626 626  
627 627  )))
628 628  
549 +
629 629  === 2.3.4  Battery Info ===
630 630  
631 -
632 632  (((
633 633  Ex1: 0x0B45 = 2885mV
634 634  )))
... ... @@ -638,9 +638,9 @@
638 638  )))
639 639  
640 640  
561 +
641 641  === 2.3.5  Signal Strength ===
642 642  
643 -
644 644  (((
645 645  NB-IoT Network signal Strength.
646 646  )))
... ... @@ -670,9 +670,9 @@
670 670  )))
671 671  
672 672  
593 +
673 673  === 2.3.6  Temperature & Humidity ===
674 674  
675 -
676 676  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
677 677  
678 678  [[image:image-20220709161741-3.png]]
... ... @@ -688,16 +688,13 @@
688 688  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
689 689  
690 690  
611 +
691 691  == 2.4  Downlink Payload ==
692 692  
614 +By default, NDDS75 prints the downlink payload to console port.
693 693  
694 -By default, N95S31B prints the downlink payload to console port.
616 +[[image:image-20220709100028-1.png]]
695 695  
696 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
697 -|(% style="background-color:#d9e2f3; color:#0070c0; width:200px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:50px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:170px" %)**Downlink payload size(bytes)**
698 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4
699 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2
700 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4
701 701  
702 702  (((
703 703  (% style="color:blue" %)**Examples:**
... ... @@ -732,7 +732,7 @@
732 732  )))
733 733  
734 734  (((
735 -If payload = 0x04FF, it will reset the N95S31B
652 +If payload = 0x04FF, it will reset the NDDS75
736 736  )))
737 737  
738 738  
... ... @@ -743,76 +743,69 @@
743 743  )))
744 744  
745 745  
746 -== 2.5  Humidity and Temperature alarm function ==
747 747  
664 +== 2.5  ​Battery Analysis ==
748 748  
749 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
666 +=== 2.5.1  ​Battery Type ===
750 750  
751 751  
752 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
669 +(((
670 +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.
671 +)))
753 753  
673 +(((
674 +The battery is designed to last for several years depends on the actually use environment and update interval. 
675 +)))
754 754  
755 -² When min=0, and max≠0, Alarm higher than max
677 +(((
678 +The battery related documents as below:
679 +)))
756 756  
757 -² When min≠0, and max=0, Alarm lower than min
681 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
682 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
683 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
758 758  
759 -² When min≠0 and max≠0, Alarm higher than max or lower than min
685 +(((
686 +[[image:image-20220709101450-2.png]]
687 +)))
760 760  
761 761  
762 - (% style="color:blue" %)**Example:**
763 763  
764 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
691 +=== 2.5.2  Power consumption Analyze ===
765 765  
693 +(((
694 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
695 +)))
766 766  
767 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
697 +(((
698 +
699 +)))
768 768  
769 -² When min=0, and max≠0, Alarm higher than max
770 770  
771 -² When min≠0, and max=0, Alarm lower than min
702 +=== 2.5.3  ​Battery Note ===
772 772  
773 -² When min≠0 and max≠0, Alarm higher than max or lower than min
704 +(((
705 +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.
706 +)))
774 774  
775 775  
776 -**~ (% style="color:blue" %)Example:(%%)**
777 777  
778 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
710 +=== 2.5.4  Replace the battery ===
779 779  
780 780  
781 -== 2.6 Set the number of data to be uploaded and the recording time ==
713 +(((
714 +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.
715 +)))
782 782  
783 783  
784 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
718 +(((
719 +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).
720 +)))
785 785  
786 -* (% 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)
787 -* (% 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.
788 788  
789 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
790 790  
791 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
792 -
793 -
794 -== 2.7 Read or Clear cached data ==
795 -
796 -
797 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
798 -
799 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
800 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
801 -
802 -[[image:image-20220908163102-2.png]]
803 -
804 -
805 -== 2.8 Battery & Power Consumption ==
806 -
807 -
808 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
809 -
810 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
811 -
812 -
813 813  = 3. ​ Access NB-IoT Module =
814 814  
815 -
816 816  (((
817 817  Users can directly access the AT command set of the NB-IoT module.
818 818  )))
... ... @@ -819,21 +819,19 @@
819 819  
820 820  (((
821 821  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/]] 
822 -
823 -
824 824  )))
825 825  
826 826  [[image:1657333200519-600.png]]
827 827  
828 828  
737 +
829 829  = 4.  Using the AT Commands =
830 830  
831 831  == 4.1  Access AT Commands ==
832 832  
742 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
833 833  
834 -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]]
835 835  
836 -
837 837  AT+<CMD>?  : Help on <CMD>
838 838  
839 839  AT+<CMD>         : Run <CMD>
... ... @@ -873,24 +873,7 @@
873 873  
874 874  AT+SERVADDR  : Server Address
875 875  
876 -AT+TR      : Get or Set record time
877 877  
878 -AT+APN     : Get or set the APN
879 -
880 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
881 -
882 -AT+DNSCFG  : Get or Set DNS Server
883 -
884 -AT+GETSENSORVALUE   : Returns the current sensor measurement
885 -
886 -AT+NOUD      : Get or Set the number of data to be uploaded
887 -
888 -AT+CDP     : Read or Clear cached data
889 -
890 -AT+SHTEMP: Get or Set alarm of temp
891 -
892 -AT+SHHUM: Get or Set alarm of moisture
893 -
894 894  (% style="color:#037691" %)**COAP Management**      
895 895  
896 896  AT+URI            : Resource parameters
... ... @@ -921,6 +921,7 @@
921 921  AT+PWORD  : Serial Access Password
922 922  
923 923  
815 +
924 924  = ​5.  FAQ =
925 925  
926 926  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -935,12 +935,15 @@
935 935  )))
936 936  
937 937  (((
938 -Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
830 +
939 939  
940 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
832 +(((
833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
941 941  )))
835 +)))
942 942  
943 943  
838 +
944 944  = 6.  Trouble Shooting =
945 945  
946 946  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -950,10 +950,14 @@
950 950  **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]]
951 951  )))
952 952  
848 +(% class="wikigeneratedid" %)
849 +(((
850 +
851 +)))
953 953  
853 +
954 954  == 6.2  AT Command input doesn't work ==
955 955  
956 -
957 957  (((
958 958  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.
959 959  
... ... @@ -960,12 +960,7 @@
960 960  
961 961  )))
962 962  
963 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
964 964  
965 -
966 -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]]//**.
967 -
968 -
969 969  = 7. ​ Order Info =
970 970  
971 971  
... ... @@ -972,6 +972,11 @@
972 972  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
973 973  
974 974  
869 +(% class="wikigeneratedid" %)
870 +(((
871 +
872 +)))
873 +
975 975  = 8.  Packing Info =
976 976  
977 977  (((
... ... @@ -994,12 +994,14 @@
994 994  * Weight / pcs : 180g
995 995  )))
996 996  
896 +(((
897 +
997 997  
998 998  
900 +
901 +)))
902 +
999 999  = 9.  Support =
1000 1000  
1001 -
1002 1002  * 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.
1003 -
1004 1004  * 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]]
1005 -
image-20220908154949-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -29.7 KB
Content
image-20221009001045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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