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

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

From version < 111.1

edited by Bei Jinggeng
on 2024/05/31 09:53

To version < 108.1 >

edited by Edwin Chen
on 2022/10/09 00:11

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (3 modified, 0 added, 0 removed)

Details

Page properties

Title

@@ -1,1 +1,1 @@
--NDDS75 -- NB-IoT Distance Detect Sensor User Manual
++NDDS75 NB-IoT Distance Detect Sensor User Manual

Author

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

Content

@@ -1,7 +3,5 @@
--
--
  (% style="text-align:center" %)
--[[image:image-20220709085040-1.png||_mstalt="429481" height="542" width="524"]]
++[[image:image-20220709085040-1.png||height="542" width="524"]]
@@ -18,6 +18,7 @@
  = 1.  Introduction =
++
  == 1.1  What is NDDS75 Distance Detection Sensor ==
  (((
@@ -52,9 +52,10 @@
  )))
--[[image:1657327959271-447.png||_mstalt="297700"]]
++[[image:1657327959271-447.png]]
++
  == 1.2  Features ==
@@ -81,12 +81,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:**
@@ -115,14 +115,18 @@
++
++
  == 1.5  Pin Definitions ==
--[[image:1657328609906-564.png||_mstalt="297440"]]
++[[image:1657328609906-564.png]]
++
  = 2.  Use NDDS75 to communicate with IoT Server =
++
  == 2.1  How it works ==
@@ -139,14 +139,16 @@
  )))
--[[image:1657328659945-416.png||_mstalt="297999"]]
++[[image:1657328659945-416.png]]
  (((
  )))
++
  == 2.2  Configure the NDDS75 ==
++
  === 2.2.1  Test Requirement ===
@@ -163,9 +163,10 @@
  )))
--[[image:1657328756309-230.png||_mstalt="294515"]]
++[[image:1657328756309-230.png]]
++
  === 2.2.2  Insert SIM card ===
@@ -177,9 +177,11 @@
  User need to take out the NB-IoT module and insert the SIM card like below:
  )))
--[[image:1657328884227-504.png||_mstalt="295776"]]
++[[image:1657328884227-504.png]]
++
++
  === 2.2.3  Connect USB – TTL to NDDS75 to configure it ===
@@ -189,7 +189,7 @@
  )))
  )))
--[[image:image-20220709092052-2.png||_mstalt="430235"]]
++[[image:image-20220709092052-2.png]]
  (% style="color:blue" %)**Connection:**
@@ -213,7 +213,7 @@
  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.
  )))
--[[image:1657329814315-101.png||_mstalt="292084"]]
++[[image:1657329814315-101.png]]
  (((
@@ -221,6 +221,7 @@
  )))
++
  === 2.2.4  Use CoAP protocol to uplink data ===
@@ -240,6 +240,7 @@
  * (((
  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/  Set COAP resource path
++
  )))
@@ -249,28 +249,34 @@
  )))
--[[image:1657330452568-615.png||_mstalt="295555"]]
++[[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||_mstalt="299481"]]
++[[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
--[[image:1657330501006-241.png||_mstalt="290121"]]
++[[image:1657330501006-241.png]]
--[[image:1657330533775-472.png||_mstalt="295763"]]
++[[image:1657330533775-472.png]]
++
  === 2.2.6  Use MQTT protocol to uplink data ===
@@ -282,10 +282,10 @@
  * (% 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||_mstalt="299377"]]
++[[image:1657249978444-674.png]]
--[[image:1657330723006-866.png||_mstalt="294996"]]
++[[image:1657330723006-866.png]]
  (((
@@ -293,6 +293,7 @@
  )))
++
  === 2.2.7  Use TCP protocol to uplink data ===
@@ -299,12 +299,13 @@
  * (% 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||_mstalt="433706"]]
++[[image:image-20220709093918-1.png]]
--[[image:image-20220709093918-2.png||_mstalt="434070"]]
++[[image:image-20220709093918-2.png]]
++
  === 2.2.8  Change Update Interval ===
