My BACNet connection won't stay Initialized

Ignition
1

I’ve configured a simple BACNet connection between my Gateway server (with a Local Device) and a PLC with BACNet enabled and settings configured. I’ve been able to achieve “Initialized” status and have been able to receive the Object List but, as soon as I start interacting with the tags, I receive Bad Status flags and start to lose the connection. Then my device goes back to “Uninitialized” and the connection starts cycling endlessly as it tries to Initialize but fails. I used Wireshark to verify not only that there is communication between devices but also that they are communicating data sporadically.

I’m not experienced with BACNet/IP so I realize this may be a problem bigger than the Ignition settings themselves but I don’t see how I can better understand what is going wrong.

2

I know this is late to this thread, but there are few other posts about this same issue and I will give you my observation as well. So I have many Tstats across our site that are connecting to Ignition. I have found a few of them I get a stable connection and I am able to pull information from the Quick Client page on the gateway. Now when I get to the Designer and start bringing in the datapoints I get nothing but Bad Status flags. I have found out with the OEM of the tstats the firmware version is the root cause that it doesn’t communicate with BacNet with Ignition properly.

So in short - Are you able to check/update the firmware of your BacNet device?