Manuals+

DDS75-NB -- NB-IoT Distance Detection Sensor User Manual

1. Introduction

The Dragino DDS75-NB is a NB-IoT Distance Detection Sensor designed for Internet of Things (IoT) solutions. It measures the distance between the sensor and a flat object using ultrasonic sensing technology. The sensor incorporates internal temperature compensation to enhance data reliability. The DDS75-NB is suitable for various applications including horizontal distance measurement, liquid level measurement, parking management systems, object proximity and presence detection, intelligent trash can management, robot obstacle avoidance, automatic control, sewer monitoring, and bottom water level monitoring.

The device detects the distance to a measured object and transmits this data to an IoT platform via the NB-IoT network. It supports multiple uplink methods such as MQTT, MQTTs, UDP, and TCP, and can connect to various IoT Servers. The DDS75-NB also features BLE configuration and Over-The-Air (OTA) firmware updates for user convenience. It is powered by a long-lasting 8500mAh Li-SOCl2 battery, designed for extended operational life, potentially up to several years. Optional built-in SIM card and pre-configured IoT server versions are available, simplifying setup.

1.1 What is DDS75-NB NB-IoT Distance Detection Sensor

The Dragino DDS75-NB is a NB-IoT Distance Detection Sensor for Internet of Things solution. It is used 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 DDS75-NB 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 sends data to an IoT platform via NB-IoT network. DDS75-NB supports different uplink methods including MQTT, MQTTs, UDP & TCP for different application requirements, and supports uplinks to various IoT Servers. DDS75-NB supports BLE configure and OTA update which make user easy to use. DDS75-NB is powered by 8500mAh Li-SOCl2 battery, it is designed for long-term use up to several years. DDS75-NB has optional built-in SIM card and default IoT server connection version. Which makes it works with simple configuration.

1.2 Features

1.3 Specification

Common DC Characteristics:

NB-IoT Spec:

Battery:

Power Consumption:

1.4 Rated environmental conditions

Item Minimum value Typical value Maximum value Unit Remarks
Storage temperature -25 25 80 °C
Storage humidity 65% 90% RH (1)
Operating temperature -15 25 60 °C
Working humidity 65% 80% RH (1)

Remarks: (1) a. When the ambient temperature is 0-39 °C, the maximum humidity is 90% (non-condensing); b. When the ambient temperature is 40-50 °C, the highest humidity is the highest humidity in the natural world at the current temperature (no condensation).

1.5 Effective measurement range Reference beam pattern

Test Object 1: A white cylindrical tube made of PVC, with a height of 100cm and a diameter of 7.5cm. The sensor's beam pattern is illustrated, showing the detection range and angle.

Test Object 2: A "corrugated cardboard box" perpendicular to the central axis of 0°, with dimensions of 60cm * 50cm. The sensor's beam pattern for this object is also illustrated.

1.6 Applications

1.7 Sleep mode and working mode

Deep Sleep Mode: In this mode, the sensor's NB-IoT is inactive. It is used for storage and shipping to conserve battery life.

Working Mode: The sensor operates as an NB-IoT device, joining the NB-IoT network and sending sensor data to a server. Between sampling/transmission periods, the sensor enters an IDLE mode, which consumes power similar to Deep Sleep mode.

1.8 Button & LEDs

The DDS75-NB features a push button and an LED indicator. The antenna is attachable, and there is a pressure balance valve.

Behavior on ACT Function Action

1~3s

Send an uplink

If the sensor is already attached to the NB-IoT network, it sends an uplink packet, and the blue LED blinks once. The BLE module becomes active, allowing users to connect via BLE for device configuration.

>3s

Active Device

The green LED blinks 5 times, indicating the device enters OTA mode for 3 seconds before attempting to attach to the NB-IoT network. Once active, the BLE module is available for configuration regardless of NB-IoT network attachment.

Note: When the device is executing a program, buttons may become invalid. It is best to press buttons after program execution is complete.

Pressing the button 5 times (x5) results in the red LED solid for 5 seconds, indicating the device is in Deep Sleep Mode.

