WAGO PFC200 BACnet/IP

Compatibility

Compatible with EpiSensor Edge over BACnet/IP

Edge’s BACnet/IP client reads the controller’s commissioned objects. The exact BACnet/IP variant documents server-side ReadProperty and ReadPropertyMultiple and readable Device and Object_List properties, so the procedure discovers the installed project’s objects rather than needing a universal point map.

750-8212/000-100 only. Manual V1.1.0 and the July 2019 PICS describe firmware 14 and 13; the April 2026 notes document later BACnet revision 26 support. Site check: read the BACnet Device-ID and UDP port on the WBM page “Configuration of General BACnet” before connecting. Read properties without changing the PLC project or outputs.

Connect it with

• Gateway ZGW-20 From €899 ex VAT Configure
• Evaluation Gateway on a Raspberry Pi Edge with one device licensed Free Set up

Models

Specifications

WAGO identifies 750-8212/000-100 as a PFC200 second-generation controller with two Ethernet ports, RS-232/-485 and BACnet/IP for building and industrial automation.¹

Exact hardware

750-8212/000-100, PFC200 second generation BACnet/IP variant^1, 2

Network interfaces

Two configurable Ethernet ports with integrated switch¹

Serial interface

RS-232/-485; the PLC project assigns its role¹

Engineering runtime

CODESYS V3.5 from firmware release 23; e!COCKPIT up to release 22²

Current BACnet evidence

The April 2026 firmware line lists 750-8212/000-100 and BACnet revision 26 support²

Monitoring starting point

ReadProperty, ReadPropertyMultiple, Device/Object_List and per-object value, unit and status properties^3, 4

Interface

Documented measurements and integration boundaries for PFC200 BACnet/IP.

• Potential temperatures, pressures, flows, energy readings, equipment states and application values depend entirely on the commissioned IEC 61131 and BACnet application.
• Retain each object identifier, name, unit, source I/O or field device and quality. Object_List supplies the installed identifiers; the application determines what each point measures.
• Keep physical I/O, serial field-device data, PLC variables and derived BACnet values distinct so a reader can trace each value to its source.
• Commandable objects, priority-array writes, schedules, PLC variables, parameters, application logic, I/O and equipment outputs remain outside this guide.

Setup

1. Locate the BACnet network and device

   Use the controller’s configured controls-network IP and BACnet UDP port. The manual’s WBM page “Configuration of General BACnet” shows Device-ID under BACnet Status and Port Number under BACnet General Parameter. Read the existing settings. In this manual’s separated Ethernet mode, BACnet uses X1, not X2. Keep the commissioned bridge or separated-port configuration; an external reader does not need a project download, firmware update or reboot.

2. Discover identity and the live point list

   On the same BACnet subnet, use the client’s Who-Is discovery and retain the returned I-Am device instance/address. Read the Device object’s Object_Identifier, Object_Name, Vendor_Name, Model_Name, Firmware_Revision and Protocol_Revision. Read Object_List to enumerate the configured object identifiers; use the client’s paged or smaller reads if a complete response exceeds its APDU/segmentation limits. WAGO’s PICS documents server-side ReadProperty and ReadPropertyMultiple. Object instances come from the project, not the controller order code.

3. Read one value with its unit and quality

   Select an Analog Input from Object_List and read Object_Name, Present_Value, Units, Status_Flags and Out_Of_Service; add Reliability when present. The PICS defines Analog Input Present_Value as REAL. For a synthetic temperature object, Present_Value = 23.4 and Units = degrees-celsius means 23.4 °C, with no Modbus-style scaling. The example is not a factory object or fixed instance number. Compare the named point with the PLC/BMS display and original sensor. Read-only clients may observe output objects too; keep WriteProperty and priority commands disabled.

4. Keep faults and overridden points visible

   Store the timestamp and object identity with the value. Status_Flags distinguish in-alarm, fault, overridden and out-of-service; also inspect Out_Of_Service and optional Reliability. An out-of-service Analog Input may hold a manually assigned value rather than the live sensor. A timeout is unavailable or stale data, not zero. Preserve a last-good value only with its age and quality clearly recorded.

5. Expand discovery without disturbing control

   Group property reads with ReadPropertyMultiple where the client and installed device support it; reduce batch size on oversized replies. The older PICS also documents COV service support, so a capable client can use subscriptions for suitable objects, retaining periodic health checks and renewing them after loss. For routed discovery, use the existing BACnet router/BBMD arrangement rather than changing PLC network settings. The PICS marks BBMD support and a combined BDT/FDT limit of 16 entries; it does not mark the controller itself as a Foreign Device client.

Common questions

Is every PFC200 750-8212 a BACnet/IP controller?

No. WAGO identifies the BACnet/IP variant by the complete order code 750-8212/000-100. The shared 750-8212 stem covers related controller hardware and does not prove the installed BACnet product variant.^1, 2

How do I find the point list without a factory register map?

Discover the BACnet Device object and read Object_List. Then inspect each selected object’s name, Present_Value, Units and quality properties. The controller order code does not assign site temperatures, meters or equipment-state instances; the PLC application does.^3, 4

Can Edge write PLC variables or BACnet setpoints through this guide?

No. This guide releases no commandable object, priority-array write, schedule change, PLC variable, parameter, application-logic change or physical output command.¹