How to bring a Vertiv Liebert cooling unit with the iCOM controller onto a BMS over BACnet: the IntelliSlot Unity card that does the talking, the write-access switch that blocks every write until you enable it, BACnet/IP or MS/TP, the data map the card builds for your unit, object names that are data IDs, a relinquish that changes nothing — and two writes a second at most. With a free BACManager workspace for a data-centre room.
Sources: Vertiv IntelliSlot Unity card guide SL-52645 REV11, BACnet PICS SL-52647 and SL-70399, Liebert IntelliSlot reference guide SL-28170 REV9 (iCOM v4 object tables)
In Vertiv's documents BACnet comes from an IntelliSlot card in the unit. The IS-Unity-DP has an Ethernet port for BACnet/IP and an RS-485 port for BACnet MS/TP, Modbus RTU or YDN23. The IS-Unity-SNMP has Ethernet only. Older units used the IS-IPBML web card (BACnet/IP). The iCOM “High Definition” display has its own PICS describing the same Unity BACnet implementation.
A Unity card runs at most two protocols at once, and only one kind of BACnet: IP or MS/TP. Only one protocol may use the RS-485 port, so MS/TP and Modbus RTU cannot share it. The card's own Velocity Protocol also uses UDP 47808.
ReadProperty, ReadPropertyMultiple, WriteProperty, WritePropertyMultiple, SubscribeCOV (COV_Increment writable, default 0.5), dynamic device and object binding, and time synchronisation. No segmentation. No alarm and event services, no schedules, no Trend Logs. The PICS state BTL testing.
You do all of this in the card's web interface. The card takes an address from DHCP by default; with no DHCP server, connect a PC directly and use the link-local address in Vertiv's guide. Change the factory user names and passwords first, as Vertiv recommends.
| Setting | Default | Set to |
|---|---|---|
| Protocols: BACnet | off | Ticked, and no more than one other protocol |
| Managed Device Write Access | not stated | Enabled (read/write) if the BMS is to write anything. It decides whether the BACnet server may write to the unit at all |
| BACnet Interface | — | BACnet IP or BACnet MSTP |
| Device Object Instance Number | not stated | 0–4194302, unique in the building |
| Device Object Name | card default | A unique name, e.g. the unit tag |
| APDU Timeout / Retries | 3000 ms / 3 | Usually leave |
| BACnet IP: Port Number | 47808 | The site's BACnet port |
| BACnet IP: Register as Foreign Device, BBMD, Time-to-Live | — | Only when the card sits on another subnet than the BMS |
| BACnet MSTP: Node ID | 1 | 0–127, unique on the RS-485 trunk |
| BACnet MSTP: Data Rate, Max Master, Max Info Frames | not stated | The trunk's baud rate; Max Master at least the highest MAC on the trunk |
Save, then restart the card: Communications tab → Support → Enable → Restart. For MS/TP the Unity-DP takes the RS-485 trunk on its RJ-45 “485” port through Vertiv's adapter cable with a terminal block (see the guide for the colours). The card discovers the unit behind it and creates the BACnet objects itself. The Device object stands for the card, not for the cooling unit.
Vertiv's PICS: Present_Value can be written on outputs, and on value objects whose data point in the unit is writable. Those objects carry a priority array.
| Object | Object name | Access | What it does |
|---|---|---|---|
| MSV115 | 5143_1 | RW | System On/Off Control: 1 Off, 2 On |
| AV20 | 5331_1_1 | RW | Supply Air Temperature Set Point |
| AV32 | 5333_1_1 | RW | Return Air Temperature Set Point (the air at the unit's inlet) |
| AV1 / AV2 / AV3 | 5008_1 / 5325_1 / 5011_1 | RW | Air Temperature Set Point, Proportional Band, Dead Band |
| AV61 / AV62 | 5029_1 / 5339_1 | RW | Humidity Set Point; Return Humidity Set Point |
| AV211 | 5050_1 | RW | Fan Speed Maximum Set Point |
| AV268 | 5075_1 | RW | BMS Timeout Period: the time within which the BMS must talk to the unit |
| MSV12 / MSV23 / MSV82 | 5324_1 / 5332_1_1 / 5373_1 | RW | Air Temperature Control Type; Supply Air Temperature Sensor Control (Disabled, Limit, Control, Temp Only); Fan Control Mode |
With Managed Device Write Access not enabled on the card, the BACnet server does not write to the unit. Check this before you look for anything else when writes go nowhere.
Some BMSs resend the same setpoint over and over. Vertiv asks for no more than two writes per second on average, so the unit can catch up after a burst. If you use BACManager's per-tag “Refresh (s)” re-write, keep its interval long.
On these objects Relinquish_Default always equals Present_Value. Writing NULL to every priority therefore leaves the last value in place. To hand a setpoint back, write the value you want, not NULL. BACManager writes at priority 8 unless you choose another; Vertiv names no priority.
The card builds its object list from the unit it finds. Download it from the Managed Device tab → Summary → Downloads → BACnetDataMap.txt. The only published table is SL-28170 from 2012, for iCOM v4. Treat its instances as a starting point and check them against your map.
In SL-28170 the Object_Name is a numeric data ID such as 5002_1_1 (Supply Air Temperature), and the readable text is the data description. A BMS that imports by name gets a column of numbers, so label the points from the map.
The map has three temperature setpoints: Air Temperature Set Point (AV1), supply (AV20) and return (AV32). Which one the iCOM controls to depends on how the unit is set up, for example Supply Air Temperature Sensor Control (MSV23). SL-28170 does not explain it, so check the unit's configuration before writing.
From SL-28170 REV9 Tables 69–71 (Liebert iCOM v4 on Challenger 3000/ITR, CW, Deluxe System/3, DS, HPM, PeX). RW = read/write, RD = read only. The table gives no units. Multistate values count from 1.
| Object | Object name | Access | Data description |
|---|---|---|---|
| AV19 / AV31 | 5002_1_1 / 4291_1_1 | RD | Supply Air Temperature (outlet); Return Air Temperature (inlet) |
| AV60 | 5028_1 | RD | Return Humidity |
| AV45–47 / AV82–84 | 4594_1_1… / 4595_1_1… | RD | Ext Air Sensor A, B, C temperature / humidity |
| AV33 / AV34, AV66 / AV67 | 5022_1_1 / 5334_1_1, 5033_1 / 5035_1 | RW | Return air over/under temperature and high/low humidity thresholds |
| AV280 / AV281 | 5077_1 / 5078_1 | RD | Fan Speed, % of maximum rated speed; Compressor Utilization, % of rated capacity |
| AV282 / AV124 | 5379_1 / 5358_1 | RD | Free Cooling Valve Open Position; Free Cooling Fluid Temperature |
| AV286–289 | 5380_1, 5080_1, 5081_1, 5079_1 | RD | Hot water / hot gas valve position; reheat, humidifier, dehumidifier utilization |
| AV97 / AV110 / AV212 | 5267_1_1 / 5267_1_2 / 5374_1 | RW | Compressor 1 and 2 hours; fan hours |
| MSV93 | 4123_1 | RD | System Status: Normal Operation, StartUp, Normal with Warning, Normal with Alarm, Abnormal Operation |
| MSV94 / MSV95 / MSV96 | 4706_1 / 4707_1 / 5074_1 | RD | System Operating State (Off, On, Standby); Control Mode (Internal/External); Operating State Reason |
| MSV45 / MSV57 | 5264_1_1 / 5264_1_2 | RD | Compressor 1 / 2 State, Off/On |
| MSV107–114 | 5381_1 … 5388_1 | RD | Fan, Cooling, Free Cooling, Maintenance, Hot Water/Hot Gas, Electric Reheat, Dehumidifier, Humidifier state |
| BV1 / BV2, BV14 / BV15 | 5015_1_1 / 5019_1_1, 5023_1_1 / 5335_1_1 | RD | Supply and return air over/under temperature events |
| BV41 / BV42 | 5034_1 / 5036_1 | RD | High / Low Return Humidity |
| BV77–86, BV97–106 | 5269_1_1… | RD | Compressor 1 / 2 events: hours, high head pressure, low suction pressure, short cycle, thermal overload… |
| BV206 / BV207 / BV263 | 5376_1 / 4729_1 / 5053_1 | RD | Main Fan Overload; Fan Issue; Loss of Air Flow |
| BV260 | 5115_1 | RD | BMS Communications Timeout |
| BV262 / BV269 / BV275 | 5118_1 / 4720_1 / 4723_1 | RD | Clogged Air Filter; Smoke Detected; Water Under Floor |
| BV310–314 | 5110_1_1 … 5111_1_1 | RD | Unit Off, Unit On, Unit Partial Shutdown, Unit Shutdown, Unit Standby |
| MSV126 and up | 4718_1… | RW | Event Control (Disabled/Enabled) and Event Type (Message, Warning, Alarm) for each event |
The events arrive as binary values, not as BACnet alarms: the card has no alarm services. Poll them or subscribe with COV. The Event Control objects can disable an event. Vertiv's glossary says a disabled event goes into no active list and no history, so check them before you trust a quiet unit. Liebert SN sensors on the card are not available over BACnet.
One dashboard page for a Liebert DS cooling a computer room: fan state and speed, compressor utilization and states, supply, return and rack-inlet air, return humidity, humidifier, three events, system status and operating state, a trend, and on/off, supply, return and humidity set points as controls.
On the BACnet tab open BACnet/IP (or MS/TP on the PC's RS-485 port) and press Discover. The card appears with its Device Object Instance Number. If it is on another subnet, register with the site's BBMD first.
Workspace → Open. The file reads device 70101; if yours has another instance, BACManager asks which discovered device takes its place and moves every point over. Then compare the instances with your BACnetDataMap.txt.
BACManager starts reading the unit by itself. On the Dashboard press Run to use the controls, which write only in Run mode and only after the unit has answered. Writes need Managed Device Write Access on the card.
| What you see | Why | What to do |
|---|---|---|
| Reads work, every write fails or does nothing | Managed Device Write Access is not enabled | Enable it under Protocols → BACnet, save, restart the card |
| BACnet cannot be ticked | Two protocols are already enabled | Switch one off; a card runs two at most |
| MS/TP silent while Modbus RTU works | Only one protocol may use the RS-485 port | Choose MS/TP or Modbus RTU for the 485 port |
| Instances do not match the published table | The card builds the map for the unit it finds | Download BACnetDataMap.txt from the Managed Device tab |
| Points show up as numbers only | Object names are data IDs | Name the points from the data map's descriptions |
| Relinquished, value stayed | Relinquish_Default equals Present_Value | Write the value you want instead of NULL |
| Unit slow to answer after setpoint bursts | The BMS rewrites setpoints continuously | Two writes per second at most, on average |
| BMS Communications Timeout (BV260) active | No BMS traffic within BMS Timeout Period (AV268) | Poll more often than AV268, or lengthen it |
| A large ReadPropertyMultiple fails | No segmentation | Fewer properties per request (BACManager splits by itself) |
| Card not found from the BMS subnet | Who-Is broadcasts do not cross routers | Register the card as a foreign device with the BBMD |
Vertiv: Liebert IntelliSlot Unity Card Installer/User Guide SL-52645 REV11; BACnet PICS Reference Guide — Liebert IntelliSlot Unity Card IS-UNITY-DP SL-52647 REV1; BACnet PICS Reference Guide — iCOM High Definition SL-70399 REV0; Liebert IntelliSlot Modbus 485, Modbus IP and BACnet IP Reference Guide SL-28170 REV9 (10-12), section 4.2, Tables 69–72. Get the guides from Vertiv and the PICS from BACnet International. The object tables date from 2012 (iCOM v4); current cards generate the map per unit. Default device instance, max APDU, units per object, the iCOM's behaviour after a BMS timeout, and which temperature set point is in control are not stated in these documents. Vertiv, Liebert, iCOM and IntelliSlot are Vertiv names; BACManager is not affiliated with Vertiv. The pictures on this page are from BACManager connected to a simulated unit built from the published tables.
Download the free trial, discover the Unity card and open the iCOM workspace — supply, return, humidity and set points on one page. No credit card.
Windows 10/11 · $149 one-time
We use Google Analytics cookies to see how the site is used. You can accept or decline — declining keeps analytics off.