1.9 BLE connection

DDS75-NB supports BLE for remote configuration and firmware updates. BLE can be used to configure sensor parameters or view console output. BLE is activated under the following conditions:

If there is no BLE activity for 60 seconds, the sensor will shut down the BLE module to enter low power mode.

1.10 Pin Definitions, Switch & SIM Direction

A diagram shows the circuit board layout with labels for various pins and connectors, including ISP, RUN, LED, Power Jumper, RESET, VBAT_OUT, BOARD_RX, BOARD_TX, GPIO_EXTI, SCL, SDA, ONE_WIRE, and GND. It also indicates UART_TXD, UART_RXD, NRST, SWCLK, and SWDIO.

1.10.1 Jumper JP2

This jumper enables device power-on when inserted.

1.10.2 BOOT MODE / SW1

  1. ISP: Upgrade mode. The device will not have any signal but is ready for firmware upgrades. The LED will not work, and firmware will not run.
  2. Flash: Work mode. The device starts operating and sends console output for further debugging.

1.10.3 Reset Button

Press this button to reboot the device.

1.10.4 SIM Card Direction

Refer to the link: How to insert SIM Card for guidance on SIM card insertion.

1.11 Mechanical

Mechanical drawings provide detailed dimensions for the sensor probe and the main unit, showing views from different angles with measurements in millimeters.

2. Use DDS75-NB to communicate with IoT Server

The DDS75-NB is equipped with an NB-IoT module and pre-loaded firmware to collect environmental data from sensors. This data is sent to a local NB-IoT network, which then forwards it to an IoT server using the protocol defined by the DDS75-NB. The network structure is illustrated.

Two versions are available: -GE and -1T.

The document provides a glance at the results of different servers:

Servers Dash Board Comments
Node-Red ?

Screenshots of Node-Red dashboards showing SHT-TEMP, SHT-HUM, DSTEMP data.
DataCake ?

Screenshots of DataCake dashboards showing Humidity, Temperature, Battery, and Signal data.
Tago.IO ? Raw Payload. Need Developer to design Dash Board
General UDP Raw Payload. Need Developer to design Dash Board
General MQTT Raw Payload. Need Developer to design Dash Board
ThingSpeak ?

Screenshots of ThingSpeak charts displaying Temperature and Humidity data.
ThingsBoard ?

Screenshots of ThingsBoard dashboards showing temperature and humidity gauges.

2.2 Payload Types

To meet diverse server requirements, DDS75-NB supports various payload types:

Users can specify the payload type when choosing the connection protocol. Examples include:

2.2.1 General Json Format(Type=5)

This is the General Json Format:

{
  "IMEI": "863663062798914",
  "IMSI": "460083513507314",
  "Model": "DDS75-NB",
  "distance": 1752,
  "interrupt": 0,
  "interrupt_level": 0,
  "battery": 3.29,
  "signal": 17,
  "time": "2024/11/21 08:31:30",
  "1": [2109, "2024/11/21 08:04:46"],
  "2": [1015, "2024/11/21 07:49:45"],
  "3": [1118, "2024/11/21 07:34:46"],
  "4": [0, "2024/11/21 05:26:12"],
  "5": [0, "2024/11/21 05:11:12"],
  "6": [0, "2024/11/21 04:56:12"],
  "7": [0, "2024/11/21 04:41:12"],
  "8": [0, "2024/11/21 04:26:12"]
}

Notice, from above payload:

2.2.2 HEX format Payload(Type=0)

This is the HEX Format:

f863663062798914f46008351350731409820ce81101000008d1673ef0a1083d673ee99e03f7673ee619045e673e

A table details the HEX format for DDS75-NB (AT+CLOCKLOG=1,65535,15,8), breaking down fields like IMEI, IMSI, Version, BAT, Signal, Interrupt, Interrupt_level, Distance, and Timestamp.

When using an MQTT client to subscribe to the relevant MQTT topic, the following information is observed during NB sensor uplink data transmission:

Signal strength values are detailed:

