A useful VFD communication matrix must distinguish drive family, manufacturer, protocol, and how the interface is implemented. Do not combine onboard interfaces and optional communication modules in one undifferentiated protocol list.
Define the Comparison Scope
Use drive families rather than an unrestricted list of every model found. Define the inclusion rule before collecting data—for example, include only families for which manufacturer documentation identifies both the supported protocol and the required interface type. Record unverified claims separately instead of presenting them as confirmed capabilities.
Use a Traceable Table Structure
| Drive family | Manufacturer | Protocol | Interface type | Verification status |
|---|---|---|---|---|
| Vacon NXL, NXS, NXP, NXC | Vacon | Profibus DP; Profinet; Modbus RTU; Modbus TCP; N2; BACNet; BACNet/IP; LonWorks; CAN; DeviceNet | Not identified in the available evidence | Verify against manufacturer documentation for each family |
| Unspecified Lenze drive | Lenze | CAN Open | Onboard | Drive model is not identified |
| Unspecified Lenze drive | Lenze | Profibus DP; DeviceNet | Bridge module | Module and drive models are not identified |
The Lenze evidence also mentions AIF II, but it does not establish whether that term is a protocol, interface, or module designation. Keep it in a notes field until product documentation resolves the classification.
Separate Protocol Support from Implementation
A protocol name alone is insufficient for engineering selection. For each row, determine whether communication is onboard or requires a bridge module, then capture the exact compatible drive and module identifiers when documentation provides them. The available evidence explicitly distinguishes onboard CAN Open from bridge-module access to Profibus DP and DeviceNet for an unspecified Lenze product.
Do not infer that every listed Vacon protocol applies identically to all four named families. The evidence provides a combined family and protocol list but no family-by-family mapping or interface details; verify those relationships before marking individual combinations as supported.
Verify Protocol Documentation
- Open the drive family documentation and confirm the protocol name and supported model.
- Identify whether the interface is onboard or supplied by an additional module.
- For frame-level analysis, obtain the relevant protocol specification and the drive manufacturer's communication manual; the available evidence does not provide verifiable frame definitions for Profibus DP or LonWorks.
- Record the document title or identifier and revision in the table so each entry can be audited.
Do not copy a protocol list into a frame-format study. A drive capability matrix answers which interfaces are available, while protocol and product communication manuals define the exchanged data and implementation details.
FAQ
Which communication protocols are listed for Vacon drives?
The evidence lists Profibus DP, Profinet, Modbus RTU, Modbus TCP, N2, BACNet, BACNet/IP, LonWorks, CAN, and DeviceNet for Vacon NXL, NXS, NXP, and NXC. Verify the exact protocol-to-family mapping in manufacturer documentation.
Should onboard and optional VFD protocols be in separate columns?
Yes. Add an interface-type column that distinguishes onboard communication from a bridge module, because the required hardware affects selection and compatibility.
Does the available evidence define Profibus DP or LonWorks frames?
No. It names both protocols but supplies no verifiable frame structure, document revision, or usable official documentation link.
