Slow Response from BACNet Devices

[JoelHaggar]

Did you look through your logs to see if there are any errors?
How many total BACnet Data Points do you have?
What is the Polling rate of the Data Source?
Are they all BACnet MSTP?

Often with BACnet it will use up your High Priority Thread Pool and you'll see an error in the logs about this. I would recommend increasing the thread pool on the system setting page to 1000 or to as many data points as you have.

We have also seen better performance when you have all your data points under one data source rather than a separate data source for each device.

[zdabbas]

Hi Joel

No errors when the devices stop responding. As I said Mango seems to think that the devices are responding I did however noticed that when you turn on / off relay a couple of times it sort of starts turning on and off erratically after a long delay.
As for the thread pool I got the error a while back and I increased it to 1000.
I have 12 devices each with 21 data points and all the data points are in the same data source.
The pooling period is 1 second.

[zdabbas]

OK here is something new, I'm getting this error alot:

Lights_Fire': Data source with xid: DS_Lights_FireCom3 and name: Lights_Fire, aborted 12 polls.

and the number keeps increasing...

any thoughts?

[JoelHaggar]

That means the polls are not completing before the next poll is scheduled to start. I would look at your metrics page like this:

[zdabbas]

I have no idea where to find this matrix..

having said that I increased the timeout on the Bacnet serial configuration and it seems to have solved it. I did find a mis-configuration on the devices and I solved it the delays are still there but a little lower now. I'm getting between 5 - 10 seconds delay between action and physical reaction.

I still think that you should go into the server and see if I made any mistakes that is causing this problem.

also the problem of device discovery still exists, the only way I can do discover is to put a Johnson controller on the serial network. I think it's a problem with devices they need to get the serial configuration from Mango, and Mango is not giving them that.

[JoelHaggar]

You find that on the page when you edit a Data Source. I can't comment on the other issue you describe as I have no way of knowing what is going on there.

[zdabbas]

this is what I got

as for the other problem, it was suppose to fixed with the Bacnet module upgrade. but it wasn't>.

[zdabbas]

Joel

OK since my last post this is what I did.

I checked all the devices for termination and made sure that all of them have no termination except the first and the last.

I changed the USB->RS485 dongle and placed it on a different USB port that doesn't have any devices connected to it.

the result is that the delay has dropped to 4-9 secs for response. (Still a bit long)
the pooling error has Stopped
the problem with the devices being seen by mango but not responding has stooped.

discovery is still an issue. ( I really need help with that since I need to put a $1000 controller to see the devices)

I need help with the delay.

[zdabbas]

Dear Joel

since my last post I did some experimenting and I discovered that the delay is actually from Mango.

what I did was I have a DGBox that I had before, I disconnected Mango from the Bacnet MS/TP network and connected the DGBox, I also Disconnected the Johnson controller. the DGBox discovred the devices quickly, I added the devices and the speed was amazing, as soon as you turn on a datapoint it happens instantly.

any thoughts on that.

[JoelHaggar]

We will do some testing on our side and see if we can reproduce something similar. It would be helpful if you could get a serial capture of when the network is slow and when it is fast so we can compare the differences.