Interrupt: Indicates if the packet is generated by an interrupt. 0x00 is a normal uplink packet, and 0x01 is an Interrupt Uplink Packet.

Interrupt_level: Shows if the interrupt was triggered by a high or low level. 0x00 for falling edge (low level), 0x01 for rising edge (high level).

Distance: Reports the measured distance. The flat object range is 280mm - 7500mm. For example, a register value of 0x0B 0x05 translates to a distance of 2821mm (0B05(H) = 2821(D)). A sensor value of 0x0000 means the ultrasonic sensor did not detect an object.

Timestamp: Unit Timestamp Example: 6653ddb4(H) = 1716772276(D). This decimal value can be converted to a time using epochconverter.com.

2.2.3 ThingsBoard Payload(Type=3)

This payload is specifically designed for ThingsBoard and can also configure other default servers. It includes topic and payload details with IMEI, Model, distance, interrupt status, battery, signal, and historical sampling data with timestamps.

{
  "topic": "2276492",
  "payload": {
    "IMEI": "863663062798914",
    "Model": "DDS75-NB",
    "distance": 347,
    "interrupt": 0,
    "interrupt_level": 0,
    "battery": 3.38,
    "signal": 15,
    "1": [347, "2024/05/27 01:26:21"],
    "2": [250, "2024/05/27 00:57:17"],
    "3": [250, "2024/05/27 00:42:17"],
    "4": [250, "2024/05/27 00:27:17"],
    "5": [250, "2024/05/27 00:12:17"],
    "6": [250, "2024/05/26 23:57:17"],
    "7": [250, "2024/05/26 23:42:17"],
    "8": [250, "2024/05/26 23:27:16"]
  }
}

2.2.4 ThingSpeak Payload(Type=1)

This payload meets ThingSpeak platform requirements, including four fields. Fields 1-3 are: Distance, Battery & Signal. This payload type is only valid for the ThingsSpeak Platform.

Format: field1=Distance value&field2=Battery value&field3=Signal value

ThingSpeak charts display historical data for distance, battery voltage, and signal strength.

2.3 Test Uplink and Change Update Interval

By default, the sensor sends uplinks every 2 hours. Users can change the uplink interval using AT commands.

Note: Users can also push the button for more than 1 second to activate an uplink.

2.4 Multi-Samplings and One uplink

Notice: The AT+NOUD feature is upgraded to Clock Logging. Please refer to the Clock Logging Feature section.

To conserve battery life, the DDS75-NB samples distance data every 15 minutes and sends one uplink every 2 hours. Each uplink includes 8 stored data points + 1 real-time data point. These are defined by:

Diagrams illustrate the relationship between TR, NOUD, and TDC for data sampling and uplink intervals.

2.5 Trigger an uplink by external interrupt

The DDS75-NB has an external trigger interrupt function. Users can utilize the GPIO_EXTI pin to trigger data packet uploads.

2.6 Distance Alarm

This feature allows setting alarms for LDDS and NMDS.

2.7 Clock logging (Since firmware version v1.2.1)

When deploying multiple end nodes, it's often necessary for all sensors to sample data simultaneously for unified analysis. The clock logging feature facilitates this.

This command sets the start time for data recording and the time interval to meet specific data collection requirements:

Note: To disable clock recording, set parameters: AT+CLOCKLOG=1,65535,0,0.

Example: AT+CLOCKLOG=1,0,15,8. The device will log data to memory starting from the 0" second (e.g., 11:00:00) and sample/log every 15 minutes. Each TDC uplink will include battery information + the last 8 memory records with timestamps + the latest sample at uplink time.

A timeline diagram illustrates the process: Attached Network, First Sample and Log, subsequent samples at 15-minute intervals, and the final uplink including 8 samples plus the latest one.

Note: Users must synchronize the server time before configuring this command. If the server time is not synchronized, the command takes effect only after the node is reset.

Note: When entering the downlink payload, there must be no spaces between bytes.

2.8 Example Query saved historical records

