A commercial property management team needed a Hunter ACC99D irrigation controller integrated into standard building-system workflows. Chipkin FieldServer helped bridge the ACC2 source into BACnet and Modbus so the site could keep its installed irrigation controls while exposing usable data to the supervisory layer.
This case stood out because the upstream side was not a routine open protocol. The project depended on translating a specialized irrigation controller into formats the downstream systems could consume, then iterating the configuration until the field behavior matched the real site expectations.
At a Glance
- Industry: Commercial property operations / irrigation automation
- Location: Kazakhstan
- Customer: Commercial property management team
- Facility type: Large property irrigation control deployment
- Client role: Facilities engineering and plumbing support
- Project scale: 1 Hunter ACC99D controller with 5 configuration revisions and repeated field validation
- Protocols: From: Hunter ACC2 -> To: BACnet and Modbus
- Chipkin product: Chipkin FieldServer
- Project start: March 2025
- Internal reference: FSE16059
Architecture: Hunter ACC99D irrigation controller -> Hunter ACC2 -> Chipkin FieldServer -> BACnet and Modbus -> property monitoring workflow
ACC2 to BACnet and Modbus Challenge
The upstream/server side was a Hunter ACC99D irrigation controller using the Hunter ACC2 protocol. The downstream/client side needed standard BACnet and Modbus visibility so the property management team could incorporate irrigation information into its broader monitoring workflow.
That created a real protocol translation problem, not just a point-list exercise. The source side was a specialized irrigation controller, while the destination side expected standard building automation and industrial integration paths. The job required the gateway to normalize the source data into forms the downstream systems could commission reliably.
The support history also shows why this kind of project takes iteration. Firmware handling, configuration packaging, and field validation all had to line up before the project could move from troubleshooting into stable operation.
Why Chipkin
This was a strong fit for Chipkin because the project combined a specialized upstream protocol with standard downstream requirements. Chipkin FieldServer gave the customer a practical bridge between the installed Hunter controller and the supervisory systems that needed to consume the data.
Chipkin support also mattered because the job required repeated validation rather than a single configuration drop. That is often the difference between shipping hardware and delivering an integration that the site can actually use.
The Solution
Chipkin configured the FieldServer to translate the Hunter ACC99D controller data from Hunter ACC2 into BACnet and Modbus. The project moved through multiple file revisions as the team refined the scope and validated the gateway behavior against the installed system.
That iterative process was the solution, not an afterthought. Each revision brought the delivered file closer to the real field requirements, and the support workflow stayed active until the customer had a working handoff instead of an unproven draft.
The result was a standards-based integration path for an irrigation controller that would otherwise have remained isolated from the broader property-management environment.
For another project that brought a nonstandard source system into mainstream building workflows, see the Control4 XML to BACnet/IP Home Automation Gateway case study.
Irrigation Control Results
The project delivered a working Hunter ACC2 to BACnet and Modbus integration path for a live property deployment.
Project proof points:
- A Hunter ACC99D controller was integrated without replacing the installed irrigation platform.
- 5 configuration revisions were completed as the project moved through validation.
- BACnet and Modbus outputs were both part of the final supervisory integration scope.
- The customer confirmed successful completion after the extended troubleshooting and support cycle.
Have a Similar Irrigation Integration Project?
Need to expose a Hunter ACC2 irrigation controller to BACnet or Modbus without replacing the source system? Chipkin can help with FieldServer configuration, iterative validation, and difficult protocol-bridge projects that sit outside standard building controls. Tell us about your project.
Frequently Asked Questions
Can FieldServer expose Hunter ACC2 data to both BACnet and Modbus?
Yes. This project used Chipkin FieldServer to translate Hunter ACC2 irrigation-controller data into both BACnet and Modbus for the downstream supervisory workflow.
Why would an ACC2 integration need multiple revisions?
Projects like this often need a few rounds of file refinement because the live irrigation behavior and the downstream BAS expectations are not always fully aligned in the first pass. This deployment moved through five revisions before the final handoff was confirmed.
Can Chipkin help validate live irrigation points during commissioning?
Yes. The value in this case was not just the gateway file. Chipkin also supported the validation cycle until the site had a working supervisory handoff instead of an unproven draft.