> This is part 1 of 2 of the full documentation (pages 1–100 of 154).
> The content is paginated: fetch every part to see all of it.
> Next part: https://docs.yudash.com/llms-full.txt/1
> Page index: https://docs.yudash.com/llms.txt

# Welcome

IoT · Edge · AI: from field instruments to actionable insight.

[YuDash](https://www.yudash.com/) designs and manufactures IoT data loggers, gateways and instrument controllers in India, together with the cloud platform that brings their data to life. Our devices read industrial instruments, analysers and environmental sensors, process data at the edge, and deliver it securely to compliance portals, enterprise clouds or your own servers.

This documentation covers every step of that journey: wiring a sensor, configuring a device, choosing a network, and integrating with your IoT platform.

### The YuDash IIoT Stack

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FvZACiauUuRZu601frAlM%2Fyudash_iiot_stack_2.png?alt=media&amp;token=f4b3f9c2-5ba9-4bd7-bd53-61239d139e9a" alt=""><figcaption></figcaption></figure>

Every YuDash deployment follows the same path, from the instrument in the field to the application on your screen. Each section of this documentation covers one or more of these layers.

### YuDash Products

From field data loggers to the cloud, YuDash products work together as one connected system. Choose the right product for your application, or explore the platform that connects them all.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>YuDash FELYX</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FLjp3jU3Uronoavh0KI91%2FYuDash_FELYX.png?alt=media&amp;token=26334663-71d6-4505-9d49-0564cd520d01">YuDash_FELYX.png</a></td><td><a href="/felyx">FELYX</a></td></tr><tr><td>YuDash ZENYX</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FZrr5zB74v84g9It4TruC%2FYuDash_ZENYX.png?alt=media&amp;token=777dd56a-4cd2-496f-b878-375a2eb023b0">YuDash_ZENYX.png</a></td><td><a href="/zenyx">ZENYX</a></td></tr><tr><td>YuDash NUREX</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FZ4Dx63ixkLY1rNjViCkc%2FYuDash_NUREX.png?alt=media&amp;token=76cbcd32-9ee3-43fe-b45c-34798503d552">YuDash_NUREX.png</a></td><td><a href="/nurex">NUREX</a></td></tr><tr><td>YuDash ZEVA</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDoIrcwJCEUbO0NfsX9FM%2FYuDash_ZEVA.png?alt=media&amp;token=fdd9c633-9881-4624-b8cb-e26cc210c577">YuDash_ZEVA.png</a></td><td></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FBXApMEvyTy0EPW9AD9Xw%2FYuDash_YuFourIA.png?alt=media&amp;token=d891b40a-4a66-487f-9014-50f182bda8ca">YuDash_YuFourIA.png</a></td><td></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FyWi5iKFJ9H8DHJjQVvJb%2FYuDash_SETU.png?alt=media&amp;token=61fbef3e-f8b3-44a1-bb49-7c7579d4e00e">YuDash_SETU.png</a></td><td></td></tr></tbody></table>


# FELYX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F3S6U3dl96hpHZ4RaYSJd%2F1.png?alt=media&amp;token=87d2abd0-8a42-4bd0-8e4f-7ce6afbc6d45" alt=""><figcaption></figcaption></figure>

## IoT Data Logger for Weather & Hydromet <a href="#felyx-overview" id="felyx-overview"></a>

YuDash FELYX is a compact, industrial IoT data logger designed for **weather, hydromet and environmental monitoring applications**. It combines flexible sensor connectivity, local data logging, edge processing and IoT telemetry in a DIN-rail platform.

FELYX is built around a **Dual-Core 32-bit Xtensa LX7 processor running at 240 MHz** and is designed for low-power operation at approximately **1 W nominal power**, depending on the active features.

FELYX can acquire data from a wide range of sensors and instruments, process the data locally, store it on the industrial SD card, display current values through its local interface, and transmit selected data to cloud platforms or remote servers.

### Flexible Sensor Connectivity

FELYX supports multiple sensor interfaces for integration with weather, water, environmental and industrial instruments.

Supported interfaces include:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6wFoVpSE1go6dJngjpT4%2Ficon_modbus_rtu.png?alt=media&amp;token=c0e25901-595d-4ca7-a20f-f40428eb1084">icon_modbus_rtu.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FLeZvcconh8nA2KHGSreJ%2Ficon_sdi12.png?alt=media&amp;token=52e53a7f-c03c-428d-a102-f4571f2cd102">icon_sdi12.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkcPk0n4Mcm0TuufcXuc6%2Ficon_analog_inputs.png?alt=media&amp;token=def1dfed-7081-4191-862d-bbea7367dd3f">icon_analog_inputs.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FVZfgHLbiH5MdSGlcmNVW%2Ficon_rain_gauge.png?alt=media&amp;token=3976fc58-fafa-49fd-b873-91d47d168bed">icon_rain_gauge.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FlOWzogXUUbJXaRGMfdA4%2Ficon_wind_sensor.png?alt=media&amp;token=03ef2ff7-c629-4615-bd4c-3cfe9f32a576">icon_wind_sensor.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYiBzjczFbAHKgP3MThsV%2Ficon_rs232_ascii.png?alt=media&amp;token=26b7de27-940e-4935-b7ab-66e0b307faf1">icon_rs232_ascii.png</a></td></tr></tbody></table>

* Built-in sensor recipes for faster integration with supported instruments

Depending on the FELYX model, analog inputs can support **0–20 mA, 0–5 V and battery-voltage measurement**, along with optional differential low-level voltage measurement.

### Data Logging & Edge Processing

FELYX provides local data acquisition and processing independently of cloud connectivity.

Key capabilities include:

* **8 GB Industrial SD Card**
* Flexible CSV data logging
* Configurable file name and logging interval
* Data Scaling and Clipping
* High-speed **Burst Mode up to 50 Hz**
* Formula-based derived parameters
* ASCII / Custom Protocol Parsing
* Rule-based edge actions
* Embedded SQL database and dashboard through **YuDash AXON**

### IoT Telemetry

FELYX provides multiple options for sending data to cloud platforms, APIs and remote servers.

Connectivity options include **4G/LTE Cellular, Ethernet LAN and 2.4 GHz Wi-Fi**.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FViy3mTvb1y2vryqN0Fws%2Ficon_4g_lte.png?alt=media&amp;token=19d43eed-ba26-482f-b021-bd4f3dc708f3">icon_4g_lte.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FpcGPy5cR4TJfJ6w6iAbv%2Ficon_ethernet_lan.png?alt=media&amp;token=13b34854-2b02-402d-b24d-d1573e79233f">icon_ethernet_lan.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmVz8JWiyHpFwOLkLWKtG%2Ficon_wifi.png?alt=media&amp;token=eeffee11-77cd-4362-ae59-2b233823319f">icon_wifi.png</a></td></tr></tbody></table>

Cloud and telemetry features include:

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FoNv0eaTs50UNXySCRuW8%2Ficon_ftp.png?alt=media&amp;token=abb59bcd-5577-43a8-a925-bb630814df59">icon_ftp.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fy05LbhkBsXW5xr1XXhI9%2Ficon_rest_api.png?alt=media&amp;token=34473ac9-a248-4ff8-9581-c28950b4d056">icon_rest_api.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6650xXk5ECaNPJR2Qcbl%2Ficon_mqtt.png?alt=media&amp;token=41bd7ce2-1ba3-4531-9e54-5d4c6b22355c">icon_mqtt.png</a></td></tr><tr><td></td><td></td></tr></tbody></table>

* TLS/SSL encryption
* Configurable JSON / TXT payloads
* Multi-API and Multi-Server support
* Automatic backfill after network recovery
* High-speed real-time data access through Modbus TCP Server

### Local Configuration & Monitoring

FELYX includes a built-in Web UI for configuration and monitoring over LAN or Wi-Fi.

Most device functions use structured, **Wizard-based configuration**, while JSON-based configuration allows device settings to be backed up and restored. The local interface also provides live device monitoring and access to logged data on the SD card. YuDash\_FELYX\_Oct26

The built-in **0.96-inch OLED display** provides local status and diagnostic information directly on the device.

### Expandable for Field Applications

FELYX is available in multiple hardware variants to suit different combinations of Analog, Modbus, SDI-12, Weather and RS232 interfaces.

Optional add-ons include:

* **4G/LTE module with GNSS**
* Davis Wind & Rain sensor interfaces
* 4-channel 24-bit ADC for low-level 0–100 mV inputs
* IP66 outdoor enclosure
* External 16×4 character LCD or 4.3-inch TFT display

## FELYX Product Variants <a href="#felyxpartnumbers" id="felyxpartnumbers"></a>

### FELYX81

FELYX81 is our standard product, mostly available in stock. This is the most versatile product supporting all major protocols. This product variant is used in the documentation reference. It supports&#x20;

### FELYX Part Numbers

| Part No | Analog 0-20mA | Analog 0-5V | Analog 0-90V | RS485 Modbus #1 | Rain Gauge Pulse | SDI-12 | Wind Speed Pulse | RS232 | RS485 Modbus #2 |
| ------- | ------------- | ----------- | ------------ | --------------- | ---------------- | ------ | ---------------- | ----- | --------------- |
| FELYX81 | 4 Ch          | 3 Ch        | 1 Ch         | Yes             | Yes              | Yes    | Yes              | -     | -               |
| FELYX83 | -             | 7 Ch        | 1 Ch         | Yes             | Yes              | Yes    | Yes              | -     | -               |
| FELYX85 | 7 Ch          | -           | 1 Ch         | Yes             | Yes              | Yes    | Yes              | -     | -               |
| FELYX86 | 4 Ch          | 3 Ch        | 1 Ch         | Yes             | Yes              | Yes    | Yes              | Yes   | -               |
| FELYX61 | 4 Ch          | 3 Ch        | 1 Ch         | Yes             | Yes              | -      | -                | -     | Yes             |
| FELYX65 | 7 Ch          | -           | 1 Ch         | Yes             | Yes              | -      | -                | -     | Yes             |

**Common features across all FELYX models:**&#x20;

4G/LTE connectivity, Ethernet LAN, 8 GB industrial SD card.

{% hint style="info" %}
As the FELYX UI is continuously evolving, some interfaces in your product may be slightly different from the ones in this manual.
{% endhint %}


# FELYX Interfaces

## YuDash FELYX Terminals

#### Front view of FELYX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDfn3WjRHIfmGylaFTYzc%2F2.png?alt=media&amp;token=a3fea9fb-c35b-450d-9192-4030451c56fa" alt=""><figcaption></figcaption></figure>

### FELYX terminals and network ports

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FKD9Cu7nvRCZnMzz4iMSB%2F3.png?alt=media&amp;token=aad57693-f5f4-4836-8dc6-57d4d322dd09" alt=""><figcaption></figcaption></figure>

### Terminal view of FELYX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FKMTzvHAoQdumKbrmmwe7%2F4.png?alt=media&amp;token=4375fe77-dcad-4363-ad51-331450932e34" alt=""><figcaption></figcaption></figure>

### FELYX Network Ports

FELYX supports 4G/LTE, Ethernet LAN and Wi-Fi as standard. Availability of RS232, SDI-12, RS485 Modbus#2, Rain Gauge and Wind Speed pulse inputs depends on the part number — see FELYX Product variants.

### Ethernet LAN Port

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6Z8JBfRkuExalOG3ShqN%2F6.png?alt=media&amp;token=8ea7278b-1051-4254-8ab3-37692bdce029" alt=""><figcaption></figcaption></figure>

### 4G/LTE SIM Card and Antenna

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FN7lgvtIOuSoqSHl5cMdt%2F5.png?alt=media&amp;token=3f7203c8-098e-4258-af22-e6d1e350dccd" alt=""><figcaption></figcaption></figure>

###

{% embed url="<https://youtu.be/q9vi3afGTk4>" %}

### SD Card Slot

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FIvEPGgAJqb9XT9LNHLvW%2F7.png?alt=media&amp;token=72a0d7d4-0cc5-44a4-bcf3-0c66c68e0b30" alt=""><figcaption></figcaption></figure>

##


# Getting Started


# Configuration

FELYX includes an integrated web-based configuration interface. No configuration software needs to be installed on the user's computer.

The configuration interface can be accessed using either **Wi-Fi** or **Ethernet**, allowing a laptop, tablet or mobile device to configure FELYX directly from a standard web browser.

At every boot, FELYX provides a short **5-second configuration window**. If the Config button is not pressed during this period, FELYX automatically continues into normal operation. This follows the same basic configuration concept used across YuDash devices.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQQP5CW2gaYaFPwNFiSRL%2FYuDash_FELYX_Config_Summary.png?alt=media&amp;token=13d5dfaa-e208-4be7-a211-4e0eceabc906" alt=""><figcaption></figcaption></figure>

### Enter Configuration Mode

#### Step 1 — Power up FELYX

Power ON or restart the device.

During startup, the OLED displays a countdown of approximately **5 seconds** during which Configuration Mode can be activated.

> **Tip:** No action is required for normal operation. Simply allow the countdown to complete and FELYX will continue with its normal run sequence.

#### Step 2 — Press the Config button

During the countdown, **short-press and release the Config button**.

FELYX will start its local Configuration Server and make the configuration interface available over the supported network interfaces.

> **Important:** Use a short press only. Do not hold the Config button continuously.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FxO1XbS3v0iYdkzTLxpiP%2Fconfig_button_press.jpg?alt=media&amp;token=00114acc-34e9-4add-b573-bc8581a04193" alt=""><figcaption></figcaption></figure>

***

#### Step 3 — Configuration Server starts

Once Configuration Mode is activated, FELYX starts its configuration services.

The OLED displays the network information required to connect to the device.

Two connection methods are available:

**Wi-Fi**

* FELYX creates a local Wi-Fi network.
* **SSID:** based on the device number
* **Default Wi-Fi password:** `12345678`
* **Configuration IP:** `192.168.4.1`

**Ethernet**

* FELYX starts the Ethernet configuration server.
* **Configuration IP:** `192.168.2.1`

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FyA7iuZn0C7WFLJg2WpUC%2Fconfig_mode_status.jpg?alt=media&amp;token=096c5625-738f-4e35-8c96-9fea85a90390" alt=""><figcaption></figcaption></figure>

***

## Configure through Ethernet

FELYX can be configured using a direct Ethernet connection.

#### 1. Connect the Ethernet cable

Connect the laptop/PC directly to **ETH1** on FELYX.

#### 2. Configure the laptop Ethernet address

During Configuration Mode, FELYX uses the Ethernet address:

`192.168.2.1`

Configure the laptop Ethernet interface with an IP address in the same subnet, for example:

`192.168.2.2`

or another unused address in the `192.168.2.x` range.

This direct-Ethernet method follows the same approach used in the existing YuDash configuration workflow.

#### 3. Open FELYX in the browser

Open a web browser and enter:

`http://192.168.2.1`

The **FELYX Configuration Server login page** will open.

{% embed url="<https://youtu.be/_ozW9MDU4ts>" %}

***

## Configure through Wi-Fi

Wi-Fi configuration is the easy wireless method when using a laptop, tablet or mobile device.

#### 1. Connect to FELYX Wi-Fi

Open the Wi-Fi settings on your laptop, tablet or mobile device and select the Wi-Fi network displayed on the FELYX OLED.

Enter the displayed/default password when requested.

Your device is now connected directly to FELYX.

#### 2. Open the configuration page

Open a web browser and enter:

`http://192.168.4.1`

The **FELYX Configuration Server login page** will open.

> While connected directly to the FELYX configuration Wi-Fi, Internet access on the laptop or mobile device may not be available. This is normal for the local configuration connection.

{% embed url="<https://youtu.be/U4Ix6BGRAho>" %}

## Normal Operation

If the Config button is **not pressed during the startup countdown**, FELYX proceeds automatically to normal operation.

During normal operation, the Ethernet interface uses the IP address configured in the device settings.

The **factory-default Ethernet IP shown in your current FELYX flow is:**

`192.168.1.10`

This address is different from the temporary Ethernet configuration address `192.168.2.1`.

{% hint style="info" %}
**Configuration IP vs. Normal IP**\
`192.168.2.1` — Ethernet address used while entering Configuration Mode\
`192.168.1.10` — factory-default Ethernet address during normal operation\
The normal-operation IP can be changed from FELYX Network Settings.
{% endhint %}

***


# How FELYX Works

## Understanding FELYX: Configuration & Data Flow

FELYX is designed around a modular configuration architecture. The device is configured through its built-in **Web UI over LAN or Wi-Fi**, while JSON-based configuration is used extensively across device functions and for configuration backup and restore.

A typical FELYX application can be understood as a simple data flow:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYllhLUZonxsgTZrLBuiY%2Foverall_flow.png?alt=media&amp;token=cbdf8374-7339-4b7e-849d-7168e87edf66" alt=""><figcaption></figcaption></figure>

The configuration pages and Wizards define how data moves through each stage.

#### Network Configuration – How FELYX Connects

In addition to defining **what data to read, how to process it, and where to send it**, FELYX must also be configured for **how it connects to the network or Internet**.

This is handled separately under **Network Settings**, where the required connection mode is selected: **4G/LTE, Ethernet, Wi-Fi, or Offline**.

Network settings are stored separately from the main device configuration. This allows the same FELYX configuration to be retained even when the network connection method changes.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FUiAVZRI2X51xmhEyL42w%2Fnetwork_config.png?alt=media&amp;token=131b6c2a-12dc-4c4f-9137-a014293bc269" alt=""><figcaption></figcaption></figure>

### Wizard-Based Configuration

Most FELYX features are configured through dedicated **Wizards**. Each Wizard groups the settings required for a particular function and provides a structured interface for configuring that feature.

For example, Analog Inputs are configured through the **Analog Wizard**, SDI-12 sensors through the **SDI-12 Wizard**, Data Scaling through the **DataScale Wizard**, and AXON functions through the **AXON Wizard**.

The detailed settings are saved through the respective Wizard and remain available as part of the device configuration.

### Configure and Enable

In FELYX, **configuration and feature activation are separate**.

A feature can be fully configured and its settings saved through the corresponding Wizard. However, the feature is processed by the device only when it is also **enabled under Device Settings → Feature Settings**.

For example, Analog Input channels may be configured and saved in the Analog Wizard, but analog inputs will be processed only when the **Analog Inputs** checkbox is enabled under Feature Settings.

This separation provides flexibility. A feature can be temporarily disabled without deleting or changing its saved configuration.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FopXS38cQehzYMvUeUi5x%2Fwizard_enable.jpg?alt=media&amp;token=85d25d25-1007-4370-acb3-da1518d09f84" alt=""><figcaption></figcaption></figure>

### Sensor Settings – What to Read

The **Sensor Settings** section defines the sensors and instruments from which FELYX acquires data.

Depending on the FELYX model and application, sensor data may be acquired through interfaces such as **RS485 Modbus RTU, SDI-12, Analog Inputs, Rain Gauge inputs, Wind Speed & Direction inputs and other supported interfaces**.

Each sensor configuration maps the acquired measurements to variables within FELYX. These variables can then be used by other device functions for processing, monitoring, logging and telemetry.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FgycUdvWqlTaXKXgdNLQs%2Ffelyx_sensor_how.jpg?alt=media&amp;token=5f81acb3-c68d-42ae-b0a4-f38ed544b3cc" alt=""><figcaption></figcaption></figure>

### Data Processing – What to Do with the Data

After data has been acquired, FELYX can process the values locally before they are displayed, logged or transmitted.

#### Data Scaling

**Data Scaling** provides functions for scaling and clipping sensor values. It can be used to convert acquired values into the required engineering or application values.

#### YuDash AXON

**YuDash AXON Edge Intelligence** provides additional on-device processing capabilities. AXON supports functions including formula-based derived parameters, ASCII/custom protocol parsing, rule-based edge actions and an embedded SQL database and dashboard.

This allows FELYX to perform calculations and application logic directly at the edge rather than only forwarding raw sensor data.

**Sensor Settings acquire the data. Data Scaling and AXON process the data.**

### Live Monitoring and Display

FELYX provides local methods for viewing device and sensor information without requiring cloud connectivity.

#### Live Dashboard

The on-device **Live Dashboard** provides real-time monitoring of the present sensor and parameter values through the FELYX Web UI. It is useful during installation, commissioning, testing and diagnostics.

FELYX also provides on-device data monitoring and access to the SD Card through its local interface.

#### OLED Display

The built-in **OLED Display** provides local device status and diagnostic information directly on the FELYX hardware.

Together, the Web UI and OLED provide immediate local visibility of device operation.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FOs4eBbABBrOxLT31uURx%2Ffelyx_live_dashbaor.jpg?alt=media&amp;token=16a34fbf-6276-4602-89b1-65c08c638fdd" alt=""><figcaption></figcaption></figure>

### Data Logger – Store the Data

The **Data Logger** provides local storage of sensor and calculated data.

FELYX supports configurable CSV format and timestamping, along with user-defined file names and logging intervals.

The Data Logger therefore provides historical data storage independently of cloud or network connectivity.

**Data Logger defines what FELYX stores locally.**

### Cloud Settings – Where to Send the Data

The **Cloud Settings** section controls IoT Telemetry from FELYX to external servers and cloud platforms.

FELYX supports **MQTT, REST API, HTTP and FTP**, TLS/SSL encryption, configurable JSON/TXT payloads, and multi-server telemetry with automatic backfill after network recovery.

The Cloud Settings determine how the required variables are packaged and transmitted to the configured destination.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FtUJjItSdcTua5Nof8HDD%2Ffelyx_cloud_how1.jpg?alt=media&amp;token=1aea6148-9af2-4f2b-8c92-0a82cff22469" alt=""><figcaption></figcaption></figure>

### Overall FELYX Data Flow


# FELYX Features

FELYX combines flexible sensor interfaces, local data processing, data logging, device monitoring and IoT telemetry in a compact field data logger.

This page provides an overview of the features available on FELYX. Follow the links below for detailed configuration and technical documentation.

### Configuration

FELYX is configured through its browser-based Web UI. Configuration includes device settings, feature enable/disable, Wizards, variable configuration and JSON-based backup and restore.

[**Detailed documentation**](/pf/cf)

### Sensor Inputs

<table data-view="cards"><thead><tr><th data-hidden data-card-target data-type="content-ref"></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pf/si/modbus">Modbus/RS485</a></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6wFoVpSE1go6dJngjpT4%2Ficon_modbus_rtu.png?alt=media&amp;token=c0e25901-595d-4ca7-a20f-f40428eb1084">icon_modbus_rtu.png</a></td></tr><tr><td><a href="/felyx/pf/si/analog-inputs">Analog Inputs</a></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkcPk0n4Mcm0TuufcXuc6%2Ficon_analog_inputs.png?alt=media&amp;token=def1dfed-7081-4191-862d-bbea7367dd3f">icon_analog_inputs.png</a></td></tr><tr><td><a href="/felyx/pf/si/sdi12">SDI-12</a></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FLeZvcconh8nA2KHGSreJ%2Ficon_sdi12.png?alt=media&amp;token=52e53a7f-c03c-428d-a102-f4571f2cd102">icon_sdi12.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FVZfgHLbiH5MdSGlcmNVW%2Ficon_rain_gauge.png?alt=media&amp;token=3976fc58-fafa-49fd-b873-91d47d168bed">icon_rain_gauge.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FlOWzogXUUbJXaRGMfdA4%2Ficon_wind_sensor.png?alt=media&amp;token=03ef2ff7-c629-4615-bd4c-3cfe9f32a576">icon_wind_sensor.png</a></td></tr><tr><td></td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYiBzjczFbAHKgP3MThsV%2Ficon_rs232_ascii.png?alt=media&amp;token=26b7de27-940e-4935-b7ab-66e0b307faf1">icon_rs232_ascii.png</a></td></tr></tbody></table>


# Sensors & Inputs


# Modbus/RS485

Modbus instrument integration of YuDash FELYX

Modbus/RS485 is a popular serial protocol to read various sensors. YuDash FELYX dataloggers are being used to read a variety of instruments, sensors and PLCs for various applications. FELYX provides easy to configure approach for reading field Modbus instruments. Following are the key information points required for a successful read of instrument through Modbus:

1. Baudrate
2. Data Bits, Parity and Stop Bit
3. Slave ID of instrument
4. Modbus register information to read:
   1. Modbus register numbers and types)
   2. Modbus register data types (Size: integer/float/real. Byte swapping information: LSB/MSB etc.)
5. Modbus register address.

## Modbus Register Mapping in YuDash FELYX <a href="#h.jt0n9eorg4hg_l" id="h.jt0n9eorg4hg_l"></a>

Following four inputs have to be provided for processing of each Modbus register in YuDash FELYX Data logger:

1\) **Variable Name:** YuDash FELYX reads a given Modbus register and stores it in a variable. This is the user defined string, which will be sent to IoT platform/server along with the process values. For sending to YuDash cloud, the variable names should be all small letters without any blank spaces. Sample variable name: **volt1 temperature\_celcius amp\_01 amp\_02 machine\_status\_flag**

2\) **Register Number:** The register types/function codes of Modbus are defined by register numbers. User has to specify complete **#Register No.** in Modbus register section. Following is the available range of registers:

| Function Code | Registers             | Range       |
| ------------- | --------------------- | ----------- |
| **1**         | **COIL STATUS**       | 0-9990      |
| **2**         | **INPUT STATUS**      | 10000-19999 |
| **4**         | **INPUT REGISTERS**   | 30000-39999 |
| **3**         | **HOLDING REGISTERS** | 40000-49999 |

{% hint style="info" %}
Important Note: YuDash FELYX uses base-0 register addressing (starting with 40000). OEM instrument manual uses both base-0 or base-1 registers, so that they have to checked accordingly. The MODSCAN uses base 1 register addressing (starting with 40001). So, after MODSCAN registers are identified, you have to enter register as one less than the MODSCAN register.
{% endhint %}

3\) **Type**: The data type of Modbus registers are specified in data **Type** code in MODUS register settings. Following are the register type codes:

<table><thead><tr><th width="130">Type</th><th width="300.3333333333333">Description</th><th>No. of Registers read</th><th>Byte Sequence</th></tr></thead><tbody><tr><td>1</td><td>SIGNED INTEGER</td><td>1</td><td></td></tr><tr><td>2 or 20</td><td>Floating Point (LSB first)</td><td>2</td><td>CDAB</td></tr><tr><td>21</td><td>Floating Point (MSB first) </td><td>2</td><td>ABCD</td></tr><tr><td>22</td><td>32bit Integer (LSB first)</td><td>2</td><td>CDAB</td></tr><tr><td>23</td><td>32bit Integer (MSB first)</td><td>2</td><td>ABCD</td></tr><tr><td>24</td><td>32bit Unsigned Integer (LSB first)</td><td>2</td><td>CDAB</td></tr><tr><td>25</td><td>32bit Unsigned Integer (MSB first)</td><td>2</td><td>ABCD</td></tr><tr><td>11</td><td>Bit pattern Extraction</td><td>1</td><td></td></tr></tbody></table>

{% hint style="info" %}
FELYX also supports byte swapping for 32 bit registers. For these special case, we have to use 3 digit Type (by adding a suffix 1 to original type). It will enable byte swapping with same data type as corresponding 2 digit code: \
**201, 221, 241**: **DCBA** \
**211, 231, 251**: **BADC**

*Note: Support of code 24, 25 and 3 digit types is available in firmware V3.6 onwards.*
{% endhint %}

YuDash IoT devices also support various 64 bit data types as IEEE-754 Floating-Point numbers and also 64 bit signed integer. For 64 bit data types, 4 modbus registers are read. We are not using terminology of LSB and MSB as there are various nomenclatures. We effectively support all swapping at 16bit register . We are calling them P, Q, R, S (for each 16 bit modbus register). This is similar to ABCD were bytes. *Note: 64 bit data type is available in firmware V3.6 onwards.*

Following are possible combinations:&#x20;

<table><thead><tr><th width="122">Type</th><th>Sequence</th><th>Type</th><th>Sequence</th><th>Data Type</th></tr></thead><tbody><tr><td><strong>4 or 40</strong></td><td>RSPQ</td><td><strong>401</strong></td><td>SRQP</td><td>Float 64</td></tr><tr><td><strong>41</strong></td><td>PQRS</td><td><strong>411</strong></td><td>QPSR</td><td>Float 64</td></tr><tr><td><strong>42</strong></td><td>RSPQ</td><td><strong>421</strong></td><td>SRQP</td><td>Int 64</td></tr><tr><td><strong>43</strong></td><td>PQRS</td><td><strong>431</strong></td><td>QPSR</td><td>Int 64</td></tr></tbody></table>

{% hint style="info" %}
By default, all values from YuDash IoT devices are converted to 32 bit floating point numbers. So, while we can read larger 64 bit values, there may be data precision loss or possibly overflow while processing large number 32 bit integer or 64 bit data types. Use of factor (see below) may be useful to handle cases of data overflow.&#x20;
{% endhint %}

4\) **Factor**: FELYX provides option to post process register value after reading of inputs. The register value is divided by the value provided in Factor. By default, Factor of 1 used . Typically, Factor of 10 or 100 may be used in cases when Modbus registers are integer representations in multiple. For example, if the voltage of 234.6 is represented as integer of 2346 in Modbus register, factor of 10 can be used. With this factor, FELYX will read 2346 integer value, divide by 10 and send 234.6 on the cloud platform. This helps in receiving values on cloud which map to values seen on display. In many cases, 100X value is used in integer form.

{% hint style="info" %}
In most of industrial applications, MODSCAN (or similar) software is used to validate the Modbus settings. In case of any troubleshooting, we strongly suggest to validate the communication through MODSCAN. Our tutorial explains the mapping in reference of MODSCAN to FELYX settings.
{% endhint %}

## Modbus/RS485 interfacing example

To explain Modbus/RS485 mapping in FELYX, we will interface it with a single phase energy meter to read its voltage and frequency.

1. Selec make EM2M is used to interface with MODSCAN software followed by YuDash FELYX.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fq8yIsNS3lACoKVHov5fd%2FYuDashHelpPages_EM2M.png?alt=media&amp;token=39bc657d-745b-406f-b411-616d8999aed0" alt=""><figcaption></figcaption></figure>

2. Energy Meter MODUBUS settings checked in MODSCAN software.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F0kv1c1Ar9qxxMkx8NlJw%2Fem2m_1.png?alt=media&amp;token=193b09ba-2a30-4658-bf08-e87bc85be465" alt=""><figcaption></figcaption></figure>

3. Voltage and Frequency values test-read in MODSCAN software and co-related with datasheet values.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FOeDX77eGcvSf8WyyQ6io%2Fem2m_2.png?alt=media&amp;token=4ba10e6f-0370-4be9-84fa-0035cbdee859" alt=""><figcaption></figcaption></figure>

4. Corresponding settings updated in YuDash FELYX Modbus/RS485 section.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FZMtAWVi8uAjXsFfF5OqI%2FYuDashHelpPages_EM2M%20(1).png?alt=media&amp;token=1fe6ff55-2a00-4375-846a-a2c092e1019f" alt=""><figcaption></figcaption></figure>

5. After configuration and reboot, sensor values can be seed on OLED and live dashboard

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F9NERtIWWkvHWoOH5gbor%2FYuDash_FELYX_Modbus_EM2M.png?alt=media&amp;token=ffe17223-b90f-4c52-86b0-2b8450f84759" alt=""><figcaption></figcaption></figure>

Following video explains the steps for updating Modbus/RS485 settings in FELYX:

{% embed url="<https://youtu.be/Ahz1q9E2gtw>" %}


# Analog Inputs

FELYX provides 8 channels of 16-bit ADC analog input, supporting 0-20mA, and 0-5V ranges (an optional 0-90V DC input is available on some variants for battery voltage monitoring). The exact channel split between 0-20mA, 0-5V and 0-90V depends on the part number

Few variants of LYNX support direct analog read inputs. LYNX supports 8 channels of 0-20mA read. The terminals A1 to A8 terminals are available for 8 channels of analog.

In most of industrial applications, 4-20mA values are mapped to given process values. LYNX has advanced data scaling features to handle process values of different applications.

While user can perform scaling within Analog Inputs, we recommend using generic [**Data Scaling**](/yudash-iot-products/lynx/lynx-settings/data-scaling) section of LYNX for analog data interpolation.

## Analog Input Settings

### Types of Analog Inputs

In this section, we explain analog inputs using our standard product FELYX81. FELYX81 has 8 analog terminals: A1, A2, A3, A4, C5, C6, C7 and D8.

The first character of the terminal name shows the type of input:

* A – Current input, 0-20mA. Use it for 4-20mA sensors.
* C – Voltage input, 0-5V DC. Use it for sensors with voltage output.
* D – High voltage input, 0-90V DC. Use it for battery or solar panel voltage.

The number after the letter is the channel number (1 to 8).

| Terminal       | Type             | Input range | Typical use             |
| -------------- | ---------------- | ----------- | ----------------------- |
| A1, A2, A3, A4 | A – Current      | 0-20mA      | 4-20mA sensors          |
| C5, C6, C7     | C – Voltage      | 0-5V DC     | Voltage output sensors  |
| D8             | D – High voltage | 0-90V DC    | Battery / solar voltage |

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FwI7c92K8jaq5q9ONaulX%2FFELYX_SensorIntegration.png?alt=media&amp;token=2146790a-b9e4-4cfc-b745-314b5978581e" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**The actual analog terminals depend on the FELYX part number. For example, FELYX83 has 7 voltage inputs (C) and FELYX85 has 7 current inputs (A). Refer to the part number being used, and see the FELYX catalog for the channel details of each model.**
{% endhint %}

By default, all analog values are measured with respect to ground (GND).

FELYX also supports:

* Low voltage range of 0-2.5V with respect to ground, by changing the ADC gain.
* 0-250mV range using differential voltage between two terminals.

These options are covered in the Advanced Analog Settings section.

{% hint style="info" %}
Important: Always make sure that the correct voltage or current is given to each analog terminal. For example, do not connect more than 5V to a C terminal or more than 20mA to an A terminal. FELYX has suitable fuses, but incorrect usage may damage the analog input.
{% endhint %}

### Step#1 Enable Analog Inputs

The actual analog channel configuration is carried out and saved separately through the **Analog Wizard**. However, the device will process analog inputs only when the **Analog Inputs** checkbox is enabled under Feature Settings.

Therefore, this checkbox acts as the **master enable** for analog input processing.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fw4M4q0VtSSUB8T6fL3eP%2F14.jpg?alt=media&amp;token=b45b9804-41b5-4cb2-9e73-43e71e445328" alt=""><figcaption></figcaption></figure>

#### Step 2: Open the Analog Wizard

Go to the **Analog** page under **Sensor Settings**.

Under **Analog Input Configuration**, click **Open Analog Wizard**.

Similar to other configurable FELYX features, all analog channel settings are managed through this wizard rather than directly on the main configuration page.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FElOfxIKjGZgR28C6LNd1%2F15.jpg?alt=media&amp;token=1d042652-e872-4e55-96a2-bb8457b8a937" alt=""><figcaption></figcaption></figure>

#### Step 3: Configure the Analog Channels

The **Channel Matrix** page of the Analog Wizard displays all available analog channels and their configuration parameters.

For each channel, the user can:

* **Enable** or disable the individual channel.
* Select the required **Topology** according to the available hardware input.
* Define the **Input Min–Max** range.
* Define the corresponding **Output Min–Max** range.
* Apply a **Multiplier**, if required.
* Assign a **Variable** name.
* Assign an optional **Backup Variable**.

After completing the configuration, click **Save & Close** to save the Analog Wizard settings.

Only channels whose individual **Enable** checkbox is selected will be processed, provided that the main **Analog Inputs** feature has also been enabled under Device Settings.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FA3pbWS3BkGcCZWDN2qiq%2F16.jpg?alt=media&amp;token=31aa313a-2587-4410-85f2-82e66a4e46d9" alt=""><figcaption></figcaption></figure>