This command can be used to search saved history, recording up to 32 groups of data, with each group containing a maximum of 100 bytes.

2.9 Uplink log query

This command can be used to query upstream logs of data packets.

2.10 Scheduled domain name resolution

This command is used to set up scheduled domain name resolution.

After setting this command, domain name resolution will be performed regularly.

2.11 Set the QoS level

This command is used to set the QoS level for MQTT.

2.12 Set CoAP option

This command sets the connection parameters for COAP.

Example:

2.13 Set the downlink debugging mode (Since firmware v1.3.0)

Feature: Set the conversion between the standard version and 1T version downlinks.

Command Example Function/Parameters Response/Explanation
AT+DOWNTE=? Get current Settings 0,0 (default) OK
AT+DOWNTE=a,b a: Set the conversion between the downlink of the standard version and 1T version 0: Set the downlink of the standard version.
1: Set the downlink of the 1T version (ThingsEye platform)
b: Enable/Disable downlink debugging 0: Disable downlink debugging mode.
1: Enable downlink debugging mode, users can see the original downlink reception.

Example:

Downlink Command: No downlink commands for this feature.

2.14 Domain name resolution settings (Since firmware v1.3.0)

Feature: Set dynamic domain name resolution IP.

Command Example Function/Parameters Response/Explanation
AT+BKDNS=? Get current Settings 0,0,NULL (default) OK
AT+BKDNS=a,b,c a: Enable/Disable dynamic domain name resolution. 1: Disable dynamic domain name update. The IP address will be saved after the domain name is resolved; if the next domain name resolution fails, the last saved IP address will be used.
2: Enable dynamic domain name update. The IP address will be saved after domain name resolution; if the next domain name resolution fails, the last saved IP address will be used, and the domain name resolution will be updated regularly according to the time set by the customer.
b: Set the time to update the domain name resolution at regular intervals. Unit: hour
c: Set the IP address manually. The format is the same as AT+SERVADDR. If domain name resolution fails, this IP address will be used directly. If domain name resolution succeeds, parameter 'c' will be updated to the successfully resolved IP address.

Example:

Downlink Command: No downlink commands for this feature.

3. Configure DDS75-NB

3.1 Configure Methods

DDS75-NB supports the following configuration methods:

3.2 Serial Access Password

After a successful Bluetooth or UART connection, use the Serial Access Password to enter the AT command window. The initial password is printed on the node's label as AT+PIN=xxxxxx. Use the six-digit password directly to access the AT instruction window.

Note: Do not use AT+PIN=xxxx to enter the password. Just use the six digits (e.g., 123456).

If you need to change the password, use AT+PWORD=xxxxxx (6 characters). NB nodes only support lowercase letters.

Note: After entering the command, a line break is required. Automatic line breaks can also be set in the Bluetooth tool or UART connection tool.

3.3 AT Commands Set

General AT command syntax:

General Commands

MQTT Management

Information

4. Battery & Power Consumption

The DDS75-NB uses an ER26500 + SPC1520 battery pack. For detailed information about the battery and replacement procedures, refer to the link: Battery Info & Power Consumption Analyze.

5. Firmware update

Users can update the device firmware to:

Firmware and changelog can be downloaded from: Firmware download link.

Methods to Update Firmware:

6. FAQ

6.1 How can I access BC660K-GL AT Commands?

User can access the BC660K-GL directly and send AT Commands. See BC660K-GL AT Command set.

6.2 Can I use DDS75-NB in condensation environment?

DDS75-NB is not suitable for use in condensation environments. Condensation on the DDS75-NB probe will affect readings and may result in a consistent reading of 0.

6.3 How to configure the certificate?

User can refer to this description to configure the certificate.

7. Trouble Shooting

7.1 Why does the sensor reading show 0 or "No sensor"

  1. The measurement object is very close to the sensor, but in the blind spot of the sensor.
  2. Sensor wiring is disconnected.
  3. Not using the correct decoder.

