Overview
This guide covers the most common Hunter ACC2 gateway failures Chipkin is likely to see: incorrect controller IP setup, incomplete point inventories, stale zone or alarm data, and controller cloud features that do not coexist cleanly with the gateway path. Use it with the Hunter ACC2 when exposing irrigation-controller data into BACnet or another supervisory system.
Diagnostic Flow
- Confirm the exact controller model, firmware, and network context.
- Confirm the points spreadsheet or controller export exists.
- Confirm which schedules, alarms, and status values are in scope.
- Validate that live controller data is actually changing.
- Only then review downstream mapping and cloud-coexistence behavior.
Symptoms & Solutions
| Symptom | Likely Cause | Action | Related Page |
|---|---|---|---|
| The gateway never reaches the ACC2 even though the network looks normal | The team entered the default gateway IP instead of the ACC2 controller IP | Recheck the controller address before deeper troubleshooting | Hunter ACC2 |
| The BAS sees only a few irrigation values | The project never had a complete controller points inventory | Stop and collect the ACC2 points spreadsheet or equivalent export | Hunter ACC2 |
| Values appear but do not update reliably | Live data is stale or the mapped object set is incomplete | Recheck point freshness against the controller before changing BACnet exposure | BACnet |
| Controller cloud or remote features break when the gateway is attached | Network coexistence was not validated | Review gateway placement and controller cloud behavior together | QuickServer |
| The site wants one gateway for several ACC2 controllers | The deployed driver pattern does not support the expected multi-controller layout | Recheck the architecture before changing individual point maps | FieldServer |
| The integrator expected alarm pages or schedule views that never appeared | The job was scoped like a simple point conversion rather than a controller-specific integration | Reconfirm deliverables before continuing the build | Hunter ACC2 |
| Field side looks healthy but BAS values are still wrong | Downstream object mapping now needs review | Recheck the target-side object model after source-side validation | BACnet |
The Points Inventory Was Never Defined
This is the most common ACC2 failure pattern. The team knows the controller but not the data model.
Confirm The Controller Export
Confirm:
- Points spreadsheet or equivalent export
- Required zones and schedules
- Required alarms and statuses
- Which values must be live versus summary-only
[!WARNING] If the irrigation points inventory is missing, troubleshooting the gateway is mostly noise.
The Wrong IP Was Configured
This is one of the most repeatable ACC2 setup failures.
Verify The Controller Address
Confirm:
- The actual ACC2 controller IP
- Whether the team accidentally used the default gateway IP
- Whether the current project notes distinguish source IP from gateway management IP
[!WARNING] Do not use the default gateway IP as if it were the ACC2 controller address. Prove the source controller IP first.
Live Data Is Stale Or Incomplete
Healthy connectivity does not guarantee meaningful controller exposure.
Recheck The Source Data Model
Look again at:
- Whether the controller values actually change locally
- Whether all required point groups were included
- Whether alarm and schedule values were separated correctly
- Whether one controller export revision was replaced by another mid-project
Cloud Features Stop Working With The Gateway Present
Cloud-connected irrigation controllers need coexistence validation.
Validate The Combined Network Path
Confirm:
- Whether cloud connectivity must remain active during gateway operation
- Whether the gateway changed the controller’s expected network behavior
- Whether the issue is source-side or simply target-side visibility
Quick Diagnostic Decision Tree
- Start by confirming the controller model, firmware, and points export.
- If that is unclear: stop and collect the controller engineering artifacts first.
- If it is clear: continue to live-value validation.
- Check whether the source values change correctly at the controller.
- If not: solve the controller-side data issue first.
- If yes: continue to scope validation.
- Check whether the configured source IP is really the ACC2 controller.
- If not: correct that before deeper troubleshooting.
- If yes: continue to scope validation.
- Check whether all required schedules, alarms, and statuses are actually mapped.
- If not: rebuild the point inventory and map.
- If yes: continue to coexistence review.
- Check whether cloud or remote controller features break when the gateway is present.
- If yes: treat network coexistence as a first-class issue.
- If no: continue to target-side validation.
- Check whether the BAS view is still wrong after source-side validation.
- If yes: recheck BACnet exposure.
- If no: the main fault was on the ACC2 engineering side.