# SDI-12

FELYX supports **SDI-12 sensors** for environmental, hydrology, agriculture and weather monitoring applications. SDI-12 provides a simple digital interface for connecting compatible multi-parameter sensors to the data logger.

For wiring, sensor setup, variable mapping and verification, refer to the [**SDI-12 Sensor Configuration**](/pf) documentation

Typical applications include:

* Soil moisture and soil temperature
* Water level and hydrology sensors
* Weather and environmental instruments
* Agricultural monitoring
* Multi-parameter SDI-12 probes

### SDI-12 Tool

YuDash also provides an **SDI-12 Tool** for sensor commissioning, testing and troubleshooting

{% embed url="<https://youtu.be/rb-zh083QQ8>" %}

&#x20;

####

#### Sensor Recipes

{% hint style="info" %}
Support for reusable **SDI-12 Sensor Recipes** is available for quicker deployment of commonly used sensors.&#x20;
{% endhint %}


# Network and Cloud


# Edge Processing


# System Features


# NUREX

## YuDash NUREX AIoT Data logger <a href="#h.4p90d3pdegr5_l" id="h.4p90d3pdegr5_l"></a>

YuDash **NUREX** is a next-generation **AI-enabled Edge Data Logger** designed for mission-critical industrial and environmental monitoring applications. Built for reliability, compliance, and long-term field deployment, NUREX bridges the gap between raw sensor data and actionable intelligence—directly at the edge.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYbUbfOHy34trBZ8vgQ3x%2FYuDash_NUREX_Datalogger.jpg?alt=media&amp;token=b0fb2896-dd20-4bb7-8d00-00d66a3a763c" alt=""><figcaption></figcaption></figure>

Engineered for **emission monitoring, environmental compliance, and complex industrial use-cases**, NUREX processes, validates, and secures data locally before transmitting it to cloud or regulatory systems. This approach ensures higher data integrity, reduced latency, and continued operation even under intermittent network conditions.

At its core, NUREX combines **edge AI capabilities**, **multi-protocol industrial connectivity**, and **secure data handling** into a single compact platform. It supports diverse field instruments and protocols while enabling advanced logic, calculations, and contextual decision-making at the device level—unlocking new use-cases beyond traditional data logging.

NUREX is fully aligned with **CPCB OCEMS requirements**, making it suitable for regulated emission and pollution monitoring deployments across industries. With built-in support for secure APIs, encrypted communication, and scalable architecture, it is equally prepared for enterprise, government, and OEM deployments.

Designed and built in India, NUREX reflects a strong focus on **robust engineering, long lifecycle support, and adaptability**—empowering industries to move from simple data collection to **intelligent edge-driven operations**.&#x20;

## NUREX Product Variants <a href="#lynxpartnumbers" id="lynxpartnumbers"></a>

## YuDash NUREX44 Data Logger&#x20;

**1) Core Processor**

* Quad‑core Arm® Cortex®‑A55 (Armv8 64bit @ 1.6 GHz)
* AI GPU: Arm® Mali™‑G52‑2EE
* 1GB LPDDR4 RAM (or higher)

**2) Storage**

* 16 GB / 8GB storage (Industrial SD card / eMMC)

**3) Ethernet (as per part number)**

* Direct RJ45 port OR&#x20;
* USB type-C (use with USB to Ethernet converter)

**4) 4G/LTE Connectivity (as per part number)**

**5) Modbus/RS485 (dual ports)**&#x20;

* Each port can be configured as Modbus RTU Master or slave.

**6) Analog Inputs (4-20 mA)**&#x20;

* 4 channel Analog Inputs (4-20mA/0-20mA).
* 16 bit high precision ADC

**7) Digital Input for Tipping bucket rain gauge**

### NUREX44 Part Numbers

<table><thead><tr><th width="154.75">Part No</th><th width="124">Short Part No.</th><th width="134.5">Ethernet/USB </th><th width="108">4G/LTE</th><th width="108">RAM</th><th width="86">Storage</th></tr></thead><tbody><tr><td>NUREX44LA1016</td><td>NUREX44</td><td>RJ45</td><td>India (Asia)</td><td>1 GB</td><td>16 GB</td></tr><tr><td>NUREX44UA1016</td><td>NUREX44U</td><td>USB</td><td>India (Asia)</td><td>1 GB</td><td>16 GB</td></tr></tbody></table>

## User Manual Overview

The NUREX user manual covers the following sections:

* NUREX Terminals, connections and wiring
* NUREX configuration for various aspects.&#x20;

{% hint style="info" %}
As the NUREX UI is continuously evolving, some of interfaces in your product may be slightly different from the ones in manual.
{% endhint %}


# NUREX Interfaces

## YuDash NUREX Terminals

#### Front View of NUREX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FEWxOScHYPY5l1sH5qeqx%2F1.png?alt=media&amp;token=2bd3a1cc-f110-40b0-8788-eed86431fd03" alt=""><figcaption></figcaption></figure>

#### Terminal view of NUREX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FaXNogP67ihsTe3zyBWdv%2F2.png?alt=media&amp;token=6aa66fe5-05b9-41e1-b587-30e4c5e94040" alt=""><figcaption></figcaption></figure>

### NUREX Network Ports

NUREX is available in two hardware variants, differentiated by their network interface:

* **NUREX44** – Equipped with a dedicated **Ethernet (LAN) port** for wired network connectivity.
* **NUREX44U** – Equipped with a **USB Type-C port** for network connectivity via USB.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fn1t0E4vwcjvktUI626TJ%2FNUREX_HelpPages.png?alt=media&amp;token=90d5028b-dc03-43e3-acd3-16ac271b595c" alt=""><figcaption></figcaption></figure>

### NUREX44 Network ports

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2Q6rBh25oK7K1ggPtZlc%2F6.png?alt=media&amp;token=dd5eefe3-fa9b-4002-b8bf-d76a04bc6871" alt=""><figcaption></figcaption></figure>

### NUREX44 Top view (4G antenna and RJ45 jack)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FXHCG7kYfQUvU5sEzuyT5%2F3.png?alt=media&amp;token=f368b9fc-a3ec-4963-be39-4485d77a46f0" alt=""><figcaption><p>NUREX</p></figcaption></figure>

### NUREX44U Network ports

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FjdSO6o4VxVfSwJDDBmuF%2F7.png?alt=media&amp;token=ba17d04c-21cd-4b7c-b12d-c286b87fb303" alt=""><figcaption></figcaption></figure>

### NUREX44U Top view (USB-C and 4G antenna)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F54e01RS7It1fTVQMZwA6%2F4.png?alt=media&amp;token=61d6f363-46d6-44c5-94dc-5269c8a6fd1c" alt=""><figcaption></figcaption></figure>

### NUREX Right side view (4G SIM slot)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FbuoIHm7auG6PctHIMIBX%2F5.png?alt=media&amp;token=3f06b6e1-84de-45f1-bd27-a98322bd4031" alt=""><figcaption></figcaption></figure>

## NUREX Connection Examples

### NUREX Terminal Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FZLzQLdqjHnTuymADzsjf%2F8.png?alt=media&amp;token=3edd0069-20b3-4e83-ae55-fb167d1d7ab8" alt=""><figcaption></figcaption></figure>

### NUREX SIM card

{% embed url="<https://youtu.be/EuAuaKj2b9E>" %}


# NUREX User Manual

NUREX is configured through ethernet port.&#x20;

{% hint style="info" %}
MAC address of NUREX is required for use of data loggers in enterprise networks for security purpose. The MAC address is required for "White Listing" of the gateway.&#x20;

In some cases, MAC address and static IP of device is tightly coupled to gain access to the network.&#x20;
{% endhint %}


# NUREX Configuration

NUREX is configured primarily through Ethernet port

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FFJXOxpp6GCTpPSUzoHwF%2FYuDash_NUREX_ConfigPage_LAN_June25%20(1).png?alt=media&amp;token=3cbecc4d-fc15-4a9e-b624-b190a3089323" alt=""><figcaption></figcaption></figure>

####

Following are the list of sections in Configuration page. These are documented as part of LYNX manual or separate integration guides.

#### [Modbus RS485 Settings](/yudash-iot-products/lynx/lynx-settings/modbus-rs485)

#### [Analog Input Settings](/yudash-iot-products/lynx/lynx-settings/analog-inputs)

#### [DataScale Settings](/yudash-iot-products/lynx/lynx-settings/data-scaling)

#### [Advance Feature Settings](#advance-feature-settings)

1. RTC Settings
2. Network Failure Handler Settings
3. YuReCon Settings

#### [Custom Cloud Server Settings](broken://pages/MtQxVQEesZPdMOFNMBWO)

#### [Payload Settings](/pf/ct/payload)

#### [Ethernet Settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings)

#### [Modbus TCP Settings](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip)

#### HTML Parser Settings

#### SNMP Settings

{% hint style="info" %}
MAC address of NUREX is required for use of data logger in enterprise networks for security purpose. The MAC address is required for "White Listing" of the data logger.&#x20;

In some cases, MAC address and static IP of device is tightly coupled to gain access to the network.&#x20;
{% endhint %}


# Network Setttings

NUREX is configured primarily through Ethernet port

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FFJXOxpp6GCTpPSUzoHwF%2FYuDash_NUREX_ConfigPage_LAN_June25%20(1).png?alt=media&amp;token=3cbecc4d-fc15-4a9e-b624-b190a3089323" alt=""><figcaption></figcaption></figure>

####

Following are the list of sections in Configuration page. These are documented as part of LYNX manual or separate integration guides.

#### [Modbus RS485 Settings](/yudash-iot-products/lynx/lynx-settings/modbus-rs485)

#### [Analog Input Settings](/yudash-iot-products/lynx/lynx-settings/analog-inputs)

#### [DataScale Settings](/yudash-iot-products/lynx/lynx-settings/data-scaling)

#### [Advance Feature Settings](#advance-feature-settings)

1. RTC Settings
2. Network Failure Handler Settings
3. YuReCon Settings

#### [Custom Cloud Server Settings](broken://pages/MtQxVQEesZPdMOFNMBWO)

#### [Payload Settings](/pf/ct/payload)

#### [Ethernet Settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings)

#### [Modbus TCP Settings](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip)

#### HTML Parser Settings

#### SNMP Settings

{% hint style="info" %}
MAC address of NUREX is required for use of data logger in enterprise networks for security purpose. The MAC address is required for "White Listing" of the data logger.&#x20;

In some cases, MAC address and static IP of device is tightly coupled to gain access to the network.&#x20;
{% endhint %}


# Main Settings

NUREX is configured primarily through Ethernet port

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FFJXOxpp6GCTpPSUzoHwF%2FYuDash_NUREX_ConfigPage_LAN_June25%20(1).png?alt=media&amp;token=3cbecc4d-fc15-4a9e-b624-b190a3089323" alt=""><figcaption></figcaption></figure>

####

Following are the list of sections in Configuration page. These are documented as part of LYNX manual or separate integration guides.

#### [Modbus RS485 Settings](/yudash-iot-products/lynx/lynx-settings/modbus-rs485)

#### [Analog Input Settings](/yudash-iot-products/lynx/lynx-settings/analog-inputs)

#### [DataScale Settings](/yudash-iot-products/lynx/lynx-settings/data-scaling)

#### [Advance Feature Settings](#advance-feature-settings)

1. RTC Settings
2. Network Failure Handler Settings
3. YuReCon Settings

#### [Custom Cloud Server Settings](broken://pages/MtQxVQEesZPdMOFNMBWO)

#### [Payload Settings](/pf/ct/payload)

#### [Ethernet Settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings)

#### [Modbus TCP Settings](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip)

#### HTML Parser Settings

#### SNMP Settings

{% hint style="info" %}
MAC address of NUREX is required for use of data logger in enterprise networks for security purpose. The MAC address is required for "White Listing" of the data logger.&#x20;

In some cases, MAC address and static IP of device is tightly coupled to gain access to the network.&#x20;
{% endhint %}


# Ethernet Settings

NUREX has ethernet (RJ45) as optional hardware feature depending on part number. Please refer to [LYNX ethernet settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings) for further details.


# Modbus RS485

Modbus/RS485 is a popular serial protocol to read various sensors. YuDash NUREX is being used to read a variety of instruments, sensors and PLCs for various applications. NUREX provides easy to configure approach for reading field Modbus instruments. Following are the key information points required for a successful read of instrument through Modbus:

1. Baudrate
2. Data Bits, Parity and Stop Bit
3. Slave ID of instrument
4. Modbus register information to read:
   1. Modbus register numbers and types)
   2. Modbus register data types (Size: integer/float/real. Byte swapping information: LSB/MSB etc.)
5. Modbus register address.

## Modbus Register Mapping in YuDash NUREX. <a href="#h.jt0n9eorg4hg_l" id="h.jt0n9eorg4hg_l"></a>

Various Modbus topologies are covered in [Modbus protocol](/pf/af/mt) documentation.

## Modbus/RS485 interfacing example

YuDash NUREX datalogger is connected with Selec EM2M energy meter on Modbus channel#1&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMLRFUEf8g02sid35HLvS%2F10.jpg?alt=media&amp;token=468bb2ee-7665-48eb-b308-eec8fc5910e7" alt=""><figcaption></figcaption></figure>

## Modbus/RS485 interfacing example (2channels)

YuDash NUREX datalogger is connected with Selec EM2M energy meter on Modbus channel#1 and XY-02 temperature and humidity sensor on Modbus Channel#2.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F60U5dIKuYDsLcDQ0YGWR%2F11.jpg?alt=media&amp;token=868fb09c-be2b-48de-8810-4d5de8c64fe4" alt=""><figcaption></figcaption></figure>


# Analog Inputs

NUREX44 supports 4 channel of 0-20mA read. The terminals A1 to A4 terminals are available for 4 channels of analog.

In most of industrial applications, 4-20mA values are mapped to given process values. NUREX has advanced data scaling features to handle process values of different applications.

While user can perform scaling within Analog Inputs, we recommend using generic [**Data Scaling**](/yudash-iot-products/lynx/lynx-settings/data-scaling) section for analog data interpolation.

### Analog Input Source Wiring

There are 4 analog inputs (A1, A2, A3 and A4) terminals along with two GND terminals.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fs1O1sbthtMxRiXXEXdyd%2Fanalog_wiring.jpg?alt=media&amp;token=b177a4f4-2b3e-4c24-8433-524a61e6154f" alt=""><figcaption></figcaption></figure>


# Data Scaling

Please refer to [Data Scaling section of LYNX](/yudash-iot-products/lynx/lynx-settings/data-scaling).


# Modbus TCP/IP

YuDash NUREX supports Modbus TCP/IP to read various PLC/HMIs through ethernet.  Please refer to [LYNX Modbus TCP/IP](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip) documentation.


# HTML Parser

YuDash NUREX supports Modbus TCP/IP to read various PLC/HMIs through ethernet.  Please refer to [LYNX Modbus TCP/IP](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip) documentation.


# Modbus Server

YuDash NUREX supports Modbus TCP/IP to read various PLC/HMIs through ethernet.  Please refer to [LYNX Modbus TCP/IP](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip) documentation.


# Multi-API

NUREX has ethernet (RJ45) as optional hardware feature depending on part number. Please refer to [LYNX ethernet settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings) for further details.


# Advance Features

The **Advance Feature Settings** contains a group of features for fine tuning of NUREX for specific use-cases.&#x20;

Please refer to [LYNX Advance Feature Settings](/yudash-iot-products/lynx/lynx-settings/advance-feature-settings).

&#x20;


# System Tools

The **Advance Feature Settings** contains a group of features for fine tuning of NUREX for specific use-cases.&#x20;

Please refer to [LYNX Advance Feature Settings](/yudash-iot-products/lynx/lynx-settings/advance-feature-settings).

&#x20;


# Data Logger

The **Advance Feature Settings** contains a group of features for fine tuning of NUREX for specific use-cases.&#x20;

Please refer to [LYNX Advance Feature Settings](/yudash-iot-products/lynx/lynx-settings/advance-feature-settings).

&#x20;


# Custom Cloud

Pleaser refer to [YuDash Device to Cloud API](broken://pages/u5xHPU0L7MiYQrQY2GFF) for Cloud and Payload Settings.


# NUREX for CEMS

NUREX is fully aligned with **CPCB OCEMS requirements**, making it suitable for regulated emission and pollution monitoring deployments across industries. With built-in support for secure APIs, encrypted communication, and scalable architecture, it is equally prepared for enterprise, government, and OEM deployments.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fpwnx3VGjLWWEeelzU7sB%2FYuDash_NUREX_CEMS.png?alt=media&amp;token=df9e422e-8370-4169-842e-6db479ecc037" alt=""><figcaption></figcaption></figure>


# CPCB

YuDash NUREX supports real-time data push to the **Central Pollution Control Board (CPCB)** Online Continuous Emission/Effluent Monitoring System (OCEMS) portal at `cems.cpcb.gov.in`. This is the national regulatory requirement for industries under CPCB monitoring.

NUREX implements the **CPCB 2025 API** with AES-256 encryption as mandated by CPCB guidelines. Data is pushed at configurable intervals (typically every 15 minutes) directly from the NUREX device to the CPCB server. Please refere to following link for CPCB OCEMS documentaton:

<https://cems.cpcb.gov.in/#/p/login>

***

## Required CPCB credentials for Configuration

Before configuring NUREX, you must have completed registration on the CPCB OCEMS portal and received the following credentials:

### 1) CPCB Tokens

Following is a sample set of credentials received from CEMS CPCB authority after your industry is registered on the OCEMS portal. This email contains all the credentials needed to configure NUREX. Note down the following from this email:

* **Industry Id** — your industry registration ID
* **Device ID** — unique device identifier assigned by CPCB
* **Station Id** — monitoring station identifier
* **Token Id** — authentication token used for AES-256 encryption

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FV9rstBvar0iWkFYy55fl%2F1.png?alt=media&amp;token=bc564add-edc4-4bd5-b1dd-c183a19d2c4e" alt=""><figcaption></figcaption></figure>

***

### 2) CPCB Industry Key&#x20;

The industry Key has to be downloaded from relevant **Industry Key Generation** section in the CEMS portal. Following is sample industry key download snippet:

Log in to `cems.cpcb.gov.in` and navigate to **Industry Key Generation** from the left sidebar.  The public key dialog will appear showing the RSA public key in PEM format. Click **Copy Key** to copy the full key text to your clipboard — you will paste this into NUREX in a later step.

{% hint style="info" %}
You need to click **Generate New Key** if no key exists. This step may lose all created devices. So, it is advisable to have the Industy Key generated before stations and devices are added.
{% endhint %}

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FOMnQBcmGEw9ZRs9gWQgO%2F2.png?alt=media&amp;token=d491fdb6-1217-48d9-a2a6-07ee4ea81860" alt=""><figcaption></figcaption></figure>

### 3) Approved Parameter List

Only the approved parameters for a given station can be pushed to CPCB portal. The name of parameters and applicable units should be available for given station.

***

## NUREX Device Configuration for CPCB

CPCB push is configured under **Multi-API mode** in the NUREX configuration page. This allows CPCB push to run alongside other API cloud destinations (MQTT, HTTP, FTP) simultaneously.

#### Step 1 — Select Multi-API Cloud Mode

Open the NUREX configuration page at `http://<NUREX-IP>/api/config` and click **Multi-API Settings** from the left sidebar. The **Multi-Cloud API Settings** panel will appear. In the **Add API** row, enter a name for this API entry (e.g. `cpcb`) in the name field, then click the **Select API** dropdown.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FqctbJnUpQXXVDItcE3ba%2F3.png?alt=media&amp;token=96bd5cfb-e097-45ed-b1ab-d7367e12abff" alt=""><figcaption></figcaption></figure>

***

#### Step 2 — Select CPCB from the API List

The API type dropdown shows all supported PCB and cloud APIs. Select **Central CPCB (CEMS)** from the list. Other state PCB options (Tamil Nadu, Haryana, Punjab, Maharashtra, Madhya Pradesh, etc.) are also available for specific part number.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FqFcTqnEwe0mMv420x6wp%2F4.png?alt=media&amp;token=0fb79328-a4b6-4fe1-a4c2-d9a7cc04596a" alt=""><figcaption></figcaption></figure>

***

#### Step 3 — Add CPCB API in the API list

With the name set to cpcb and Central CPCB (CEMS) selected, click the Add button. This creates the CPCB API entry as Seq#1 in your Multi-API configuration.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FhZ8cZ6Y0M4GCeO1qMKt8%2F5.png?alt=media&amp;token=75a0230e-9a09-4af4-b02f-923882a28008" alt=""><figcaption></figcaption></figure>

After adding, the **CPCB Configuration** panel appears. This panel has three fields to fill:

* **Device ID** — from the CPCB approval email
* **Station ID** — from the CPCB approval email
* **Token ID** — from the CPCB approval email

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FuCs87E3E35viOxPcps3K%2F6.png?alt=media&amp;token=0b072643-41e0-4fb6-9d36-979d8b9e5bed" alt=""><figcaption></figcaption></figure>

#### Step 4 — Enter Token Settings

Enter the **Device ID**, **Station ID**, and **Token ID** exactly as received in the CPCB approval email. Once filled, click **Manage Industry Key** to open the public key dialog where you will paste the key copied from the CPCB portal.

Click **Populate & Verify JSON** after filling the fields to generate and validate the configuration.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYQo0k2Qc2CcjDUts6YOE%2F7.png?alt=media&amp;token=039542a9-f4d0-4bf1-892b-be86d703e2b3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
The **Data Pause** option controls whether NUREX pauses data submission — leave it on **Never** for continuous monitoring. Use **On DI1** if you have a physical pause signal from your instrument system.
{% endhint %}

#### Step 5 — Enter Industry Key

Once filled, click **Manage Industry Key** to open the public key dialog where you will paste the key copied from the CPCB portal.

The **Industry Key** dialog shows the file location where the key will be saved on NUREX (`api directory/cpcb/public.pem`). Paste the full public key text copied from the CPCB portal — it must include the `-----BEGIN PUBLIC KEY-----` and `-----END PUBLIC KEY-----` lines.&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FaYjBRuvm3yjpcwAwU1Mj%2F8.png?alt=media&amp;token=5fcf0169-f7ae-48f2-a0bb-49139597cd40" alt=""><figcaption></figcaption></figure>

NUREX confirms with a **"Public Key saved successfully!"** message. The key is now stored on the device at `api directory/cpcb/public.pem` and will be used automatically for AES-256 encryption of all data sent to the CPCB server. Click **OK** to close.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FH9K6Fb1BWPMdSNicubiR%2F9.png?alt=media&amp;token=b3672c76-bad7-455d-bb16-80f6f391ac8c" alt=""><figcaption></figcaption></figure>

#### Step 6 — Device Registration with CPCB portal

{% hint style="info" %}
This step registers data logger with the CPCB ODAMS server and sets up a periodic heartbeat. It is required for full CPCB compliance but may not needed for basic data push to start.
{% endhint %}

{% hint style="info" %}
**Disclaimer:** If the registration process stops or fails midway, it may not be possible to re-run it for the same Device ID. YuDash provides the registration wizard as a convenience mechanism and has no control over the CPCB registration software or server behavior. YuDash cannot provide support for registration failures — please contact CPCB directly in such cases.
{% endhint %}

After entering credentials and saving the Industry Key, click **Open Registration Wizard** under the **Device Registration** row. This opens the registration page in a new browser tab.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FyhaQ8oI6UILUBDSNJ5fR%2F10.png?alt=media&amp;token=395c3ab3-c383-4ee3-92b6-6fb067dcb543" alt=""><figcaption></figcaption></figure>

> **Use LAN/Ethernet only for this step.** The registration process downloads software components from the CPCB server. 4G/Mobile connections may cause timeouts and incomplete registration. Connect NUREX to a stable wired internet connection before proceeding.

The **Device Registration: cpcb** page loads with two steps. The Device ID and Token ID are automatically pre-filled from your saved configuration.

Download the CPCB registration executable (`main` file) from the CPCB portal. Select the **Linux ARM64** version — this is the correct binary for NUREX hardware. Click **Choose File**, select the downloaded `main` file, and click **Upload File**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FM9gLbx7c5Kv9A30bu6Vd%2F12.png?alt=media&amp;token=4f10d6a0-8ff5-4152-838a-846f10f430f7" alt=""><figcaption></figcaption></figure>

Verify that the Device ID and Token ID are correctly shown. Click **Start Registration** to begin the process.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmLNYYK1VeQmY1d6ypupa%2F13.png?alt=media&amp;token=8230f0dc-72c1-4edd-9cef-e620b35dd8c8" alt=""><figcaption></figcaption></figure>

The terminal window shows the registration progress in real time. NUREX connects to the CPCB ODAMS server, sends the Device ID and Token, receives a unique **Machine ID**, and sets up a cron job for periodic heartbeat.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FjrxeCWfGMigoZpQ7gdYC%2F14.png?alt=media&amp;token=a3fe3f75-7be8-442d-98da-397ad9b41789" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4NGd4pQP8hySgbrmP6IT%2F15.png?alt=media&amp;token=619e2e75-2205-481e-b200-fae18d2ac11c" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
A successful registration ends with:

Response Status Code: success\
Device Register Successfully!\
Device Added Successfully
{% endhint %}

**Disclaimer:** If the registration process stops or fails midway, it may not be possible to re-run it for the same Device ID. YuDash provides the registration wizard as a convenience mechanism and has no control over the CPCB registration software or server behavior. YuDash cannot provide support for registration failures — please contact CPCB directly in such cases.

### Parameter Configuration & Data Flow&#x20;

This section explains the complete data flow from instrument to CPCB portal, using a 4-parameter effluent monitoring station as an example. In this example, four 4–20mA inputs are mapped to four CPCB approved parameters:

<table><thead><tr><th width="136">Channel</th><th width="94">Variable Name</th><th width="250">Parameter</th><th>Typical Unit</th></tr></thead><tbody><tr><td>Ch 1</td><td><code>bod</code></td><td>Biological Oxygen Demand</td><td>mg/L</td></tr><tr><td>Ch 2</td><td><code>cod</code></td><td>Chemical Oxygen Demand</td><td>mg/L</td></tr><tr><td>Ch 3</td><td><code>tss</code></td><td>Total Suspended Solids</td><td>mg/L</td></tr><tr><td>Ch 4</td><td><code>ph</code></td><td>pH</td><td>pH</td></tr></tbody></table>

Each variable read by NUREX must be named using the **exact CPCB approved parameter name** for your station. The variable name in NUREX is what gets sent to the CPCB portal — so it must match the approved parameter list precisely.

Input data can come from any source — Analog inputs, Modbus RS485, Modbus TCP/IP, or HTML Parser. In this example, four parameters are read from 4–20mA analog inputs.

{% hint style="info" %}
**The variable name must exactly match the CPCB approved parameter name — including lower/upper case.** For example, use `bod` not `BOD`, `ph` not `PH`. Only the approved parameters from NUREX master list are pushed to CPCB API, other parametersa are skipped. NUREX automatically assigns the correct unit for each recognised parameter — no manual unit entry is needed.
{% endhint %}

Open **Analog Input Settings → Open Analog Wizard → Channel Matrix**. Enable each channel, select the input topology (e.g. 0–20mA), and enter the **Variable name** using the exact CPCB approved parameter name for that channel.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2qcT59hAtI9OnMnantXQ%2F17.png?alt=media&amp;token=31b7aee3-0940-4ac6-b295-e1caa16892db" alt=""><figcaption></figcaption></figure>

Open **DataScale Settings** and configure the input-to-output scaling for each variable. This converts the raw 4–20mA signal from the instrument into the actual engineering value sent to CPCB.

!\[Image 18 — Data Scale Settings showing scaling for bod, cod, tss, ph with Variable Name column highlighted]

In this example:

* `bod`, `cod` — 4–20mA input mapped to 0–300 mg/L output, cutoff –1 to 300
* `tss` — 4–20mA input mapped to 0–150 mg/L output, cutoff –1 to 150
* `ph` — 4–20mA input mapped to 0–14 pH output, cutoff –1 to 14

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FwE4NtZMJevhXPv35rLyv%2F18.png?alt=media&amp;token=b968ec09-b905-4a9a-8053-0d665cd4db4e" alt=""><figcaption></figcaption></figure>

Enable the **Enable Scaling Flag** for each active variable. NUREX sends the scaled output value to CPCB — units are automatically applied based on the parameter name.

{% hint style="info" %}
If your approved parameter is not in the NUREX default list, or CPCB has specified a non-standard unit for your station, NUREX supports custom parameter addition and unit override. Contact [YuDash support](mailto:info@yudash.com) for assistance
{% endhint %}

### Data Push Timing & Averaging

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FfE2slRXGz7ypa3t2H6qu%2F16.png?alt=media&amp;token=da574774-076a-4a12-8c73-172cad0e80dc" alt=""><figcaption></figcaption></figure>

CPCB guidelines require data to be submitted at **15-minute intervals**, exactly at **xx:00, xx:15, xx:30, and xx:45** of each hour. Each submission must represent the **average of per-minute readings** over that 15-minute window (15 samples per push).

NUREX handles this automatically:

* Set **TimeSync Run (Minute)** to `1` so that NUREX reads the input parameter every 1 minute.
* NUREX internally averages the 15 per-minute readings and pushes the result at each 15-minute boundary
* The averaging window and push timing are managed by the NUREX CPCB API — no manual configuration is needed. There is option to over-rider the averaging mechanism.

### Security & Encryption

All data transmitted from NUREX to the CPCB OCEMS portal is protected by the encryption and authentication framework mandated under the CPCB 2025 API guidelines:

* **AES-256-CBC encryption** — every data payload is encrypted using the industry-specific RSA public key obtained from the CPCB portal before transmission
* **Token-based authentication** — each request is authenticated using the unique Token ID issued by CPCB, ensuring only registered devices can submit data for a given station
* **HTTPS transport** — all communication with `cems.cpcb.gov.in` is over TLS-secured HTTPS, preventing interception or tampering in transit
* **Device binding** — the Machine ID assigned during device registration ties the NUREX unit to the specific CPCB device record, preventing unauthorized substitution

The entire security layer — key management, payload encryption, token handling, and secure transmission — is handled automatically by NUREX firmware based on the credentials provided during configuration. No additional security configuration is required from the user.

***

## Troubleshooting

***

## YuDash CEMS and AKSH Platform


# ZENYX

## YuDash ZENYX Overview <a href="#h.4p90d3pdegr5_l" id="h.4p90d3pdegr5_l"></a>

YuDash ZENYX is compact Industrial IoT Gateway, part of YuDash IoT Gateways and Data Loggers. It provides a flexible cloud connectivity to industrial and environmental instruments, PLC/HMIs and equipment. It supports a host of industrial protocols, including Modbus RS485, MODBUS TCP/IP, analog inputs. ZENYX acts as Modbus master and reads up to 96 parameters across 16 Modbus slaves. Four analog channels (0-20/4-20mA) are supported. ZENYX can connect to network (LAN or Cloud) through 4G/LTE, Ethernet and Wi Fi. ZENYX communicates with IoT platforms through MQTT, HTTP and FTP protocols. Effectively, any IoT platform can be connected using inbuilt JSON payload format library. It also has payload generator engine to support custom text and CSV payload.

ZENYX can be easily configured in web-browser through laptop or mobile phone. On-device OLED display shows running status and simplifies deployment and debugging. Advanced features like input data scaling, two-way communication through Modbus-write, low power variants are available to support various use-cases. JSON based configuration backup and restoration aids deployment at scale. Product variants with subset of features are available for a cost-effective IoT gateway depending on application.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMSvixJWWcNxFKG6mdWcy%2F15.png?alt=media&amp;token=674c4aab-76ad-43da-8abe-9beb153ee920" alt=""><figcaption></figcaption></figure>

### Key Features

* Easy to configure gateway over local Wi-Fi
* Configurable through JSON file for mass deployments
* On-device OLED for status and fault detection
* Data Scaling feature to map inputs to required process parameters
* Configurable looping cycles (10 second to 1 day).
* Auto Reboot options
* Low Power version with deep-sleep
* Network failure handler: local storage and back-filling

### **Technical Specifications**

* Input Power: 24V DC Standard (12-28V)
* DIN Rail / Wall mounting
* 50 x 110 x 65mm
* ABS plastic enclosure with IP30 rating
* On device OLED display
* Weight: 210 grams approx.
* SMA female connector for external 4G/LTE Antenna
* Micro SIM card slot

### **Cloud Connectivity Options**

* 4G/LTE
* Ethernet
* Wi-Fi

### **Supported Industrial Protocols:**

* Modbus RS485
* Modbus TCP/IP
* Analog Inputs

### **Cloud Protocols:**

* MQTT
* HTTPS (REST API)

**Payload Formats**

* JSON: ZENYX has multiple inbuilt JSON payload formats to support various IoT platforms.
* TEXT: Inbuilt payload generator for custom text and CSV formats.

## ZENYX Product Variants <a href="#lynxpartnumbers" id="lynxpartnumbers"></a>

### YuDash ZENYX IoT Gateway Part Numbers

<table><thead><tr><th width="126">Part No</th><th width="92" data-type="checkbox">4G/LTE</th><th width="107" data-type="checkbox">Ethernet</th><th width="93" data-type="checkbox">RS485</th><th width="108" data-type="checkbox">Analog</th><th width="86" data-type="checkbox">RTC</th><th data-type="checkbox">Data Logging</th></tr></thead><tbody><tr><td>ZENYX44</td><td>true</td><td>true</td><td>true</td><td>true</td><td>true</td><td>false</td></tr><tr><td>ZENYX46</td><td>false</td><td>true</td><td>true</td><td>true</td><td>true</td><td>true</td></tr></tbody></table>

* Wi-Fi network connectivity common across all IoT Gateways.
* RTC is standard feature across all variants.

## User Manual Overview

The ZENYX user manual covers the following sections:

* ZENYX Terminals, connections and wiring
* ZENYX configuration for various aspects.&#x20;
* In most of the cases, relevant sections of [LYNX documentation](/yudash-iot-products/lynx) is referenced.
* Refer to [YuDash Devices Features & APIs](broken://pages/BXY6T8tLZtquDeI4XAGm) for protocol specific features.

{% hint style="info" %}
As the ZENYX/LYNX UI is continuously evolving, some of interfaces in your product may be slightly different from the ones in manual.
{% endhint %}


# ZENYX Interfaces

## Introduction

## YuDash ZENYX Terminals

Front View of ZENYX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMSvixJWWcNxFKG6mdWcy%2F15.png?alt=media&amp;token=674c4aab-76ad-43da-8abe-9beb153ee920" alt=""><figcaption></figcaption></figure>

Terminal view of ZENYX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FXKefazZZpk66tcTLL4Z3%2F16.png?alt=media&amp;token=8986a6d7-28fa-4b0d-a688-81f6909e060a" alt=""><figcaption><p>ZENYX terminals (standard version)</p></figcaption></figure>

## ZENYX Power Connection

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FsXib5cRZOL348TzSiWDX%2F20.png?alt=media&amp;token=d40a0efc-73d5-4745-9e5b-87779cda7209" alt=""><figcaption></figcaption></figure>

ZENYX is powered by 24V External Supply (red and black wire in the image below).

## ZENYX Peripheral Inputs

Besides wire terminals, ZENYX has various input connections, as represented below:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FJlGztjBXftUbAtXRRug8%2F17.png?alt=media&amp;token=b70e5da4-be36-45b4-8dca-920260b83a26" alt=""><figcaption></figcaption></figure>

##

## 4G/LTE SIM card Slot

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4H7wFUyqRILlbBmfMTCG%2F19.png?alt=media&amp;token=cc51c386-bde9-4b5f-9317-eea84728a0e7" alt=""><figcaption></figcaption></figure>

## Ethernet LAN connection

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FrJuSYdlpH5QXFY0vnDdI%2F18.png?alt=media&amp;token=79340707-dd00-49ef-9428-0e44da6b775a" alt=""><figcaption></figcaption></figure>

## ZENYX Terminal Wiring Examples

## Modbus RS485 Wiring

Modbus (A and B) terminals of ZENYX are connected to yellow and green wires respectively.&#x20;

12/24V DC +/- power terminals are connected to red and black wires respectively.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FUSo0GcjyE4aCE2Jb1HCb%2F21.png?alt=media&amp;token=10cd4823-997f-4e89-ae2a-3ffc5b750ab8" alt=""><figcaption></figcaption></figure>


# ZENYX Configuration

ZENYX is configured through Wi-Fi using a laptop, tablet or mobile phone. There is no need to install any software or LAN wiring.

Following are 3 simple steps to initiate ZENYX configuration.

**Step 1**: On ZENYX bootup, the device waits for 5 seconds for user to start configuration server. The ZENYX screen shows the following message (with countdown from 5 to 0):

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F9C5XJX7EOkwFjLOqYaq1%2F28.jpg?alt=media&amp;token=b2ced3e2-71d4-4962-b46d-54923373f2a6" alt=""><figcaption></figcaption></figure>

During the countdown, short press the Config button (present on top left side) to start the configuration server.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FpbmBdyU60xd3AYmIvHof%2F22.png?alt=media&amp;token=1d54d801-68ca-4d80-89ed-c8010c690b4f" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Do not long press the Config Button. Just push and release!
{% endhint %}

**Step 2:** Once the button is pressed, the device will enter in AP (Access Point) mode, meaning a Wi-Fi network will be broadcasted. The Wi-Fi SSID name and password are displayed on the ZENYX screen. Connect the laptop to the given Wi-Fi.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Faczu4qVu9MQYy0ty35l8%2F30.jpg?alt=media&amp;token=9e4de019-2b69-4117-9d33-c9819653b070" alt=""><figcaption></figcaption></figure>

Details of Wi-Fi created by ZENYX are displayed on the ZENYX screen and are as follows:

1. Wi-Fi SSID: ***yu10001031***
2. Wi-Fi password: **12345678**
3. ZENYX IP address: ***192.168.4.1***

{% hint style="info" %}
**Troubleshooting Guide to connect to ZENYX Wi-Fi**

1\) In some cases, Wi-Fi may be shown as "Open network". In this case, no need to enter Wi-Fi password.

2\) At times, the Wi-Fi setting on laptop may be showing "Connecting.." instead of "Connected to Wi-Fi" after ZENYX Wi-Fi is selected. No need worry. Please open the Configuration URL (192.168.4.1) on laptop. It should simply open.

