ALDAR EUROASIA PROPERTY MANAGEMENT LLP can now expose Hunter ACC99D irrigation controller data to its building systems over both BACnet and Modbus. Getting there required configuration alignment, a repeatable loading workflow, and staged commissioning on a protocol family most BMS teams do not handle every day.
At this Astana project, the challenge was not just reading an irrigation controller. The upstream device was a Hunter ACC99D running the ACC2 protocol, while the downstream side needed both BACnet and Modbus visibility for the broader building management workflow. Chipkin used a FieldServer to bridge that protocol gap, refine the configuration workflow, and stay with the job until the customer confirmed the integration was working.
At a Glance
- Industry: Irrigation / property management
- Location: Astana, Kazakhstan
- Customer: ALDAR EUROASIA PROPERTY MANAGEMENT LLP
- Facility type: Commercial property irrigation infrastructure
- Client role: Property engineering team
- Protocols: From: ACC2 → To: BACnet and Modbus
- Chipkin product: FieldServer
- Project window: March 2025 kickoff with final confirmation in January 2026
Hunter ACC99D Irrigation Controller → ACC2 → Chipkin FieldServer → BACnet / Modbus → BMS / SCADA
ACC2 to BACnet and Modbus Challenge
The upstream side of the project was a Hunter ACC99D irrigation controller. The downstream side needed standard building-system visibility over BACnet and Modbus so the irrigation data could be supervised alongside the rest of the site infrastructure. There was no native handoff between the ACC2 controller workflow and the controls network the property team needed to use.
The project also required configuration-file alignment and a repeatable firmware-loading workflow early in the process. The customer had the hardware in place, but the gateway still needed the right file path, loading sequence, and reviewed configuration before the live points could be commissioned cleanly. That is common on less familiar controller families: the protocol pair is supported, but the project still depends on careful intake review and a reliable startup process.
The practical business problem was simple. Without a clean BACnet and Modbus handoff, the site team could not bring irrigation status and control data into the larger building workflow with confidence. They needed a working integration, not another round of guesswork around config files and protocol settings.
Why Chipkin
This was a strong fit for Chipkin because it combined a specialized upstream controller family with two downstream protocols that building teams already understand. FieldServer gave ALDAR a protocol-conversion platform that could sit between the irrigation controller and the building systems, while Chipkin support handled the iterative validation that made the difference between a shipped box and a confirmed working project.
For jobs like this, the value is not only protocol translation. It is having support engineers who can align the firmware-loading workflow, revise the configuration as field details become clearer, and keep the customer moving when the project stretches across multiple review cycles.
The Solution
Hunter ACC99D Irrigation Controller → ACC2 → Chipkin FieldServer → BACnet / Modbus → BMS / SCADA
Chipkin configured the FieldServer to read the Hunter ACC99D controller over ACC2 and serve the resulting points downstream over both BACnet and Modbus. The work centered on aligning the file-loading path, revising the configuration as more field information became available, and validating that the translated data was usable on the building-system side.
Rather than treating the early loading workflow as a one-time support answer, Chipkin stayed involved through multiple rounds of customer testing and follow-up. On specialized controller integrations, the protocol bridge is only useful when the customer team can actually commission it in the field.
By the end of the project, the delivered package was not just a gateway file. It was a working protocol handoff backed by iterative support and customer confirmation.
ALDAR Irrigation Integration Results
- Confirmed dual-protocol handoff — ALDAR could expose ACC2 irrigation-controller data to the site over both BACnet and Modbus.
- 5 configuration revisions were completed through commissioning and validation.
- 3 live support calls helped move the project through the final commissioning steps.
- 40 support hours were invested across the engagement.
- 60% customer-side wait time shows that Chipkin stayed engaged through long testing and response gaps instead of dropping the project after the first delivery.
Before: The site had a Hunter ACC99D controller, but not a dependable way to bring that irrigation data into the broader building workflow over standard BMS protocols.
After: The property team had a confirmed FieldServer integration serving the controller data over BACnet and Modbus, with the configuration and loading workflow validated.
Have a Similar ACC2-to-BACnet-or-Modbus Project?
If you need Hunter irrigation-controller data to appear cleanly inside a BACnet or Modbus building-system workflow, Chipkin can scope the protocol gap, configure the gateway, and help your team through commissioning without leaving the hard protocol details to field guesswork. Tell us about your project.