Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 129.36 >
edited by Xiaoling
on 2023/04/03 17:01
To version < 115.5 >
edited by Xiaoling
on 2022/07/09 17:18
>
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  
... ... @@ -22,29 +22,16 @@
22 22  (((
23 23  
24 24  
25 -(((
26 26  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*.
27 -)))
28 28  
29 -(((
30 30  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.
31 -)))
32 32  
33 -(((
34 34  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 -)))
36 36  
37 -(((
38 38  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).
39 -)))
40 40  
41 -(((
42 -
43 -)))
44 44  
45 -(((
46 46  ~* make sure you have NB-IoT coverage locally.
47 -)))
48 48  
49 49  
50 50  )))
... ... @@ -55,7 +55,6 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
58 -
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 60  * Monitor Temperature & Humidity via SHT31
61 61  * AT Commands to change parameters
... ... @@ -69,6 +69,7 @@
69 69  
70 70  
71 71  
57 +
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -79,15 +79,16 @@
79 79  
80 80  (% style="color:#037691" %)**NB-IoT Spec:**
81 81  
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
68 +* - B1 @H-FDD: 2100MHz
69 +* - B3 @H-FDD: 1800MHz
70 +* - B8 @H-FDD: 900MHz
71 +* - B5 @H-FDD: 850MHz
72 +* - B20 @H-FDD: 800MHz
73 +* - B28 @H-FDD: 700MHz
88 88  
89 89  (% style="color:#037691" %)**Battery:**
90 90  
77 +
91 91  * Li/SOCI2 un-chargeable battery
92 92  * Capacity: 8500mAh
93 93  * Self Discharge: <1% / Year @ 25°C
... ... @@ -96,9 +96,9 @@
96 96  
97 97  
98 98  
86 +
99 99  == ​1.4  Applications ==
100 100  
101 -
102 102  * Smart Buildings & Home Automation
103 103  * Logistics and Supply Chain Management
104 104  * Smart Metering
... ... @@ -110,49 +110,41 @@
110 110  ​
111 111  
112 112  
113 -== 1.5  Pin Definitions & Switch ==
100 +== 1.5  Pin Definitions ==
114 114  
115 -
116 116  N95S31B use the mother board from NBSN95 which as below.
117 117  
118 -
119 119  [[image:image-20220709144723-1.png]]
120 120  
121 121  
122 122  === 1.5.1 Jumper JP2 ===
123 123  
124 -
125 125  Power on Device when put this jumper.
126 126  
127 127  
112 +
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
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.
130 130  
131 -(((
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.
133 -)))
117 +2) Flash: work mode, device starts to work and send out console output for further debug
134 134  
135 -(((
136 -**2) Flash:**  work mode, device starts to work and send out console output for further debug
137 -)))
138 138  
139 139  
140 140  === 1.5.3 Reset Button ===
141 141  
142 -
143 143  Press to reboot the device.
144 144  
145 145  
126 +
146 146  === 1.5.4 LED ===
147 147  
148 -
149 149  It will flash:
150 150  
151 -1.  When boot the device in flash mode
131 +1. When boot the device in flash mode
132 +1. Send an uplink packet
152 152  
153 -2.  Send an uplink packet
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:1657520100595-569.png]]
153 +[[image:1657350248151-650.png]]
175 175  
176 176  (((
177 177  
... ... @@ -180,6 +180,7 @@
180 180  
181 181  == 2.2 ​ Configure the N95S31B ==
182 182  
162 +
183 183  === 2.2.1  Power On N95S31B ===
184 184  
185 185  
... ... @@ -186,48 +186,26 @@
186 186  [[image:image-20220709150546-2.png]]
187 187  
188 188  
189 -=== 2.2.2 Test Requirement ===
169 +=== 2.2.1 Test Requirement ===
190 190  
191 191  
192 -(((
193 193  To use N95S31B in your city, make sure meet below requirements:
194 -)))
195 195  
196 -* (((
197 -Your local operator has already distributed a NB-IoT Network there.
198 -)))
199 -* (((
200 -The local NB-IoT network used the band that N95S31B supports.
201 -)))
202 -* (((
203 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
204 -)))
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.
205 205  
206 -(((
207 207  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
208 -)))
209 209  
210 -(((
211 211  N95S31B supports different communication protocol such as :
212 -)))
213 213  
214 214  (((
215 -* (((
216 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
217 -)))
218 -* (((
219 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
220 -)))
221 -* (((
222 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
223 -)))
224 -* (((
225 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
226 -)))
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(%%))
227 227  
228 -(((
229 229  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.
230 -)))
231 231  
232 232  
233 233  )))
... ... @@ -235,9 +235,9 @@
235 235  [[image:1657350625843-586.png]]
236 236  
237 237  
196 +
238 238  === 2.2.3  Insert SIM card ===
239 239  
240 -
241 241  (((
242 242  Insert the NB-IoT Card get from your provider.
243 243  )))
... ... @@ -250,29 +250,26 @@
250 250  [[image:1657351240556-536.png]]
251 251  
252 252  
211 +
253 253  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
254 254  
255 -
256 256  (((
257 257  (((
258 258  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 -
261 261  )))
262 262  )))
263 263  
264 264  [[image:1657351312545-300.png]]
265 265  
222 +**Connection:**
266 266  
267 -(% style="color:blue" %)**Connection:**
224 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
268 268  
269 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
226 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
270 270  
271 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
228 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
272 272  
273 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
274 274  
275 -
276 276  In the PC, use below serial tool settings:
277 277  
278 278  * Baud:  (% style="color:green" %)**9600**
... ... @@ -287,18 +287,17 @@
287 287  
288 288  [[image:1657329814315-101.png]]
289 289  
290 -
291 291  (((
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]]**
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/]]
293 293  )))
294 294  
295 295  
250 +
296 296  === 2.2.5  Use CoAP protocol to uplink data ===
297 297  
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/]]
298 298  
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/]]**
300 300  
301 -
302 302  (((
303 303  **Use below commands:**
304 304  )))
... ... @@ -307,10 +307,10 @@
307 307  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
308 308  )))
309 309  * (((
310 -(% 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
311 311  )))
312 312  * (((
313 -(% 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
314 314  )))
315 315  
316 316  (((
... ... @@ -329,6 +329,7 @@
329 329  [[image:1657352185396-303.png]]
330 330  
331 331  
286 +
332 332  === 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
333 333  
334 334  
... ... @@ -342,18 +342,18 @@
342 342  [[image:1657352403317-397.png]]
343 343  
344 344  
300 +
345 345  === 2.2.7  Use MQTT protocol to uplink data ===
346 346  
347 -
348 348  N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
349 349  
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
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
357 357  
358 358  [[image:1657352634421-276.png]]
359 359  
... ... @@ -360,7 +360,6 @@
360 360  
361 361  [[image:1657352645687-385.png]]
362 362  
363 -
364 364  (((
365 365  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.
366 366  )))
... ... @@ -371,9 +371,9 @@
371 371  )))
372 372  
373 373  
328 +
374 374  === 2.2.8  Use TCP protocol to uplink data ===
375 375  
376 -
377 377  This feature is supported since firmware version v110
378 378  
379 379  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
... ... @@ -385,9 +385,9 @@
385 385  [[image:1657352914475-252.png]]
386 386  
387 387  
342 +
388 388  === 2.2.9  Change Update Interval ===
389 389  
390 -
391 391  User can use below command to change the (% style="color:green" %)**uplink interval**.
392 392  
393 393  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
... ... @@ -396,99 +396,58 @@
396 396  
397 397  )))
398 398  
399 -(((
400 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
401 -)))
402 402  
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 -)))
406 406  
407 -
408 408  == 2.3  Uplink Payload ==
409 409  
410 410  
411 -(((
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.
413 -)))
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.
414 414  
415 415  
416 -(((
417 417  For example:
418 -)))
419 419  
420 -(((
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.
422 -)))
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.
423 423  
424 424  
425 -(((
426 426  The uplink payloads are composed in  ASCII String. For example:
427 -)))
428 428  
429 -(((
430 430  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
431 -)))
432 432  
433 -(((
434 434  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
435 -)))
436 436  
437 437  
438 -(((
439 439  (% style="color:red" %)**NOTE:**
440 -)))
441 441  
442 442  (% style="color:red" %)
443 -1. (((
444 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
445 -)))
446 -1. (((
447 -**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.
448 448  
449 449  
450 -
451 -)))
452 452  
453 453  === 2.3.1  Payload Analyze ===
454 454  
455 -==== 2.3.1.1  Before Firmware v1.2 ====
456 -
457 -
458 458  N95S31B uplink payload includes in total 21 bytes
459 459  
460 460  
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" %)(((
464 -(((
386 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
387 +|=(% style="width: 60px;" %)(((
388 +**Size(bytes)**
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" %)(((
465 465  Reserve/ Same as NBSN95 CFGMOD=1
466 -)))
467 467  
468 -(((
469 469  No function here.
470 -)))
471 -)))|(% style="width:102px" %)(((
472 -(((
473 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
474 -)))
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
475 475  
476 -(((
477 477  By SHT31
478 -)))
479 -)))|(% style="width:81px" %)(((
480 -(((
481 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
482 -)))
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
483 483  
484 -(((
485 485  By SHT31
486 486  )))
487 -)))
488 488  
489 489  (((
490 -
491 -
492 492  (((
493 493  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
494 494  )))
... ... @@ -498,89 +498,29 @@
498 498  [[image:1657354294009-643.png]]
499 499  
500 500  
501 -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:
502 502  
503 -**where:**
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
504 504  
505 -* (% 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
506 506  
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 -
521 521  (((
522 522  
428 +)))
523 523  
430 +(((
524 524  
525 525  )))
526 526  
527 -==== 2.3.1.2 Since Firmware v1.2 ====
528 528  
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 -
581 581  === 2.3.2  Device ID ===
582 582  
583 -
584 584  (((
585 585  By default, the Device ID equal to the last 6 bytes of IMEI.
586 586  )))
... ... @@ -587,12 +587,10 @@
587 587  
588 588  (((
589 589  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
590 -
591 -
592 592  )))
593 593  
594 594  (((
595 -(% style="color:blue" %)**Example:**
446 +**Example:**
596 596  )))
597 597  
598 598  (((
... ... @@ -600,54 +600,30 @@
600 600  )))
601 601  
602 602  (((
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 -
454 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
606 606  )))
607 607  
608 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
609 609  
610 610  
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 -
621 621  === 2.3.3  Version Info ===
622 622  
623 623  
624 -(((
625 625  These bytes include the hardware and software version.
626 -)))
627 627  
628 -(((
629 629  Higher byte: Specify hardware version: always 0x00 for N95S31B
630 -)))
631 631  
632 -(((
633 633  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
634 -)))
635 635  
636 -(((
637 -
638 -)))
639 639  
640 -(((
641 641  For example: 0x00 6E: this device is N95S31B with firmware version 110.
642 -)))
643 643  
644 644  (((
645 645  
646 646  )))
647 647  
475 +
648 648  === 2.3.4  Battery Info ===
649 649  
650 -
651 651  (((
652 652  Ex1: 0x0B45 = 2885mV
653 653  )))
... ... @@ -657,9 +657,9 @@
657 657  )))
658 658  
659 659  
487 +
660 660  === 2.3.5  Signal Strength ===
661 661  
662 -
663 663  (((
664 664  NB-IoT Network signal Strength.
665 665  )))
... ... @@ -689,9 +689,9 @@
689 689  )))
690 690  
691 691  
519 +
692 692  === 2.3.6  Temperature & Humidity ===
693 693  
694 -
695 695  The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
696 696  
697 697  [[image:image-20220709161741-3.png]]
... ... @@ -707,10 +707,10 @@
707 707  Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
708 708  
709 709  
710 -== 2.4  Downlink Payload ==
711 711  
538 +== 2.5  Downlink Payload ==
712 712  
713 -By default, N95S31B prints the downlink payload to console port.
540 +By default, NDDS75 prints the downlink payload to console port.
714 714  
715 715  [[image:image-20220709100028-1.png]]
716 716  
... ... @@ -748,7 +748,7 @@
748 748  )))
749 749  
750 750  (((
751 -If payload = 0x04FF, it will reset the N95S31B
578 +If payload = 0x04FF, it will reset the NDDS75
752 752  )))
753 753  
754 754  
... ... @@ -759,76 +759,90 @@
759 759  )))
760 760  
761 761  
762 -== 2.5  Humidity and Temperature alarm function ==
763 763  
590 +== 2.5  ​Battery Analysis ==
764 764  
765 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
592 +=== 2.5.1  ​Battery Type ===
766 766  
767 767  
768 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
595 +(((
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.
597 +)))
769 769  
599 +(((
600 +The battery is designed to last for several years depends on the actually use environment and update interval. 
601 +)))
770 770  
771 -² When min=0, and max≠0, Alarm higher than max
603 +(((
604 +The battery related documents as below:
605 +)))
772 772  
773 -² When min≠0, and max=0, Alarm lower than min
607 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
608 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
609 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
774 774  
775 -² When min≠0 and max≠0, Alarm higher than max or lower than min
611 +(((
612 +[[image:image-20220709101450-2.png]]
613 +)))
776 776  
777 777  
778 - (% style="color:blue" %)**Example:**
779 779  
780 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
617 +=== 2.8.2  Power consumption Analyze ===
781 781  
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 +)))
782 782  
783 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
784 784  
785 -² When min=0, and max≠0, Alarm higher than max
624 +(((
625 +Instruction to use as below:
626 +)))
786 786  
787 -² When min≠0, and max=0, Alarm lower than min
628 +(((
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/]]
630 +)))
788 788  
789 -² When min≠0 and max≠0, Alarm higher than max or lower than min
790 790  
633 +(((
634 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
635 +)))
791 791  
792 -**~ (% style="color:blue" %)Example:(%%)**
637 +* (((
638 +Product Model
639 +)))
640 +* (((
641 +Uplink Interval
642 +)))
643 +* (((
644 +Working Mode
645 +)))
793 793  
794 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
647 +(((
648 +And the Life expectation in difference case will be shown on the right.
649 +)))
795 795  
651 +[[image:image-20220709110451-3.png]]
796 796  
797 -== 2.6 Set the number of data to be uploaded and the recording time ==
798 798  
799 799  
800 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
655 +=== 2.8.3  ​Battery Note ===
801 801  
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.
657 +(((
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.
659 +)))
804 804  
805 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
806 806  
807 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
808 808  
663 +=== 2.8.4  Replace the battery ===
809 809  
810 -== 2.7 Read or Clear cached data ==
665 +(((
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).
667 +)))
811 811  
812 812  
813 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
814 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 -
829 829  = 3. ​ Access NB-IoT Module =
830 830  
831 -
832 832  (((
833 833  Users can directly access the AT command set of the NB-IoT module.
834 834  )))
... ... @@ -835,21 +835,19 @@
835 835  
836 836  (((
837 837  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 -
840 840  )))
841 841  
842 842  [[image:1657333200519-600.png]]
843 843  
844 844  
684 +
845 845  = 4.  Using the AT Commands =
846 846  
847 847  == 4.1  Access AT Commands ==
848 848  
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/]]
849 849  
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]]
851 851  
852 -
853 853  AT+<CMD>?  : Help on <CMD>
854 854  
855 855  AT+<CMD>         : Run <CMD>
... ... @@ -889,24 +889,7 @@
889 889  
890 890  AT+SERVADDR  : Server Address
891 891  
892 -AT+TR      : Get or Set record time
893 893  
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 -
910 910  (% style="color:#037691" %)**COAP Management**      
911 911  
912 912  AT+URI            : Resource parameters
... ... @@ -937,6 +937,7 @@
937 937  AT+PWORD  : Serial Access Password
938 938  
939 939  
762 +
940 940  = ​5.  FAQ =
941 941  
942 942  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -951,14 +951,11 @@
951 951  )))
952 952  
953 953  (((
954 -
955 -
956 -(((
957 -(% 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.
958 958  )))
959 -)))
960 960  
961 961  
781 +
962 962  = 6.  Trouble Shooting =
963 963  
964 964  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -973,9 +973,9 @@
973 973  
974 974  )))
975 975  
796 +
976 976  == 6.2  AT Command input doesn't work ==
977 977  
978 -
979 979  (((
980 980  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.
981 981  
... ... @@ -982,12 +982,18 @@
982 982  
983 983  )))
984 984  
805 +
985 985  = 7. ​ Order Info =
986 986  
987 987  
988 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
809 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
989 989  
990 990  
812 +(% class="wikigeneratedid" %)
813 +(((
814 +
815 +)))
816 +
991 991  = 8.  Packing Info =
992 992  
993 993  (((
... ... @@ -995,7 +995,7 @@
995 995  
996 996  (% style="color:#037691" %)**Package Includes**:
997 997  
998 -* N95S31B NB-IoT Temperature and Humidity Sensor
824 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
999 999  * External antenna x 1
1000 1000  )))
1001 1001  
... ... @@ -1004,23 +1004,21 @@
1004 1004  
1005 1005  (% style="color:#037691" %)**Dimension and weight**:
1006 1006  
833 +
1007 1007  * Device Size: 13.0 x 5 x 4.5 cm
1008 1008  * Device Weight: 150g
1009 -* Package Size / pcs : 14.0 x 8x 5 cm
1010 -* Weight / pcs : 180g
836 +* Package Size / pcs : 15 x 12x 5.5 cm
837 +* Weight / pcs : 220g
1011 1011  )))
1012 1012  
1013 1013  (((
1014 1014  
1015 1015  
843 +
1016 1016  
1017 1017  )))
1018 1018  
1019 1019  = 9.  Support =
1020 1020  
1021 -
1022 1022  * 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.
1023 1023  * 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,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