3\) In case of further trouble, please "Forget" any previously stored Wi-Fi names linked to ZENYX.
{% endhint %}

**Step 3:** This is how ZENYX configuration page looks like on laptop.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F8HBD9KBIQ448YHoPgHiS%2Fdevice_info.png?alt=media&amp;token=d065fdcd-9b5d-4e6d-afa0-77d550634359" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
While laptop is connected to local Wi-Fi of ZENYX, internet will not be accessible on the laptop.
{% endhint %}

ZENYX will keep the configuration server running for up to 5 minutes on inactivity. All ZENYX configuration will be done through this page as covered in subsequent sections.

**Following video explains the complete procedure to start ZENYX Configuration page**&#x20;

{% embed url="<https://youtu.be/wrpNlBjK4Fw>" %}

###

### ZENYX Configuration Sections

Following are the main sections in YuDash ZENYX Configuration page:

1. **ZENYX Device Information**: This is read-only section with ZENYX model, hardware and firmware information.
2. **Network Setting**: This section is used to configure network connectivity of ZENYX. Depending on model, ZENYX can connect to internet through (a) 4G/LTE (SIM card) (b) Wi-Fi or (c) Ethernet LAN. It can also work in offline mode (when it is used for local storage or display only).
3. **ZENYX Settings**: This is main section in which all features of ZENYX are configured. It includes (a) Data send frequency, (b) Feature enable/disable (given industrial protocol) and (c) Custom cloud selection. Detailed configuration of a given feature is done in subsequent sections.

### ZENYX Device Information <a href="#h.6jks5zwzrhq0_l" id="h.6jks5zwzrhq0_l"></a>

**ZENYX Device Information** read-only section with ZENYX model with following information:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F8HBD9KBIQ448YHoPgHiS%2Fdevice_info.png?alt=media&amp;token=d065fdcd-9b5d-4e6d-afa0-77d550634359" alt=""><figcaption></figcaption></figure>

1. **Part No**: The device part number.
2. **Serial No**: Unique serial number of the device.
3. **Hardware Ver**: Hardware PCB version.
4. **Firmware Ver**: ZENYX firmware version.
5. **Default Device Settings**: By default, each ZENYX gateway is pre-configured with "YuDash Cloud". Effectively, given IoT gateway is mapped to a unique "device" on YuDash IoT platform.
6. **Get Mac Address** **Button**: This button fetches the MAC address of the ZENYX IoT gateway. This MAC address is used for both Wi-Fi and Ethernet.&#x20;

{% hint style="info" %}
MAC address of ZENYX is required for use of IoT gateway in enterprise networks for security purpose. The MAC address is required for "White Listing" of the gateway.&#x20;

In some cases, MAC address and static IP of device is tightly coupled to gain access to the network.&#x20;
{% endhint %}


# Network Settings

**Network Settings** section deals with connection of ZENYX with the network. It is typically internet or local LAN in some cases. Depending on model, ZENYX supports the following options to connect to network.

1. **Wi-Fi**: ZENYX connects to a Wi-Fi network (router) to access the internet/local LAN. All models of ZENYX support connection to internet through Wi-Fi.
2. **Ethernet**: ZENYX connects to internet through Ethernet (RJ45 jack).
   * By default, it assumes DHCP connection (in which IP address is assigned by router). In this case, no further change in setting is needed.
   * ZENYX also supports static IP address configuration under advanced Ethernet settings.
3. **4G/LTE (Sim card)**: LYNX connects to internet through 4G/LTE SIM card.
   * Support of all 4G networks, independent of carriers. LYNX has been tested with all carriers in India.
   * Option to provide carrier APN. Though, this is not critical.
   * Support of external antenna for in-panel applications.
4. **None (Offline)**: ZENYX is not being connected to any network and is being used as display unit. This mode is also used for debugging purpose.

Please refer to [LYNX Network Setting](/yudash-iot-products/lynx/network-settings) page for further configuration steps.

## &#x20;<a href="#h.7essfeb8lo72_l" id="h.7essfeb8lo72_l"></a>


# ZENYX Settings

ZENYX settings are based on the LYNX IoT Gateway. Please refer to [LYNX settings](/yudash-iot-products/lynx/lynx-settings) for the configuration.

#### **Loading LYNX Settings from JSON in local laptop/PC.**

## ZENYX Features

ZENYX supports various integration with various industrial protocols and cloud platforms. Each feature is covered under a different section in configuration page. It is scrollable from left bar.

In most of cases, each section (or its sub-section) has an open, read and update button.&#x20;

Finally, one needs to do an "Update and Preview" and write to ZENYX, as explained in applicable LYNX tutorial.

For first time users, it is recommended to write to ZENYX, power cycle the device and verify that given changes were actually updated in device.

Following are the list of sections in Configuration page. These are documented as part of LYNX manual or separate integration guides.

#### [Modbus RS485 Settings](/yudash-iot-products/lynx/lynx-settings/modbus-rs485)

#### [Analog Input Settings](/yudash-iot-products/lynx/lynx-settings/analog-inputs)

#### [DataScale Settings](/yudash-iot-products/lynx/lynx-settings/data-scaling)

#### [Advance Feature Settings](#advance-feature-settings)

1. RTC Settings
2. Network Failure Handler Settings
3. YuReCon Settings

#### [Custom Cloud Server Settings](broken://pages/MtQxVQEesZPdMOFNMBWO)

#### [Payload Settings](/pf/ct/payload)

#### [Ethernet Settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings)

#### [Modbus TCP Settings](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip)

#### HTML Parser Settings

#### SNMP Settings

#### Extension Settings

1. Modbus RS485 Channel#2

#### 4G Modem Diagnostics

Each feature is accessible from The feature details are covered in subsequent sections

&#x20;

*


# Modbus RS485

Modbus/RS485 is a popular serial protocol to read various sensors. YuDash ZENYX is being used to read a variety of instruments, sensors and PLCs for various applications. LYNX provides easy to configure approach for reading field Modbus instruments. Following are the key information points required for a successful read of instrument through Modbus:

1. Baudrate
2. Data Bits, Parity and Stop Bit
3. Slave ID of instrument
4. Modbus register information to read:
   1. Modbus register numbers and types)
   2. Modbus register data types (Size: integer/float/real. Byte swapping information: LSB/MSB etc.)
5. Modbus register address.

## Modbus Register Mapping in YuDash ZENYX. <a href="#h.jt0n9eorg4hg_l" id="h.jt0n9eorg4hg_l"></a>

Refer to [LYNX Modbus RS485](/yudash-iot-products/lynx/lynx-settings/modbus-rs485) documentation for more details for Modbus settings.

Various Modbus topologies are covered in [Modbus protocol](/pf/af/mt) documentation.

## Modbus/RS485 interfacing example

YuDash ZENYX is connected with XY-MD02 temperature and humidity sensor through Modbus/RS485. Refer to [XY-MD02](/ig/in/process-control/temp+humidity-xy-md02) integration guide for register mapping.&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FbBKqZKe8zs6LBDsHCZNX%2Fzenyx_modbus1.jpg?alt=media&amp;token=3407b2e8-2d18-46fc-a654-76919ee0c5ed" alt=""><figcaption></figcaption></figure>


# Analog Inputs

Few variants of ZENYX support direct analog read inputs. ZENYX supports 4 channels of 0-20mA read. The terminals A1 to A4 terminals are available for 4 channels of analog.

In most of industrial applications, 4-20mA values are mapped to given process values. ZENYX has advanced data scaling features to handle process values of different applications.

While user can perform scaling within Analog Inputs, we recommend using generic [**Data Scaling**](/yudash-iot-products/lynx/lynx-settings/data-scaling) section of ZENYX/LYNX for analog data interpolation.

## Analog Input Settings

**Analog Inputs Settings** has 4 buttons for 4 channels, which can be enabled/disabled and configured independently.

**Analog Inputs** feature has to be enabled (check box) in LYNX Feature Settings to process analog channels.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F3Bx0CH8xBUTZty4ymLV6%2F1.png?alt=media&amp;token=ad2fdea3-b5b3-4cc7-b375-0ce9c65c95ad" alt=""><figcaption></figcaption></figure>

## Analog Input Configuration

1. A given analog channel (A1 to A4) has to be enabled by clicking the checkbox.
2. Output values ranges \[**minOutVal,** **maxOutVal]:** These are the output value ranges (minimum and maximum) of the analog module. These can be used for basic linear scaling of inputs. If set to \[0, 100], the analog output will be 0 to 100 for given input mA range (0-20).
3. Input current range \[**minmA, maxmA**]: This is the range of input milli Amperes to be read. For most of the applications, this should be 0 and 20. For instrument calibration, the maxmA may be set lower than 20 (say 19.8) to map to real-world process values.
4. **varName**: The variable name in which output value will be stored.
5. **varName2**: For analog inputs, this is optional additional variable name in which analog output will be stored. Keep it blank unless necessary.
6. **varFactor**: The output value will be multiplied by the varFactor. We will keep it 1.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FrZCyvfJ8T6E1S9hCRhEv%2F2.png?alt=media&amp;token=788e870e-3259-4bce-bff0-b285259210e9" alt=""><figcaption></figcaption></figure>

### Analog Input Source Wiring

There are 4 analog inputs (A1, A2, A3 and A4) terminals along with two GND terminals.

Sample connection of 4 analog sources connected to ZENYX. This is a typical scenario of ZENYX connected to environmental sensors with multiple analog outputs.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDNMiXhbuvDWeAD7HpcId%2Fanalog_terminals.jpg?alt=media&amp;token=26a26897-95f3-4268-b797-af8304c38308" alt=""><figcaption></figcaption></figure>


# Data Scaling

Please refer to [Data Scaling section of LYNX](/yudash-iot-products/lynx/lynx-settings/data-scaling).


# Advance Feature Settings

The **Advance Feature Settings** contains a group of features for fine tuning of ZENYX for specific use-cases.&#x20;

Please refer to [LYNX Advance Feature Settings](/yudash-iot-products/lynx/lynx-settings/advance-feature-settings).

&#x20;


# Cloud and Payload Settings

Pleaser refer to [YuDash Device to Cloud API](broken://pages/u5xHPU0L7MiYQrQY2GFF) for Cloud and Payload Settings.


# Ethernet Settings

ZENYX has ethernet (RJ45) as optional hardware feature depending on part number. Please refer to [LYNX ethernet settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings) for further details.


# Modbus TCP/IP

YuDash ZENYX supports Modbus TCP/IP to read various PLC/HMIs through ethernet.  Please refer to [LYNX Modbus TCP/IP](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip) documentation.


# ZEVA

ZEVA is a field-ready water quality controller. It measures key parameters such as pH, conductivity, temperature and turbidity, shows them on a local display, and connects to PLC/SCADA systems or the YuDash IoT platform. It is designed for industrial process water, ETP/STP, drinking water, aquaculture, swimming pools and boiler applications.

{% hint style="info" %}
For details, contact [**sales@yudash.com**](mailto:sales@yudash.com).
{% endhint %}

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fd8e977t4AutirqeoXycm%2FYuDash_ZEVA_v1.jpg?alt=media&amp;token=78bd6637-dbeb-4545-8102-20f9f7a5384f" alt=""><figcaption></figcaption></figure>


# Product Features


# Configuration


# Configuration JSON download/upload

All YuDash IoT devices are configured using a single JSON configuration file (typically called **`lynx.json).`**&#x54;his file defines everything about the device — from sensor inputs, logic formulas, and network settings, to output behavior and communication protocols.

Think of `lynx.json` as the **"PLC program"** for your YuDash device. You can either:

* Edit settings using the **built-in web UI**, or
* Modify the `lynx.json` file directly for advanced customization.

> ✅ Once your configuration is stable and tested, it is **good practice to download the current `lynx.json` file**. This serves as a backup and can be reused for future deployments.

### YuDash Configuration JSON file download

{% embed url="<https://youtu.be/rYdnaPNauaY>" %}

### YuDash Configuration JSON file upload

{% embed url="<https://youtu.be/UN_CmP_vjeg>" %}


# Network

YuDash IoT devices support various options to connect to network (cloud or LAN)

<table><thead><tr><th width="218">Network Connectivity</th><th>Typical Use-Cases.</th></tr></thead><tbody><tr><td>4G/LTE</td><td>Standalone IoT connectivity through SIM card. This provides a reliable connectivity without any external dependies.</td></tr><tr><td>Ethernet</td><td><p>a) IoT gateway connected to Internet enabled LAN.</p><p>b) IoT coupled with 4G/LTE router.</p><p>c) IoT gateway connected to LAN with local/on-prem server.</p></td></tr><tr><td>WiFi</td><td><p>a) IoT gateway connected to Internet enabled LAN through WiFi.</p><p>b) IoT coupled with 4G/LTE Wifi router.</p><p>c) IoT gateway connected to LAN with local/on-prem server.<br><strong>It is important to have a strong Wi-Fi for a reliable connection</strong></p></td></tr><tr><td>LoRaWan</td><td>YuDash IoT devices do not support LoRaWan at present.</td></tr></tbody></table>

## **Network Settings**

**LYNX Network Settings** section deals with connection of LYNX with the network. It is typically internet or local LAN in some cases. Depending on model, LYNX supports the following options to connect to network:

1. **Wi-Fi**: LYNX connects to a Wi-Fi network (router) to access the internet/local LAN. All models of LYNX support connection to internet through Wi-Fi.
2. **Ethernet**: LYNX connects to internet through Ethernet (RJ45 jack).
   * By default, it assumes DHCP connection (in which IP address is assigned by router). In this case, no further change in setting is needed.
   * LYNX also supports static IP address configuration under advanced Ethernet settings.
3. **4G/LTE (Sim card)**: LYNX connects to internet through 4G/LTE SIM card.
   * Support of all 4G networks, independent of carriers. LYNX has been tested with all carriers in India.
   * Option to provide carrier APN. Though, this is not critical.
   * Support of external antenna for in-panel applications.
4. **None (Offline)**: LYNX is not being connected to any network and is being used as display unit. This mode is also used for debugging purpose.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FjMKzeJgZlGSzit27GvrA%2Fnw_info.png?alt=media&amp;token=28c04296-0988-4b40-a83c-70d3a110bf8a" alt=""><figcaption></figcaption></figure>

## &#x20;Read and Write Network Settings <a href="#h.7essfeb8lo72_l" id="h.7essfeb8lo72_l"></a>

1. **Click on "Read Network Settings"** button. The network settings will be populated in configuration page from LYNX. It may take 1-2 seconds for this process.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FjYxD78gh0IYfkrtz2tVx%2F1.png?alt=media&amp;token=f6520b3b-5f22-475d-a769-244a578d31bb" alt=""><figcaption></figcaption></figure>

2. Various network Settings are populated in the configuration page from LYNX. Apply required changes in given section.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FdnvU9vs3nfjZCQpNeyu8%2F2.png?alt=media&amp;token=2eaf5165-0611-4791-a07d-ac2235f45073" alt=""><figcaption></figcaption></figure>

3\. After all the changes are completed, click on **Write Network Settings** button. This will update the network settings in the LYNX. A popup is displayed. After clicking on Write Network Settings, wait for 2-3 seconds for update.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FoORNSF2O40z8i4J28EuZ%2F6.png?alt=media&amp;token=58e23b43-be17-40df-afec-ac827bf2b388" alt=""><figcaption></figcaption></figure>

4\. Click on **Reboot LYNX** button to reboot the LYNX. Alternately, LYNX can be power cycled. LYNX will use updated Network Settings after reboot. During initial runs, it is better to cross check whether settings have been updated in LYNX after the reboot.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmAnmSE5zlvjzGNc5rfAZ%2F7.png?alt=media&amp;token=c535505f-8672-419d-9709-3e6db1ef0792" alt=""><figcaption></figcaption></figure>

## Selection of Network Settings in LYNX <a href="#h.k4m76haudqyd_l" id="h.k4m76haudqyd_l"></a>

**Network Selection** radio button is used to select a given type of network. Details of each network type is covered in following sections.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FwWqHEjSx7ICpSSZMXzvC%2F3.png?alt=media&amp;token=30026528-6381-4d65-9fe2-2ee9522cb5ac" alt=""><figcaption></figcaption></figure>

Complete steps of Network Selection are covered in the video below:

{% embed url="<https://youtu.be/WYFol9QFN0w>" %}

## Updating Wi-Fi Settings in YuDash LYNX <a href="#h.evyaga4mm2a1_l" id="h.evyaga4mm2a1_l"></a>

1. To Change the Wi-Fi settings, click on show password checkbox. Update the Wi-Fi SSID name and password in given text boxes.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FTF4PbmbvOigg6LG1a0Il%2F8.png?alt=media&amp;token=fa173784-432d-4ea6-bc6b-d9ae72192217" alt=""><figcaption></figcaption></figure>

2. In the above settings, the SSID#1 has been changed from yudashdemo to my\_test\_1 and password has been updated. Similarly, WIFI SSID#2 has been changed to mytest2.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FZOeKJ50M6lmxJPq7NFez%2F9.png?alt=media&amp;token=7b3834f9-b73f-4faf-9a4c-b26ed1f61866" alt=""><figcaption></figcaption></figure>

### **LYNX WiFi Features and Specifications**

1. LYNX supports DHCP Wi-fi connection only.
2. LYNX supports 2.4GHz Wi-Fi only. 5GHz Wi-Fi networks are not supported.
3. LYNX supports DHCP Wi-fi connection only (IP address issued by Wi-Fi router).
4. For on-premise solutions, Wi-Fi with local LAN access can be used (without any need for internet connection).
5. LYNX has in-built Wi-Fi antenna. There is no provision of external Wi-Fi antenna.
6. There is provision to provide two Wi-Fi networks. By default, LYNX attempts connection to first Wi-Fi (Wi-Fi SSID#1 and Wi-Fi Password). In case it is not connected, it will attempt to connect to (Wi-Fi SSID#2). It is not mandatory to fill both Wi-Fi settings.

{% hint style="info" %}
**YuDash LYNX WiFi Trouble Shooting Guide**

Please consider the following in case you are facing Wi-Fi connection issues:

1. Check special characters and space in Wi-Fi SSID and password entry boxes.
2. Create a simple SSID name and password using mobile phone and first connect to that Wi-Fi.
   {% endhint %}

## Updating 4G/SIM LTE Settings in LYNX <a href="#h.9av3fahqnmhw_l" id="h.9av3fahqnmhw_l"></a>

When 4G/LTE sim card is selected, LYNX uses 4G connection for connecting to internet. In general, there are no settings required.

* There is option to provide APN (Access Point Name) which can be selected based on carrier. In our observation, it is not mandatory to update this.
* The option 4G TimeOut (sec) is the time LYNX will attempt to connect to the SIM network. Depending on network strength, it takes up to \~20 seconds for LYNX modem to connect to network. This setting can be tweaked in case of connectivity issues.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F8cT4bwMLFeDpBlphqN4A%2F5.png?alt=media&amp;token=b458b191-5461-4a9f-a3df-585e7eacc443" alt=""><figcaption></figcaption></figure>

{% embed url="<https://youtu.be/8z1vXeRFoEg>" %}

## Updating Ethernet Settings in LYNX

Ethernet port can be used to connect to cloud (or on-premise server). This is enabled by selecting Ethernet in Network Settings as below.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkhT25EllQYm5Y9ZGVZeb%2FNetwork_Ether.jpg?alt=media&amp;token=0d23acbc-8325-45a6-8296-3f3d35ed8f38" alt="" width="563"><figcaption></figcaption></figure>

Ethernet supports dynamic IP (DHCP) and static IP option. By default, dynamic IP is assumed in which IP address is assigned by local LAN router. In this case, there is no further configuration in this section. This is most common use-case for most of the applications.

For assigning static IP to LYNX for network connection, please refer to [Ethernet Settings](/yudash-iot-products/lynx/lynx-settings/ethernet-settings) section.

{% hint style="info" %}
For using ethernet port for network connectivity, there is no need to enable Ethernet within LYNX settings. Just selection of Ethernet in Network Selection is sufficient.&#x20;
{% endhint %}

Following is sample connection of Ethernet RJ45 jack connected to LYNX:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FVqfZnG6SSBmEqTpHuBnq%2F8.png?alt=media&amp;token=ddf583af-d6e9-4b61-b6e8-79646cf54e12" alt="" width="563"><figcaption></figcaption></figure>

### **LYNX display during Ethernet Setup**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F7TSpgb8FLxLaVcyz75nI%2Fether1.jpg?alt=media&amp;token=bf04f720-aed2-4ca3-8706-11f54865760f" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FPbRcntlr0CKWqCgyjLIA%2Fether2.jpg?alt=media&amp;token=d50d7e43-c850-4fcf-b8bb-e45bcb8d333e" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FJMY3Q1y1hKXR8RSnc16L%2Fetherr3.jpg?alt=media&amp;token=ad619cc6-452a-4893-89bb-4bd6962cce3d" alt=""><figcaption></figcaption></figure>


# Sensor Interface


# Analog Inputs

YuDash devices can acquire analog signals directly from field sensors, transmitters and measurement instruments.

Depending on the product and model, supported analog interfaces may include:

* **0–20 mA / 4–20 mA current inputs**
* **0–5 V voltage inputs**
* **High-range DC voltage inputs**
* **Low-level differential voltage inputs**

This page explains the common YuDash analog-input configuration workflow. **FELYX is used as the working example.** Always refer to the relevant product interface and model-selection pages for the physical terminals and input ranges available on a particular device.

For a simple linear conversion, the **Input**, **Output** and **Multiplier** settings in the Analog Wizard can perform the required conversion directly.

The separate **Data Scaling** feature is therefore **not required for every analog input**.

## Example: Reading 0–20 mA Inputs

This example demonstrates direct measurement of four **0–20 mA analog signals** using FELYX.

A multi-channel analog signal generator is connected to analog inputs **A1–A4** and adjusted to approximately:

* 5 mA
* 10.7 mA
* 15.1 mA
* 20 mA

The Analog Wizard is configured so that the resulting YuDash variables directly represent the measured current in mA. **The separate Data Scaling feature is not used in this example.**

{% stepper %}
{% step %}

### Connect the analog signals

Connect the analog current outputs to the required FELYX current-input channels.

For this example:

| Signal          | FELYX input |
| --------------- | ----------- |
| Current input 1 | A1          |
| Current input 2 | A2          |
| Current input 3 | A3          |
| Current input 4 | A4          |

Connect the corresponding signal return as required by the product terminal layout.

The four signal-generator channels are set to approximately **5.06 mA, 10.71 mA, 15.13 mA and 20.41 mA**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FFJ6Y1KavcjktvIGdePPZ%2FFELYX_HelpPages%20(1).png?alt=media&amp;token=42d6df4a-630d-4e42-803b-7ae56eca7c9c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Open the Analog Wizard

From **Device Configuration**, go to:

**Sensor Settings → Analog**

Select **Open Analog Wizard**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Ffh1IMeHOexl2X1Nfsajt%2FFELYX_HelpPages%20(2).png?alt=media&amp;token=b24bde27-c84b-4462-af8d-0723f7bacff0" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the analog channels

The Analog Wizard opens the **Channel Matrix**.

Each row represents one physical analog input. Enable the required channels and configure their signal range and variable names.

For this example:

<table><thead><tr><th width="87">Channel</th><th width="116">Topology</th><th width="123">Input Min–Max</th><th width="137">Output Min–Max</th><th>Variable</th></tr></thead><tbody><tr><td>A1</td><td>0–20 mA</td><td>0–20</td><td>0–20</td><td><code>analog_1</code></td></tr><tr><td>A2</td><td>0–20 mA</td><td>0–20</td><td>0–20</td><td><code>analog_2</code></td></tr><tr><td>A3</td><td>0–20 mA</td><td>0–20</td><td>0–20</td><td><code>analog_3</code></td></tr><tr><td>A4</td><td>0–20 mA</td><td>0–20</td><td>0–20</td><td><code>analog_4</code></td></tr><tr><td></td><td></td><td></td><td></td><td></td></tr><tr><td></td><td></td><td></td><td></td><td></td></tr></tbody></table>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDswBGwW3gZhjQ1W2Sc8H%2FFELYX_HelpPages%20(3).png?alt=media&amp;token=ce58a78b-bce4-41ca-b657-888513dbcbad" alt=""><figcaption></figcaption></figure>

The important Channel Matrix fields are:

* **Enable** — enables processing of that channel.
* **Topology** — selects the physical input and electrical input type.
* **Input Min–Max** — expected electrical input range.
* **Output Min–Max** — value range generated from the measured input.
* **Multiplier** — final multiplier applied to the value.
* **Variable** — name used for monitoring, logging and telemetry.
* **Backup Variable** — optional and may be left blank when not required.

In this example, both the input and output ranges are **0–20**, and the multiplier is **1**. The resulting variable therefore directly represents the measured current in mA.

For example:

`10.7 mA input → approximately 10.7 in the YuDash variable`

No separate Data Scaling configuration is required for this direct reading.

Select **Save & Close** after completing the channel configuration.
{% endstep %}

{% step %}

### Enable Analog Inputs

Configuring the channels in the Analog Wizard does not by itself enable analog acquisition.

Go to:

**Device Settings → Feature Settings**

Enable **Analog Inputs**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYckCXpNVjO0GulCZObvK%2FFELYX_HelpPages%20(4).png?alt=media&amp;token=18a61035-70d6-4237-992f-6dc45b1ae7fd" alt=""><figcaption></figcaption></figure>

For this example, **Data Scaling remains disabled**.
{% endstep %}

{% step %}

### Apply the configuration and reboot

* Select **Update and Preview** to review the updated configuration.
* Select **Write Device Config** to write the configuration to the YuDash device.
* Select **Reboot Device** to restart the device with the new settings.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fyak4MJs7W7lG4YZQClDH%2FFELYX_HelpPages%20(7).png?alt=media&amp;token=a6698b95-fc37-480a-a6d4-3d26321b95a5" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Verify the analog values

Open the **Live Dashboard** and verify that the configured analog variables are updating.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FqpoHTLj5LiBtzkk3kLDR%2FFELYX_HelpPages%20(6).png?alt=media&amp;token=7f20f69f-eeaf-4ed7-b438-52dc1255805c" alt=""><figcaption></figcaption></figure>

In this example, the dashboard displays:

| Variable   | Measured value |
| ---------- | -------------- |
| `analog_1` | 5.086          |
| `analog_2` | 10.773         |
| `analog_3` | 15.159         |
| `analog_4` | 20.046         |

These values correspond closely to the current levels applied using the analog signal generator.The live acquisition path is:

```mermaid
flowchart LR
    A["Sensor / Signal Generator<br/>0–20 mA"] --> B["YuDash Analog Input"]
    B --> C["YuDash Variable<br/>analog_1 ... analog_4"]
    C --> D["Live Dashboard"]
```

**0–20 mA Signal → Analog Input → YuDash Variable → Live Dashboard**

The **Analog Wizard** is used during configuration to define the input range, output range, multiplier and variable mapping.

This confirms that the analog channels are configured correctly and that the acquired values are available for subsequent **monitoring, data logging and cloud telemetry**.
{% endstep %}
{% endstepper %}

## Voltage Inputs

FELYX also supports voltage-based analog inputs.

On the FELYX81 used in this example, the analog terminal group is arranged as:

**A1 · A2 · A3 · A4 · GND · C5 · C6 · C7 · D8 · GND**

The inputs are divided by electrical range:

| Input group | Channels | Input type |
| ----------- | -------- | ---------- |
| **Type A**  | A1–A4    | 0–20 mA    |
| **Type C**  | C5–C7    | 0–5000 mV  |
| **Type D**  | D8       | 0–90000 mV |

{% hint style="info" %}
Available analog channels depend on the YuDash product and model. Always verify the product interface before wiring.
{% endhint %}

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FL15M6JoZfYfqHjh6E6Cv%2FFELYX_HelpPages.jpg?alt=media&amp;token=fe757980-de3f-4e14-b1ab-995735805d35" alt=""><figcaption></figcaption></figure>

#### Understanding the FELYX voltage terminals

The right-side analog terminal block contains both current and voltage inputs.

* **C5, C6 and C7** are intended for signals up to **5000 mV (5 V)**.
* **D8** is a high-range voltage input intended for applications such as **battery or DC supply-voltage monitoring**.
* The adjacent **GND** terminals provide the signal reference.

The channel type must match the electrical signal being connected.

***

### Type C — 0–5 V Inputs

Type C channels are used for voltage signals from **0 to 5000 mV (0–5 V)**.

In this example, channels **C5** and **C6** are enabled in the Analog Wizard with:

| Channel | Topology  | Input  | Output | Multiplier | Variable   |
| ------- | --------- | ------ | ------ | ---------- | ---------- |
| C5      | 0–5000 mV | 0–5000 | 0–5000 | 1          | `analog_5` |
| C6      | 0–5000 mV | 0–5000 | 0–5000 | 1          | `analog_6` |

The same figure also shows the corresponding values on the **Live Dashboard**.

In this example:

* `analog_5` ≈ **3004.8 mV**
* `analog_6` ≈ **2552.6 mV**

Because the Input and Output ranges are both set to **0–5000** and the multiplier is **1**, the YuDash variables represent the measured voltage directly in **millivolts**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fr4tVTVp3AZKDTSSls23B%2FFELYX_HelpPages%20(8).png?alt=media&amp;token=51849cdd-04f9-4aea-911d-59b8ccb23f64" alt=""><figcaption></figcaption></figure>

Because the Input and Output ranges are both set to **0–5000** and the multiplier is **1**, the YuDash variables represent the measured voltage directly in **millivolts**.

For example:

```
3005 mV input → analog_5 ≈ 3005
2553 mV input → analog_6 ≈ 2553
```

If the value is required directly in **volts**, set the multiplier to `0.001`.

```
3005 mV × 0.001 = 3.005 V
```

> The Type-C channel therefore performs the voltage measurement directly; no separate Data Scaling configuration is required for this simple conversion.

#### Type D — Battery / High-Range Voltage Input

The **D8** channel is used for higher DC voltage measurements such as **battery or supply-voltage monitoring**.

D8 supports a measurement range of:

**0–90000 mV (0–90 V)**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYXRmPb63GB6wV6Zz0Dt4%2FFELYX_HelpPages%20(9).png?alt=media&amp;token=db6eb138-06f3-4d8e-b27b-fcc90f187712" alt=""><figcaption></figcaption></figure>

In this example, D8 is enabled in the Analog Wizard with the following settings:

| Channel | Topology   | Input   | Output  | Multiplier | Variable       |
| ------- | ---------- | ------- | ------- | ---------- | -------------- |
| D8      | 0–90000 mV | 0–90000 | 0–90000 | 1          | `Battery_Volt` |

The same figure shows the corresponding value on the **Live Dashboard**.

In this example:

* `Battery_Volt` ≈ **8479 mV**

Because the Input and Output ranges are both set to **0–90000** and the multiplier is **1**, the YuDash variable represents the measured voltage directly in **millivolts**.


# Modbus/RS485

Modbus RTU is a widely used serial communication protocol for connecting industrial sensors, instruments, meters and PLCs.

YuDash dataloggers and IoT gateways can operate as a **Modbus RTU Master**, periodically reading data registers from one or more Modbus slave devices over RS485.

In this guide, a **FELYX datalogger** and an **XY-MD02 temperature and humidity transmitter** are used as the working example.

### Information required from the Modbus device

Before configuring a Modbus instrument, identify the following information from its datasheet or communication manual:

1. **Baud rate**
2. **Data bits, parity and stop bit**
3. **Modbus Slave ID**
4. **Register information**
   * register number or address
   * register/function type
   * data type and size
   * byte/word order, where applicable
   * scaling or factor, where applicable
5. **Addressing convention** — base-0 or base-1

These settings must match between the Modbus slave device and the YuDash datalogger.

### Modbus Register Mapping in YuDash Devices <a href="#h.jt0n9eorg4hg_l" id="h.jt0n9eorg4hg_l"></a>

For each value to be read from a Modbus slave, YuDash requires four main settings:

1. **Variable Name**
2. **Register Number**
3. **Type**
4. **Factor**

Together, these settings define **where the value is read from, how the register data is interpreted, and how the final value is represented in YuDash**.

#### 1. Variable Name

Each Modbus register value read by the device is stored as a named YuDash variable.

The variable name is used throughout the system for functions such as:

* Live Dashboard
* Data Logging
* Cloud Telemetry
* Data Scaling
* AXON Edge processing

Use short, descriptive variable names without spaces.

Examples:

`Temperature`\
`Humidity`\
`volt1`\
`machine_status`

In the FELYX example used later on this page, the XY-MD02 registers are mapped to the variables **Temperature** and **Humidity**.

#### 2. Register Number

The **Register Number** identifies the Modbus data location to be read.

Different Modbus register ranges correspond to different Modbus function codes.

| Function Code | Registers             | Range       |
| ------------- | --------------------- | ----------- |
| **1**         | **COIL STATUS**       | 0-9990      |
| **2**         | **INPUT STATUS**      | 10000-19999 |
| **4**         | **INPUT REGISTERS**   | 30000-39999 |
| **3**         | **HOLDING REGISTERS** | 40000-49999 |

**Register addressing: Base 0 and Base 1**

Modbus register addresses may be represented differently by instrument manuals and Modbus software.

YuDash configuration uses **base-0 / protocol addressing**. Some Modbus software displays registers using **base-1 / PLC addressing**, where the displayed register number is one higher.

For example:

`40000` in base-0 addressing corresponds to `40001` in base-1 addressing.

The same difference applies to other register ranges.

This becomes important when copying register numbers from software such as ModScan into YuDash configuration. Always check which addressing convention is being used.

> **Important:** Do not change a register number simply because it “looks different” from the instrument manual. First determine whether the manual or software is using base-0 or base-1 addressing.

We will demonstrate this later using the same XY-MD02 registers in **FELYX, Modbus Poll and ModScan**.

#### 3. Type

The **Type** setting tells YuDash how the data contained in the Modbus register should be interpreted.

It defines information such as:

* signed integer or floating-point data
* 16-bit, 32-bit or 64-bit values
* number of Modbus registers used by the value
* byte and word ordering
* byte-swapped representations

<table><thead><tr><th width="130">Type</th><th width="300.3333333333333">Description</th><th>No. of Registers read</th><th>Byte Sequence</th></tr></thead><tbody><tr><td>1</td><td>SIGNED INTEGER</td><td>1</td><td></td></tr><tr><td>2 or 20</td><td>Floating Point (LSB first)</td><td>2</td><td>CDAB</td></tr><tr><td>21</td><td>Floating Point (MSB first) </td><td>2</td><td>ABCD</td></tr><tr><td>22</td><td>32bit Integer (LSB first)</td><td>2</td><td>CDAB</td></tr><tr><td>23</td><td>32bit Integer (MSB first)</td><td>2</td><td>ABCD</td></tr><tr><td>24</td><td>32bit Unsigned Integer (LSB first)</td><td>2</td><td>CDAB</td></tr><tr><td>25</td><td>32bit Unsigned Integer (MSB first)</td><td>2</td><td>ABCD</td></tr><tr><td>11</td><td>Bit pattern Extraction</td><td>1</td><td></td></tr></tbody></table>

{% hint style="info" %}
YuDash also supports byte swapping for 32 bit registers. For these special case, we have to use 3 digit Type (by adding a suffix 1 to original type). It will enable byte swapping with same data type as corresponding 2 digit code: \
**201, 221, 241**: **DCBA** \
**211, 231, 251**: **BADC**

*Note: Support of code 24, 25 and 3 digit types is available in firmware V3.6 onwards.*
{% endhint %}

YuDash devices also support 64-bit IEEE-754 floating-point and signed integer values. A 64-bit value occupies four consecutive Modbus registers. Because different manufacturers use different terminology for byte and word order, YuDash represents the four 16-bit register words as **P, Q, R and S**.

Following are possible combinations:&#x20;

<table><thead><tr><th width="122">Type</th><th>Sequence</th><th>Type</th><th>Sequence</th><th>Data Type</th></tr></thead><tbody><tr><td><strong>4 or 40</strong></td><td>RSPQ</td><td><strong>401</strong></td><td>SRQP</td><td>Float 64</td></tr><tr><td><strong>41</strong></td><td>PQRS</td><td><strong>411</strong></td><td>QPSR</td><td>Float 64</td></tr><tr><td><strong>42</strong></td><td>RSPQ</td><td><strong>421</strong></td><td>SRQP</td><td>Int 64</td></tr><tr><td><strong>43</strong></td><td>PQRS</td><td><strong>431</strong></td><td>QPSR</td><td>Int 64</td></tr></tbody></table>

{% hint style="info" %}
YuDash internally converts acquired values to 32-bit floating-point values for further processing. Very large 32-bit integer or 64-bit values may therefore be subject to precision loss or overflow. Where appropriate, the **Factor** setting can be used to reduce the magnitude of the processed value.
{% endhint %}

#### 4. Factor

The **Factor** setting provides simple post-processing of the value after it is read from the Modbus register.

The acquired register value is:

**divided by the configured Factor**

A Factor of **1** leaves the value unchanged.

Factors such as **10** or **100** are commonly used when an instrument stores a decimal measurement as an integer.

For example, if an instrument represents:

**234.6 V as the integer `2346`**

then:

**Factor = 10**

gives:

`2346 ÷ 10 = 234.6`

This allows the YuDash variable to directly represent the engineering value shown by the instrument.

In the XY-MD02 example later on this page, the Temperature and Humidity registers use a **Factor of 100**.

{% hint style="info" %}
In most of industrial applications, MODSCAN (or similar) software is used to validate the Modbus settings. In case of any troubleshooting, we strongly suggest to validate the communication through MODSCAN. Our tutorial explains the mapping in reference of MODSCAN to LYNX settings.
{% endhint %}

### Example: Reading XY-MD02 over Modbus RTU

The **XY-MD02** is a temperature and humidity transmitter with **Modbus RTU / RS485** communication.

In this example, we use the same transmitter in three contexts:

* **ModScan** — to verify the device and inspect its Modbus registers
* **Modbus Poll** — to view the same registers using another Modbus test utility
* **FELYX** — to configure the transmitter as a Modbus slave and acquire its Temperature and Humidity values

This allows the register information seen on a PC to be directly related to the configuration used in FELYX.

### Verify XY-MD02 with ModScan

Before connecting the XY-MD02 to FELYX, the transmitter can be tested directly from a laptop using an **RS485-to-USB converter** and Modbus software.

This is useful for confirming the wiring, communication settings and register values independently of the datalogger. The test arrangement is:

**XY-MD02 → RS485-to-USB Converter → Laptop**

#### Wiring

Connect the XY-MD02 RS485 **A and B** terminals to the corresponding terminals of the RS485-to-USB converter. Power the XY-MD02 from a suitable DC supply and connect the USB converter to the laptop.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fgy8yOeUztaSxzUtffUHF%2F01_XYMD02_RS485_USB_Laptop_Wiring_AI.png?alt=media&amp;token=5b879483-5872-4f0d-87ca-68e24311204a" alt=""><figcaption></figcaption></figure>

ModScan can be used to communicate directly with the XY-MD02 and view its Modbus registers.

#### Select the Modbus data to read

Set Device ID `1`, select `04: INPUT REGISTER`, use Address `0002` and Length `2`.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FzCido2QK1qETbvLxiwDh%2F02_ModScan_Initial_Interface.png?alt=media&amp;token=9b508871-9dda-4f93-9f3e-d5aa4cd76fad" alt=""><figcaption></figcaption></figure>

#### Configure the serial connection

Select the COM port connected to the RS485-to-USB converter and use **9600 baud, 8N1**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F0CpsCZOJaJUqoAnXZpoE%2FConnection%20Details%20Configuration%20Highlight.png?alt=media&amp;token=02412559-fcab-4f73-81c9-2ff4bd9ef1a2" alt=""><figcaption></figcaption></figure>

These parameters must match the communication settings of the Modbus slave.

#### Read the Temperature and Humidity registers

Configure ModScan for:

| Setting           | Value              |
| ----------------- | ------------------ |
| Device ID         | 1                  |
| Modbus Point Type | 04: INPUT REGISTER |
| Address           | 0002               |
| Length            | 2                  |

ModScan then displays the two register values:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FxOvSANasJO5D1N7H25XZ%2F04_ModScan_Input_Register_Read.png?alt=media&amp;token=5d7864fb-e5bf-4a7e-a017-b756e5f60e27" alt=""><figcaption></figcaption></figure>

With a Factor of 100, the displayed values `3048` and `6515` correspond to **30.48 °C** and **65.15 %RH**.

#### Display formats in ModScan

ModScan can display register contents in several formats:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FNRuh3raFu42G5ybGtpx1%2F05_ModScan_Display_Types.png?alt=media&amp;token=21d118b5-c248-42c1-ac16-4474c8cc16f0" alt=""><figcaption></figcaption></figure>

The selected display format should match the data representation specified by the instrument manufacturer.

For the XY-MD02, the Temperature and Humidity values in this example are read as integer values and subsequently divided by 100.

### View XY-MD02 Registers in Modbus Poll

The same XY-MD02 can also be read using **Modbus Poll**. This provides another view of the communication settings, register definition and addressing convention.

#### Serial Connection Settings

Configure the serial port for **Modbus RTU, 9600 baud, 8 data bits, no parity and 1 stop bit**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F3VKSdHGdCBPuK6vwSYKF%2F06_ModbusPoll_Serial_Settings.png?alt=media&amp;token=a88f854c-cd89-44d6-b521-49bd50d50f2d" alt=""><figcaption></figcaption></figure>

#### Read Definition

Set the **Slave ID**, select **Function 04 — Read Input Registers**, and define the starting address and number of registers to read.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F23MEh0J9OdFNKSTsrYFq%2F07_ModbusPoll_Read_Definition.png?alt=media&amp;token=31344130-5bba-4909-b54b-f2113eacfbcc" alt=""><figcaption></figcaption></figure>

#### Addressing and Data Format

Modbus Poll can display addresses using either **PLC Addresses (Base 1)** or **Protocol Addresses (Base 0)**.

For this example, use **Protocol Addresses (Base 0)**.

The same menu also provides different display formats such as Signed, Unsigned, Hex, Long, Float and Double.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMs5lctYYGe6OmPTw4VPU%2F08_ModbusPoll_DataTypes_Base0.png?alt=media&amp;token=cb741ff6-ae6b-4e1a-a614-091549a17b7b" alt=""><figcaption></figcaption></figure>

#### Register Values

The two XY-MD02 input registers are then visible directly in Modbus Poll.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FbhEumcIjttBUyGyVQio9%2F09_ModbusPoll_Register_Values.png?alt=media&amp;token=786cc09c-df0b-46dd-a1b2-393d59db6451" alt=""><figcaption></figcaption></figure>

### Configure XY-MD02 with FELYX

After verifying the XY-MD02 registers using ModScan or Modbus Poll, the transmitter can be connected directly to FELYX and configured as a Modbus RTU slave device.

{% stepper %}
{% step %}

#### Connect XY-MD02 to FELYX

Connect the XY-MD02 to FELYX over RS485. In this demonstration, the XY-MD02 is also powered from FELYX using the loopback connection shown below.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F81amUz5XJAS4ktGlyfQv%2F01_FELYX_XYMD02_RS485_Setup.png?alt=media&amp;token=1a387ff1-2091-4308-b529-da433a34acb9" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Open the Modbus Wizard

Open **Device Configuration** and select **Open Modbus #1 Wizard**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FLUu7rCp8RMCaIv1JKvZJ%2F09_FELYX_Open_Modbus_Wizard.png?alt=media&amp;token=e18b14de-d693-451e-b8f3-13efb92e9de4" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Configure the RS485 communication

Set the channel to **9600 baud, 8N1, Modbus RTU**, with **Read Try Count = 3**.

These settings must match the communication parameters configured in the Modbus slave.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMS2jn8UHZwferl1ACNFr%2F10_FELYX_RS485_Settings.png?alt=media&amp;token=295651b9-f548-49ee-9214-ca5876e48258" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Add the XY-MD02 and map its registers

Add **Slave ID 1** and map **Temperature → 30001** and **Humidity → 30002**, both with **Type 1** and **Factor 100**.

`MD02` is used as the Sensor Name for identification.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FbvY1Lrf1NaDAIOTT1A9M%2F11_FELYX_Slave_Register_Mapping.png?alt=media&amp;token=83e82664-11d1-4225-819a-4ef3203423ff" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Enable Modbus

Under **Device Settings → Feature Settings**, enable **Modbus #1**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fp6vRFSxsIA96XkQJaEBt%2F12_FELYX_Enable_Modbus.png?alt=media&amp;token=cc1e04ad-a522-4d13-9460-36c7111e9cae" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Apply the configuration and reboot

After enabling Modbus:

1. Select **Update and Preview**.
2. Review the updated configuration.
3. Select **Write Device Config**.
4. Select **Reboot Device**.

The device restarts with the new Modbus configuration.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FWLtsEQ9FgeRtZqn4lIPj%2F13_FELYX_Apply_Config_and_Reboot.png?alt=media&amp;token=5bb13995-2610-4ac9-b8b1-1ab20c19c4d0" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Verify the values on the Live Dashboard

After FELYX restarts, open the **Live Dashboard**.

The two configured variables should now appear under Sensor Data.

In the example shown:

* **Temperature:** `28.69`
* **Humidity:** `70.49`

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FJhZ67Wu1As10w9R5WsRP%2F14_FELYX_Live_Dashboard.png?alt=media&amp;token=7527a531-6901-48d6-8b87-2dc507411921" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

The complete acquisition path is:

```mermaid
flowchart LR
    A["XY-MD02"] --> B["RS485 / Modbus RTU"]
    B --> C["FELYX"]
    C --> D["Temperature & Humidity Variables"]
    D --> E["Live Dashboard"]
```

Once the variables are available in FELYX, they can also be used by other features such as **Data Logging, Cloud Telemetry, Data Scaling and AXON Edge processing**.


# Modbus Poll Tutorial

For a new instrument integration with IoT, it is advisable to first read a given set of registers using PC based software to validate Modbus settings of the instrument. Following are two popular software tools used in the industry:

1\) Modscan [download link](https://www.win-tech.com/)

2\) Modbus Poll [download link](https://www.modbustools.com/download.html)

{% hint style="info" %}
The integration of instrument with PC based software is not in YuDash support scope. The details of software are shared for reference only and ease of integration.&#x20;
{% endhint %}

In this tutorial, steps for reading the Modbus instrument using YuDash IoT device with help of Modbus poll is explained (with focus on data type). Following are steps involved

## 1) Modbus read through Modbus Poll

1a) Interface the given Instrument using Modbus poll software.&#x20;

