Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.35 >
edited by Xiaoling
on 2023/04/03 16:57
To version < 118.9 >
edited by Xiaoling
on 2022/07/12 17:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,7 +55,6 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
58 -
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 60  * Monitor Temperature & Humidity via SHT31
61 61  * AT Commands to change parameters
... ... @@ -68,6 +68,7 @@
68 68  * 8500mAh Battery for long term use
69 69  
70 70  
70 +
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -94,9 +94,9 @@
94 94  * Max boost current: 2A, 1 second
95 95  
96 96  
97 +
97 97  == ​1.4  Applications ==
98 98  
99 -
100 100  * Smart Buildings & Home Automation
101 101  * Logistics and Supply Chain Management
102 102  * Smart Metering
... ... @@ -110,45 +110,42 @@
110 110  
111 111  == 1.5  Pin Definitions & Switch ==
112 112  
113 -
114 114  N95S31B use the mother board from NBSN95 which as below.
115 115  
116 -
117 117  [[image:image-20220709144723-1.png]]
118 118  
119 119  
120 120  === 1.5.1 Jumper JP2 ===
121 121  
122 -
123 123  Power on Device when put this jumper.
124 124  
125 125  
123 +
126 126  === 1.5.2 BOOT MODE / SW1 ===
127 127  
128 -
129 129  (((
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.
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.
131 131  )))
132 132  
133 133  (((
134 -**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
135 135  )))
136 136  
137 137  
135 +
138 138  === 1.5.3 Reset Button ===
139 139  
140 -
141 141  Press to reboot the device.
142 142  
143 143  
141 +
144 144  === 1.5.4 LED ===
145 145  
146 -
147 147  It will flash:
148 148  
149 -1.  When boot the device in flash mode
146 +1. When boot the device in flash mode
147 +1. Send an uplink packet
150 150  
151 -2.  Send an uplink packet
152 152  
153 153  
154 154  = 2.  Use N95S31B to communicate with IoT Server =
... ... @@ -178,6 +178,7 @@
178 178  
179 179  == 2.2 ​ Configure the N95S31B ==
180 180  
178 +
181 181  === 2.2.1  Power On N95S31B ===
182 182  
183 183  
... ... @@ -184,7 +184,7 @@
184 184  [[image:image-20220709150546-2.png]]
185 185  
186 186  
187 -=== 2.2.2 Test Requirement ===
185 +=== 2.2.1 Test Requirement ===
188 188  
189 189  
190 190  (((
... ... @@ -233,9 +233,9 @@
233 233  [[image:1657350625843-586.png]]
234 234  
235 235  
234 +
236 236  === 2.2.3  Insert SIM card ===
237 237  
238 -
239 239  (((
240 240  Insert the NB-IoT Card get from your provider.
241 241  )))
... ... @@ -248,29 +248,26 @@
248 248  [[image:1657351240556-536.png]]
249 249  
250 250  
249 +
251 251  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
252 252  
253 -
254 254  (((
255 255  (((
256 256  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 -
259 259  )))
260 260  )))
261 261  
262 262  [[image:1657351312545-300.png]]
263 263  
260 +**Connection:**
264 264  
265 -(% style="color:blue" %)**Connection:**
262 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
266 266  
267 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
264 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
268 268  
269 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
266 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
270 270  
271 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
272 272  
273 -
274 274  In the PC, use below serial tool settings:
275 275  
276 276  * Baud:  (% style="color:green" %)**9600**
... ... @@ -285,18 +285,17 @@
285 285  
286 286  [[image:1657329814315-101.png]]
287 287  
288 -
289 289  (((
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 +(% 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/]]
291 291  )))
292 292  
293 293  
288 +
294 294  === 2.2.5  Use CoAP protocol to uplink data ===
295 295  
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/]]
296 296  
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/]]**
298 298  
299 -
300 300  (((
301 301  **Use below commands:**
302 302  )))
... ... @@ -305,10 +305,10 @@
305 305  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
306 306  )))
307 307  * (((
308 -(% 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
309 309  )))
310 310  * (((
311 -(% 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
312 312  )))
313 313  
314 314  (((
... ... @@ -327,6 +327,7 @@
327 327  [[image:1657352185396-303.png]]
328 328  
329 329  
324 +
330 330  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
331 331  
332 332  
... ... @@ -340,18 +340,18 @@
340 340  [[image:1657352403317-397.png]]
341 341  
342 342  
338 +
343 343  === 2.2.7  Use MQTT protocol to uplink data ===
344 344  
345 -
346 346  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
347 347  
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
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
355 355  
356 356  [[image:1657352634421-276.png]]
357 357  
... ... @@ -358,7 +358,6 @@
358 358  
359 359  [[image:1657352645687-385.png]]
360 360  
361 -
362 362  (((
363 363  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.
364 364  )))
... ... @@ -369,9 +369,9 @@
369 369  )))
370 370  
371 371  
366 +
372 372  === 2.2.8  Use TCP protocol to uplink data ===
373 373  
374 -
375 375  This feature is supported since firmware version v110
376 376  
377 377  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -383,9 +383,9 @@
383 383  [[image:1657352914475-252.png]]
384 384  
385 385  
380 +
386 386  === 2.2.9  Change Update Interval ===
387 387  
388 -
389 389  User can use below command to change the (% style="color:green" %)**uplink interval**.
390 390  
391 391  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -394,20 +394,13 @@
394 394  
395 395  )))
396 396  
397 -(((
398 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
399 -)))
400 400  
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 -)))
404 404  
405 -
406 406  == 2.3  Uplink Payload ==
407 407  
408 408  
409 409  (((
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 +N95S31B 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.
411 411  )))
412 412  
413 413  
... ... @@ -439,26 +439,26 @@
439 439  
440 440  (% style="color:red" %)
441 441  1. (((
442 -**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"]].
443 443  )))
444 444  1. (((
445 -**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.
446 446  
447 447  
435 +
448 448  
449 449  )))
450 450  
451 451  === 2.3.1  Payload Analyze ===
452 452  
453 -==== 2.3.1.1  Before Firmware v1.2 ====
454 -
455 -
456 456  N95S31B uplink payload includes in total 21 bytes
457 457  
458 458  
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" %)(((
444 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
445 +|=(% style="width: 60px;" %)(((
446 +**Size(bytes)**
447 +)))|=(% 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**
448 +|(% 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" %)(((
462 462  (((
463 463  Reserve/ Same as NBSN95 CFGMOD=1
464 464  )))
... ... @@ -466,7 +466,7 @@
466 466  (((
467 467  No function here.
468 468  )))
469 -)))|(% style="width:102px" %)(((
456 +)))|(% style="width:77px" %)(((
470 470  (((
471 471  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
472 472  )))
... ... @@ -474,7 +474,7 @@
474 474  (((
475 475  By SHT31
476 476  )))
477 -)))|(% style="width:81px" %)(((
464 +)))|(% style="width:80px" %)(((
478 478  (((
479 479  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
480 480  )))
... ... @@ -485,8 +485,6 @@
485 485  )))
486 486  
487 487  (((
488 -
489 -
490 490  (((
491 491  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
492 492  )))
... ... @@ -496,89 +496,29 @@
496 496  [[image:1657354294009-643.png]]
497 497  
498 498  
499 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
484 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
500 500  
501 -**where:**
486 +* Device ID: 0x724031607457 = 724031607457
487 +* Version: 0x006e=110=1.1.0
502 502  
503 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
489 +* BAT: 0x0ccd = 3277 mV = 3.277V
490 +* Signal: 0x1b = 27
491 +* Model: 0x01 = 1
492 +* 0x00dc000ccc= reserve, ignore in N95S31B
493 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
494 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
504 504  
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 -
519 519  (((
520 520  
498 +)))
521 521  
522 -
500 +(((
523 523  
524 524  )))
525 525  
526 -==== 2.3.1.2 Since Firmware v1.2 ====
527 527  
528 -
529 -In this mode, uplink payload includes 91 bytes in total by default.
530 -
531 -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.
532 -
533 -
534 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
535 -|=(% 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**
536 -|=(% 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 .....
537 -
538 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
539 -
540 -
541 -[[image:image-20220908154949-1.png]]
542 -
543 -
544 -The payload is ASCII string, representative same HEX:
545 -
546 -**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__ **
547 -
548 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
549 -
550 -**where:**
551 -
552 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
553 -
554 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
555 -
556 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
557 -
558 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
559 -
560 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
561 -
562 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
563 -
564 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
565 -
566 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
567 -
568 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
569 -
570 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
571 -
572 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
573 -
574 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
575 -
576 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
577 -
578 -
579 579  === 2.3.2  Device ID ===
580 580  
581 -
582 582  (((
583 583  By default, the Device ID equal to the last 6 bytes of IMEI.
584 584  )))
... ... @@ -585,12 +585,10 @@
585 585  
586 586  (((
587 587  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
588 -
589 -
590 590  )))
591 591  
592 592  (((
593 -(% style="color:blue" %)**Example:**
516 +**Example:**
594 594  )))
595 595  
596 596  (((
... ... @@ -598,27 +598,13 @@
598 598  )))
599 599  
600 600  (((
601 -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.
602 -
603 -
524 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
604 604  )))
605 605  
606 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
607 607  
608 608  
609 -By default, the Device ID equal to the last 15 bits of IMEI.
610 -
611 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
612 -
613 -
614 -(% style="color:blue" %)**Example:**
615 -
616 -AT+DEUI=868411056754138
617 -
618 -
619 619  === 2.3.3  Version Info ===
620 620  
621 -
622 622  (((
623 623  These bytes include the hardware and software version.
624 624  )))
... ... @@ -643,9 +643,9 @@
643 643  
644 644  )))
645 645  
555 +
646 646  === 2.3.4  Battery Info ===
647 647  
648 -
649 649  (((
650 650  Ex1: 0x0B45 = 2885mV
651 651  )))
... ... @@ -655,9 +655,9 @@
655 655  )))
656 656  
657 657  
567 +
658 658  === 2.3.5  Signal Strength ===
659 659  
660 -
661 661  (((
662 662  NB-IoT Network signal Strength.
663 663  )))
... ... @@ -687,9 +687,9 @@
687 687  )))
688 688  
689 689  
599 +
690 690  === 2.3.6  Temperature & Humidity ===
691 691  
692 -
693 693  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
694 694  
695 695  [[image:image-20220709161741-3.png]]
... ... @@ -705,9 +705,9 @@
705 705  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
706 706  
707 707  
617 +
708 708  == 2.4  Downlink Payload ==
709 709  
710 -
711 711  By default, N95S31B prints the downlink payload to console port.
712 712  
713 713  [[image:image-20220709100028-1.png]]
... ... @@ -757,78 +757,69 @@
757 757  )))
758 758  
759 759  
760 -== 2.5  Humidity and Temperature alarm function ==
761 761  
670 +== 2.5  ​Battery Analysis ==
762 762  
763 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
672 +=== 2.5.1  ​Battery Type ===
764 764  
765 765  
766 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
675 +(((
676 +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.
677 +)))
767 767  
679 +(((
680 +The battery is designed to last for several years depends on the actually use environment and update interval. 
681 +)))
768 768  
769 -² When min=0, and max≠0, Alarm higher than max
683 +(((
684 +The battery related documents as below:
685 +)))
770 770  
771 -² When min≠0, and max=0, Alarm lower than min
687 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
688 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
689 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
772 772  
773 -² When min≠0 and max≠0, Alarm higher than max or lower than min
691 +(((
692 +[[image:image-20220709101450-2.png]]
693 +)))
774 774  
775 775  
776 - (% style="color:blue" %)**Example:**
777 777  
778 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
697 +=== 2.5.2  Power consumption Analyze ===
779 779  
699 +(((
700 +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.
701 +)))
780 780  
781 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
703 +(((
704 +
705 +)))
782 782  
783 -² When min=0, and max≠0, Alarm higher than max
784 784  
785 -² When min≠0, and max=0, Alarm lower than min
708 +=== 2.5.3  ​Battery Note ===
786 786  
787 -² When min≠0 and max≠0, Alarm higher than max or lower than min
710 +(((
711 +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.
712 +)))
788 788  
789 789  
790 -**~ (% style="color:blue" %)Example:(%%)**
791 791  
792 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
716 +=== 2.5.4  Replace the battery ===
793 793  
794 794  
795 -== 2.6 Set the number of data to be uploaded and the recording time ==
719 +(((
720 +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.
721 +)))
796 796  
797 797  
798 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
724 +(((
725 +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).
726 +)))
799 799  
800 -* (% 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)
801 -* (% 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.
802 802  
803 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
804 804  
805 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
806 -
807 -
808 -== 2.7 Read or Clear cached data ==
809 -
810 -
811 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
812 -
813 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
814 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
815 -
816 -[[image:image-20220908163102-2.png]]
817 -
818 -
819 -= 2.8 Battery & Power Consumption =
820 -
821 -
822 -N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
823 -
824 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
825 -
826 -
827 -
828 -
829 829  = 3. ​ Access NB-IoT Module =
830 830  
831 -
832 832  (((
833 833  Users can directly access the AT command set of the NB-IoT module.
834 834  )))
... ... @@ -835,21 +835,19 @@
835 835  
836 836  (((
837 837  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/]] 
838 -
839 -
840 840  )))
841 841  
842 842  [[image:1657333200519-600.png]]
843 843  
844 844  
743 +
845 845  = 4.  Using the AT Commands =
846 846  
847 847  == 4.1  Access AT Commands ==
848 848  
748 +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/]]
849 849  
850 -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]]
851 851  
852 -
853 853  AT+<CMD>?  : Help on <CMD>
854 854  
855 855  AT+<CMD>         : Run <CMD>
... ... @@ -889,24 +889,7 @@
889 889  
890 890  AT+SERVADDR  : Server Address
891 891  
892 -AT+TR      : Get or Set record time
893 893  
894 -AT+APN     : Get or set the APN
895 -
896 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
897 -
898 -AT+DNSCFG  : Get or Set DNS Server
899 -
900 -AT+GETSENSORVALUE   : Returns the current sensor measurement
901 -
902 -AT+NOUD      : Get or Set the number of data to be uploaded
903 -
904 -AT+CDP     : Read or Clear cached data
905 -
906 -AT+SHTEMP: Get or Set alarm of temp
907 -
908 -AT+SHHUM: Get or Set alarm of moisture
909 -
910 910  (% style="color:#037691" %)**COAP Management**      
911 911  
912 912  AT+URI            : Resource parameters
... ... @@ -937,6 +937,7 @@
937 937  AT+PWORD  : Serial Access Password
938 938  
939 939  
821 +
940 940  = ​5.  FAQ =
941 941  
942 942  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -954,11 +954,12 @@
954 954  
955 955  
956 956  (((
957 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
839 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
958 958  )))
959 959  )))
960 960  
961 961  
844 +
962 962  = 6.  Trouble Shooting =
963 963  
964 964  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -973,9 +973,9 @@
973 973  
974 974  )))
975 975  
859 +
976 976  == 6.2  AT Command input doesn't work ==
977 977  
978 -
979 979  (((
980 980  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.
981 981  
... ... @@ -982,6 +982,7 @@
982 982  
983 983  )))
984 984  
868 +
985 985  = 7. ​ Order Info =
986 986  
987 987  
... ... @@ -988,6 +988,11 @@
988 988  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
989 989  
990 990  
875 +(% class="wikigeneratedid" %)
876 +(((
877 +
878 +)))
879 +
991 991  = 8.  Packing Info =
992 992  
993 993  (((
... ... @@ -1013,15 +1013,11 @@
1013 1013  (((
1014 1014  
1015 1015  
905 +
1016 1016  
1017 1017  )))
1018 1018  
1019 1019  = 9.  Support =
1020 1020  
1021 -
1022 1022  * 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.
1023 1023  * 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]]
1024 -
1025 -
1026 -
1027 -
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