Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.27 >
edited by Xiaoling
on 2022/07/11 08:36
To version < 125.5 >
edited by Xiaoling
on 2022/09/09 16:02
>
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
... ... @@ -66,9 +66,6 @@
66 66  * Micro SIM card slot for NB-IoT SIM
67 67  * 8500mAh Battery for long term use
68 68  
69 -
70 -
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -88,7 +88,6 @@
88 88  
89 89  (% style="color:#037691" %)**Battery:**
90 90  
91 -
92 92  * Li/SOCI2 un-chargeable battery
93 93  * Capacity: 8500mAh
94 94  * Self Discharge: <1% / Year @ 25°C
... ... @@ -97,6 +97,7 @@
97 97  
98 98  == ​1.4  Applications ==
99 99  
98 +
100 100  * Smart Buildings & Home Automation
101 101  * Logistics and Supply Chain Management
102 102  * Smart Metering
... ... @@ -108,15 +108,21 @@
108 108  ​
109 109  
110 110  
111 -== 1.5  Pin Definitions ==
112 112  
111 +
112 +== 1.5  Pin Definitions & Switch ==
113 +
114 +
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
117 +
115 115  [[image:image-20220709144723-1.png]]
116 116  
117 117  
121 +
118 118  === 1.5.1 Jumper JP2 ===
119 119  
124 +
120 120  Power on Device when put this jumper.
121 121  
122 122  
... ... @@ -123,14 +123,20 @@
123 123  
124 124  === 1.5.2 BOOT MODE / SW1 ===
125 125  
131 +
132 +(((
126 126  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 +)))
127 127  
136 +(((
128 128  2) Flash: work mode, device starts to work and send out console output for further debug
138 +)))
129 129  
130 130  
131 131  
132 132  === 1.5.3 Reset Button ===
133 133  
144 +
134 134  Press to reboot the device.
135 135  
136 136  
... ... @@ -137,6 +137,7 @@
137 137  
138 138  === 1.5.4 LED ===
139 139  
151 +
140 140  It will flash:
141 141  
142 142  1. When boot the device in flash mode
... ... @@ -144,6 +144,7 @@
144 144  
145 145  = 2.  Use N95S31B to communicate with IoT Server =
146 146  
159 +
147 147  == 2.1  How it works ==
148 148  
149 149  
... ... @@ -160,7 +160,7 @@
160 160  
161 161  )))
162 162  
163 -[[image:1657350248151-650.png]]
176 +[[image:1657520100595-569.png]]
164 164  
165 165  (((
166 166  
... ... @@ -176,26 +176,49 @@
176 176  [[image:image-20220709150546-2.png]]
177 177  
178 178  
192 +
179 179  === 2.2.1 Test Requirement ===
180 180  
181 181  
196 +(((
182 182  To use N95S31B in your city, make sure meet below requirements:
198 +)))
183 183  
184 -* Your local operator has already distributed a NB-IoT Network there.
185 -* The local NB-IoT network used the band that N95S31B supports.
186 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
200 +* (((
201 +Your local operator has already distributed a NB-IoT Network there.
202 +)))
203 +* (((
204 +The local NB-IoT network used the band that N95S31B supports.
205 +)))
206 +* (((
207 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
208 +)))
187 187  
210 +(((
188 188  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
212 +)))
189 189  
214 +(((
190 190  N95S31B supports different communication protocol such as :
216 +)))
191 191  
192 192  (((
193 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
194 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
195 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
196 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
219 +* (((
220 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
221 +)))
222 +* (((
223 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
224 +)))
225 +* (((
226 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
227 +)))
228 +* (((
229 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
230 +)))
197 197  
232 +(((
198 198  We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
234 +)))
199 199  
200 200  
201 201  )))
... ... @@ -206,6 +206,7 @@
206 206  
207 207  === 2.2.3  Insert SIM card ===
208 208  
245 +
209 209  (((
210 210  Insert the NB-IoT Card get from your provider.
211 211  )))
... ... @@ -221,14 +221,18 @@
221 221  
222 222  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
223 223  
261 +
224 224  (((
225 225  (((
226 226  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.
265 +
266 +
227 227  )))
228 228  )))
229 229  
230 230  [[image:1657351312545-300.png]]
231 231  
272 +
232 232  **Connection:**
233 233  
234 234   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -252,8 +252,9 @@
252 252  
253 253  [[image:1657329814315-101.png]]
254 254  
296 +
255 255  (((
256 -(% 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/]]
298 +(% 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]]**
257 257  )))
258 258  
259 259  
... ... @@ -260,9 +260,10 @@
260 260  
261 261  === 2.2.5  Use CoAP protocol to uplink data ===
262 262  
263 -(% 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/]]
264 264  
306 +(% 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/]]**
265 265  
308 +
266 266  (((
267 267  **Use below commands:**
268 268  )))
... ... @@ -310,6 +310,7 @@
310 310  
311 311  === 2.2.7  Use MQTT protocol to uplink data ===
312 312  
356 +
313 313  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
314 314  
315 315  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
... ... @@ -325,6 +325,7 @@
325 325  
326 326  [[image:1657352645687-385.png]]
327 327  
372 +
328 328  (((
329 329  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.
330 330  )))
... ... @@ -338,6 +338,7 @@
338 338  
339 339  === 2.2.8  Use TCP protocol to uplink data ===
340 340  
386 +
341 341  This feature is supported since firmware version v110
342 342  
343 343  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -352,6 +352,7 @@
352 352  
353 353  === 2.2.9  Change Update Interval ===
354 354  
401 +
355 355  User can use below command to change the (% style="color:green" %)**uplink interval**.
356 356  
357 357  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -360,43 +360,76 @@
360 360  
361 361  )))
362 362  
410 +(((
411 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
412 +)))
363 363  
414 +(((
415 +(% 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).**
416 +)))
364 364  
418 +
419 +
365 365  == 2.3  Uplink Payload ==
366 366  
367 367  
368 -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.
423 +(((
424 +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.
425 +)))
369 369  
370 370  
428 +(((
371 371  For example:
430 +)))
372 372  
373 - (% 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.
432 +(((
433 + (% 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.
434 +)))
374 374  
375 375  
437 +(((
376 376  The uplink payloads are composed in  ASCII String. For example:
439 +)))
377 377  
441 +(((
378 378  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
443 +)))
379 379  
445 +(((
380 380  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
447 +)))
381 381  
382 382  
450 +(((
383 383  (% style="color:red" %)**NOTE:**
452 +)))
384 384  
385 385  (% style="color:red" %)
386 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
387 -1. By default, the device will send an uplink message every 1 hour.
455 +1. (((
456 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
457 +)))
458 +1. (((
459 +**By default, the device will send an uplink message every 1 hour.**
388 388  
389 389  
462 +
463 +
464 +)))
465 +
390 390  === 2.3.1  Payload Analyze ===
391 391  
468 +
469 +==== 2.3.1.1  Before Firmware v1.2 ====
470 +
471 +
392 392  N95S31B uplink payload includes in total 21 bytes
393 393  
394 394  
395 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
475 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
396 396  |=(% style="width: 60px;" %)(((
397 397  **Size(bytes)**
398 -)))|=(% 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**
399 -|(% 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" %)(((
478 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
479 +|(% 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:174px" %)(((
400 400  (((
401 401  Reserve/ Same as NBSN95 CFGMOD=1
402 402  )))
... ... @@ -404,7 +404,7 @@
404 404  (((
405 405  No function here.
406 406  )))
407 -)))|(% style="width:77px" %)(((
487 +)))|(% style="width:106px" %)(((
408 408  (((
409 409  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
410 410  )))
... ... @@ -412,7 +412,7 @@
412 412  (((
413 413  By SHT31
414 414  )))
415 -)))|(% style="width:80px" %)(((
495 +)))|(% style="width:85px" %)(((
416 416  (((
417 417  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
418 418  )))
... ... @@ -423,6 +423,8 @@
423 423  )))
424 424  
425 425  (((
506 +
507 +
426 426  (((
427 427  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
428 428  )))
... ... @@ -434,27 +434,82 @@
434 434  
435 435  The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
436 436  
437 -* Device ID: 0x724031607457 = 724031607457
438 -* Version: 0x006e=110=1.1.0
519 +* Device ID:  0x724031607457 = 724031607457
439 439  
440 -* BAT: 0x0ccd = 3277 mV = 3.277V
441 -* Signal: 0x1b = 27
442 -* Model: 0x01 = 1
521 +* Version:  0x006e=110=1.1.0
522 +
523 +* BAT:  0x0ccd = 3277 mV = 3.277V
524 +
525 +* Signal:  0x1b = 27
526 +
527 +* Model:  0x01 = 1
528 +
443 443  * 0x00dc000ccc= reserve, ignore in N95S31B
444 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
445 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
446 446  
531 +* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
532 +
533 +* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
534 +
447 447  (((
448 448  
449 -)))
450 450  
451 -(((
538 +
452 452  
453 453  )))
454 454  
542 +==== 2.3.1.2 Since Firmware v1.2 ====
455 455  
544 +
545 +In this mode, uplink payload includes 91 bytes in total by default.
546 +
547 +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.
548 +
549 +
550 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
551 +|(% 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**
552 +|(% 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 .....
553 +
554 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
555 +
556 +
557 +[[image:image-20220908154949-1.png]]
558 +
559 +
560 +The payload is ASCII string, representative same HEX:
561 +
562 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
563 +
564 +* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
565 +
566 +* (% style="color:blue" %)Version: 0x000c=120=1.2
567 +
568 +* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
569 +
570 +* (% style="color:red" %)Singal: 0x0c = 12
571 +
572 +* (% style="color:blue" %)Mod: 0x01 = 1
573 +
574 +* TemDS18B20: 0x0000= 0 = 0
575 +
576 +* (% style="color:green" %)Interrupt: 0x00= 0
577 +
578 +* (% style="color:green" %)adc: 0x0030= 48
579 +
580 +* SHTTEM: 0x0114= 276 = 27.6
581 +
582 +* SHTHUM:0x0231 =561=56.1%
583 +
584 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
585 +
586 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
587 +
588 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
589 +
590 +
591 +
456 456  === 2.3.2  Device ID ===
457 457  
594 +
458 458  (((
459 459  By default, the Device ID equal to the last 6 bytes of IMEI.
460 460  )))
... ... @@ -461,10 +461,13 @@
461 461  
462 462  (((
463 463  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
601 +
602 +
464 464  )))
465 465  
466 466  (((
467 -**Example:**
606 +*
607 +** (% style="color:blue" %)Example:
468 468  )))
469 469  
470 470  (((
... ... @@ -472,22 +472,48 @@
472 472  )))
473 473  
474 474  (((
475 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
615 +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.
616 +
617 +
476 476  )))
477 477  
620 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
478 478  
479 479  
623 +By default, the Device ID equal to the last 15 bits of IMEI.
624 +
625 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
626 +
627 +
628 +*
629 +** (% style="color:blue" %)Example:
630 +
631 +AT+DEUI=868411056754138
632 +
633 +
634 +
480 480  === 2.3.3  Version Info ===
481 481  
482 482  
638 +(((
483 483  These bytes include the hardware and software version.
640 +)))
484 484  
642 +(((
485 485  Higher byte: Specify hardware version: always 0x00 for N95S31B
644 +)))
486 486  
646 +(((
487 487  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
648 +)))
488 488  
650 +(((
651 +
652 +)))
489 489  
654 +(((
490 490  For example: 0x00 6E: this device is N95S31B with firmware version 110.
656 +)))
491 491  
492 492  (((
493 493  
... ... @@ -496,6 +496,7 @@
496 496  
497 497  === 2.3.4  Battery Info ===
498 498  
665 +
499 499  (((
500 500  Ex1: 0x0B45 = 2885mV
501 501  )))
... ... @@ -508,6 +508,7 @@
508 508  
509 509  === 2.3.5  Signal Strength ===
510 510  
678 +
511 511  (((
512 512  NB-IoT Network signal Strength.
513 513  )))
... ... @@ -540,6 +540,7 @@
540 540  
541 541  === 2.3.6  Temperature & Humidity ===
542 542  
711 +
543 543  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
544 544  
545 545  [[image:image-20220709161741-3.png]]
... ... @@ -558,8 +558,9 @@
558 558  
559 559  == 2.4  Downlink Payload ==
560 560  
561 -By default, NDDS75 prints the downlink payload to console port.
562 562  
731 +By default, N95S31B prints the downlink payload to console port.
732 +
563 563  [[image:image-20220709100028-1.png]]
564 564  
565 565  
... ... @@ -596,7 +596,7 @@
596 596  )))
597 597  
598 598  (((
599 -If payload = 0x04FF, it will reset the NDDS75
769 +If payload = 0x04FF, it will reset the N95S31B
600 600  )))
601 601  
602 602  
... ... @@ -608,11 +608,73 @@
608 608  
609 609  
610 610  
611 -== 2.5  ​Battery Analysis ==
781 +== 2.5  Humidity and Temperature alarm function ==
612 612  
613 -=== 2.5.1  ​Battery Type ===
614 614  
784 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
615 615  
786 +
787 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
788 +
789 +
790 +² When min=0, and max≠0, Alarm higher than max
791 +
792 +² When min≠0, and max=0, Alarm lower than min
793 +
794 +² When min≠0 and max≠0, Alarm higher than max or lower than min
795 +
796 +
797 + (% style="color:blue" %)**Example:**
798 +
799 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
800 +
801 +
802 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
803 +
804 +² When min=0, and max≠0, Alarm higher than max
805 +
806 +² When min≠0, and max=0, Alarm lower than min
807 +
808 +² When min≠0 and max≠0, Alarm higher than max or lower than min
809 +
810 +
811 +**~ (% style="color:blue" %)Example:(%%)**
812 +
813 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
814 +
815 +
816 +
817 +== 2.6 Set the number of data to be uploaded and the recording time ==
818 +
819 +
820 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
821 +
822 +* (% 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)
823 +* (% 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.
824 +
825 +
826 +
827 +
828 +== 2.7 Read or Clear cached data ==
829 +
830 +
831 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
832 +
833 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
834 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
835 +
836 +
837 +
838 +[[image:image-20220908163102-2.png]]
839 +
840 +
841 +
842 +== 2.8  ​Battery Analysis ==
843 +
844 +
845 +=== 2.8.1  ​Battery Type ===
846 +
847 +
616 616  (((
617 617  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.
618 618  )))
... ... @@ -635,10 +635,11 @@
635 635  
636 636  
637 637  
638 -=== 2.5.2  Power consumption Analyze ===
870 +=== 2.8.2  Power consumption Analyze ===
639 639  
872 +
640 640  (((
641 -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.
874 +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.
642 642  )))
643 643  
644 644  (((
... ... @@ -646,8 +646,9 @@
646 646  )))
647 647  
648 648  
649 -=== 2.5.3  ​Battery Note ===
882 +=== 2.8.3  ​Battery Note ===
650 650  
884 +
651 651  (((
652 652  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.
653 653  )))
... ... @@ -654,7 +654,7 @@
654 654  
655 655  
656 656  
657 -=== 2.5.4  Replace the battery ===
891 +=== 2.8.4  Replace the battery ===
658 658  
659 659  
660 660  (((
... ... @@ -670,6 +670,7 @@
670 670  
671 671  = 3. ​ Access NB-IoT Module =
672 672  
907 +
673 673  (((
674 674  Users can directly access the AT command set of the NB-IoT module.
675 675  )))
... ... @@ -676,6 +676,8 @@
676 676  
677 677  (((
678 678  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/]] 
914 +
915 +
679 679  )))
680 680  
681 681  [[image:1657333200519-600.png]]
... ... @@ -684,11 +684,13 @@
684 684  
685 685  = 4.  Using the AT Commands =
686 686  
924 +
687 687  == 4.1  Access AT Commands ==
688 688  
689 -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/]]
690 690  
928 +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]]
691 691  
930 +
692 692  AT+<CMD>?  : Help on <CMD>
693 693  
694 694  AT+<CMD>         : Run <CMD>
... ... @@ -728,7 +728,24 @@
728 728  
729 729  AT+SERVADDR  : Server Address
730 730  
970 +AT+TR      : Get or Set record time
731 731  
972 +AT+APN     : Get or set the APN
973 +
974 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
975 +
976 +AT+DNSCFG  : Get or Set DNS Server
977 +
978 +AT+GETSENSORVALUE   : Returns the current sensor measurement
979 +
980 +AT+NOUD      : Get or Set the number of data to be uploaded
981 +
982 +AT+CDP     : Read or Clear cached data
983 +
984 +AT+SHTEMP: Get or Set alarm of temp
985 +
986 +AT+SHHUM: Get or Set alarm of moisture
987 +
732 732  (% style="color:#037691" %)**COAP Management**      
733 733  
734 734  AT+URI            : Resource parameters
... ... @@ -762,6 +762,7 @@
762 762  
763 763  = ​5.  FAQ =
764 764  
1021 +
765 765  == 5.1 ​ How to Upgrade Firmware ==
766 766  
767 767  
... ... @@ -776,13 +776,16 @@
776 776  (((
777 777  
778 778  
779 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
1036 +(((
1037 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
780 780  )))
1039 +)))
781 781  
782 782  
783 783  
784 784  = 6.  Trouble Shooting =
785 785  
1045 +
786 786  == 6.1  ​Connection problem when uploading firmware ==
787 787  
788 788  
... ... @@ -798,6 +798,7 @@
798 798  
799 799  == 6.2  AT Command input doesn't work ==
800 800  
1061 +
801 801  (((
802 802  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.
803 803  
... ... @@ -847,5 +847,10 @@
847 847  
848 848  = 9.  Support =
849 849  
1111 +
850 850  * 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.
851 851  * 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]]
1114 +
1115 +
1116 +
1117 +
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

Applications

Navigation

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