1b) A sample modbus register value has been read in Modbus poll and a non-zero value is validated successfully.&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fz7oGZpxhV02uDPw6xU10%2F8a.jpg?alt=media&amp;token=6aab4e3c-0d9d-42e7-82ec-574862eff4ae" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Details and support for above step (1)is outside the scope of YuDash support.&#x20;

As per customer requirement, YuDash provided online training and RS-485 to USB kit on chargeable basis.
{% endhint %}

## 2) Mapping of Modbus-Poll Settings to YuDash Modbus

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FiJnVXa1WCprrgeHnMINw%2Fyudash_with_modbus.jpg?alt=media&amp;token=0d327788-4123-40f7-b472-aab334de51e3" alt=""><figcaption><p>RS485/Modbus instrument is connected to YuDash IoT device</p></figcaption></figure>

### 2a) Baudrate and parity settings

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRg6X5R6jqZ1bVA9VJMw3%2F9.jpg?alt=media&amp;token=d0a6ad46-b609-4519-9ac7-28efc0a16824" alt=""><figcaption></figcaption></figure>

### 2b) SlaveID, register and display type mapping

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FcQCyFRUK7XAtTddwdxe6%2F10.jpg?alt=media&amp;token=e8bbd239-bd88-4da3-88d8-d3463a05fb00" alt=""><figcaption></figcaption></figure>

## 3) Mapping of Display data types to YuDash Modbus Types

There are various data types (16, 32 and 64 bit) applicable in Modbus. It is important to have correct data type selected while reading the instrument/PLC from YuDash IoT devices. The data types are explained in [Modbus Integration guide. ](https://docs.yudash.com/pf/si/modbus/pages/VogxISTVQJKQuRFsVKvT#h.jt0n9eorg4hg_l)

After successful read of register in step 1b, corresponding code in "Type" has to be filled in YuDash Modbus settings as per below mapping:&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMGNrQzFqpvnWL2iggg4e%2FYuDash_Modbus_Modbuspoll.jpg?alt=media&amp;token=df557b60-3ffd-4638-beed-108334919364" alt=""><figcaption></figcaption></figure>

### Data Type for 16 bit integers

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FY3GKfrHT8blkOsZ1grM5%2F2.jpg?alt=media&amp;token=0986edeb-720c-4ee8-99bb-17cbc413465e" alt=""><figcaption></figcaption></figure>

### Data Type for 32 bit signed integer

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FPL30nGidKcIQQC908v1X%2F3.jpg?alt=media&amp;token=87c31f46-f3d6-42dc-90fb-7023f336c8bb" alt=""><figcaption></figcaption></figure>

### Data type for 32 bi unsigned integer

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FUXWe2bQFfWAYazao7VWA%2F4.jpg?alt=media&amp;token=dc019362-b236-4f1f-88d1-a6c1c9a0b8a6" alt=""><figcaption></figcaption></figure>

### Data type for 32 bit Float

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FdUwGF6s3MWa2TNXlJ2Tb%2F6.jpg?alt=media&amp;token=effe6521-990b-4de8-91b0-7982f63256e6" alt=""><figcaption></figcaption></figure>

### Data type for 64 bit data types

YuDash supports few 64 bit register data types which are converted to 32 bit floating point numbers.

## Byte Alignment Reference

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fa6x7p2X3OFgqBDPCTEmY%2Fbyte_page.jpg?alt=media&amp;token=abf3ee17-68c0-4b94-b3ae-6b23ef67e939" alt=""><figcaption></figcaption></figure>

## 4) Technical Notes

### 4a) Data exchange between YuDash IoT and RS485 instrument

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRZetAS93Atr7xUEibCq4%2Fdata_flow.jpg?alt=media&amp;token=7c689fff-e65a-4b6b-ae09-2d35012614c9" alt=""><figcaption></figcaption></figure>


# String read in RS485/RS232

YuDash devices use the built-in **Modbus RS485/RS232 interface** to receive ASCII/text data from serial instruments such as weather sensors, analyzers, or weighing systems. The interface is defined as custom Modbus registers, for a flexible **raw text inputs** parsing.&#x20;

The input string is defined with modbus register value of 60000 range.

mbReg: 60ABC:  ABC represent maximum bytes to be read from the input stream.

varType:  defines the format and handline of input read.

The input can be treated as String (ASCII) or HEX data:

1. String: Input treated as ASCII/text data. This is applicable for varType range 50-54.
2. Hex: The input is treated as HEX data. A two character output in capital letters (followed by a space) is written for every input hex byte. This is applicable for varType range 55-59.

<table><thead><tr><th width="119">varType</th><th width="102">Input Type</th><th>Input read behavior</th></tr></thead><tbody><tr><td>50</td><td>String</td><td>Terminate input read at new line (\n, or \r). Flush balance input buffer after read.</td></tr><tr><td>51</td><td>String</td><td>Do not terminal at newline. Read all input bytes based on mbReg.</td></tr><tr><td>52</td><td>String</td><td>Terminate read at new line (\n, or \r). Do not flush buffer after serial read.</td></tr><tr><td>55</td><td>Hex</td><td>Terminate input read at new line (\n, or \r). Flush balance input buffer after read. </td></tr><tr><td>56</td><td>Hex</td><td>Do not terminal at newline. Read all input bytes based on mbReg.</td></tr><tr><td>57</td><td>Hex</td><td>Terminate read at new line (\n, or \r). Do not flush buffer after serial read.</td></tr></tbody></table>

#### Sample Modbus Slave settings for String input

* **slaveID and mbRegCnt:** These value remain 1 as default.&#x20;
* **varName**: The output variable name (**voltage\_string**) in which output string will be stored for further processing.
* mbReg: 60050. A register number >6000 represent string input read. 50 represents maximum 50 bytes to be read from the input. This can be set based on estimated text input line from the instrument.
* varType: 50.  50 means we treat input as string (ASCII), terminate reading at a newline and flush the baalnce input buffer. This will be the typical setting for most of the use-cases.&#x20;

```json
// modbus settings for RS485 string read
  "modBusSlaves": [
    {
      "slaveID": "1",
      "mbRegCnt": 1,
      "mbArray": [
        {
          "varName": "voltage_string",
          "mbReg": "60050",
          "varType": "50",
          "varFactor": "1"
        }
      ]
    }
  ],
```


# SDI-12

SDI-12 is a digital communication interface commonly used with environmental, hydrology, agriculture and weather sensors.

YuDash data loggers with SDI-12 support can communicate with compatible SDI-12 sensors, acquire multiple variables from a sensor and map the returned values to user-defined parameter names.

Typical applications include:

* Soil moisture and soil temperature
* Water level and hydrology sensors
* Water-quality instruments
* Meteorological sensors
* Agriculture and irrigation monitoring
* Multi-parameter environmental probes

On supported FELYX models, SDI-12 is available as a dedicated sensor interface.

### How SDI-12 works in YuDash devices

A typical configuration consists of:

**SDI-12 Sensor → YuDash Data Logger → Variable Mapping → Data Logging / Cloud / Local Monitoring**

Each connected sensor is assigned an **SDI-12 address**. The YuDash device sends the configured measurement command to the sensor and reads the returned measurement values.

The individual returned values can then be assigned meaningful variable names.

### SDI-12 Sensor Connection

Connect the SDI-12 sensor to the supported YuDash device before starting configuration.

A typical SDI-12 connection includes:

* **Power** — sensor supply from the device, where supported
* **GND** — common ground
* **SDI** — SDI-12 data line

The example below shows an SDI-12 soil-moisture sensor connected to a YuDash FELYX data logger.

> Always refer to the sensor datasheet and the product wiring guide for the exact terminal assignment, supply requirement, and wire colors.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fe7yUHiAHjCHO73uwQeXa%2FFELYX%20SDI-12%20Soil%20Sensor%20Connection%20Guide.jpg?alt=media&amp;token=c27f244b-a591-4dee-9fdd-f0a47af9812a" alt=""><figcaption></figcaption></figure>

## Configuring an SDI-12 Sensor

{% stepper %}
{% step %}

### Enable the SDI-12 feature

Open **Device Settings** and locate **Feature Settings**.

Enable **SDI-12** for the device. This activates the SDI-12 sensor interface in the runtime configuration.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmUKH9OG9JrkCQIQaNp0J%2F01_enable_sdi12.png?alt=media&amp;token=94fa3e25-7cbf-4f75-ac8e-2eee8b762f4c" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Open the SDI-12 Wizard

Go to **Sensor Settings** and select:

**Open SDI-12 Wizard**

This opens the **SDI-12 Sensor Manager**, where connected SDI-12 sensors and their returned variables can be configured.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4ziMWyiiHIFAguUqGUJv%2F02_open_sdi12_wizard.png?alt=media&amp;token=09214d55-4bd5-4d7b-a671-f91dbd528710" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Add or select a sensor

In the **SDI-12 Sensor Manager**, add a new sensor or select an existing sensor from the list.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Ffv3Wi6f8sMsUQR5UMCK5%2F03_configure_sdi12_sensor.png?alt=media&amp;token=dc0877a9-6823-4f2a-b405-9e705a75675c" alt=""><figcaption></figcaption></figure>

Configure the sensor settings:

* **Address** — SDI-12 address assigned to the sensor.
* **Label** — optional descriptive name for the sensor.
* **Measure Cmd** — measurement command used to request data from the sensor. `M!` is the standard measurement command shown in this example.
* **sdi12VarCnt** — optional variable-count setting. Leave blank when all returned variables are to be processed.

Under **Variable Mapping**, map the values returned by the sensor to YuDash variables.

For each variable, configure:

* **Var Name** — name used for the parameter in YuDash.
* **Factor** — scaling multiplier; normally `1` when no additional scaling is required.
* **Unit** — engineering unit, where required.
* **Description** — optional description of the parameter.

The **IDX** represents the sequence position of the value returned by the sensor.

In the example shown, one SDI-12 sensor returns five parameters:

1. Volumetric water content
2. Soil temperature
3. Relative permittivity
4. Bulk EC
5. Pore water EC

Select **Save & Close** after completing the sensor configuration.
{% endstep %}

{% step %}

### Configure the sensor

Return to **Device Settings** after saving the SDI-12 configuration.

Follow the standard YuDash configuration sequence:

**Update and Preview → Write Device Config → Reboot**

The new SDI-12 settings become active after the device restarts.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4VZ0XMKX5ZZswEPMwkef%2FFELYX_HelpPages%20(7).png?alt=media&amp;token=1c3e3f5d-4a63-48b0-a089-9295b4983e9c" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Verify SDI-12 Data

After the device restarts, open the **Live Dashboard**.

The configured SDI-12 variables should appear under **Sensor Data** with their current values.

The **Device Run Status** can also be used to confirm communication with the sensor. During normal operation, the log will show the SDI-12 sequence, including sensor detection, measurement, reading and processing of the returned values.

This provides a quick way to verify that:

**Sensor detected → Measurement completed → Values read → Variables available**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F0pCS8caynV5f4LSEJVai%2F04_verify_sdi12_data.png?alt=media&amp;token=b04dfe62-025b-4166-93c2-2f63a36b000d" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

***

## SDI-12 Tool

YuDash also provides an **SDI-12 Tool** for sensor commissioning, testing and troubleshooting. It can be used independently to communicate with SDI-12 sensors before or during field installation.

{% embed url="<https://youtu.be/rb-zh083QQ8>" %}

***


# Weather

The **Weather** feature supports traditional meteorological sensors that provide simple **pulse** or **analog** signals.

A YuDash data logger can directly measure:

* **Wind Speed** from a pulse-generating anemometer
* **Wind Direction** from a potentiometer-based wind vane
* **Rainfall** from a tipping-bucket rain gauge

These measurements are handled differently inside the data logger.

**Wind speed** is calculated over a configurable measurement window. Pulses are counted during the selected sample duration and converted into a wind-speed value using the configured calibration factor.

**Rainfall**, on the other hand, is accumulated continuously in the background. Each tipping-bucket pulse represents a known amount of rainfall and is added to the relevant rainfall counters.

Wind direction is typically acquired as an analog voltage from the wind-vane potentiometer and converted to **0–359°** using analog measurement and data scaling.

{% hint style="info" %}
**Sensor calibration is application-specific.** The user must configure the appropriate conversion factors, pulse resolution, debounce and related measurement settings according to the connected sensor manufacturer's specifications. Incorrect settings can result in inaccurate measurements.
{% endhint %}

Compact weather stations with internal electronics may provide wind and rainfall parameters directly over **Modbus, SDI-12 or serial/ASCII interfaces**. Those sensors are handled through the corresponding digital sensor interface rather than through the direct Weather measurements described here.

## Wind Speed and Direction <a href="#wind" id="wind"></a>

**Wind speed** is measured from pulses generated as the cups rotate. The YuDash data logger counts these pulses over a configured sample window and converts the measured pulse rate into wind speed using the configured sensor factor. The resulting value can then be represented in the required engineering units, such as **m/s, km/h, mph or knots**, depending on the application.

**Wind direction** is usually measured using a potentiometer connected to the wind vane. The changing potentiometer position produces an analog voltage, which is measured by the YuDash data logger and scaled into the required angular representation. A typical application may use **degrees (0–359°)**, while other angular units such as **radians** may also be used where required.

```mermaid
flowchart LR
    A["Wind Speed Sensor<br/>Pulse Output"] --> B["YuDash Data Logger<br/>Pulse Counting"]
    B --> C["Wind Speed"]

    D["Wind Direction Sensor<br/>Potentiometer Output"] --> E["YuDash Data Logger<br/>Analog Input"]
    E --> F["Data Scaling<br/>0–359°"]
    F --> G["Wind Direction"]
```

{% hint style="info" %}
**Wind measurement accuracy depends on the sensor configuration.** The correct speed factor, sample window, debounce and direction scaling must be set according to the connected anemometer specifications and the required output units.
{% endhint %}

### Configure Wind Speed & Direction

The following example explains the Weather configuration using the **Davis 6410 anemometer**, which provides both wind-speed pulse output and potentiometer-based wind direction.

The same **configuration workflow** can be used with other traditional anemometers. Sensor-specific wiring, pulse factors, debounce values and direction scaling must be set according to the connected sensor. Detailed sensor wiring is covered separately under **Sensor Integrations**.

> If the installation uses a **wind-speed-only sensor**, the Wind Direction configuration can be skipped.

For this example:

* **Wind Speed** is measured through the Weather pulse input.
* **Wind Direction** is measured through an analog input and converted to the required angular units using Data Scaling.

The following steps show the complete configuration.

Our primary worked example is the **Davis anemometer**, which is widely used in weather and hydrometeorological installations.

{% stepper %}
{% step %}

#### Connect the Davis 6410 to FELYX

For this example:

* **DI1** is used for wind-speed pulse counting.
* **C5** is used for the 0–5 V wind-direction signal.
* **V5B** provides the potentiometer excitation supply.
* **GND** is common to the sensor.

> Wind speed and wind direction are independent measurements even though both are carried through the same Davis RJ11 cable.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FO1JL1MQjuYTfIFREAG8p%2FFELYX_SensorIntegration%20(2).png?alt=media&amp;token=18188bcc-64b3-4de0-a077-70e8e741ce1f" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

#### Enable Weather Measurement

From **Device Settings**, enable the **Weather** feature. Also keep **Analog Inputs** and **Data Scaling** enabled, since wind direction is handled through the analog channel and then converted to degrees.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRTSgBdiCmRDILyQHg8S5%2F02_enable_weather.png?alt=media&amp;token=3a389194-5276-403b-a1db-02646d81a17b" alt=""><figcaption></figcaption></figure>

After applying the device configuration, open:

**Sensor Settings → Weather**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4PGL3qPu3wvyj3Pb23yt%2F03_enable_weather_wizard.png?alt=media&amp;token=4b1b7b46-7345-4c84-bbc9-f16e10d2da33" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Configure Wind Speed

The Davis 6410 wind-speed output is connected to **DI2**. FELYX counts the incoming pulses and converts them into a wind-speed value inside the **Weather** block.

Open **Weather → Wind Speed** and enable **Wind Speed**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FTJJpFXaMcoXGm7Lx5cOY%2F04_wind_speed_settings.png?alt=media&amp;token=2c01e114-36e8-484b-9d1d-1065cab4b2f3" alt=""><figcaption></figcaption></figure>

For this example:

<table><thead><tr><th width="186">Setting</th><th width="126">Value</th><th>Purpose</th></tr></thead><tbody><tr><td><strong>Cloud Variable Name</strong></td><td><code>wind_speed</code></td><td>Variable generated by FELYX</td></tr><tr><td><strong>Speed Factor</strong></td><td><code>0.1667</code></td><td>Calibration factor used to convert the measured pulse count/frequency into wind speed</td></tr><tr><td><strong>Debounce</strong></td><td><code>5 ms</code></td><td>Rejects very closely spaced transitions or electrical noise</td></tr><tr><td><strong>Sample Window</strong></td><td><code>10000 ms</code></td><td>Measurement window over which the wind-speed pulses are evaluated</td></tr></tbody></table>

> The **Speed Factor** depends on the pulse-to-speed relationship of the connected anemometer. The value shown above is the factor used for this Davis 6410 integration.
> {% endstep %}

{% step %}

#### Configure Wind Direction Input

Wind direction from the Davis 6410 is obtained from the **potentiometer wiper** on the green conductor. With the potentiometer powered from the FELYX 5 V supply, the direction signal is measured as a **0–5 V analog input**.

Open: **Sensor Settings → Analog**

Enable **Channel 5 / C5** and configure it as:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMg3FfgFM6XEid4mfVpfn%2F05_wind_direction_analog_c5.png?alt=media&amp;token=819171d0-ae6e-467f-a360-4ff156d1a98a" alt=""><figcaption></figcaption></figure>

| Setting        | Value           |
| -------------- | --------------- |
| **Topology**   | `C5: 0–5000 mV` |
| **Input Min**  | `0`             |
| **Input Max**  | `5000`          |
| **Output Min** | `0`             |
| **Output Max** | `5000`          |
| **Multiplier** | `1`             |
| **Variable**   | `w_direction`   |

At this stage, FELYX is measuring the raw wind-direction signal in millivolts.

The Davis 6410 uses a **wind vane and potentiometer** for direction sensing; the green wire is the potentiometer wiper and the yellow wire is its supply
{% endstep %}

{% step %}

#### Convert Wind Direction to Degrees

Open: **Data Scale & AXON → Data Scaling**

Add the variable `w_direction` and configure:

| Setting           | Value         |
| ----------------- | ------------- |
| **Variable Name** | `w_direction` |
| **Min In**        | `0`           |
| **Max In**        | `5000`        |
| **Min Out**       | `0`           |
| **Max Out**       | `359`         |

{% endstep %}

{% step %}

#### Step 6 — Verify Wind Data

After saving the configuration, open the **YuDash Local Dashboard** and verify the generated wind variables

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F1XGY7yA7NrLzJNv9cd9O%2FYuDash%20Real-Time%20Sensor%20Dashboard.png?alt=media&amp;token=9b9e1fa0-4986-4bc0-b31b-3ad19b6fdce4" alt=""><figcaption></figcaption></figure>

In this test, approximately **2.3 V** was applied to the wind-direction input **C5**. The dashboard shows:

* `analog_5` = **2307.07 mV** — raw analog input
* `w_direction` = **165.648°** — scaled wind-direction value
* `wind_speed` — wind-speed value generated from the pulse input

With the configured scaling of **0–5000 mV → 0–359°.**

```
2307 mV / 5000 mV × 359 ≈ 165.6°
```

The dashboard therefore confirms that the analog wind-direction signal is being acquired and converted correctly.

> During commissioning, rotate the wind vane and anemometer to confirm that both `w_direction` and `wind_speed` respond correctly across their operating range.
> {% endstep %}
> {% endstepper %}

## Rain Gauge <a href="#rain" id="rain"></a>

A **tipping-bucket rain gauge** converts rainfall into a sequence of electrical pulses.

Rainwater is collected through the funnel and directed into a small two-sided tipping bucket. As one side fills to a calibrated volume, the bucket tips and empties. A magnet attached to the tipping mechanism passes a **reed switch**, creating one electrical pulse for each tip.

Each pulse therefore represents a known amount of rainfall, defined by the sensor calibration or **mm per tip** value.

#### How FELYX Measures Rainfall

The rain-gauge output is connected to the YuDash data logger as a simple pulse input.

For the example shown here:

* one reed-switch wire is connected to **DI1**
* the second wire is connected to **GND**
* every valid bucket tip produces one pulse
* the data logger continuously counts these pulses in the background
* the pulse count is converted into rainfall using the configured **mm per tip** value

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDUuniHvKQ90IQrdN1h9d%2Frainfall_concept.png?alt=media&amp;token=a7340fea-6adf-4c6e-9ab4-6a6333433141" alt=""><figcaption></figcaption></figure>

Unlike wind speed, rainfall is not calculated only during a short sample window. The rain counter remains active continuously so that individual bucket tips are not missed.

A **debounce** setting is used to prevent contact bounce or electrical noise from causing a single physical tip to be counted more than once.

> **Rainfall accuracy depends on correct sensor settings.** The configured `mm per tip`, debounce and pulse-input wiring must match the rain-gauge manufacturer's specification.

### Configure Rain Gauge

1\) The wiring shown below is a **representative example** of connecting the Davis 6464 tipping-bucket rain gauge to a YuDash data logger using the sensor's RJ11 cable.

In standard terminal-input configurations, the rain pulse and ground conductors are connected to the appropriate **DI** and **GND** terminals. YuDash also offers product variants with **direct RJ11 sensor connectors** for simplified Davis installations.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FOmypWznoywclH8bl89bQ%2FFELYX_SensorIntegration%20(5).png?alt=media&amp;token=0f3300d6-2f6b-4f8c-bdc8-0ac2aec5ebaf" alt=""><figcaption></figcaption></figure>

2\) Open **Sensor Settings → Weather → Rain Gauge** and enable **Rain Gauge**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4YhXawTb8xY4haF13kNm%2Fconfiguration_6.png?alt=media&amp;token=34768569-3981-4a83-b61a-3de436ca19a6" alt=""><figcaption></figcaption></figure>

#### 3) Rain Gauge Settings

