Home › Technical articles

Đọc bằng tiếng Việt

Bringing AHUs and air compressors into an FMCS SCADA: BACnet/IP, Modbus, gateways and KEPServerEX

TDL Industrial Automation · Last updated:

From PTC's Kepware driver help and AVEVA's Application Server 2026 documentation: the three routes from packaged units into an FMCS SCADA, BACnet objects, properties and command priority, Modbus register maps, zero-based addressing and word order, gateways and converters, timeouts and the _Error tag, OPCClient, templates, Bad value alarms and timestamps.

An FMCS SCADA can only show what each packaged unit tells it. Air handling units, outdoor air units, chillers, air compressors and meters arrive with their own controllers, and each reaches the central SCADA by BACnet, by Modbus (serial or TCP), or through signals wired to a PLC. This article follows those routes as PTC documents the Kepware BACnet/IP and Modbus drivers, and as AVEVA documents the System Platform side. What an FMCS is, and how it differs from a BMS: What is FMCS.

Three routes from the unit to the SCADA

TDL's SEHC projects use all three. Admin Building AHU and OAC data come in through BACnet/IP to Modbus TCP gateways and KEPServerEX; a new air compressor through a Modbus RTU to Modbus TCP converter and KEPServerEX; on the VD5 rooftop, an AHU, two OAC units and five exhaust fans now run on a CompactLogix controller that the SCADA reads through KEPServerEX. PTC's help centre now calls the server Kepware Server and lists the KEPServerEX help as legacy.

Protocol Physical layer How a point is addressed What the documentation says to watch
BACnet/IP Ethernet, UDP; default port 47808 (0xBAC0) object type, instance and property, such as AnalogValue.100.PresentValue, in a device identified by network number and device instance where routers block broadcasts, discovery needs a BBMD on each subnet; COV-updated tags can stay Good while the device is offline
BACnet MS/TP serial RS-485, master-slave and token passing (ABB) the same objects, through a BACnet gateway or router; the MS/TP MAC address is one octet Kepware takes the MAC as a hex string; a gateway's web page may show it in decimal
Modbus RTU serial COM port; PTC's notes cover RS-485 converters and two-wire RS-485 station ID, then a register address such as 400001 echoes on two-wire RS-485; longer timeouts below 9600 baud; at most 32 devices per serial channel recommended without amplification
Modbus TCP Ethernet, TCP port 502 by default IP address and Modbus server ID (0 to 255), then the register address one-based or zero-based addressing, word order of 32-bit values, block size
Three routes from packaged units into the FMCS SCADATop row: three groups of equipment. A is BACnet/IP equipment such as AHU and OAC units; B is equipment with a Modbus RTU port on RS-485, such as air compressors and meters; C is hardwired signals from AHU, OAC units and exhaust fans. Second row: A goes through a BACnet/IP to Modbus TCP gateway or straight to the BACnet/IP driver; B through a Modbus RTU to Modbus TCP converter; C into a CompactLogix or ControlLogix PLC and onto EtherNet/IP. All three reach the KEPServerEX driver layer (channels and devices, timeouts, auto-demotion, _Error system tags), then over OPC DA, OPC UA or SuiteLink reach AVEVA System Platform (OPCClient object, one template per unit type, Bad value alarms) and the historian (storage by exception, deadband, source timestamps in UTC), and finally the central control room with graphics, alarms, trends and automated reports.Three routes from packaged units into the FMCS SCADAA · BACnet unitsAHU and OAC units withBACnet/IPB · Modbus RTU unitsair compressors, meters,RS-485 portC · Hardwired unitsAHU, OAC and exhaustfan signalsBACnet/IPModbus RTUhardwired I/OGatewayBACnet/IP to Modbus TCP, orstraight to the BACnet/IP driverConverterModbus RTU to Modbus TCPPLCCompactLogix or ControlLogixModbus TCP or BACnet/IPModbus TCPEtherNet/IPKEPServerEX · driver layerchannels and devices, timeouts, auto-demotion, _Error system tagsOPC DA · OPC UA · SuiteLinkAVEVA System PlatformOPCClient object, one template per unit type,Bad value alarmsHistorianstorage by exception, value deadband, sourcetimestamps in UTCCentral control roomgraphics, alarms, trends, automated reportsBased on PTC, Kepware Drivers help (BACnet/IP, Modbus) and Kepware Server help; AVEVA, Application Server2026 and OMI 2026 documentation; ABB, AC500 BACnet-BC help; TDL's SEHC project pages (read15 November 2026). Figure: drawn by TDL.
Figure 1: Three routes from packaged units into the FMCS SCADA. On a phone, swipe sideways to see the whole figure.

