Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 102.2 >
edited by Xiaoling
on 2022/07/09 15:06
To version < 118.6 >
edited by Xiaoling
on 2022/07/12 17:31
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -9,6 +9,7 @@
9 9  
10 10  **Table of Contents:**
11 11  
12 +{{toc/}}
12 12  
13 13  
14 14  
... ... @@ -21,16 +21,29 @@
21 21  (((
22 22  
23 23  
25 +(((
24 24  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 +)))
25 25  
29 +(((
26 26  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 +)))
27 27  
33 +(((
28 28  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 +)))
29 29  
37 +(((
30 30  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 +)))
31 31  
41 +(((
42 +
43 +)))
32 32  
45 +(((
33 33  ~* make sure you have NB-IoT coverage locally.
47 +)))
34 34  
35 35  
36 36  )))
... ... @@ -41,7 +41,6 @@
41 41  
42 42  == 1.2 ​ Features ==
43 43  
44 -
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 46  * Monitor Temperature & Humidity via SHT31
47 47  * AT Commands to change parameters
... ... @@ -74,7 +74,6 @@
74 74  
75 75  (% style="color:#037691" %)**Battery:**
76 76  
77 -
78 78  * Li/SOCI2 un-chargeable battery
79 79  * Capacity: 8500mAh
80 80  * Self Discharge: <1% / Year @ 25°C
... ... @@ -96,7 +96,7 @@
96 96  ​
97 97  
98 98  
99 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
100 100  
101 101  N95S31B use the mother board from NBSN95 which as below.
102 102  
... ... @@ -111,9 +111,13 @@
111 111  
112 112  === 1.5.2 BOOT MODE / SW1 ===
113 113  
126 +(((
114 114  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.
128 +)))
115 115  
130 +(((
116 116  2) Flash: work mode, device starts to work and send out console output for further debug
132 +)))
117 117  
118 118  
119 119  
... ... @@ -131,8 +131,6 @@
131 131  1. Send an uplink packet
132 132  
133 133  
134 -
135 -
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
138 138  == 2.1  How it works ==
... ... @@ -151,7 +151,7 @@
151 151  
152 152  )))
153 153  
154 -[[image:1657350248151-650.png]]
168 +[[image:1657520100595-569.png]]
155 155  
156 156  (((
157 157  
... ... @@ -166,27 +166,59 @@
166 166  
167 167  [[image:image-20220709150546-2.png]]
168 168  
183 +
169 169  === 2.2.1 Test Requirement ===
170 170  
186 +
171 171  (((
172 -To use NDDS75 in your city, make sure meet below requirements:
188 +To use N95S31B in your city, make sure meet below requirements:
173 173  )))
174 174  
175 -* Your local operator has already distributed a NB-IoT Network there.
176 -* The local NB-IoT network used the band that NSE01 supports.
177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
191 +* (((
192 +Your local operator has already distributed a NB-IoT Network there.
193 +)))
194 +* (((
195 +The local NB-IoT network used the band that N95S31B supports.
196 +)))
197 +* (((
198 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +)))
178 178  
179 179  (((
180 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
202 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181 181  )))
182 182  
205 +(((
206 +N95S31B supports different communication protocol such as :
207 +)))
183 183  
184 -[[image:1657328756309-230.png]]
209 +(((
210 +* (((
211 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
212 +)))
213 +* (((
214 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
215 +)))
216 +* (((
217 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
218 +)))
219 +* (((
220 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
221 +)))
185 185  
223 +(((
224 +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.
225 +)))
186 186  
227 +
228 +)))
187 187  
188 -=== 2.2.2 Insert SIM card ===
230 +[[image:1657350625843-586.png]]
189 189  
232 +
233 +
234 +=== 2.2.3  Insert SIM card ===
235 +
190 190  (((
191 191  Insert the NB-IoT Card get from your provider.
192 192  )))
... ... @@ -196,19 +196,19 @@
196 196  )))
197 197  
198 198  
199 -[[image:1657328884227-504.png]]
245 +[[image:1657351240556-536.png]]
200 200  
201 201  
202 202  
203 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
249 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
204 204  
205 205  (((
206 206  (((
207 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
253 +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.
208 208  )))
209 209  )))
210 210  
211 -[[image:image-20220709092052-2.png]]
257 +[[image:1657351312545-300.png]]
212 212  
213 213  **Connection:**
214 214  
... ... @@ -228,18 +228,18 @@
228 228  * Flow Control: (% style="color:green" %)**None**
229 229  
230 230  (((
231 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
277 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
232 232  )))
233 233  
234 234  [[image:1657329814315-101.png]]
235 235  
236 236  (((
237 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
283 +(% 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/]]
238 238  )))
239 239  
240 240  
241 241  
242 -=== 2.2.4 Use CoAP protocol to uplink data ===
288 +=== 2.2.5  Use CoAP protocol to uplink data ===
243 243  
244 244  (% 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/]]
245 245  
... ... @@ -259,10 +259,12 @@
259 259  )))
260 260  
261 261  (((
308 +
309 +
262 262  For parameter description, please refer to AT command set
263 263  )))
264 264  
265 -[[image:1657330452568-615.png]]
313 +[[image:1657352146020-183.png]]
266 266  
267 267  
268 268  (((
... ... @@ -269,11 +269,11 @@
269 269  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
270 270  )))
271 271  
272 -[[image:1657330472797-498.png]]
320 +[[image:1657352185396-303.png]]
273 273  
274 274  
275 275  
276 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
324 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
277 277  
278 278  
279 279  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -280,15 +280,16 @@
280 280  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
281 281  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
282 282  
283 -[[image:1657330501006-241.png]]
331 +[[image:1657352391268-297.png]]
284 284  
285 285  
286 -[[image:1657330533775-472.png]]
334 +[[image:1657352403317-397.png]]
287 287  
288 288  
289 289  
290 -=== 2.2.6 Use MQTT protocol to uplink data ===
338 +=== 2.2.7  Use MQTT protocol to uplink data ===
291 291  
340 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
292 292  
293 293  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
294 294  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -295,35 +295,40 @@
295 295  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
296 296  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
297 297  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
298 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
299 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
347 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
348 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
300 300  
301 -[[image:1657249978444-674.png]]
350 +[[image:1657352634421-276.png]]
302 302  
303 303  
304 -[[image:1657330723006-866.png]]
353 +[[image:1657352645687-385.png]]
305 305  
355 +(((
356 +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.
357 +)))
306 306  
359 +
307 307  (((
308 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
361 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
309 309  )))
310 310  
311 311  
312 312  
313 -=== 2.2.7 Use TCP protocol to uplink data ===
366 +=== 2.2.8  Use TCP protocol to uplink data ===
314 314  
368 +This feature is supported since firmware version v110
315 315  
316 316  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
317 317  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
318 318  
319 -[[image:image-20220709093918-1.png]]
373 +[[image:1657352898400-901.png]]
320 320  
321 321  
322 -[[image:image-20220709093918-2.png]]
376 +[[image:1657352914475-252.png]]
323 323  
324 324  
325 325  
326 -=== 2.2.8 Change Update Interval ===
380 +=== 2.2.9  Change Update Interval ===
327 327  
328 328  User can use below command to change the (% style="color:green" %)**uplink interval**.
329 329  
... ... @@ -330,59 +330,51 @@
330 330  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
331 331  
332 332  (((
333 -(% style="color:red" %)**NOTE:**
387 +
334 334  )))
335 335  
336 -(((
337 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
338 -)))
339 339  
340 340  
341 -
342 342  == 2.3  Uplink Payload ==
343 343  
344 -In this mode, uplink payload includes in total 14 bytes
345 345  
395 +(((
396 +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.
397 +)))
346 346  
347 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
348 -|=(% style="width: 60px;" %)(((
349 -**Size(bytes)**
350 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
351 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
352 352  
353 353  (((
354 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
401 +For example:
355 355  )))
356 356  
404 +(((
405 + (% 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.
406 +)))
357 357  
358 -[[image:1657331036973-987.png]]
359 359  
360 360  (((
361 -The payload is ASCII string, representative same HEX:
410 +The uplink payloads are composed in  ASCII String. For example:
362 362  )))
363 363  
364 364  (((
365 -0x72403155615900640c6c19029200 where:
414 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
366 366  )))
367 367  
368 -* (((
369 -Device ID: 0x724031556159 = 724031556159
417 +(((
418 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
370 370  )))
371 -* (((
372 -Version: 0x0064=100=1.0.0
420 +
421 +
422 +(((
423 +(% style="color:red" %)**NOTE:**
373 373  )))
374 374  
375 -* (((
376 -BAT: 0x0c6c = 3180 mV = 3.180V
426 +(% style="color:red" %)
427 +1. (((
428 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
377 377  )))
378 -* (((
379 -Signal: 0x19 = 25
380 -)))
381 -* (((
382 -Distance: 0x0292= 658 mm
383 -)))
384 -* (((
385 -Interrupt: 0x00 = 0
430 +1. (((
431 +By default, the device will send an uplink message every 1 hour.
386 386  
387 387  
388 388  
... ... @@ -389,105 +389,108 @@
389 389  
390 390  )))
391 391  
392 -== 2.4  Payload Explanation and Sensor Interface ==
438 +=== 2.3.1  Payload Analyze ===
393 393  
440 +N95S31B uplink payload includes in total 21 bytes
394 394  
395 -=== 2.4.1  Device ID ===
396 396  
443 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
444 +|=(% style="width: 60px;" %)(((
445 +**Size(bytes)**
446 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
447 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
397 397  (((
398 -By default, the Device ID equal to the last 6 bytes of IMEI.
449 +Reserve/ Same as NBSN95 CFGMOD=1
399 399  )))
400 400  
401 401  (((
402 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
453 +No function here.
403 403  )))
404 -
455 +)))|(% style="width:77px" %)(((
405 405  (((
406 -**Example:**
457 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
407 407  )))
408 408  
409 409  (((
410 -AT+DEUI=A84041F15612
461 +By SHT31
411 411  )))
412 -
463 +)))|(% style="width:80px" %)(((
413 413  (((
414 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
465 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
415 415  )))
416 416  
417 -
418 -
419 -=== 2.4.2  Version Info ===
420 -
421 421  (((
422 -Specify the software version: 0x64=100, means firmware version 1.00.
469 +By SHT31
423 423  )))
471 +)))
424 424  
425 425  (((
426 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
474 +(((
475 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
427 427  )))
477 +)))
428 428  
429 429  
480 +[[image:1657354294009-643.png]]
430 430  
431 -=== 2.4.3  Battery Info ===
432 432  
433 -(((
434 -Ex1: 0x0B45 = 2885mV
435 -)))
483 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
436 436  
437 -(((
438 -Ex2: 0x0B49 = 2889mV
439 -)))
485 +* Device ID: 0x724031607457 = 724031607457
486 +* Version: 0x006e=110=1.1.0
440 440  
488 +* BAT: 0x0ccd = 3277 mV = 3.277V
489 +* Signal: 0x1b = 27
490 +* Model: 0x01 = 1
491 +* 0x00dc000ccc= reserve, ignore in N95S31B
492 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
493 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
441 441  
442 -
443 -=== 2.4.4  Signal Strength ===
444 -
445 445  (((
446 -NB-IoT Network signal Strength.
496 +
447 447  )))
448 448  
449 449  (((
450 -**Ex1: 0x1d = 29**
500 +
451 451  )))
452 452  
503 +
504 +=== 2.3.2  Device ID ===
505 +
453 453  (((
454 -(% style="color:blue" %)**0**(%%)  -113dBm or less
507 +By default, the Device ID equal to the last 6 bytes of IMEI.
455 455  )))
456 456  
457 457  (((
458 -(% style="color:blue" %)**1**(%%)  -111dBm
511 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459 459  )))
460 460  
461 461  (((
462 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 +**Example:**
463 463  )))
464 464  
465 465  (((
466 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 +AT+DEUI=A84041F15612
467 467  )))
468 468  
469 469  (((
470 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
523 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
471 471  )))
472 472  
473 473  
474 474  
475 -=== 2.4.5  Distance ===
528 +=== 2.3.3  Version Info ===
476 476  
477 -Get the distance. Flat object range 280mm - 7500mm.
478 -
479 479  (((
480 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
531 +These bytes include the hardware and software version.
481 481  )))
482 482  
483 483  (((
484 -(((
485 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
535 +Higher byte: Specify hardware version: always 0x00 for N95S31B
486 486  )))
487 -)))
488 488  
489 489  (((
490 -
539 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
491 491  )))
492 492  
493 493  (((
... ... @@ -494,65 +494,81 @@
494 494  
495 495  )))
496 496  
497 -=== 2.4.6  Digital Interrupt ===
498 -
499 499  (((
500 -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.
547 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
501 501  )))
502 502  
503 503  (((
504 -The command is:
551 +
505 505  )))
506 506  
554 +
555 +=== 2.3.4  Battery Info ===
556 +
507 507  (((
508 -(% 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]])**.**
558 +Ex1: 0x0B45 = 2885mV
509 509  )))
510 510  
511 -
512 512  (((
513 -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.
562 +Ex2: 0x0B49 = 2889mV
514 514  )))
515 515  
516 516  
566 +
567 +=== 2.3.5  Signal Strength ===
568 +
517 517  (((
518 -Example:
570 +NB-IoT Network signal Strength.
519 519  )))
520 520  
521 521  (((
522 -0x(00): Normal uplink packet.
574 +**Ex1: 0x1d = 29**
523 523  )))
524 524  
525 525  (((
526 -0x(01): Interrupt Uplink Packet.
578 +(% style="color:blue" %)**0**(%%)  -113dBm or less
527 527  )))
528 528  
529 -
530 -
531 -=== 2.4.7  ​+5V Output ===
532 -
533 533  (((
534 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
582 +(% style="color:blue" %)**1**(%%)  -111dBm
535 535  )))
536 536  
537 -
538 538  (((
539 -The 5V output time can be controlled by AT Command.
586 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
540 540  )))
541 541  
542 542  (((
543 -(% style="color:blue" %)**AT+5VT=1000**
590 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
544 544  )))
545 545  
546 546  (((
547 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
594 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
548 548  )))
549 549  
550 550  
551 551  
552 -== 2.5  Downlink Payload ==
599 +=== 2.3.6  Temperature & Humidity ===
553 553  
554 -By default, NDDS75 prints the downlink payload to console port.
601 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
555 555  
603 +[[image:image-20220709161741-3.png]]
604 +
605 +
606 +Convert the read byte to decimal and divide it by ten.
607 +
608 +
609 +**Example:**
610 +
611 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
612 +
613 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
614 +
615 +
616 +
617 +== 2.4  Downlink Payload ==
618 +
619 +By default, N95S31B prints the downlink payload to console port.
620 +
556 556  [[image:image-20220709100028-1.png]]
557 557  
558 558  
... ... @@ -589,7 +589,7 @@
589 589  )))
590 590  
591 591  (((
592 -If payload = 0x04FF, it will reset the NDDS75
657 +If payload = 0x04FF, it will reset the N95S31B
593 593  )))
594 594  
595 595  
... ... @@ -601,51 +601,16 @@
601 601  
602 602  
603 603  
604 -== 2.6  ​LED Indicator ==
669 +== 2.5  ​Battery Analysis ==
605 605  
671 +=== 2.5.1  ​Battery Type ===
606 606  
607 -The NDDS75 has an internal LED which is to show the status of different state.
608 608  
609 -
610 -* 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)
611 -* Then the LED will be on for 1 second means device is boot normally.
612 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
613 -* For each uplink probe, LED will be on for 500ms.
614 -
615 615  (((
616 -
675 +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.
617 617  )))
618 618  
619 -
620 -
621 -== 2.7  ​Firmware Change Log ==
622 -
623 -
624 624  (((
625 -Download URL & Firmware Change log
626 -)))
627 -
628 -(((
629 -[[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/]]
630 -)))
631 -
632 -
633 -(((
634 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
635 -)))
636 -
637 -
638 -
639 -== 2.8  ​Battery Analysis ==
640 -
641 -=== 2.8.1  ​Battery Type ===
642 -
643 -
644 -(((
645 -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.
646 -)))
647 -
648 -(((
649 649  The battery is designed to last for several years depends on the actually use environment and update interval. 
650 650  )))
651 651  
... ... @@ -663,56 +663,35 @@
663 663  
664 664  
665 665  
666 -=== 2.8.2  Power consumption Analyze ===
696 +=== 2.5.2  Power consumption Analyze ===
667 667  
668 668  (((
669 -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.
699 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
670 670  )))
671 671  
672 -
673 673  (((
674 -Instruction to use as below:
703 +
675 675  )))
676 676  
677 -(((
678 -(% 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/]]
679 -)))
680 680  
707 +=== 2.5.3  ​Battery Note ===
681 681  
682 682  (((
683 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
710 +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.
684 684  )))
685 685  
686 -* (((
687 -Product Model
688 -)))
689 -* (((
690 -Uplink Interval
691 -)))
692 -* (((
693 -Working Mode
694 -)))
695 695  
696 -(((
697 -And the Life expectation in difference case will be shown on the right.
698 -)))
699 699  
700 -[[image:image-20220709110451-3.png]]
715 +=== 2.5.4  Replace the battery ===
701 701  
702 702  
703 -
704 -=== 2.8.3  ​Battery Note ===
705 -
706 706  (((
707 -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.
719 +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.
708 708  )))
709 709  
710 710  
711 -
712 -=== 2.8.4  Replace the battery ===
713 -
714 714  (((
715 -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).
724 +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).
716 716  )))
717 717  
718 718  
... ... @@ -735,7 +735,7 @@
735 735  
736 736  == 4.1  Access AT Commands ==
737 737  
738 -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/]]
747 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
739 739  
740 740  
741 741  AT+<CMD>?  : Help on <CMD>
... ... @@ -823,8 +823,12 @@
823 823  )))
824 824  
825 825  (((
826 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
835 +
836 +
837 +(((
838 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
827 827  )))
840 +)))
828 828  
829 829  
830 830  
... ... @@ -855,7 +855,7 @@
855 855  = 7. ​ Order Info =
856 856  
857 857  
858 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
871 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
859 859  
860 860  
861 861  (% class="wikigeneratedid" %)
... ... @@ -870,7 +870,7 @@
870 870  
871 871  (% style="color:#037691" %)**Package Includes**:
872 872  
873 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
886 +* N95S31B NB-IoT Temperature and Humidity Sensor
874 874  * External antenna x 1
875 875  )))
876 876  
... ... @@ -879,11 +879,10 @@
879 879  
880 880  (% style="color:#037691" %)**Dimension and weight**:
881 881  
882 -
883 883  * Device Size: 13.0 x 5 x 4.5 cm
884 884  * Device Weight: 150g
885 -* Package Size / pcs : 15 x 12x 5.5 cm
886 -* Weight / pcs : 220g
897 +* Package Size / pcs : 14.0 x 8x 5 cm
898 +* Weight / pcs : 180g
887 887  )))
888 888  
889 889  (((
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content

Applications

Navigation

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