<table data-header-hidden><thead><tr><th width="144"></th><th width="161"></th><th></th></tr></thead><tbody><tr><td>Setting</td><td>Example</td><td>Description</td></tr><tr><td><strong>Gauge Mode</strong></td><td><code>0 — ISR (no deep sleep)</code></td><td>Standard rain-pulse counting mode. Keep this at <code>0</code> for normal installations. Other modes are intended for experimental/special use.</td></tr><tr><td><strong>mm Per Tip</strong></td><td><code>0.2</code></td><td>Rainfall represented by one valid bucket tip. This value must match the rain-gauge calibration.</td></tr><tr><td><strong>Debounce</strong></td><td><code>50 ms</code></td><td>Rejects additional contact transitions occurring immediately after a valid tip.</td></tr><tr><td><strong>Start of Day</strong></td><td><code>0</code></td><td>Defines when the daily rainfall counter rolls over, in minutes after local <code>00:00</code>.</td></tr><tr><td><strong>Rain Data Directory</strong></td><td><code>/rain_dir</code></td><td>Internal SD-card directory used by the rain-processing system.</td></tr></tbody></table>

> **Do not modify or delete files inside `/rain_dir`.** These files are maintained internally by the YuDash data logger for rainfall calculations and counter continuity.

#### 4) Rainfall Variables

The Weather feature maintains four rainfall variables. These values are refreshed on approximately a **one-minute basis**.

<table><thead><tr><th width="171">Variable</th><th>Meaning</th></tr></thead><tbody><tr><td><code>rain_today</code></td><td>Total rainfall accumulated during the current configured rainfall day</td></tr><tr><td><code>rain_yesterday</code></td><td>Total rainfall accumulated during the previous rainfall day</td></tr><tr><td><code>rain_curr_hr</code></td><td>Rainfall accumulated during the current clock hour</td></tr><tr><td><code>rain_prev_hr</code></td><td>Total rainfall accumulated during the immediately preceding clock hour</td></tr></tbody></table>

The variable names can be changed to suit the destination application.

Current Hour and Previous Hour

`rain_curr_hr` accumulates rainfall during the current local clock hour.

At the hour rollover, the completed value is transferred to `rain_prev_hr`, while `rain_curr_hr` starts again from zero.

#### 5) Start of Day

Rainfall calculations use the **device local time**. By default, the rainfall day changes at **00:00 local time**.

The **Start of Day** setting allows this rollover time to be shifted to match the reporting convention required by the applicable meteorological department or project specification. The value is entered as the number of minutes after midnight.

For example:

```
00:00 → 0
04:00 → 240
06:00 → 360
```

This setting affects **rainfall calculations only**. It does not change the device clock or the timestamp used by other measurements.

#### How Rainfall Variables Update

The example below illustrates how `rain_today`, `rain_yesterday`, `rain_curr_hr`, and `rain_prev_hr` change over time during rainfall.

It also shows how the configured **Start of Day** and hourly rollover affect the accumulated values.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmkTsKL4BpnU6gq08jmJi%2FTwo-Day%20Rainfall%20Variables%20Update%20Chart.png?alt=media&amp;token=5351ca06-ae44-4da5-9582-7ec9c1dcb440" alt=""><figcaption></figcaption></figure>


# Modbus TCP/IP

YuDash LYNX supports Modbus TCP/IP to read various PLC/HMIs through ethernet. In principle, following are the pre-requesites for using Modbus TCP/IP:

1. Valid Ethernet settings of YuDash LYNX for communication over TCP/IP.
2. LYNX is Modbus Client, who request the data. The given PLC is Modbus server, who will provide the data. LYNX can read multiple Modbus TCP/IP servers.
3. Following details of a given Modbus Server (PLC) are required for communication:

* **IP address** of PLC. For example: ***192.168.1.100***
* **IP Port** on which Modbus server is running. For example: ***502*** (standard port). Or ***8888*** (any port being used by PLC)
* **Modbus Server ID** as per protocol. For example: ***1*** (The Server ID of Modbus is similar to slave ID of Modbus RS-485)
* **Modbus Registers and Data Types** The mapping of registers and selection procedure is similar to Modbus RS-485

There are different network topology possible for interfacing PLC/HMI with LYNX using Modbus TCP/IP. For example:

#### A) Peer to Peer Direct Connection&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FiknnyIq390FC6OTjLxX8%2Fmodbus_tcpip_1.jpg?alt=media&amp;token=b59985b5-50e4-4017-9e04-26d2e3cda77b" alt=""><figcaption></figcaption></figure>

#### B) Through Ethernet Switch&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fd4ulpIu1YQKJ5djbxkTn%2Fmodbus_tcpip_2.jpg?alt=media&amp;token=7adfa5e6-c778-403a-a453-8c9bf4ee1eae" alt=""><figcaption></figcaption></figure>

#### C) Through LAN Router with Static IP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FLIR8UrT4w5Q8YZCiHKcD%2Fmodbus_tcpip_3.jpg?alt=media&amp;token=86d1c4e1-a512-41c4-9465-721fb6e7c9d0" alt=""><figcaption></figcaption></figure>

#### &#x20;D) Through LAN Router with Dynamic IP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FW6zpPsmKtiJ1d4YuuRdO%2Fmodbus_tcpip_4.jpg?alt=media&amp;token=e6c8daa0-5a43-453c-8091-bc0039a9e144" alt=""><figcaption></figcaption></figure>

All the scenarios of Modbus TCP/IP are covered in the video below.

{% embed url="<https://youtu.be/nYAulkX165c>" %}


# Data Scaling

**Data Scaling** is a generic data-processing layer available for YuDash variables. It can be applied to values acquired from different interfaces, including **Analog Inputs, Modbus, SDI-12, weather sensors, and other supported data sources**. The feature performs a configurable two-point linear transformation on an existing variable and can optionally apply minimum and maximum clipping limits before the value is used for logging, display, calculations, or telemetry.

Data Scaling operates **on the variable itself**. The **Variable Name** entered in the DataScale configuration must exactly match the variable name created by the corresponding input configuration. When a match is found, YuDash applies the scaling rule and updates that same variable with the processed value. DataScale does not create a separate output variable automatically.

If a DataScale entry refers to a variable that does not exist among the active input variables, that scaling rule is simply ignored. This allows DataScale configurations to coexist with different sensor configurations without affecting unrelated variables.

For example, a variable named `temperature` may originate from an analog input, while another variable such as `water_level` may originate from Modbus and `soil_moisture` from SDI-12. Data Scaling can be applied independently to any of them, provided the variable name in the DataScale rule matches the input variable name.

### How Data Scale Works

Data Scale works on a **two-point linear scaling model**, with optional minimum and maximum clipping. The user defines two input-to-output reference points:

* **Min In → Min Out**
* **Max In → Max Out**

These two points define the linear relationship between the raw input value and the required engineering value.

The diagram below illustrates the concept. **Point A** represents the lower reference point and **Point B** represents the upper reference point. YuDash calculates the corresponding output for values between these points, and also continues the same linear relationship for values outside the defined input range.

Optional **Min Cutoff** and **Max Cutoff** values can then be used to restrict the final output. In other words, **scaling determines the converted value, while clipping limits the final value if required**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQN4aAyOhCYBI3oWr7Og6%2Fdatascale_diagram1.jpg?alt=media&amp;token=f3818e99-4a26-4897-8c47-801b516fb269" alt=""><figcaption></figcaption></figure>

#### Important Notes

* The variable name in the Data Scaling table must match an existing YuDash input variable exactly.
* Data Scaling updates the **same variable**; it does not create a separate output variable automatically.
* If the configured variable name is not found in the active inputs, that Data Scaling row is ignored.
* The input value does **not** have to remain strictly inside the Min In / Max In range. YuDash still applies the linear equation, and the final value may then be limited by the optional cutoff values.
* The same Data Scaling feature can be used for **analog, Modbus, SDI-12, and other YuDash variables**.

### Example: Converting 4–20 mA to Temperature

A typical use of Data Scale is to convert a standard **4–20 mA transmitter signal** into an engineering value. In this example, a **Novus TxBlock-USB** converts a Pt100 temperature measurement of **−50 to 100 °C** into **4–20 mA**.

####

{% stepper %}
{% step %}

### Configure the transmitter

Configure the Novus TxBlock-USB using **TxConfig II**:

* Sensor: **Pt100, 3 wires**
* Range: **−50 to 100 °C**
* Output: **4–20 mA**

Thus:

**4 mA → −50 °C**\
**20 mA → 100 °C**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FSvYPkDiEGeGV0oczypp9%2F01_novus_txblock_configuration.png?alt=media&amp;token=ec0834ed-aba8-43b2-a6a0-ab4fc36e5a74" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

#### Connect the transmitter

Connect the **4–20 mA output** of the transmitter to a compatible YuDash analog input. This example uses **Analog Channel 1**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fqb08MytozBvse7cYVSNZ%2F02_connect_transmitter_to_analog_input.png?alt=media&amp;token=b061fbd4-7767-4535-a2d4-30dd0836f9f7" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Enable Analog Inputs and Data Scaling

Open **Device Settings** and enable:

* **Analog Inputs**
* **Data Scaling**

Write/update the device configuration after making the changes.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkaTcIVWDIpmCItn2l8bK%2F03_enable_analog_and_datascaling.png?alt=media&amp;token=21f65951-100f-4d9c-b434-29bce9b087bf" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the Analog Input

Go to **Sensor Settings → Open Analog Wizard**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FpBG438eNSLKE8TBuUnVy%2F04_open_analog_wizard.png?alt=media&amp;token=4bf58dc5-405a-4aca-b3a1-95a592127eb9" alt=""><figcaption></figcaption></figure>

Configure Channel 1 as:

| Setting         | Value                |
| --------------- | -------------------- |
| Topology        | A1: 0–20 mA          |
| Input           | 0 to 20              |
| Output          | 0 to 20              |
| Multiplier      | 1                    |
| Variable        | `Temperature`        |
| Backup Variable | `Temperature_Raw_mA` |

The channel therefore retains the signal in **mA** before Data Scale is applied. `Temperature_Raw_mA` keeps a copy of the raw current for diagnostics.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FlM5JnVr02FkEwcwMSAJE%2F05_configure_analog_channel.png?alt=media&amp;token=e266077d-0d87-4f93-a210-14658f5520f5" alt=""><figcaption></figcaption></figure>

{% endstep %}

{% step %}

### Open the DataScale Wizard

Return to **Sensor Settings** and select:

**Open DataScale Wizard**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6sdoRs4b52evRH9dFRjY%2F06_open_datascale_wizard.png?alt=media&amp;token=86f83542-d331-4b0a-8bf2-a4455a38b050" alt=""><figcaption></figcaption></figure>
{% endstep %}

{% step %}

### Configure the scaling

Add a Data Scale rule for `Temperature`:

| Setting       | Value         |
| ------------- | ------------- |
| Variable Name | `Temperature` |
| Min In        | 4             |
| Max In        | 20            |
| Min Out       | −50           |
| Max Out       | 100           |

The variable name must match the input variable exactly. Data Scale therefore converts the existing `Temperature` variable from **4–20 mA** to **−50 to 100 °C**.

For this example, the optional cutoff fields are left blank.

{% endstep %}

{% step %}

### Verify the scaled value

Open the **Live Dashboard**.

The example shows:

* `Temperature_Raw_mA` = **12.152 mA**
* `Temperature` = **26.421 °C**

This confirms that the raw transmitter current is being converted to the corresponding temperature value.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FeeeBwSjQ5GHC1OBo4XY4%2F08_verify_live_dashboard.png?alt=media&amp;token=11f7c37b-5e3e-41e1-bc07-50492d4afc8a" alt=""><figcaption></figcaption></figure>
{% endstep %}
{% endstepper %}

&#x20;


# Data Logging

YuDash data loggers support periodic data logging to an onboard microSD card. This feature is essential for applications requiring offline storage, regulatory audit trails. The files in the microSD card can be downloaded in laptop or it cane be accessed through YuDash interface.

## Data Logger Configuration

### 1. Enabling Data Logging

To enable the SD card logging feature:

1. Navigate to the **LYNX Settings** section from the side menu.
2. In the **Feature Settings** block, check the box labeled **Data Logging**.
3. Click **Write LYNX Config** to save the changes.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2WBHokwcjE0AEAUrWWQm%2F1.png?alt=media&amp;token=3ac570a4-31c5-4c73-93aa-afc501467d22" alt=""><figcaption></figcaption></figure>

4. SD Card logging requires both the **SD Card** and **RTC (Real-Time Clock)** features to be enabled in the configuration. If either is disabled, the logger will not function. Make sure both checkboxes are selected before setting up the data logger.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDQQjHMnyoYi2IAH4gh0q%2F2.png?alt=media&amp;token=00a2a66c-6d09-4e88-89d0-723e1b00ee79" alt=""><figcaption></figcaption></figure>

### 2. Data Logging Section

* **Navigate** to the **Data Logger Settings** tab from the sidebar.
* Click **Read Data Logger Settings** to load the current configuration from the device.
* Modify the necessary fields such as:
  * Logging interval
  * File cycle and naming
  * Encoder pattern or custom header
* After making changes, click **Update Data Logger Settings** to save the configuration to the device.
* There is an option to tick **Use Default Settings**. When this is enabled, the data logger uses its internal default configuration and other blocks can be blank. As soon as you provide any **custom entry** — like a header text or an encoder format — the corresponding default is overridden. Only fields left blank will fall back to default behavior.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FuCB7acQ60U2GrGtTS7Ll%2FYuDash_Datalogging.png?alt=media&amp;token=e3ec174d-c1c1-4813-bb67-1d2ff0b162a4" alt=""><figcaption></figcaption></figure>

### 3. File directory and name

In this section, you configure where and how the data logger files will be stored:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2qnw91uZz33YUrzGVp0a%2F4.png?alt=media&amp;token=b631c51d-08a5-4132-b6c0-751ad2205b91" alt=""><figcaption></figcaption></figure>

