Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.3 >
edited by Xiaoling
on 2022/10/15 10:08
To version < 115.4 >
edited by Xiaoling
on 2022/07/09 17:16
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,6 @@
9 9  
10 10  **Table of Contents:**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
... ... @@ -17,35 +17,21 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 -
21 21  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 22  
23 23  (((
24 24  
25 25  
26 -(((
27 27  The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
28 -)))
29 29  
30 -(((
31 31  The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
32 -)))
33 33  
34 -(((
35 35  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 -)))
37 37  
38 -(((
39 39  N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
40 -)))
41 41  
42 -(((
43 -
44 -)))
45 45  
46 -(((
47 47  ~* make sure you have NB-IoT coverage locally.
48 -)))
49 49  
50 50  
51 51  )))
... ... @@ -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
... ... @@ -70,6 +70,7 @@
70 70  
71 71  
72 72  
57 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -89,6 +89,7 @@
89 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
77 +
92 92  * Li/SOCI2 un-chargeable battery
93 93  * Capacity: 8500mAh
94 94  * Self Discharge: <1% / Year @ 25°C
... ... @@ -97,9 +97,9 @@
97 97  
98 98  
99 99  
86 +
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  
100 +== 1.5  Pin Definitions ==
114 114  
115 -== 1.5  Pin Definitions & Switch ==
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,20 +131,14 @@
131 131  
132 132  === 1.5.2 BOOT MODE / SW1 ===
133 133  
115 +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 134  
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.
137 -)))
117 +2) Flash: work mode, device starts to work and send out console output for further debug
138 138  
139 -(((
140 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
141 -)))
142 142  
143 143  
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,14 @@
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
131 +1. When boot the device in flash mode
132 +1. Send an uplink packet
158 158  
159 -2.  Send an uplink packet
160 160  
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  
... ... @@ -179,7 +179,7 @@
179 179  
180 180  )))
181 181  
182 -[[image:1657520100595-569.png]]
153 +[[image:1657350248151-650.png]]
183 183  
184 184  (((
185 185  
... ... @@ -195,49 +195,26 @@
195 195  [[image:image-20220709150546-2.png]]
196 196  
197 197  
198 -
199 199  === 2.2.1 Test Requirement ===
200 200  
201 201  
202 -(((
203 203  To use N95S31B in your city, make sure meet below requirements:
204 -)))
205 205  
206 -* (((
207 -Your local operator has already distributed a NB-IoT Network there.
208 -)))
209 -* (((
210 -The local NB-IoT network used the band that N95S31B supports.
211 -)))
212 -* (((
213 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
214 -)))
174 +* Your local operator has already distributed a NB-IoT Network there.
175 +* The local NB-IoT network used the band that N95S31B supports.
176 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
215 215  
216 -(((
217 217  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
218 -)))
219 219  
220 -(((
221 221  N95S31B supports different communication protocol such as :
222 -)))
223 223  
224 224  (((
225 -* (((
226 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
227 -)))
228 -* (((
229 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
230 -)))
231 -* (((
232 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
233 -)))
234 -* (((
235 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
236 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
237 237  
238 -(((
239 239  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.
240 -)))
241 241  
242 242  
243 243  )))
... ... @@ -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,18 +264,14 @@
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  
278 -
279 279  **Connection:**
280 280  
281 281   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -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]]**
246 +(% 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  
253 +(% 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
264 +(% 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
267 +(% 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
305 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
306 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
307 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
308 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
309 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% 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,104 +413,58 @@
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 -(((
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.
431 -)))
358 +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.
432 432  
433 433  
434 -(((
435 435  For example:
436 -)))
437 437  
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.
440 -)))
363 + (% 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.
441 441  
442 442  
443 -(((
444 444  The uplink payloads are composed in  ASCII String. For example:
445 -)))
446 446  
447 -(((
448 448  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
449 -)))
450 450  
451 -(((
452 452  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
453 -)))
454 454  
455 455  
456 -(((
457 457  (% style="color:red" %)**NOTE:**
458 -)))
459 459  
460 460  (% style="color:red" %)
461 -1. (((
462 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
463 -)))
464 -1. (((
465 -**By default, the device will send an uplink message every 1 hour.**
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
466 466  
467 467  
468 468  
469 -
470 -)))
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="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %)
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
482 482  |=(% style="width: 60px;" %)(((
483 483  **Size(bytes)**
484 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2**
485 -|(% 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" %)(((
486 -(((
389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
487 487  Reserve/ Same as NBSN95 CFGMOD=1
488 -)))
489 489  
490 -(((
491 491  No function here.
492 -)))
493 -)))|(% style="width:102px" %)(((
494 -(((
495 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
496 -)))
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
497 497  
498 -(((
499 499  By SHT31
500 -)))
501 -)))|(% style="width:81px" %)(((
502 -(((
503 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
504 -)))
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
505 505  
506 -(((
507 507  By SHT31
508 508  )))
509 -)))
510 510  
511 511  (((
512 -
513 -
514 514  (((
515 515  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
516 516  )))
... ... @@ -520,90 +520,29 @@
520 520  [[image:1657354294009-643.png]]
521 521  
522 522  
523 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
524 524  
525 -**where:**
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
526 526  
527 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
528 528  
529 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
530 -
531 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
532 -
533 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
534 -
535 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
536 -
537 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
538 -
539 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
540 -
541 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
542 -
543 543  (((
544 544  
428 +)))
545 545  
546 -
430 +(((
547 547  
548 548  )))
549 549  
550 -==== 2.3.1.2 Since Firmware v1.2 ====
551 551  
552 -
553 -In this mode, uplink payload includes 91 bytes in total by default.
554 -
555 -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.
556 -
557 -
558 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
559 -|(% 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**
560 -|(% 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 .....
561 -
562 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
563 -
564 -
565 -[[image:image-20220908154949-1.png]]
566 -
567 -
568 -The payload is ASCII string, representative same HEX:
569 -
570 -**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__ **
571 -
572 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
573 -
574 -**where:**
575 -
576 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
577 -
578 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
579 -
580 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
581 -
582 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
583 -
584 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
585 -
586 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
587 -
588 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
589 -
590 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
591 -
592 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
593 -
594 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
595 -
596 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
597 -
598 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
599 -
600 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
601 -
602 -
603 -
604 604  === 2.3.2  Device ID ===
605 605  
606 -
607 607  (((
608 608  By default, the Device ID equal to the last 6 bytes of IMEI.
609 609  )))
... ... @@ -610,12 +610,10 @@
610 610  
611 611  (((
612 612  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
613 -
614 -
615 615  )))
616 616  
617 617  (((
618 -(% style="color:blue" %)**Example:**
446 +**Example:**
619 619  )))
620 620  
621 621  (((
... ... @@ -623,47 +623,22 @@
623 623  )))
624 624  
625 625  (((
626 -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.
627 -
628 -
454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
629 629  )))
630 630  
631 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
632 632  
633 633  
634 -By default, the Device ID equal to the last 15 bits of IMEI.
635 -
636 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
637 -
638 -
639 -(% style="color:blue" %)**Example:**
640 -
641 -AT+DEUI=868411056754138
642 -
643 -
644 -
645 645  === 2.3.3  Version Info ===
646 646  
647 647  
648 -(((
649 649  These bytes include the hardware and software version.
650 -)))
651 651  
652 -(((
653 653  Higher byte: Specify hardware version: always 0x00 for N95S31B
654 -)))
655 655  
656 -(((
657 657  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
658 -)))
659 659  
660 -(((
661 -
662 -)))
663 663  
664 -(((
665 665  For example: 0x00 6E: this device is N95S31B with firmware version 110.
666 -)))
667 667  
668 668  (((
669 669  
... ... @@ -672,7 +672,6 @@
672 672  
673 673  === 2.3.4  Battery Info ===
674 674  
675 -
676 676  (((
677 677  Ex1: 0x0B45 = 2885mV
678 678  )))
... ... @@ -685,7 +685,6 @@
685 685  
686 686  === 2.3.5  Signal Strength ===
687 687  
688 -
689 689  (((
690 690  NB-IoT Network signal Strength.
691 691  )))
... ... @@ -718,7 +718,6 @@
718 718  
719 719  === 2.3.6  Temperature & Humidity ===
720 720  
721 -
722 722  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
723 723  
724 724  [[image:image-20220709161741-3.png]]
... ... @@ -735,11 +735,10 @@
735 735  
736 736  
737 737  
738 -== 2.4  Downlink Payload ==
538 +== 2.5  Downlink Payload ==
739 739  
540 +By default, NDDS75 prints the downlink payload to console port.
740 740  
741 -By default, N95S31B prints the downlink payload to console port.
742 -
743 743  [[image:image-20220709100028-1.png]]
744 744  
745 745  
... ... @@ -776,7 +776,7 @@
776 776  )))
777 777  
778 778  (((
779 -If payload = 0x04FF, it will reset the N95S31B
578 +If payload = 0x04FF, it will reset the NDDS75
780 780  )))
781 781  
782 782  
... ... @@ -788,76 +788,13 @@
788 788  
789 789  
790 790  
791 -== 2.5  Humidity and Temperature alarm function ==
792 -
793 -
794 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
795 -
796 -
797 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
798 -
799 -
800 -² When min=0, and max≠0, Alarm higher than max
801 -
802 -² When min≠0, and max=0, Alarm lower than min
803 -
804 -² When min≠0 and max≠0, Alarm higher than max or lower than min
805 -
806 -
807 - (% style="color:blue" %)**Example:**
808 -
809 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
810 -
811 -
812 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
813 -
814 -² When min=0, and max≠0, Alarm higher than max
815 -
816 -² When min≠0, and max=0, Alarm lower than min
817 -
818 -² When min≠0 and max≠0, Alarm higher than max or lower than min
819 -
820 -
821 -**~ (% style="color:blue" %)Example:(%%)**
822 -
823 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
824 -
825 -
826 -
827 -== 2.6 Set the number of data to be uploaded and the recording time ==
828 -
829 -
830 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
831 -
832 -* (% 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)
833 -* (% 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.
834 -
835 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
836 -
837 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
838 -
839 -
840 -
841 -== 2.7 Read or Clear cached data ==
842 -
843 -
844 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
845 -
846 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
847 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
848 -
849 -[[image:image-20220908163102-2.png]]
850 -
851 -
852 -
853 853  == 2.8  ​Battery Analysis ==
854 854  
855 -
856 856  === 2.8.1  ​Battery Type ===
857 857  
858 858  
859 859  (((
860 -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.
596 +The NDDS75 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.
861 861  )))
862 862  
863 863  (((
... ... @@ -880,35 +880,54 @@
880 880  
881 881  === 2.8.2  Power consumption Analyze ===
882 882  
619 +(((
620 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
621 +)))
883 883  
623 +
884 884  (((
885 -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.
625 +Instruction to use as below:
886 886  )))
887 887  
888 888  (((
889 -
629 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
890 890  )))
891 891  
892 892  
893 -=== 2.8.3  ​Battery Note ===
633 +(((
634 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
635 +)))
894 894  
637 +* (((
638 +Product Model
639 +)))
640 +* (((
641 +Uplink Interval
642 +)))
643 +* (((
644 +Working Mode
645 +)))
895 895  
896 896  (((
897 -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.
648 +And the Life expectation in difference case will be shown on the right.
898 898  )))
899 899  
651 +[[image:image-20220709110451-3.png]]
900 900  
901 901  
902 -=== 2.8.4  Replace the battery ===
903 903  
655 +=== 2.8.3  ​Battery Note ===
904 904  
905 905  (((
906 -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.
658 +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 transmit LoRa, then the battery life may be decreased.
907 907  )))
908 908  
909 909  
662 +
663 +=== 2.8.4  Replace the battery ===
664 +
910 910  (((
911 -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).
666 +The default battery pack of NDDS75 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).
912 912  )))
913 913  
914 914  
... ... @@ -915,7 +915,6 @@
915 915  
916 916  = 3. ​ Access NB-IoT Module =
917 917  
918 -
919 919  (((
920 920  Users can directly access the AT command set of the NB-IoT module.
921 921  )))
... ... @@ -922,8 +922,6 @@
922 922  
923 923  (((
924 924  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/]] 
925 -
926 -
927 927  )))
928 928  
929 929  [[image:1657333200519-600.png]]
... ... @@ -932,13 +932,11 @@
932 932  
933 933  = 4.  Using the AT Commands =
934 934  
935 -
936 936  == 4.1  Access AT Commands ==
937 937  
689 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
938 938  
939 -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]]
940 940  
941 -
942 942  AT+<CMD>?  : Help on <CMD>
943 943  
944 944  AT+<CMD>         : Run <CMD>
... ... @@ -978,24 +978,7 @@
978 978  
979 979  AT+SERVADDR  : Server Address
980 980  
981 -AT+TR      : Get or Set record time
982 982  
983 -AT+APN     : Get or set the APN
984 -
985 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
986 -
987 -AT+DNSCFG  : Get or Set DNS Server
988 -
989 -AT+GETSENSORVALUE   : Returns the current sensor measurement
990 -
991 -AT+NOUD      : Get or Set the number of data to be uploaded
992 -
993 -AT+CDP     : Read or Clear cached data
994 -
995 -AT+SHTEMP: Get or Set alarm of temp
996 -
997 -AT+SHHUM: Get or Set alarm of moisture
998 -
999 999  (% style="color:#037691" %)**COAP Management**      
1000 1000  
1001 1001  AT+URI            : Resource parameters
... ... @@ -1029,7 +1029,6 @@
1029 1029  
1030 1030  = ​5.  FAQ =
1031 1031  
1032 -
1033 1033  == 5.1 ​ How to Upgrade Firmware ==
1034 1034  
1035 1035  
... ... @@ -1042,18 +1042,13 @@
1042 1042  )))
1043 1043  
1044 1044  (((
1045 -
1046 -
1047 -(((
1048 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
777 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1049 1049  )))
1050 -)))
1051 1051  
1052 1052  
1053 1053  
1054 1054  = 6.  Trouble Shooting =
1055 1055  
1056 -
1057 1057  == 6.1  ​Connection problem when uploading firmware ==
1058 1058  
1059 1059  
... ... @@ -1069,7 +1069,6 @@
1069 1069  
1070 1070  == 6.2  AT Command input doesn't work ==
1071 1071  
1072 -
1073 1073  (((
1074 1074  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.
1075 1075  
... ... @@ -1080,7 +1080,7 @@
1080 1080  = 7. ​ Order Info =
1081 1081  
1082 1082  
1083 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
809 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1084 1084  
1085 1085  
1086 1086  (% class="wikigeneratedid" %)
... ... @@ -1095,7 +1095,7 @@
1095 1095  
1096 1096  (% style="color:#037691" %)**Package Includes**:
1097 1097  
1098 -* N95S31B NB-IoT Temperature and Humidity Sensor
824 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1099 1099  * External antenna x 1
1100 1100  )))
1101 1101  
... ... @@ -1104,10 +1104,11 @@
1104 1104  
1105 1105  (% style="color:#037691" %)**Dimension and weight**:
1106 1106  
833 +
1107 1107  * Device Size: 13.0 x 5 x 4.5 cm
1108 1108  * Device Weight: 150g
1109 -* Package Size / pcs : 14.0 x 8x 5 cm
1110 -* Weight / pcs : 180g
836 +* Package Size / pcs : 15 x 12x 5.5 cm
837 +* Weight / pcs : 220g
1111 1111  )))
1112 1112  
1113 1113  (((
... ... @@ -1119,6 +1119,5 @@
1119 1119  
1120 1120  = 9.  Support =
1121 1121  
1122 -
1123 1123  * 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.
1124 1124  * 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,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
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