Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual

Last modified by Bei Jinggeng on 2024/05/31 09:53

From 94.1 to 95.1 From 108.14 to 108.15

From version 95.1

edited by Xiaoling
on 2022/07/09 10:20

Change comment: Uploaded new attachment "1657333200519-600.png", version {1}

To version 108.14

edited by Xiaoling
on 2023/05/17 18:16

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 4 added, 0 removed)

Details

Page properties

Content

@@ -7,6 +7,7 @@
  **Table of Contents:**
++{{toc/}}
@@ -21,24 +21,37 @@
  (((
++(((
  The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
--\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
--\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
--\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
--\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
--\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
  )))
--
++(((
++The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
  )))
--[[image:1654503236291-817.png]]
++(((
++NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
++)))
++(((
++NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
++)))
--[[image:1657327959271-447.png]]
++(((
++NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
++)))
++(((
++To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
++)))
++)))
++
++)))
++[[image:1657327959271-447.png]]
++
++
  == 1.2  Features ==
@@ -66,12 +66,12 @@
  (% style="color:#037691" %)**NB-IoT Spec:**
--* - B1 @H-FDD: 2100MHz
--* - B3 @H-FDD: 1800MHz
--* - B8 @H-FDD: 900MHz
--* - B5 @H-FDD: 850MHz
--* - B20 @H-FDD: 800MHz
--* - B28 @H-FDD: 700MHz
++* B1 @H-FDD: 2100MHz
++* B3 @H-FDD: 1800MHz
++* B8 @H-FDD: 900MHz
++* B5 @H-FDD: 850MHz
++* B20 @H-FDD: 800MHz
++* B28 @H-FDD: 700MHz
  (% style="color:#037691" %)**Battery:**
@@ -84,12 +84,12 @@
  (% style="color:#037691" %)**Power Consumption**
  * STOP Mode: 10uA @ 3.3v
--* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
++* Max transmit power: 350mA@3.3v
--
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -101,7 +101,6 @@
--
  == 1.5  Pin Definitions ==
@@ -108,11 +108,11 @@
  [[image:1657328609906-564.png]]
--
  = 2.  Use NDDS75 to communicate with IoT Server =
  == 2.1  How it works ==
++
  (((
  The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
  )))
@@ -132,22 +132,21 @@
  )))
--
  == 2.2  Configure the NDDS75 ==
--
  === 2.2.1  Test Requirement ===
++
  (((
  To use NDDS75 in your city, make sure meet below requirements:
  )))
  * Your local operator has already distributed a NB-IoT Network there.
--* The local NB-IoT network used the band that NSE01 supports.
++* The local NB-IoT network used the band that NDDS75 supports.
  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
  (((
--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
++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.
  )))
@@ -154,9 +154,9 @@
  [[image:1657328756309-230.png]]
--
  === 2.2.2  Insert SIM card ===
++
  (((
  Insert the NB-IoT Card get from your provider.
  )))
@@ -169,9 +169,9 @@
  [[image:1657328884227-504.png]]
--
  === 2.2.3  Connect USB – TTL to NDDS75 to configure it ===