1. **Logger Directory**: Specifies the folder path on the SD card where log files will be created. Points to note:

   1. The path must begin with a forward slash `/` (root directory).
   2. Use `/` as the folder separator (like in Unix/Linux), **not** the Windows-style backslash `\`.
   3. **Do not** add a trailing slash at the end of the path.\
      ✅ `/logger_dir`   ❌ `/logger_dir/` or `\logger_dir\`
   4. The directory will be **automatically created** if it does not already exist on the SD card.

2. **File Name**

YuDash provides flexible file naming by allowing a customizable **prefix**, dynamic **timestamp insertion** (based on selected cycle), and optional **suffix**.\
This makes it easy to:

* Align with existing file naming conventions in your systems
* Simplify automated file parsing or importing on downstream software
* Organize logs by project, device, or department

The file name is constructed using a **prefix**, the **cycle-based timestamp**, and a **suffix**. The suffix is typically `.csv`, `.txt`, or any other extension as per your application's needs.

**File Name**: Define a custom file name using a **prefix** and **suffix**. The actual file name is generated dynamically using the selected **File Cycle:**

**file\_name = Prefix + Cycle + Suffix.**

**File Naming Examples for different Cylcles**

* **Prefix**: `log_`  **Suffix:** `.csv`
* **File Cycle Options**

| File Cycle               | Description                   | Example File Name          |
| ------------------------ | ----------------------------- | -------------------------- |
| **None**                 | Single file                   | `log_.csv`                 |
| **YYYY**                 | Yearly                        | `log_2025.csv`             |
| **YYYY\_MM**             | Monthly                       | `log_2025_06.csv`          |
| **YYYY\_MM\_DD**         | Daily                         | `log_2025_04_18.csv`       |
| **YYYY\_MM\_DD\_HH**     | Hourly                        | `log_2025_04_15_05.csv`    |
| **YYYY\_MM\_DD\_HH\_NN** | Per minute (for testing only) | `log_2025_04_15_05_03.csv` |

### 4. File content

In this section, you define the **format of each line** in the log file, including optional header text, timestamp placement, and variable encoding using a flexible text template.

1. **Optional File Header**
   * A one-time header line is added at the top **only when a new file is created** (e.g., on a new day or month depending on the file cycle).
   * Useful for column labels or unit information.
   * Can be left blank if not needed.
2. **Timestamp Format Selection**
   * Select the **TimeStamp format** from the dropdown. This determines the format that will be used when `#TS` is inserted into the encoder.
   * You can choose from UTC or Local time formats such as:
     * `YYYY-MM-DD HH:MM:SS`
     * `DD-MM-YYYY HH:MM:SS`
     * `UNIX_EPOCH`
     * `ISO 8601`
   * For a full list of available timestamp formats and codes (`TS_50` to `TS_66`), refer to the[ Time Stamp formats](https://docs.yudash.com/pf/pages/zVPbfkPk535M9wb3d1lP#h.t8n8abq6601b_l).&#x20;
3. **Logger Text Encoder**
   * This is a simple, text-based encoder that defines how each line in the log file is written. This is of format TEXT\_FORMAT\_20 of [YuTGT](/pf/ct/payload/yutgt-yudash-text-generator#yudash-text-generator-for-payload)
   * You can use:
     * **Single-character separators** such as `,`, `:`, `|`, , etc.
     * **Variable names** (e.g., `bod`, `tss`, `cod`) as defined in earlier configuration flows. These are replaced with their actual values during logging.
     * **Special `#` tags** to insert system-defined fields:
       * `#TS` → Timestamp (as per the selected format)
       * `#NL` → New line (typically added at the end of each encoder string to ensure proper row formatting)
       * Other #tags as per YuTGT
   * This flexible approach allows you to generate well-structured `.csv` or `.txt` files tailored to any downstream system.

## Example: Logging 4 Analog Channels with YuDash LYNX

This example shows how to configure YuDash LYNX to log data from 4 analog input channels to the SD card using default settings. No Modbus devices or cloud connection is required. You’ll get one `.csv` file per day, which can be opened directly in Excel. &#x20;

### Step 1: Load Example Configuration File

To get started quickly, you can **load the ready-made lynx configuration json file:**

{% file src="/files/6E8f95YcUHV6ouE78oNM" %}

Simply download above json file and load into YuDash device.&#x20;

#### Step-by-Step Review of Settings

Now let’s review what’s inside this file — based on screenshots and setting blocks:

***

**✅ 1. Enabled Features**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYqPS1CKK8YdO14o8S7hK%2F10.png?alt=media&amp;token=4827ee5c-9c5d-418e-8252-e2742e71328d" alt=""><figcaption></figcaption></figure>

In **LYNX Settings**:

* `Analog Inputs`: ✔️ Enabled
* `Data Logging`: ✔️ Enabled
* `Ethernet/LAN`: ✔️ Enabled (for accessing logs via LAN browser)
* Cloud/Network Server is set to "Offline"&#x20;

***

**✅ 2. Logging Frequency and RTC Settings**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fx83mlN9A0LmASgSYgRtg%2F11.png?alt=media&amp;token=1a960c94-b0c6-4020-abb5-4f68f88f75fc" alt=""><figcaption></figcaption></figure>

In **Advance Feature Settings**:

* `TimeSync Run (Minute)`: `1`\
  → This tells the logger to save data every 1 minute
* `Enable RTC`: ✔️ Checked
* `Enable SDCard`: ✔️ Checked

***

**✅ 3. Logger Settings (Default Mode)**

*(See Screenshot 112)*

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkUqJiluhelJxlrtI4Kyr%2F12.png?alt=media&amp;token=75e686a4-905b-4796-a4e5-3a5cdc8f1b2e" alt=""><figcaption></figcaption></figure>

In **Data Logger Settings**:

* `Use Default Settings`: ✔️ Enabled
* All other fields: left empty

> In this mode, the logger automatically:
>
> * Logs **all available analog inputs** (e.g., analog1 to analog4)
> * Adds a **timestamp** at the beginning
> * Uses **comma-separated CSV** format
> * Saves one file per day in `/logger_dir`

### Step 2: Run LYNX with uploaded lynx.json

Start by powering up the YuDash LYNX device with a microSD card inserted.

* You **do not need to connect any analog sensors** at this stage.
* LYNX will still log the 4 analog channels with default values (typically zero raw ADC readings).
* Let the device run for a few minutes so it can generate at least 2–3 log entries.

### Step 3: View the File Created on SD Card

After a few minutes of running, a log file will be created automatically on the SD card by the LYNX.

* **Folder Path:** `/logger_dir`
* **File Name Format:**

  ```
  logger_file_YYYY_MM_DD.csv
  ```

  For example: `logger_file_2025_06_12.csv`
* **Sample File Content (this example has analog inputs connected, with 5,10,15,20mA at inputs):**

{% file src="/files/buM6olJrtrb9n23IzB0W" %}

## Retrieval of data logger files in laptop/PC

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQnx84BySeJk7biYmdYMG%2Fpage7.png?alt=media&amp;token=49150715-52ea-442a-8d1e-5c842b3fa127" alt=""><figcaption></figcaption></figure>

The data files created by the YuDash logger on the SD card can be easily accessed using a laptop or desktop system. Follow the steps below (also illustrated in the image):

1. **Remove the SD Card from the Logger**
   * Gently push the SD card using a non-metal tool (e.g., plastic tweezer) to release it from the slot on the YuDash device.
2. **Insert SD Card into Laptop**
   * Use the built-in SD card slot (if available), or a USB card reader as shown in the example.
3. **Browse the Logger Directory**
   * Once inserted, the SD card appears as a removable drive.
   * Navigate to the configured **logger directory** (e.g., `/loggerDir`) to view the generated log files.
4. **Open Files in Excel or a Text Editor**
   * The files (typically `.csv` or `.txt`) can be opened in applications like Microsoft Excel, Notepad, or any spreadsheet/data analysis software for review and further processing.

> 📎 Tip: Ensure the logging cycle has completed (e.g., file has closed properly) before removing the SD card for reliable file reads.

SD card file access&#x20;


# Device Monitoring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2WBHokwcjE0AEAUrWWQm%2F1.png?alt=media&amp;token=3ac570a4-31c5-4c73-93aa-afc501467d22" alt=""><figcaption></figcaption></figure>

4. SD Card logging requires both the **SD Card** and **RTC (Real-Time Clock)** features to be enabled in the configuration. If either is disabled, the logger will not function. Make sure both checkboxes are selected before oder format — the corresponding default is overridden. Only fields left blank will fall back to default behavior.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FuCB7acQ60U2GrGtTS7Ll%2FYuDash_Datalogging.png?alt=media&amp;token=e3ec174d-c1c1-4813-bb67-1d2ff0b162a4" alt=""><figcaption></figcaption></figure>

### 3. File directory and name

In this section, you configure where and how the data logger files will be stored:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2qnw91uZz33YUrzGVp0a%2F4.png?alt=media&amp;token=b631c51d-08a5-4132-b6c0-751ad2205b91" alt=""><figcaption></figcaption></figure>

1. **Logger Directory**: Specifies the folder path on the SD card where log files will be created. Points to note:

   1. The path must begin with a forward slash `/` (root directory).
   2. Use `/` as the folder separator (like in Unix/Linux), **not** the Windows-style backslash `\`.
   3. **Do not** add a trailing slash at the end of the path.\
      ✅ `/logger_dir`   ❌ `/logger_dir/` or `\logger_dir\`
   4. The directory will be **automatically created** if it does not already exist on the SD card.

2. **File Name**

YuDash provides flexible file naming by allowing a customizable **prefix**, dynamic **timestamp insertion** (based on selected cycle), and optional **suffix**.\
This makes it easy to:

* Align with existing file naming conventions in your systems
* Simplify automated file parsing or importing on downstream software
* Organize logs by project, device, or department

The file name is constructed using a **prefix**, the **cycle-based timestamp**, and a **suffix**. The suffix is typically `.csv`, `.txt`, or any other extension as per your application's needs.

**File Name**: Define a custom file name using a **prefix** and **suffix**. The actual file name is generated dynamically using the selected **File Cycle:**

**file\_name = Prefix + Cycle + Suffix.**

**File Naming Examples for different Cylcles**

* **Prefix**: `log_`  **Suffix:** `.csv`
* **File Cycle Options**

| File Cycle               | Description                   | Example File Name          |
| ------------------------ | ----------------------------- | -------------------------- |
| **None**                 | Single file                   | `log_.csv`                 |
| **YYYY**                 | Yearly                        | `log_2025.csv`             |
| **YYYY\_MM**             | Monthly                       | `log_2025_06.csv`          |
| **YYYY\_MM\_DD**         | Daily                         | `log_2025_04_18.csv`       |
| **YYYY\_MM\_DD\_HH**     | Hourly                        | `log_2025_04_15_05.csv`    |
| **YYYY\_MM\_DD\_HH\_NN** | Per minute (for testing only) | `log_2025_04_15_05_03.csv` |

### 4. File content

In this section, you define the **format of each line** in the log file, including optional header text, timestamp placement, and variable encoding using a flexible text template.

1. **Optional File Header**
   * A one-time header line is added at the top **only when a new file is created** (e.g., on a new day or month depending on the file cycle).
   * Useful for column labels or unit information.
   * Can be left blank if not needed.
2. **Timestamp Format Selection**
   * Select the **TimeStamp format** from the dropdown. This determines the format that will be used when `#TS` is inserted into the encoder.
   * You can choose from UTC or Local time formats such as:
     * `YYYY-MM-DD HH:MM:SS`
     * `DD-MM-YYYY HH:MM:SS`
     * `UNIX_EPOCH`
     * `ISO 8601`
   * For a full list of available timestamp formats and codes (`TS_50` to `TS_66`), refer to the[ Time Stamp formats](https://docs.yudash.com/pf/pages/zVPbfkPk535M9wb3d1lP#h.t8n8abq6601b_l).&#x20;
3. **Logger Text Encoder**
   * This is a simple, text-based encoder that defines how each line in the log file is written. This is of format TEXT\_FORMAT\_20 of [YuTGT](/pf/ct/payload/yutgt-yudash-text-generator#yudash-text-generator-for-payload)
   * You can use:
     * **Single-character separators** such as `,`, `:`, `|`, , etc.
     * **Variable names** (e.g., `bod`, `tss`, `cod`) as defined in earlier configuration flows. These are replaced with their actual values during logging.
     * **Special `#` tags** to insert system-defined fields:
       * `#TS` → Timestamp (as per the selected format)
       * `#NL` → New line (typically added at the end of each encoder string to ensure proper row formatting)
       * Other #tags as per YuTGT
   * This flexible approach allows you to generate well-structured `.csv` or `.txt` files tailored to any downstream system.

## Example: Logging 4 Analog Channels with YuDash LYNX

This example shows how to configure YuDash LYNX to log data from 4 analog input channels to the SD card using default settings. No Modbus devices or cloud connection is required. You’ll get one `.csv` file per day, which can be opened directly in Excel. &#x20;

### Step 1: Load Example Configuration File

To get started quickly, you can **load the ready-made lynx configuration json file:**

{% file src="/files/6E8f95YcUHV6ouE78oNM" %}

Simply download above json file and load into YuDash device.&#x20;

#### Step-by-Step Review of Settings

Now let’s review what’s inside this file — based on screenshots and setting blocks:

***

**✅ 1. Enabled Features**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYqPS1CKK8YdO14o8S7hK%2F10.png?alt=media&amp;token=4827ee5c-9c5d-418e-8252-e2742e71328d" alt=""><figcaption></figcaption></figure>

In **LYNX Settings**:

* `Analog Inputs`: ✔️ Enabled
* `Data Logging`: ✔️ Enabled
* `Ethernet/LAN`: ✔️ Enabled (for accessing logs via LAN browser)
* Cloud/Network Server is set to "Offline"&#x20;

***

**✅ 2. Logging Frequency and RTC Settings**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fx83mlN9A0LmASgSYgRtg%2F11.png?alt=media&amp;token=1a960c94-b0c6-4020-abb5-4f68f88f75fc" alt=""><figcaption></figcaption></figure>

In **Advance Feature Settings**:

* `TimeSync Run (Minute)`: `1`\
  → This tells the logger to save data every 1 minute
* `Enable RTC`: ✔️ Checked
* `Enable SDCard`: ✔️ Checked

***

**✅ 3. Logger Settings (Default Mode)**

*(See Screenshot 112)*

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkUqJiluhelJxlrtI4Kyr%2F12.png?alt=media&amp;token=75e686a4-905b-4796-a4e5-3a5cdc8f1b2e" alt=""><figcaption></figcaption></figure>

In **Data Logger Settings**:

* `Use Default Settings`: ✔️ Enabled
* All other fields: left empty

> In this mode, the logger automatically:
>
> * Logs **all available analog inputs** (e.g., analog1 to analog4)
> * Adds a **timestamp** at the beginning
> * Uses **comma-separated CSV** format
> * Saves one file per day in `/logger_dir`

### Step 2: Run LYNX with uploaded lynx.json

Start by powering up the YuDash LYNX device with a microSD card inserted.

* You **do not need to connect any analog sensors** at this stage.
* LYNX will still log the 4 analog channels with default values (typically zero raw ADC readings).
* Let the device run for a few minutes so it can generate at least 2–3 log entries.

### Step 3: View the File Created on SD Card

After a few minutes of running, a log file will be created automatically on the SD card by the LYNX.

* **Folder Path:** `/logger_dir`
* **File Name Format:**

  ```
  logger_file_YYYY_MM_DD.csv
  ```

  For example: `logger_file_2025_06_12.csv`
* **Sample File Content (this example has analog inputs connected, with 5,10,15,20mA at inputs):**

{% file src="/files/buM6olJrtrb9n23IzB0W" %}

## Retrieval of data logger files in laptop/PC

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQnx84BySeJk7biYmdYMG%2Fpage7.png?alt=media&amp;token=49150715-52ea-442a-8d1e-5c842b3fa127" alt=""><figcaption></figcaption></figure>

The data files created by the YuDash logger on the SD card can be easily accessed using a laptop or desktop system. Follow the steps below (also illustrated in the image):

1. **Remove the SD Card from the Logger**
   * Gently push the SD card using a non-metal tool (e.g., plastic tweezer) to release it from the slot on the YuDash device.
2. **Insert SD Card into Laptop**
   * Use the built-in SD card slot (if available), or a USB card reader as shown in the example.
3. **Browse the Logger Directory**
   * Once inserted, the SD card appears as a removable drive.
   * Navigate to the configured **logger directory** (e.g., `/loggerDir`) to view the generated log files.
4. **Open Files in Excel or a Text Editor**
   * The files (typically `.csv` or `.txt`) can be opened in applications like Microsoft Excel, Notepad, or any spreadsheet/data analysis software for review and further processing.

> 📎 Tip: Ensure the logging cycle has completed (e.g., file has closed properly) before removing the SD card for reliable file reads.

SD card file access&#x20;


# Cloud Telemetry

Cloud Telemetry defines how data acquired by a YuDash device is transmitted to an **IoT platform, enterprise cloud, on-premise server or other remote application**.

This section covers the **cloud-facing side** of the YuDash IoT data path — from the data logger to the receiving platform or server.

### Understanding the Telemetry Path

The diagram shows the cloud telemetry path from **sensor values to the receiving server or cloud platform**. YuDash first acquires the field data, forms the required payload, and then transmits it through an available network using the selected cloud protocol.

The underlying network may be **Ethernet/LAN, 4G/LTE, Wi-Fi or another supported IP connection**. Network configuration is covered separately under **Network**.

```mermaid
flowchart BT

    A[Sensor Values]
    B[YuDash Data Logger]

    subgraph P[Payload Formation]
        P0[Structured Payload]
        P1[JSON]
        P2[Text / CSV]
    end

    subgraph N[Network]
        N0[Available Network]
        N1[Ethernet / LAN]
        N2[4G / LTE]
        N3[Wi-Fi]
        N4[Other Network]
    end

    subgraph T[Telemetry Protocol]
        T0[Available Protocol]
        T1[MQTT]
        T2[HTTP / HTTPS]
        T3[FTP]
    end

    S[Receiving Server / Cloud Platform]

    A --> B --> P0 --> N0 --> T0 --> S
```

### Cloud Protocols

YuDash supports multiple standard protocols for sending data to external servers and IoT platforms.

In cloud telemetry, the **YuDash device acts as the client/data sender**. It initiates the communication and sends data to the configured broker, server or endpoint.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Publish telemetry data to a configured MQTT broker.</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2BqNQjEwHQlJFWvk69TX%2Ficon_mqtt.png?alt=media&amp;token=5707026f-5a5f-4086-8168-a4a5fe3a91d1">icon_mqtt.png</a></td><td><a href="/pf/ct/mqtt">MQTT</a></td></tr><tr><td>Send telemetry data directly to a web server or API endpoint.</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYtlf2fl6PKnDRyAvVf76%2Ficon_rest_api.png?alt=media&amp;token=f965cc3c-6b30-4178-99ea-134b087bc2a0">icon_rest_api.png</a></td><td><a href="/pf/ct/http">HTTP</a></td></tr><tr><td>Upload telemetry or logged data files to a remote FTP server.</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmSAaTHQJ8cpsINRxoGGS%2Ficon_ftp.png?alt=media&amp;token=ef8914f2-b99d-4510-aa0b-5ec9c50a777a">icon_ftp.png</a></td><td></td></tr></tbody></table>

### Payload

The **payload** defines how the acquired sensor values are packaged before they are transmitted. The payload format is configured according to what the receiving server or platform expects.

YuDash supports configurable **JSON** and **text-based payloads**.

<table data-view="cards"><thead><tr><th></th><th data-hidden data-card-cover data-type="image">Cover image</th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td>Package telemetry data in structured JSON format for server integration.</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FsRBZZv4XH2tJe6CLYsn1%2Ficon_json_backup.png?alt=media&amp;token=bfa1d49f-8eb5-4ead-87a1-32a86c32019f">icon_json_backup.png</a></td><td><a href="/pf/ct/payload#json-payload">Payload</a></td></tr><tr><td>Format telemetry data as configurable text or CSV-style content.</td><td><a href="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkJxmVwVGTutHsjscp2jZ%2Ficon_csv_files.png?alt=media&amp;token=3d1ebfb3-0c9b-4b0b-b913-8154ea28305f">icon_csv_files.png</a></td><td></td></tr></tbody></table>


# MQTT

MQTT is a lightweight publish/subscribe protocol widely used for IoT telemetry.

In a typical YuDash installation, the **YuDash device acts as an MQTT client and publisher**. It connects to an MQTT broker and publishes the configured payload to a topic. The broker then makes that data available to the receiving IoT platform or other subscribed MQTT clients.

### MQTT Example

In this example, a YuDash FELYX device will publish two telemetry variables:

* **Temperature**
* **Humidity**

These variables may be acquired from any configured sensor interface, such as **Modbus, analog inputs, or another supported source**. Once available inside the device, they are encoded into a JSON payload and published over MQTT.

For this example, **ThingsBoard Cloud** is used as the receiving IoT platform and MQTT broker.

The target telemetry payload is:

```
{
  "Temperature": 29.01,
  "Humidity": 67.39
}
```

The complete flow is:

```mermaid
flowchart LR
    A["Temperature / Humidity"] --> B["YuDash FELYX"]
    B --> C["JSON_FORMAT_10"]
    C --> D["ThingsBoard MQTT Broker"]
```

#### Step 1 — Open the MQTT Wizard

From **Cloud Settings**, select **Open MQTT Wizard**.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FHtCsYRjH4tOAiBcQmJZL%2F01_mqtt_open_wizard.png?alt=media&amp;token=a203afc7-57b3-46f8-9cdc-decf16d4b13e" alt=""><figcaption></figcaption></figure>

***

#### Step 2 — Configure Broker & Topics

Enter the connection details supplied by the MQTT broker or IoT platform.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FhAlavFwpabR9TFosLeM8%2F02_mqtt_broker_topics.png?alt=media&amp;token=c3b262b1-706d-4c4f-b2c5-7c0e8f7076e9" alt=""><figcaption></figcaption></figure>

For the ThingsBoard example:

| Setting             | Example                    | Description                                          |
| ------------------- | -------------------------- | ---------------------------------------------------- |
| **Broker Host**     | `mqtt.thingsboard.cloud`   | MQTT broker hostname or IP address                   |
| **Port**            | `1883`                     | MQTT broker port                                     |
| **Client ID**       | `YuDash_FELYX`             | Client identifier used by the YuDash device          |
| **Username**        | `<ACCESS_TOKEN>`           | Username or access token required by the broker      |
| **Password**        | blank                      | Password, where required                             |
| **Publish Topic**   | `/v1/devices/me/telemetry` | Topic to which telemetry is published                |
| **Subscribe Topic** | optional                   | Topic used where incoming MQTT messages are required |
| **YuDM Topic**      | optional                   | Reserved for YuDash device-management applications   |

The current FELYX configuration stores the broker address, port, client name, username, password and publish topic as MQTT settings. mqtt\_thingsboard

> Broker authentication varies between platforms. Some brokers use a username and password, while others use an access token or allow unauthenticated connections.

#### Step 3 — Select MQTT as the Cloud Protocol

Under **Device Settings → Cloud / Network Server**, select:

**Custom Protocol → MQTT**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FFY2w1aCpeUI9A8YOYj3u%2F03_mqtt_select_protocol.png?alt=media&amp;token=0d53ae11-f941-43dd-a480-2f3cf49cd71c" alt=""><figcaption></figcaption></figure>

#### Step 4 — Configure the Payload

MQTT defines **how the data is transported**; the Payload settings define **what data is published**.

For this example, **`JSON_FORMAT_10`** is used to generate a simple JSON key-value payload.

The target payload is:

```
{
  "Temperature": 29.01,
  "Humidity": 67.39
}
```

Each acquired variable is sent directly as a JSON key-value pair. This is a simple and widely compatible format for MQTT telemetry.

Payload format, timestamp and optional metadata are configured separately under **Cloud Telemetry → Payload**.

### Step 5 — Verify MQTT Telemetry

Once configured, FELYX periodically acquires the configured sensor values, generates the payload and publishes it to the MQTT broker.

In this example, FELYX acquires **Temperature** and **Humidity** as the telemetry variables.

#### Verify with an MQTT Subscriber

An independent MQTT client such as **MQTTX** can also be used to subscribe to a topic and verify the messages available through the MQTT broker.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FLw5u1DsuR2DlQU9VeZVW%2F05_mqttx_received_payload.png?alt=media&amp;token=80b755bd-496a-4daa-bd16-0db179420c2f" alt=""><figcaption></figcaption></figure>

This is useful during commissioning because it allows the transmitted MQTT payload to be inspected independently of the final IoT application.

> MQTTX is shown here only as an example MQTT subscriber. Any compatible MQTT client may be used.

#### Verify in ThingsBoard

The latest values received by ThingsBoard can be viewed under the device's **Latest telemetry** section.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FBvr5v8qtjS3tuUUTjnDW%2F04_mqtt_thingsboard_latest_telemetry.png?alt=media&amp;token=3b4c374e-c86b-4990-b613-6eaa6149590b" alt=""><figcaption></figcaption></figure>

The received values confirm the complete telemetry path:

**Sensor → FELYX → MQTT Broker → ThingsBoard**

If required, the stored telemetry can also be viewed as a time series.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FtOEN2eCT9f1ooxjY9Ns0%2F06_mqtt_thingsboard_timeseries_optional.png?alt=media&amp;token=ad349e63-b5d2-4dee-bc2b-04a5214e8419" alt=""><figcaption></figcaption></figure>

####

### MQTT Publish Command Equivalent

Conceptually, the YuDash MQTT client performs the same operation as an MQTT publish command: it connects to the configured broker and publishes a payload to the configured topic.

For example:

```
mosquitto_pub \
  -h mqtt.thingsboard.cloud \
  -p 1883 \
  -t v1/devices/me/telemetry \
  -u "<ACCESS_TOKEN>" \
  -m '{"temperature":25}'
```

The corresponding relationship is:

| YuDash MQTT Setting     | `mosquitto_pub` option |
| ----------------------- | ---------------------- |
| Broker Host             | `-h`                   |
| Port                    | `-p`                   |
| Client ID               | `-i`                   |
| Username / Access Token | `-u`                   |
| Password                | `-P`                   |
| Publish Topic           | `-t`                   |
| Generated Payload       | `-m`                   |

The supplied ThingsBoard test uses the same broker, port, publish topic and access-token-style username. thingsboard\_mosquito

> **In simple terms, FELYX acts as an automated MQTT publisher:** it continuously acquires sensor data, generates the configured payload and publishes it to the configured MQTT broker.


# HTTP

YuDash IoT devices support data push through REST POST API. Both HTTP and HTTPS (SSL) are supported.

**HTTP** is the default TCP/IP protocol for cloud communication. YuDash LYNX supports POST REST API for sending data to HTTP Server. The HTTP headers can be configured to support  various authentication types.&#x20;

Following are the settings in LYNX to configure connection to HTTP server:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F5EjuYeSBJ83LzOftcKvX%2Fyudash_http.jpg?alt=media&amp;token=5347b041-79d2-4851-8b04-ee95cab715cb" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="215">HTTP Parameter</th><th>Description</th></tr></thead><tbody><tr><td>HTTP Server</td><td><p></p><p>The URL of HTTP server is faccessible on the network. Alternately, unique IP address can be provided. This may be required for a local deployment.</p><ul><li>Remove any prefixes (http:// or https://) in the server name.</li><li>Remove any suffix APIs from server name. They are provided in API below.</li></ul></td></tr><tr><td>HTTP API</td><td>The API name (similar to subdirectory) which will accept POST request. This will typically start with "/".</td></tr><tr><td>HTTP Port</td><td>The port on which HTTP server is running.</td></tr><tr><td>HTTP Success Code</td><td>Success code REST API. This is used to check if POST command by IoT device was success or failure. This value has to be set as per cloud API. </td></tr><tr><td>HTTP SSL Enabled</td><td>Check this box for enabling HTTPS using SSL. This is recommended for production applications.</td></tr></tbody></table>

### **HTTP Headers for Authentication**

1. HTTP supports various authentication options. The authentication header keys and values are filled in section.&#x20;
   * These are sent as HTTP headers to server for handshake.
   * The UI supports two headers. In case multiple custom headers are required, it can be configured in JSON configuration.&#x20;

### &#x20;Device headers with HTTP Payload

In many HTTP servers, there may be single API accepting inputs from various sensors. So, it may be sharing credentials across a set of devices. In such cases, additional device information (say, machine name, sensorID, user-name) may have to be passed in JSON payload. This is besides the actual real-time data collected from sensors. For this requirement, there is an option to add device headers in JSON formats.

### SSL/TLS secure communication with HTTP

YuDash IoT devices support HTTP with SSL/TLS secure communication. Refer to [SSL/TLS for HTTP ](/pf/ct/ssl#ssl-tls-for-http)documentation.

## LYNX Display with HTTP Post

Following are the typical LYNX display screens with HTTP POST

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FD8ifFUkSGOZtz9nP1u1x%2Fhttp1.jpg?alt=media&amp;token=51858108-2927-4d96-9f3d-d224b8990d15" alt=""><figcaption><p>LYNX attempting HTTP POST to a given API on port 443</p></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2Ukh4GKJRdOA5DTxIHyJ%2Fhttp2.jpg?alt=media&amp;token=c9f5abfc-a6bd-4954-8a1c-c4666fe297ee" alt=""><figcaption><p>LYNX waiting for response from HTTP server</p></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FZhpH9pNmK1sZQuE1dSj9%2Fhttp3.jpg?alt=media&amp;token=2b79550b-87f2-4b9d-808f-164708d6952d" alt=""><figcaption><p>LYNX received HTTP response of 200, which matched with success code of 200</p></figcaption></figure>


# FTP

File Transport Protocol

In general, [FTP ](https://en.wikipedia.org/wiki/File_Transfer_Protocol)(File Transfer Protocol) is an old protocol, not really suitable for IoT applications. But, there are many systems working on FTP for data logging.&#x20;

In principal, following are steps in file transfer in FTP:

1. Create a local file (typically text or CSV file) with a given name and text content.
2. Login to given FTP server (typically an IP address) using a login name and password.
3. Change directory at destination FTP server
4. Transfer the file from local device (YuDash IoT device) to FTP server

### Selection of FTP as cloud protocol in YuDash IoT Device

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6FzeButylX9hIBWgioPc%2F10.jpg?alt=media&amp;token=4e90e91d-18ab-49fd-b8eb-6125789d6a1c" alt=""><figcaption><p>FTP is selected as cloud protocol in Cloud/Network Server</p></figcaption></figure>

{% hint style="info" %}
For custom cloud server, please ensure "Use YuDash Cloud" is **unchecked**.
{% endhint %}

### Custom FTP Server Settings

FTP settings are available within the **Cloud Settings** section.

There are two sections in FTP settings, which are covered in following sections:

1. The FTP server details
2. The FTP file details (file name and content).&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FtWOliWhxjun4vLZVgNEF%2FYuDashHelpPages_CloudSettings%20(1).jpg?alt=media&amp;token=53ed4bfe-fab3-4930-a61a-9d05763ff8e3" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
Similar to all sub sections, you have to click on "Read FTP Settings" to load present FTP Settings. After updating, please click on "Update FTP Settings". New FTP settings block will be created if not present earlier.
{% endhint %}

### FTP Server Configuration

FTP server includes following components:

<table><thead><tr><th width="181">Component</th><th>Description</th></tr></thead><tbody><tr><td>FTP Server</td><td>The target FTP server, which is typically an IP address. </td></tr><tr><td>FTP User name</td><td>The user name for the given FTP server</td></tr><tr><td>FTP Password</td><td>The password to login to given FTP server</td></tr><tr><td>FTP Directory</td><td>The target FTP server directory where the payload fill will be uploaded by the YuDash IoT device.</td></tr></tbody></table>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FyD9hEr9CjaXhTXLsQwSz%2FFTP_server1.jpg?alt=media&amp;token=e2166e03-29f6-43ff-ba00-5022aba9ecfb" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
It is advisable that FTP server credentials are verified using a FTP client PC software, for example [coreFTP](https://www.coreftp.com/).
{% endhint %}

### FTP File Configuration

After FTP server details are configured, next step is to configure the file which will be transferred to FTP server. There are two parts to it:

1. **File content**: The file will have text content with mix of telemetry, metadata and possibly timestamp.
2. **File Name**: We need to define the ***file name***,  which will be created on given server directory. Typically, there a time stamp/snippet encoded in file name as we will uploading multiple files in same directory.

{% hint style="info" %}
YuDash don't support appending of file in FTP. A new file is created on the FTP server. Please contact us at <info@yudash.com> if you have this requirement. We can surely do it, subject to business use-case!
{% endhint %}

There are two ways to create FTP files in the YuDash device. This is categorized by radio box **FTP File Type**".

1. **Default:** This is a default format which make a 3 line file with pre-defined file naming convention. This is used for a specific compliance server.
2. **Generic:**  This is an extremely generic technique with flexibility of file name and content. In this case, file content is defined under payload setting.

### Generic FTP File Settings

#### File Content in Generic FTP File Settings

The file content of generic FTP File Type is defined under **Payload Settings.** Basically, the payload is the content of file, which can be technically a text or JSON payload. In most of cases, text payload will be used in FTP configuration. For this, powerful [YuTGT ](/pf/ct/payload/yutgt-yudash-text-generator)(YuDash Text Generator) is used to generate any kind of text payloads with mix of telemetry, separators and device meta-data. Please refer [YuTGT TuDash Text Generator ](/pf/ct/payload/yutgt-yudash-text-generator)documentation to get familiar with semantics.

#### File Name is Generic FTP File Settings

The file name itself is generated using the YuTGT. Following two settings are defined under "**Generic FTP File Settings**"

1. &#x20;File Name Encoder: The input text to [YuTGT](/pf/ct/payload/yutgt-yudash-text-generator) to create the **file name**. The file name is created using semantics of  [YuTGT](/pf/ct/payload/yutgt-yudash-text-generator).
2. File Name TimeStamp: The time stamp format (if required) to be used in the file name creation. This is similar to TimeStamp format used in [payload ](/pf/ct/payload/json)settings.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRB3JezWc6io2RNE4Csdr%2FFTP_generic1.jpg?alt=media&amp;token=7b080946-01a4-46bf-afcf-e363680608e0" alt=""><figcaption></figcaption></figure>

### Generic FTP File Example

We will explain the FTP file creation using an example. This uses [YuTGT Example#1](/pf/ct/payload/yutgt-yudash-text-generator#yutgt-examples) for payload generation.

File name encoder has following input

```
#YY #MM #DD #HH #NN #SS $_file.csv
```

Sample generated file and file name: **20240518101304\_file.csv**

{% file src="/files/Kd8HpxelAt3t3nvoaBtR" %}

&#x20;

### FTP Troubleshooting guide

In case of connection errors to FTP server for first time, please refer to following trouble shooting guide:

<details>

<summary>I am new to FTP. How do I start?</summary>

First and foremost, in case you are not able to connect to FTP server from YuDash IoT device, first connect to the server using FTP client PC software, for example [coreFTP](https://www.coreftp.com/). This will ensure that credentials and network access is correct.

</details>

<details>

<summary>I am not able to connect to FTP from my broadband (ethernet/WiFi) from YuDash or PC</summary>

FTP works on TCP/IP port 20 (data) and 21 (control). In many cases, these ports are disabled in router. Please enable these in your router settings.

In most of cases of 4G/LTE network, we have not observed this problem. So, a mobile wifi hotspot based on 4G/LTE may be good option to try.&#x20;

</details>

<details>

<summary>My PC client is working, but YuDash is not working</summary>

Please check FTP settings within YuDash. Few points to check:

* Don't put any prefix (ftp\:// etc) in the IP address.
* The FTP directory should start with slash /
* Try some other network settings (WiFi/ 4G/Ethernet)
* Ensure that target FTP directory has read/write access.

</details>

<details>

<summary>How to reach YuDash support</summary>

Please contact us on <sales@yudash.com> with your details. It is mandatory that FTP credentials are verified by customer through PC based client.

</details>

###


# SSL/TLS

YuDash IoT gateways supports SSL/TLS secure communication for MQTT and HTTP protocol.

Following are typical steps to enable SSL/TLS security layer

1. Enable TLS/SSL within the cloud protocol settings.
2. Change the server port for TLS/SSL communication.
3. Upload server CA certificate in the IoT device.

{% hint style="info" %}
This documentation explains the TLS for CA signed server, which require a single pem file. For self signed TLS (involving pem, crt  and key), refer to this [documentation](/pf/ct/ssl/selfsigned).
{% endhint %}

### **SSL/TLS for MQTT**

1\) Enable "SSL/TLS" radio button in **MQTT Secure Layer**. Change the **MQTT port** pertaining to secure layer of server. This is typically 8883 for MQTT.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F1I9cfAGzT8i0ZDG099dy%2Fmqtt_30.jpg?alt=media&amp;token=1366f074-bb51-401a-b4f8-e0873a9459b1" alt=""><figcaption></figcaption></figure>

2\) Upload server CA certificate to IoT device. First, **Choose File** and select the .pem file from local computer. Then, click on **Load SSL/TLS File** which will load the file in the browser. Finally, click on **Write SSL/TLS file**, which will write the the file into the IoT device.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2GhsCAkXenL5vugyegLI%2Fmqtt_31.jpg?alt=media&amp;token=13f0bd39-59bb-43d4-bf2b-3ac5e61559c5" alt=""><figcaption></figcaption></figure>

3\) Following message is shown when CA certificate file is written successfully.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Feqsmc8ntVp7p20tua9eJ%2Fmqtt_32.jpg?alt=media&amp;token=744c6e6b-7133-4932-9554-506fed2c7e57" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
By default, the CA certificate for MQTT protocol is stored as file name /assets/mqtt\_cacert.pem within the YuDash IoT device.&#x20;
{% endhint %}

### **SSL/TLS for HTTP**

1\) Enable "SSL/TLS" radio button in **HTTP Secure Layer**. Change the **HTTP port** pertaining to secure layer of server. This is typically 443 for HTTP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F7qs5c6MtlC19J2oU3pBx%2Fhttp_33.jpg?alt=media&amp;token=129e19d4-057a-4704-b164-8295f0a9d075" alt=""><figcaption></figcaption></figure>

2\) Upload server CA certificate to IoT device. First, **Choose File** and select the .pem file from local computer. Then, click on **Load SSL/TLS File** which will load the file in the browser. Finally, click on **Write SSL/TLS file**, which will write the the file into the IoT device.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fo3TQAbInDYDsmlHCQYnF%2Fhttp_34.jpg?alt=media&amp;token=d85d53b9-b8dd-4251-a7ff-49c8f2979dc1" alt=""><figcaption></figcaption></figure>

3\) Following message is shown when CA certificate is written successfully.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FiJKDtEj7GcxHGC7U0gYh%2Fhttp_35.jpg?alt=media&amp;token=d48bbc35-bf86-4134-8380-d9114db41245" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
By default, the CA certificate for HTTP protocol is stored as file name /assets/http\_cacert.pem within the YuDash IoT device.&#x20;
{% endhint %}


# MQTT with Self Signed TLS

This tutorial explains how to enable TLS security using **self-signed certificates** with YuDash products.

To establish a secure connection with the MQTT broker, the client must present the following three files during the TLS handshake:

* **CA Certificate** (`.pem`) – Certificate Authority file used to verify the server's certificate.
* **Client Certificate** (`.crt`) – Identifies the YuDash device to the server.
* **Client Private Key** (`.key`) – Used to prove ownership of the client certificate.

To use self-signed TLS certificates with YuDash devices, you must upload the required files via the **Assets** section on the YuDash configuration page.

{% hint style="info" %}
Before configuring TLS settings on your YuDash device, it is **strongly recommended** to first verify the MQTT connection using a desktop client such as **MQTTX** (or any similar tool).

This helps ensure that:

* The server is accessible,
* The self-signed certificates are valid,
* The MQTT topic and credentials are correct.

Once the connection works reliably on your PC/laptop, you can proceed to apply the same settings in the YuDash JSON configuration.
{% endhint %}

## Connecting YuDash to AWS IoT Core via MQTT

In this tutorial, we will walk through the process of configuring **YuDash devices** to connect with **AWS IoT Core** over MQTT.

To ensure a smooth setup, we will first demonstrate the connection using the **MQTTX** desktop client as a reference. Once verified, the same configuration can be applied to YuDash via its JSON settings.

### **1) MQTT General Settings in MQTTX**

MQTTX General Settings are filled with AWS IoT Core broker details. "CA or Self signed certificate" is selected.&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F1GYFBd5Rt7D3C2cRTJXl%2F1.png?alt=media&amp;token=1aad6aee-6211-47e3-8089-f5d47e0bfb06" alt=""><figcaption></figcaption></figure>

### &#x20;&#x32;**) Certificates section in MQTTX**

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FPUy1NQzqOphD038uxc6u%2F2.png?alt=media&amp;token=c5626f60-6239-4275-b554-f21e03d8c488" alt=""><figcaption></figcaption></figure>

### 3) MQTT Settings mapped to YuDash configuration

The MQTT settings are per regular MQTT settings. MQTT Secure Layer is enabled. We will not select "MQTT CA Certificate" as we will use self signed certificates. These files will uploaded from Assets section (explained in next step).

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FMhJOnbTNu2Q4pL8EmCu4%2F3.png?alt=media&amp;token=ee66ad06-0b3a-46dd-aeb5-c429e2ecb067" alt=""><figcaption></figcaption></figure>

### 4)  Uploading Certificate files in YuDash through Assets folder

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FJF2jPXomx6J2ZHPHYdjb%2FYuDash_TLS_AWS_self_signed.png?alt=media&amp;token=20c4c324-bdd4-414f-b847-e620e529659a" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FIv6SQT4NVjgtRFev9ytd%2F6.png?alt=media&amp;token=780b2537-3a59-4ef3-a16c-762ed1086bba" alt=""><figcaption></figcaption></figure>

### 5) Mapping the uploaded certificate files in MQTT Settings

After the certificate files are uploaded in the YuDash IoT device (/assets), the MQTT settings have to be manually updated in lynx.json file. Besides regular MQTT settings, the "tls\*" keys have to be inserted for mapping to certificate files.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4mUnJaU2xDZQKraLFDGJ%2F7.png?alt=media&amp;token=11c2013d-f89f-4765-a58c-d3b7d1fd26cb" alt=""><figcaption></figcaption></figure>

### 6) Sample lynx.json for self signed certificate

Following is sample mqttSettings block to use self signed certificate in TLS

```json
// sample MQTT settings in lynx.json
  "mqttSettings": {
    "platformName": "AWS",
    "mqttSSL": 1,
    "mqttServer": "MQTT_broker_url",  // as per server settings
    "userName": "<username>",           
    "password": "<password>",
    "publishTopic": "<publis_topic>",
    "clientName": "<client_name>",
    "mqttTLS": 1,
    "tlsCaCert": "/assets/AmazonRootCA1.pem", // names as per uploaded files.
    "tlsClientCert": "/assets/AWS1.pem.crt",
    "tlsClientKey": "/assets/AWS1.pem.key",
    "tlsSetInsecure": 0,
    "mqttPort": "8883",
  },
```


# Payload

A **payload** is the structured data generated by the YuDash device before it is transmitted to a server or written to a file.

The core payload contains the acquired **sensor data**. Depending on the application, optional metadata such as a **timestamp, device header, and device status** can also be included before the final JSON or TXT payload is generated.

```mermaid
flowchart LR
    A["Sensor Data"] --> B["Payload Encoder"]
    C["Timestamp"] --> B
    D["Device Header"] --> B
    E["Device Status"] --> B

    B --> F["JSON / TXT Payload"]
```

### Payload Configuration

Payload settings are configured from:

**Cloud Settings → Payload → Open Payload Wizard**

The **Payload Formatter Wizard** controls how acquired sensor data is encoded before it is transmitted or stored.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FF8F3c77Nd5OJK0Oj8uYC%2F01_payload_open_wizard_full_highlight.png?alt=media&amp;token=cc547e62-3504-4fa7-9244-c92e595b59fc" alt=""><figcaption></figcaption></figure>

#### Payload Format

The **Payload Format** selects the encoder used to generate the final payload. YuDash provides simple predefined JSON formats as well as configurable JSON and text generators.

Use **Format & Keys** to select the required format.

<table><thead><tr><th width="207">Payload Format</th><th>Use</th></tr></thead><tbody><tr><td><strong>JSON_FORMAT_10</strong></td><td>Standard key-value JSON payload. Recommended starting format for most MQTT and HTTP integrations.</td></tr><tr><td><strong>JSON_FORMAT_11 .. 18</strong></td><td>Other predefined JSON structures for specific integration requirements and existing deployments.</td></tr><tr><td><strong>JSON_FORMAT_19</strong></td><td>Configurable JSON generator for creating custom JSON payload structures.</td></tr><tr><td><strong>TXT20</strong></td><td>Configurable text generator for text, CSV-style, FTP and data-logging formats.</td></tr></tbody></table>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FsmfxHSGrmY8tMa8HQpJc%2F02_payload_format_keys.png?alt=media&amp;token=a5187b46-d9c0-4679-9c9d-7684ec73b4b1" alt=""><figcaption></figcaption></figure>

{% hint style="info" %}
**For most new JSON integrations, start with JSON10.** Use JSON19 when the receiving system requires a custom JSON structure.
{% endhint %}

## JSON Payload

JSON payloads provide a structured format for sending acquired variables to MQTT brokers, HTTP/HTTPS APIs and other applications that accept JSON data.

For most integrations, **JSON\_FORMAT\_10** is the recommended starting point. Alternative predefined structures are available where required, while **JSON\_FORMAT\_19** provides a configurable JSON generator for custom payloads.

#### JSON\_FORMAT\_10 — Standard Key-Value Payload

JSON10 sends each YuDash variable directly as a JSON key-value pair.

```
{
  "volt1_in": 237.67,
  "freq_in": 49.98,
  "kwhr_in": 1792.17
}
```

This simple structure works well for most MQTT and HTTP integrations where the receiving server can directly use the YuDash variable names.

***

#### JSON11 — Two-Level Payload

JSON11 creates a two-level JSON structure, with each variable name used as the main key.

```
{
  "volt1_in": {
    "value": 244.4
  },
  "freq_in": {
    "value": 50
  },
  "kwhr_in": {
    "value": 1792.17
  }
}
```

The secondary key, such as `value`, is configurable.

#### Other Predefined JSON Formats

Additional predefined JSON formats are available for **specific platforms, legacy integrations and application-specific data structures**.

### JSON\_FORMAT\_19 — JSON Template Engine

`JSON_FORMAT_19` enables the [**YuDash JSON Template Engine**](/pf/ct/payload/json), a generic payload engine for creating custom JSON structures to match application-specific APIs and server schemas.

Use the [**JSON Generator**](/pf/ct/payload) page for template syntax, live variables, device metadata, timestamps, nested objects and arrays./

### Time Stamp

A timestamp can be added to the generated payload when the receiving application requires the time associated with the data.

Enable **Send TimeStamp**, then configure:

* **Time Stamp Key** — the JSON key used for the timestamp, for example `ts`, `timestamp` or `time`
* **Time Stamp Format** — the required timestamp representation

The timestamp is inserted into the generated JSON along with the sensor data.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F0yQgxJZKt6tJxi68jbxq%2F04_payload_timestamp_settings.png?alt=media&amp;token=5626e5ea-b951-43ad-a167-3a862990d5a6" alt=""><figcaption></figcaption></figure>

#### UTC Timestamp Formats

| Format                                    | Sample Time Stamp      |
| ----------------------------------------- | ---------------------- |
| **TS\_50 — UTC Seconds**                  | `1675630526`           |
| **TS\_51 — UTC MilliSeconds**             | `1675630526000`        |
| **TS\_52 — UTC YYYY-MM-DDTHH:MM:SS**      | `2023-02-05T20:55:26Z` |
| **TS\_53 — UTC YYYY-MM-DD HH:MM:SS**      | `2023-02-05 20:55:26`  |
| **TS\_54 — UTC YYYY\_MM\_DD\_HH\_MM\_SS** | `2023_02_05_20_55_26`  |
| **TS\_55 — UTC YYYY-MM-DDTHH:MM:00**      | `2023-02-05 20:55:00`  |
| **TS\_56 — UTC DD-MM-YYYY HH:MM:SS**      | `05-02-2023 20:55:26`  |

For **TS\_55**, seconds are set to `00`.

#### Local Time Timestamp Formats

| Format     | Representation                     |
| ---------- | ---------------------------------- |
| **TS\_60** | LocalTime Seconds                  |
| **TS\_61** | LocalTime MilliSeconds             |
| **TS\_62** | LocalTime YYYY-MM-DDTHH:MM:SS      |
| **TS\_63** | LocalTime YYYY-MM-DD HH:MM:SS      |
| **TS\_64** | LocalTime YYYY\_MM\_DD\_HH\_MM\_SS |
| **TS\_65** | LocalTime YYYY-MM-DDTHH:MM:00      |
| **TS\_66** | LocalTime DD-MM-YYYY HH:MM:SS      |

#### Example

With `JSON_FORMAT_10` and a timestamp key configured as `timestamp`:

```
{
  "volt1_in": 247.55,
  "freq_in": 49.94,
  "kwhr_in": 1792.17,
  "timestamp": "1675630887"
}
```

The **timestamp key is configurable**; common choices include `timestamp`, `ts` and `time`.

### Device Headers

**Device Headers** add identification or other metadata to the JSON payload in addition to the acquired sensor data.

A header consists of a **Key** and a **Value**. The value can either be a fixed value entered by the user or a dynamic YuDash metadata reference.

#### Fixed Key-Value Headers

Use a fixed value when the information remains constant for the installation.

For example:

| Header Key   | Header Value |
| ------------ | ------------ |
| `device_id`  | `YU10005054` |
| `station_id` | `STATION001` |

With `JSON_FORMAT_10`, these headers are added alongside the measured variables:

```
{
  "temperature": 28.4,
  "humidity": 67.2,
  "device_id": "YU10005054",
  "station_id": "STATION001"
}
```

Fixed headers are useful for application-specific identifiers such as a site name, station code or customer-defined device ID.

***

#### Dynamic Device Metadata

Instead of entering a fixed value, the Header Value can use a supported **`@` metadata reference**. YuDash resolves the reference when the payload is generated, allowing information such as the device serial number, station ID or firmware version to be included automatically.

For example:

| Header Key   | Header Value |
| ------------ | ------------ |
| `station_id` | `@YSID`      |
| `serial_no`  | `@YDNO`      |
| `firmware`   | `@YFWV`      |

The transmitted JSON then contains the actual runtime values rather than the `@` references.

#### Available Metadata References

| Reference | Value                             |
| --------- | --------------------------------- |
| `@YSID`   | Station ID                        |
| `@YDNO`   | Device serial number              |
| `@YFWV`   | Firmware version                  |
| `@YMC1`   | MAC address without separators    |
| `@YMC2`   | Device MAC-address representation |
| `@EIPA`   | Ethernet IP address               |
| `@MBSL`   | Modbus Slave ID as text           |
| `@MBSI`   | Modbus Slave ID as a number       |
| `@FGDB`   | Cellular signal-strength value    |
| `@YUTS`   | Generated payload timestamp       |

These metadata references are resolved by the YuDash payload engine at runtime.

> **Fixed values** are transmitted exactly as configured. **`@` metadata values** are resolved dynamically each time the payload is generated.


# JSON Generator

The **YuDash JSON Template Engine** creates custom JSON payloads for MQTT, HTTP and other server/API integrations.

Unlike predefined payload formats, the JSON Template Engine does not impose a fixed JSON structure. The user defines a reference JSON template, and the data logger dynamically inserts live sensor values, timestamps and device metadata into that structure at runtime.

This makes the engine suitable for integrating with APIs that require their own field names, nested objects, arrays, parameter metadata, timestamps, device identifiers or other application-specific content.

The generated output remains valid JSON and can closely match the schema expected by the receiving application.

{% hint style="info" %}
**Payload Format:** Select `JSON_FORMAT_19` in the Payload Formatter to use the **JSON Template Engine**.
{% endhint %}

### How the JSON Template Engine Works

The engine starts with a **reference JSON template**.

The template may contain normal static JSON together with special YuDash references. At runtime, the data logger processes the complete JSON structure and replaces these references with current values.

```mermaid
flowchart LR
    A["Reference JSON<br/>Template"] --> B["JSON Template Engine"]

    C["Static JSON"] --> B
    D["$ Live Variables"] --> B
    E["@ Device Metadata"] --> B
    F["@YUTS Timestamp"] --> B

    B --> G["Generated JSON Payload"]
```

Objects and arrays remain actual JSON structures. Numerical sensor values are inserted as JSON numbers rather than being converted into quoted text.

### Template Syntax

The JSON Template Engine uses a small set of conventions.

| Template content    | Example                 | Behaviour                                     |
| ------------------- | ----------------------- | --------------------------------------------- |
| **Static value**    | `"unit": "mA"`          | Sent exactly as entered                       |
| **Live variable**   | `"value": "$analog_1"`  | Replaced with the current value of `analog_1` |
| **Device metadata** | `"station_id": "@YSID"` | Replaced with a YuDash device/system value    |
| **Timestamp**       | `"date_time": "@YUTS"`  | Replaced with the configured timestamp        |

The **JSON keys are defined entirely by the application**. They do not need to match the internal YuDash variable names.

For example:

```json
"bod": "$analog_1"
```

means:

> Use the current value of the YuDash variable `analog_1`, but publish it under the JSON key `bod`.

### Example 1 — Simple Key-Value Mapping

A basic template can directly map YuDash variables to the field names required by the receiving application.

#### Template

```json
{
  "bod": "$analog_1",
  "cod": "$analog_2",
  "tss": "$analog_3",
  "ph": "$analog_4"
}
```

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FvinhjdhVnAbia8IfC4vI%2F01_simple_template_config.png?alt=media&amp;token=4e4aba38-8eb6-4df5-aeb9-581fe0741233" alt=""><figcaption></figcaption></figure>

#### Generated Payload

```json
{
  "bod": 5.9965,
  "cod": 6.99675,
  "tss": 7.997,
  "ph": 8.99725
}
```

The `$` prefix identifies a **live YuDash variable**. At runtime, each reference is replaced by the current value of that variable. The test output confirms this substitution.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FaDjb6jGI9BDemH8fpXLh%2F02_simple_template_mqtt_output.png?alt=media&amp;token=c3e0ab12-f5d6-46f9-9ff7-ea931cb98c48" alt=""><figcaption></figcaption></figure>

### Live Variables — `$`

A JSON string value beginning with `$` is treated as a reference to a current YuDash datapoint.

For example:

```json
{
  "temperature": "$temperature",
  "humidity": "$humidity"
}
```

If the current values are `28.4` and `67.2`, the generated payload becomes:

```json
{
  "temperature": 28.4,
  "humidity": 67.2
}
```

The engine preserves the runtime data type where supported. Numerical datapoints are inserted as JSON numbers, while strings and Boolean values can retain their corresponding JSON types.

> The referenced variable must exist in the current YuDash datapoint set. The name should match the configured sensor, calculated or other generated variable.

***

### Example 2 — Nested JSON with Metadata

The JSON Template Engine can combine sensor values with device metadata, timestamps and nested JSON objects.

#### Template

```json
{
  "station_id": "@YSID",
  "device_id": "yu10005054",
  "date_time": "@YUTS",
  "sensor_data": {
    "analog_1": "$analog_1",
    "analog_2": "$analog_2",
    "analog_3": "$analog_3",
    "analog_4": "$analog_4"
  }
}
```

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F8sFJuYbZ8g1IgHymlPN6%2F03_nested_json_template_config%20(1).png?alt=media&amp;token=dea9fca3-b3c6-47b2-87f7-dd5b83da7f4f" alt=""><figcaption></figcaption></figure>

#### Generated Payload

```json
{
  "date_time": "2026-10-18 13:29:46",
  "device_id": "yu10005054",
  "sensor_data": {
    "analog_1": 5.9965,
    "analog_2": 6.99675,
    "analog_3": 7.99625,
    "analog_4": 8.99725
  },
  "station_id": "station001"
}
```

Here:

* `device_id` is a **static value**
* $analog\_1 to $analog\_4 are **live variables**
* `@YSID` inserts the configured **Station ID**
* `@YUTS` inserts the generated **timestamp**

The resulting nested structure is created directly by the engine. payload

***

### Device Metadata — `@`

YuDash provides system-generated values that can be inserted into the template using `@` references.

For example:

```json
{
  "station_id": "@YSID",
  "firmware": "@YFWV",
  "timestamp": "@YUTS",
  "temperature": "$temperature"
}
```

Unlike `$` variables, these values describe the **device or runtime environment** rather than a measured process variable.

Device metadata can also be added to predefined payload formats through the **Device Headers** settings. The JSON Template Engine provides additional flexibility by allowing these values to be positioned directly within a custom JSON hierarchy.

***

### Timestamp — `@YUTS`

`@YUTS` inserts the timestamp generated by the Payload Formatter.

The required representation is defined using the **Timestamp Encoder**.

For example:

```
#YY-#MM-#DD#SP#HH:#NN:#SS
```

generates:

```
2026-10-18 14:02:50
```

Therefore:

```
{
  "observed_at": "@YUTS"
}
```

becomes:

```
{
  "observed_at": "2026-10-18 14:02:50"
}
```

`@YUTS` may be used at multiple locations within the same JSON template.

***

### Example 3 — Array-Based API Payload

Many APIs expect measurements as an **array of parameter objects** rather than as a simple key-value object.

The JSON Template Engine can generate this structure directly.

#### Template

```json
{
  "station_id": "@YSID",
  "device_id": "yu10005054",
  "date_time": "@YUTS",
  "sensor_data": [
    {
      "observed_at": "@YUTS",
      "parameter_key": "Analog_1",
      "value": "$analog_1",
      "unit": "mA"
    },
    {
      "observed_at": "@YUTS",
      "parameter_key": "Analog_2",
      "value": "$analog_2",
      "unit": "mA"
    },
    {
      "observed_at": "@YUTS",
      "parameter_key": "Analog_3",
      "value": "$analog_3",
      "unit": "mA"
    },
    {
      "observed_at": "@YUTS",
      "parameter_key": "Analog_4",
      "value": "$analog_4",
      "unit": "mA"
    }
  ]
}
```

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FIMC21btZxI6nWs3sDeXO%2F04_array_json_template_config.png?alt=media&amp;token=6e3b311b-7b24-460c-8b25-fdba583f1d5c" alt=""><figcaption></figcaption></figure>

#### Generated Payload

```json
{
  "date_time": "2026-10-18 14:02:50",
  "device_id": "yu10005054",
  "sensor_data": [
    {
      "observed_at": "2026-10-18 14:02:50",
      "parameter_key": "Analog_1",
      "unit": "mA",
      "value": 5.9965
    },
    {
      "observed_at": "2026-10-18 14:02:50",
      "parameter_key": "Analog_2",
      "unit": "mA",
      "value": 6.99675
    },
    {
      "observed_at": "2026-10-18 14:02:50",
      "parameter_key": "Analog_3",
      "unit": "mA",
      "value": 7.99625
    },
    {
      "observed_at": "2026-10-18 14:02:50",
      "parameter_key": "Analog_4",
      "unit": "mA",
      "value": 8.996562
    }
  ],
  "station_id": "station001"
}
```

This example combines **arrays, nested objects, repeated timestamps, live variables, static parameter metadata and device metadata** in a single payload. payload

This makes the engine particularly useful when integrating YuDash devices directly with APIs that mandate their own telemetry schema.

***

### Timestamp Encoder Reference

The Timestamp Encoder controls the representation inserted by `@YUTS`.

| Token | Meaning              | Example      |
| ----- | -------------------- | ------------ |
| `#YY` | Four-digit year      | `2026`       |
| `#MM` | Month                | `10`         |
| `#DD` | Day                  | `18`         |
| `#HH` | Hour                 | `14`         |
| `#NN` | Minute               | `02`         |
| `#SS` | Second               | `50`         |
| `#DT` | Date as `YYYY_MM_DD` | `2026_10_18` |
| `#TD` | Time as `HH_MM_SS`   | `14_02_50`   |
| `#SP` | Space                |              |
| `#NL` | New line             | line break   |

Normal non-space characters may be used as separators.

For example:

```
#YY/#MM/#DD#SP#HH:#NN:#SS
```

produces:

```
2026/10/18 14:02:50
```

while:

```
#YY-#MM-#DDT#HH:#NN:#SS
```

produces:

```
2026-10-18T14:02:50
```

> Literal spaces in the encoder are ignored. Use `#SP` whenever an actual space is required in the generated timestamp.

Timestamp timezone selection is configured separately in the Payload timestamp settings.

***

## Device Metadata Reference

The following device/system values can currently be resolved by the JSON Template Engine:

| Code    | Runtime value                           |
| ------- | --------------------------------------- |
| `@YSID` | Station ID                              |
| `@YDNO` | Device serial number                    |
| `@YFWV` | Firmware version                        |
| `@YMC1` | MAC address without separators          |
| `@YMC2` | Device MAC-address representation       |
| `@EIPA` | Ethernet IP address                     |
| `@MBSL` | Modbus Slave ID represented as text     |
| `@MBSI` | Modbus Slave ID represented as a number |
| `@FGDB` | Cellular signal-strength value          |
| `@YUTS` | Generated payload timestamp             |

These references may be combined with static content and `$` live variables.

For example:

```
{
  "serial_no": "@YDNO",
  "station_id": "@YSID",
  "firmware": "@YFWV",
  "timestamp": "@YUTS",
  "flow": "$flow_rate"
}
```

***

### Advanced — Variable Groups

The JSON Template Engine also supports insertion of a **YuDash variable group** into a JSON object.

A template entry whose key begins with:

```
YU_VARGROUP
```

can reference a configured variable-group number. During payload generation, the datapoints belonging to that group are dynamically inserted into the corresponding JSON object.

This can be useful where a larger collection of variables needs to be transmitted without explicitly listing every $variable in the template.

> For fixed third-party API schemas, explicit $variable mappings are generally easier to read and maintain. Variable-group insertion is intended for more advanced or dynamic applications.

I would keep this section short until we have a clean worked UI example.

***

### Engine Behaviour

The JSON Template Engine recursively processes both **JSON objects and JSON arrays**.

Static values remain unchanged, while recognised `$` and `@` references are resolved at runtime. This allows static application metadata and dynamic YuDash data to coexist anywhere inside the same payload.

If a referenced datapoint is in an error state, the engine can substitute the configured payload error value instead of a normal datapoint.

The JSON Template Engine defines the **payload structure**. MQTT broker settings, HTTP endpoint configuration, transmission interval and network connectivity are configured independently.

***

### When to Use the JSON Template Engine

Use a **predefined JSON payload**, such as the standard key-value format, when the receiving system accepts a straightforward payload.

Use the **JSON Template Engine** when the destination API requires a specific structure, for example:

```json
{
  "station": "...",
  "timestamp": "...",
  "measurements": [
    {
      "parameter": "...",
      "value": 0,
      "unit": "..."
    }
  ]
}
```

The engine allows this structure to be generated **directly at the edge**, reducing or eliminating the need for an intermediate payload-conversion service.


# YuTGT: YuDash Text Generator

YuDash Text Generator

YuDash Text Generator is a powerful engine to generate any kind of text payload in flexible manner including the telemetry, metadata and timestamps. YuDash Text Generator is primarily used to generate text&#x20;

### YuDash Text Generator for Payload&#x20;

The YuDash Text Generator is primarily for payload generator, which is explained here. It is also used in FTP file name creation, and local data logging. The semantics for engine remains same.

### Payload Settings

1. Select the payload Format of "TEXT\_FORMAT\_20" to use YuTGT.
2. Select the timestamp format to be used in Text Generator.
3. The configuration to YuDash Text Generator&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FIzpHfMybesCU8H08m7Jd%2FYuTGT1.jpg?alt=media&amp;token=537b216f-55b0-43cc-880f-91a2292f6ba5" alt=""><figcaption></figcaption></figure>

### YuDash Text Generator Block

The YuTGT block contains the series of encoding block (string) to generate the output payload text. Each string is separated by blank space(s). The complete block is processed by YuTGT engine to generate the text payload in every run-cycle.

#### YuTGT String components

<table><thead><tr><th width="182">Encoding String</th><th>Description</th></tr></thead><tbody><tr><td>$meta_data</td><td>The string prefixed by $ is encoded as it is in the output text (with $ removed). It is used to encoder any meta_data in the output text.</td></tr><tr><td>Single character</td><td>A single character (probably ,  . # etc) is encoded as it is in the output text. This simplifies creation of CSV without cryptic encoding. It is assumed that variable names are at least 2 characters! </td></tr><tr><td>#AA Encoder</td><td>The string prefixed with an # followed by 2 capital letters are used to encode specific data-times and special characters.</td></tr><tr><td>#TS</td><td>The timestamp as selected in payload settings will be encoded in the text. It can be UTC or local-time as per selection in Time-Stamp Settings.</td></tr><tr><td>#YY</td><td>Year encoded as 4 digits. This is taken from local-time.</td></tr><tr><td>#MM</td><td>Month encoded as 2 digits. This is taken from local-time.</td></tr><tr><td>#DD</td><td>Date encoded as 2 digits. This is taken from local-time.</td></tr><tr><td>#HH</td><td>Hour encoded as 2 digits. It is taken in 24 hour cycle from localtime. </td></tr><tr><td>#NN</td><td>Minutes encoded 2 digits. It is taken from local-time. Please note that minutes is #NN (not #MM, which used in month). </td></tr><tr><td>#SS</td><td>Seconds encoded as 2 digits. It is taken from local-time.</td></tr><tr><td>#DT</td><td>Date is format YYYY_MM_DD in encoded. It is taken from local-time.</td></tr><tr><td>#TD</td><td>TimeOfDay of format HH_NN_SS is encoded.</td></tr><tr><td>#NL</td><td>New line character. Please use #NL at end if you need and newline after text. Also, this is used to create a multi-line text file.</td></tr><tr><td>#SP</td><td>A black space is generated in the output text.</td></tr><tr><td>normal_string</td><td>A normal string is one without a prefix (a $ or an #) and at least 2 character long. <br>This is looked up in the variables of payload and replaced with the actual value. Notes:<br>a) For example, a <strong>temperature</strong> variable read from modbus written as 234.56 in the output text. The numbers are written as 2 decimal digits as default.<br>b) In case the normal_string is not found in the variable list, it is ignored and no output text will be generated.<br>c) In case, there was an error associated with reading of given variable (say modbus read error), the error string can be encoded in the output. It has to be specified in JSON configuration (not available in UI)</td></tr></tbody></table>

## &#x20;YuTGT Examples

Let's understand the YuDash Text Generator by actual examples. In all the examples, we are reading temperature and humidity from XY02 modbus sensor which are read as **temp** and **humid** in Modbus Settings.

#### YuTGT Example#1

Input YuDash Text Encoder Block

```
#YY / #MM / #DD , #HH : #NN : #SS , temp , humid , #NL
```

Output Text payload

```
2024/05/18,10:13:04,38.50,27.70,

```

Explanation

* \#YY #MM and #DD are replaced with present date. They were encoded with / in between.&#x20;
* \#HH #NN #SS was the time block, which were encoded with : in between.
* The **temp** and **humid** values as read from Modbus sensor were encoded with comma separators.
* Finally, **#NL** adds a newline to the output file.

#### YuTGT Example#2

Input YuDash Text Encoder Block

```
$date , $temp , $humid #NL , $celcius , $percent #NL #TS , temp , humid , #NL
```

Output Text payload

```
date,temp,humid
,celcius,percent
2024_05_18_11_12_12,38.70,27.80,
```

Explanation

* $date $temp $humid strings are encoded as raw string (meta) data.&#x20;
* \#NL is used to create  multiple line file with new lines between 3 parts.
* \#TS is used to generate a fixed time stamp format. Timestamp format of TS\_64 has been selected in TimeStamp section to generate given time stamp.
* The actual value of temp and humid were encoded in the output text.


# Axon Edge

**YuDash Axon** is the edge intelligence layer built into **YuDash IoT devices**, designed to preprocess data at the device level before forwarding it to the cloud or industrial systems. It enables real-time transformation, computation, and standardization of raw inputs from a wide range of sensors and instruments.  This feature is available only in few part numbers.

***

#### **Key Features of Axon**

* **🧩** [**YuParse**](/pf/ax/parse)\
  Extracts structured values from ASCII/text sensor outputs using pattern-based parsing. Supports flexible tokenized patterns (`#D1`, `#A2`, etc.) and maps them to named variables.
* **➗ Calculator**\
  Perform real-time computations using parsed or raw values. Supports arithmetic expressions like addition, multiplier and basic functions (`min()`, `abs()`, etc.) to derive synthetic values at the edge.


# YuParse

**YuParse** is a lightweight and efficient ASCII/text parser designed for real-time data extraction on the edge. It is a core component of the **YuDash Axon** processing engine and is optimized for structured sensor output from industrial instruments such as weather stations, weighing scales, and transmitters.

YuParse uses a **pattern-matching approach** where users define a template string with token identifiers (like `#D1`, `#I2`, `#T`, `#A1`, etc.) to extract specific fields from continuous or formatted ASCII inputs. It is tolerant to inconsistent whitespace and supports both data capture and structural matching.

YuParse simplifies the challenge of parsing vendor-specific ASCII formats by providing a flexible yet deterministic framework that decouples pattern logic from parsing code. It enables high-throughput, low-overhead data structuring — critical for scalable IIoT deployments.

The values extracted by YuParse can be directly utilized in various downstream pipelines. Parsed fields can be published to MQTT or HTTP endpoints. Additionally, these values can be fed into YuDash’s built-in Modbus RS485 or TCP/IP server, enabling seamless SCADA or PLC integration. This makes YuDash a powerful edge converter — capable of translating vendor-specific ASCII outputs into json payloads or  Modbus-readable registers.

Following are the steps to use YuParse Engine:

### 1) Reading text data from RS485/RS232 device

The reading of text data from RS485 (or RS232) port is handled as custom "Modbus" registers, as explained here. Refer to documentation of [String Read in RS485/RS232](/pf/si/modbus/string).  The string is provided as input (inputVar) to YuParse engine which will be matched with "pattern" string.

### 2) YuParse Pattern

This the pattern string which will be used to parse the inputVar.

* YuParse matches the `inputVar` (ASCII string) against the provided **`pattern`**.
* By default, whitespace is ignored during matching for both inputVar and pattern. Extra spaces, tabs, or inconsistent spacing do not affect parsing. For strict parsing of inputVar, there is an option (described later).
* The pattern is composed of:
  * **Tokens** (e.g., `#D1`, `#A2`) used to capture values.
  * Tokens without a numeric index (e.g., `#D`, `#S`) are treated as **match-only** and **not stored** in the output.
  * **Static strings** (e.g., `TEMP=`, `RH=`, `(Gross)`) that must match exactly
* **Matching is case-sensitive** for static strings (`TEMP` ≠ `temp`).
* YuParse performs a **best effort left-to-right match**, allowing partial parsing when some fields are missing or invalid.
* Parsing stops when:
  * The pattern is fully matched
  * Or the input string ends unexpectedly or mismatches

<table data-header-hidden><thead><tr><th width="159"></th><th width="161"></th><th width="115"></th><th></th></tr></thead><tbody><tr><td>Pattern Element</td><td>Type</td><td>Stored?</td><td>Description</td></tr><tr><td>#D1, #D2</td><td>Decimal/Float</td><td>✅ Yes</td><td>Parsed as float</td></tr><tr><td>#I1, #I2</td><td>Integer</td><td>✅ Yes</td><td>Parsed as integer</td></tr><tr><td>#T1</td><td>Timestamp</td><td>✅ Yes</td><td>Epoch timestamp</td></tr><tr><td>#S1, #S2</td><td>String</td><td>✅ Yes</td><td>Any text until next whitespace</td></tr><tr><td>#A1, #A2</td><td>Alphanumeric</td><td>✅ Yes</td><td>Strictly alphanumeric (letters and digits only)</td></tr><tr><td>#Sx</td><td>String ending with fixed character</td><td>❌ No</td><td><p>Any text until a known character (x). </p><p>x may be mostly a "," or "=" etc.</p></td></tr><tr><td>#D, #S, #A</td><td>Match-only</td><td>❌ No</td><td>Used for pattern alignment; parsed but not stored</td></tr><tr><td>#N</td><td>New line</td><td>❌ No</td><td>Match a new line (\n) or carriage return (\r). </td></tr><tr><td>Non-token word</td><td>Literal Match</td><td>❌ No</td><td>Must exactly match input, ignoring extra whitespace</td></tr></tbody></table>

| **Input String (inputVar)**        | **YuParse Pattern (pattern)**   | **Parsed Values**            |
| ---------------------------------- | ------------------------------- | ---------------------------- |
| `TEMP=23.4 RH=65.2`                | `TEMP=#D1 RH=#D2`               | `D1=23.4`, `D2=65.2`         |
| `STATUS=(OK) VALUE=99.8`           | `STATUS=(#A1) VALUE=#D1`        | `A1=OK`, `D1=99.8`           |
| `Device=ABC TEMP=45.0 UNIT=C`      | `Device=#A TEMP=#D1 UNIT=#S`    | `D1=45.0`                    |
| `Device=ABC TEMP=45.0 UNIT=C`      | `#S=#A1 TEMP=#D1 UNIT=#A2`      | `A1=ABC, D1=45.0 A2=C`       |
| `t=21.5 , humid=(64.2)%`           | `t=#D1 , humid=(#D2)%`          | `D1=21.5`, `D2=64.2`         |
| `(Gross) 125.67 kg (Tare) 5.00 kg` | `(Gross) #D1 kg (Tare) #D2 kg`  | `D1=125.67`, `D2=5.00`       |
| `TEMP:23.4,HUMIDITY:55.6`          | `TEMP:#D1,HUMIDITY:#D2`         | `D1=23.4`, `D2=55.6`         |
| `S/N=SNX123 Value=7.89`            | `S/N=#A1 Value=#D1`             | `A1=SNX123`, `D1=7.89`       |
| `Sensor1=OK Pressure=102.56 mbar`  | `Sensor1=#A1 Pressure=#D1 mbar` | `A1=OK`, `D1=102.56`         |
| `DATA: A23 B56 C99`                | `DATA: #A1 #A2 #A3`             | `A1=A23`, `A2=B56`, `A3=C99` |
| `WSpd=5.2 Dir=NW Temp=21.3`        | `WSpd=#D Dir=#A1 Temp=#D2`      | `A1=NW`, `D2=21.3`           |

### **3) Mapping Tags to Variable Names**

After parsing the input string using the pattern, YuParse assigns values to temporary tags such as `D1`, `A2`, `S1`, etc. These tags must then be **mapped to user-defined variable names** to make them meaningful and usable in further processing.

* Mapping is defined using the `tagArray` field in your configuration.
* Each entry maps a **token tag** (e.g., `"D1"`) to a **custom variable name** (e.g., `"temperature"`).
* These variable names are similar to other variables read by YuDash devices. They can be published to MQTT/HTTP or used in Modbus server (only for numeric numbers)

## YuDash JSON APIs for Axon

### 1) Enabling YuDash Axon

* Axon must be **explicitly enabled** using `"axon": 1`
* The `axonSettings` block is ignored unless Axon is active
* **Axon is supported only on selected YuDash models**&#x20;

```json
"dotFourSettings": {
  ...
  "axon": 1,
  ...
}
```

### 2) YuParse Settings within axonSettings&#x20;

```json
{
  "dotFourSettings": {
    // ... other flags and features
    "axon": 1
  },

  "axonSettings": {
    "parseArray": [
      {
        "inputVar": "sensor_string",
        "pattern": "TEMP=#D1 RH=#D2",
        "tagArray": [
          { "tagName": "D1", "varName": "temperature" },
          { "tagName": "D2", "varName": "humidity" }
        ]
      }
    ]
  },

  // ... other settings like mqttSettings
}
```

### Syntax of the Json blocks

<table><thead><tr><th width="129">Key</th><th width="122">Type</th><th>Description</th></tr></thead><tbody><tr><td><code>inputVar</code></td><td>string</td><td>Name of the input variable holding the ASCII string to be parsed. This is typically read through Modbus module.</td></tr><tr><td><code>pattern</code></td><td>string</td><td>YuParse-compatible pattern using tokens like <code>#D1</code>, <code>#A1</code>, etc. This will be matched with the inputVar.</td></tr><tr><td><code>tagArray</code></td><td>array</td><td>List of mappings between token tags and output variable names. </td></tr><tr><td><code>tagName</code></td><td>string</td><td>The token ID from the pattern (e.g., <code>"D1"</code>, <code>"A2"</code>, <code>"T"</code>)</td></tr><tr><td><code>varName</code></td><td>string</td><td>Custom variable name to use in downstream logic, MQTT, Modbus, etc.</td></tr></tbody></table>

### Explanation of the json

* `sensor_string` is assumed to be an ASCII input like:

  ```
  TEMP=23.4 RH=56.2
  ```
* The `pattern` uses tokens `#D1` and `#D2` to extract two decimal numbers
* These are mapped to final variable names `temperature` and `humidity` via `tagArray`
* These variables can then be used in the payload.

## **Whitespace-Sensitive Parsing**

By default, YuParse **ignores all whitespace** (spaces, tabs, etc.) in the input string when matching against a pattern.

To enable **strict whitespace matching**, set `"whiteSpace": 1` inside a `parseArray` block.

#### 🔖 **Special Token for Whitespace-Sensitive Mode**

<table><thead><tr><th width="172">Token</th><th>Meaning</th><th>Notes</th></tr></thead><tbody><tr><td><code>#W</code></td><td>Match <strong>any number</strong> of whitespace characters</td><td>Required only when <code>whiteSpace</code> is <code>1</code></td></tr></tbody></table>

📌 **Note:** The `#N` (newline) token can be used in both whitespace-sensitive and default modes. Newlines are **not ignored**, even when general whitespace is ignored.

#### 🧾 Example **of Whitespace Matching**

```json
{
  "parseArray": [
    {
      "inputVar": "sensor_data",
      "pattern": "VOLT=#D1 #W UNIT=V",
      "whiteSpace": 1,
      "tagArray": [
        { "tagName": "D1", "varName": "voltage" }
      ]
    }
  ]
}
```

***

## YuParse Examples

### **1) Example#1**

**Input String:**

```
tT=(24.5C) RH=(64.3)%
```

#### **YuParse JSON Configuration**

```json

  "axonSettings": {
    "parseArray": [
      {
        "inputVar": "env_data",
        "pattern": "T=(#D1C) RH=(#D2)%",
        "tagArray": [
          { "tagName": "D1", "varName": "temperature_c" },
          { "tagName": "D2", "varName": "humidity_percent" }
        ]
      }
    ]
  }

```

### **2) Example#2**

**Input String:**

```
TEMP=22.3 RH=48.2 STATUS=OK
```

#### **YuParse JSON Configuration**

```json


  "axonSettings": {
    "parseArray": [
      {
        "inputVar": "sensor_raw",
        "pattern": "TEMP=#D1 RH=#D2 STATUS=#A1",
        "tagArray": [
          { "tagName": "D1", "varName": "temperature" },
          { "tagName": "D2", "varName": "humidity" },
          { "tagName": "A1", "varName": "status" }
        ]
      }
    ]
  }

```

### 3) **Example: Parsing Vaisala WXT530 Output**

**🧾 Sample Input String:**

```
Ta=24.7C RH=53.2% P=1007.3hPa Ws=2.3m/s Wd=180D
```

***

#### ⚙️ **Expected Output Variables:**

```json
{
  "temperature": 24.7,
  "humidity": 53.2,
  "pressure": 1007.3,
  "windspeed": 2.3,
  "winddir": 180
}
```

***

#### **YuParse JSON Configuration**

```json

  "axonSettings": {
    "parseArray": [
      {
        "inputVar": "vaisala_string",
        "pattern": "Ta=#D1C RH=#D2% P=#D3hPa Ws=#D4m/s Wd=#D5D",
        "tagArray": [
          { "tagName": "D1", "varName": "temperature" },
          { "tagName": "D2", "varName": "humidity" },
          { "tagName": "D3", "varName": "pressure" },
          { "tagName": "D4", "varName": "windspeed" },
          { "tagName": "D5", "varName": "winddir" }
        ]
      }
    ]
  }
}
```

### 4) **Example:**&#x20;

YuParse supports parsing **multiple input strings simultaneously**, each potentially coming from different sensors or serial sources.\
To enable this, the configuration uses a **`parseArray` array**, where:

* Each item in the array defines a **separate parsing block**
* Each block specifies:
  * An `inputVar` (input string source)
  * A `pattern` to match
  * A `tagArray` to map captured values to usable variable names

This design allows you to process **multiple ASCII inputs in parallel**, even if they come from different instruments or formats.

***

#### 🧾 Input Strings

* `env1_string`:

  ```
  TEMP=23.4 RH=56.2
  ```
* `env2_string`:

  ```
  Ta=24.7C RH=53.2% P=1007.3hPa
  ```

***

#### JSON Configuration

```json

  "axonSettings": {
    "parseArray": [
      {
        "inputVar": "env1_string",
        "pattern": "TEMP=#D1 RH=#D2",
        "tagArray": [
          { "tagName": "D1", "varName": "temperature1" },
          { "tagName": "D2", "varName": "humidity1" }
        ]
      },
      {
        "inputVar": "env2_string",
        "pattern": "Ta=#D1C RH=#D2% P=#D3hPa",
        "tagArray": [
          { "tagName": "D1", "varName": "temperature2" },
          { "tagName": "D2", "varName": "humidity2" },
          { "tagName": "D3", "varName": "pressure2" }
        ]
      }
    ]
  }
}
```

***

#### **Resulting Output Variables**

```json
{
  "temperature1": 23.4,
  "humidity1": 56.2,
  "temperature2": 24.7,
  "humidity2": 53.2,
  "pressure2": 1007.3
}
```


# Advance Features


# Modbus Server

Typically, YuDash IoT devices act as Modbus master (client) reading data from the instruments or PLCs. The data is sent to some cloud server through MQTT or REST API. &#x20;

There are many applications in which aggregated data is required on SCADA systems. For these applications, YuDash IoT devices act as per Modbus Server (Slave) on a given RS485 port or Ethernet (Modbus TCP/IP).

Effectively any inputs read by YuDash (4-20mA analog inputs, RS485 or even MQTT subscribe) can be provided on Modbus server on configured port.  The YuDash IoT devices can be configured as dedicated Modbus server or they can be configured in parallel to regular cloud data push.

Modbus Server feature is explained in following tutorials:

## [YuDash ZENYX for Analog to Modbus RS/485 Server (Slave)](/pf/af/ms/anambus)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FPJlHrgyD1Poww1C6hyYD%2F17.jpg?alt=media&amp;token=afb676f9-f40b-4039-b6ad-5f6ca7279a1d" alt=""><figcaption></figcaption></figure>

&#x20;

YuDash LYNX as Analog to Modbus TCP/IP Server

&#x20;

YuDash IoT devices support acting as Modbus Server (RS485 or Modbus TCP/IP)


# Analog to Modbus/RS485 Server (Slave)

In this tutorial, YuDash ZENYX will be used to read 4 channel analog inputs (4-20mA) and act as Modbus/RS485 slave (server).&#x20;

{% hint style="info" %}
Ready-to-use json configuration files are available for ZENYX and LYNX in the end of the tutoral. They can simply be loaded into the device for quick start.
{% endhint %}

## 1) Connection Diagram

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FPJlHrgyD1Poww1C6hyYD%2F17.jpg?alt=media&amp;token=afb676f9-f40b-4039-b6ad-5f6ca7279a1d" alt=""><figcaption></figcaption></figure>

1. Test setup of 4 channel 4-20mA analog generator is connected (red line) to analog inputs of ZENYX. The value of 5, 10, 15 and 20 mA are being generated in the test setup.
2. The Modbus/RS485 is connected to RS485-USB converter (yellow and green) for modbus read on the laptop. ZENYX Modbus/RS85 is configured as modbus slave (server).
3. The Modbus Poll software is acting as modbus master in the laptop. It is reading ZENYX Modbus/RS485 and receiving 4 analog values on given modbus registers.

{% hint style="info" %}
Modbus Poll [download link](https://www.modbustools.com/download.html)
{% endhint %}

## 2) General Settings in ZENYX settings

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F8FxI6KK2aETZT4zjG1Ey%2F18.jpg?alt=media&amp;token=4f3b6d8f-3b60-46c2-80f1-b602e6fa64f9" alt=""><figcaption></figcaption></figure>

* **Loop Delay** is set to 0.  As we act as server, we want to read input data continuously without any delay.
* **Analog Inputs** is enabled to read 4-20mA input.
* The Cloud/Network set to to "**Offline**". In this usage, we are not sending data to any server.&#x20;

{% hint style="info" %}
Notes in general settings:

1\) Modbus/RS485 is NOT enabled here (which makes YuDash as Modbus master). We will be enabling Modbus/RS485 server in the next step

2\) The datascale feature of YuDash can be used to scale the analog input to required process values. This is not covered in this tutorial for simplicity.
{% endhint %}

## 3) Analog Input Settings in ZENYX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FXwcIy17blJSTpIpVssdj%2F19.jpg?alt=media&amp;token=6e0062dd-597b-43bf-ab17-87eca4d4b338" alt=""><figcaption></figcaption></figure>

* **Analog Input Settings:** The four analog inputs are enabled. We read 0-20mA inputs.
* The four variables are read as **analog1**, **analog2**, **analog3** and **analog4**. These variables will be mapped to Modbus/RS485 server register in next section.&#x20;

## 4) Modbus Server Settings

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FfucAihCPRPNoeM3GmA6V%2F20.jpg?alt=media&amp;token=4d07a98e-d073-42b4-8a70-ec63ae00e1eb" alt=""><figcaption></figcaption></figure>

* **Modbus Server Type:** This is selected as RS485. This pertains to RS485 acting as Modbus Server (Slave). *In case of LYNX, this maps to first RS485 channel acting as server.*
* **Modbus RS485 Server Settings:**
  * Modbus Server Id:  Enter the Slave ID as per choice.  (selected as 1 at present)
  * BaudRate: Required baud rate. Selected as 9600. &#x20;
  * Data Parity: Required data parity. Selected as 8N1.
* **Modbus Server Register Settings block**
  * You need to click "Open Modbus Server Settings" to open the details.
  * Click on "Read Modbus Server Settings" to check existing mappings.
  * Click on "Update Modbus Server Settings" after any changes.
* **Modbus Server Register Settings**
  * Input variables "analog1" is mapped to 40000 register as floating point output.&#x20;
  * The "Var Type" is set to 2 (floating point data type). This is the only supported data type at present. So, 2 modbus registers are used for one variable.
  * The "Enable Modbus Register" checkbox enables the value. This entry is ignored/delete if the check box is not present.&#x20;
  * In the tutorial, the four analog inputs variables (analog1, analog2, analog3 and analog4) are mapped to registers 40000 40002 40004 and 40006&#x20;

## 5) Tutorial Json configuration file

Above 4 steps complete the configuration in the ZENYX. These settings are readily available in the following json file. We recommend loading below json file to run through the tutorial.

{% file src="/files/PzcfHV4L3cJMRaLTnGJT" %}

## 6) Advance Feature Settings (optional)

These settings pertain to using TimeSync mode within "Advane Feature Settings".&#x20;

In case RTC and timeSync is enabled in the advance settings, loopDelay=0 will be ignored. In this case TimeSync Server Mode sould be enabled for fast response.&#x20;

*These settings are for specific advance use-cases and not required for the tutorial. We recommend loading ready-made json configuration files as starting point.*

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FzD19XqFfZIeZcKwneea1%2FYuDash_Modbus_Server.jpg?alt=media&amp;token=00205e12-2758-43e4-8f54-a2ab5d8a7ace" alt=""><figcaption></figcaption></figure>

## 6) Modbus poll read

Reboot ZENYX after completing all settings. The input analog values should be available on modbus-poll on the laptop. Following are typical settings to match the Modbus server

1\) The Connection Setup is matched to 9600, 8N1

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FEtnSv6NE89yiX8Xo9nGF%2F22.jpg?alt=media&amp;token=c1ebc98d-8c36-4fa4-97a2-97f2f880b11e" alt=""><figcaption></figcaption></figure>

2\) The Slave ID is 1 and function is 0x3 (Read Holding Registers)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FwXWKgnJjUXd2pD2LWZmU%2F23.jpg?alt=media&amp;token=1b591433-6511-4537-bcac-35bd748d34fe" alt=""><figcaption></figcaption></figure>

3\) The Display data type is "32 bit Float" with Little-endian byte swap

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fv3X8lu301TQjsarZdkMV%2F24.jpg?alt=media&amp;token=2b7cf615-871f-4e48-88cb-866d2ae84eab" alt=""><figcaption></figcaption></figure>