7.2 Abnormal readings: The gap between multiple readings is too large or the gap between the readings and the actual value is too large

  1. Please check if there is something on the probe affecting its measurement (e.g., condensed water, volatile oil, etc.).
  2. Check if the reading changes with temperature; temperature can affect measurement.
  3. If abnormal data occurs, turn on DEBUG mode. Use a downlink or AT command to enter DEBUG mode.

Command: Downlink command: F1 01, AT command: AT+DDEBUG=1

After entering debug mode, the device will send 20 pieces of data at a time. This data can be sent for analysis. The original payload will be longer than other data, even if parsed, it can be seen as abnormal data. Please send the data for checking.

8. Order Info

Part Number: DDS75-NB-XX

Where XX indicates:

9. Packing Info

Package Includes:

Dimension and weight:

10. Support

Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different time zones, live support cannot be guaranteed. However, questions will be answered as soon as possible within the mentioned schedule.

To receive support, please provide as much information as possible regarding your inquiry (product models, accurate description of the problem, and steps to replicate it, etc.) and send an email to Support@dragino.cc.

Models: DDS75-NB NB-IoT Distance Detection Sensor, DDS75-NB, NB-IoT Distance Detection Sensor, Distance Detection Sensor, Detection Sensor

File Info : application/pdf, 29 Pages, 2.00MB

PDF preview unavailable. Download the PDF instead.

20120079-dds75 nb nb iot distance detection sensor user manual ?srsltid=AfmBOooXhK8h-D2485p5pkfrJKOU6vTuuxPS4Y2vh5FBhxsDzcDbE GPL Ghostscript 9.50 Prawn

Related Documents

Preview Dragino NB-IoT Sensor Configuration Guide for IoT Servers
Comprehensive guide detailing configuration commands and procedures for Dragino NB-IoT models (-NB, -NS) to connect with various IoT servers like ThingSpeak, Datacake, Node-Red, ThingsBoard, and Tago.io using UDP, MQTT, and COAP protocols. Includes troubleshooting and FAQs.
Preview Dragino SDI-12-NB NB-IoT Analog Sensor User Manual
User manual for the Dragino SDI-12-NB NB-IoT Analog Sensor, detailing its features, specifications, connectivity, configuration, and AT commands for IoT deployments.
Preview SN50v3-NB NB-IoT Sensor Node User Manual | Dragino
Comprehensive user manual for the Dragino SN50v3-NB NB-IoT Sensor Node. Learn about its features, specifications, applications, working modes, configuration, and more for industrial IoT solutions.
Preview Dragino DS20L: LoRaWAN Lidar Distance Sensor User Guide
Explore the capabilities of the Dragino DS20L, a LoRaWAN Lidar distance sensor designed for long-range IoT applications. This guide covers setup, configuration, and usage for smart cities and industrial automation.
Preview Dragino T68DL LoRaWAN Temperature Sensor Manual
This manual provides detailed instructions for the Dragino T68DL LoRaWAN Temperature Sensor, covering its features, specifications, connection to IoT servers, configuration via AT commands or LoRaWAN downlink, battery information, firmware updates, FAQs, and support.
Preview Dragino LSN50v2-D2x LoRaWAN Temperature Sensor User Manual
Comprehensive user manual for the Dragino LSN50v2-D2x series of LoRaWAN waterproof outdoor temperature sensors. This guide covers device specifications, hardware variants, pin definitions, setup procedures for LoRaWAN networks (OTAA), payload analysis, temperature alarm features, configuration via AT commands, battery information, and support details.
Preview Dragino LA66 USB Adapter V2 User Manual - LoRaWAN Connectivity
Comprehensive user manual for the Dragino LA66 USB Adapter V2, detailing its features, specifications, LoRaWAN connectivity, setup examples, and troubleshooting for IoT applications.
Preview Dragino LHT52 LoRaWAN Temperature & Humidity Sensor
The Dragino LHT52 is a Long Range LoRaWAN Sensor for monitoring temperature and humidity. It features a built-in sensor, USB Type-C connector for external sensors, and supports LoRaWAN v1.0.3 protocol. The device includes a datalogging feature and temperature alarm functionality.