VFD BACnet Integration: Why Start/Stop Commands Don’t Work
The VFD is online. You can read frequency, current, alarms, and status in the BAS. Then you command the fan OFF and nothing happens.
Or Start/Stop works but the drive ignores the BAS speed command. These problems are often called “BACnet communication issues,” even when communication is already working.
Determine who owns the drive command right now.
Quick Answer
- Confirm the VFD is actually communicating.
- Identify who owns Start/Stop.
- Check hardwired permissives and interlocks.
- Identify the active speed-reference source.
- Compare command with actual drive feedback.
- Verify BACnet addressing and communication settings.
- Check BAS overrides and command priorities.
- Understand the intended response to communication loss.
Online does not mean under BACnet control.
What to Check First
- ✓ Is the VFD online and are live BACnet values updating?
- ✓ Is the drive in the intended Auto/Remote mode?
- ✓ What source controls Start/Stop?
- ✓ What source controls speed?
- ✓ Is a hardwired run permissive or interlock involved?
- ✓ Does the BAS command change when Start/Stop is issued?
- ✓ Does the VFD run status change in response?
- ✓ Does actual frequency follow the speed command?
- ✓ Are BAS overrides or higher-priority commands active?
- ✓ Are there drive warnings, trips, or safeties?
1. Prove BACnet Communication Before Troubleshooting Control
If the BAS can reliably read changing values such as output frequency, motor current, run status, and faults, the network is exchanging useful information with the drive. That does not prove writable control points are configured correctly.
For example, Trane TR200 documentation separates BACnet communication settings from control-source, start-selection, and reference settings. Other manufacturers use different menus and parameter numbers, but the same troubleshooting concept applies.
2. Find Out Who Owns Start/Stop
Depending on the drive and application, Start/Stop may come from the local keypad, a hardwired digital input, BACnet, another fieldbus, internal logic, or a packaged controller.
On the Trane TR200, for example, control-site and bus/digital start-selection settings determine how the drive accepts control. Do not copy its parameter numbers to a Danfoss, ABB, Yaskawa, or another VFD. Use the exact manual for the installed drive and firmware.
3. A Run Permissive Is Not the Same as a Start Command
A Start command requests operation. A run permissive or interlock determines whether operation is allowed. Those are different functions.
A fan may require a damper-proven signal, smoke-control condition, freeze-protection state, equipment enable, or another auxiliary contact before the drive is permitted to run. If BACnet Start changes but the drive does not start, check the permissive path.
4. Why Won’t the VFD Stop?
If the BAS writes OFF but the drive keeps running, look for another active command source: hardwired Start, local/manual mode, life-safety sequence, internal drive logic, or another controller.
Never remove or defeat a life-safety or hardwired protection function just to make network Start/Stop behave the way you expect.
5. Start/Stop and Speed Reference Are Separate Problems
A drive can accept Start/Stop from one source and speed reference from another. One application might use BACnet for Start/Stop and 0-10 V for speed. Another might use a hardwired Start input and BACnet speed reference.
If the fan starts but remains at a fixed speed, identify the active reference source before blaming the BACnet network.
6. Compare Command With Feedback
Always separate what the BAS requests from what the drive actually does.
- BAS Start command
- Drive Run status
- Speed command/reference
- Actual VFD speed or frequency
- Alarm/fault status
Start ON with Run OFF points toward permissives, faults, mode, or command source. Start OFF with Run ON points toward another active command or override. Speed command at 40% with actual speed at 100% points toward another reference, internal PID, limits, scaling, or configuration.
7. Do Not Copy BACnet Object Numbers Between VFD Brands
Different drive manufacturers and product families expose different BACnet objects. A Trane TR200 example may use one set of objects, while Danfoss FC 102, ABB ACH580, and other drives use different point lists and option-card structures.
Use the point list for the exact drive, communication option, and firmware.
8. BACnet Addressing Still Matters
For MS/TP drives, verify the local MAC address, baud rate, Device Instance, wiring, and termination. For BACnet/IP drives, verify the manufacturer’s IP and BACnet settings. Do not confuse IP address with Device Instance.
9. Check BAS Overrides and BACnet Command Priority
A drive can be configured correctly while the BAS command is being held by an override or higher BACnet command priority. If a command refuses to release, inspect the BAS priority/override path before changing VFD parameters.
Implementation varies: some drive points are commandable BACnet objects, while other BAS integrations use proxy points. Follow the actual architecture.
10. Know What Happens When BACnet Communication Is Lost
A fieldbus-controlled VFD needs an intentional failure response. Depending on the drive and application, communication loss may stop the drive, hold the last condition, switch to another reference, or follow a predefined fail-safe strategy.
The correct behavior depends on the sequence of operation. Comfort ventilation, smoke control, cooling towers, pumps, and critical cooling systems may require very different responses.
Real-World Field Lesson: BACnet Was Only One Part of the Start/Stop Circuit
During a field investigation involving a Danfoss HVAC VFD, BAS Start/Stop operation did not behave as expected. A hardwired run-permissive connection was present at the drive while BACnet control was also part of the investigation.
The fan would not respond to the expected stop behavior, so troubleshooting had to move beyond checking whether the BACnet point changed. The useful question became: which input or control source actually has authority over the drive?
A final manufacturer parameter change was not documented in the available field record, so the lesson is the diagnostic method rather than a universal setting.
BAS command → BACnet point → VFD control source → hardwired inputs/permissives → final drive state
A Better VFD Commissioning Sequence
- Verify the drive locally and safely.
- Establish reliable BACnet communication.
- Map and verify read-only feedback first.
- Identify the intended Start/Stop and speed-reference sources.
- Test both Start and Stop.
- Test several safe speed commands and verify actual response.
- Test permissives and interlocks according to the sequence.
- Verify the intended communication-loss response where authorized.
- Remove temporary overrides and commissioning commands.
What Facility Managers Can Check
- Is the VFD in Auto/Remote?
- What does the BAS Start command show?
- What does Run Status show?
- What speed is commanded?
- What speed is the drive actually running?
- Are there drive alarms?
- Is a BAS override present?
- Did the problem start after drive replacement or controls work?
What a BAS Technician Should Check
- BACnet communication and addressing
- Point mapping
- Start/Stop source
- Speed-reference source
- Local/remote status
- Digital inputs and run permissives
- Interlocks and life-safety sequences
- BACnet priority/overrides
- Communication-loss behavior
- Actual speed feedback and alarms
- Approved sequence of operation
Key Takeaways
- An online VFD is not necessarily under BACnet control.
- Start/Stop and speed reference can come from different sources.
- A run permissive is not the same as a Start command.
- Hardwired inputs can interact with network commands.
- Compare command with feedback.
- Do not copy point IDs or parameter numbers between VFD brands.
- Check BAS overrides and command priorities.
- Commission communication-loss behavior intentionally.
FAQ
Why is my VFD online in BACnet but won’t start?
The drive may not be configured to accept Start from the network, or a permissive, interlock, fault, local-control condition, or another command source may be preventing operation.
Why won’t my VFD stop from the BAS?
Another control source may still be active. Check local/remote status, hardwired Start inputs, permissives, overrides, and life-safety sequences before changing network settings.
Can Start/Stop be BACnet while speed is controlled by analog?
Potentially, yes. Start/Stop and speed reference are separate control functions. The exact combinations depend on the drive and firmware.
Is a run permissive the same as a fan command?
No. A permissive establishes whether the drive is allowed to operate; a Start command requests operation.
Which BACnet point starts a VFD?
There is no universal object ID for every VFD. Use the exact manufacturer point list for the installed drive, communication option, and firmware.
Related Articles
Sources & Further Reading
- Trane – TR200 Embedded BACnet Operating Instructions
- Trane – TR200 Series HVAC Drives
- Danfoss – VLT HVAC Drive FC 102
- Danfoss – VLT Fieldbus Options
- ABB – ACH580 Manuals and BACnet Documentation
- BACnet Committee – Addenda and Command Priority Clarifications
Disclaimer: This article provides general commercial building-automation information. Always follow manufacturer documentation, approved site procedures, cybersecurity requirements, and applicable electrical or life-safety practices.