Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.26 >
edited by Xiaoling
on 2022/07/11 08:35
To version < 103.2 >
edited by Xiaoling
on 2022/07/09 15:10
>
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,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
44 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -66,6 +66,8 @@
66 66  * Micro SIM card slot for NB-IoT SIM
67 67  * 8500mAh Battery for long term use
68 68  
56 +
57 +
69 69  == 1.3  Specification ==
70 70  
71 71  
... ... @@ -92,6 +92,8 @@
92 92  * Max continuously current: 130mA
93 93  * Max boost current: 2A, 1 second
94 94  
84 +
85 +
95 95  == ​1.4  Applications ==
96 96  
97 97  * Smart Buildings & Home Automation
... ... @@ -139,6 +139,9 @@
139 139  1. When boot the device in flash mode
140 140  1. Send an uplink packet
141 141  
133 +
134 +
135 +
142 142  = 2.  Use N95S31B to communicate with IoT Server =
143 143  
144 144  == 2.1  How it works ==
... ... @@ -182,6 +182,7 @@
182 182  * The local NB-IoT network used the band that N95S31B supports.
183 183  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
184 184  
179 +
185 185  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
186 186  
187 187  N95S31B supports different communication protocol such as :
... ... @@ -201,7 +201,7 @@
201 201  
202 202  
203 203  
204 -=== 2.2.3  Insert SIM card ===
199 +=== 2.2.2 Insert SIM card ===
205 205  
206 206  (((
207 207  Insert the NB-IoT Card get from your provider.
... ... @@ -212,19 +212,19 @@
212 212  )))
213 213  
214 214  
215 -[[image:1657351240556-536.png]]
210 +[[image:1657328884227-504.png]]
216 216  
217 217  
218 218  
219 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
214 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
220 220  
221 221  (((
222 222  (((
223 -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.
218 +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.
224 224  )))
225 225  )))
226 226  
227 -[[image:1657351312545-300.png]]
222 +[[image:image-20220709092052-2.png]]
228 228  
229 229  **Connection:**
230 230  
... ... @@ -244,18 +244,18 @@
244 244  * Flow Control: (% style="color:green" %)**None**
245 245  
246 246  (((
247 -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.
242 +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.
248 248  )))
249 249  
250 250  [[image:1657329814315-101.png]]
251 251  
252 252  (((
253 -(% 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/]]
248 +(% 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/]]
254 254  )))
255 255  
256 256  
257 257  
258 -=== 2.2.5  Use CoAP protocol to uplink data ===
253 +=== 2.2.4 Use CoAP protocol to uplink data ===
259 259  
260 260  (% 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/]]
261 261  
... ... @@ -275,12 +275,10 @@
275 275  )))
276 276  
277 277  (((
278 -
279 -
280 280  For parameter description, please refer to AT command set
281 281  )))
282 282  
283 -[[image:1657352146020-183.png]]
276 +[[image:1657330452568-615.png]]
284 284  
285 285  
286 286  (((
... ... @@ -287,11 +287,11 @@
287 287  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.
288 288  )))
289 289  
290 -[[image:1657352185396-303.png]]
283 +[[image:1657330472797-498.png]]
291 291  
292 292  
293 293  
294 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
295 295  
296 296  
297 297  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -298,16 +298,15 @@
298 298  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
299 299  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
300 300  
301 -[[image:1657352391268-297.png]]
294 +[[image:1657330501006-241.png]]
302 302  
303 303  
304 -[[image:1657352403317-397.png]]
297 +[[image:1657330533775-472.png]]
305 305  
306 306  
307 307  
308 -=== 2.2.7  Use MQTT protocol to uplink data ===
301 +=== 2.2.6 Use MQTT protocol to uplink data ===
309 309  
310 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
311 311  
312 312  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
313 313  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -314,40 +314,35 @@
314 314  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
315 315  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
316 316  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
317 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
318 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
319 319  
320 -[[image:1657352634421-276.png]]
312 +[[image:1657249978444-674.png]]
321 321  
322 322  
323 -[[image:1657352645687-385.png]]
315 +[[image:1657330723006-866.png]]
324 324  
325 -(((
326 -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.
327 -)))
328 328  
329 -
330 330  (((
331 -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.
319 +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.
332 332  )))
333 333  
334 334  
335 335  
336 -=== 2.2.8  Use TCP protocol to uplink data ===
324 +=== 2.2.7 Use TCP protocol to uplink data ===
337 337  
338 -This feature is supported since firmware version v110
339 339  
340 340  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
341 341  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
342 342  
343 -[[image:1657352898400-901.png]]
330 +[[image:image-20220709093918-1.png]]
344 344  
345 345  
346 -[[image:1657352914475-252.png]]
333 +[[image:image-20220709093918-2.png]]
347 347  
348 348  
349 349  
350 -=== 2.2.9  Change Update Interval ===
337 +=== 2.2.8 Change Update Interval ===
351 351  
352 352  User can use below command to change the (% style="color:green" %)**uplink interval**.
353 353  
... ... @@ -354,207 +354,227 @@
354 354  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
355 355  
356 356  (((
357 -
344 +(% style="color:red" %)**NOTE:**
358 358  )))
359 359  
347 +(((
348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
349 +)))
360 360  
361 361  
352 +
362 362  == 2.3  Uplink Payload ==
363 363  
355 +In this mode, uplink payload includes in total 14 bytes
364 364  
365 -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.
366 366  
358 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
359 +|=(% style="width: 60px;" %)(((
360 +**Size(bytes)**
361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
362 +|(% 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"]]
367 367  
368 -For example:
364 +(((
365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
366 +)))
369 369  
370 - (% 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.
371 371  
369 +[[image:1657331036973-987.png]]
372 372  
373 -The uplink payloads are composed in  ASCII String. For example:
371 +(((
372 +The payload is ASCII string, representative same HEX:
373 +)))
374 374  
375 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
375 +(((
376 +0x72403155615900640c6c19029200 where:
377 +)))
376 376  
377 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
379 +* (((
380 +Device ID: 0x724031556159 = 724031556159
381 +)))
382 +* (((
383 +Version: 0x0064=100=1.0.0
384 +)))
378 378  
386 +* (((
387 +BAT: 0x0c6c = 3180 mV = 3.180V
388 +)))
389 +* (((
390 +Signal: 0x19 = 25
391 +)))
392 +* (((
393 +Distance: 0x0292= 658 mm
394 +)))
395 +* (((
396 +Interrupt: 0x00 = 0
379 379  
380 -(% style="color:red" %)**NOTE:**
381 381  
382 -(% style="color:red" %)
383 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
384 -1. By default, the device will send an uplink message every 1 hour.
385 385  
400 +
401 +)))
386 386  
387 -=== 2.3.1  Payload Analyze ===
403 +== 2.4  Payload Explanation and Sensor Interface ==
388 388  
389 -N95S31B uplink payload includes in total 21 bytes
390 390  
406 +=== 2.4.1  Device ID ===
391 391  
392 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
393 -|=(% style="width: 60px;" %)(((
394 -**Size(bytes)**
395 -)))|=(% 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**
396 -|(% 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 -Reserve/ Same as NBSN95 CFGMOD=1
409 +By default, the Device ID equal to the last 6 bytes of IMEI.
399 399  )))
400 400  
401 401  (((
402 -No function here.
413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
403 403  )))
404 -)))|(% style="width:77px" %)(((
415 +
405 405  (((
406 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
417 +**Example:**
407 407  )))
408 408  
409 409  (((
410 -By SHT31
421 +AT+DEUI=A84041F15612
411 411  )))
412 -)))|(% style="width:80px" %)(((
423 +
413 413  (((
414 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
415 415  )))
416 416  
428 +
429 +
430 +=== 2.4.2  Version Info ===
431 +
417 417  (((
418 -By SHT31
433 +Specify the software version: 0x64=100, means firmware version 1.00.
419 419  )))
420 -)))
421 421  
422 422  (((
423 -(((
424 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
425 425  )))
426 -)))
427 427  
428 428  
429 -[[image:1657354294009-643.png]]
430 430  
442 +=== 2.4.3  Battery Info ===
431 431  
432 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
433 -
434 -* Device ID: 0x724031607457 = 724031607457
435 -* Version: 0x006e=110=1.1.0
436 -
437 -* BAT: 0x0ccd = 3277 mV = 3.277V
438 -* Signal: 0x1b = 27
439 -* Model: 0x01 = 1
440 -* 0x00dc000ccc= reserve, ignore in N95S31B
441 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
442 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
443 -
444 444  (((
445 -
445 +Ex1: 0x0B45 = 2885mV
446 446  )))
447 447  
448 448  (((
449 -
449 +Ex2: 0x0B49 = 2889mV
450 450  )))
451 451  
452 452  
453 -=== 2.3.2  Device ID ===
454 454  
454 +=== 2.4.4  Signal Strength ===
455 +
455 455  (((
456 -By default, the Device ID equal to the last 6 bytes of IMEI.
457 +NB-IoT Network signal Strength.
457 457  )))
458 458  
459 459  (((
460 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
461 +**Ex1: 0x1d = 29**
461 461  )))
462 462  
463 463  (((
464 -**Example:**
465 +(% style="color:blue" %)**0**(%%)  -113dBm or less
465 465  )))
466 466  
467 467  (((
468 -AT+DEUI=A84041F15612
469 +(% style="color:blue" %)**1**(%%)  -111dBm
469 469  )))
470 470  
471 471  (((
472 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
473 473  )))
474 474  
476 +(((
477 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
478 +)))
475 475  
480 +(((
481 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
482 +)))
476 476  
477 -=== 2.3.3  Version Info ===
478 478  
479 479  
480 -These bytes include the hardware and software version.
486 +=== 2.4.5  Distance ===
481 481  
482 -Higher byte: Specify hardware version: always 0x00 for N95S31B
488 +Get the distance. Flat object range 280mm - 7500mm.
483 483  
484 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
490 +(((
491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
492 +)))
485 485  
486 -
487 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
488 -
489 489  (((
490 -
495 +(((
496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
491 491  )))
498 +)))
492 492  
493 -
494 -=== 2.3.4  Battery Info ===
495 -
496 496  (((
497 -Ex1: 0x0B45 = 2885mV
501 +
498 498  )))
499 499  
500 500  (((
501 -Ex2: 0x0B49 = 2889mV
505 +
502 502  )))
503 503  
508 +=== 2.4.6  Digital Interrupt ===
504 504  
505 -
506 -=== 2.3.5  Signal Strength ===
507 -
508 508  (((
509 -NB-IoT Network signal Strength.
511 +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.
510 510  )))
511 511  
512 512  (((
513 -**Ex1: 0x1d = 29**
515 +The command is:
514 514  )))
515 515  
516 516  (((
517 -(% style="color:blue" %)**0**(%%)  -113dBm or less
519 +(% 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]])**.**
518 518  )))
519 519  
522 +
520 520  (((
521 -(% style="color:blue" %)**1**(%%)  -111dBm
524 +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.
522 522  )))
523 523  
527 +
524 524  (((
525 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
529 +Example:
526 526  )))
527 527  
528 528  (((
529 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
533 +0x(00): Normal uplink packet.
530 530  )))
531 531  
532 532  (((
533 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
537 +0x(01): Interrupt Uplink Packet.
534 534  )))
535 535  
536 536  
537 537  
538 -=== 2.3.6  Temperature & Humidity ===
542 +=== 2.4.7  ​+5V Output ===
539 539  
540 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
544 +(((
545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
546 +)))
541 541  
542 -[[image:image-20220709161741-3.png]]
543 543  
549 +(((
550 +The 5V output time can be controlled by AT Command.
551 +)))
544 544  
545 -Convert the read byte to decimal and divide it by ten.
553 +(((
554 +(% style="color:blue" %)**AT+5VT=1000**
555 +)))
546 546  
557 +(((
558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
559 +)))
547 547  
548 -**Example:**
549 549  
550 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
551 551  
552 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
563 +== 2.5  Downlink Payload ==
553 553  
554 -
555 -
556 -== 2.4  Downlink Payload ==
557 -
558 558  By default, NDDS75 prints the downlink payload to console port.
559 559  
560 560  [[image:image-20220709100028-1.png]]
... ... @@ -605,16 +605,51 @@
605 605  
606 606  
607 607  
608 -== 2.5  ​Battery Analysis ==
615 +== 2.6  ​LED Indicator ==
609 609  
610 -=== 2.5.1  ​Battery Type ===
611 611  
618 +The NDDS75 has an internal LED which is to show the status of different state.
612 612  
620 +
621 +* 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)
622 +* Then the LED will be on for 1 second means device is boot normally.
623 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
624 +* For each uplink probe, LED will be on for 500ms.
625 +
613 613  (((
614 -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.
627 +
615 615  )))
616 616  
630 +
631 +
632 +== 2.7  ​Firmware Change Log ==
633 +
634 +
617 617  (((
636 +Download URL & Firmware Change log
637 +)))
638 +
639 +(((
640 +[[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/]]
641 +)))
642 +
643 +
644 +(((
645 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
646 +)))
647 +
648 +
649 +
650 +== 2.8  ​Battery Analysis ==
651 +
652 +=== 2.8.1  ​Battery Type ===
653 +
654 +
655 +(((
656 +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.
657 +)))
658 +
659 +(((
618 618  The battery is designed to last for several years depends on the actually use environment and update interval. 
619 619  )))
620 620  
... ... @@ -632,35 +632,56 @@
632 632  
633 633  
634 634  
635 -=== 2.5.2  Power consumption Analyze ===
677 +=== 2.8.2  Power consumption Analyze ===
636 636  
637 637  (((
638 -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.
680 +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.
639 639  )))
640 640  
683 +
641 641  (((
642 -
685 +Instruction to use as below:
643 643  )))
644 644  
688 +(((
689 +(% 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/]]
690 +)))
645 645  
646 -=== 2.5.3  ​Battery Note ===
647 647  
648 648  (((
649 -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.
694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
650 650  )))
651 651  
697 +* (((
698 +Product Model
699 +)))
700 +* (((
701 +Uplink Interval
702 +)))
703 +* (((
704 +Working Mode
705 +)))
652 652  
707 +(((
708 +And the Life expectation in difference case will be shown on the right.
709 +)))
653 653  
654 -=== 2.5.4  Replace the battery ===
711 +[[image:image-20220709110451-3.png]]
655 655  
656 656  
714 +
715 +=== 2.8.3  ​Battery Note ===
716 +
657 657  (((
658 -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.
718 +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 659  )))
660 660  
661 661  
722 +
723 +=== 2.8.4  Replace the battery ===
724 +
662 662  (((
663 -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).
726 +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).
664 664  )))
665 665  
666 666  
... ... @@ -683,7 +683,7 @@
683 683  
684 684  == 4.1  Access AT Commands ==
685 685  
686 -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/]]
749 +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/]]
687 687  
688 688  
689 689  AT+<CMD>?  : Help on <CMD>
... ... @@ -771,9 +771,7 @@
771 771  )))
772 772  
773 773  (((
774 -
775 -
776 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
777 777  )))
778 778  
779 779  
... ... @@ -805,7 +805,7 @@
805 805  = 7. ​ Order Info =
806 806  
807 807  
808 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
809 809  
810 810  
811 811  (% class="wikigeneratedid" %)
... ... @@ -820,7 +820,7 @@
820 820  
821 821  (% style="color:#037691" %)**Package Includes**:
822 822  
823 -* N95S31B NB-IoT Temperature and Humidity Sensor
884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
824 824  * External antenna x 1
825 825  )))
826 826  
... ... @@ -829,10 +829,11 @@
829 829  
830 830  (% style="color:#037691" %)**Dimension and weight**:
831 831  
893 +
832 832  * Device Size: 13.0 x 5 x 4.5 cm
833 833  * Device Weight: 150g
834 -* Package Size / pcs : 14.0 x 8x 5 cm
835 -* Weight / pcs : 180g
896 +* Package Size / pcs : 15 x 12x 5.5 cm
897 +* Weight / pcs : 220g
836 836  )))
837 837  
838 838  (((
1657351240556-536.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content

Applications

Navigation

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