ABB ACH580 Modbus to enteliWEB BMS Integration
Case Study – ABB ACH580 Modbus to enteliWEB BMS Integration
Please CONTACT US for questions
Overview
Ainsworth Inc. needed to bring operational data from seventeen ABB ACH580 variable-frequency drives into their Delta Controls enteliWEB management system. Each drive communicated over Modbus TCP using an FMBT-21 adapter module and was networked through an ABB BACnet/IP HVAC controller, which acted as the BACnet/IP interface feeding data into enteliWEB.
To unify the system, Chipkin deployed a FieldServer QuickServer gateway capable of converting all Modbus TCP data from the ACH580 drives into structured BACnet/IP objects for the ABB BACnet/IP HVAC controller and enteliWEB. The goal was to provide reliable, centralized visibility of all drive data through the existing BMS.
This approach delivered a stable and fully validated data path from the ACH580 drives into enteliWEB, ensuring accurate and consistent VFD monitoring across the site’s BACnet/IP infrastructure.
By combining a proven FieldServer gateway with Chipkin’s protocol-integration expertise, Ainsworth was able to expose all critical ACH580 drive data directly in enteliWEB without changing existing BMS infrastructure.
Challenge & Chipkin’s Solution
Ainsworth needed a way to view all ACH580 operational data—speed, torque, frequency, alarms, and status—through enteliWEB without relying on separate Modbus tools. However, the systems were not natively compatible: the drives communicated only via Modbus TCP, while the building management environment operated solely over BACnet/IP.
Beyond the protocol mismatch, several technical issues had to be solved to produce clean, usable data inside the BMS:
- Two incompatible protocols – ACH580 VFDs exposed data via Modbus TCP, while enteliWEB consumed BACnet/IP.
- Incorrect values in the BMS – Key parameters such as speed, torque, and frequency were reported as raw Modbus integers (e.g., 0–20,000) and required scaling into real engineering units.
- Alarms not visible to operators – Multiple alarm and status conditions were bit-packed into single Modbus registers and needed decoding into individual BACnet objects.
- Seventeen drives to manage – Operators wanted a unified BACnet structure in which all VFDs appeared under a single, well-organized device instance.
Using the FS-8790-33 Configuration & Support Service, Chipkin engineered a clean, fully validated Modbus TCP–to–BACnet/IP integration designed specifically for the ACH580 series. Raw Modbus values were converted into engineering units so enteliWEB displayed meaningful percentages and real-world readings. ABB’s bit-packed status registers were decoded into individual BACnet Binary Values—covering alarm active, tripped state, hand/auto mode, at-setpoint indication, and more.
All seventeen drives were grouped into a single BACnet/IP device instance with structured folders, readable labels, and standardized point naming to match Ainsworth’s navigation requirements in enteliWEB. Chipkin then performed remote commissioning to validate communication across the entire chain: ACH580 (Modbus TCP) → FieldServer → ABB BACnet/IP HVAC controller → enteliWEB. All required points were verified for accuracy, stability, and consistent behavior.
Outcome & Real-World Impact
The completed integration provided Ainsworth with a unified BACnet/IP view of all seventeen ACH580 drives, enabling accurate monitoring of speed, alarms, operating states, and performance data directly through enteliWEB. With validated scaling, stable Modbus TCP polling, and a structured BACnet object model, the FieldServer solution ensured dependable long-term operation without requiring changes to existing site infrastructure.
Ainsworth now benefits from centralized HVAC visibility, improved maintenance and diagnostics workflow, and seamless compatibility with their Delta Controls BMS—all while continuing to use their existing ABB ACH580 VFD hardware.
About Chipkin
Chipkin Automation Systems specializes in protocol integration, gateway configuration, and legacy system modernization across HVAC, industrial, and building-automation sectors. We provide FieldServer configuration services and engineering expertise for communication with platforms such as Delta Controls enteliWEB, Schneider Electric EcoStruxure, Johnson Controls Metasys, Tridium Niagara, Siemens Desigo, and many other BACnet/IP, Modbus, and proprietary systems.
Chipkin helps clients reduce risk, streamline commissioning, and unlock the full potential of existing equipment.
FAQ
Can you integrate ABB ACH580 VFDs into a Delta Controls enteliWEB BMS? +
Yes. Using a FieldServer QuickServer, Chipkin can convert ACH580 Modbus TCP data (via FMBT-21 modules) into BACnet/IP objects that can be read by an ABB BACnet/IP controller and displayed in enteliWEB. We provide both the configuration and engineering support needed to complete the integration.
Do we need to replace our existing VFDs or ABB controller? +
No. In this project, the existing ABB ACH580 drives and ABB BACnet/IP HVAC controller were retained. Chipkin added a FieldServer gateway and custom configuration to bridge Modbus TCP to BACnet/IP, allowing enteliWEB to use the existing hardware stack.
How are ACH580 values scaled so they display correctly in the BMS? +
Many ACH580 values (such as speed or demand) are reported as raw Modbus integers. Chipkin configures the FieldServer to apply the correct scaling factors so the BMS sees real engineering units or percentages, rather than unscaled register values.
Can alarms and status bits from the ACH580 be shown as individual BACnet points? +
Yes. The ACH580 encodes multiple flags in bit-packed Modbus registers. Chipkin uses the FieldServer to extract these bits and publish them as individual BACnet Binary Values so operators can clearly see alarm, trip, hand/auto, and other status conditions in the BMS.
What information do you need to start an ACH580 to BACnet/IP integration project? +
Typically we request an ACH580 parameter or setup report, the desired point list, details on the network topology (including FMBT-21 usage), and information about the BMS and any intermediate controllers. With that, we can design and deliver a custom FieldServer configuration and support commissioning.