@@ -315,6 +315,7 @@
  (((
++
  (% style="color:red" %)**NOTE:**
  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
@@ -325,89 +325,96 @@
  (% 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 ==
++
  === 2.3.1  Before Firmware v1.3.2 ===
  In this mode, uplink payload includes in total 14 bytes
--(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
--|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
++|=(% style="width: 60px;" %)(((
  **Size(bytes)**
--)))|=(% style="width: 61px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**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"]]
++)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**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 NDDS75 uplink data.
++If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
  )))
--[[image:1657331036973-987.png||_mstalt="298740"]]
++[[image:1657331036973-987.png]]
++(((
  The payload is **ASCII** string, representative same HEX:
++)))
--(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
++(((
++0x72403155615900640c6c19029200 where:
++)))
--**where :**
++* (((
++Device ID: 0x724031556159 = 724031556159
++)))
++* (((
++Version:    0x0064=100=1.0.0
++)))
--* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
++* (((
++BAT:     0x0c6c = 3180 mV = 3.180V
++)))
++* (((
++Signal: 0x19 = 25
++)))
++* (((
++Distance: 0x0292= 658 mm
++)))
++* (((
++Interrupt: 0x00 = 0
--* (% 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** ===
--=== 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" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
--|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:25px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:70px" %)**4**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:65px" %)**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.......
++(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
++|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)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||_mstalt="432328"]]
++[[image:image-20220908175246-1.png]]
  The payload is ASCII string, representative same HEX:
--**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 (%%)**
++0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
--**where:**
++* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
++* (% style="color:red" %)Version: 0x0084=132=1.3.2
++* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
++* (% style="color:blue" %)Singal: 0x1e = 30
++* (% style="color:red" %)Mod: 0x01 = 1
++* Interrupt: 0x00= 0
++* Distance: 0x0039= 57 = 57
++* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
++* Distance,Time stamp : 00396319baf0
++* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
--* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
--
--* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
--
--* (% 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
--
--* (% _mstmutation="1" style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/||_mstmutation="1"]])
--
--* (% 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 ===
@@ -446,6 +446,7 @@
  AT+DEUI=868411056754138
++
  === 2.4.2  Version Info ===
@@ -458,6 +458,7 @@
  )))
++
  === 2.4.3  Battery Info ===
@@ -470,6 +470,7 @@
  )))
++
  === 2.4.4  Signal Strength ===
@@ -502,6 +502,7 @@
  )))
++
  === 2.4.5  Distance ===
@@ -508,13 +508,23 @@
  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(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
++For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
  )))
  (((
++(((
++(% style="color:blue" %)**                                                        0B05(H) = 2821(D) = 2821mm.**
++)))
++)))
++
++(((
  )))
++(((
++
++)))
++
  === 2.4.6  Digital Interrupt ===
@@ -535,8 +535,9 @@
  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.
  )))
++
  (((
--**Example:**
++Example:
  )))
  (((
@@ -548,6 +548,7 @@
  )))
++
  === 2.4.7  +5V Output ===
@@ -555,12 +555,17 @@
  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
  )))
++
  (((
  The 5V output time can be controlled by AT Command.
++
++
  )))
  (((
  (% style="color:blue" %)**AT+5VT=1000**
++
++
  )))
  (((
@@ -568,17 +568,15 @@
  )))
++
  == 2.5  Downlink Payload ==
  By default, NDDS75 prints the downlink payload to console port.
--(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
--|(% style="background-color:#4f81bd; color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:56px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:151px" %)**Downlink payload size(bytes)**
--|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
--|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
--|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
++[[image:image-20220709100028-1.png]]
++
  (((
  (% style="color:blue" %)**Examples:**
  )))
@@ -623,6 +623,7 @@
  )))
++
  == 2.6  Distance alarm function(Since firmware v1.3.2) ==
@@ -642,6 +642,7 @@
  **AT+ LDDSALARM=260,2000**    ~/~/ Alarm when distance lower than 260.
++
  == 2.7  Set the number of data to be uploaded and the recording time ==
@@ -652,9 +652,10 @@
   The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
--[[image:image-20221009001114-1.png||_mstalt="425269" height="687" width="955"]]
++[[image:image-20221009001114-1.png||height="687" width="955"]]
++
  == 2.8  Read or Clear cached data ==
