Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.32 >
edited by Xiaoling
on 2022/10/25 18:13
To version < 114.2 >
edited by Xiaoling
on 2022/07/09 16:12
>
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  )))
... ... @@ -69,7 +69,6 @@
69 69  * 8500mAh Battery for long term use
70 70  
71 71  
72 -
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -89,6 +89,7 @@
89 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
76 +
92 92  * Li/SOCI2 un-chargeable battery
93 93  * Capacity: 8500mAh
94 94  * Self Discharge: <1% / Year @ 25°C
... ... @@ -96,10 +96,8 @@
96 96  * Max boost current: 2A, 1 second
97 97  
98 98  
99 -
100 100  == ​1.4  Applications ==
101 101  
102 -
103 103  * Smart Buildings & Home Automation
104 104  * Logistics and Supply Chain Management
105 105  * Smart Metering
... ... @@ -111,20 +111,15 @@
111 111  ​
112 112  
113 113  
97 +== 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  
112 +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 -)))
114 +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,15 @@
151 151  
152 152  === 1.5.4 LED ===
153 153  
154 -
155 155  It will flash:
156 156  
157 -1.  When boot the device in flash mode
128 +1. When boot the device in flash mode
129 +1. Send an uplink packet
158 158  
159 -2.  Send an uplink packet
160 160  
161 161  
162 -
163 163  = 2.  Use N95S31B to communicate with IoT Server =
164 164  
165 -
166 166  == 2.1  How it works ==
167 167  
168 168  
... ... @@ -179,7 +179,7 @@
179 179  
180 180  )))
181 181  
182 -[[image:1657520100595-569.png]]
151 +[[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 -)))
172 +* Your local operator has already distributed a NB-IoT Network there.
173 +* The local NB-IoT network used the band that N95S31B supports.
174 +* 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 -)))
181 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 +* 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,27 +264,23 @@
264 264  
265 265  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
266 266  
267 -
268 268  (((
269 269  (((
270 270  User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
271 -
272 -
273 273  )))
274 274  )))
275 275  
276 276  [[image:1657351312545-300.png]]
277 277  
220 +**Connection:**
278 278  
279 -(% style="color:blue" %)**Connection:**
222 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
280 280  
281 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
224 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
282 282  
283 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
226 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
284 284  
285 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
286 286  
287 -
288 288  In the PC, use below serial tool settings:
289 289  
290 290  * Baud:  (% style="color:green" %)**9600**
... ... @@ -299,9 +299,8 @@
299 299  
300 300  [[image:1657329814315-101.png]]
301 301  
302 -
303 303  (((
304 -(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
244 +(% 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  
251 +(% 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
262 +(% 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
265 +(% 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
303 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
305 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 +* (% 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,102 +413,59 @@
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 -)))
356 +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 -)))
361 + (% 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.**
374 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 +1. By default, the device will send an uplink message every 1 hour.
466 466  
467 467  
468 468  
469 -
470 -)))
471 471  
472 472  === 2.3.1  Payload Analyze ===
473 473  
474 -
475 -==== 2.3.1.1  Before Firmware v1.2 ====
476 -
477 -
478 478  N95S31B uplink payload includes in total 21 bytes
479 479  
480 480  
481 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
482 -|=(% style="width: 50px;" %)**Size(bytes)**|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 65px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 70px;" %)**2**|=(% style="width: 70px;" %)**2**
483 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
484 -(((
385 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
386 +|=(% style="width: 60px;" %)(((
387 +**Size(bytes)**
388 +)))|=(% 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**
389 +|(% 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" %)(((
485 485  Reserve/ Same as NBSN95 CFGMOD=1
486 -)))
487 487  
488 -(((
489 489  No function here.
490 -)))
491 -)))|(% style="width:102px" %)(((
492 -(((
493 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
494 -)))
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
495 495  
496 -(((
497 497  By SHT31
498 -)))
499 -)))|(% style="width:81px" %)(((
500 -(((
501 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
502 -)))
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
503 503  
504 -(((
505 505  By SHT31
506 506  )))
507 -)))
508 508  
509 509  (((
510 -
511 -
512 512  (((
513 513  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
514 514  )))
... ... @@ -517,89 +517,43 @@
517 517  
518 518  [[image:1657354294009-643.png]]
519 519  
412 +(((
413 +The payload is ASCII string, representative same HEX:
414 +)))
520 520  
521 -The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
416 +(((
417 +0x72403155615900640c6c19029200 where:
418 +)))
522 522  
523 -**where:**
420 +* (((
421 +Device ID: 0x724031556159 = 724031556159
422 +)))
423 +* (((
424 +Version: 0x0064=100=1.0.0
425 +)))
524 524  
525 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
427 +* (((
428 +BAT: 0x0c6c = 3180 mV = 3.180V
429 +)))
430 +* (((
431 +Signal: 0x19 = 25
432 +)))
433 +* (((
434 +Distance: 0x0292= 658 mm
435 +)))
436 +* (((
437 +Interrupt: 0x00 = 0
526 526  
527 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
528 528  
529 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
530 530  
531 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
532 -
533 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
534 -
535 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
536 -
537 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
538 -
539 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
540 -
541 -(((
542 542  
543 -
544 -
545 -
546 546  )))
547 547  
548 -==== 2.3.1.2 Since Firmware v1.2 ====
444 +== 2.4  Payload Explanation and Sensor Interface ==
549 549  
550 550  
551 -In this mode, uplink payload includes 91 bytes in total by default.
447 +=== 2.4.1  Device ID ===
552 552  
553 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
554 -
555 -
556 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
557 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:20px" %)**2**|(% style="width:20px" %)**2**|(% style="width:30px" %)**1**|(% style="width:20px" %)**1**|(% style="width:55px" %)**2**|(% style="width:35px" %)**1**|(% style="width:20px" %)**2**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:30px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**2**|(% style="width:35px" %)**4**
558 -|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
559 -
560 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
561 -
562 -
563 -[[image:image-20220908154949-1.png]]
564 -
565 -
566 -The payload is ASCII string, representative same HEX:
567 -
568 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ **
569 -
570 -**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
571 -
572 -**where:**
573 -
574 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
575 -
576 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
577 -
578 -* (% style="color:#037691" %)**BAT:**      (%%)0x0d0f = 3343 mV = 3.343V
579 -
580 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
581 -
582 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
583 -
584 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
585 -
586 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
587 -
588 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
589 -
590 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
591 -
592 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
593 -
594 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
595 -
596 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
597 -
598 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
599 -
600 -=== 2.3.2  Device ID ===
601 -
602 -
603 603  (((
604 604  By default, the Device ID equal to the last 6 bytes of IMEI.
605 605  )))
... ... @@ -606,12 +606,10 @@
606 606  
607 607  (((
608 608  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
609 -
610 -
611 611  )))
612 612  
613 613  (((
614 -(% style="color:blue" %)**Example:**
458 +**Example:**
615 615  )))
616 616  
617 617  (((
... ... @@ -619,123 +619,148 @@
619 619  )))
620 620  
621 621  (((
622 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
623 -
624 -
466 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
625 625  )))
626 626  
627 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
628 628  
629 629  
630 -By default, the Device ID equal to the last 15 bits of IMEI.
471 +=== 2.4.2  Version Info ===
631 631  
632 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
473 +(((
474 +Specify the software version: 0x64=100, means firmware version 1.00.
475 +)))
633 633  
477 +(((
478 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
479 +)))
634 634  
635 -(% style="color:blue" %)**Example:**
636 636  
637 -AT+DEUI=868411056754138
638 638  
483 +=== 2.4.3  Battery Info ===
639 639  
485 +(((
486 +Ex1: 0x0B45 = 2885mV
487 +)))
640 640  
641 -=== 2.3.3  Version Info ===
642 -
643 -
644 644  (((
645 -These bytes include the hardware and software version.
490 +Ex2: 0x0B49 = 2889mV
646 646  )))
647 647  
493 +
494 +
495 +=== 2.4.4  Signal Strength ===
496 +
648 648  (((
649 -Higher byte: Specify hardware version: always 0x00 for N95S31B
498 +NB-IoT Network signal Strength.
650 650  )))
651 651  
652 652  (((
653 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
502 +**Ex1: 0x1d = 29**
654 654  )))
655 655  
656 656  (((
657 -
506 +(% style="color:blue" %)**0**(%%)  -113dBm or less
658 658  )))
659 659  
660 660  (((
661 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
510 +(% style="color:blue" %)**1**(%%)  -111dBm
662 662  )))
663 663  
664 664  (((
665 -
514 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
666 666  )))
667 667  
668 -
669 -=== 2.3.4  Battery Info ===
670 -
671 -
672 672  (((
673 -Ex1: 0x0B45 = 2885mV
518 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
674 674  )))
675 675  
676 676  (((
677 -Ex2: 0x0B49 = 2889mV
522 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
678 678  )))
679 679  
680 680  
681 681  
682 -=== 2.3.5  Signal Strength ===
527 +=== 2.4.5  Distance ===
683 683  
529 +Get the distance. Flat object range 280mm - 7500mm.
684 684  
685 685  (((
686 -NB-IoT Network signal Strength.
532 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
687 687  )))
688 688  
689 689  (((
690 -**Ex1: 0x1d = 29**
536 +(((
537 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
691 691  )))
539 +)))
692 692  
693 693  (((
694 -(% style="color:blue" %)**0**(%%)  -113dBm or less
542 +
695 695  )))
696 696  
697 697  (((
698 -(% style="color:blue" %)**1**(%%)  -111dBm
546 +
699 699  )))
700 700  
549 +=== 2.4.6  Digital Interrupt ===
550 +
701 701  (((
702 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
552 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
703 703  )))
704 704  
705 705  (((
706 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
556 +The command is:
707 707  )))
708 708  
709 709  (((
710 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
560 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
711 711  )))
712 712  
713 713  
564 +(((
565 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
566 +)))
714 714  
715 -=== 2.3.6  Temperature & Humidity ===
716 716  
569 +(((
570 +Example:
571 +)))
717 717  
718 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
573 +(((
574 +0x(00): Normal uplink packet.
575 +)))
719 719  
720 -[[image:image-20220709161741-3.png]]
577 +(((
578 +0x(01): Interrupt Uplink Packet.
579 +)))
721 721  
722 722  
723 -Convert the read byte to decimal and divide it by ten.
724 724  
583 +=== 2.4.7  ​+5V Output ===
725 725  
726 -**Example:**
585 +(((
586 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
587 +)))
727 727  
728 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
729 729  
730 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
590 +(((
591 +The 5V output time can be controlled by AT Command.
592 +)))
731 731  
594 +(((
595 +(% style="color:blue" %)**AT+5VT=1000**
596 +)))
732 732  
598 +(((
599 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
600 +)))
733 733  
734 -== 2.4  Downlink Payload ==
735 735  
736 736  
737 -By default, N95S31B prints the downlink payload to console port.
604 +== 2.5  Downlink Payload ==
738 738  
606 +By default, NDDS75 prints the downlink payload to console port.
607 +
739 739  [[image:image-20220709100028-1.png]]
740 740  
741 741  
... ... @@ -772,7 +772,7 @@
772 772  )))
773 773  
774 774  (((
775 -If payload = 0x04FF, it will reset the N95S31B
644 +If payload = 0x04FF, it will reset the NDDS75
776 776  )))
777 777  
778 778  
... ... @@ -784,76 +784,48 @@
784 784  
785 785  
786 786  
787 -== 2.5  Humidity and Temperature alarm function ==
656 +== 2.6  ​LED Indicator ==
788 788  
789 789  
790 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
659 +The NDDS75 has an internal LED which is to show the status of different state.
791 791  
792 792  
793 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
662 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
663 +* Then the LED will be on for 1 second means device is boot normally.
664 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
665 +* For each uplink probe, LED will be on for 500ms.
794 794  
667 +(((
668 +
669 +)))
795 795  
796 -² When min=0, and max≠0, Alarm higher than max
797 797  
798 -² When min≠0, and max=0, Alarm lower than min
799 799  
800 -² When min≠0 and max≠0, Alarm higher than max or lower than min
673 +== 2.7  ​Firmware Change Log ==
801 801  
802 802  
803 - (% style="color:blue" %)**Example:**
676 +(((
677 +Download URL & Firmware Change log
678 +)))
804 804  
805 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
680 +(((
681 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
682 +)))
806 806  
807 807  
808 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
685 +(((
686 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
687 +)))
809 809  
810 -² When min=0, and max≠0, Alarm higher than max
811 811  
812 -² When min≠0, and max=0, Alarm lower than min
813 813  
814 -² When min≠0 and max≠0, Alarm higher than max or lower than min
815 -
816 -
817 -**~ (% style="color:blue" %)Example:(%%)**
818 -
819 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
820 -
821 -
822 -
823 -== 2.6 Set the number of data to be uploaded and the recording time ==
824 -
825 -
826 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
827 -
828 -* (% style="color:#037691" %)**AT+TR=900**     (%%)~/~/  The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
829 -* (% style="color:#037691" %)**AT+NOUD=8**  (%%)~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
830 -
831 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
832 -
833 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
834 -
835 -
836 -
837 -== 2.7 Read or Clear cached data ==
838 -
839 -
840 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
841 -
842 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
843 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
844 -
845 -[[image:image-20220908163102-2.png]]
846 -
847 -
848 -
849 849  == 2.8  ​Battery Analysis ==
850 850  
851 -
852 852  === 2.8.1  ​Battery Type ===
853 853  
854 854  
855 855  (((
856 -The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
697 +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.
857 857  )))
858 858  
859 859  (((
... ... @@ -876,35 +876,54 @@
876 876  
877 877  === 2.8.2  Power consumption Analyze ===
878 878  
720 +(((
721 +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.
722 +)))
879 879  
724 +
880 880  (((
881 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
726 +Instruction to use as below:
882 882  )))
883 883  
884 884  (((
885 -
730 +(% 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/]]
886 886  )))
887 887  
888 888  
889 -=== 2.8.3  ​Battery Note ===
734 +(((
735 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
736 +)))
890 890  
738 +* (((
739 +Product Model
740 +)))
741 +* (((
742 +Uplink Interval
743 +)))
744 +* (((
745 +Working Mode
746 +)))
891 891  
892 892  (((
893 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
749 +And the Life expectation in difference case will be shown on the right.
894 894  )))
895 895  
752 +[[image:image-20220709110451-3.png]]
896 896  
897 897  
898 -=== 2.8.4  Replace the battery ===
899 899  
756 +=== 2.8.3  ​Battery Note ===
900 900  
901 901  (((
902 -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.
759 +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.
903 903  )))
904 904  
905 905  
763 +
764 +=== 2.8.4  Replace the battery ===
765 +
906 906  (((
907 -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).
767 +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).
908 908  )))
909 909  
910 910  
... ... @@ -911,7 +911,6 @@
911 911  
912 912  = 3. ​ Access NB-IoT Module =
913 913  
914 -
915 915  (((
916 916  Users can directly access the AT command set of the NB-IoT module.
917 917  )))
... ... @@ -918,8 +918,6 @@
918 918  
919 919  (((
920 920  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
921 -
922 -
923 923  )))
924 924  
925 925  [[image:1657333200519-600.png]]
... ... @@ -928,13 +928,11 @@
928 928  
929 929  = 4.  Using the AT Commands =
930 930  
931 -
932 932  == 4.1  Access AT Commands ==
933 933  
790 +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/]]
934 934  
935 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
936 936  
937 -
938 938  AT+<CMD>?  : Help on <CMD>
939 939  
940 940  AT+<CMD>         : Run <CMD>
... ... @@ -974,24 +974,7 @@
974 974  
975 975  AT+SERVADDR  : Server Address
976 976  
977 -AT+TR      : Get or Set record time
978 978  
979 -AT+APN     : Get or set the APN
980 -
981 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
982 -
983 -AT+DNSCFG  : Get or Set DNS Server
984 -
985 -AT+GETSENSORVALUE   : Returns the current sensor measurement
986 -
987 -AT+NOUD      : Get or Set the number of data to be uploaded
988 -
989 -AT+CDP     : Read or Clear cached data
990 -
991 -AT+SHTEMP: Get or Set alarm of temp
992 -
993 -AT+SHHUM: Get or Set alarm of moisture
994 -
995 995  (% style="color:#037691" %)**COAP Management**      
996 996  
997 997  AT+URI            : Resource parameters
... ... @@ -1025,7 +1025,6 @@
1025 1025  
1026 1026  = ​5.  FAQ =
1027 1027  
1028 -
1029 1029  == 5.1 ​ How to Upgrade Firmware ==
1030 1030  
1031 1031  
... ... @@ -1038,18 +1038,13 @@
1038 1038  )))
1039 1039  
1040 1040  (((
1041 -
1042 -
1043 -(((
1044 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
878 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
1045 1045  )))
1046 -)))
1047 1047  
1048 1048  
1049 1049  
1050 1050  = 6.  Trouble Shooting =
1051 1051  
1052 -
1053 1053  == 6.1  ​Connection problem when uploading firmware ==
1054 1054  
1055 1055  
... ... @@ -1065,7 +1065,6 @@
1065 1065  
1066 1066  == 6.2  AT Command input doesn't work ==
1067 1067  
1068 -
1069 1069  (((
1070 1070  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
1071 1071  
... ... @@ -1076,7 +1076,7 @@
1076 1076  = 7. ​ Order Info =
1077 1077  
1078 1078  
1079 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
910 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1080 1080  
1081 1081  
1082 1082  (% class="wikigeneratedid" %)
... ... @@ -1091,7 +1091,7 @@
1091 1091  
1092 1092  (% style="color:#037691" %)**Package Includes**:
1093 1093  
1094 -* N95S31B NB-IoT Temperature and Humidity Sensor
925 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1095 1095  * External antenna x 1
1096 1096  )))
1097 1097  
... ... @@ -1100,10 +1100,11 @@
1100 1100  
1101 1101  (% style="color:#037691" %)**Dimension and weight**:
1102 1102  
934 +
1103 1103  * Device Size: 13.0 x 5 x 4.5 cm
1104 1104  * Device Weight: 150g
1105 -* Package Size / pcs : 14.0 x 8x 5 cm
1106 -* Weight / pcs : 180g
937 +* Package Size / pcs : 15 x 12x 5.5 cm
938 +* Weight / pcs : 220g
1107 1107  )))
1108 1108  
1109 1109  (((
... ... @@ -1115,6 +1115,5 @@
1115 1115  
1116 1116  = 9.  Support =
1117 1117  
1118 -
1119 1119  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
1120 1120  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 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