VRF Controls + BMS Integration — DIII-NET + M-NET + H-LINK + BACnet/Modbus Gateway Matrix

A 200-IDU office VRF deployment swings ₹2.5-5.1 lakh in BMS-gateway capex depending on brand choice (Samsung ₹2.48 lakh vs Carrier ₹5.10 lakh). Each brand runs a proprietary refrigerant-control protocol (Mitsubishi M-NET, Daikin DIII-NET, LG PI485, etc.) and exposes it to BMS via vendor-specific gateways at 32-64 IDU per gateway. Three architecture errors Indian projects keep making: over-specifying BACnet at 60-80 points/IDU (Modbus 16 points covers FM needs at -40 % cost), mixing brands without FieldServer-class neutral gateways, losing refrigerant-circuit fault-code visibility because BACnet maps only a subset.

VRF control architecture — why the protocol matters

VRF systems run proprietary refrigerant-control protocols at the outdoor + indoor unit level (Mitsubishi M-NET, Daikin DIII-NET, Toshiba TCC-Link, Hitachi H-LINK II, LG PI485, Samsung F4/F2, Carrier RGW, Blue Star VRF-NET). Building integration with BMS uses gateway translation to BACnet/IP, Modbus TCP, or KNX. Picking the right architecture decides cost, flexibility, and FM-team friction for 15+ years.

VRF brand integration matrix — 6 brands × BMS protocols

Three control-architecture mistakes Indian projects keep making

1. BACnet vs Modbus over-spec — most VRF gateways expose 60-80 points per IDU on BACnet (set/return/mode/fan/comp Hz/EXV%/heat-recovery state). FM uses 6-8 of them. Modbus TCP at 16 points/IDU is enough, costs 40 % less, and reduces BMS database churn.
2. Cross-brand integration — mixing brands needs vendor-neutral gateways (e.g., FieldServer ProtoNode). Hard-wiring proprietary cables across brands fails. Either single-brand or BACnet-only integration in tender.
3. Loss of refrigerant-circuit fault data — proprietary protocols carry rich fault codes (E1-E45 type errors, compressor current, EXV step, oil-return alarms). BACnet gateways only expose a subset. Specify which fault registers must be mapped — or lose predictive maintenance value.