++
  (((
  (((
  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.
@@ -180,15 +180,16 @@
  [[image:image-20220709092052-2.png]]
--**Connection:**
-- (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
++(% style="color:blue" %)**Connection:**
-- (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
++ (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
-- (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
++**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
++**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
++
  In the PC, use below serial tool settings:
  * Baud:       (% style="color:green" %)**9600**
@@ -203,40 +203,60 @@
  [[image:1657329814315-101.png]]
++
  (((
--(% 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/]]
++(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
  )))
--
  === 2.2.4  Use CoAP protocol to uplink data ===
--(% 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/]]
++(% 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/]]**
++
++(((
  **Use below commands:**
++)))
--* (% style="color:blue" %)**AT+PRO=1**  (%%)                                             ~/~/ Set to use CoAP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **  (%%)~/~/ to set CoAP server address and port
--* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/Set COAP resource path
++* (((
++(% style="color:blue" %)**AT+PRO=1**  (%%)                                             ~/~/ Set to use CoAP protocol to uplink
++)))
++* (((
++(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   **  (%%)~/~/  to set CoAP server address and port
++)))
++* (((
++(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/  Set COAP resource path
++
++
++)))
++
++(((
  For parameter description, please refer to AT command set
++
++)))
++
  [[image:1657330452568-615.png]]
++
++(((
  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.
++
++)))
++
  [[image:1657330472797-498.png]]
--
  === 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
--* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   **  (%%) ~/~/ to set UDP server address and port
--* (% style="color:blue" %)**AT+CFM=1       **   (%%) ~/~/If the server does not respond, this command is unnecessary
++* (% style="color:blue" %)**AT+PRO=2   ** (%%)        ~/~/  Set to use UDP protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   **  (%%) ~/~/  to set UDP server address and port
++* (% style="color:blue" %)**AT+CFM=1       **   (%%) ~/~/  If the server does not respond, this command is unnecessary
  [[image:1657330501006-241.png]]
@@ -244,17 +244,16 @@
  [[image:1657330533775-472.png]]
--
  === 2.2.6  Use MQTT protocol to uplink data ===
--* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                       ~/~/Set to use MQTT protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)   ~/~/Set MQTT server address and port
--* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                           (%%)~/~/Set up the CLIENT of MQTT
--* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
--* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
--* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
--* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%)       ~/~/Set the subscription topic of MQTT
++* (% style="color:blue" %)**AT+PRO=3   **       (%%)                                        ~/~/  Set to use MQTT protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   **   (%%)    ~/~/  Set MQTT server address and port
++* (% style="color:blue" %)**AT+CLIENT=CLIENT       **                            (%%)~/~/  Set up the CLIENT of MQTT
++* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
++* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
++* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/   Set the sending topic of MQTT
++* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%)       ~/~/   Set the subscription topic of MQTT
  [[image:1657249978444-674.png]]
@@ -267,12 +267,11 @@
  )))
--
  === 2.2.7  Use TCP protocol to uplink data ===
--* (% style="color:blue" %)**AT+PRO=4   ** (%%)                                          ~/~/ Set to use TCP protocol to uplink
--* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
++* (% style="color:blue" %)**AT+PRO=4   ** (%%)                                          ~/~/  Set to use TCP protocol to uplink
++* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/    to set TCP server address and port
  [[image:image-20220709093918-1.png]]
@@ -280,75 +280,113 @@
  [[image:image-20220709093918-2.png]]
--
  === 2.2.8  Change Update Interval ===
++
  User can use below command to change the (% style="color:green" %)**uplink interval**.
--* (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/ Set Update Interval to 600s
++* (% style="color:blue" %)**AT+TDC=600      **  (%%)~/~/  Set Update Interval to 600s
  (((
++
++
++
  (% style="color:red" %)**NOTE:**
--)))
--(((
--(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
++(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
++
++(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
  )))
++(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
  == 2.3  Uplink Payload ==
--In this mode, uplink payload includes in total 14 bytes
++=== 2.3.1  Before Firmware v1.3.2 ===
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
--|=(% style="width: 60px;" %)(((
++In this mode, uplink payload includes in total 14 bytes
++
++(% border="1" cellspacing="10" style="background-color:#f2f2f2; width:440px" %)
++|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
  **Size(bytes)**
--)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
--|(% 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
++)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
++|(% 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"]]
  (((
--If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
  )))
  [[image:1657331036973-987.png]]
--(((
++
++The payload is **ASCII** string, representative same HEX:
++
++(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
++
++**where :**
++
++* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
++
++* (% style="color:#037691" %)**Version:**(%%)    0x0064=100=1.0.0
++
++* (% style="color:#037691" %)**BAT:** (%%)      0x0c6c = 3180 mV = 3.180V
++
++* (% style="color:#037691" %)**Signal:**(%%)   0x19 = 25
++
++* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
++
++* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
++
++=== 2.3.2  Since firmware v1.3.2 ===
++
++
++In this mode, uplink payload includes 69 bytes in total by default.
++
++Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
++
++(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
++|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:70px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**4**
++|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
++
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
++
++[[image:image-20220908175246-1.png]]
++
++
  The payload is ASCII string, representative same HEX:
--)))
--(((
--0x72403155615900640c6c19029200 where:
--)))
++**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
--* (((
--Device ID: 0x724031556159 = 724031556159
--)))
--* (((
--Version: 0x0064=100=1.0.0
--)))
++**where:**
--* (((
--BAT: 0x0c6c = 3180 mV = 3.180V
--)))
--* (((
--Signal: 0x19 = 25
--)))
--* (((
--Distance: 0x0292= 658 mm
--)))
--* (((
--Interrupt: 0x00 = 0
--)))
++* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
++* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
--== 2.4  Payload Explanation and Sensor Interface ==
++* (% style="color:#037691" %)**BAT:**(%%)       0x0cf4 = 3316 mV = 3.316V
++* (% style="color:#037691" %)**Singal:**(%%)   0x1e = 30
++* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
++
++* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
++
++* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
++
++* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
++
++* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
++
++* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
++
++== 2.4  Payload Explanation and Sensor Interface ==
++
  === 2.4.1  Device ID ===
++
  (((
  By default, the Device ID equal to the last 6 bytes of IMEI.
  )))
@@ -355,10 +355,12 @@
  (((
  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
++
++
  )))
  (((
--**Example:**
++(% style="color:blue" %)**Example :**
  )))
  (((
@@ -366,13 +366,25 @@
  )))
  (((
--The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
++The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
  )))
++(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
++(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
++
++User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
++
++
++(% style="color:blue" %)**Example :**
++
++AT+DEUI=868411056754138
++
++
  === 2.4.2  Version Info ===
++
  (((
  Specify the software version: 0x64=100, means firmware version 1.00.
  )))
@@ -382,12 +382,8 @@
  )))
--
  === 2.4.3  Battery Info ===
--(((
--Check the battery voltage for LSE01.
--)))
  (((
  Ex1: 0x0B45 = 2885mV
@@ -398,9 +398,9 @@
  )))
--
  === 2.4.4  Signal Strength ===
++
  (((
  NB-IoT Network signal Strength.
  )))
@@ -430,12 +430,14 @@
  )))
++=== 2.4.5  Distance ===
--=== 2.4.5  Soil Moisture ===
  Get the distance. Flat object range 280mm - 7500mm.
++(((
  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
++)))
  (((
  (((
@@ -447,12 +447,9 @@
  )))
--(((
--
--)))
--
  === 2.4.6  Digital Interrupt ===
++
  (((
  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.
  )))
@@ -462,7 +462,7 @@
  )))
  (((
--(% 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]])**.**
++(% 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]])**.**
  )))
@@ -484,9 +484,9 @@
  )))
--
  === 2.4.7  +5V Output ===
++
  (((
  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
  )))
@@ -494,10 +494,14 @@
  (((
  The 5V output time can be controlled by AT Command.
++
++
  )))
  (((
  (% style="color:blue" %)**AT+5VT=1000**
++
++
  )))
  (((
@@ -505,9 +505,9 @@
  )))
--
  == 2.5  Downlink Payload ==
++
  By default, NDDS75 prints the downlink payload to console port.
  [[image:image-20220709100028-1.png]]
@@ -557,213 +557,195 @@
  )))