@@ -663,9 +663,10 @@
  * (% style="color:#037691" %)** AT+CDP **  (%%)           ~/~/  Read cached data
  * (% style="color:#037691" %)** AT+CDP=0**  (%%)       ~/~/  Clear cached data
--[[image:image-20220908175333-2.png||_mstalt="431665"]]
++[[image:image-20220908175333-2.png]]
++
  == 2.9  LED Indicator ==
@@ -682,6 +682,7 @@
  )))
++
  == 2.10  Firmware Change Log ==
@@ -690,18 +690,100 @@
  )))
  (((
++
++)))
++
++(((
  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
  )))
--== 2.11  Battery & Power Consumption ==
++== 2.11  Battery Analysis ==
--NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
--[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
++=== 2.11.1  Battery Type ===
++(((
++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.
++)))
++
++(((
++The battery is designed to last for several years depends on the actually use environment and update interval.
++)))
++
++(((
++The battery related documents as below:
++)))
++
++* [[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-20220709101450-2.png]]
++)))
++
++
++
++=== 2.11.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:
++)))
++
++(((
++(% 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
++)))
++
++* (((
++Product Model
++)))
++* (((
++Uplink Interval
++)))
++* (((
++Working Mode
++)))
++
++(((
++And the Life expectation in difference case will be shown on the right.
++)))
++
++[[image:image-20220709110451-3.png]]
++
++
++
++=== 2.11.3  Battery Note ===
++
++
++(((
++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.
++)))
++
++
++
++=== 2.11.4  Replace the battery ===
++
++
++(((
++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).
++)))
++
++
++
  = 3.  Access NB-IoT Module =
@@ -710,16 +710,18 @@
  )))
  (((
--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/||_mstmutation="1"]]
++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:1657333200519-600.png||_mstalt="291603"]]
++[[image:1657333200519-600.png]]
++
  = 4.  Using the AT Commands =
++
  == 4.1  Access AT Commands ==
@@ -787,7 +787,11 @@
  AT+URI            :   Resource parameters
++(% style="color:#037691" %)**UDP Management**
++AT+CFM          :   Upload confirmation mode (only valid for UDP)
++
++
  (% style="color:#037691" %)**MQTT Management**
  AT+CLIENT         :   Get or Set MQTT client
@@ -808,8 +808,10 @@
  AT+PWORD       :   Serial Access Password
++
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -826,8 +826,10 @@
  )))
++
  = 6.  Trouble Shooting =
++
  == 6.1  Connection problem when uploading firmware ==
@@ -840,41 +840,17 @@
  )))
++
  == 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.
++
++
  )))
--== 6.3  Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
--
--
--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]]//**.
--
--
--== 6.4 Why does the DDS75 sensor keep flashing blue? ==
--
--This is caused by the incompatibility between the latest firmware and the hardware.
--
--Please check your hardware production date
--
--The first two digits are the week of the year, and the last two digits are the year.
--
--The number 3322 is the first batch we changed the power IC.
--
--As shown below:
--
-- [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20240531090837-1.png?rev=1.1||_mstalt="431418" alt="image-20240531090837-1.png"]]
--
--Have you updated the Lora ST's firmware? Please send downline 26 01 to check the version number.
--
--If it is v1.4.1 version, please modify a value according to the above four digits, the AT command is AT+POWERIC. The date after 3322 is AT+POWERIC=1, and the date before it is AT+POWERIC=0.
--
--Downlink is FF 01(AT+POWERIC=1);FF 00(AT+POWERIC=0).
--
--
  = 7.  Order Info =
@@ -881,6 +881,11 @@
  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++(% class="wikigeneratedid" %)
++(((
++
++)))
++
  = 8.  Packing Info =
  (((
@@ -895,6 +895,7 @@
  (((
++
  (% style="color:#037691" %)**Dimension and weight**:
  * Device Size: 13.0 x 5 x 4.5 cm
@@ -906,6 +906,7 @@
  (((
++
  )))
@@ -913,5 +913,4 @@
  * 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]]

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

Summary

Details

Applications

Navigation