WAGO PFC200 BACnet/IP

Building automation controller

WAGO identifies 750-8212/000-100 as the second-generation PFC200 with two Ethernet ports, RS-232/-485 and BACnet/IP. The product is programmed with CODESYS V3.5 from firmware release 23, while WAGO's 2026 release notes list this exact order code and BACnet revision 26 support in the current firmware line. These sources establish product identity and controller capability, but do not publish the commissioned BACnet server object schedule, object access rules, application version or a direct Edge pairing. Monitoring remains unverified and all PLC, I/O, setpoint and output writes are excluded.

  • BACnet/IP
  • RS-485

Building automation controller

Compatibility

Direct Edge integration not yet verified

WAGO publishes the exact BACnet/IP order code and current BACnet firmware support. The retained public sources do not define the commissioned application's BACnet device instance, object identifiers, read permissions, quality behavior or polling limits, and do not prove an installed Edge client path.

750-8212/000-100 only. Record the order code, hardware revision, firmware, CODESYS project, application checksum and BACnet configuration. Obtain the exported BACnet object schedule and matching PICS or application documentation from the controls owner. Use only an approved read-only object allowlist. Do not write PLC variables, commandable BACnet objects, priorities, schedules, parameters, I/O or equipment outputs.

Models

Download
ModelsInterfaceRoute into Edge
750-8212/000-100PFC200 second generation with two configurable Ethernet ports, integrated switch, RS-232/-485 and the BACnet/IP product variant.Hold a direct route until firmware, application identity, BACnet device and object export, permissions and Edge client support are proven.
750-8212 without /000-100PFC200 second-generation controller with two Ethernet ports and serial interface, but the base order code does not establish the BACnet/IP variant.Do not infer BACnet/IP from the shared 750-8212 stem. Confirm the full order code.
Other PFC100, PFC200 and PFC300 variantsSeparate controllers with different Ethernet, serial, CAN, cellular, temperature and runtime combinations.Use the exact WAGO order code and its own current firmware documentation.

Specifications

The product page states CODESYS V3.5 programming from firmware release 23 and e!COCKPIT support through release 22. Firmware and project identity therefore belong in every integration record.1

Exact hardware
750-8212/000-100, PFC200 second generation BACnet/IP variant12
Network interfaces
Two configurable Ethernet ports with integrated switch1
Serial interface
RS-232/-485; its project role is not established by the BACnet/IP product name1
Engineering runtime
CODESYS V3.5 from firmware release 23; e!COCKPIT up to release 221
Current BACnet evidence
The April 2026 firmware line lists 750-8212/000-100 and BACnet revision 26 support2
Evidence gap
No commissioned device instance, object schedule, object permissions, quality contract, polling limit or verified Edge pairing12

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 device and object identifiers, type, unit, source I/O or field device, update behavior, reliability or status and commandability for every approved observation.
  • 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.

Assessment

Exact 750-8212/000-100 after hardware, firmware, CODESYS project, application checksum, BACnet export and Edge client support are confirmed; no released path or control.

InteroperabilityLimited
WAGO publishes the exact BACnet/IP variant and current BACnet firmware support, but the project-specific device, object and access contract remains absent.12
AccuracyNot yet assessed
The modular I/O and PLC application can expose many value types, but source accuracy, unit, scale and quality depend on the installed module, field device and application mapping.1
SecurityNot yet assessed
The retained public sources do not establish an authenticated or encrypted BACnet client path, application permissions or the site's network policy.12
ReliabilityNot yet assessed
Current firmware maintenance is visible, but polling limits, object-update timing, stale-value behavior and restart semantics for an external client are not published here.2
RuggednessNot yet assessed
The product page identifies industrial and building-automation use, but this retained evidence set does not record the complete environmental and enclosure ratings.1
ScalabilityNot yet assessed
The controller accepts modular WAGO I/O, but the public evidence here does not define an external BACnet object count, polling budget or concurrent-client limit for the commissioned application.1
LifecycleWell supported
WAGO lists the exact order code in its current product catalogue and April 2026 firmware release notes, including an updated BACnet implementation.12

Setup

  1. Confirm the complete WAGO identity

    Record 750-8212/000-100, hardware revision, serial number, firmware release, runtime, CODESYS project version and application checksum. The base 750-8212 order code is not equivalent evidence for the BACnet/IP variant.

  2. Obtain the application object contract

    Request the project's PICS and BACnet export from the controls owner. Retain device and object identifiers, types, units, source I/O or field device, update behavior, quality and commandability.

  3. Approve a read-only network path

    Use the approved controls VLAN and an explicit non-commandable object allowlist. Confirm the installed Edge build's BACnet/IP client separately. Do not expose the PLC web or engineering interfaces to the public internet.

  4. Compare a bounded point set

    Compare selected objects with the CODESYS or BMS view and the original sensor, meter or field device. Test stale data, PLC restart and communications loss without changing the controller application or outputs.

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.12
Does BACnet revision 26 support provide a ready point list?
No. It describes firmware capability. The CODESYS application and BACnet configuration determine the device instance, object identifiers, values, units, access and quality behavior for a particular project.12
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.1

Sources

  1. PFC200 BACnet/IP controller 750-8212/000-100 product page (opens in a new tab) WAGO
  2. Controller PFC100/200 second generation and PFC300 release notes (opens in a new tab) (PDF) WAGO

Further reading

Product names and trademarks belong to their owners. Publication does not imply endorsement or a commercial relationship.