### **YuDash Modbus Server specifications**

1. The output registers are mapped in holding registers (starting from 40000).
2. The data type is fixed floating type (Var Type = 2).&#x20;
3. The entries in the register map should be in increasing order only.
4. Maximum of 16 variables  (32 registers) can be mapped to modbus register map.
5. The data scaling on input variables can be applied to receive process data on the modbus registers.&#x20;

## 7) YuDash ZENYX as Analog to Modbus TCP/IP Server

Similar to above tutorial, YuDash ZENYX can be configured as Modbus TCP/IP Server. Following is typical wire connection:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYHKAQWIHhQwegwiSbPdu%2F25.jpg?alt=media&amp;token=8c5897b6-bc2b-4cdb-804f-294b7fbbd27f" alt=""><figcaption></figcaption></figure>

####

#### 7.1) Ethernet LAN is enabled to use LAN port for Modbus TCP/IP server

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6gUpLvl4A5dYciCTboZ5%2F26.jpg?alt=media&amp;token=e309cfdb-a2c2-4fea-ac89-392fbe0fa890" alt=""><figcaption></figcaption></figure>

#### 7.2) Ethernet of YuDash ZENYX is configured as static IP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYEmkOOWduoFzNxNbwx0r%2F27.jpg?alt=media&amp;token=421feefc-df08-4c53-a788-e93018f156af" alt=""><figcaption></figcaption></figure>

The IP address is assigned as static. Sample IP address of 192.168.2.73 is assigned. This IP address will be readby Modbus poll software.

#### 7.3)  Modbus Server Settings.

* In Modbus Server Type Settings, "TCP/IP" is selected
* The Modbus TCP/IP port of 502 is assigned. The IP address was assigned in 7.2 earlier.&#x20;
* The block of "Modbus RS485 Server Settings" is ignored.
* &#x20;Modbus Server ID remains 1 for Modbus TCP/IP.&#x20;
* Only server ID of 1 is supported in Modbus TCP/IP. The uniqueness is managed by port number.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fanm3AmGatoj9x2kkMF18%2F28.jpg?alt=media&amp;token=d80705fe-d583-4663-83bf-66cc2940967e" alt=""><figcaption></figcaption></figure>

## 8) Analog to Modbus TCP/IP Server Json file

{% file src="/files/B5sgQma8EDBNwGBwtqJp" %}


# Analog to Modbus/TCP-IP Server

In this tutorial, YuDash LYNX will be used to read 8 channel analog inputs (4-20mA) and act as Modbus TCP-IP server&#x20;

{% hint style="info" %}
Ready-to-use json configuration files are available for ZENYX and LYNX in the end of the tutoral. They can simply be loaded into the device for quick start.
{% endhint %}

## 1) Connection Diagram

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FL9WJT4NzPNLItu7gcqh3%2F30.jpg?alt=media&amp;token=7efb2212-6f41-4f85-99ea-9e29a36a5261" alt=""><figcaption></figcaption></figure>

1. Test setup of 4 channel 4-20mA analog generator is connected (red line) to analog inputs of LYNX. The value of 5, 10, 15 and 20 mA are being generated in the test setup. LYNX will read 8 analog channels. So, balance 4 channels will have zero values.
2. The LAN cable is connected from ethernet port of LYNX to laptop. Modbus/TCP-IP server is configured on the ethernet LAN port.
3. The Modbus Poll software is acting as modbus TCP-IP client on the laptop. It is reading LYNX Modbus/TCP-IP and receiving 8 analog values on given modbus registers.

{% hint style="info" %}
Modbus Poll [download link](https://www.modbustools.com/download.html)
{% endhint %}

## 2) General Settings in LYNXsettings

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F40wchcIInXiIi8RaYgek%2F32.jpg?alt=media&amp;token=ca6d8508-10f4-45c5-a987-e2a53487ba6e" alt=""><figcaption></figcaption></figure>

* **Loop Delay** is set to 0.  As we act as server, we want to read input data continuously without any delay.
* **Analog Inputs** is enabled to read 4-20mA input.
* The Cloud/Network set to to "**Offline**". In this usage, we are not sending data to any server.&#x20;
* Ethernet/LAN is enabled

{% hint style="info" %}
Notes in general settings:

1\) Modbus/RS485 is NOT enabled here (which makes YuDash as Modbus master). We will be enabling Modbus/RS485 server in the next step

2\) The datascale feature of YuDash can be used to scale the analog input to required process values. This is not covered in this tutorial for simplicity.
{% endhint %}

## 3) Analog Input Settings in LYNX

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FXwcIy17blJSTpIpVssdj%2F19.jpg?alt=media&amp;token=6e0062dd-597b-43bf-ab17-87eca4d4b338" alt=""><figcaption></figcaption></figure>

