The goal is just to have a reference of a connector in the database so that it can be visible as an alarm somewhere on the hierarchy tree. It doesn't matter if it's 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({connRef: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 a floor or equip level. |
First, the user will select an equip they would like to use to get the connector status from. It can be any equip. Then add a connRef property tag to it like below (unless the query above was used).
Then create a program that runs on that equip only or if you have multiple equips for multiple connectors, then run it on those. When creating the program, don't select any points, all you need to do is select "Tags" because we will be using a tag from the connRef property tag that was added. Should look something like below when creating the program. We did it based on "equip and connRef" because we only have one.
Because "Tags" option was selected, the user will be prompted with the below pop up to add additional tags based on available refs on the equip. Since we added 'connRef', it will appear in the drop down for the user to select from. Once selected, the user will see available tags from the connector they can use. In this case, we want the connector status, so we'll select "connStatus" tag and finish creating the program.
From there, the user will now have the variable available to use in logic program. It can be something like if the status is not "ok", then set a boolean variable to true and use that for the alarm etc.
Below are screenshots of the program logic that the user can replicate. As well as a copy if they prefer to upload our examples. The example includes a “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".
BACnet version if needed.
The reason we used to check if it's not ‘ok' and ‘down' is because when it’s down, it doesn't necessarily mean that is bad. It just means that there is nothing keeping it in watch so it’s 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 recommend to add the second "Any Connector" version. |
Any Connector version. The program is called "connStatusProgramEquip". Runs on "(equip or site) and connRef".
