Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 131.1
edited by Mengting Qiu
on 2024/04/02 16:44
To version < 116.3 >
edited by Xiaoling
on 2022/07/11 09:42
Change comment: There is no comment for this version

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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
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,8 @@
58 58  * Micro SIM card slot for NB-IoT SIM
59 59  * 8500mAh Battery for long term use
60 60  
69 +
70 +
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
81 +* - B1 @H-FDD: 2100MHz
82 +* - B3 @H-FDD: 1800MHz
83 +* - B8 @H-FDD: 900MHz
84 +* - B5 @H-FDD: 850MHz
85 +* - B20 @H-FDD: 800MHz
86 +* - B28 @H-FDD: 700MHz
77 77  
78 78  (% style="color:#037691" %)**Battery:**
79 79  
... ... @@ -83,9 +83,10 @@
83 83  * Max continuously current: 130mA
84 84  * Max boost current: 2A, 1 second
85 85  
86 -== ​1.4  Applications ==
87 87  
88 88  
98 +== ​1.4  Applications ==
99 +
89 89  * Smart Buildings & Home Automation
90 90  * Logistics and Supply Chain Management
91 91  * Smart Metering
... ... @@ -97,47 +97,44 @@
97 97  ​
98 98  
99 99  
100 -== 1.5  Pin Definitions & Switch ==
111 +== 1.5  Pin Definitions ==
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  
123 +
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.
127 +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
131 +2) Flash: work mode, device starts to work and send out console output for further debug
124 124  )))
125 125  
126 126  
135 +
127 127  === 1.5.3 Reset Button ===
128 128  
129 -
130 130  Press to reboot the device.
131 131  
132 132  
141 +
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
146 +1. When boot the device in flash mode
147 +1. Send an uplink packet
139 139  
140 -2.  Send an uplink packet
141 141  
142 142  
143 143  = 2.  Use N95S31B to communicate with IoT Server =
... ... @@ -158,14 +158,16 @@
158 158  
159 159  )))
160 160  
161 -[[image:1657520100595-569.png]]
169 +[[image:1657350248151-650.png]]
162 162  
163 163  (((
164 164  
165 165  )))
166 166  
175 +
167 167  == 2.2 ​ Configure the N95S31B ==
168 168  
178 +
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 ===
185 +=== 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  
234 +
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  
249 +
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  
260 +**Connection:**
252 252  
253 -(% style="color:blue" %)**Connection:**
262 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
254 254  
255 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
264 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
256 256  
257 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
266 + (% 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]]**
284 +(% 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  
288 +
282 282  === 2.2.5  Use CoAP protocol to uplink data ===
283 283  
291 +(% 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
302 +(% 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
305 +(% 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,11 +315,13 @@
315 315  [[image:1657352185396-303.png]]
316 316  
317 317  
324 +
318 318  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
319 319  
320 320  
321 321  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
322 322  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
330 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
323 323  
324 324  [[image:1657352391268-297.png]]
325 325  
... ... @@ -327,18 +327,18 @@
327 327  [[image:1657352403317-397.png]]
328 328  
329 329  
338 +
330 330  === 2.2.7  Use MQTT protocol to uplink data ===
331 331  
332 -
333 333  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
334 334  
335 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
336 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
337 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
338 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
339 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
340 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
341 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
343 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
344 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
345 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
346 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
347 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
348 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
349 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
342 342  
343 343  [[image:1657352634421-276.png]]
344 344  
... ... @@ -345,19 +345,19 @@
345 345  
346 346  [[image:1657352645687-385.png]]
347 347  
348 -
349 349  (((
350 350  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.
351 351  )))
352 352  
360 +
353 353  (((
354 354  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.
355 355  )))
356 356  
357 357  
366 +
358 358  === 2.2.8  Use TCP protocol to uplink data ===
359 359  
360 -
361 361  This feature is supported since firmware version v110
362 362  
363 363  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -369,9 +369,9 @@
369 369  [[image:1657352914475-252.png]]
370 370  
371 371  
380 +
372 372  === 2.2.9  Change Update Interval ===
373 373  
374 -
375 375  User can use below command to change the (% style="color:green" %)**uplink interval**.
376 376  
377 377  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -380,20 +380,13 @@
380 380  
381 381  )))
382 382  
383 -(((
384 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
385 -)))
386 386  
387 -(((
388 -(% 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).**
389 -)))
390 390  
391 -
392 392  == 2.3  Uplink Payload ==
393 393  
394 394  
395 395  (((
396 -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.
397 +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.
397 397  )))
398 398  
399 399  
... ... @@ -402,7 +402,7 @@
402 402  )))
403 403  
404 404  (((
405 - (% 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.
406 + (% 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.
406 406  )))
407 407  
408 408  
... ... @@ -425,25 +425,24 @@
425 425  
426 426  (% style="color:red" %)
427 427  1. (((
428 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
429 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
429 429  )))
430 430  1. (((
431 -**By default, the device will send an uplink message every 1 hour.**
432 +By default, the device will send an uplink message every 1 hour.
433 +)))
432 432  
433 433  
434 -
435 -)))
436 436  
437 437  === 2.3.1  Payload Analyze ===
438 438  
439 -==== 2.3.1.1  Before Firmware v1.2 ====
439 +N95S31B uplink payload includes in total 21 bytes
440 440  
441 441  
442 -N95S31B uplink payload includes in total 21 bytes.
443 -
444 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
445 -|=(% 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**
446 -|(% 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" %)(((
442 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
443 +|=(% style="width: 60px;" %)(((
444 +**Size(bytes)**
445 +)))|=(% 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**
446 +|(% 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" %)(((
447 447  (((
448 448  Reserve/ Same as NBSN95 CFGMOD=1
449 449  )))
... ... @@ -451,7 +451,7 @@
451 451  (((
452 452  No function here.
453 453  )))
454 -)))|(% style="width:102px" %)(((
454 +)))|(% style="width:77px" %)(((
455 455  (((
456 456  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
457 457  )))
... ... @@ -459,7 +459,7 @@
459 459  (((
460 460  By SHT31
461 461  )))
462 -)))|(% style="width:81px" %)(((
462 +)))|(% style="width:80px" %)(((
463 463  (((
464 464  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
465 465  )))
... ... @@ -470,8 +470,6 @@
470 470  )))
471 471  
472 472  (((
473 -
474 -
475 475  (((
476 476  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
477 477  )))
... ... @@ -481,86 +481,29 @@
481 481  [[image:1657354294009-643.png]]
482 482  
483 483  
484 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
482 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
485 485  
486 -**where:**
484 +* Device ID: 0x724031607457 = 724031607457
485 +* Version: 0x006e=110=1.1.0
487 487  
488 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
487 +* BAT: 0x0ccd = 3277 mV = 3.277V
488 +* Signal: 0x1b = 27
489 +* Model: 0x01 = 1
490 +* 0x00dc000ccc= reserve, ignore in N95S31B
491 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
492 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
489 489  
490 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
491 -
492 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
493 -
494 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
495 -
496 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
497 -
498 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
499 -
500 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
501 -
502 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
503 -
504 504  (((
505 505  
496 +)))
506 506  
498 +(((
507 507  
508 508  )))
509 509  
510 -==== 2.3.1.2 Since Firmware v1.2 ====
511 511  
512 -
513 -In this mode, uplink payload includes 91 bytes in total by default.
514 -
515 -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.
516 -
517 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
518 -|(% 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**
519 -|(% 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 .....
520 -
521 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
522 -
523 -
524 -[[image:image-20220908154949-1.png]]
525 -
526 -
527 -The payload is ASCII string, representative same HEX:
528 -
529 -**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__ **
530 -
531 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
532 -
533 -**where:**
534 -
535 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
536 -
537 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
538 -
539 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
540 -
541 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
542 -
543 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
544 -
545 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
546 -
547 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
548 -
549 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
550 -
551 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
552 -
553 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
554 -
555 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
556 -
557 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
558 -
559 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
560 -
561 561  === 2.3.2  Device ID ===
562 562  
563 -
564 564  (((
565 565  By default, the Device ID equal to the last 6 bytes of IMEI.
566 566  )))
... ... @@ -567,12 +567,10 @@
567 567  
568 568  (((
569 569  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
570 -
571 -
572 572  )))
573 573  
574 574  (((
575 -(% style="color:blue" %)**Example:**
514 +**Example:**
576 576  )))
577 577  
578 578  (((
... ... @@ -580,37 +580,23 @@
580 580  )))
581 581  
582 582  (((
583 -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.
584 -
585 -
522 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
586 586  )))
587 587  
588 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
589 589  
590 590  
591 -By default, the Device ID equal to the last 15 bits of IMEI.
592 -
593 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
594 -
595 -
596 -(% style="color:blue" %)**Example:**
597 -
598 -AT+DEUI=868411056754138
599 -
600 -
601 601  === 2.3.3  Version Info ===
602 602  
603 -
604 604  (((
605 605  These bytes include the hardware and software version.
606 606  )))
607 607  
608 608  (((
609 -**Higher byte:** Specify hardware version: always 0x00 for N95S31B
534 +Higher byte: Specify hardware version: always 0x00 for N95S31B
610 610  )))
611 611  
612 612  (((
613 -**Lower byte:** Specify the software version: 0x6E=110, means firmware version 110
538 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
614 614  )))
615 615  
616 616  (((
... ... @@ -625,9 +625,9 @@
625 625  
626 626  )))
627 627  
553 +
628 628  === 2.3.4  Battery Info ===
629 629  
630 -
631 631  (((
632 632  Ex1: 0x0B45 = 2885mV
633 633  )))
... ... @@ -637,9 +637,9 @@
637 637  )))
638 638  
639 639  
565 +
640 640  === 2.3.5  Signal Strength ===
641 641  
642 -
643 643  (((
644 644  NB-IoT Network signal Strength.
645 645  )))
... ... @@ -669,9 +669,9 @@
669 669  )))
670 670  
671 671  
597 +
672 672  === 2.3.6  Temperature & Humidity ===
673 673  
674 -
675 675  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
676 676  
677 677  [[image:image-20220709161741-3.png]]
... ... @@ -687,16 +687,13 @@
687 687  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
688 688  
689 689  
615 +
690 690  == 2.4  Downlink Payload ==
691 691  
618 +By default, NDDS75 prints the downlink payload to console port.
692 692  
693 -By default, N95S31B prints the downlink payload to console port.
620 +[[image:image-20220709100028-1.png]]
694 694  
695 -(% border="1" style="background-color:#f2f2f2; width:520px" %)
696 -|(% 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)**
697 -|(% style="width:204px" %)TDC(Transmit Time Interval)|(% style="width:80px" %)Any|(% style="width:94px" %)01|(% style="width:150px" %)4
698 -|(% style="width:204px" %)RESET|(% style="width:80px" %)Any|(% style="width:94px" %)04|(% style="width:150px" %)2
699 -|(% style="width:204px" %)INTMOD|(% style="width:80px" %)Any|(% style="width:94px" %)06|(% style="width:150px" %)4
700 700  
701 701  (((
702 702  (% style="color:blue" %)**Examples:**
... ... @@ -731,7 +731,7 @@
731 731  )))
732 732  
733 733  (((
734 -If payload = 0x04FF, it will reset the N95S31B
656 +If payload = 0x04FF, it will reset the NDDS75
735 735  )))
736 736  
737 737  
... ... @@ -742,76 +742,69 @@
742 742  )))
743 743  
744 744  
745 -== 2.5  Humidity and Temperature alarm function ==
746 746  
668 +== 2.5  ​Battery Analysis ==
747 747  
748 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
670 +=== 2.5.1  ​Battery Type ===
749 749  
750 750  
751 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
673 +(((
674 +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.
675 +)))
752 752  
677 +(((
678 +The battery is designed to last for several years depends on the actually use environment and update interval. 
679 +)))
753 753  
754 -² When min=0, and max≠0, Alarm higher than max
681 +(((
682 +The battery related documents as below:
683 +)))
755 755  
756 -² When min≠0, and max=0, Alarm lower than min
685 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
686 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
687 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
757 757  
758 -² When min≠0 and max≠0, Alarm higher than max or lower than min
689 +(((
690 +[[image:image-20220709101450-2.png]]
691 +)))
759 759  
760 760  
761 - (% style="color:blue" %)**Example:**
762 762  
763 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
695 +=== 2.5.2  Power consumption Analyze ===
764 764  
697 +(((
698 +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.
699 +)))
765 765  
766 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
701 +(((
702 +
703 +)))
767 767  
768 -² When min=0, and max≠0, Alarm higher than max
769 769  
770 -² When min≠0, and max=0, Alarm lower than min
706 +=== 2.5.3  ​Battery Note ===
771 771  
772 -² When min≠0 and max≠0, Alarm higher than max or lower than min
708 +(((
709 +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.
710 +)))
773 773  
774 774  
775 -**~ (% style="color:blue" %)Example:(%%)**
776 776  
777 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
714 +=== 2.5.4  Replace the battery ===
778 778  
779 779  
780 -== 2.6 Set the number of data to be uploaded and the recording time ==
717 +(((
718 +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.
719 +)))
781 781  
782 782  
783 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
722 +(((
723 +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).
724 +)))
784 784  
785 -* (% 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)
786 -* (% 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.
787 787  
788 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
789 789  
790 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
791 -
792 -
793 -== 2.7 Read or Clear cached data ==
794 -
795 -
796 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
797 -
798 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
799 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
800 -
801 -[[image:image-20220908163102-2.png]]
802 -
803 -
804 -== 2.8 Battery & Power Consumption ==
805 -
806 -
807 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
808 -
809 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
810 -
811 -
812 812  = 3. ​ Access NB-IoT Module =
813 813  
814 -
815 815  (((
816 816  Users can directly access the AT command set of the NB-IoT module.
817 817  )))
... ... @@ -818,21 +818,19 @@
818 818  
819 819  (((
820 820  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/]] 
821 -
822 -
823 823  )))
824 824  
825 825  [[image:1657333200519-600.png]]
826 826  
827 827  
741 +
828 828  = 4.  Using the AT Commands =
829 829  
830 830  == 4.1  Access AT Commands ==
831 831  
746 +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/]]
832 832  
833 -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]]
834 834  
835 -
836 836  AT+<CMD>?  : Help on <CMD>
837 837  
838 838  AT+<CMD>         : Run <CMD>
... ... @@ -872,29 +872,17 @@
872 872  
873 873  AT+SERVADDR  : Server Address
874 874  
875 -AT+TR      : Get or Set record time
876 876  
877 -AT+APN     : Get or set the APN
789 +(% style="color:#037691" %)**COAP Management**      
878 878  
879 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
791 +AT+URI            : Resource parameters
880 880  
881 -AT+DNSCFG  : Get or Set DNS Server
882 882  
883 -AT+GETSENSORVALUE   : Returns the current sensor measurement
794 +(% style="color:#037691" %)**UDP Management**
884 884  
885 -AT+NOUD      : Get or Set the number of data to be uploaded
796 +AT+CFM          : Upload confirmation mode (only valid for UDP)
886 886  
887 -AT+CDP     : Read or Clear cached data
888 888  
889 -AT+SHTEMP: Get or Set alarm of temp
890 -
891 -AT+SHHUM: Get or Set alarm of moisture
892 -
893 -(% style="color:#037691" %)**COAP Management**      
894 -
895 -AT+URI            : Resource parameters
896 -
897 -
898 898  (% style="color:#037691" %)**MQTT Management**
899 899  
900 900  AT+CLIENT               : Get or Set MQTT client
... ... @@ -915,6 +915,7 @@
915 915  AT+PWORD  : Serial Access Password
916 916  
917 917  
819 +
918 918  = ​5.  FAQ =
919 919  
920 920  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -929,12 +929,15 @@
929 929  )))
930 930  
931 931  (((
932 -Firmware Download：[[https:~~/~~/www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0>>https://www.dropbox.com/sh/fr8w23rb951512i/AACSJeGQg-7ZjKhAI_Sn57H6a?dl=0]]
834 +
933 933  
934 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
836 +(((
837 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
935 935  )))
839 +)))
936 936  
937 937  
842 +
938 938  = 6.  Trouble Shooting =
939 939  
940 940  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -944,10 +944,14 @@
944 944  **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]]
945 945  )))
946 946  
852 +(% class="wikigeneratedid" %)
853 +(((
854 +
855 +)))
947 947  
857 +
948 948  == 6.2  AT Command input doesn't work ==
949 949  
950 -
951 951  (((
952 952  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.
953 953  
... ... @@ -954,12 +954,7 @@
954 954  
955 955  )))
956 956  
957 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
958 958  
959 -
960 -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]]//**.
961 -
962 -
963 963  = 7. ​ Order Info =
964 964  
965 965  
... ... @@ -966,6 +966,11 @@
966 966  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
967 967  
968 968  
873 +(% class="wikigeneratedid" %)
874 +(((
875 +
876 +)))
877 +
969 969  = 8.  Packing Info =
970 970  
971 971  (((
... ... @@ -988,11 +988,14 @@
988 988  * Weight / pcs : 180g
989 989  )))
990 990  
900 +(((
901 +
991 991  
992 992  
904 +
905 +)))
906 +
993 993  = 9.  Support =
994 994  
995 -
996 996  * 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.
997 -
998 998  * 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]]
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
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