++== 2.6  Distance alarm function(Since firmware v1.3.2) ==
--== 2.6  LED Indicator ==
++(% style="color:blue" %)** ➢ AT Command:**
--The NDDS75 has an internal LED which is to show the status of different state.
++(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
++² When min=0, and max≠0, Alarm higher than max
--* 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)
--* Then the LED will be on for 1 second means device is boot normally.
--* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
--* For each uplink probe, LED will be on for 500ms.
++² When min≠0, and max=0, Alarm lower than min
--(((
--
--)))
++² When min≠0 and max≠0, Alarm higher than max or lower than min
++(% style="color:blue" %)** Example:**
--== 2.7  Firmware Change Log ==
++**AT+ LDDSALARM=260,2000**    ~/~/ Alarm when distance lower than 260.
--Download URL & Firmware Change log
++== 2.7  Set the number of data to be uploaded and the recording time ==
--(((
--[[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/]]
--)))
++(% style="color:blue" %)** ➢ AT Command:**
--Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++* (% style="color:#037691" %)** AT+TR=900** (%%)                ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
++* (% style="color:#037691" %)** AT+NOUD=8**             (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
++ The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
++[[image:image-20221009001114-1.png||height="687" width="955"]]
--== 2.9  Battery Analysis ==
--=== 2.9.1  Battery Type ===
++== 2.8  Read or Clear cached data ==
--(((
--The NSE01 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.
--)))
++(% style="color:blue" %)** ➢ AT Command:**
++* (% style="color:#037691" %)** AT+CDP **  (%%)           ~/~/  Read cached data
++* (% style="color:#037691" %)** AT+CDP=0**  (%%)       ~/~/  Clear cached data
--(((
--The battery is designed to last for several years depends on the actually use environment and update interval.
--)))
++[[image:image-20220908175333-2.png]]
--(((
--The battery related documents as below:
--)))
++== 2.9  LED Indicator ==
--* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
--* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
--* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
--(((
--[[image:image-20220708140453-6.png]]
--)))
++The NDDS75 has an internal LED which is to show the status of different state.
++* 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)
++* Then the LED will be on for 1 second means device is boot normally.
++* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
++* For each uplink probe, LED will be on for 500ms.
--=== 2.9.2  Power consumption Analyze ===
--
  (((
--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.
++
  )))
