Easy BACnet- Home
- BACnet points lists
- Hunter Fans
- Fan with Yaskawa drive (ProtoNode FPC-N64 profile)
Fan drive (VFD) via BACnet gateway · BACnet points list
Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile) BACnet points list
Updated 7 November 2026Unofficial source
Hunter's ProtoNode FPC-N64 profile for fans with a Yaskawa drive exposes 19 BACnet objects per fan: a command word, speed command and feedback, fault code, motor current, fire relay input and function, communication-loss timeout, reference and run-command source, and the drive's network settings. It is served as BACnet IP or BACnet MS/TP.
This page lists 19 BACnet objects for the Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile) — 15 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from a copy of Hunter Fans’s documentation hosted by W.W. Cannon (manufacturer's rep), not by Hunter Fans itself, so treat it as unofficial.
- Manufacturer
- Hunter Fans
- Model
- Fan with Yaskawa drive (ProtoNode FPC-N64 profile)
- Equipment
- Fan drive (VFD) via BACnet gateway
- Equipment type
- VFDs & pumps
- BACnet objects
- 19 (15 writable)
- Transport
- BACnet IP, BACnet MS/TP
- Firmware
- Not stated
- Default device instance
- 50000 + Node-ID
- Also known as
- Hunter Fans ProtoNode, FPC-N64, Hunter Yaskawa fan BACnet
- Source document
- ProtoNode FPC-N64 Start-up Guide For Interfacing Hunter Fans Products · rev. Document Revision 2.B (unofficial copy, hosted by W.W. Cannon (manufacturer's rep))
Reference only, provided as-is: verify against Hunter Fans’s current documentation and the live device before use. Not official Hunter Fans information. Terms of use.
BMS integration notes: Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile)
Write the command and speed command for each fan and read speed feedback, current and the fault code. The communication-loss timeout and reference/run source objects set how the drive reacts to the network.
Minimum points to map
The short list most integrators start with — enough to run the unit from a BMS. Map more as the job needs.
| Object | Name | Why | Access |
|---|---|---|---|
| AV 1 | CommandXXX | Run command word | Write |
| AV 2 | SpeedCmdXXX | Speed command | Write |
| AI 3 | SpeedMonXXX | Speed feedback | Read |
| AI 6 | FanXXX/Current | Motor current | Read |
| BI 7 | FanXXX/FireRelay | Fire relay input | Read |
| AI 4 | FaultMonXXX | Drive fault code | Read |
Network setup
- Each fan drive is its own BACnet device: Device Instance = Node_Offset (default 50,000) + the drive's Node-ID.
- The drives talk Modbus TCP/IP to the ProtoNode; enter each drive's ip_address and tcp_id when adding its profile in the web configurator.
- Default ProtoNode IP address 192.168.1.24; the ProtoNode serves BACnet IP or BACnet MS/TP to the BMS.
Watch out for
- The guide does not decode the command word or fault code; use the Yaskawa drive manual.
- Network-setting objects (ip, sn, Write) change the drive's own configuration; don't write them from routine BMS logic.
Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile) BACnet objects
Type: AI, AO, AV, BI, BO, BV, MI/MO/MV (multi-state) · Access: Read read-only, Write writable, Command writable with a priority array.
Note: the source document has no read/write column, so access here is inferred from the object type (inputs read-only, values writable). Confirm on the live controller before writing.
| Description | States | |||||
|---|---|---|---|---|---|---|
| AVmin | 1 | CommandXXX | Modbus register 1 | Write | ||
| AVmin | 2 | SpeedCmdXXX | Modbus register 2 | Write | ||
| AImin | 3 | SpeedMonXXX | Modbus register 65 | Read | ||
| AImin | 4 | FaultMonXXX | Modbus register 128 | Read | ||
| AV | 5 | FanXXX/CommLossTimeout | Modbus register 1012 | Write | ||
| AImin | 6 | FanXXX/Current | Modbus register 8199 | Read | ||
| BImin | 7 | FanXXX/FireRelay | Modbus register 43.2 | Read | ||
| AV | 8 | FanXXX/FireRelayFunction | Modbus register 1024 | Write | ||
| AV | 9 | FanXXX/FreqRefSel | Modbus register 384 | Write | ||
| AV | 10 | FanXXX/ip1 | Modbus register 997 | Write | ||
| AV | 11 | FanXXX/ip2 | Modbus register 998 | Write | ||
| AV | 12 | FanXXX/ip3 | Modbus register 999 | Write | ||
| AV | 13 | FanXXX/ip4 | Modbus register 1000 | Write | ||
| AV | 14 | FanXXX/RunCmdSel | Modbus register 385 | Write | ||
| AV | 15 | FanXXX/sn1 | Modbus register 1001 | Write | ||
| AV | 16 | FanXXX/sn2 | Modbus register 1002 | Write | ||
| AV | 17 | FanXXX/sn3 | Modbus register 1003 | Write | ||
| AV | 18 | FanXXX/sn4 | Modbus register 1004 | Write | ||
| AV | 19 | FanXXX/Write | Modbus register 2304 | Write |
No points match these filters.
Object ID lookup: Hunter Fans Fan with Yaskawa drive point IDs by name
AV1CommandXXXAV2SpeedCmdXXXAI3SpeedMonXXXAI4FaultMonXXXAV5FanXXX/CommLossTimeoutAI6FanXXX/CurrentBI7FanXXX/FireRelayAV8FanXXX/FireRelayFunctionAV9FanXXX/FreqRefSelAV10FanXXX/ip1AV11FanXXX/ip2AV12FanXXX/ip3AV13FanXXX/ip4AV14FanXXX/RunCmdSelAV15FanXXX/sn1AV16FanXXX/sn2AV17FanXXX/sn3AV18FanXXX/sn4AV19FanXXX/Write
Integration notes
- XXX in each object name is replaced by the fan's number on the ProtoNode.
- The guide prints the Modbus register for each object but no units, ranges or state texts.
- No read/write column: access is inferred (AV/BV writable, AI/BI read-only).
- By their names, FanXXX/ip1-ip4 and sn1-sn4 carry the drive's IP address and subnet mask octets; the guide does not describe them.
Check it against the live device. A points list tells you what the controller can expose; the unit in front of you may differ by firmware or installed options. This list is provided as-is for reference only and may contain mistakes — confirming it before you write, map or commission anything is up to you (terms). Easy BACnet scans a network for BACnet IP devices from an Android phone, reads every object on the Fan with Yaskawa drive (ProtoNode FPC-N64 profile) and exports what it actually has to Excel — free. New to BACnet? Start with what a BACnet points list is and what the object types mean.
Questions about the Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile)
How many BACnet points does the Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile) have?
This list has 19 BACnet objects: 3 analog inputs, 15 analog values, 1 binary input. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile) BACnet points are writable?
15 of the 19 objects accept a write. Points marked Command have a priority array: a write holds until it is released, so release it back to automatic when you are done. The source has no read/write column, so this is inferred from object type.
Where is the official Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile) BACnet documentation?
Hunter Fans does not publish it on its own website. This list comes from ProtoNode FPC-N64 Start-up Guide For Interfacing Hunter Fans Products, revision Document Revision 2.B, a copy hosted by W.W. Cannon (manufacturer's rep) at https://wwcannon.com/wp-content/uploads/2024/11/Hunter-ProtoNode-BMS-Secure-Gateway-Interface-Products.pdf. Ask Hunter Fans or its representative for the current revision.
What are the minimum BACnet points to integrate the Hunter Fans Fan with Yaskawa drive (ProtoNode FPC-N64 profile)?
Start with AV 1 CommandXXX (Run command word); AV 2 SpeedCmdXXX (Speed command); AI 3 SpeedMonXXX (Speed feedback); AI 6 FanXXX/Current (Motor current); BI 7 FanXXX/FireRelay (Fire relay input); AI 4 FaultMonXXX (Drive fault code).
How do I check these points on the real Fan with Yaskawa drive (ProtoNode FPC-N64 profile)?
Scan the network with a BACnet IP browser such as Easy BACnet, open the device and compare its object list with this table. Anything missing is usually an option that isn't installed or a point that is disabled in the controller's configuration.
More Hunter Fans BACnet points lists
Source: ProtoNode FPC-N64 Start-up Guide For Interfacing Hunter Fans Products · rev. Document Revision 2.B. Object names, instances and units are reproduced as published; descriptions are our own.