Easy BACnet
  1. Home
  2. BACnet points lists
  3. Vertiv
  4. Liebert Liqui-tect LP6000 leak detection

Leak detection controller (water sensor cable) · BACnet points list

Vertiv Liebert Liqui-tect LP6000 leak detection BACnet points list

Updated 6 November 2026

Short answer

The Liebert Liqui-tect LP6000 leak detection reports leak, cable-break and contamination alarms plus leak location and leakage current for the cable and each zone through a Liebert IntelliSlot card. The guide prints no object names for this panel.

This page lists 27 BACnet objects for the Vertiv Liebert Liqui-tect LP6000 leak detection — 0 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from Vertiv’s own free documentation, linked below.

Manufacturer
Vertiv
Model
Liebert Liqui-tect LP6000 leak detection
Equipment
Leak detection controller (water sensor cable)
Equipment type
Thermostats, sensors & meters
BACnet objects
27 (0 writable)
Transport
BACnet IP, BACnet MS/TP
Firmware
Not stated
Also known as
LP6000, Liqui-tect LP6000, SL-28170
Source document
Liebert IntelliSlot Modbus/BACnet Reference Guide (Modbus RTU and TCP, BACnet MSTP and IP) · SL-28170 · rev. 2024-04 (Rev 29)
Download CSV 27 rows Download EDE B.I.G.-EU JSON Manufacturer PDF ↗ Compare with your scan Download Easy BACnet Mobile App Google Play

Reference only, provided as-is: verify against Vertiv’s current documentation and the live device before use. Not official Vertiv information. Terms of use.

BMS integration notes: Vertiv Liebert Liqui-tect LP6000 leak detection

Integration in brief

Fit a Liebert IntelliSlot BACnet card (the guide's compatibility table names no card for this panel), give it a unique device instance and let it discover the equipment; the objects are then created automatically. Map the status, main measurements and event objects for monitoring.

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.

ObjectNameWhyAccess
BI 1Leak AlarmLeak detectedRead
AI 1Location of LeakDistance to the leak along the cableRead
BI 2Cable Break AlarmSensor cable breakRead
MV 1Virtual Zone # in AlarmWhich zone is in alarmRead

Network setup

Watch out for

Vertiv Liebert Liqui-tect LP6000 leak detection 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.

27 of 27 shown
Type
BinaryMulti-stateOther
Show
Vertiv Liebert Liqui-tect LP6000 leak detection BACnet Points List
DescriptionStates
BImin1Leak AlarmRead
AImin1Location of LeakRead
MVmin1Virtual Zone # in AlarmShown on BACnet IP onlyRead
BImin2Cable Break AlarmRead
AI2Leakage Current on CableRead
BI3Contamination AlarmRead
AI3Length of CableRead
BI4Unit of MeasureReadtrue = ft false = meters
AV1Virtual Zone # in AlarmRead
TL2Trend-log Leakage CurrentReadma 0.xxx
TL3Trend-log Leakage CurrentReadua xxx
BI201Zone 2 EnabledRead
AI201Zone 2 Location of LeakRead
BI202Zone 2 Leak DetectedRead
AI202Zone 2 Leakage CurrentRead
BI203Zone 2 Cable BreakRead
AI203Zone 2 Length of CableRead
BI204Zone 2 ContaminationRead
BI205Zone 2 Comm LossRead
BI12801Zone 128 EnabledRead
AI12801Zone 128 Location of LeakRead
BI12802Zone 128 Leak DetectedRead
AI12802Zone 128 Leakage CurrentRead
BI12803Zone 128 Cable BreakRead
AI12803Zone 128 Length of CableRead
BI12804Zone 128 ContaminationRead
BI12805Zone 128 Comm LossRead
Object ID lookup: Vertiv Liebert Liqui-tect LP6000 leak detection point IDs by name

Integration notes

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 Liebert Liqui-tect LP6000 leak detection 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 Vertiv Liebert Liqui-tect LP6000 leak detection

How many BACnet points does the Vertiv Liebert Liqui-tect LP6000 leak detection have?

This list has 27 BACnet objects: 9 analog inputs, 1 analog value, 14 binary inputs, 1 multi-state value, 2 trend logs. The exact set on a given unit depends on its firmware, installed options and configuration.

Which Vertiv Liebert Liqui-tect LP6000 leak detection BACnet points are writable?

None of the listed objects are marked writable in the source documentation. The source has no read/write column, so this is inferred from object type.

Where is the official Vertiv Liebert Liqui-tect LP6000 leak detection BACnet documentation?

The source is Liebert IntelliSlot Modbus/BACnet Reference Guide (Modbus RTU and TCP, BACnet MSTP and IP) (SL-28170), revision 2024-04 (Rev 29), published free by Vertiv at https://www.vertiv.com/49fb41/globalassets/shared/liebert-intellislot-modbus-rtu-reference-guide-SL-28170_0.pdf.

What are the minimum BACnet points to integrate the Vertiv Liebert Liqui-tect LP6000 leak detection?

Start with BI 1 Leak Alarm (Leak detected); AI 1 Location of Leak (Distance to the leak along the cable); BI 2 Cable Break Alarm (Sensor cable break); MV 1 Virtual Zone # in Alarm (Which zone is in alarm).

How do I check these points on the real Liebert Liqui-tect LP6000 leak detection?

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 Vertiv BACnet points lists

Source: Liebert IntelliSlot Modbus/BACnet Reference Guide (Modbus RTU and TCP, BACnet MSTP and IP) · SL-28170 · rev. 2024-04 (Rev 29). Object names, instances and units are reproduced as published; descriptions are our own.