Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 118.4 >
edited by Xiaoling
on 2022/07/12 17:29
To version < 130.1 >
edited by Bei Jinggeng
on 2023/04/19 14:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
58 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -67,7 +67,6 @@
67 67  * 8500mAh Battery for long term use
68 68  
69 69  
70 -
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -78,12 +78,12 @@
78 78  
79 79  (% style="color:#037691" %)**NB-IoT Spec:**
80 80  
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
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
87 87  
88 88  (% style="color:#037691" %)**Battery:**
89 89  
... ... @@ -94,9 +94,9 @@
94 94  * Max boost current: 2A, 1 second
95 95  
96 96  
97 -
98 98  == ​1.4  Applications ==
99 99  
99 +
100 100  * Smart Buildings & Home Automation
101 101  * Logistics and Supply Chain Management
102 102  * Smart Metering
... ... @@ -110,43 +110,47 @@
110 110  
111 111  == 1.5  Pin Definitions & Switch ==
112 112  
113 +
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
116 +
115 115  [[image:image-20220709144723-1.png]]
116 116  
117 117  
118 118  === 1.5.1 Jumper JP2 ===
119 119  
122 +
120 120  Power on Device when put this jumper.
121 121  
122 122  
123 -
124 124  === 1.5.2 BOOT MODE / SW1 ===
125 125  
128 +
126 126  (((
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.
130 +**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.
128 128  )))
129 129  
130 130  (((
131 -2) Flash: work mode, device starts to work and send out console output for further debug
134 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
132 132  )))
133 133  
134 134  
135 -
136 136  === 1.5.3 Reset Button ===
137 137  
140 +
138 138  Press to reboot the device.
139 139  
140 140  
141 -
142 142  === 1.5.4 LED ===
143 143  
146 +
144 144  It will flash:
145 145  
146 -1. When boot the device in flash mode
147 -1. Send an uplink packet
149 +1.  When boot the device in flash mode
148 148  
151 +2.  Send an uplink packet
149 149  
153 +
150 150  = 2.  Use N95S31B to communicate with IoT Server =
151 151  
152 152  == 2.1  How it works ==
... ... @@ -174,7 +174,6 @@
174 174  
175 175  == 2.2 ​ Configure the N95S31B ==
176 176  
177 -
178 178  === 2.2.1  Power On N95S31B ===
179 179  
180 180  
... ... @@ -181,7 +181,7 @@
181 181  [[image:image-20220709150546-2.png]]
182 182  
183 183  
184 -=== 2.2.1 Test Requirement ===
187 +=== 2.2.2 Test Requirement ===
185 185  
186 186  
187 187  (((
... ... @@ -230,9 +230,9 @@
230 230  [[image:1657350625843-586.png]]
231 231  
232 232  
233 -
234 234  === 2.2.3  Insert SIM card ===
235 235  
238 +
236 236  (((
237 237  Insert the NB-IoT Card get from your provider.
238 238  )))
... ... @@ -245,26 +245,29 @@
245 245  [[image:1657351240556-536.png]]
246 246  
247 247  
248 -
249 249  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
250 250  
253 +
251 251  (((
252 252  (((
253 253  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.
257 +
258 +
254 254  )))
255 255  )))
256 256  
257 257  [[image:1657351312545-300.png]]
258 258  
259 -**Connection:**
260 260  
261 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
265 +(% style="color:blue" %)**Connection:**
262 262  
263 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
267 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
264 264  
265 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
269 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
266 266  
271 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
267 267  
273 +
268 268  In the PC, use below serial tool settings:
269 269  
270 270  * Baud:  (% style="color:green" %)**9600**
... ... @@ -279,17 +279,18 @@
279 279  
280 280  [[image:1657329814315-101.png]]
281 281  
288 +
282 282  (((
283 -(% 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/]]
290 +(% 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 284  )))
285 285  
286 286  
287 -
288 288  === 2.2.5  Use CoAP protocol to uplink data ===
289 289  
290 -(% 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/]]
291 291  
297 +(% 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/]]**
292 292  
299 +
293 293  (((
294 294  **Use below commands:**
295 295  )))
... ... @@ -298,10 +298,10 @@
298 298  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
299 299  )))
300 300  * (((
301 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
308 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
302 302  )))
303 303  * (((
304 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
311 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
305 305  )))
306 306  
307 307  (((
... ... @@ -320,7 +320,6 @@
320 320  [[image:1657352185396-303.png]]
321 321  
322 322  
323 -
324 324  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
325 325  
326 326  
... ... @@ -334,18 +334,18 @@
334 334  [[image:1657352403317-397.png]]
335 335  
336 336  
337 -
338 338  === 2.2.7  Use MQTT protocol to uplink data ===
339 339  
345 +
340 340  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
341 341  
342 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
343 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
344 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
345 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
346 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
347 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
348 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
348 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
349 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
350 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
351 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
352 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
353 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
354 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
349 349  
350 350  [[image:1657352634421-276.png]]
351 351  
... ... @@ -352,6 +352,7 @@
352 352  
353 353  [[image:1657352645687-385.png]]
354 354  
361 +
355 355  (((
356 356  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.
357 357  )))
... ... @@ -362,9 +362,9 @@
362 362  )))
363 363  
364 364  
365 -
366 366  === 2.2.8  Use TCP protocol to uplink data ===
367 367  
374 +
368 368  This feature is supported since firmware version v110
369 369  
370 370  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -376,9 +376,9 @@
376 376  [[image:1657352914475-252.png]]
377 377  
378 378  
379 -
380 380  === 2.2.9  Change Update Interval ===
381 381  
388 +
382 382  User can use below command to change the (% style="color:green" %)**uplink interval**.
383 383  
384 384  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -387,13 +387,20 @@
387 387  
388 388  )))
389 389  
397 +(((
398 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
399 +)))
390 390  
401 +(((
402 +(% 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).**
403 +)))
391 391  
405 +
392 392  == 2.3  Uplink Payload ==
393 393  
394 394  
395 395  (((
396 -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.
410 +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 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 NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
419 + (% 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 406  )))
407 407  
408 408  
... ... @@ -425,26 +425,26 @@
425 425  
426 426  (% style="color:red" %)
427 427  1. (((
428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
442 +**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.
445 +**By default, the device will send an uplink message every 1 hour.**
432 432  
433 433  
434 -
435 435  
436 436  )))
437 437  
438 438  === 2.3.1  Payload Analyze ===
439 439  
453 +==== 2.3.1.1  Before Firmware v1.2 ====
454 +
455 +
440 440  N95S31B uplink payload includes in total 21 bytes
441 441  
442 442  
443 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
444 -|=(% style="width: 60px;" %)(((
445 -**Size(bytes)**
446 -)))|=(% 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**
447 -|(% 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" %)(((
459 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
460 +|=(% 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**
461 +|(% 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" %)(((
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:77px" %)(((
469 +)))|(% style="width:102px" %)(((
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:80px" %)(((
477 +)))|(% style="width:81px" %)(((
464 464  (((
465 465  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
466 466  )))
... ... @@ -471,6 +471,8 @@
471 471  )))
472 472  
473 473  (((
488 +
489 +
474 474  (((
475 475  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
476 476  )))
... ... @@ -480,29 +480,88 @@
480 480  [[image:1657354294009-643.png]]
481 481  
482 482  
483 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
499 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
484 484  
485 -* Device ID: 0x724031607457 = 724031607457
486 -* Version: 0x006e=110=1.1.0
501 +**where:**
487 487  
488 -* BAT: 0x0ccd = 3277 mV = 3.277V
489 -* Signal: 0x1b = 27
490 -* Model: 0x01 = 1
491 -* 0x00dc000ccc= reserve, ignore in N95S31B
492 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
493 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
503 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
494 494  
505 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
506 +
507 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
508 +
509 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
510 +
511 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
512 +
513 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
514 +
515 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
516 +
517 +* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
518 +
495 495  (((
496 496  
497 -)))
498 498  
499 -(((
500 500  
501 501  )))
502 502  
525 +==== 2.3.1.2 Since Firmware v1.2 ====
503 503  
527 +
528 +In this mode, uplink payload includes 91 bytes in total by default.
529 +
530 +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.
531 +
532 +
533 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
534 +|=(% 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**
535 +|=(% 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 .....
536 +
537 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
538 +
539 +
540 +[[image:image-20220908154949-1.png]]
541 +
542 +
543 +The payload is ASCII string, representative same HEX:
544 +
545 +**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__ **
546 +
547 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
548 +
549 +**where:**
550 +
551 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
552 +
553 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
554 +
555 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
556 +
557 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
558 +
559 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
560 +
561 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
562 +
563 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
564 +
565 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
566 +
567 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
568 +
569 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
570 +
571 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
572 +
573 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
574 +
575 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
576 +
577 +
504 504  === 2.3.2  Device ID ===
505 505  
580 +
506 506  (((
507 507  By default, the Device ID equal to the last 6 bytes of IMEI.
508 508  )))
... ... @@ -509,10 +509,12 @@
509 509  
510 510  (((
511 511  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
587 +
588 +
512 512  )))
513 513  
514 514  (((
515 -**Example:**
592 +(% style="color:blue" %)**Example:**
516 516  )))
517 517  
518 518  (((
... ... @@ -520,13 +520,27 @@
520 520  )))
521 521  
522 522  (((
523 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
600 +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.
601 +
602 +
524 524  )))
525 525  
605 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
526 526  
527 527  
608 +By default, the Device ID equal to the last 15 bits of IMEI.
609 +
610 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
611 +
612 +
613 +(% style="color:blue" %)**Example:**
614 +
615 +AT+DEUI=868411056754138
616 +
617 +
528 528  === 2.3.3  Version Info ===
529 529  
620 +
530 530  (((
531 531  These bytes include the hardware and software version.
532 532  )))
... ... @@ -551,9 +551,9 @@
551 551  
552 552  )))
553 553  
554 -
555 555  === 2.3.4  Battery Info ===
556 556  
647 +
557 557  (((
558 558  Ex1: 0x0B45 = 2885mV
559 559  )))
... ... @@ -563,9 +563,9 @@
563 563  )))
564 564  
565 565  
566 -
567 567  === 2.3.5  Signal Strength ===
568 568  
659 +
569 569  (((
570 570  NB-IoT Network signal Strength.
571 571  )))
... ... @@ -595,9 +595,9 @@
595 595  )))
596 596  
597 597  
598 -
599 599  === 2.3.6  Temperature & Humidity ===
600 600  
691 +
601 601  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
602 602  
603 603  [[image:image-20220709161741-3.png]]
... ... @@ -613,11 +613,11 @@
613 613  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
614 614  
615 615  
616 -
617 617  == 2.4  Downlink Payload ==
618 618  
619 -By default, NDDS75 prints the downlink payload to console port.
620 620  
710 +By default, N95S31B prints the downlink payload to console port.
711 +
621 621  [[image:image-20220709100028-1.png]]
622 622  
623 623  
... ... @@ -654,7 +654,7 @@
654 654  )))
655 655  
656 656  (((
657 -If payload = 0x04FF, it will reset the NDDS75
748 +If payload = 0x04FF, it will reset the N95S31B
658 658  )))
659 659  
660 660  
... ... @@ -665,69 +665,76 @@
665 665  )))
666 666  
667 667  
759 +== 2.5  Humidity and Temperature alarm function ==
668 668  
669 -== 2.5  ​Battery Analysis ==
670 670  
671 -=== 2.5.1  ​Battery Type ===
762 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
672 672  
673 673  
674 -(((
675 -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.
676 -)))
765 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
677 677  
678 -(((
679 -The battery is designed to last for several years depends on the actually use environment and update interval. 
680 -)))
681 681  
682 -(((
683 -The battery related documents as below:
684 -)))
768 +² When min=0, and max≠0, Alarm higher than max
685 685  
686 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
687 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
688 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
770 +² When min≠0, and max=0, Alarm lower than min
689 689  
690 -(((
691 -[[image:image-20220709101450-2.png]]
692 -)))
772 +² When min≠0 and max≠0, Alarm higher than max or lower than min
693 693  
694 694  
775 + (% style="color:blue" %)**Example:**
695 695  
696 -=== 2.5.2  Power consumption Analyze ===
777 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
697 697  
698 -(((
699 -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.
700 -)))
701 701  
702 -(((
703 -
704 -)))
780 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
705 705  
782 +² When min=0, and max≠0, Alarm higher than max
706 706  
707 -=== 2.5.3  ​Battery Note ===
784 +² When min≠0, and max=0, Alarm lower than min
708 708  
709 -(((
710 -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.
711 -)))
786 +² When min≠0 and max≠0, Alarm higher than max or lower than min
712 712  
713 713  
789 +**~ (% style="color:blue" %)Example:(%%)**
714 714  
715 -=== 2.5.4  Replace the battery ===
791 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
716 716  
717 717  
718 -(((
719 -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.
720 -)))
794 +== 2.6 Set the number of data to be uploaded and the recording time ==
721 721  
722 722  
723 -(((
724 -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).
725 -)))
797 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
726 726  
799 +* (% 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)
800 +* (% 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.
727 727  
802 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
728 728  
804 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
805 +
806 +
807 +== 2.7 Read or Clear cached data ==
808 +
809 +
810 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
811 +
812 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
813 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
814 +
815 +[[image:image-20220908163102-2.png]]
816 +
817 +
818 +== 2.8 Battery & Power Consumption ==
819 +
820 +
821 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
822 +
823 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
824 +
825 +
729 729  = 3. ​ Access NB-IoT Module =
730 730  
828 +
731 731  (((
732 732  Users can directly access the AT command set of the NB-IoT module.
733 733  )))
... ... @@ -734,19 +734,21 @@
734 734  
735 735  (((
736 736  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/]] 
835 +
836 +
737 737  )))
738 738  
739 739  [[image:1657333200519-600.png]]
740 740  
741 741  
742 -
743 743  = 4.  Using the AT Commands =
744 744  
745 745  == 4.1  Access AT Commands ==
746 746  
747 -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/]]
748 748  
847 +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]]
749 749  
849 +
750 750  AT+<CMD>?  : Help on <CMD>
751 751  
752 752  AT+<CMD>         : Run <CMD>
... ... @@ -786,7 +786,24 @@
786 786  
787 787  AT+SERVADDR  : Server Address
788 788  
889 +AT+TR      : Get or Set record time
789 789  
891 +AT+APN     : Get or set the APN
892 +
893 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
894 +
895 +AT+DNSCFG  : Get or Set DNS Server
896 +
897 +AT+GETSENSORVALUE   : Returns the current sensor measurement
898 +
899 +AT+NOUD      : Get or Set the number of data to be uploaded
900 +
901 +AT+CDP     : Read or Clear cached data
902 +
903 +AT+SHTEMP: Get or Set alarm of temp
904 +
905 +AT+SHHUM: Get or Set alarm of moisture
906 +
790 790  (% style="color:#037691" %)**COAP Management**      
791 791  
792 792  AT+URI            : Resource parameters
... ... @@ -817,7 +817,6 @@
817 817  AT+PWORD  : Serial Access Password
818 818  
819 819  
820 -
821 821  = ​5.  FAQ =
822 822  
823 823  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -832,15 +832,14 @@
832 832  )))
833 833  
834 834  (((
835 -
951 +firmware：[[Dropbox - Firmware - 简化您的生活>>url:https://www.dropbox.com/sh/ap9k142hfnlh5w6/AACJeN_St0ryUl3AggrNB5x0a/N95S31B/Firmware?dl=0&subfolder_nav_tracking=1]]
836 836  
837 837  (((
838 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
954 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
839 839  )))
840 840  )))
841 841  
842 842  
843 -
844 844  = 6.  Trouble Shooting =
845 845  
846 846  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -855,9 +855,9 @@
855 855  
856 856  )))
857 857  
858 -
859 859  == 6.2  AT Command input doesn't work ==
860 860  
975 +
861 861  (((
862 862  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.
863 863  
... ... @@ -864,7 +864,6 @@
864 864  
865 865  )))
866 866  
867 -
868 868  = 7. ​ Order Info =
869 869  
870 870  
... ... @@ -871,11 +871,6 @@
871 871  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
872 872  
873 873  
874 -(% class="wikigeneratedid" %)
875 -(((
876 -
877 -)))
878 -
879 879  = 8.  Packing Info =
880 880  
881 881  (((
... ... @@ -901,11 +901,13 @@
901 901  (((
902 902  
903 903  
904 -
905 905  
906 906  )))
907 907  
908 908  = 9.  Support =
909 909  
1018 +
910 910  * 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.
911 911  * 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]]
1021 +
1022 +
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content
image-20221009001045-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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