BACnet Initialized but nothing in Object_List

Ignition
1

Forgive me if this has been asked before, I am new to the whole forum thing...

I have just configured a BACnet connection for some RTUs and everything was going fine, until I try to see the Object_List components, as it does not have anything in it. I am wondering if anyone knows anything about how to get those to show up, or any possible troubleshooting ideas that I could try.

Thank you!

2

We'll probably need to look at a Wireshark capture to see why.

3

Hi Kevin,

We're attempting to connect to a Schneider Electric AS-P controller.

I can't recreate the exact errors we were seeing in Wireshark at the moment, but I've seen Unconfirmed-REQ i-Am messages for our devices, as well as buffer overflows.

We can see the objects and data from the AS-P controller as well as the other devices using YABE, shown below:

image
image243×541 7.89 KB

I tried connecting using Kepware's BACnet/IP driver, and while we could see the objects, we could not see their values, and Kepware was showing a segmentation not supported error.

4

Here are the tags from the AS-P controller as well.

{C1071385-93C1-4B7B-8211-00392C6AF3AE}
{C1071385-93C1-4B7B-8211-00392C6AF3AE}414×563 28.8 KB

5

What are you expecting to see under Object_List? Hopefully not all those other devices.

YABE's tree is both a network explorer and device explorer.

Ignition doesn't have any kind of network explorer, and a device connection must be made directly to each device you want to communicate with.

6

I've tried connecting to another device directly, like ID 1110101, but the connection doesn't initialize. This is what I see in Wireshark:

{90661A07-6DDB-4FAF-B8A9-79F4944EA0E7}

7

Not sure what it means when a device responds with Reject / buffer-overflow while reading the Object List property.

BACnet spec only says:

BUFFER_OVERFLOW - A buffer capacity has been exceeded.

Not sure if there's anything that can be done on the Ignition side to influence this.

1 Like
8

Kevin,

Understood, I'll reach out to the manufacturer and see if anything can be done on their side.

Thanks

9

Hi Kevin,

I'm able to see the device objects using YABE, but not from Ignition. The device 1110101, which is behind the BACnet router, doesn't initialize in Ignition.

We have also tried replacing the Schneider AS-P controller with a Contemporary Controls BASrouter. All devices are successfully discovered in YABE and BDT (manufacturer's discovery software), but still not in Ignition. I have also tried changing the discovery timeout but I see buffer overflow responses after Ignition's BACnet driver requests object-list from the device.