Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 117.1 >
edited by Xiaoling
on 2022/07/11 11:05
To version < 129.4 >
edited by Xiaoling
on 2022/10/25 17:00
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,6 +17,7 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
59 +
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  
... ... @@ -94,9 +94,9 @@
94 94  * Max boost current: 2A, 1 second
95 95  
96 96  
97 -
98 98  == ​1.4  Applications ==
99 99  
100 +
100 100  * Smart Buildings & Home Automation
101 101  * Logistics and Supply Chain Management
102 102  * Smart Metering
... ... @@ -108,15 +108,20 @@
108 108  ​
109 109  
110 110  
111 -== 1.5  Pin Definitions ==
112 112  
113 +== 1.5  Pin Definitions & Switch ==
114 +
115 +
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
118 +
115 115  [[image:image-20220709144723-1.png]]
116 116  
117 117  
122 +
118 118  === 1.5.1 Jumper JP2 ===
119 119  
125 +
120 120  Power on Device when put this jumper.
121 121  
122 122  
... ... @@ -123,12 +123,13 @@
123 123  
124 124  === 1.5.2 BOOT MODE / SW1 ===
125 125  
132 +
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.
134 +**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
138 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
132 132  )))
133 133  
134 134  
... ... @@ -135,6 +135,7 @@
135 135  
136 136  === 1.5.3 Reset Button ===
137 137  
145 +
138 138  Press to reboot the device.
139 139  
140 140  
... ... @@ -141,15 +141,18 @@
141 141  
142 142  === 1.5.4 LED ===
143 143  
152 +
144 144  It will flash:
145 145  
146 -1. When boot the device in flash mode
147 -1. Send an uplink packet
155 +1.  When boot the device in flash mode
148 148  
157 +2.  Send an uplink packet
149 149  
150 150  
160 +
151 151  = 2.  Use N95S31B to communicate with IoT Server =
152 152  
163 +
153 153  == 2.1  How it works ==
154 154  
155 155  
... ... @@ -166,7 +166,7 @@
166 166  
167 167  )))
168 168  
169 -[[image:1657350248151-650.png]]
180 +[[image:1657520100595-569.png]]
170 170  
171 171  (((
172 172  
... ... @@ -182,6 +182,7 @@
182 182  [[image:image-20220709150546-2.png]]
183 183  
184 184  
196 +
185 185  === 2.2.1 Test Requirement ===
186 186  
187 187  
... ... @@ -234,6 +234,7 @@
234 234  
235 235  === 2.2.3  Insert SIM card ===
236 236  
249 +
237 237  (((
238 238  Insert the NB-IoT Card get from your provider.
239 239  )))
... ... @@ -249,23 +249,27 @@
249 249  
250 250  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
251 251  
265 +
252 252  (((
253 253  (((
254 254  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.
269 +
270 +
255 255  )))
256 256  )))
257 257  
258 258  [[image:1657351312545-300.png]]
259 259  
260 -**Connection:**
261 261  
262 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
277 +**(% style="color:blue" %)Connection:**
263 263  
264 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
279 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
265 265  
266 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
281 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
267 267  
283 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
268 268  
285 +
269 269  In the PC, use below serial tool settings:
270 270  
271 271  * Baud:  (% style="color:green" %)**9600**
... ... @@ -280,8 +280,9 @@
280 280  
281 281  [[image:1657329814315-101.png]]
282 282  
300 +
283 283  (((
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/]]
302 +(% 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]]**
285 285  )))
286 286  
287 287  
... ... @@ -288,9 +288,10 @@
288 288  
289 289  === 2.2.5  Use CoAP protocol to uplink data ===
290 290  
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/]]
292 292  
310 +(% 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/]]**
293 293  
312 +
294 294  (((
295 295  **Use below commands:**
296 296  )))
... ... @@ -299,10 +299,10 @@
299 299  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
300 300  )))
301 301  * (((
302 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
321 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
303 303  )))
304 304  * (((
305 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
324 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
306 306  )))
307 307  
308 308  (((
... ... @@ -338,15 +338,16 @@
338 338  
339 339  === 2.2.7  Use MQTT protocol to uplink data ===
340 340  
360 +
341 341  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
342 342  
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
363 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
364 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
365 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
366 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
367 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
368 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
369 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
350 350  
351 351  [[image:1657352634421-276.png]]
352 352  
... ... @@ -353,6 +353,7 @@
353 353  
354 354  [[image:1657352645687-385.png]]
355 355  
376 +
356 356  (((
357 357  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.
358 358  )))
... ... @@ -366,6 +366,7 @@
366 366  
367 367  === 2.2.8  Use TCP protocol to uplink data ===
368 368  
390 +
369 369  This feature is supported since firmware version v110
370 370  
371 371  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -380,6 +380,7 @@
380 380  
381 381  === 2.2.9  Change Update Interval ===
382 382  
405 +
383 383  User can use below command to change the (% style="color:green" %)**uplink interval**.
384 384  
385 385  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -388,13 +388,21 @@
388 388  
389 389  )))
390 390  
414 +(((
415 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
416 +)))
391 391  
418 +(((
419 +(% 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).**
420 +)))
392 392  
422 +
423 +
393 393  == 2.3  Uplink Payload ==
394 394  
395 395  
396 396  (((
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.
428 +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.
398 398  )))
399 399  
400 400  
... ... @@ -403,7 +403,7 @@
403 403  )))
404 404  
405 405  (((
406 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
437 + (% 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.
407 407  )))
408 408  
409 409  
... ... @@ -426,24 +426,30 @@
426 426  
427 427  (% style="color:red" %)
428 428  1. (((
429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
460 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
430 430  )))
431 431  1. (((
432 -By default, the device will send an uplink message every 1 hour.
433 -)))
463 +**By default, the device will send an uplink message every 1 hour.**
434 434  
435 435  
436 436  
467 +
468 +)))
469 +
437 437  === 2.3.1  Payload Analyze ===
438 438  
472 +
473 +==== 2.3.1.1  Before Firmware v1.2 ====
474 +
475 +
439 439  N95S31B uplink payload includes in total 21 bytes
440 440  
441 441  
442 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
443 -|=(% style="width: 60px;" %)(((
479 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
480 +|=(% style="width: 50px;" %)(((
444 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" %)(((
482 +)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**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" %)(((
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:77px" %)(((
491 +)))|(% style="width:102px" %)(((
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:80px" %)(((
499 +)))|(% style="width:81px" %)(((
463 463  (((
464 464  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
465 465  )))
... ... @@ -470,6 +470,8 @@
470 470  )))
471 471  
472 472  (((
510 +
511 +
473 473  (((
474 474  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
475 475  )))
... ... @@ -479,29 +479,89 @@
479 479  [[image:1657354294009-643.png]]
480 480  
481 481  
482 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
521 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
483 483  
484 -* Device ID: 0x724031607457 = 724031607457
485 -* Version: 0x006e=110=1.1.0
523 +**where:**
486 486  
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
525 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
493 493  
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 +
494 494  (((
495 495  
496 -)))
497 497  
498 -(((
544 +
499 499  
500 500  )))
501 501  
548 +==== 2.3.1.2 Since Firmware v1.2 ====
502 502  
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="2" style="background-color:#ffffcc; color:green; width:1234px" %)
557 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**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 +
503 503  === 2.3.2  Device ID ===
504 504  
603 +
505 505  (((
506 506  By default, the Device ID equal to the last 6 bytes of IMEI.
507 507  )))
... ... @@ -508,10 +508,12 @@
508 508  
509 509  (((
510 510  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
610 +
611 +
511 511  )))
512 512  
513 513  (((
514 -**Example:**
615 +(% style="color:blue" %)**Example:**
515 515  )))
516 516  
517 517  (((
... ... @@ -519,13 +519,28 @@
519 519  )))
520 520  
521 521  (((
522 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
623 +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.
624 +
625 +
523 523  )))
524 524  
628 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
525 525  
526 526  
631 +By default, the Device ID equal to the last 15 bits of IMEI.
632 +
633 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
634 +
635 +
636 +(% style="color:blue" %)**Example:**
637 +
638 +AT+DEUI=868411056754138
639 +
640 +
641 +
527 527  === 2.3.3  Version Info ===
528 528  
644 +
529 529  (((
530 530  These bytes include the hardware and software version.
531 531  )))
... ... @@ -553,6 +553,7 @@
553 553  
554 554  === 2.3.4  Battery Info ===
555 555  
672 +
556 556  (((
557 557  Ex1: 0x0B45 = 2885mV
558 558  )))
... ... @@ -565,6 +565,7 @@
565 565  
566 566  === 2.3.5  Signal Strength ===
567 567  
685 +
568 568  (((
569 569  NB-IoT Network signal Strength.
570 570  )))
... ... @@ -597,6 +597,7 @@
597 597  
598 598  === 2.3.6  Temperature & Humidity ===
599 599  
718 +
600 600  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
601 601  
602 602  [[image:image-20220709161741-3.png]]
... ... @@ -615,8 +615,9 @@
615 615  
616 616  == 2.4  Downlink Payload ==
617 617  
618 -By default, NDDS75 prints the downlink payload to console port.
619 619  
738 +By default, N95S31B prints the downlink payload to console port.
739 +
620 620  [[image:image-20220709100028-1.png]]
621 621  
622 622  
... ... @@ -653,7 +653,7 @@
653 653  )))
654 654  
655 655  (((
656 -If payload = 0x04FF, it will reset the NDDS75
776 +If payload = 0x04FF, it will reset the N95S31B
657 657  )))
658 658  
659 659  
... ... @@ -665,11 +665,74 @@
665 665  
666 666  
667 667  
668 -== 2.5  ​Battery Analysis ==
788 +== 2.5  Humidity and Temperature alarm function ==
669 669  
670 -=== 2.5.1  ​Battery Type ===
671 671  
791 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
672 672  
793 +
794 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
795 +
796 +
797 +² When min=0, and max≠0, Alarm higher than max
798 +
799 +² When min≠0, and max=0, Alarm lower than min
800 +
801 +² When min≠0 and max≠0, Alarm higher than max or lower than min
802 +
803 +
804 + (% style="color:blue" %)**Example:**
805 +
806 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
807 +
808 +
809 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
810 +
811 +² When min=0, and max≠0, Alarm higher than max
812 +
813 +² When min≠0, and max=0, Alarm lower than min
814 +
815 +² When min≠0 and max≠0, Alarm higher than max or lower than min
816 +
817 +
818 +**~ (% style="color:blue" %)Example:(%%)**
819 +
820 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
821 +
822 +
823 +
824 +== 2.6 Set the number of data to be uploaded and the recording time ==
825 +
826 +
827 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
828 +
829 +* (% 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)
830 +* (% 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.
831 +
832 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
833 +
834 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
835 +
836 +
837 +
838 +== 2.7 Read or Clear cached data ==
839 +
840 +
841 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
842 +
843 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
844 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
845 +
846 +[[image:image-20220908163102-2.png]]
847 +
848 +
849 +
850 +== 2.8  ​Battery Analysis ==
851 +
852 +
853 +=== 2.8.1  ​Battery Type ===
854 +
855 +
673 673  (((
674 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 675  )))
... ... @@ -692,10 +692,11 @@
692 692  
693 693  
694 694  
695 -=== 2.5.2  Power consumption Analyze ===
878 +=== 2.8.2  Power consumption Analyze ===
696 696  
880 +
697 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.
882 +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.
699 699  )))
700 700  
701 701  (((
... ... @@ -703,8 +703,9 @@
703 703  )))
704 704  
705 705  
706 -=== 2.5.3  ​Battery Note ===
890 +=== 2.8.3  ​Battery Note ===
707 707  
892 +
708 708  (((
709 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 710  )))
... ... @@ -711,7 +711,7 @@
711 711  
712 712  
713 713  
714 -=== 2.5.4  Replace the battery ===
899 +=== 2.8.4  Replace the battery ===
715 715  
716 716  
717 717  (((
... ... @@ -727,6 +727,7 @@
727 727  
728 728  = 3. ​ Access NB-IoT Module =
729 729  
915 +
730 730  (((
731 731  Users can directly access the AT command set of the NB-IoT module.
732 732  )))
... ... @@ -733,6 +733,8 @@
733 733  
734 734  (((
735 735  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/]] 
922 +
923 +
736 736  )))
737 737  
738 738  [[image:1657333200519-600.png]]
... ... @@ -741,11 +741,13 @@
741 741  
742 742  = 4.  Using the AT Commands =
743 743  
932 +
744 744  == 4.1  Access AT Commands ==
745 745  
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/]]
747 747  
936 +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]]
748 748  
938 +
749 749  AT+<CMD>?  : Help on <CMD>
750 750  
751 751  AT+<CMD>         : Run <CMD>
... ... @@ -785,7 +785,24 @@
785 785  
786 786  AT+SERVADDR  : Server Address
787 787  
978 +AT+TR      : Get or Set record time
788 788  
980 +AT+APN     : Get or set the APN
981 +
982 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
983 +
984 +AT+DNSCFG  : Get or Set DNS Server
985 +
986 +AT+GETSENSORVALUE   : Returns the current sensor measurement
987 +
988 +AT+NOUD      : Get or Set the number of data to be uploaded
989 +
990 +AT+CDP     : Read or Clear cached data
991 +
992 +AT+SHTEMP: Get or Set alarm of temp
993 +
994 +AT+SHHUM: Get or Set alarm of moisture
995 +
789 789  (% style="color:#037691" %)**COAP Management**      
790 790  
791 791  AT+URI            : Resource parameters
... ... @@ -819,6 +819,7 @@
819 819  
820 820  = ​5.  FAQ =
821 821  
1029 +
822 822  == 5.1 ​ How to Upgrade Firmware ==
823 823  
824 824  
... ... @@ -834,7 +834,7 @@
834 834  
835 835  
836 836  (((
837 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1045 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
838 838  )))
839 839  )))
840 840  
... ... @@ -842,6 +842,7 @@
842 842  
843 843  = 6.  Trouble Shooting =
844 844  
1053 +
845 845  == 6.1  ​Connection problem when uploading firmware ==
846 846  
847 847  
... ... @@ -857,6 +857,7 @@
857 857  
858 858  == 6.2  AT Command input doesn't work ==
859 859  
1069 +
860 860  (((
861 861  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.
862 862  
... ... @@ -906,5 +906,6 @@
906 906  
907 907  = 9.  Support =
908 908  
1119 +
909 909  * 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.
910 910  * 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,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
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