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

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

From version < 110.1 >

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

To version < 108.9 >

edited by Xiaoling
on 2023/04/04 12:01

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.Xiaoling

Content

@@ -1,5 +3,3 @@
--
--
  (% style="text-align:center" %)
  [[image:image-20220709085040-1.png||height="542" width="524"]]
@@ -18,6 +18,7 @@
  = 1.  Introduction =
++
  == 1.1  What is NDDS75 Distance Detection Sensor ==
  (((
@@ -55,6 +55,7 @@
  [[image:1657327959271-447.png]]
++
  == 1.2  Features ==
@@ -71,6 +71,7 @@
  * Micro SIM card slot for NB-IoT SIM
  * 8500mAh Battery for long term use
++
  == 1.3  Specification ==
@@ -101,6 +101,7 @@
  * STOP Mode: 10uA @ 3.3v
  * Max transmit power: 350mA@3.3v
++
  == 1.4  Applications ==
@@ -115,6 +115,7 @@
++
  == 1.5  Pin Definitions ==
@@ -121,8 +121,10 @@
  [[image:1657328609906-564.png]]
++
  = 2.  Use NDDS75 to communicate with IoT Server =
++
  == 2.1  How it works ==
@@ -145,8 +145,10 @@
  )))
++
  == 2.2  Configure the NDDS75 ==
++
  === 2.2.1  Test Requirement ===
@@ -166,6 +166,7 @@
  [[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]]
++
  === 2.2.3  Connect USB – TTL to NDDS75 to configure it ===
@@ -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
++
  )))
@@ -252,18 +252,23 @@
  [[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
  [[image:1657330501006-241.png]]
@@ -271,6 +271,7 @@
  [[image:1657330533775-472.png]]
++
  === 2.2.6  Use MQTT protocol to uplink data ===
@@ -293,6 +293,7 @@
  )))
++
  === 2.2.7  Use TCP protocol to uplink data ===
@@ -305,6 +305,7 @@
  [[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,18 +325,20 @@
  (% 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.
@@ -346,6 +346,7 @@
  [[image:1657331036973-987.png]]
++
  The payload is **ASCII** string, representative same HEX:
  (% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
@@ -364,6 +364,7 @@
  * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
++
  === 2.3.2  Since firmware v1.3.2 ===
@@ -371,9 +371,9 @@
  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="1" style="background-color:#ffffcc; color:green; width:490px" %)
++|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**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.
@@ -408,6 +408,7 @@
  == 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 ==
@@ -655,6 +655,7 @@
  [[image:image-20221009001114-1.png||height="687" width="955"]]
++
  == 2.8  Read or Clear cached data ==
@@ -666,6 +666,7 @@
  [[image:image-20220908175333-2.png]]
++
  == 2.9  LED Indicator ==
@@ -682,6 +682,7 @@
  )))
++
  == 2.10  Firmware Change Log ==
@@ -690,18 +690,22 @@
  )))
  (((
++
++)))
++
++(((
  Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
  )))
++
  == 2.11  Battery & Power Consumption ==
--NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
++PS-LB-NA 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/]] .
--
  = 3.  Access NB-IoT Module =
@@ -718,8 +718,10 @@
  [[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,37 +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? ==
--
--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||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 =
@@ -877,6 +877,11 @@
  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++(% class="wikigeneratedid" %)
++(((
++
++)))
++
  = 8.  Packing Info =
  (((
@@ -891,6 +891,7 @@
  (((
++
  (% style="color:#037691" %)**Dimension and weight**:
  * Device Size: 13.0 x 5 x 4.5 cm
@@ -902,6 +902,7 @@
  (((
++
  )))
@@ -909,5 +909,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