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

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

From version < 108.22 >

edited by Xiaoling
on 2023/12/14 17:30

To version < 108.7 >

edited by Xiaoling
on 2022/10/26 09:45

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (2 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

Content

@@ -16,6 +16,7 @@
  = 1.  Introduction =
++
  == 1.1  What is NDDS75 Distance Detection Sensor ==
  (((
@@ -53,6 +53,7 @@
  [[image:1657327959271-447.png]]
++
  == 1.2  Features ==
@@ -70,6 +70,7 @@
  * 8500mAh Battery for long term use
++
  == 1.3  Specification ==
@@ -80,12 +80,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:**
@@ -101,6 +101,7 @@
  * 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 ===
@@ -181,6 +181,7 @@
  [[image:1657328884227-504.png]]
++
  === 2.2.3  Connect USB – TTL to NDDS75 to configure it ===
@@ -222,6 +222,7 @@
  )))
++
  === 2.2.4  Use CoAP protocol to uplink data ===
@@ -241,6 +241,7 @@
  * (((
  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%)      ~/~/  Set COAP resource path
++
  )))
@@ -263,6 +263,7 @@
  [[image:1657330472797-498.png]]
++
  === 2.2.5  Use UDP protocol to uplink data(Default protocol) ===
@@ -276,6 +276,7 @@
  [[image:1657330533775-472.png]]
++
  === 2.2.6  Use MQTT protocol to uplink data ===
@@ -298,6 +298,7 @@
  )))
++
  === 2.2.7  Use TCP protocol to uplink data ===
@@ -310,6 +310,7 @@
  [[image:image-20220709093918-2.png]]
++
  === 2.2.8  Change Update Interval ===
@@ -320,6 +320,7 @@
  (((
++
  (% style="color:red" %)**NOTE:**
  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
@@ -330,21 +330,23 @@
  (% 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="4" style="background-color:#f2f2f2; width:440px" %)
--|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)(((
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
++|=(% style="width: 60px;" %)(((
  **Size(bytes)**
--)))|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 82px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 102px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
++)))|=(% 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.
  )))
@@ -351,6 +351,7 @@
  [[image:1657331036973-987.png]]
++
  The payload is **ASCII** string, representative same HEX:
  (% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
@@ -370,6 +370,7 @@
  * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
++
  === 2.3.2  Since firmware v1.3.2 ===
@@ -377,9 +377,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="5" style="background-color:#f2f2f2; width:490px" %)
--|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; 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.......
++(% 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.
@@ -400,7 +400,7 @@
  * (% style="color:#037691" %)**Singal:**(%%)   0x1e = 30
--* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
++* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
  * (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
@@ -413,8 +413,10 @@
  * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
++
  == 2.4  Payload Explanation and Sensor Interface ==
++
  === 2.4.1  Device ID ===
@@ -453,6 +453,7 @@
  AT+DEUI=868411056754138
++
  === 2.4.2  Version Info ===
@@ -465,6 +465,7 @@
  )))
++
  === 2.4.3  Battery Info ===
@@ -477,6 +477,7 @@
  )))
++
  === 2.4.4  Signal Strength ===
@@ -509,6 +509,7 @@
  )))
++
  === 2.4.5  Distance ===
@@ -515,13 +515,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 ===
@@ -542,8 +542,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:
  )))
  (((
@@ -555,6 +555,7 @@
  )))
++
  === 2.4.7  +5V Output ===
@@ -562,12 +562,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**
++
++
  )))
  (((
@@ -575,17 +575,15 @@
  )))
++
  == 2.5  Downlink Payload ==
  By default, NDDS75 prints the downlink payload to console port.
--(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
--|(% style="background-color:#d9e2f3; color:#0070c0; width:208px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:56px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**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:**
  )))
@@ -630,6 +630,7 @@
  )))
++
  == 2.6  Distance alarm function(Since firmware v1.3.2) ==
@@ -649,6 +649,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 ==
@@ -662,6 +662,7 @@
  [[image:image-20221009001114-1.png||height="687" width="955"]]
++
  == 2.8  Read or Clear cached data ==
@@ -673,6 +673,7 @@
  [[image:image-20220908175333-2.png]]
++
  == 2.9  LED Indicator ==
@@ -689,6 +689,7 @@
  )))
++
  == 2.10  Firmware Change Log ==
@@ -697,18 +697,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 =
@@ -725,8 +725,10 @@
  [[image:1657333200519-600.png]]
++
  = 4.  Using the AT Commands =
++
  == 4.1  Access AT Commands ==
@@ -819,8 +819,10 @@
  AT+PWORD       :   Serial Access Password
++
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -837,8 +837,10 @@
  )))
++
  = 6.  Trouble Shooting =
++
  == 6.1  Connection problem when uploading firmware ==
@@ -851,20 +851,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]]//**.
--
--
  = 7.  Order Info =
@@ -871,6 +871,11 @@
  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
++(% class="wikigeneratedid" %)
++(((
++
++)))
++
  = 8.  Packing Info =
  (((
@@ -885,6 +885,7 @@
  (((
++
  (% style="color:#037691" %)**Dimension and weight**:
  * Device Size: 13.0 x 5 x 4.5 cm
@@ -896,6 +896,7 @@
  (((
++
  )))
@@ -903,5 +903,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