Easy BACnet- Home
- BACnet points lists
- Veeder-Root
- TLS console system points (QuickServer gateway)
Fuel tank monitoring console via BACnet gateway · BACnet points list
Veeder-Root TLS console system points (QuickServer gateway) BACnet points list
Updated 7 November 2026Unofficial source
The QuickServer reads a TLS console over its serial V-R interface and serves BACnet IP or BACnet MS/TP. The system-wide points are fixed: 29 Binary Inputs for console alarms and warnings (printer, battery, self-test, clock, poll timeout, database and similar) and 3 Analog Inputs that report alarms from unknown device types. Tank, sensor and input points are added per device with numbers that depend on the node ID.
This page lists 32 BACnet objects for the Veeder-Root TLS console system points (QuickServer gateway) — 0 of them writable — with each object’s type, instance number, name, engineering units and access. It is re-typed from a copy of Veeder-Root’s documentation hosted by Global Fueling Systems (distributor), not by Veeder-Root itself, so treat it as unofficial.
- Manufacturer
- Veeder-Root
- Model
- TLS console system points (QuickServer gateway)
- Equipment
- Fuel tank monitoring console via BACnet gateway
- Equipment type
- Other equipment
- BACnet objects
- 32 (0 writable)
- Transport
- BACnet IP, BACnet MS/TP
- Firmware
- Not stated
- Default device instance
- 50000
- Also known as
- TLS-450PLUS BACnet, TLS4 BACnet, TLS-350 BACnet, 577014-367, Veeder-Root QuickServer
- Source document
- QuickServer Industrial Protocol Gateway Startup Guide · 577014-367 · rev. Revision D (unofficial copy, hosted by Global Fueling Systems (distributor))
Reference only, provided as-is: verify against Veeder-Root’s current documentation and the live device before use. Not official Veeder-Root information. Terms of use.
BMS integration notes: Veeder-Root TLS console system points (QuickServer gateway)
Set the console's serial port to 9600 baud, odd parity, 7 data bits, 1 stop bit, add a profile per tank or sensor (node IDs sequential from 1, address = the console's tank or sensor number), then read the system and per-device alarm points.
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.
| Object | Name | Why | Access |
|---|---|---|---|
| BI 18 | System Device Poll Timeout | Console lost contact with a polled device | Read |
| BI 16 | System Self Test Error | Console self-test error | Read |
| BI 4 | Battery Off | Console battery off | Read |
| BI 12 | Protective Cover Alarm | Protective cover alarm | Read |
| BI 21 | Database Error | Console database error | Read |
| AI 2 | Unknown Alarm Category | Alarm category from an unknown device | Read |
Network setup
- Console port settings: V-R interface, 9600 baud, odd parity, 7 data bits, 1 stop bit.
- Bac_device_id defaults to 50,000 (range 1-4,194,303); set it in the QuickServer web configurator.
- Node IDs must start at 1 and run in sequence; the node ID becomes the leading digits of that device's object instances, and the profile's address must match the tank, sensor or input number in the console.
Watch out for
- Tank and sensor points use X001-style instances where X is the node ID; build them per site from the guide's tables.
Veeder-Root TLS console system points (QuickServer gateway) 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.
| Description | States | |||||
|---|---|---|---|---|---|---|
| BI | 1 | Printer out of Paper | Read | |||
| BI | 2 | Printer Error | Read | |||
| BI | 3 | EEPROM Configuration Error | Read | |||
| BImin | 4 | Battery Off | Read | |||
| BI | 5 | Too Many Tanks | Read | |||
| BI | 6 | System Security Warning | Read | |||
| BI | 7 | ROM Revision Warning | Read | |||
| BI | 8 | Remote Display Communications Error | Read | |||
| BI | 9 | Autodial Error | Read | |||
| BI | 10 | Software Module Warning | Read | |||
| BI | 11 | Tank Test Shutdown Warning | Read | |||
| BImin | 12 | Protective Cover Alarm | Read | |||
| BI | 13 | BIR Shift Close Pending | Read | |||
| BI | 14 | BIR Daily Close Pending | Read | |||
| BI | 15 | PC(H8) Revision Warning | Read | |||
| BImin | 16 | System Self Test Error | Read | |||
| BI | 17 | System Clock Incorrect Warning | Read | |||
| BImin | 18 | System Device Poll Timeout | Read | |||
| BI | 19 | Maintenance Tracker NVMem | Read | |||
| BI | 20 | Maintenance Tracker Communication Module | Read | |||
| BImin | 21 | Database Error | Read | |||
| BI | 22 | File System Error | Read | |||
| BI | 23 | BIR Status Warning | Read | |||
| BI | 24 | VR Bus Power Outage Warning | Read | |||
| BI | 25 | Software Upgrade Failure Alarm | Read | |||
| BI | 26 | iButton Fault Warning | Read | |||
| BI | 27 | iButton Fault Alarm | Read | |||
| BI | 28 | Version Upgrade Available | Read | |||
| BI | 29 | Expansion Box Unsupported | Read | |||
| AI | 1 | Unknown Device Address | Unidentified device alarm data | Read | ||
| AImin | 2 | Unknown Alarm Category | Unidentified device alarm data | Read | ||
| AI | 3 | Unknown Alarm Type | Unidentified device alarm data | Read |
No points match these filters.
Object ID lookup: Veeder-Root TLS console system points point IDs by name
BI1Printer out of PaperBI2Printer ErrorBI3EEPROM Configuration ErrorBI4Battery OffBI5Too Many TanksBI6System Security WarningBI7ROM Revision WarningBI8Remote Display Communications ErrorBI9Autodial ErrorBI10Software Module WarningBI11Tank Test Shutdown WarningBI12Protective Cover AlarmBI13BIR Shift Close PendingBI14BIR Daily Close PendingBI15PC(H8) Revision WarningBI16System Self Test ErrorBI17System Clock Incorrect WarningBI18System Device Poll TimeoutBI19Maintenance Tracker NVMemBI20Maintenance Tracker Communication ModuleBI21Database ErrorBI22File System ErrorBI23BIR Status WarningBI24VR Bus Power Outage WarningBI25Software Upgrade Failure AlarmBI26iButton Fault WarningBI27iButton Fault AlarmBI28Version Upgrade AvailableBI29Expansion Box UnsupportedAI1Unknown Device AddressAI2Unknown Alarm CategoryAI3Unknown Alarm Type
Integration notes
- Only the fixed system (Table B-1) and unknown-type (Table B-2) points are listed here; they need no profile.
- Tanks, liquid/vapor/groundwater/Type A/Type B/MAG/smart sensors, inputs and PLLD lines are added as profiles. Their instances are printed as X001, X002 ..., where X is the device's node ID (e.g. node 3, point 2 = 3002), so they are not listed.
- The guide gives no access or state text; access is inferred (inputs are read-only).
- BI names are alarm/warning conditions; the guide does not print state texts.
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 TLS console system points (QuickServer gateway) 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 Veeder-Root TLS console system points (QuickServer gateway)
How many BACnet points does the Veeder-Root TLS console system points (QuickServer gateway) have?
This list has 32 BACnet objects: 3 analog inputs, 29 binary inputs. The exact set on a given unit depends on its firmware, installed options and configuration.
Which Veeder-Root TLS console system points (QuickServer gateway) 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 Veeder-Root TLS console system points (QuickServer gateway) BACnet documentation?
Veeder-Root does not publish it on its own website. This list comes from QuickServer Industrial Protocol Gateway Startup Guide (577014-367), revision Revision D, a copy hosted by Global Fueling Systems (distributor) at https://globalfuelingsystems.com/content/577014-367.pdf. Ask Veeder-Root or its representative for the current revision.
What are the minimum BACnet points to integrate the Veeder-Root TLS console system points (QuickServer gateway)?
Start with BI 18 System Device Poll Timeout (Console lost contact with a polled device); BI 16 System Self Test Error (Console self-test error); BI 4 Battery Off (Console battery off); BI 12 Protective Cover Alarm (Protective cover alarm); BI 21 Database Error (Console database error); AI 2 Unknown Alarm Category (Alarm category from an unknown device).
How do I check these points on the real TLS console system points (QuickServer gateway)?
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.
Source: QuickServer Industrial Protocol Gateway Startup Guide · 577014-367 · rev. Revision D. Object names, instances and units are reproduced as published; descriptions are our own.