--(((
--Instruction to use as below:
--)))
++== 2.10  Firmware Change Log ==
--(((
--(% 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/]]
--)))
--
  (((
--(% style="color:blue" %)**Step 2: **(%%) Open it and choose
++Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
  )))
--* (((
--Product Model
--)))
--* (((
--Uplink Interval
--)))
--* (((
--Working Mode
--)))
--
  (((
--And the Life expectation in difference case will be shown on the right.
++Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
  )))
--[[image:image-20220708141352-7.jpeg]]
++== 2.11  Battery & Power Consumption ==
--=== 2.9.3  Battery Note ===
++NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
--(((
--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.
--)))
++[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
++= 3.  Access NB-IoT Module =
--=== 2.9.4  Replace the battery ===
  (((
--The default battery pack of NSE01 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).
--)))
--
--
--
--= 3.  Access NB-IoT Module =
--
--(((
  Users can directly access the AT command set of the NB-IoT module.
  )))
  (((
  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
++
++
  )))
--[[image:1657261278785-153.png]]
++[[image:1657333200519-600.png]]
--
  = 4.  Using the AT Commands =
  == 4.1  Access AT Commands ==
--See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
++See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
--AT+<CMD>?                    : Help on <CMD>
--AT+<CMD>                      : Run <CMD>
++AT+<CMD>?                    :   Help on <CMD>
--AT+<CMD>=<value>      : Set the value
++AT+<CMD>                      :   Run <CMD>
--AT+<CMD>=?                  : Get the value
++AT+<CMD>=<value>      :   Set the value
++AT+<CMD>=?                  :   Get the value
++
  (% style="color:#037691" %)**General Commands**(%%)
--AT                            : Attention
++AT                            :   Attention
--AT?                           : Short Help
++AT?                           :  Short Help
--ATZ                          : MCU Reset
++ATZ                          :   MCU Reset
--AT+TDC                   : Application Data Transmission Interval
++AT+TDC                   :   Application Data Transmission Interval
--AT+CFG                   : Print all configurations
++AT+CFG                   :   Print all configurations
--AT+CFGMOD           : Working mode selection
++AT+CFGMOD           :   Working mode selection
--AT+INTMOD            : Set the trigger interrupt mode
++AT+INTMOD            :   Set the trigger interrupt mode
--AT+5VT                     : Set extend the time of 5V power
++AT+5VT                     :  Set extend the time of 5V power
--AT+PRO                    : Choose agreement
++AT+PRO                    :   Choose agreement
--AT+WEIGRE              : Get weight or set weight to 0
++AT+WEIGRE              :   Get weight or set weight to 0
--AT+WEIGAP              : Get or Set the GapValue of weight
++AT+WEIGAP              :   Get or Set the GapValue of weight
--AT+RXDL                   : Extend the sending and receiving time
++AT+RXDL                   :   Extend the sending and receiving time
--AT+CNTFAC              : Get or set counting parameters
++AT+CNTFAC              :   Get or set counting parameters
--AT+SERVADDR          : Server Address
++AT+SERVADDR         :   Server Address
++AT+TR               :  Get or Set record time"
++AT+APN            :  Get or set the APN
++
++AT+FBAND       :  Get or Set whether to automatically modify the frequency band
++
++AT+DNSCFG     :  Get or Set DNS Server
++
++AT+GETSENSORVALUE   :   Returns the current sensor measurement
++
++AT+NOUD  :     Get or Set the number of data to be uploaded
++
++AT+CDP     :      Read or Clear cached data
++
++AT+LDDSALARM :   Get or Set alarm of distance
++
++
  (% style="color:#037691" %)**COAP Management**
