In this option, a string point per connector would be created. They can be organized under a single equip or nested under their respective equip. It would have a reference to the respective connector so that the status of the connector can be retrieved.

Create new equip to organize the points. We named ours “Connector Status.”

Create a new string point configured as writable and has allowProgram and connStatusPoint marker tags.

We make it writable so that the program can write to it, and the user can view the status, trend it, and use it on a graphic, etc.

allowProgram will allow the point to be used in Logic Builder and allow the program to run on the point level otherwise, it would throw an error that it can't run on the point level.

connStatusPoint is just a unique tag to ensure the program only runs on these connector status points. You can choose to use something else.

On the point, add a property ref tag called connRef and paste the connector's ID to grab the status from. Omit the “id==” portion and save it.

connRef is just a unique tag and can be anything.
It should look something like this:

 

Then create the program that runs on the point(s). Below is an example of how it would look like. We are running the program on point and connStatusPoint. Then just hit create.

 

Then once the program editor is open. On the right menu go to “Add Variables" → “Tag”. The below popup will appear and set it up the same way.

The tag name connStatus is the tag on the connector that we are looking for.

The On field would be set to “Target Ref” because we are looking for connStatus from a property ref tag found on the point. The point is the target and it has a ref. Hence we added "connRef" property tag on the point.

Data type is set to string because the connStatus tag is of a string type.

Is would be read only because we are just reading the value from the connStatus.

 

Then in the next popup, the variable name can be chosen for that tag (camelCase). In our case, we’ll leave it as is and Ref name would be the connRef.

 

Then create a new variable that will be used to write to the curVal of the string point. Should be like below.

Tag name = curVal

On = Target

Data type = String

Is = read/write/create

 

The variable name we can leave as is or change it (camelCase).

 

That's it, the variables is now ready to be used in the logic. 

 

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 "connStatusProgramPoint".

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.

connStatusProgramPoint.z…

 

 

  Any Connector version. The program is called "connStatusProgramPoint". Runs on "point and allowProgram and connStatusPoint".

connStatusProgramPointAl…