A commercial facilities integrator needed Hunter ACC2 irrigation data inside a BACnet/IP building automation workflow. Chipkin QuickServer bridged the ACC2 controller, preserved Centralus cloud coexistence, and added custom web pages for alarms and scheduling after a standard gateway handoff alone was not enough.
This project stood out because the Hunter ACC2 controller was a specialized irrigation platform rather than a native BACnet device waiting to be discovered. The site needed irrigation status, alarms, and schedule visibility carried into the BAS while keeping the installed controller and its cloud workflow in place.
At a Glance
- Industry: Commercial property irrigation / building automation
- Location: South Carolina, USA
- Customer: Commercial facilities systems integrator
- Facility type: Large commercial property irrigation deployment
- Project scale: 1 Hunter ACC2 controller with BACnet/IP BAS handoff plus custom browser-based alarm and scheduling pages
- Upstream/server device: Hunter ACC2 irrigation controller
- Downstream/client system: BACnet/IP building automation system with browser-based service workflow
- Protocols: From: Hunter ACC2 -> To: BACnet/IP
- Chipkin product: Chipkin QuickServer FS-QS-2X10 with FS-8705-41 driver
- Project start: April 2022
- Internal reference: FSE14801
Hunter ACC2 irrigation controller -> Hunter ACC2 -> Chipkin QuickServer -> BACnet/IP -> building automation system and service web workflow
Hunter ACC2 to BACnet/IP Challenge
The upstream/server side was a Hunter ACC2 irrigation controller. The downstream/client side was a BACnet/IP building automation workflow that needed irrigation status and alarms alongside the rest of the site systems.
The challenge was broader than protocol conversion alone. The Hunter ACC2 controller also needed to keep working with Centralus cloud access, and the service team wanted browser-based pages for alarms, scheduling, and zone visibility instead of a bare protocol gateway handoff.
That made this a specialized building-integration problem. The customer wanted to keep the installed Hunter ACC2 hardware, avoid a separate irrigation-only workflow, and still give the BAS team a usable BACnet/IP view they could commission with confidence.
Why Chipkin
This was a strong fit for Chipkin because the project needed more than a commodity gateway. It needed a proven Chipkin QuickServer platform, a Hunter ACC2 driver, firmware work to preserve coexistence with the cloud-connected controller, and custom web pages that made the final integration useful for service technicians as well as the BAS team.
That combination of protocol gateway work, device-specific troubleshooting, and custom support is exactly where Chipkin tends to be strongest.
The Solution: Hunter ACC2 to BACnet/IP QuickServer Bridge
Chipkin deployed QuickServer between the Hunter ACC2 controller and the downstream BACnet/IP building automation system. The QuickServer handled the Hunter ACC2 protocol translation, exposed the required irrigation data to the BAS, and added browser-based pages for alarms, scheduling, and zone status.
The decisive part of the solution was not just reading the controller. Chipkin also updated the firmware and web files so the Hunter ACC2 controller could stay usable with its Centralus cloud workflow while the BACnet/IP handoff and service web experience were being delivered.
The end result was a single integration path that kept the installed Hunter ACC2 controller in place while giving both operators and technicians a more usable monitoring workflow.
For another project that brought a specialized upstream system into a standard BACnet/IP workflow, see the Control4 XML to BACnet/IP Home Automation Gateway case study.
Hunter ACC2 to BACnet/IP Results
The project delivered a working Hunter ACC2 to BACnet/IP integration for a live commercial irrigation deployment.
Project proof points:
- Hunter ACC2 irrigation data and alarms were exposed to the BACnet/IP building automation workflow.
- Custom browser-based pages gave the service team alarm, scheduling, and zone-status visibility beyond the BACnet/IP handoff.
- Centralus cloud coexistence was preserved while the QuickServer integration stayed in place.
- Final commissioning was verified after the firmware and web files were loaded on site.
Before: the Hunter ACC2 controller sat outside the site’s standard BACnet/IP monitoring workflow, and the service model still depended on a separate irrigation-only path. After: the same Hunter ACC2 controller remained in place while the BAS and service team gained a usable BACnet/IP and browser-based monitoring workflow.
The closeout tone from the project was simple and practical:
“Everything is working well now and the site can move ahead with the handoff.”
— Project lead, commercial irrigation integration team
Have a Similar Hunter ACC2-to-BACnet/IP Project?
Need to expose a Hunter ACC2 irrigation controller to a BACnet/IP BAS without losing cloud visibility or technician-friendly service access? Chipkin can help with QuickServer configuration, custom web workflows, and protocol gateway support for difficult irrigation integration projects. Tell us about your project.
Frequently Asked Questions
Can QuickServer expose Hunter ACC2 irrigation data to BACnet/IP?
Yes. In this project, Chipkin QuickServer translated Hunter ACC2 controller data into a BACnet/IP presentation the BAS team could use.
Can Chipkin keep Centralus cloud access working during a Hunter ACC2 integration?
Yes. A key part of this project was preserving the controller’s cloud coexistence while the Hunter ACC2 to BACnet/IP gateway path and service workflow were finalized.
Can Chipkin add custom alarm and scheduling pages for Hunter ACC2 projects?
Yes. This case study included custom web pages so the service team could review Hunter ACC2 alarms, schedules, and zone status in a browser instead of depending only on the downstream BACnet/IP handoff.