BACnet: objects, properties and command priority

The Kepware BACnet/IP driver speaks BACnet/IP as defined in Annex J of ANSI/ASHRAE 135. An address has three parts: object type, object instance (0 to 4194303) and property. Object types include Analog Input, Analog Value, Binary Output, Multi-State Value, Schedule and Trend Log. For an analog input the useful properties are PresentValue, StatusFlags (Fault, InAlarm, OutOfService, Overridden), Reliability and Units. Enumerated properties such as Units arrive as integers.

A device ID is written as network number and device instance, such as "1.100". By default the driver finds the device's IP address with a Who-Is/I-Am exchange, or the address can be entered by hand. Where routers block broadcasts between subnets, a BACnet Broadcast Management Device (BBMD) is needed on each subnet.

Writes need care. The present value of objects such as Analog Output, Binary Output and Multi-State Value is commandable: it is written with a priority from 1 (highest) to 16, and the driver's default is 8, which the BACnet specification associates with Manual Operator. Once the SCADA has written, writes from other applications at a lower priority are not executed until the SCADA relinquishes the point. Kepware provides RELINQUISH and PRIORITY address modifiers for this.

For speed, PTC recommends ReadPropertyMultiple where the device's PICS (Protocol Implementation Conformance Statement) lists it, the largest APDU length the path allows, and several channels, because one slow device delays every device on its channel. Change of Value (COV) subscriptions reduce polling, and the driver falls back to polling if a subscription fails.

Modbus: the register map is the contract

A Modbus device does not describe its own data, so the supplier's register map defines every point. In the Kepware Modbus drivers, the first digit selects the table: 0 output coils, 1 input coils, 3 internal registers, 4 holding registers; 40001 and 400001 are the same register. Holding registers are read with function code 03 and written with 06 or 16. Three settings decide whether a value is right:

  • Zero-based addressing. By default the driver subtracts one from the address entered, as Modicon PLCs do. If the supplier's map already counts from zero, disable it.
  • Word order. A Float or 32-bit integer uses two consecutive registers, first word low by default. If the device sends the high word first, change the setting.
  • Block size. 1 to 120 registers per request, 32 by default. A block that spans undefined addresses may be rejected, and by default the driver stops polling a block that returns exception 2 (illegal address) or 3 (illegal data).

Values can be scaled in the server (linear or square root, with optional clamping) or by the I/O scaling of System Platform. Scale each point in one place only. How Ignition, Kepware, AVEVA and N3uron write the same Modbus address is compared in Modbus RTU and TCP register maps for SCADA.

Gateways and converters

For a Modbus TCP device, Kepware's device ID is the host address plus a Modbus server ID from 0 to 255; PTC's example uses it to reach a device behind a Modbus Ethernet bridge, and it is 0 when no bridge is used. Serial drivers, the Modbus RTU Serial driver among them, can also use Ethernet Encapsulation through a terminal server that converts TCP/IP messages to serial data.

A BACnet gateway can forward Who-Is messages to MS/TP and other non-IP networks; the driver then needs the device's BACnet MAC. The driver reads each device's maximum APDU length but does not detect the limits of gateways and routers in between, so a smaller value may be needed.

Polling, timeouts and comm-loss alarms