* **Analog Input Settings:** All 8 analog inputs are enabled. We read 0-20mA inputs.
* The eight variables read are **analog1 to analog8** respectively. These variables will be mapped to Modbus/ TCP-IP server register in next section.&#x20;

## 4) Ethernet LAN Settings

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYEmkOOWduoFzNxNbwx0r%2F27.jpg?alt=media&amp;token=421feefc-df08-4c53-a788-e93018f156af" alt=""><figcaption></figcaption></figure>

&#x20;&#x20;

* Ethernet Settings are used to assign a static IP address to the LYNX
* Static IP of 192.168.2.73 is assigned in this tutorial. This can be changed as per network topology.&#x20;
* This IP address will be used to read LYNX Modbus TCP-IP server in the Mobus poll.

## 5) Modbus Server Settings

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FabSHEj4QowCdMmeS0uyH%2F34.jpg?alt=media&amp;token=a06c2cb5-c438-431b-9734-6cf3791a1130" alt=""><figcaption></figcaption></figure>

* **Modbus Server Type:** This is selected as TCP/IP. This pertains to TCP/IP (LAN port) acting as Modbus Server.
* **Modbus TCP-IP  Server Settings:**
  * Modbus TCP/IP port: The TCP/IP port used to run the server. It is set to 502 in the example.
  * The section of "Modbus RS485 Server Settings" is not applicable.&#x20;
  * Only Server Id of 1 is applicable for Modbus TCP-IP.&#x20;
* **Modbus Server Register Settings block**
  * You need to click "Open Modbus Server Settings" to open the details.
  * Click on "Read Modbus Server Settings" to check existing mappings.
  * Click on "Update Modbus Server Settings" after any changes.
* **Modbus Server Register Settings**
  * Input variables "analog1" is mapped to 40000 register as floating point output.&#x20;
  * The "Var Type" is set to 2 (floating point data type). This is the only supported data type at present. So, 2 modbus registers are used for one variable.
  * The "Enable Modbus Register" checkbox enables the value. This entry is ignored/delete if the check box is not present.&#x20;
  * In the tutorial, the eight analog inputs variables (analog1 to analog8) are mapped to registers 40000 40002 40004, upto 40014.&#x20;

## 6) Tutorial Json configuration file

Above 5 steps complete the configuration in the LYNX. These settings are readily available in the following json file. We recommend loading below json file to run through the tutorial.

{% file src="/files/LE6S6OMDJUOZLIgRCwbJ" %}

In case RTC and timeSync is enabled in the advance settings, loopDelay=0 will be ignored. In this case TimeSync Server Mode sould be enabled for fast response.&#x20;

*These settings are for specific advance use-cases and not required for the tutorial. We recommend loading ready-made json configuration files as starting point.*

## 7) Modbus poll read

Reboot LYNX after completing all settings. The input analog values should be available on modbus-poll on the laptop. Following are typical settings to match the Modbus server

1\) The Connection Setup is selected as Modbus TCP/IP and IP address of 192.168.2.73 is selected. Server port of 502 is selected.&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FiquZtPsIrUSk4PnKtX8q%2F35.jpg?alt=media&amp;token=fd2b1923-f263-487c-b603-2340e0d4fb12" alt=""><figcaption></figcaption></figure>

2\) The "Display" is selected as 32-bit Float with Little-endian byte swap

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FBWFHZx9iTmiIPPvtgyLC%2F36.jpg?alt=media&amp;token=a2a76f6b-1ca9-4bde-a6e4-e506d1f14893" alt=""><figcaption></figcaption></figure>

3\) All 8 variables (16 registers) are visible in Modbus poll. First 4 registers have analog values from the test setup. Rest 4 analog inputs have zero values as they are not connected.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F8u7MPrJMqX8hVNc9ykm9%2F37.jpg?alt=media&amp;token=83c42e4e-2984-464c-9400-b5cf2c4cdf93" alt=""><figcaption></figcaption></figure>

### **YuDash Modbus Server specifications**

1. The output registers are mapped in holding registers (starting from 40000).
2. The data type is fixed floating type (Var Type = 2).&#x20;
3. The entries in the register map should be in increasing order only.
4. Maximum of 16 variables  (32 registers) can be mapped to modbus register map.
5. The data scaling on input variables can be applied to receive process data on the modbus registers.&#x20;

## 8) YuDash ZENYX as Analog to Modbus TCP/IP Server

Similar to above tutorial, YuDash LYNX can be configured as Modbus TCP/IP Server. Following is typical wire connection:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYHKAQWIHhQwegwiSbPdu%2F25.jpg?alt=media&amp;token=8c5897b6-bc2b-4cdb-804f-294b7fbbd27f" alt=""><figcaption></figcaption></figure>

####

#### 7.1) Ethernet LAN is enabled to use LAN port for Modbus TCP/IP server

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6gUpLvl4A5dYciCTboZ5%2F26.jpg?alt=media&amp;token=e309cfdb-a2c2-4fea-ac89-392fbe0fa890" alt=""><figcaption></figcaption></figure>

#### 7.2) Ethernet of YuDash ZENYX is configured as static IP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FYEmkOOWduoFzNxNbwx0r%2F27.jpg?alt=media&amp;token=421feefc-df08-4c53-a788-e93018f156af" alt=""><figcaption></figcaption></figure>

The IP address is assigned as static. Sample IP address of 192.168.2.73 is assigned. This IP address will be readby Modbus poll software.

#### 7.3)  Modbus Server Settings.

* In Modbus Server Type Settings, "TCP/IP" is selected
* The Modbus TCP/IP port of 502 is assigned. The IP address was assigned in 7.2 earlier.&#x20;
* The block of "Modbus RS485 Server Settings" is ignored.
* &#x20;Modbus Server ID remains 1 for Modbus TCP/IP.&#x20;
* Only server ID of 1 is supported in Modbus TCP/IP. The uniqueness is managed by port number.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fanm3AmGatoj9x2kkMF18%2F28.jpg?alt=media&amp;token=d80705fe-d583-4663-83bf-66cc2940967e" alt=""><figcaption></figcaption></figure>

## 8) Analog to Modbus TCP/IP Server Json file


# Modbus Topology

Modbus for connecting IoT Gateways with instruments

Modbus is one of the most popular serial protocol for industrial systems. It is used for data exchange between sensors, instruments, PLC, HMI and parts of SCADA system. Please refer to [Wikipedia](https://en.wikipedia.org/wiki/Modbus) and [official standard](https://modbus.org/docs/Modbus_Application_Protocol_V1_1b.pdf) for technical details.

With advent of IIoT, IoT gateways communicate with various components over Modbus. This documents various topologies of Modbus based systems.

## Modbus Communication Concept

Modbus works on the concept of **Master** and **Slave.** The master sends a **request** to slave and slave **reply** with required information.

{% hint style="info" %}
These words have been [officially](https://modbus.org/docs/Client-ServerPR-07-2020-final.docx.pdf) replaced to **Client** *(Master)* and **Server** *(Slave).* Unfortunately, Master/Slave words still remain popular in industry (at least for Modbus/RS485). In Modbus TCP/IP, Client-Server is more prevalent. For ease of understanding, we use unofficial words in this tutorial.
{% endhint %}

## Modbus Versions

Following are two popular version of Modbus which are supported by YuDash IoT devices.

#### 1) Modbus/RS485 (or Modbus/RTU)

* Refer to [Modbus Settings in LYNX User Manual](/yudash-iot-products/lynx/lynx-settings/modbus-rs485).&#x20;
* Integration with RS/485 devices in [Industrial Equipment Integration Guide](/ig/in).
* [Modbus RS485](/pf/si/modbus) in YuDash Device Features
* [Modbus Poll Tutorial](/pf/si/modbus/modbus-poll-tutorial) in YuDash Device Features

#### 2) Modbus/TCP-IP

* Refer to [Modbus TCP/IP](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip) in LYNX User Manual

With assumption of basic Modbus understanding, we explain integration of YuDash IoT devices with Modbus instruments, PLCs and HMIs.

## Integration of IoT Gateway in various Modbus topologies

### 1) Integration of IoT Gateway with PLC based systems

#### 1) Typical PLC application with Modbus/RS485 communication

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fw1XyphWB4uCAzykW2jLn%2F3.jpg?alt=media&amp;token=b60ea77a-523c-4246-a566-a4b297295c35" alt=""><figcaption></figcaption></figure>

#### 1A) PLC system with IoT Gateway using Modbus/RS485

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F6MURJgvTNoqHIjfC5O8j%2F4.jpg?alt=media&amp;token=634a567f-8339-4352-98d3-ef8b1bede2c5" alt=""><figcaption></figcaption></figure>

#### 1B) PLC system with IoT Gateway using Modbus TCP/IP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FOcJddaHvOoZuo0F2ma36%2F8.jpg?alt=media&amp;token=81d5154f-ee70-48d3-a6df-fc9725d4e1e3" alt=""><figcaption></figcaption></figure>

### 2) Integration of IoT Gateway with PLC+HMI based systems

#### 2) Typical PLC+HMI based system

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FhsmK7sBRl9g5iMSILuUW%2F5.jpg?alt=media&amp;token=a3e0c267-6780-483c-9f73-d45b6cd96aef" alt=""><figcaption></figcaption></figure>

#### 2A) PLC+HMI with IoT Gateway using Modbus/RS485

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FoHYb2nlQ4r9755951Gmu%2F6.jpg?alt=media&amp;token=609e5bf1-ad74-4a78-bbc9-38d09af12026" alt=""><figcaption></figcaption></figure>

#### 2B) PLC+HMI with IoT Gateway using Modbus TCP/IP

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FOg7fbR7z0NcRErLbtH9i%2F9.jpg?alt=media&amp;token=826023bc-c668-478b-801e-379f13761732" alt=""><figcaption></figcaption></figure>

### 3) IoT Gateway with RS485 enabled instruments

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FF85EPOWMwSAKgaDezLDj%2F11.jpg?alt=media&amp;token=07edfc77-69d7-4b10-bfd3-3b4a68becb11" alt=""><figcaption></figcaption></figure>

All Modbus topologies are captured in below tutorial

{% file src="/files/IUA5SxqUPeJDKcCLyzM5" %}

## Requirements in PLC system for IoT compatible

It is important that PLC based system for Industrial Machines/Assets are designed to be IoT compatible. It is imperative that all machines will be IoT enabled (Industry 4.0) now or later in future. Following are key requirements during system design to make IoT ready (using Modbus):&#x20;

1. Identify existing topology of PLC/HMI system from [above](#integration-of-iot-gateway-in-various-modbus-topologies) list and select one of integration option for IoT Gateway.
2. One channel of Modbus RS485 or Modbus TCP/IP (Ethernet) has to be made available for IoT gateway. IoT Gateway will be Modbus Master (Client) which will request data from the existing system.
3. The select Modbus channel has to be configured as Slave (Server) and communication settings should be well documented.&#x20;
4. Following is required information for **Modbus RS485**:

<table><thead><tr><th width="281">RS485 Parameter</th><th>Sample/Description</th></tr></thead><tbody><tr><td>Baudrate</td><td>9600, 19200 etc</td></tr><tr><td>Data Bits, Parity &#x26; Stop Bit</td><td>8N1, 8E1 etc.</td></tr><tr><td>Slave ID for Modbus slave</td><td>1, 2 etc.</td></tr><tr><td>Modbus RS485 terminals</td><td><p>The RS485 terminals should be well defined (preferably take a photograph with A and B marked). </p><p>In case of DB9/RJ25/RJ45  jack, clearly identify the pins. It is advisable to provide a two wire connector on the jack.</p></td></tr><tr><td></td><td></td></tr></tbody></table>

> It is advisable that provided communication settings should be verified by PC based Modscan software. Please document snapshots of Modscan, similar to this [example](/yudash-iot-products/lynx/lynx-settings/modbus-rs485). &#x20;

5. Following is required information for **Modbus TCP/IP**

| Modbus TCP/IP Paramter                | Sample/Description                                                               |
| ------------------------------------- | -------------------------------------------------------------------------------- |
| IP address                            | 192.168.100, 10.0.0.1 etc.                                                       |
| IP port                               | The port number on which Modbus Server is running. For example: 503, 888         |
| Server ID Modbus Server               | 1, 2, etc.                                                                       |
| RJ 45 jack for connecting IoT gateway | Well defined RJ45 jack to connect IoT Gateway. It can be in PLC/HMI or a switch. |

6. Identify critical parameters from the system to be provided to the IoT Gateway. These can be real-time process values, thresholds, batch numbers or alarm values.&#x20;
7. List down the parameter names, Modbus register numbers, data types in tabular form.&#x20;
   1. The register should be complete 5 digits or define the register type (Input, Holding etc).
   2. If data type is Floating point, please define LSB/MSB type.
8. Sample Table of Modbus Registers&#x20;

| Parameter   | Modbus Register | Data Type            |
| ----------- | --------------- | -------------------- |
| Voltage     | 40000           | Signed Integer       |
| Temperature | 30050           | Floating point (LSB) |
| Alarm1      | 10000           | Binary               |

### Technical References for YuDash IoT Gateways

1. [Modbus RS485 Settings in YuDash LYNX](/yudash-iot-products/lynx/lynx-settings/modbus-rs485)
2. [Modbus TCP/IP Settings in YuDash LYNX](/yudash-iot-products/lynx/lynx-settings/modbus-tcp-ip)
3. [Instrument Integration Guides with YuDash LYNX](/ig/in)

&#x20;


# Integrations


# Sensors


# Rain Gauge

Tipping bucket rain gauges typically use a magnet-operated reed switch to generate a pulse whenever the bucket tips. The reed switch is normally open and closes momentarily for each tip.

FELYX uses **DI1 as the Rain Pulse Counter input**. Connect the two reed-switch output wires to **DI1 and GND**. Rainfall is calculated from the number of pulses and the configured rain-per-tip value.

### Integration note

* Wire colors and terminal assignments may vary by manufacturer and model. Always refer to the OEM manual for the exact wiring reference before installation.
* Detailed pulse-input configuration and rainfall scaling settings are covered in the FELYX Sensor Integration / Pulse Input configuration section.

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FV8eesnZ8lDe47ZuXpa1S%2Frainfall_concept.png?alt=media&amp;token=1cf0d7d2-eb35-4da3-b65e-abf9fddb2e21" alt=""><figcaption></figcaption></figure>

### Sensor Integration Examples

The following examples show tipping bucket rain gauges that have been integrated with YuDash FELYX. Wiring colours, connector pinouts and rainfall resolution vary between manufacturers; always verify the corresponding OEM documentation before installation.

### RainWise Tipping Bucket

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FNYEpGOGU0CUxCAZ7KPmQ%2Frain_rainwise.png?alt=media&amp;token=0ba16c8d-4128-4dc6-8fdb-99f00193f1e4" alt=""><figcaption></figcaption></figure>

### Xylem Waterlog H-3401-02

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQr7xtXf7qywdYDX17XeG%2Frain_waterlog.png?alt=media&amp;token=673ece18-3f3b-450b-96d9-1b93aab58955" alt=""><figcaption></figcaption></figure>

### Davis Instruments 6464&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRNgbHvayVOs7HlqQGwCV%2Frain_davis.png?alt=media&amp;token=9565b6f8-e142-4b6c-bae2-45606e69e551" alt=""><figcaption></figcaption></figure>


# Solar Radiation

Solar radiation sensors measure the energy received from the sun and are widely used in weather and hydromet stations, agriculture, ecological research, evapotranspiration studies, solar-energy monitoring, and surface energy-balance studies. Depending on the sensor type, measurements may include global shortwave radiation, net radiation, reflected radiation, PAR/ePAR, or spectral irradiance.

Radiation sensors are commonly available with **Modbus/RS485, SDI-12, 4–20 mA, or voltage outputs such as 0–5 V**, depending on the sensor model. FELYX can interface directly with these supported digital and analog outputs. Apogee, for example, offers pyranometer variants with 4–20 mA, 0–5 V, SDI-12 and Modbus outputs.

### Apogee SN-522-SS Net Radiometer

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F1kAakgUzQ5f3biultaQa%2Fapogee_sn522.jpg?alt=media&amp;token=66d34f92-d287-464c-b860-7c443eefdb58" alt=""><figcaption></figcaption></figure>


# Soil Sensors

**Soil sensors** are used for continuous measurement of soil water and related parameters in hydrology, agriculture, irrigation, watershed studies and environmental research. Depending on the sensor, measurements may include **volumetric water content (VWC), soil temperature, electrical conductivity and permittivity**.

FELYX supports digital soil sensors using interfaces such as **SDI-12 and RS485/Modbus**, allowing multiple measurement parameters to be acquired, logged and transmitted from remote field installations.

### Acclima TDR Soil Moisture Sensors

[Acclima TDS Sensor Manual](https://acclima.com/wp-content/uploads/Acclima-TDR-Sensor-User-Manual-REV-9-30-21.pdf)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDf39mv13QZciizkQ8P39%2Facclima_tdr_sensors.jpg?alt=media&amp;token=0e984d8a-6e7f-4d40-96b1-0ff5bd47bedc" alt=""><figcaption></figcaption></figure>


# Plant Science

Plant Science sensors are used to study plant growth, physiology and the interaction between plants and their surrounding environment. Typical measurements include **plant microclimate, PAR/light conditions, CO₂, temperature and humidity, NDVI/vegetation response, sap flow, oxygen and other plant-related parameters**.

These measurements are widely used in **crop and greenhouse research, controlled-environment agriculture, plant physiology studies, irrigation research, ecological monitoring and experimental field stations**.

FELYX can integrate with plant science instruments using interfaces such as **RS485/Modbus, SDI-12 and supported analog inputs**, depending on the sensor model. Sensor data can then be logged locally, processed at the edge and transmitted to remote servers or IoT platforms as required.

### Apogee SM-500 Guardian CEA Multi-Sensor Monitor

[SM-500 Documentation PDF](https://www.apogeeinstruments.com/content/SM-500-600-manual.pdf)

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F78q8lNfM2W2nieoHJXgN%2Fapogee_sm_500.jpg?alt=media&amp;token=a836cd72-bc3d-4191-a1c0-981d5db95f93" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FggKV99kkVSpy9pruEOOU%2Fapogee_sm500_deploy.jpg?alt=media&amp;token=57c9e26e-f9a8-4c73-93df-55d6a3556c24" alt=""><figcaption></figcaption></figure>

##

## Quantum Sensors

### Apogee SQ-522 Quantum Sensor

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FAP03U4tmtRW3Nsqig7Dy%2Fapogee_sq522.jpg?alt=media&amp;token=6d5f9578-e5ae-4f6e-b690-2a003ea3aeee" alt=""><figcaption></figcaption></figure>

[Apogee SQ-522 Documentation](https://www.apogeeinstruments.com/content/SQ-522-manual.pdf)

### Apogee SQ-618 ePAR Sensor

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F5PcDeT061CP1NaI1KTVH%2Fapogee_sq618.jpg?alt=media&amp;token=e28e914f-7efa-42b1-87d5-b13a6b8f298a" alt=""><figcaption></figcaption></figure>

[Apogee SQ-618 Documentation](https://www.apogeeinstruments.com/content/SQ-522-manual.pdf)


# Integrated Weather

Integrated weather instruments combine multiple environmental measurements in a single compact sensor assembly. Depending on the instrument, these may include parameters such as **wind speed and direction, air temperature, relative humidity, atmospheric pressure, rainfall, solar radiation, and other weather-related measurements**.

These instruments typically communicate digitally using **Modbus RTU over RS485**, or through **ASCII / proprietary serial protocols over RS485 or RS232**.

FELYX supports both standard Modbus integration and custom serial communication. For instruments using proprietary ASCII or text-based protocols, the flexible **YuParse engine** can be used to parse the incoming data and map the required parameters to FELYX variables for logging, processing and telemetry.

### Sensor Integration Examples

### RainWise Tipping Bucket

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FNYEpGOGU0CUxCAZ7KPmQ%2Frain_rainwise.png?alt=media&amp;token=0ba16c8d-4128-4dc6-8fdb-99f00193f1e4" alt=""><figcaption></figcaption></figure>

### Xylem Waterlog H-3401-02

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQr7xtXf7qywdYDX17XeG%2Frain_waterlog.png?alt=media&amp;token=673ece18-3f3b-450b-96d9-1b93aab58955" alt=""><figcaption></figcaption></figure>

### Davis Instruments 6464&#x20;

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRNgbHvayVOs7HlqQGwCV%2Frain_davis.png?alt=media&amp;token=9565b6f8-e142-4b6c-bae2-45606e69e551" alt=""><figcaption></figcaption></figure>


# Industrial Instruments

This section covers integration of YuDash IoT devices with various industrial instruments. These guides refer to practical deployment of the following part of YuDash IIoT Stack:

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FmKzYZngjQD29vJttwNeM%2Fyudash_iiot_field.jpg?alt=media&amp;token=abfdfe94-dece-4f87-8472-c9873871fd6d" alt=""><figcaption></figcaption></figure>

The integration guides are categorized by application types as below &#x20;

{% tabs %}
{% tab title="Energy Meters" %}
[Schneider Electric EM6400NG+](/ig/in/energy/se-em6400ng+)

[Selec MFM376](/ig/in/energy/selec-mfm376)
{% endtab %}

{% tab title="Process Control" %}

{% endtab %}
{% endtabs %}

{% hint style="info" %}
RS485/Modbus is a popular industrial protocol to enable communication between YuDash IoT Gateway and Industrial Instrument (eg. Energy meter).  YuDash IoT Gateway is **Modbus Master** and instrument is **Modbus Slave.**&#x20;
{% endhint %}


# Energy


# SE EM6400NG+

&#x20;Schneider Electric EM6400NG+ is one of the most advanced and popular MFM in market.

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>3 Phase Energy Meter</td></tr><tr><td>Model Number</td><td><a href="https://www.se.com/in/en/product-range/63369-em6400ng+/">Schneider Electric EM6400 NG+</a></td></tr><tr><td>Brand</td><td>Schneider Electric</td></tr><tr><td>Reference</td><td><a href="https://download.schneider-electric.com/files?p_Doc_Ref=NHA2768503+-+00&#x26;p_enDocType=User+guide&#x26;p_File_Name=NHA2768503-07_EN.pdf">Datasheet PDF</a></td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus Settings</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>19200 8E1</td></tr><tr><td>Typical Data Type</td><td><strong>Float MSB  * (varType=21 in YuDash)</strong></td></tr></tbody></table>

{% hint style="info" %}
Schneider Electric has a vast range of energy meters. Please double check availability of RS485 and mapping for specific model in use.&#x20;

In many cases, the Modbus mapping is not part of the manual and is available as separate xls sheet. The file **Public\_EM6400\_PM2xxx PM RegisterList\_v1050\_6.xls** is referred to in this documentation&#x20;
{% endhint %}

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FXj5PupBU4TOyBvhyN2J0%2Fem6400ng%2B_pg3.jpg?alt=media&amp;token=54ab057b-4fad-4f21-8457-62c22827fd9a" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDobYfJagC5jqV803weQg%2Fem6400ng%2B_pg2.jpg?alt=media&amp;token=2827f76c-02d0-4dfb-bbf9-d0619e2975dc" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FH25i7UqR9w31xWF550LR%2Fem6400ng%2B_pg1.jpg?alt=media&amp;token=b858a810-5399-43e6-9084-5f4fb213b9db" alt=""><figcaption></figcaption></figure>


# Selec MFM376

<table><thead><tr><th width="327">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>3 Phase Multifunction meter</td></tr><tr><td>Model Number</td><td><a href="https://www.selec.com/product-details/multifunction-meter-376">Selec MFM376-C-CE </a></td></tr><tr><td>Brand</td><td>Selec</td></tr><tr><td>Category</td><td>Energy Meters</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus/RS485 Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1</td></tr><tr><td>Typical Data Type</td><td>Float LSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FAqrh0N7twL9KaanfTbTE%2Fmfm376_p1.jpg?alt=media&amp;token=2a73ba11-538c-4e3c-a45f-c578e4052b2e" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FdhEeU8YCp0xyKDBUWbLV%2Fmfm376_p2.jpg?alt=media&amp;token=a0ae48ee-5d67-45d1-a0d8-8069f8240018" alt=""><figcaption></figcaption></figure>

## Instrument Read in Modscan Software

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F4AoiunX8JuJfRIftbgX4%2Fmfm376_p3.jpg?alt=media&amp;token=fb4d2182-17a9-4cea-89dd-621a9052da81" alt=""><figcaption></figcaption></figure>


# L\&T WL 4040

<table><thead><tr><th width="327">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>Dual Source Energy meter</td></tr><tr><td>Model Number</td><td><a href="https://www.lntebg.com/ems/pdf/4.%20WL-WC%204040%20Dual%20Source%20meter.pdf">WL-4040</a></td></tr><tr><td>Brand</td><td>Larsen and Toubro</td></tr><tr><td>Category</td><td>Energy Meters</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus/RS485 Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1</td></tr><tr><td>Typical Data Type</td><td>Float LSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FkcCLLoWeuWTSrXCKYSyz%2F34.jpg?alt=media&amp;token=b15e2c06-4fe8-4b19-b0da-c7ba3b1822c2" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FuYlx0UxUiZk4j6qbNMDn%2F35.jpg?alt=media&amp;token=975981cb-410c-47b9-b571-7850342597c3" alt=""><figcaption></figcaption></figure>

## Instrument Read in Modscan Software

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FovUPAyedLaMxu5PJ6lxQ%2F36.jpg?alt=media&amp;token=0b246187-fc63-403f-89be-2d155f4de329" alt=""><figcaption></figcaption></figure>


# Entes MPR-46S

<table><thead><tr><th width="327">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>Network Analyzer / Multifunction meter</td></tr><tr><td>Model Number</td><td><a href="https://www.entes.eu/mpr-46s/">MPR-46S</a></td></tr><tr><td>Brand</td><td><a href="https://www.entes.eu/">Entes</a></td></tr><tr><td>Category</td><td>Energy Meters / Network Analyzer</td></tr><tr><td>Protocol</td><td>RS485/Modbus   <a href="https://www.entes.com.tr/uploads/files/MPR-3_4_Series_Register_Table.pdf">Modbus Mapping Table</a></td></tr><tr><td><strong>Modbus/RS485 Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>115200 8N1 (changed to 9600 in example)</td></tr><tr><td>Typical Data Type</td><td>32bit Integer MSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FEV5yL5rXYEAgwZNrWG9J%2F41.jpg?alt=media&amp;token=ba7cd972-becd-45de-a5be-2265ab86a9b2" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FfK9lwYHc88VJmJbMuCxy%2F42.jpg?alt=media&amp;token=ee8d3004-f241-4476-a4bb-b35c2395c1fc" alt=""><figcaption></figcaption></figure>

## Instrument Read in Modscan Software

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F3JoabGtGJGALtQjMHOPp%2F43.jpg?alt=media&amp;token=d07b716c-bbc0-4340-b315-68a98600a468" alt=""><figcaption></figcaption></figure>


# Selec EM4M

<table><thead><tr><th width="327">Parameter</th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>3 Phase Energy Meter</td></tr><tr><td>Model Number</td><td><a href="https://www.selec.com/product-details/energy-meter-direct-operated-em4m">EM4M</a></td></tr><tr><td>Brand</td><td>Selec</td></tr><tr><td>Category</td><td>3 Phase Energy Meters</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus/RS485 Settings</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1</td></tr><tr><td>Typical Data Type</td><td>Float LSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FGI50x4SITCDq9UApxAIE%2Fem4m_p1.jpg?alt=media&amp;token=921d018e-3e47-4431-8fec-2ff7d85a21ba" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2sZCUZwW15ZLFyzWrBgd%2Fem4m_p2.jpg?alt=media&amp;token=fae1b5e6-72c7-42e8-a8ee-21bdb934693c" alt=""><figcaption></figcaption></figure>

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FIfHMJRCGMwo8YxyZdzZE%2Flynx_em4m_deployment.jpg?alt=media&amp;token=48e6e380-bafd-4817-9616-8acfe7bd5f4c" alt=""><figcaption></figcaption></figure>


# Secure Elite 100

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>3 Phase Energy Meter</td></tr><tr><td>Model Number</td><td><a href="https://www.securemeters.com/in/product/multi-function-panel-meters/elite-100-and-300/">Secure Elite 100</a></td></tr><tr><td>Brand</td><td>Secure</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus/RS485 Settings</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1</td></tr><tr><td>Typical Data Type</td><td>Float LSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FnKznnARKCySxs1BzTm1A%2Fsecure_elite_pg1.jpg?alt=media&amp;token=7e58097c-b031-4678-b8e7-f0af0f4341e6" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FyDqAWNsVFm7fHSnkJWbJ%2Fsecure_elite_pg2.jpg?alt=media&amp;token=6b352382-8682-4420-a873-cadbec07df5b" alt=""><figcaption></figcaption></figure>


# Siemens Smart 7KT

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>3 Phase Energy Meter</td></tr><tr><td>Model Number</td><td><a href="https://assets.new.siemens.com/siemens/assets/api/uuid:add7ae8b-ea57-44ea-90e3-d174f4d69540/smart7ktcatalog2019.pdf">Siemens Smart 7KT</a></td></tr><tr><td>Brand</td><td>Siemens</td></tr><tr><td>Protocol</td><td>RS485/Modbus</td></tr><tr><td><strong>RS485/Modbus Settings</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1</td></tr><tr><td>Typical Data Type</td><td>Float LSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FDNUbuGGZU3DnNNDdk3cq%2Fsiemens_7kt_pg1.jpg?alt=media&amp;token=c20d32d0-821c-4b5c-aeb1-e3179a1d3bf4" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fq76NaMTdI44VwLofThXH%2Fsiemens_7kt_pg2.jpg?alt=media&amp;token=863cb0b3-67f7-419d-bdfc-0a30d3503088" alt=""><figcaption></figcaption></figure>


# Selec EM2M

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>1 Phase Energy Meter</td></tr><tr><td>Model Number</td><td><a href="https://www.selec.com/product-details/multifunction-meter-376">Selec </a><a href="https://www.selec.com/product-details/energy-meter-direct-operated-em2m">EM2M</a></td></tr><tr><td>Brand</td><td>Selec</td></tr><tr><td>Category</td><td>1 Phase Energy Meter</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus/RS485 Settings</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1</td></tr><tr><td>Typical Data Type</td><td>Float LSB</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FzxzVVOruhWeTcyRuMZv7%2Fem2m_p1.jpg?alt=media&amp;token=a4e50bcb-78c8-48c3-b9d5-116041482642" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FRgv3QWqwF1DHPDtFhwoW%2Fem2m_p2.jpg?alt=media&amp;token=4899b994-dd95-46a0-895e-d34a93c8c348" alt=""><figcaption></figcaption></figure>

## Instrument Read in Modscan Software

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FWhLApzoB46basGWXaVKL%2Fem2m_p3.jpg?alt=media&amp;token=6367e8ac-7da4-4db4-addb-89c6fa1c6feb" alt=""><figcaption></figcaption></figure>


# Process Control

This section covers Instruments pertaining to process control for industrial and environment applications.


# Selec FLEX2MV3 6AII

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>6 Channel Analog (0-20mA) to Modbus Converter</td></tr><tr><td>Model Number</td><td><a href="https://www.selec.com/product-details/expansion-slot-flexys-series">Selec FLEX 2M</a> V3  with 6AII card</td></tr><tr><td>Brand</td><td>Selec</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>19200 8N2 (DIP switch configurable)</td></tr><tr><td>Slave</td><td>1 (DIP switch Configurable)</td></tr><tr><td>Data Type</td><td>Integer (0-1000 process value)</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2Fo8hFYsjPL1Y5qYPoZyH5%2Fselec_flex2mv3_6aii.jpg?alt=media&amp;token=c65a1e57-824a-4a97-b965-3a9b3cd3127e" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQV7rVGWaVZ8Kelg5FGM4%2Fselec_flex2mv3_6aii_p2.jpg?alt=media&amp;token=ce27be72-4728-44ea-92bc-3df15770026d" alt=""><figcaption></figcaption></figure>


# Selec MiBRX 2M PLC

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>Generic compact DIN rail PLC</td></tr><tr><td>Model Number</td><td><a href="https://www.selec.com/product-details/2m-sized-modular-plc-1">Selec MiBRX 2M PLC</a></td></tr><tr><td>Brand</td><td>Selec</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>19200 8N1</td></tr><tr><td>Slave</td><td>1 (Configurable in PLC)</td></tr><tr><td>Data Type</td><td>Configurable as per programming</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FQVNUKER0TDcLZOBSHFcO%2F38.jpg?alt=media&amp;token=79a8d386-06ae-48e3-b15f-8d51283909cf" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2F2ZqffYCvCZZod8viSzpz%2F39.jpg?alt=media&amp;token=9a85dc78-037b-4bd3-9d70-d4ad509697b5" alt=""><figcaption></figcaption></figure>


# Temp+Humidity XY-MD02

SHT20/SHT30 series of temperature and humidity sensors are widely used in process and environment monitoring. In this tutorial, we explain a popular instrument which has SHT20 sensor (or similar model) and provides Modbus/RS485 output.&#x20;

{% hint style="info" %}
YuDash IoT devices also support SHT sensors through I2C interface for direct reading of sensors without Modbus
{% endhint %}

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>Temperature and Humidity sensor</td></tr><tr><td>Model Number</td><td>XY-MD02</td></tr><tr><td>Brand</td><td>Generic / China</td></tr><tr><td>Protocol</td><td>RS485/Modbus </td></tr><tr><td><strong>Modbus Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>9600 8N1 (configurable by Modbus)</td></tr><tr><td>Slave</td><td>1 (default slave ID)</td></tr><tr><td>Data Type</td><td>Integer (10X or proces value)</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FzD9WTSDb4YU3NPMvpi3P%2F30.jpg?alt=media&amp;token=295d10d2-3ccb-41be-96d8-c68ab14246e4" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FvAVvRuaAkz6gDQ3dv6WO%2F31.jpg?alt=media&amp;token=871f927e-883f-417a-8e35-28a698e926f5" alt=""><figcaption></figcaption></figure>

## Modscan Settings for XY-MD02

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FsK2xl1C9sW0lpZtxwqh1%2F32.jpg?alt=media&amp;token=ed162f00-e51a-4c19-9abb-369cbf5a256c" alt=""><figcaption></figcaption></figure>


# PPI AIMS 4/8X

<table><thead><tr><th width="327"></th><th>Description</th></tr></thead><tbody><tr><td>Instrument Type</td><td>4/8 Channel Analog to Modbus Converter</td></tr><tr><td>Model Number</td><td><a href="https://ppiindia.net/product/aims-4-8x/">PPI AIMS 4/8X</a></td></tr><tr><td>Brand</td><td>PPI</td></tr><tr><td></td><td><a href="https://ppiindia.net/wp-content/uploads/2022/02/Product-063-UM.pdf">Technical Manual</a></td></tr><tr><td>Protocol</td><td>RS485/Modbus</td></tr><tr><td><strong>Modbus Setting</strong></td><td></td></tr><tr><td>Default Baud Rate </td><td>19200 8E1</td></tr></tbody></table>

## Communication Wiring

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FtyR8QEk6swcjD4l31UQR%2Fppi_pg1.jpg?alt=media&amp;token=a6b241f2-111b-4f6a-b4b3-8584172f0737" alt=""><figcaption></figcaption></figure>

## Modbus Configuration in YuDash

## YuDash LYNX with PPI Convertor

<figure><img src="https://1858257737-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FToww5EM1cml3ouN6fvnJ%2Fuploads%2FAIDFOLxuzzm7h32vNJ3z%2Fppi_lynx.jpg?alt=media&amp;token=98abe250-911c-4e56-84b8-3ed39c1e2e80" alt="" width="563"><figcaption></figcaption></figure>




---

[Next Page](https://docs.yudash.com/llms-full.txt/1)

