Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 108.1 >
edited by Xiaoling
on 2022/07/09 15:39
To version < 115.21 >
edited by Xiaoling
on 2022/07/09 18:17
>
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  
... ... @@ -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
... ... @@ -53,8 +53,6 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -81,8 +81,6 @@
81 81  * Max continuously current: 130mA
82 82  * Max boost current: 2A, 1 second
83 83  
84 -
85 -
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -130,9 +130,6 @@
130 130  1. When boot the device in flash mode
131 131  1. Send an uplink packet
132 132  
133 -
134 -
135 -
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
138 138  == 2.1  How it works ==
... ... @@ -176,7 +176,6 @@
176 176  * The local NB-IoT network used the band that N95S31B supports.
177 177  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
178 178  
179 -
180 180  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  N95S31B supports different communication protocol such as :
... ... @@ -293,15 +293,16 @@
293 293  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
294 294  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
295 295  
296 -[[image:1657330501006-241.png]]
288 +[[image:1657352391268-297.png]]
297 297  
298 298  
299 -[[image:1657330533775-472.png]]
291 +[[image:1657352403317-397.png]]
300 300  
301 301  
302 302  
303 -=== 2.2.6 Use MQTT protocol to uplink data ===
295 +=== 2.2.7  Use MQTT protocol to uplink data ===
304 304  
297 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
305 305  
306 306  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 307  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -308,35 +308,40 @@
308 308  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 309  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 310  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password 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
304 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
305 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
313 313  
314 -[[image:1657249978444-674.png]]
307 +[[image:1657352634421-276.png]]
315 315  
316 316  
317 -[[image:1657330723006-866.png]]
310 +[[image:1657352645687-385.png]]
318 318  
312 +(((
313 +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.
314 +)))
319 319  
316 +
320 320  (((
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.
318 +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.
322 322  )))
323 323  
324 324  
325 325  
326 -=== 2.2.7 Use TCP protocol to uplink data ===
323 +=== 2.2.8  Use TCP protocol to uplink data ===
327 327  
325 +This feature is supported since firmware version v110
328 328  
329 329  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
330 330  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
331 331  
332 -[[image:image-20220709093918-1.png]]
330 +[[image:1657352898400-901.png]]
333 333  
334 334  
335 -[[image:image-20220709093918-2.png]]
333 +[[image:1657352914475-252.png]]
336 336  
337 337  
338 338  
339 -=== 2.2.8 Change Update Interval ===
337 +=== 2.2.9  Change Update Interval ===
340 340  
341 341  User can use below command to change the (% style="color:green" %)**uplink interval**.
342 342  
... ... @@ -343,227 +343,209 @@
343 343  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
344 344  
345 345  (((
346 -(% style="color:red" %)**NOTE:**
344 +
347 347  )))
348 348  
349 -(((
350 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
351 -)))
352 352  
353 353  
354 -
355 355  == 2.3  Uplink Payload ==
356 356  
357 -In this mode, uplink payload includes in total 14 bytes
358 358  
352 +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.
359 359  
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"]]
365 365  
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 -)))
355 +For example:
369 369  
357 + (% 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.
370 370  
371 -[[image:1657331036973-987.png]]
372 372  
373 -(((
374 -The payload is ASCII string, representative same HEX:
375 -)))
360 +The uplink payloads are composed in  ASCII String. For example:
376 376  
377 -(((
378 -0x72403155615900640c6c19029200 where:
379 -)))
362 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
380 380  
381 -* (((
382 -Device ID: 0x724031556159 = 724031556159
383 -)))
384 -* (((
385 -Version: 0x0064=100=1.0.0
386 -)))
364 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
387 387  
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
399 399  
367 +(% style="color:red" %)**NOTE:**
400 400  
369 +(% style="color:red" %)
370 +1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
371 +1. By default, the device will send an uplink message every 1 hour.
401 401  
402 -
403 -)))
404 404  
405 -== 2.4  Payload Explanation and Sensor Interface ==
406 406  
407 407  
408 -=== 2.4.1  Device ID ===
376 +=== 2.3.1  Payload Analyze ===
409 409  
378 +N95S31B uplink payload includes in total 21 bytes
379 +
380 +
381 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
382 +|=(% style="width: 60px;" %)(((
383 +**Size(bytes)**
384 +)))|=(% style="width: 45px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 120px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
385 +|(% 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" %)(((
410 410  (((
411 -By default, the Device ID equal to the last 6 bytes of IMEI.
387 +Reserve/ Same as NBSN95 CFGMOD=1
412 412  )))
413 413  
414 414  (((
415 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
391 +No function here.
416 416  )))
417 -
393 +)))|(% style="width:77px" %)(((
418 418  (((
419 -**Example:**
395 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
420 420  )))
421 421  
422 422  (((
423 -AT+DEUI=A84041F15612
399 +By SHT31
424 424  )))
425 -
401 +)))|(% style="width:80px" %)(((
426 426  (((
427 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
403 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
428 428  )))
429 429  
430 -
431 -
432 -=== 2.4.2  Version Info ===
433 -
434 434  (((
435 -Specify the software version: 0x64=100, means firmware version 1.00.
407 +By SHT31
436 436  )))
409 +)))
437 437  
438 438  (((
439 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
412 +(((
413 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
440 440  )))
415 +)))
441 441  
442 442  
418 +[[image:1657354294009-643.png]]
443 443  
444 -=== 2.4.3  Battery Info ===
445 445  
421 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
422 +
423 +* Device ID: 0x724031607457 = 724031607457
424 +* Version: 0x006e=110=1.1.0
425 +
426 +* BAT: 0x0ccd = 3277 mV = 3.277V
427 +* Signal: 0x1b = 27
428 +* Model: 0x01 = 1
429 +* 0x00dc000ccc= reserve, ignore in N95S31B
430 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
431 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
432 +
446 446  (((
447 -Ex1: 0x0B45 = 2885mV
434 +
448 448  )))
449 449  
450 450  (((
451 -Ex2: 0x0B49 = 2889mV
438 +
452 452  )))
453 453  
454 454  
442 +=== 2.3.2  Device ID ===
455 455  
456 -=== 2.4.4  Signal Strength ===
457 -
458 458  (((
459 -NB-IoT Network signal Strength.
445 +By default, the Device ID equal to the last 6 bytes of IMEI.
460 460  )))
461 461  
462 462  (((
463 -**Ex1: 0x1d = 29**
449 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
464 464  )))
465 465  
466 466  (((
467 -(% style="color:blue" %)**0**(%%)  -113dBm or less
453 +**Example:**
468 468  )))
469 469  
470 470  (((
471 -(% style="color:blue" %)**1**(%%)  -111dBm
457 +AT+DEUI=A84041F15612
472 472  )))
473 473  
474 474  (((
475 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
461 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
476 476  )))
477 477  
478 -(((
479 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
480 -)))
481 481  
482 -(((
483 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
484 -)))
485 485  
466 +=== 2.3.3  Version Info ===
486 486  
487 487  
488 -=== 2.4.5  Distance ===
469 +These bytes include the hardware and software version.
489 489  
490 -Get the distance. Flat object range 280mm - 7500mm.
471 +Higher byte: Specify hardware version: always 0x00 for N95S31B
491 491  
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 -)))
473 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
495 495  
475 +
476 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
477 +
496 496  (((
497 -(((
498 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
479 +
499 499  )))
500 -)))
501 501  
482 +
483 +=== 2.3.4  Battery Info ===
484 +
502 502  (((
503 -
486 +Ex1: 0x0B45 = 2885mV
504 504  )))
505 505  
506 506  (((
507 -
490 +Ex2: 0x0B49 = 2889mV
508 508  )))
509 509  
510 -=== 2.4.6  Digital Interrupt ===
511 511  
494 +
495 +=== 2.3.5  Signal Strength ===
496 +
512 512  (((
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.
498 +NB-IoT Network signal Strength.
514 514  )))
515 515  
516 516  (((
517 -The command is:
502 +**Ex1: 0x1d = 29**
518 518  )))
519 519  
520 520  (((
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]])**.**
506 +(% style="color:blue" %)**0**(%%)  -113dBm or less
522 522  )))
523 523  
524 -
525 525  (((
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.
510 +(% style="color:blue" %)**1**(%%)  -111dBm
527 527  )))
528 528  
529 -
530 530  (((
531 -Example:
514 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
532 532  )))
533 533  
534 534  (((
535 -0x(00): Normal uplink packet.
518 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
536 536  )))
537 537  
538 538  (((
539 -0x(01): Interrupt Uplink Packet.
522 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
540 540  )))
541 541  
542 542  
543 543  
544 -=== 2.4.7  ​+5V Output ===
527 +=== 2.3.6  Temperature & Humidity ===
545 545  
546 -(((
547 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
548 -)))
529 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
549 549  
531 +[[image:image-20220709161741-3.png]]
550 550  
551 -(((
552 -The 5V output time can be controlled by AT Command.
553 -)))
554 554  
555 -(((
556 -(% style="color:blue" %)**AT+5VT=1000**
557 -)))
534 +Convert the read byte to decimal and divide it by ten.
558 558  
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 -)))
562 562  
537 +**Example:**
563 563  
539 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
564 564  
565 -== 2.5  Downlink Payload ==
541 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
566 566  
543 +
544 +
545 +== 2.4  Downlink Payload ==
546 +
567 567  By default, NDDS75 prints the downlink payload to console port.
568 568  
569 569  [[image:image-20220709100028-1.png]]
... ... @@ -614,51 +614,16 @@
614 614  
615 615  
616 616  
617 -== 2.6  ​LED Indicator ==
597 +== 2.5  ​Battery Analysis ==
618 618  
599 +=== 2.5.1  ​Battery Type ===
619 619  
620 -The NDDS75 has an internal LED which is to show the status of different state.
621 621  
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 -
628 628  (((
629 -
603 +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.
630 630  )))
631 631  
632 -
633 -
634 -== 2.7  ​Firmware Change Log ==
635 -
636 -
637 637  (((
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 -(((
662 662  The battery is designed to last for several years depends on the actually use environment and update interval. 
663 663  )))
664 664  
... ... @@ -676,56 +676,35 @@
676 676  
677 677  
678 678  
679 -=== 2.8.2  Power consumption Analyze ===
624 +=== 2.5.2  Power consumption Analyze ===
680 680  
681 681  (((
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.
627 +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.
683 683  )))
684 684  
685 -
686 686  (((
687 -Instruction to use as below:
631 +
688 688  )))
689 689  
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 -)))
693 693  
635 +=== 2.5.3  ​Battery Note ===
694 694  
695 695  (((
696 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
638 +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.
697 697  )))
698 698  
699 -* (((
700 -Product Model
701 -)))
702 -* (((
703 -Uplink Interval
704 -)))
705 -* (((
706 -Working Mode
707 -)))
708 708  
709 -(((
710 -And the Life expectation in difference case will be shown on the right.
711 -)))
712 712  
713 -[[image:image-20220709110451-3.png]]
643 +=== 2.5.4  Replace the battery ===
714 714  
715 715  
716 -
717 -=== 2.8.3  ​Battery Note ===
718 -
719 719  (((
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.
647 +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.
721 721  )))
722 722  
723 723  
724 -
725 -=== 2.8.4  Replace the battery ===
726 -
727 727  (((
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).
652 +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).
729 729  )))
730 730  
731 731  
... ... @@ -748,7 +748,7 @@
748 748  
749 749  == 4.1  Access AT Commands ==
750 750  
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/]]
675 +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/]]
752 752  
753 753  
754 754  AT+<CMD>?  : Help on <CMD>
... ... @@ -836,7 +836,9 @@
836 836  )))
837 837  
838 838  (((
839 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
763 +
764 +
765 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
840 840  )))
841 841  
842 842  
... ... @@ -868,7 +868,7 @@
868 868  = 7. ​ Order Info =
869 869  
870 870  
871 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
797 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
872 872  
873 873  
874 874  (% class="wikigeneratedid" %)
... ... @@ -883,7 +883,7 @@
883 883  
884 884  (% style="color:#037691" %)**Package Includes**:
885 885  
886 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
812 +* N95S31B NB-IoT Temperature and Humidity Sensor
887 887  * External antenna x 1
888 888  )))
889 889  
... ... @@ -892,11 +892,10 @@
892 892  
893 893  (% style="color:#037691" %)**Dimension and weight**:
894 894  
895 -
896 896  * Device Size: 13.0 x 5 x 4.5 cm
897 897  * Device Weight: 150g
898 -* Package Size / pcs : 15 x 12x 5.5 cm
899 -* Weight / pcs : 220g
823 +* Package Size / pcs : 14.0 x 8x 5 cm
824 +* Weight / pcs : 180g
900 900  )))
901 901  
902 902  (((
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
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