# WaterFurnace Heat-Pump PX

## What is included
- WaterFurnace.px: one PX file containing three tabs.- Point_Bindings.json: 64 unique placeholder point names, relative ORDs, expected types, and an empty actual_ord field for your mapping notes. This JSON is a reference worksheet, not an automatic import or binding tool.- Three PNG design previews: Graphic, Controls, and Diagnostics. These are illustrative renders of the PX layout, with missing values shown as dashes; they are not Workbench screenshots or live readings. They omit the outer tab navigation. Fonts and status effects can differ in Niagara.
The PX uses native geometry and text for its equipment diagram. It does not require external image files or a third-party graphic library. Values are data-bound; the equipment symbols are static, with no rotating fan or animated refrigerant flow.
## Tabs
| Tab | Contents || --- | --- || Graphic | Air/water schematic, temperatures, occupancy, operating mode, compressor/fan/valve status, setpoints and demands || Controls | Comfort settings, mode/enable points, and optional equipment points; click values to open their components || Diagnostics | Faults, freeze protection, pressures, temperatures, run hours, power and energy where available || Points | Your original BACnet point manager || Extensions | Your original JCI point extension manager || Alarms | Your original station-wide alarm console, not filtered to this unit || Trend Graphs | Your original supply-air history chart, with a last-24-hours default |

## Install and bind
1. Copy WaterFurnace.px into the station's PX folder, for example Files/px/WaterFurnace.px. The previews and JSON do not need to be installed on the JACE.2. Create a PX view on the BACnet device component, choosing this existing PX file as the source. The assumed view context has a child points folder and health/down, matching your base template. Attaching it to points itself requires removing points/ from the new relative ORDs and adapting the title/offline bindings.3. Open the view in PX Editor. For each new value, edit its BoundLabelBinding ord and hyperlink to the actual point. Both fields use placeholders such as slot:points/SpaceTemp.4. Keep the binding on the point component, not its out slot: the ObjectToString format is %out%. If you intentionally bind directly to out, adapt the converter to format that status value instead.5. Change every occurrence of a renamed point across Graphic, Controls, and Diagnostics. The JSON lists each unique alias once. Use valid Niagara slot-path encoding for spaces and special characters; copy ORDs from Workbench.6. Check numeric facets/units, Boolean text and polarity, enum labels, and available actions. No BACnet object IDs, write priorities, enum numbers, or manufacturer point names have been invented or assigned.7. Remove unsupported optional rows using PX Editor. Unsupported bindings may display unresolved/degraded status; they are not automatically hidden or substituted with a normal value. Do not create fake normal-status points to fill missing telemetry.8. Verify the retained navigation and history paths below. Save, open the view normally, and check the browser view as well as Workbench.

## Tailor by model
| Model supplied | Template treatment || --- | --- || V7AH036 | Retain compressor running status and available modulation/capacity telemetry. Check whether the controller reports percent, speed index, Hz, or RPM and rename the field accordingly. A variable-speed compressor is not a second compressor stage. || V3AH015 | Retain single-stage compressor status. Remove compressor modulation and Stage 2 unless adapting the template to different equipment with those features. || Either | Retain only the installed fan, valve, economizer, reheat, auxiliary heat, flow, power, pressure and leak-detection points. Exact options and point availability require the complete model suffix and controller point list. |
Air and water paths are functional illustrations, not a piping/refrigerant circuit drawing or an assertion of exact fan/coil placement. Reversing-valve state does not establish heating/cooling mode until coil polarity is verified.
## Operator controls and calculations
The Controls tab provides point-navigation links. It does not issue writes merely by opening the page and does not include preset overrides or direct command buttons. Use the actual writable point's normal actions, permissions, configured priority, and release mechanism. If you want inline Set/Auto actions, generate them from the confirmed writable point using Workbench's widget wizard.
AirDeltaT means supply minus return air temperature; WaterDeltaT means leaving minus entering water temperature. These fields require existing measured/calculated station points. The PX does not calculate delta-T, superheat, subcooling, power, runtime, or fault conditions. Alarm rows require actual fault signals; the alarm console requires existing station alarm configuration.
## Reusing the same PX
When devices expose identical relative point names, attach the same file to each device. The title and relative bindings resolve from that device. Editing a shared file changes all its views. For differing point names, either standardize the station's graphic-facing point organization while preserving actual point behavior, or make a per-unit copy and change its bindings. This template does not automatically detect model series or reconcile different controllers' point names.

## Manufacturer references
- [WaterFurnace Versatec 700](https://www.waterfurnace.com/commercial/products/water-source-geothermal-heat-pumps/versatec-700): variable-capacity water-to-air product family.- [WaterFurnace Versatec 300](https://www.waterfurnace.com/commercial/products/water-source-geothermal-heat-pumps/versatec-300): single-stage water-to-air product family.- [Versatec 700 installation guide](https://www.waterfurnace.com/literature/versatec/igv7-0011wa.pdf).- [Versatec 300 installation guide](https://www.waterfurnace.com/literature/versatec/igv3-0007wb.pdf).
Product-family references guide the template's feature organization; they do not establish the options or BACnet object mapping of your individual units.

Copyright 2026 Brian Tahara