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

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

From version < 97.13 >

edited by Xiaoling
on 2022/07/09 11:36

To version < 104.6 >

edited by Xiaoling
on 2022/09/09 13:35

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)
Attachments (0 modified, 2 added, 0 removed)
- image-20220908175246-1.png
- image-20220908175333-2.png

Details

Page properties

Content

@@ -16,6 +16,7 @@
  = 1.  Introduction =
++
  == 1.1  What is NDDS75 Distance Detection Sensor ==
  (((
@@ -22,23 +22,30 @@
  (((
++(((
  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.
  )))
++)))
  )))
@@ -64,6 +64,9 @@
  * 8500mAh Battery for long term use
++
++
++
  == 1.3  Specification ==
@@ -95,8 +95,12 @@
  * Max transmit power: 350mA@3.3v
++
++
++
  == 1.4  Applications ==
++
  * Smart Buildings & Home Automation
  * Logistics and Supply Chain Management
  * Smart Metering
@@ -108,6 +108,8 @@
++
++
  == 1.5  Pin Definitions ==
@@ -117,8 +117,10 @@
  = 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.
  )))
@@ -144,16 +144,17 @@
  === 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.
  )))
@@ -163,6 +163,7 @@
  === 2.2.2  Insert SIM card ===
++
  (((
  Insert the NB-IoT Card get from your provider.
  )))
@@ -178,6 +178,7 @@
  === 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.
@@ -186,6 +186,7 @@
  [[image:image-20220709092052-2.png]]
++
  **Connection:**
   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
@@ -209,8 +209,9 @@
  [[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]]**
  )))
@@ -217,9 +217,10 @@
  === 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:**
  )))
@@ -232,17 +232,25 @@
  )))
  * (((
  (% 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]]
@@ -301,29 +301,38 @@
  === 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: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 1.3.2 ===
--(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
++
++In this mode, uplink payload includes in total 14 bytes
++
++(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
  |=(% style="width: 60px;" %)(((
  **Size(bytes)**
--)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 60px;" %)**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"]]
  (((
@@ -333,8 +333,9 @@
  [[image:1657331036973-987.png]]
++
  (((
--The payload is ASCII string, representative same HEX:
++The payload is **ASCII** string, representative same HEX:
  )))
  (((
@@ -345,11 +345,11 @@
  Device ID: 0x724031556159 = 724031556159
  )))
  * (((
--Version: 0x0064=100=1.0.0
++Version:    0x0064=100=1.0.0
  )))
  * (((
--BAT: 0x0c6c = 3180 mV = 3.180V
++BAT:     0x0c6c = 3180 mV = 3.180V
  )))
  * (((
  Signal: 0x19 = 25
@@ -362,14 +362,51 @@
++
  )))
++=== **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="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]]
++
++
++The payload is ASCII string, representative same HEX:
++
++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:
++
++* (% 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**//,.......
++
++
++
++
++
  == 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.
  )))
@@ -376,10 +376,12 @@
  (((
  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
++
++
  )))
  (((
--**Example:**
++(% style="color:blue" %)**Example :**
  )))
  (((
@@ -387,13 +387,26 @@
  )))
  (((
--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.
  )))
@@ -406,6 +406,7 @@
  === 2.4.3  Battery Info ===
++
  (((
  Ex1: 0x0B45 = 2885mV
  )))
@@ -418,6 +418,7 @@
  === 2.4.4  Signal Strength ===
++
  (((
  NB-IoT Network signal Strength.
  )))
@@ -450,9 +450,12 @@
  === 2.4.5  Distance ===
++
  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
++)))
  (((
  (((
@@ -470,6 +470,7 @@
  === 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.
  )))
@@ -504,6 +504,7 @@
  === 2.4.7  +5V Output ===
++
  (((
  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling.
  )))
@@ -511,10 +511,14 @@
  (((
  The 5V output time can be controlled by AT Command.
++
++
  )))
  (((
  (% style="color:blue" %)**AT+5VT=1000**
++
++
  )))
  (((
@@ -525,6 +525,7 @@
  == 2.5  Downlink Payload ==
++
  By default, NDDS75 prints the downlink payload to console port.
  [[image:image-20220709100028-1.png]]
@@ -575,9 +575,54 @@
--== 2.6  LED Indicator ==
++== 2.6  Distance alarm function(Since firmware v1.3.2) ==
++(% style="color:blue" %)** ➢ AT Command:**
++
++(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
++
++² When min=0, and max≠0, Alarm higher than max
++
++² 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:**
++
++**AT+ LDDSALARM=260,2000**    ~/~/ Alarm when distance lower than 260.
++
++
++
++== 2.7  Set the number of data to be uploaded and the recording time ==
++
++
++(% style="color:blue" %)** ➢ AT Command:**
++
++* (% 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.
++
++
++
++
++== 2.8  Read or Clear cached data ==
++
++
++(% style="color:blue" %)** ➢ AT Command:**
++
++* (% style="color:#037691" %)** AT+CDP **  (%%)       ~/~/ Read cached data
++* (% style="color:#037691" %)** AT+CDP=0**  (%%)  ~/~/  Clear cached data
++
++
++
++[[image:image-20220908175333-2.png]]
++
++
++
++== 2.9  LED Indicator ==
++
++
  The NDDS75 has an internal LED which is to show the status of different state.
@@ -592,23 +592,27 @@
--== 2.7  Firmware Change Log ==
++== 2.10  Firmware Change Log ==
--Download URL & Firmware Change log
++(((
++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]]
++)))
  (((
--[[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/]]
++
  )))
++(((
++Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++)))
--Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
++== 2.11  Battery Analysis ==
--== 2.8  Battery Analysis ==
--=== 2.8.1  Battery Type ===
++=== 2.11.1  Battery Type ===
  (((
@@ -633,8 +633,9 @@
--=== 2.8.2  Power consumption Analyze ===
++=== 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.
  )))
@@ -671,8 +671,9 @@
--=== 2.8.3  Battery Note ===
++=== 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.
  )))
@@ -679,8 +679,9 @@
--=== 2.8.4  Replace the battery ===
++=== 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).
  )))
@@ -689,6 +689,7 @@
  = 3.  Access NB-IoT Module =
++
  (((
  Users can directly access the AT command set of the NB-IoT module.
  )))
@@ -695,6 +695,8 @@
  (((
  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]]
@@ -703,11 +703,13 @@
  = 4.  Using the AT Commands =
++
  == 4.1  Access AT Commands ==
--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/]]
++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>
@@ -747,7 +747,23 @@
  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
@@ -781,6 +781,7 @@
  = 5.  FAQ =
++
  == 5.1  How to Upgrade Firmware ==
@@ -793,7 +793,7 @@
  )))
  (((
--(% style="color:red" %)Notice, NDDS75 and LDDS75 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.**
  )))
@@ -800,6 +800,7 @@
  = 6.  Trouble Shooting =
++
  == 6.1  Connection problem when uploading firmware ==
@@ -815,6 +815,7 @@
  == 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.
@@ -840,7 +840,7 @@
  (% style="color:#037691" %)**Package Includes**:
--* NSE01 NB-IoT Distance Detect Sensor Node x 1
++* NDDS75 NB-IoT Distance Detect Sensor Node x 1
  * External antenna x 1
  )))
@@ -847,9 +847,9 @@
  (((
++
  (% style="color:#037691" %)**Dimension and weight**:
--
  * Device Size: 13.0 x 5 x 4.5 cm
  * Device Weight: 150g
  * Package Size / pcs : 15 x 12x 5.5 cm
@@ -865,5 +865,6 @@
  = 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-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

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

Summary

Details

Applications

Navigation