Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.32 >
edited by Xiaoling
on 2022/10/25 18:13
To version < 118.2 >
edited by Xiaoling
on 2022/07/11 14:15
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,7 +17,6 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 -
21 21  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 22  
23 23  (((
... ... @@ -56,7 +56,6 @@
56 56  
57 57  == 1.2 ​ Features ==
58 58  
59 -
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 61  * Monitor Temperature & Humidity via SHT31
62 62  * AT Commands to change parameters
... ... @@ -99,7 +99,6 @@
99 99  
100 100  == ​1.4  Applications ==
101 101  
102 -
103 103  * Smart Buildings & Home Automation
104 104  * Logistics and Supply Chain Management
105 105  * Smart Metering
... ... @@ -111,20 +111,15 @@
111 111  ​
112 112  
113 113  
114 -
115 115  == 1.5  Pin Definitions & Switch ==
116 116  
117 -
118 118  N95S31B use the mother board from NBSN95 which as below.
119 119  
120 -
121 121  [[image:image-20220709144723-1.png]]
122 122  
123 123  
124 -
125 125  === 1.5.1 Jumper JP2 ===
126 126  
127 -
128 128  Power on Device when put this jumper.
129 129  
130 130  
... ... @@ -131,13 +131,12 @@
131 131  
132 132  === 1.5.2 BOOT MODE / SW1 ===
133 133  
134 -
135 135  (((
136 -**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.
137 137  )))
138 138  
139 139  (((
140 -**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
141 141  )))
142 142  
143 143  
... ... @@ -144,7 +144,6 @@
144 144  
145 145  === 1.5.3 Reset Button ===
146 146  
147 -
148 148  Press to reboot the device.
149 149  
150 150  
... ... @@ -151,18 +151,15 @@
151 151  
152 152  === 1.5.4 LED ===
153 153  
154 -
155 155  It will flash:
156 156  
157 -1.  When boot the device in flash mode
146 +1. When boot the device in flash mode
147 +1. Send an uplink packet
158 158  
159 -2.  Send an uplink packet
160 160  
161 161  
162 -
163 163  = 2.  Use N95S31B to communicate with IoT Server =
164 164  
165 -
166 166  == 2.1  How it works ==
167 167  
168 168  
... ... @@ -195,7 +195,6 @@
195 195  [[image:image-20220709150546-2.png]]
196 196  
197 197  
198 -
199 199  === 2.2.1 Test Requirement ===
200 200  
201 201  
... ... @@ -248,7 +248,6 @@
248 248  
249 249  === 2.2.3  Insert SIM card ===
250 250  
251 -
252 252  (((
253 253  Insert the NB-IoT Card get from your provider.
254 254  )))
... ... @@ -264,27 +264,23 @@
264 264  
265 265  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
266 266  
267 -
268 268  (((
269 269  (((
270 270  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.
271 -
272 -
273 273  )))
274 274  )))
275 275  
276 276  [[image:1657351312545-300.png]]
277 277  
260 +**Connection:**
278 278  
279 -(% style="color:blue" %)**Connection:**
262 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
280 280  
281 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
264 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
282 282  
283 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
266 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
284 284  
285 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
286 286  
287 -
288 288  In the PC, use below serial tool settings:
289 289  
290 290  * Baud:  (% style="color:green" %)**9600**
... ... @@ -299,9 +299,8 @@
299 299  
300 300  [[image:1657329814315-101.png]]
301 301  
302 -
303 303  (((
304 -(% 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/]]
305 305  )))
306 306  
307 307  
... ... @@ -308,10 +308,9 @@
308 308  
309 309  === 2.2.5  Use CoAP protocol to uplink data ===
310 310  
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/]]
311 311  
312 -(% 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/]]**
313 313  
314 -
315 315  (((
316 316  **Use below commands:**
317 317  )))
... ... @@ -320,10 +320,10 @@
320 320  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
321 321  )))
322 322  * (((
323 -(% 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
324 324  )))
325 325  * (((
326 -(% 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
327 327  )))
328 328  
329 329  (((
... ... @@ -359,16 +359,15 @@
359 359  
360 360  === 2.2.7  Use MQTT protocol to uplink data ===
361 361  
362 -
363 363  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
364 364  
365 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
366 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
367 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
368 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
369 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
370 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
371 -* (% 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
372 372  
373 373  [[image:1657352634421-276.png]]
374 374  
... ... @@ -375,7 +375,6 @@
375 375  
376 376  [[image:1657352645687-385.png]]
377 377  
378 -
379 379  (((
380 380  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.
381 381  )))
... ... @@ -389,7 +389,6 @@
389 389  
390 390  === 2.2.8  Use TCP protocol to uplink data ===
391 391  
392 -
393 393  This feature is supported since firmware version v110
394 394  
395 395  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -404,7 +404,6 @@
404 404  
405 405  === 2.2.9  Change Update Interval ===
406 406  
407 -
408 408  User can use below command to change the (% style="color:green" %)**uplink interval**.
409 409  
410 410  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -413,21 +413,13 @@
413 413  
414 414  )))
415 415  
416 -(((
417 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
418 -)))
419 419  
420 -(((
421 -(% 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).**
422 -)))
423 423  
424 -
425 -
426 426  == 2.3  Uplink Payload ==
427 427  
428 428  
429 429  (((
430 -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.
431 431  )))
432 432  
433 433  
... ... @@ -436,7 +436,7 @@
436 436  )))
437 437  
438 438  (((
439 - (% 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.
440 440  )))
441 441  
442 442  
... ... @@ -459,28 +459,22 @@
459 459  
460 460  (% style="color:red" %)
461 461  1. (((
462 -**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"]].
463 463  )))
464 464  1. (((
465 -**By default, the device will send an uplink message every 1 hour.**
466 -
467 -
468 -
469 -
432 +By default, the device will send an uplink message every 1 hour.
470 470  )))
471 471  
472 472  === 2.3.1  Payload Analyze ===
473 473  
474 -
475 -==== 2.3.1.1  Before Firmware v1.2 ====
476 -
477 -
478 478  N95S31B uplink payload includes in total 21 bytes
479 479  
480 480  
481 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
482 -|=(% 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**
483 -|(% 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" %)(((
440 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
441 +|=(% style="width: 60px;" %)(((
442 +**Size(bytes)**
443 +)))|=(% 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**
444 +|(% 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" %)(((
484 484  (((
485 485  Reserve/ Same as NBSN95 CFGMOD=1
486 486  )))
... ... @@ -488,7 +488,7 @@
488 488  (((
489 489  No function here.
490 490  )))
491 -)))|(% style="width:102px" %)(((
452 +)))|(% style="width:77px" %)(((
492 492  (((
493 493  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
494 494  )))
... ... @@ -496,7 +496,7 @@
496 496  (((
497 497  By SHT31
498 498  )))
499 -)))|(% style="width:81px" %)(((
460 +)))|(% style="width:80px" %)(((
500 500  (((
501 501  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
502 502  )))
... ... @@ -507,8 +507,6 @@
507 507  )))
508 508  
509 509  (((
510 -
511 -
512 512  (((
513 513  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
514 514  )))
... ... @@ -518,88 +518,29 @@
518 518  [[image:1657354294009-643.png]]
519 519  
520 520  
521 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
480 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
522 522  
523 -**where:**
482 +* Device ID: 0x724031607457 = 724031607457
483 +* Version: 0x006e=110=1.1.0
524 524  
525 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
485 +* BAT: 0x0ccd = 3277 mV = 3.277V
486 +* Signal: 0x1b = 27
487 +* Model: 0x01 = 1
488 +* 0x00dc000ccc= reserve, ignore in N95S31B
489 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
490 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
526 526  
527 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
528 -
529 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
530 -
531 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
532 -
533 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
534 -
535 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
536 -
537 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
538 -
539 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
540 -
541 541  (((
542 542  
494 +)))
543 543  
544 -
496 +(((
545 545  
546 546  )))
547 547  
548 -==== 2.3.1.2 Since Firmware v1.2 ====
549 549  
550 -
551 -In this mode, uplink payload includes 91 bytes in total by default.
552 -
553 -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.
554 -
555 -
556 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
557 -|=(% 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**
558 -|=(% 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 .....
559 -
560 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
561 -
562 -
563 -[[image:image-20220908154949-1.png]]
564 -
565 -
566 -The payload is ASCII string, representative same HEX:
567 -
568 -**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__ **
569 -
570 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
571 -
572 -**where:**
573 -
574 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
575 -
576 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
577 -
578 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
579 -
580 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
581 -
582 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
583 -
584 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
585 -
586 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
587 -
588 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
589 -
590 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
591 -
592 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
593 -
594 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
595 -
596 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
597 -
598 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
599 -
600 600  === 2.3.2  Device ID ===
601 601  
602 -
603 603  (((
604 604  By default, the Device ID equal to the last 6 bytes of IMEI.
605 605  )))
... ... @@ -606,12 +606,10 @@
606 606  
607 607  (((
608 608  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
609 -
610 -
611 611  )))
612 612  
613 613  (((
614 -(% style="color:blue" %)**Example:**
512 +**Example:**
615 615  )))
616 616  
617 617  (((
... ... @@ -619,28 +619,13 @@
619 619  )))
620 620  
621 621  (((
622 -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.
623 -
624 -
520 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
625 625  )))
626 626  
627 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
628 628  
629 629  
630 -By default, the Device ID equal to the last 15 bits of IMEI.
631 -
632 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
633 -
634 -
635 -(% style="color:blue" %)**Example:**
636 -
637 -AT+DEUI=868411056754138
638 -
639 -
640 -
641 641  === 2.3.3  Version Info ===
642 642  
643 -
644 644  (((
645 645  These bytes include the hardware and software version.
646 646  )))
... ... @@ -668,7 +668,6 @@
668 668  
669 669  === 2.3.4  Battery Info ===
670 670  
671 -
672 672  (((
673 673  Ex1: 0x0B45 = 2885mV
674 674  )))
... ... @@ -681,7 +681,6 @@
681 681  
682 682  === 2.3.5  Signal Strength ===
683 683  
684 -
685 685  (((
686 686  NB-IoT Network signal Strength.
687 687  )))
... ... @@ -714,7 +714,6 @@
714 714  
715 715  === 2.3.6  Temperature & Humidity ===
716 716  
717 -
718 718  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
719 719  
720 720  [[image:image-20220709161741-3.png]]
... ... @@ -733,9 +733,8 @@
733 733  
734 734  == 2.4  Downlink Payload ==
735 735  
616 +By default, NDDS75 prints the downlink payload to console port.
736 736  
737 -By default, N95S31B prints the downlink payload to console port.
738 -
739 739  [[image:image-20220709100028-1.png]]
740 740  
741 741  
... ... @@ -772,7 +772,7 @@
772 772  )))
773 773  
774 774  (((
775 -If payload = 0x04FF, it will reset the N95S31B
654 +If payload = 0x04FF, it will reset the NDDS75
776 776  )))
777 777  
778 778  
... ... @@ -784,74 +784,11 @@
784 784  
785 785  
786 786  
787 -== 2.5  Humidity and Temperature alarm function ==
666 +== 2.5  ​Battery Analysis ==
788 788  
668 +=== 2.5.1  ​Battery Type ===
789 789  
790 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
791 791  
792 -
793 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
794 -
795 -
796 -² When min=0, and max≠0, Alarm higher than max
797 -
798 -² When min≠0, and max=0, Alarm lower than min
799 -
800 -² When min≠0 and max≠0, Alarm higher than max or lower than min
801 -
802 -
803 - (% style="color:blue" %)**Example:**
804 -
805 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
806 -
807 -
808 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
809 -
810 -² When min=0, and max≠0, Alarm higher than max
811 -
812 -² When min≠0, and max=0, Alarm lower than min
813 -
814 -² When min≠0 and max≠0, Alarm higher than max or lower than min
815 -
816 -
817 -**~ (% style="color:blue" %)Example:(%%)**
818 -
819 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
820 -
821 -
822 -
823 -== 2.6 Set the number of data to be uploaded and the recording time ==
824 -
825 -
826 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
827 -
828 -* (% 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)
829 -* (% 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.
830 -
831 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
832 -
833 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
834 -
835 -
836 -
837 -== 2.7 Read or Clear cached data ==
838 -
839 -
840 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
841 -
842 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
843 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
844 -
845 -[[image:image-20220908163102-2.png]]
846 -
847 -
848 -
849 -== 2.8  ​Battery Analysis ==
850 -
851 -
852 -=== 2.8.1  ​Battery Type ===
853 -
854 -
855 855  (((
856 856  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.
857 857  )))
... ... @@ -874,11 +874,10 @@
874 874  
875 875  
876 876  
877 -=== 2.8.2  Power consumption Analyze ===
693 +=== 2.5.2  Power consumption Analyze ===
878 878  
879 -
880 880  (((
881 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
696 +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.
882 882  )))
883 883  
884 884  (((
... ... @@ -886,9 +886,8 @@
886 886  )))
887 887  
888 888  
889 -=== 2.8.3  ​Battery Note ===
704 +=== 2.5.3  ​Battery Note ===
890 890  
891 -
892 892  (((
893 893  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.
894 894  )))
... ... @@ -895,7 +895,7 @@
895 895  
896 896  
897 897  
898 -=== 2.8.4  Replace the battery ===
712 +=== 2.5.4  Replace the battery ===
899 899  
900 900  
901 901  (((
... ... @@ -911,7 +911,6 @@
911 911  
912 912  = 3. ​ Access NB-IoT Module =
913 913  
914 -
915 915  (((
916 916  Users can directly access the AT command set of the NB-IoT module.
917 917  )))
... ... @@ -918,8 +918,6 @@
918 918  
919 919  (((
920 920  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/]] 
921 -
922 -
923 923  )))
924 924  
925 925  [[image:1657333200519-600.png]]
... ... @@ -928,13 +928,11 @@
928 928  
929 929  = 4.  Using the AT Commands =
930 930  
931 -
932 932  == 4.1  Access AT Commands ==
933 933  
744 +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/]]
934 934  
935 -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]]
936 936  
937 -
938 938  AT+<CMD>?  : Help on <CMD>
939 939  
940 940  AT+<CMD>         : Run <CMD>
... ... @@ -974,24 +974,7 @@
974 974  
975 975  AT+SERVADDR  : Server Address
976 976  
977 -AT+TR      : Get or Set record time
978 978  
979 -AT+APN     : Get or set the APN
980 -
981 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
982 -
983 -AT+DNSCFG  : Get or Set DNS Server
984 -
985 -AT+GETSENSORVALUE   : Returns the current sensor measurement
986 -
987 -AT+NOUD      : Get or Set the number of data to be uploaded
988 -
989 -AT+CDP     : Read or Clear cached data
990 -
991 -AT+SHTEMP: Get or Set alarm of temp
992 -
993 -AT+SHHUM: Get or Set alarm of moisture
994 -
995 995  (% style="color:#037691" %)**COAP Management**      
996 996  
997 997  AT+URI            : Resource parameters
... ... @@ -1025,7 +1025,6 @@
1025 1025  
1026 1026  = ​5.  FAQ =
1027 1027  
1028 -
1029 1029  == 5.1 ​ How to Upgrade Firmware ==
1030 1030  
1031 1031  
... ... @@ -1041,7 +1041,7 @@
1041 1041  
1042 1042  
1043 1043  (((
1044 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
835 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1045 1045  )))
1046 1046  )))
1047 1047  
... ... @@ -1049,7 +1049,6 @@
1049 1049  
1050 1050  = 6.  Trouble Shooting =
1051 1051  
1052 -
1053 1053  == 6.1  ​Connection problem when uploading firmware ==
1054 1054  
1055 1055  
... ... @@ -1065,7 +1065,6 @@
1065 1065  
1066 1066  == 6.2  AT Command input doesn't work ==
1067 1067  
1068 -
1069 1069  (((
1070 1070  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.
1071 1071  
... ... @@ -1115,6 +1115,5 @@
1115 1115  
1116 1116  = 9.  Support =
1117 1117  
1118 -
1119 1119  * 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.
1120 1120  * 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]]
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