Overview
This guide covers the most common McQuay gateway failures Chipkin is likely to see: wrong controller-branch assumptions, wrong PCL type selection, incomplete OPM board settings, and point-count surprises discovered after the map is already built. Use it with the McQuay when exposing McQuay HVAC data into BACnet, Modbus, or another supervisory workflow.
Diagnostic Flow
- Confirm the exact equipment family and controller-board type.
- Confirm whether the setup uses a PCL branch or OPM branch.
- Confirm node, baud, parity, and password details.
- Confirm the requested point count against the gateway tier.
- Only then review target-side mapping.
Symptoms & Solutions
| Symptom | Likely Cause | Action | Related Page |
|---|---|---|---|
| No useful communication starts | The wrong PCL type or board profile is selected | Recheck the exact McQuay controller type before changing downstream mapping | McQuay |
| OPM settings look close but the job still stays offline | Node, password, baud, or parity is wrong or incomplete | Validate every OPM setup field against site documentation | McQuay |
| A proven McQuay config from another site still does not fit | The new unit is on a different controller branch or retrofit pattern | Compare controller family and object model before reusing the old template | FieldServer |
| The map builds but commissioning stops with point-limit messages | The gateway tier is too small for the requested scope | Recheck total point count and apply the correct point-tier plan | QuickServer |
| A repeat project behaves differently than the last one | A previous config was reused without model-specific revalidation | Compare the new unit against the prior project instead of assuming they match | FieldServer |
| Source-side values look right but BAS objects are still wrong | The target-side presentation now needs review | Recheck BACnet or Modbus mapping after the source side is proven | BACnet |
The Wrong Controller Profile Was Chosen
McQuay jobs often fail at the very first protocol assumption.
Confirm The Actual Equipment Branch
Confirm:
- Exact equipment model
- Installed controller-board type
- Whether the project expects PCL behavior or OPM behavior
- Whether the current config matches that expectation
[!WARNING] Repeated no-response or nonsense-response behavior usually means the selected McQuay profile is wrong, not that the BAS target is the problem.
The OPM Setup Is Incomplete
OPM-oriented projects need more than a model name.
Rebuild The Source Settings
Look again at:
- Node address
- Baud rate
- Parity
- Device password
- Any site-specific controller notes
If even one of these fields is missing, the project can spend days in avoidable trial-and-error.
The Previous Retrofit Template Was Over-Applied
Some McQuay jobs look similar because the equipment branding matches, but the controller branch does not.
Recheck The Retrofit Assumption
Look again at:
- Whether the project is a BACdrop replacement, PCL setup, or OPM setup
- Whether the prior object list came from the same controller family
- Whether the source side is really serial, BACnet, or another branch entirely
[!WARNING] Do not keep tuning a reused McQuay config until you first prove that the current unit is on the same controller branch as the original reference project.
The Point Count Was Not Validated Up Front
This is a recurring commercial and technical failure pattern.
Separate Scope From License Tier
Confirm:
- Total requested points
- Current gateway tier
- Whether optional points can be deferred
- Whether the site expects full visibility or a smaller operational subset
If the requested point count is well above the default tier, solve that before deeper troubleshooting.
Quick Diagnostic Decision Tree
- Start by confirming the equipment family and controller-board type.
- If that is unclear: stop and collect it before further testing.
- If it is clear: continue to source settings.
- Check whether the job uses a PCL branch or OPM branch.
- If that is unclear: resolve that first.
- If it is clear: continue to source parameter validation.
- Check whether node, baud, parity, and password details are all confirmed.
- If not: rebuild the source setup first.
- If yes: continue to point scope.
- Check whether the project is being treated as the same controller branch as a previous McQuay job.
- If not: re-verify the controller family and object model first.
- If yes: continue to point scope.
- Check whether the requested point count fits the deployed gateway tier.
- If not: solve the tier issue before more mapping work.
- If yes: continue to target-side validation.
- Check whether the BAS values are still wrong after the source side is proven.