MILESGO
Richiedi un preventivo

Smart BuildingS04

AHU Smart Control

Il problema

Old AHU controllers cannot vary fan speed or fresh air by CO2, and replacing them with a proprietary controller locks the building into one vendor.

Panoramica della soluzione

MILESGO gateways collect data from air handling units (AHU), variable frequency drives (VFD), temperature and humidity sensors, CO2 sensors, valve actuators, differential pressure sensors over Modbus RTU / BACnet MS/TP, and deliver it to the BMS, WEB HMI panels as BACnet/IP / Modbus TCP / MQTT. Field equipment keeps its own protocol and control logic; integration is done by configuration and point mapping, not custom code.

Typical scope

  • air handling units (AHU)
  • variable frequency drives (VFD)
  • temperature and humidity sensors
  • CO2 sensors
  • valve actuators
  • differential pressure sensors

Protocol path

Modbus RTU / BACnet MS/TP → BACnet/IP / Modbus TCP / MQTT

Implementation checklist for the project manager

  • For hard-wired signals, list each DI/DO/AI/AO with its type (dry contact, 4–20 mA, 0–10 V, PT1000) and choose I/O modules accordingly.
  • Write the control sequence (start/stop order, interlocks, set-points, fallback on communication loss) and have it approved before programming.
  • Agree sensor positions (height, airflow, distance from doors and diffusers) so readings are representative.
  • Commission in read-only mode first; enable write / control points only after the client approves each one.
  • Build and simulate the configuration off site (FAT) before installation to shorten time on site.
  • Confirm DIN-rail space and a stable 12–24 V supply in each panel; use UPS-backed power for critical monitoring.
  • Hand over configuration backups, point table, IP plan and as-built drawings, with a short operator training.

Project deliverables

  • Signed point table and protocol mapping
  • Gateway configuration files and backups
  • IP address plan and network drawing
  • FAT and SAT test records
  • As-built documentation and operator training

Architettura del sistema

Field layer: air handling units (AHU), variable frequency drives (VFD), temperature and humidity sensors, CO2 sensors, valve actuators, differential pressure sensors, connected over Modbus RTU / BACnet MS/TP. Edge and integration layer: MILESGO protocol gateways and edge controllers, mounted on DIN rail in existing panels, polling each device, time-stamping values and buffering them locally. Upper layer: the BMS, WEB HMI panels, which receives the data as BACnet/IP / Modbus TCP / MQTT. Remote access for maintenance runs over VPN rather than open internet ports.

Composizione del sistema

Field devices
air handling units (AHU), variable frequency drives (VFD), temperature and humidity sensors, CO2 sensors, valve actuators, differential pressure sensors
Edge / integration
MILESGO protocol gateways and edge controllers
Upper systems
the BMS, WEB HMI panels (BACnet/IP / Modbus TCP / MQTT)
Tools and commissioning
Web-based configuration, point table import/export (Excel), off-site simulation and on-site diagnostic tools

Funzionalità software e IA

  • Anomaly detection on trend dataIn roadmap
  • Predictive maintenance indicators from equipment trendsIn roadmap

Fasi di realizzazione

  1. 1

    Site survey and point list

    Inventory devices, protocols, register maps, panel space, power and network paths.

  2. 2

    Design and point table sign-off

    Map every point to the target protocol and system; agree it with the client and the upper-system contractor.

  3. 3

    Configuration and FAT

    Build the gateway configuration off site, simulate it and test against the signed point table.

  4. 4

    Installation and wiring

    Mount gateways on DIN rail, wire RS-485 / I/O / Ethernet, apply the IP plan.

  5. 5

    SAT and alarm tests

    Verify values against local readings, test every alarm and command end to end.

  6. 6

    Handover and support

    Hand over configuration backups, point table and as-built documents; train operators.

Valore per il cliente

  • Open interfaces (BACnet, Modbus, OPC UA, MQTT, HTTP) avoid lock-in to one vendor
  • Consumption visible by area, system and time period
  • Reliable trend data for optimisation and fault diagnosis
  • New equipment integrated by configuration, not custom driver development

Altre soluzioni in Smart Building

Raccontaci il tuo progetto

Indica i protocolli, il numero di punti e il sistema di destinazione. Un team commerciale e tecnico esamina ogni richiesta.

Parliamo del tuo progetto