---
title: "Devices"
slug: "devices"
updated: 2025-06-15T20:57:59Z
published: 2025-06-15T20:57:59Z
canonical: "docs.bazefield.com/devices"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.bazefield.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Devices

![](https://cdn.document360.io/a0786c0f-b171-4b24-8860-c32eb7ef2738/Images/Documentation/image-1746725659686.png?sv=2026-02-06&spr=https&st=2026-11-06T20%3A31%3A12Z&se=2026-11-06T21%3A31%3A12Z&sr=c&sp=r&sig=Tq1wZaGXz8wXFxVyJBo0Nd4RC6pQyuDMnROUNYgodUY%3D)

*Devices are deployed on the Edge Buffer (or any other Node).*

## Overview

A **Bazefield Device** is a configurable DataEngine component that securely connects to data sources to retrieve real-time and/or historical data for renewable assets.

The term **Bazefield Device** is interchangeable with **SCADA interface**, **data integrator**, **adapter**, **connector**, or **protocol handler**.

The **DataEngine Service** includes native support for all available SCADA Device protocols—they do not require additional software installation.

> [!NOTE]
> Supported protocols include:
> 
> - OPC UA
> - DNP3
> - Modbus
> - ODBC
> - REST API
> - MQTT
> - IEC104
> 
> Bazefield also offers Devices that interface directly with major wind OEM databases, retrieving alarms using preconfigured queries—no manual query writing needed.

Each **Node** (physical or virtual) can host multiple Devices, allowing full plant data integration from a single machine. While there is no hard limit on the number of Devices per Node, system resources must be sized accordingly.

## Purpose

The purpose of Bazefield Devices is to:

- Maintain a reliable and secure connection to SCADA
- Integrate real-time and historical data for renewable assets
- Control assets via writes to SCADA
- Scale and aggregate raw data efficiently at the Edge

## Administration

**Device configuration is straightforward**: from the Bazefield Portal, an administrator selects a Node (e.g., Data Buffer or Storage Node) and adds a Device with the required settings. Assuming firewall rules are in place, the Device initiates a connection to the data source and begins collecting data for configured tags.