Each Kepware device has a Connect Timeout (1 to 30 s, typically 3 s by default), a Request Timeout (usually 1,000 ms) and Attempts Before Timeout (typically 3). After a full cycle of timeouts and retries the device is in error: its _Error system tag turns True, the tag's timestamp marks the last failed operation, and _SecondsInError gives the length of the outage. With Auto-Demotion, after three failed cycles by default the device is taken off scan for 10,000 ms and its read data turns Bad.

PTC notes that COV-updated tags can keep Good quality while a device is briefly offline, because only a failed poll sets the device error state. Polling one extra property per device gives a watchdog for its COV data.

On the SCADA side: OPCClient, templates, history and time

AVEVA's Application Server 2026 documentation says the OPCClient object should be used instead of legacy Data Integration (DI) objects. Each OPCClient instance connects to one OPC communications driver that supports OPC Data Access 2.05 or later, which Kepware Server provides alongside OPC UA and SuiteLink. Points sit in scan groups with an update interval and are referenced as object.scangroup.item. After the configured maximum number of reconnection attempts, the OPCClient raises a restart alarm and stops retrying. OPC DA across computers depends on DCOM: OPC DA and DCOM errors.

An attribute read through the I/O feature turns Bad when reads fail on a communication error, and a Bad value alarm (priority 1 to 999) on it tells the operator. Alarm priorities and floods: ISA-18.2.

Templates hold the configuration shared by many instances; instances are deployed, templates are not. One derived template per unit type, such as AHU, OAC or air compressor, keeps every unit alike, and attributes locked in a template cannot be changed in its instances.

History is stored by exception, with a value deadband and an optional force storage period for values that rarely change. Values normally carry the source timestamp, propagated in UTC, but after an intermittent network disconnect the first value of a slowly changing attribute takes the AppEngine's timestamp. PTC adds that device timestamps may be UTC or local time. More on historians: what is a process historian; on choosing the AVEVA platform: InTouch HMI or System Platform.

What we check first

This is TDL's practice, not a PTC or AVEVA requirement.

  • We get each unit's register map, or its BACnet PICS and object list, with units and scaling, before cabling is planned.
  • We read one point of known value per data type on the bench, to settle zero-based addressing, word order and the server ID behind a converter.
  • We ask who else writes to each BACnet commandable point, such as a BMS, and agree the priority the SCADA uses.
  • We give slow devices their own channels, and every device a comm-loss alarm from _Error or a Bad value alarm, with a polled watchdog where COV is used.
  • We build one template per unit type before the first instance, and decide where scaling is done.
  • We check that servers, gateways and controllers share one time source, and keep gateways inside the FMCS zones and conduits: IEC 62443.

FMCS integration work at SEHC

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem and a System Integrator in the Rockwell Automation PartnerNetwork. Our project pages for Samsung Electronics HCMC CE Complex (SEHC) describe:

The services: facility monitoring (FMCS) and connecting existing equipment to SCADA.

Frequently asked questions

Can KEPServerEX read BACnet MS/TP devices?

Through a gateway. The BACnet/IP driver speaks BACnet/IP only, but it can reach MS/TP devices behind a BACnet gateway or router once the device's BACnet MAC address is entered as a hex string.

Why are all my Modbus values shifted by one register?

The driver subtracts one from each address by default, following the Modicon convention. If the supplier's register map already counts from zero, disable zero-based addressing in the device settings.

Which setting decides how a Modbus float is read?

First Word Low. A Float uses two consecutive registers and the driver takes the first one as the low word by default; if the device sends the high word first, that setting must be changed.

How does the SCADA know a unit has stopped communicating?

In Kepware, the device's _Error system tag turns True after the timeouts and retries fail. In System Platform, attributes read through the I/O feature go Bad, and a Bad value alarm can alert the operator.

Do COV-updated BACnet tags show Bad quality when a device goes offline?

Not always. PTC notes they can stay Good during a short outage, and recommends polling one extra property per device as a watchdog.

Sources

Read 15 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Facility and utility monitoring (FMCS) Connecting existing equipment to SCADA