# RPD3-01

## Overview of the device

### Image

<figure><img src="/files/RNqE9cUYkGIVqXSsIkHu" alt=""><figcaption></figcaption></figure>

### Key Features

* Advanced 24 GHz millimeter-wave radar sensor with orthogonal high-gain antenna and FMCW modulation for ultra-precise human presence detection, including micro movements such as breathing
* Lifebeing Presence Detection, delivering reliable Presence/Absence output even for stationary occupants&#x20;
* Detects major, minor, and micro motion with highly coincident coverage, up to 6–8 m maximum diameter, ensuring consistent sensing across the entire space
* A round radiation pattern enables full-room coverage with a single sensor, eliminating blind spots
* Ultra-fast response: absence → presence < 0.5 s, presence → absence ≥ 15 s for stable automation behavior
* Integrated daylight sensor supports daylight-aware lighting and smart scene applications
* Powered directly by iNELS BUS, with all parameters configurable via iDM (iNELS Design Manager)
* Low RF power output, safe for continuous human exposure, and immune to temperature, humidity, air flow, dust, noise, and ambient light interference
* Supports both flush and surface mounting, suitable for smart homes, hotels, offices, and commercial spaces
* Provides fast, accurate front-end sensing for occupancy-based automation, HVAC optimization, and energy-saving control strategies.

### Device Description

<figure><img src="/files/FB19sVww1I0XpnqVTrnZ" alt=""><figcaption></figcaption></figure>

## Connection/ Wiring Diagram

<figure><img src="/files/AaOAfvaPJqW5XZVKQVs8" alt=""><figcaption></figcaption></figure>

## Programming in iDM

**Introduction**

iNELS Design Manager, or IDM3, is for programming iNELS units. This software serves as the platform for configuring device parameters, defining functions, and executing the programming required for iNELS units.

Device parameters, such as sensor range and thresholds, backlights, and operational modes, can be easily adjusted within the IDM3.

The process of programming in IDM3 typically involves defining functions and establishing logical connections between different devices. This allows for the creation of automation scenarios and the implementation of intelligent control strategies.

**Starting up**

Select the "***blue control icon"*** as shown in ***Fig 1*** > Clicking on the option ***"New project from default template“*** allows you to create a new project from a predefined template.

Select the "***Device manager"*** (***Fig 1***)> Add "***New unit*** "> Select the central unit > Add "***New*** ***unit"***>Select the "***Internal-Master/ BUS">*** Add "***New unit*** "> Add the devices> Click on the devices to see the "***Parameters"***.

![](https://t10544682.p.clickup-attachments.com/t10544682/149b9d72-2226-41ee-b0fe-f20a6ab01840/image.png)

***Fig 1: iDM Console***

**Parameters:**

**Parameters** in the iNELS devices refer to the measurable factors or characteristics that define the behavior or performance of the device. These could include electrical properties, physical dimensions, environmental conditions, and various other specifications depending on the type of device.

These are settings specific to individual devices within your automation system.

The specific parameters of the RPD3-01 in the iDM as shown in ***Fig.2***

<figure><img src="/files/GRdQH02AAmWOSI3pFrai" alt=""><figcaption></figcaption></figure>

Clicking on the RPD3-1 (***Fig.2***), will navigate to selected firmware, unit address, name, and description, along with other parameters as described below&#x20;

**True state button**

* Time the output must be active to be considered **valid**

**Long state button**

* Defines threshold for **long press / long detection**
* Used mainly for logic or differentiation, Helps distinguish short vs long events

**Hold time**

* Time the sensor **keeps output active after last detection**
* Unit: seconds

{% hint style="info" %}
Example: If set to 3 s → after movement stops, output stays ON for 3 seconds
{% endhint %}

**Detection area**

* Detection radius (in meters): Defines how far the sensor “sees”

{% hint style="info" %}
Example: 4 m → covers medium room
{% endhint %}

**Light difference threshold** (lx): Required change in light (lux) to trigger reaction\
Prevents switching due to small fluctuations

**Sensitivity**

* Detection sensitivity level: Options: Low / Medium / High

{% hint style="info" %}
Higher = detects smaller movements\
Lower = avoids false triggers
{% endhint %}

**Light coefficient**: Calibration factor for light measurement\
Used to fine-tune lux readings

**Use LED**: Enables status LED on device\
Useful for testing, usually OFF in production

**Presence detection switch**: Enables presence detection output\
Core function (should be ON if used)

**Light detection enable**: Activates light sensor (lux measurement)\
Needed for daylight-based automation

**Approaching / moving away reporting:** Enables directional detection:

* approaching
* leaving

**Pairing action**: Used during pairing / commissioning

**Factory reset**: Resets device to default settings

### Sensor Outputs Meaning

1\. **Light-IN**: Measures ambient light level (lux)

2\. **Presence-DIN**: Detects real presence (including micro-movement like breathing

3\. **Approaching-DIN**: Detects if a person is moving towards the sensor.

4. **Moving-Away-DIN**: Detects if a person is moving away from the sensor

&#x20;5\. **Still-DIN**: Detects very small movements (micro-presence)

6\. **Environmental-AOUT**: Output related to environment learning / calibration

7\. **Status-AOUT**: Provides sensor status / analog output


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://wiki.inels.com/inels-bus/technical-manual-products/detectors/rpd3-01.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