--AT+URI            : Resource parameters
++AT+URI            :   Resource parameters
  (% style="color:#037691" %)**UDP Management**
--AT+CFM          : Upload confirmation mode (only valid for UDP)
++AT+CFM          :   Upload confirmation mode (only valid for UDP)
  (% style="color:#037691" %)**MQTT Management**
--AT+CLIENT               : Get or Set MQTT client
++AT+CLIENT         :   Get or Set MQTT client
--AT+UNAME             : Get or Set MQTT Username
++AT+UNAME        :   Get or Set MQTT Username
--AT+PWD                  : Get or Set MQTT password
++AT+PWD             :   Get or Set MQTT password
--AT+PUBTOPIC          : Get or Set MQTT publish topic
++AT+PUBTOPIC     :   Get or Set MQTT publish topic
--AT+SUBTOPIC          : Get or Set MQTT subscription topic
++AT+SUBTOPIC     :   Get or Set MQTT subscription topic
  (% style="color:#037691" %)**Information**
--AT+FDR              : Factory Data Reset
++AT+FDR              :   Factory Data Reset
--AT+PWORD       : Serial Access Password
++AT+PWORD       :   Serial Access Password
--
  = 5.  FAQ =
  == 5.1  How to Upgrade Firmware ==
@@ -778,18 +778,10 @@
  )))
  (((
--(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
++(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
  )))
--
--== 5.2  Can I calibrate NSE01 to different soil types? ==
--
--(((
--NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
--)))
--
--
  = 6.  Trouble Shooting =
  == 6.1  Connection problem when uploading firmware ==
@@ -804,27 +804,26 @@
  )))
--
  == 6.2  AT Command input doesn't work ==
++
  (((
  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
--
--
  )))
--= 7.  Order Info =
++== 6.3  Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
--Part Number**:** (% style="color:#4f81bd" %)**NSE01**
++This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
--(% class="wikigeneratedid" %)
--(((
--
--)))
++= 7.  Order Info =
++
++Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++
++
  = 8.  Packing Info =
  (((
@@ -832,7 +832,7 @@
  (% style="color:#037691" %)**Package Includes**:
--* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
++* NDDS75 NB-IoT Distance Detect Sensor Node x 1
  * External antenna x 1
  )))
@@ -841,18 +841,21 @@
  (% style="color:#037691" %)**Dimension and weight**:
--* Size: 195 x 125 x 55 mm
--* Weight:   420g
++* Device Size: 13.0 x 5 x 4.5 cm
++* Device Weight: 150g
++* Package Size / pcs : 15 x 12x 5.5 cm
++* Weight / pcs : 220g
  )))
  (((
--
  )))
  = 9.  Support =
++
  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
++
  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]

image-20220709110451-3.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Xiaoling

Size

...	...	@@ -1,0 +1,1 @@
	1	+611.5 KB

Content

image-20220908175246-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+55.7 KB

Content

image-20220908175333-2.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.David

Size

...	...	@@ -1,0 +1,1 @@
	1	+31.1 KB

Content

image-20221009001114-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Edwin

Size

...	...	@@ -1,0 +1,1 @@
	1	+282.9 KB

Content