...
One option is to add connector ref on the equip. The second option would be to create a string point that will have the connector ref. Both options will be covered below.
ConnStatus via Equip or Site
| Info |
|---|
The goal is just to have a reference of a connector in the db so that it can be visible as an alarm somewhere on the hierarchy. So it doesn't matter if its on a site, floor, or equip. Also, only one reference per connector is needed otherwise, there will be multiple alarms of the same connector. BACNET: To do the below automatically for bacnet connectors since in most cases, each connector is usually one equip. Run this query in folio: readAll(point and bacnetConnRef).each x=> readById(x->equipRef).diff({connStatusRef:x->bacnetConnRef}).commit() In cases where a bacnet connector is being used by multiple equips, go through those and remove the extra ones so that you don't get multiple alarms for the same thing. HAYSTACK: For haystack connectors, you can add them to the site instead of equip because in most cases, its for an entire site. If, there are multiple for a single site, then it would be best to add them on the equip level. |
First, the user will select an equip they would like to use to get the connector ref. It can be any equip. Then add a connRef property tag to it like below. Then drag the connector to that property to assign it to it.
...
Below is a copy of the program the user can upload that contains the logic and alarms setup. Also added the dis variable so that the users will be able to know which connector it is in case they have multiple of them. The program is called "connStatusProgramEquip". Also added couple screenshots in case you would like to create it yourself.
BACNET version if wanted.
| Tip |
|---|
The reason we used to check if its not 'ok' and 'down' is because when its down, it doesn't necessarily mean that is bad. Its just means that there is nothing keeping it in watch so its asleep until viewing the data by opening equip or graphic, or having points historized from that connector etc. |
...
This is only for Bacnet connectors. If you have a database with bacnet and/or haystack connectors, we recommened to add the second "Any Connector" version. |
| View file | ||||
|---|---|---|---|---|
|
Any Connector version. The program is called "connStatusProgramEquip". Runs on "(equip or site) and connRef".
| View file | ||||
|---|---|---|---|---|
|
ConnStatus via Custom Point
With this version, we recommend to create a new equip that will contain newly creating virtual string points, which in turn those will have the connRef instead of on the equip. So create a new equip and string point. Add a "connRef" property tag on the point like below and drag the connector to that property to assign to it. Make sure to also tag it as "allowProgram" and "connStatusPoint". What 'allowProgram' does is it will allow the point to be used in logic builder, otherwise you won't be able to use it. 'connStatusPoint' is just a generic tag to make sure the program only runs on these connector status points. IF you would also like to see the value of being the status of the connector on the point, then make sure the point is writable as well so that the program can write to it. It should look like something below before creating the point.
...
Below is a copy of the program the user can upload that contains the logic and alarms setup. Also added the dis variable so that the users will be able to know which connector it is in case they have multiple of them. As well as curVal so that we can write to the point. The The program is called "connStatusProgramPoint". Also added couple screenshots in case you would like to create it yourself.
BACNET version if wanted.
| Tip |
|---|
The reason we used to check if its not 'ok' and 'down' is because when its down, it doesn't necessarily mean that is bad. Its just means that there is nothing keeping it in watch so its asleep until viewing the data by opening equip or graphic, or having points historized from that connector etc. |
...
This is only for Bacnet connectors. If you have a database with bacnet and/or haystack connectors, we recommened to add the second "Any Connector" version. |
| View file | ||||
|---|---|---|---|---|
|
Any Connector version. The program is called "connStatusProgramPoint". Runs on "point and allowProgram and connStatusPoint".
| View file | ||||
|---|---|---|---|---|
|
Haystack Device Status
...