| Table of Contents |
|---|
Update Bacnet Cur from Description
We made a tool called Update Bacnet Cur from Description that can update point instances if a custom application is being used that is different from the original. This is unique to the DXR devices where the point instances can change depending on application type.
What this does is it looks for the "realDescription" tag on the points in the db (its a copy of the "description" tag. all we did was duplicate it and called it realDescription) and reads the description. Then it goes and finds the device that point is coming from and tries to find the record with the same description. If it is found, it updates the points instance cur and/or write instances depending on what it is. If no matching description is found, then it won't update it since it doesn't exist in the device.
...
First, the user would go to the Connectors tree in DB Builder and select the BACnet root or the bacnet connector itself.
...
Once selected, the user can click on the gear icon to open up the tools.
...
The tools pop up will appear once selected. The user would then select Update Bacnet Cur from Description.
...
Before - we randomly changed the bacnetCur instance and saved it
...
After - since the description was found, it updated the instance
...
Another use case would be that on one device a point instance can be AV100, where that same point on another device is instance AV200. Since the description matches, the user can run this tool and get the correct updated instance depending on the device its coming from.Thats it, now the user will have an updated database with the correct point instances
Once done, you user can also disable and enable the connector if needed for the point status to update if they don't update automatically. Sometimes it can take a little while or needs a push to update them.