Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.27 >
edited by Xiaoling
on 2022/07/11 08:36
To version < 111.1 >
edited by Xiaoling
on 2022/07/09 15:44
>
Change comment: Uploaded new attachment "1657352645687-385.png", version {1}

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
... ... @@ -68,7 +68,6 @@
68 68  
69 69  
70 70  
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -95,6 +95,8 @@
95 95  * Max continuously current: 130mA
96 96  * Max boost current: 2A, 1 second
97 97  
84 +
85 +
98 98  == ​1.4  Applications ==
99 99  
100 100  * Smart Buildings & Home Automation
... ... @@ -142,6 +142,9 @@
142 142  1. When boot the device in flash mode
143 143  1. Send an uplink packet
144 144  
133 +
134 +
135 +
145 145  = 2.  Use N95S31B to communicate with IoT Server =
146 146  
147 147  == 2.1  How it works ==
... ... @@ -185,6 +185,7 @@
185 185  * The local NB-IoT network used the band that N95S31B supports.
186 186  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
187 187  
179 +
188 188  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
189 189  
190 190  N95S31B supports different communication protocol such as :
... ... @@ -301,16 +301,15 @@
301 301  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
302 302  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
303 303  
304 -[[image:1657352391268-297.png]]
296 +[[image:1657330501006-241.png]]
305 305  
306 306  
307 -[[image:1657352403317-397.png]]
299 +[[image:1657330533775-472.png]]
308 308  
309 309  
310 310  
311 -=== 2.2.7  Use MQTT protocol to uplink data ===
303 +=== 2.2.6 Use MQTT protocol to uplink data ===
312 312  
313 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
314 314  
315 315  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
316 316  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -317,40 +317,35 @@
317 317  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
318 318  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
319 319  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
320 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
321 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
322 322  
323 -[[image:1657352634421-276.png]]
314 +[[image:1657249978444-674.png]]
324 324  
325 325  
326 -[[image:1657352645687-385.png]]
317 +[[image:1657330723006-866.png]]
327 327  
328 -(((
329 -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.
330 -)))
331 331  
332 -
333 333  (((
334 -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.
321 +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.
335 335  )))
336 336  
337 337  
338 338  
339 -=== 2.2.8  Use TCP protocol to uplink data ===
326 +=== 2.2.7 Use TCP protocol to uplink data ===
340 340  
341 -This feature is supported since firmware version v110
342 342  
343 343  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
344 344  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
345 345  
346 -[[image:1657352898400-901.png]]
332 +[[image:image-20220709093918-1.png]]
347 347  
348 348  
349 -[[image:1657352914475-252.png]]
335 +[[image:image-20220709093918-2.png]]
350 350  
351 351  
352 352  
353 -=== 2.2.9  Change Update Interval ===
339 +=== 2.2.8 Change Update Interval ===
354 354  
355 355  User can use below command to change the (% style="color:green" %)**uplink interval**.
356 356  
... ... @@ -357,207 +357,227 @@
357 357  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
358 358  
359 359  (((
360 -
346 +(% style="color:red" %)**NOTE:**
361 361  )))
362 362  
349 +(((
350 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
351 +)))
363 363  
364 364  
354 +
365 365  == 2.3  Uplink Payload ==
366 366  
357 +In this mode, uplink payload includes in total 14 bytes
367 367  
368 -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.
369 369  
360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
361 +|=(% style="width: 60px;" %)(((
362 +**Size(bytes)**
363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 +|(% 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"]]
370 370  
371 -For example:
366 +(((
367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
368 +)))
372 372  
373 - (% 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.
374 374  
371 +[[image:1657331036973-987.png]]
375 375  
376 -The uplink payloads are composed in  ASCII String. For example:
373 +(((
374 +The payload is ASCII string, representative same HEX:
375 +)))
377 377  
378 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
377 +(((
378 +0x72403155615900640c6c19029200 where:
379 +)))
379 379  
380 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
381 +* (((
382 +Device ID: 0x724031556159 = 724031556159
383 +)))
384 +* (((
385 +Version: 0x0064=100=1.0.0
386 +)))
381 381  
388 +* (((
389 +BAT: 0x0c6c = 3180 mV = 3.180V
390 +)))
391 +* (((
392 +Signal: 0x19 = 25
393 +)))
394 +* (((
395 +Distance: 0x0292= 658 mm
396 +)))
397 +* (((
398 +Interrupt: 0x00 = 0
382 382  
383 -(% style="color:red" %)**NOTE:**
384 384  
385 -(% style="color:red" %)
386 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
387 -1. By default, the device will send an uplink message every 1 hour.
388 388  
402 +
403 +)))
389 389  
390 -=== 2.3.1  Payload Analyze ===
405 +== 2.4  Payload Explanation and Sensor Interface ==
391 391  
392 -N95S31B uplink payload includes in total 21 bytes
393 393  
408 +=== 2.4.1  Device ID ===
394 394  
395 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
396 -|=(% style="width: 60px;" %)(((
397 -**Size(bytes)**
398 -)))|=(% 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**
399 -|(% 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" %)(((
400 400  (((
401 -Reserve/ Same as NBSN95 CFGMOD=1
411 +By default, the Device ID equal to the last 6 bytes of IMEI.
402 402  )))
403 403  
404 404  (((
405 -No function here.
415 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
406 406  )))
407 -)))|(% style="width:77px" %)(((
417 +
408 408  (((
409 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
419 +**Example:**
410 410  )))
411 411  
412 412  (((
413 -By SHT31
423 +AT+DEUI=A84041F15612
414 414  )))
415 -)))|(% style="width:80px" %)(((
425 +
416 416  (((
417 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
427 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
418 418  )))
419 419  
430 +
431 +
432 +=== 2.4.2  Version Info ===
433 +
420 420  (((
421 -By SHT31
435 +Specify the software version: 0x64=100, means firmware version 1.00.
422 422  )))
423 -)))
424 424  
425 425  (((
426 -(((
427 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
439 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
428 428  )))
429 -)))
430 430  
431 431  
432 -[[image:1657354294009-643.png]]
433 433  
444 +=== 2.4.3  Battery Info ===
434 434  
435 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
436 -
437 -* Device ID: 0x724031607457 = 724031607457
438 -* Version: 0x006e=110=1.1.0
439 -
440 -* BAT: 0x0ccd = 3277 mV = 3.277V
441 -* Signal: 0x1b = 27
442 -* Model: 0x01 = 1
443 -* 0x00dc000ccc= reserve, ignore in N95S31B
444 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
445 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
446 -
447 447  (((
448 -
447 +Ex1: 0x0B45 = 2885mV
449 449  )))
450 450  
451 451  (((
452 -
451 +Ex2: 0x0B49 = 2889mV
453 453  )))
454 454  
455 455  
456 -=== 2.3.2  Device ID ===
457 457  
456 +=== 2.4.4  Signal Strength ===
457 +
458 458  (((
459 -By default, the Device ID equal to the last 6 bytes of IMEI.
459 +NB-IoT Network signal Strength.
460 460  )))
461 461  
462 462  (((
463 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
463 +**Ex1: 0x1d = 29**
464 464  )))
465 465  
466 466  (((
467 -**Example:**
467 +(% style="color:blue" %)**0**(%%)  -113dBm or less
468 468  )))
469 469  
470 470  (((
471 -AT+DEUI=A84041F15612
471 +(% style="color:blue" %)**1**(%%)  -111dBm
472 472  )))
473 473  
474 474  (((
475 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
475 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
476 476  )))
477 477  
478 +(((
479 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
480 +)))
478 478  
482 +(((
483 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
484 +)))
479 479  
480 -=== 2.3.3  Version Info ===
481 481  
482 482  
483 -These bytes include the hardware and software version.
488 +=== 2.4.5  Distance ===
484 484  
485 -Higher byte: Specify hardware version: always 0x00 for N95S31B
490 +Get the distance. Flat object range 280mm - 7500mm.
486 486  
487 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
492 +(((
493 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
494 +)))
488 488  
489 -
490 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
491 -
492 492  (((
493 -
497 +(((
498 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
494 494  )))
500 +)))
495 495  
496 -
497 -=== 2.3.4  Battery Info ===
498 -
499 499  (((
500 -Ex1: 0x0B45 = 2885mV
503 +
501 501  )))
502 502  
503 503  (((
504 -Ex2: 0x0B49 = 2889mV
507 +
505 505  )))
506 506  
510 +=== 2.4.6  Digital Interrupt ===
507 507  
508 -
509 -=== 2.3.5  Signal Strength ===
510 -
511 511  (((
512 -NB-IoT Network signal Strength.
513 +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.
513 513  )))
514 514  
515 515  (((
516 -**Ex1: 0x1d = 29**
517 +The command is:
517 517  )))
518 518  
519 519  (((
520 -(% style="color:blue" %)**0**(%%)  -113dBm or less
521 +(% 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]])**.**
521 521  )))
522 522  
524 +
523 523  (((
524 -(% style="color:blue" %)**1**(%%)  -111dBm
526 +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.
525 525  )))
526 526  
529 +
527 527  (((
528 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
531 +Example:
529 529  )))
530 530  
531 531  (((
532 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
535 +0x(00): Normal uplink packet.
533 533  )))
534 534  
535 535  (((
536 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
539 +0x(01): Interrupt Uplink Packet.
537 537  )))
538 538  
539 539  
540 540  
541 -=== 2.3.6  Temperature & Humidity ===
544 +=== 2.4.7  ​+5V Output ===
542 542  
543 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
546 +(((
547 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
548 +)))
544 544  
545 -[[image:image-20220709161741-3.png]]
546 546  
551 +(((
552 +The 5V output time can be controlled by AT Command.
553 +)))
547 547  
548 -Convert the read byte to decimal and divide it by ten.
555 +(((
556 +(% style="color:blue" %)**AT+5VT=1000**
557 +)))
549 549  
559 +(((
560 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
561 +)))
550 550  
551 -**Example:**
552 552  
553 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
554 554  
555 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
565 +== 2.5  Downlink Payload ==
556 556  
557 -
558 -
559 -== 2.4  Downlink Payload ==
560 -
561 561  By default, NDDS75 prints the downlink payload to console port.
562 562  
563 563  [[image:image-20220709100028-1.png]]
... ... @@ -608,16 +608,51 @@
608 608  
609 609  
610 610  
611 -== 2.5  ​Battery Analysis ==
617 +== 2.6  ​LED Indicator ==
612 612  
613 -=== 2.5.1  ​Battery Type ===
614 614  
620 +The NDDS75 has an internal LED which is to show the status of different state.
615 615  
622 +
623 +* 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)
624 +* Then the LED will be on for 1 second means device is boot normally.
625 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
626 +* For each uplink probe, LED will be on for 500ms.
627 +
616 616  (((
617 -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.
629 +
618 618  )))
619 619  
632 +
633 +
634 +== 2.7  ​Firmware Change Log ==
635 +
636 +
620 620  (((
638 +Download URL & Firmware Change log
639 +)))
640 +
641 +(((
642 +[[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/]]
643 +)))
644 +
645 +
646 +(((
647 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
648 +)))
649 +
650 +
651 +
652 +== 2.8  ​Battery Analysis ==
653 +
654 +=== 2.8.1  ​Battery Type ===
655 +
656 +
657 +(((
658 +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.
659 +)))
660 +
661 +(((
621 621  The battery is designed to last for several years depends on the actually use environment and update interval. 
622 622  )))
623 623  
... ... @@ -635,35 +635,56 @@
635 635  
636 636  
637 637  
638 -=== 2.5.2  Power consumption Analyze ===
679 +=== 2.8.2  Power consumption Analyze ===
639 639  
640 640  (((
641 -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.
682 +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.
642 642  )))
643 643  
685 +
644 644  (((
645 -
687 +Instruction to use as below:
646 646  )))
647 647  
690 +(((
691 +(% 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/]]
692 +)))
648 648  
649 -=== 2.5.3  ​Battery Note ===
650 650  
651 651  (((
652 -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.
696 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
653 653  )))
654 654  
699 +* (((
700 +Product Model
701 +)))
702 +* (((
703 +Uplink Interval
704 +)))
705 +* (((
706 +Working Mode
707 +)))
655 655  
709 +(((
710 +And the Life expectation in difference case will be shown on the right.
711 +)))
656 656  
657 -=== 2.5.4  Replace the battery ===
713 +[[image:image-20220709110451-3.png]]
658 658  
659 659  
716 +
717 +=== 2.8.3  ​Battery Note ===
718 +
660 660  (((
661 -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.
720 +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.
662 662  )))
663 663  
664 664  
724 +
725 +=== 2.8.4  Replace the battery ===
726 +
665 665  (((
666 -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).
728 +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 667  )))
668 668  
669 669  
... ... @@ -686,7 +686,7 @@
686 686  
687 687  == 4.1  Access AT Commands ==
688 688  
689 -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/]]
751 +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/]]
690 690  
691 691  
692 692  AT+<CMD>?  : Help on <CMD>
... ... @@ -774,9 +774,7 @@
774 774  )))
775 775  
776 776  (((
777 -
778 -
779 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
839 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
780 780  )))
781 781  
782 782  
... ... @@ -808,7 +808,7 @@
808 808  = 7. ​ Order Info =
809 809  
810 810  
811 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
871 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
812 812  
813 813  
814 814  (% class="wikigeneratedid" %)
... ... @@ -823,7 +823,7 @@
823 823  
824 824  (% style="color:#037691" %)**Package Includes**:
825 825  
826 -* N95S31B NB-IoT Temperature and Humidity Sensor
886 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
827 827  * External antenna x 1
828 828  )))
829 829  
... ... @@ -832,10 +832,11 @@
832 832  
833 833  (% style="color:#037691" %)**Dimension and weight**:
834 834  
895 +
835 835  * Device Size: 13.0 x 5 x 4.5 cm
836 836  * Device Weight: 150g
837 -* Package Size / pcs : 14.0 x 8x 5 cm
838 -* Weight / pcs : 180g
898 +* Package Size / pcs : 15 x 12x 5.5 cm
899 +* Weight / pcs : 220g
839 839  )))
840 840  
841 841  (((
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