MAngoES Bacnet resolved issues question
Hi, I have a question about resolved issues in the bacnet stack. I have several MangoES on a site using bacnet to read data. I currently have three devices which read four different sources. This has happened numerous times over the last year, and now it has happened again, where the mango simply stops being able to read data from the other device. Restarting the datasource, or even making a change and saving it, resolves the issue. Are there any issues which have been resolved in the last six months which sound like this?
I know I'm providing no info and I'm sorry but this is a real problem.
terrypacker last edited by
Yes, the latest release 3.5.1 of the BacNet module will likely fix this issue if any of your data sources shared a local device and you were using COV subscriptions.
Two of my Mangos are on V2 and updated to the latest version already. Could I get some help to on writing a script which would restart the bacnet datasource programatically please? I found a post referencing this
var dsxid = 'DS_Modbus'; //Change to your data source's XID RuntimeManager.disableDataSource(dsxid); RuntimeManager.enableDataSource(dsxid);
Would that be the best way?
I will backport the fix for the COV.
Yes that is a valid way to restart a data source from within a scripting environment with adequate permissions. I would recommend using a scripting data source to check if the points haven't updated instead of an event detector on the points on the data source. Otherwise you may see your data source cycle on and off a few times once the event triggers, because it will likely trigger again when the data source resumes.
You could see if BACnet 2.3.1 solves the issue.
Excellent thanks Phil, I'll try to get to site in the next two weeks and load that onto the v2 units.
FYI at least on 2.3.1 the bacnet driver failed again, just stopped reading data, required a restart of the DS and off it goes again.
EDIT: It's two units on the same network in two different buildings but both stopped recording on the same day, March 12. Nothing in ma.log out of the ordinary.
Did all points stop or only the COV points?