Troubleshooting PI BACnet Connector Integration with Siemens PX Systems

Integrating building automation systems with data historians can sometimes throw up unexpected challenges, especially when working with different vendors and protocols. In this post, we’ll examine a real-world scenario: connecting a Siemens PX system via BACnet/IP to the OSIsoft PI System using the PI BACnet Connector—and what to do when the connection doesn’t work as expected.

Understanding the Integration Challenge

A newcomer to PI systems reported difficulty in connecting a Siemens PX device through the PI BACnet Connector, even though the device was visible and accessible via Kepware’s BACnet/IP driver and other tools like YABE. Notably, network firewalls were ruled out as a cause.

Other users echoed similar experiences: while Kepware and third-party BACnet browsers could successfully discover and communicate with the BACnet device behind the Siemens PX, the PI BACnet Connector failed to establish a connection.

Key Troubleshooting Steps

1. Verify Network Accessibility

• Ping/Test Connectivity: Ensure both the PI Connector node and the Siemens PX are visible to each other on the network.
• Wireshark BACnet Broadcasts: Use a protocol analyzer (e.g. Wireshark) to confirm BACnet broadcasts and responses are present and look for differences between Kepware and PI Connector attempts.

2. Compare BACnet Device Discovery

• Global vs Local Broadcast: Some BACnet devices or systems only respond to certain broadcast messages, or use different mechanisms for device discovery. Check the PI Connector logs and compare them to Kepware’s connection logs.

3. Review Connector Configuration

• Connector Settings: Ensure the PI BACnet Connector is configured for correct BACnet/IP network interface, device instance, and port. Some Siemens PX drivers may use custom ports or non-standard discovery.
• Device Instance ID Matching: Double-check device identifiers and network configuration in both the PI Connector and the Siemens PX setup.

4. Confirm Protocol Compatibility

• Protocol Implementations: Vendors sometimes implement BACnet/IP in ways that are subtly incompatible. For example, proprietary addressing methods or device isolation features on the PX Gateway might prevent direct access by generic BACnet clients (like the PI Connector), but not vendor-specific clients or OPC drivers.

5. Leverage Third-Party Solutions

If direct connection isn’t possible, a third-party OPC server (like Kepware) can bridge the communication between BACnet devices and the PI System. This method was successfully employed by users in the scenario, illustrating its practical value when facing interoperability issues.

Lessons Learned

• Not all BACnet/IP implementations are equal: Device vendors sometimes create custom variations that external connectors can’t interpret directly.
• Third-party protocol servers (e.g., Kepware) can act as middleware, translating between non-standard BACnet implementations and the PI Connector.
• Community forums and user experiences are invaluable when troubleshooting integrations across complex system boundaries.

Resources

• Kepware BACnet/IP Driver
• OSIsoft PI BACnet Connector Documentation
• YABE (Yet Another BACnet Explorer)

Final Thoughts

If you’re struggling to connect the PI BACnet Connector to a Siemens PX—or any BACnet/IP device—start by methodically checking network access, BACnet configuration, protocol compatibility, and consult your vendor’s documentation. If all else fails, integrating your PI System via an OPC server like Kepware can often resolve the issue and get your data flowing.

Do you have similar experiences or additional tips? Share them in the comments below!