Article - CS431513
Added Support to provide non-error response to Object Identifier, Object Name, System Status, and Vendor Identifier in BACnet/IP Driver of PTC Kepware Products
Modified: 18-Nov-2024
Applies To
- Kepware Server (formerly KEPServerEX) 6.0.2107.0 to 6.17
- ThingWorx Kepware Server (legacy) 8.0 to 6.17
Description
- The BACnet/IP Driver is being used to connect to Siemens controllers on a building automation network
- The BACnet controllers are not sending data to KEPServerEX at the expected frequency
- It appears that repeated "Who-Is, I-Am" queries are being sent between the controller and KEPServerEX
- The BACnet device keeps asking for a list of services that the KEPServerEX can support and in response KEPServerEX says "I'm this device" but doesn't acknowledge all of it's abilities
- This seems to break the next function of RPM (Read Property Multiple)
- Siemens has investigated this on their side and does not believe this to be a Siemens issue
- No error messages are appearing in KEPServerEX. A "who-is" log from the BACnet device is available upon request
- Missing Property Values: The original request (from Siemens) asked for multiple properties (protocol-services-supported, object-identifier, object-name, system-status, vendor-identifier)
- This "I-Am" response (from Kepware) only provides the vendor ID
- The other properties may be provided in separate messages or may not be supported by this device
- Cannot get COV subscription working using the BACNet/IP driver when connecting to a Siemens PXC100-E96.A
- We are able to "Not Use COV' and we do get data when we set a polling rate, however we wanted to use COV to ensure we didn't miss quick transitions on digital tags
- Using wireshark to do a packet capture when attempting to get COV to work, we see Kepware request the subscription, the controller sends an acknowledgement of the request, and the controller immediately sends the first data point
- We then get no more data point updates until the "resubscription" occurs
This is a printer-friendly version of Article 431513 and may be out of date. For the latest version click CS431513