Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.32 >
edited by Xiaoling
on 2022/07/11 09:06
To version < 129.36 >
edited by Xiaoling
on 2023/04/03 17:01
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
58 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -68,7 +68,6 @@
68 68  
69 69  
70 70  
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -77,17 +77,15 @@
77 77  * Supply Voltage: 2.1v ~~ 3.6v
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
80 -
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 -* - B1 @H-FDD: 2100MHz
84 -* - B3 @H-FDD: 1800MHz
85 -* - B8 @H-FDD: 900MHz
86 -* - B5 @H-FDD: 850MHz
87 -* - B20 @H-FDD: 800MHz
88 -* - B28 @H-FDD: 700MHz
82 +* B1 @H-FDD: 2100MHz
83 +* B3 @H-FDD: 1800MHz
84 +* B8 @H-FDD: 900MHz
85 +* B5 @H-FDD: 850MHz
86 +* B20 @H-FDD: 800MHz
87 +* B28 @H-FDD: 700MHz
89 89  
90 -
91 91  (% style="color:#037691" %)**Battery:**
92 92  
93 93  * Li/SOCI2 un-chargeable battery
... ... @@ -98,9 +98,9 @@
98 98  
99 99  
100 100  
101 -
102 102  == ​1.4  Applications ==
103 103  
101 +
104 104  * Smart Buildings & Home Automation
105 105  * Logistics and Supply Chain Management
106 106  * Smart Metering
... ... @@ -112,47 +112,49 @@
112 112  ​
113 113  
114 114  
115 -== 1.5  Pin Definitions ==
113 +== 1.5  Pin Definitions & Switch ==
116 116  
115 +
117 117  N95S31B use the mother board from NBSN95 which as below.
118 118  
118 +
119 119  [[image:image-20220709144723-1.png]]
120 120  
121 121  
122 122  === 1.5.1 Jumper JP2 ===
123 123  
124 +
124 124  Power on Device when put this jumper.
125 125  
126 126  
127 -
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
130 +
130 130  (((
131 -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.
132 +**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.
132 132  )))
133 133  
134 134  (((
135 -2) Flash: work mode, device starts to work and send out console output for further debug
136 +**2) Flash:**  work mode, device starts to work and send out console output for further debug
136 136  )))
137 137  
138 138  
139 -
140 140  === 1.5.3 Reset Button ===
141 141  
142 +
142 142  Press to reboot the device.
143 143  
144 144  
145 -
146 146  === 1.5.4 LED ===
147 147  
148 +
148 148  It will flash:
149 149  
150 -1. When boot the device in flash mode
151 -1. Send an uplink packet
151 +1.  When boot the device in flash mode
152 152  
153 +2.  Send an uplink packet
153 153  
154 154  
155 -
156 156  = 2.  Use N95S31B to communicate with IoT Server =
157 157  
158 158  == 2.1  How it works ==
... ... @@ -171,7 +171,7 @@
171 171  
172 172  )))
173 173  
174 -[[image:1657350248151-650.png]]
174 +[[image:1657520100595-569.png]]
175 175  
176 176  (((
177 177  
... ... @@ -180,7 +180,6 @@
180 180  
181 181  == 2.2 ​ Configure the N95S31B ==
182 182  
183 -
184 184  === 2.2.1  Power On N95S31B ===
185 185  
186 186  
... ... @@ -187,7 +187,7 @@
187 187  [[image:image-20220709150546-2.png]]
188 188  
189 189  
190 -=== 2.2.1 Test Requirement ===
189 +=== 2.2.2 Test Requirement ===
191 191  
192 192  
193 193  (((
... ... @@ -236,9 +236,9 @@
236 236  [[image:1657350625843-586.png]]
237 237  
238 238  
239 -
240 240  === 2.2.3  Insert SIM card ===
241 241  
240 +
242 242  (((
243 243  Insert the NB-IoT Card get from your provider.
244 244  )))
... ... @@ -251,26 +251,29 @@
251 251  [[image:1657351240556-536.png]]
252 252  
253 253  
254 -
255 255  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
256 256  
255 +
257 257  (((
258 258  (((
259 259  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.
259 +
260 +
260 260  )))
261 261  )))
262 262  
263 263  [[image:1657351312545-300.png]]
264 264  
265 -**Connection:**
266 266  
267 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
267 +(% style="color:blue" %)**Connection:**
268 268  
269 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
269 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
270 270  
271 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
271 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
272 272  
273 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
273 273  
275 +
274 274  In the PC, use below serial tool settings:
275 275  
276 276  * Baud:  (% style="color:green" %)**9600**
... ... @@ -285,17 +285,18 @@
285 285  
286 286  [[image:1657329814315-101.png]]
287 287  
290 +
288 288  (((
289 -(% 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/]]
292 +(% 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]]**
290 290  )))
291 291  
292 292  
293 -
294 294  === 2.2.5  Use CoAP protocol to uplink data ===
295 295  
296 -(% 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/]]
297 297  
299 +(% 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  
301 +
299 299  (((
300 300  **Use below commands:**
301 301  )))
... ... @@ -304,10 +304,10 @@
304 304  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
305 305  )))
306 306  * (((
307 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
310 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
308 308  )))
309 309  * (((
310 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
313 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
311 311  )))
312 312  
313 313  (((
... ... @@ -326,7 +326,6 @@
326 326  [[image:1657352185396-303.png]]
327 327  
328 328  
329 -
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  
343 -
344 344  === 2.2.7  Use MQTT protocol to uplink data ===
345 345  
347 +
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
350 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
351 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
352 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
353 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
354 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
355 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/  Set the sending topic of MQTT
356 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/  Set the subscription topic of MQTT
355 355  
356 356  [[image:1657352634421-276.png]]
357 357  
... ... @@ -358,6 +358,7 @@
358 358  
359 359  [[image:1657352645687-385.png]]
360 360  
363 +
361 361  (((
362 362  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.
363 363  )))
... ... @@ -368,9 +368,9 @@
368 368  )))
369 369  
370 370  
371 -
372 372  === 2.2.8  Use TCP protocol to uplink data ===
373 373  
376 +
374 374  This feature is supported since firmware version v110
375 375  
376 376  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -382,9 +382,9 @@
382 382  [[image:1657352914475-252.png]]
383 383  
384 384  
385 -
386 386  === 2.2.9  Change Update Interval ===
387 387  
390 +
388 388  User can use below command to change the (% style="color:green" %)**uplink interval**.
389 389  
390 390  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -393,13 +393,20 @@
393 393  
394 394  )))
395 395  
399 +(((
400 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
401 +)))
396 396  
403 +(((
404 +(% 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).**
405 +)))
397 397  
407 +
398 398  == 2.3  Uplink Payload ==
399 399  
400 400  
401 401  (((
402 -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.
412 +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.
403 403  )))
404 404  
405 405  
... ... @@ -408,7 +408,7 @@
408 408  )))
409 409  
410 410  (((
411 - (% 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.
421 + (% 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.
412 412  )))
413 413  
414 414  
... ... @@ -431,23 +431,26 @@
431 431  
432 432  (% style="color:red" %)
433 433  1. (((
434 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
444 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
435 435  )))
436 436  1. (((
437 -By default, the device will send an uplink message every 1 hour.
438 -)))
447 +**By default, the device will send an uplink message every 1 hour.**
439 439  
440 440  
450 +
451 +)))
452 +
441 441  === 2.3.1  Payload Analyze ===
442 442  
455 +==== 2.3.1.1  Before Firmware v1.2 ====
456 +
457 +
443 443  N95S31B uplink payload includes in total 21 bytes
444 444  
445 445  
446 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
447 -|=(% style="width: 60px;" %)(((
448 -**Size(bytes)**
449 -)))|=(% 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**
450 -|(% 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" %)(((
461 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
462 +|=(% 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**
463 +|(% 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" %)(((
451 451  (((
452 452  Reserve/ Same as NBSN95 CFGMOD=1
453 453  )))
... ... @@ -455,7 +455,7 @@
455 455  (((
456 456  No function here.
457 457  )))
458 -)))|(% style="width:77px" %)(((
471 +)))|(% style="width:102px" %)(((
459 459  (((
460 460  [[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
461 461  )))
... ... @@ -463,7 +463,7 @@
463 463  (((
464 464  By SHT31
465 465  )))
466 -)))|(% style="width:80px" %)(((
479 +)))|(% style="width:81px" %)(((
467 467  (((
468 468  [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
469 469  )))
... ... @@ -474,6 +474,8 @@
474 474  )))
475 475  
476 476  (((
490 +
491 +
477 477  (((
478 478  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
479 479  )))
... ... @@ -483,29 +483,89 @@
483 483  [[image:1657354294009-643.png]]
484 484  
485 485  
486 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
501 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
487 487  
488 -* Device ID: 0x724031607457 = 724031607457
489 -* Version: 0x006e=110=1.1.0
503 +**where:**
490 490  
491 -* BAT: 0x0ccd = 3277 mV = 3.277V
492 -* Signal: 0x1b = 27
493 -* Model: 0x01 = 1
494 -* 0x00dc000ccc= reserve, ignore in N95S31B
495 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
496 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
505 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
497 497  
507 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
508 +
509 +* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
510 +
511 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
512 +
513 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
514 +
515 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
516 +
517 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
518 +
519 +* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
520 +
498 498  (((
499 499  
500 -)))
501 501  
502 -(((
503 503  
504 504  )))
505 505  
527 +==== 2.3.1.2 Since Firmware v1.2 ====
506 506  
529 +
530 +In this mode, uplink payload includes 91 bytes in total by default.
531 +
532 +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.
533 +
534 +
535 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
536 +|=(% 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**
537 +|=(% 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 .....
538 +
539 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
540 +
541 +
542 +[[image:image-20220908154949-1.png]]
543 +
544 +
545 +The payload is ASCII string, representative same HEX:
546 +
547 +**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__ **
548 +
549 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
550 +
551 +**where:**
552 +
553 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
554 +
555 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
556 +
557 +* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
558 +
559 +* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
560 +
561 +* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
562 +
563 +* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
564 +
565 +* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
566 +
567 +* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
568 +
569 +* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
570 +
571 +* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
572 +
573 +* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
574 +
575 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
576 +
577 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
578 +
579 +
580 +
507 507  === 2.3.2  Device ID ===
508 508  
583 +
509 509  (((
510 510  By default, the Device ID equal to the last 6 bytes of IMEI.
511 511  )))
... ... @@ -512,10 +512,12 @@
512 512  
513 513  (((
514 514  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
590 +
591 +
515 515  )))
516 516  
517 517  (((
518 -**Example:**
595 +(% style="color:blue" %)**Example:**
519 519  )))
520 520  
521 521  (((
... ... @@ -523,30 +523,54 @@
523 523  )))
524 524  
525 525  (((
526 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
603 +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.
604 +
605 +
527 527  )))
528 528  
608 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
529 529  
530 530  
611 +By default, the Device ID equal to the last 15 bits of IMEI.
612 +
613 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
614 +
615 +
616 +(% style="color:blue" %)**Example:**
617 +
618 +AT+DEUI=868411056754138
619 +
620 +
531 531  === 2.3.3  Version Info ===
532 532  
533 533  
624 +(((
534 534  These bytes include the hardware and software version.
626 +)))
535 535  
628 +(((
536 536  Higher byte: Specify hardware version: always 0x00 for N95S31B
630 +)))
537 537  
632 +(((
538 538  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
634 +)))
539 539  
636 +(((
637 +
638 +)))
540 540  
640 +(((
541 541  For example: 0x00 6E: this device is N95S31B with firmware version 110.
642 +)))
542 542  
543 543  (((
544 544  
545 545  )))
546 546  
547 -
548 548  === 2.3.4  Battery Info ===
549 549  
650 +
550 550  (((
551 551  Ex1: 0x0B45 = 2885mV
552 552  )))
... ... @@ -556,9 +556,9 @@
556 556  )))
557 557  
558 558  
559 -
560 560  === 2.3.5  Signal Strength ===
561 561  
662 +
562 562  (((
563 563  NB-IoT Network signal Strength.
564 564  )))
... ... @@ -588,9 +588,9 @@
588 588  )))
589 589  
590 590  
591 -
592 592  === 2.3.6  Temperature & Humidity ===
593 593  
694 +
594 594  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
595 595  
596 596  [[image:image-20220709161741-3.png]]
... ... @@ -606,11 +606,11 @@
606 606  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
607 607  
608 608  
609 -
610 610  == 2.4  Downlink Payload ==
611 611  
612 -By default, NDDS75 prints the downlink payload to console port.
613 613  
713 +By default, N95S31B prints the downlink payload to console port.
714 +
614 614  [[image:image-20220709100028-1.png]]
615 615  
616 616  
... ... @@ -647,7 +647,7 @@
647 647  )))
648 648  
649 649  (((
650 -If payload = 0x04FF, it will reset the NDDS75
751 +If payload = 0x04FF, it will reset the N95S31B
651 651  )))
652 652  
653 653  
... ... @@ -658,69 +658,76 @@
658 658  )))
659 659  
660 660  
762 +== 2.5  Humidity and Temperature alarm function ==
661 661  
662 -== 2.5  ​Battery Analysis ==
663 663  
664 -=== 2.5.1  ​Battery Type ===
765 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
665 665  
666 666  
667 -(((
668 -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.
669 -)))
768 +(% style="color:#037691" %)**AT+ SHHUM=min,max**
670 670  
671 -(((
672 -The battery is designed to last for several years depends on the actually use environment and update interval. 
673 -)))
674 674  
675 -(((
676 -The battery related documents as below:
677 -)))
771 +² When min=0, and max≠0, Alarm higher than max
678 678  
679 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
680 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
681 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
773 +² When min≠0, and max=0, Alarm lower than min
682 682  
683 -(((
684 -[[image:image-20220709101450-2.png]]
685 -)))
775 +² When min≠0 and max≠0, Alarm higher than max or lower than min
686 686  
687 687  
778 + (% style="color:blue" %)**Example:**
688 688  
689 -=== 2.5.2  Power consumption Analyze ===
780 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
690 690  
691 -(((
692 -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.
693 -)))
694 694  
695 -(((
696 -
697 -)))
783 +(% style="color:#037691" %)**AT+ SHTEMP=min,max**
698 698  
785 +² When min=0, and max≠0, Alarm higher than max
699 699  
700 -=== 2.5.3  ​Battery Note ===
787 +² When min≠0, and max=0, Alarm lower than min
701 701  
702 -(((
703 -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.
704 -)))
789 +² When min≠0 and max≠0, Alarm higher than max or lower than min
705 705  
706 706  
792 +**~ (% style="color:blue" %)Example:(%%)**
707 707  
708 -=== 2.5.4  Replace the battery ===
794 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
709 709  
710 710  
711 -(((
712 -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.
713 -)))
797 +== 2.6 Set the number of data to be uploaded and the recording time ==
714 714  
715 715  
716 -(((
717 -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).
718 -)))
800 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
719 719  
802 +* (% 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)
803 +* (% 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.
720 720  
805 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
721 721  
807 +[[image:image-20221009001045-1.png||height="726" width="1009"]]
808 +
809 +
810 +== 2.7 Read or Clear cached data ==
811 +
812 +
813 +**~ (% style="color:blue" %)➢ AT Command:(%%)**
814 +
815 +* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
816 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
817 +
818 +[[image:image-20220908163102-2.png]]
819 +
820 +
821 +== 2.8 Battery & Power Consumption ==
822 +
823 +
824 +N95S31B uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
825 +
826 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
827 +
828 +
722 722  = 3. ​ Access NB-IoT Module =
723 723  
831 +
724 724  (((
725 725  Users can directly access the AT command set of the NB-IoT module.
726 726  )))
... ... @@ -727,19 +727,21 @@
727 727  
728 728  (((
729 729  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 +
730 730  )))
731 731  
732 732  [[image:1657333200519-600.png]]
733 733  
734 734  
735 -
736 736  = 4.  Using the AT Commands =
737 737  
738 738  == 4.1  Access AT Commands ==
739 739  
740 -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/]]
741 741  
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]]
742 742  
852 +
743 743  AT+<CMD>?  : Help on <CMD>
744 744  
745 745  AT+<CMD>         : Run <CMD>
... ... @@ -779,7 +779,24 @@
779 779  
780 780  AT+SERVADDR  : Server Address
781 781  
892 +AT+TR      : Get or Set record time
782 782  
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 +
783 783  (% style="color:#037691" %)**COAP Management**      
784 784  
785 785  AT+URI            : Resource parameters
... ... @@ -810,7 +810,6 @@
810 810  AT+PWORD  : Serial Access Password
811 811  
812 812  
813 -
814 814  = ​5.  FAQ =
815 815  
816 816  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -827,11 +827,12 @@
827 827  (((
828 828  
829 829  
830 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
956 +(((
957 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
831 831  )))
959 +)))
832 832  
833 833  
834 -
835 835  = 6.  Trouble Shooting =
836 836  
837 837  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -846,9 +846,9 @@
846 846  
847 847  )))
848 848  
849 -
850 850  == 6.2  AT Command input doesn't work ==
851 851  
978 +
852 852  (((
853 853  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.
854 854  
... ... @@ -855,7 +855,6 @@
855 855  
856 856  )))
857 857  
858 -
859 859  = 7. ​ Order Info =
860 860  
861 861  
... ... @@ -862,11 +862,6 @@
862 862  Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
863 863  
864 864  
865 -(% class="wikigeneratedid" %)
866 -(((
867 -
868 -)))
869 -
870 870  = 8.  Packing Info =
871 871  
872 872  (((
... ... @@ -892,11 +892,14 @@
892 892  (((
893 893  
894 894  
895 -
896 896  
897 897  )))
898 898  
899 899  = 9.  Support =
900 900  
1021 +
901 901  * 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.
902 902  * 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 +
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