Abstract: A protocol independent programming tool for constructing control logic. The control logic may be constructed without dealing in the details of an underlying protocol. The protocol details may be abstracted and exposed and generic points used in constructing the logic. The tool may automatically map or translate the points used in the logic to protocol specific entities.

Abstract: A priority selection mechanism for driving outputs from control logic which can be automatically translated to controllers of various protocols. The priority selection mechanism may assign a priority to the outputs and select the output having the highest priority as the output of the control logic. There may be an abstract representation of the priority logic which may permit a protocol mechanism to be used in the logic without the designer or user needing to know the details of the mechanism.

Abstract: A graphical approach to setup data sharing between two controllers. Symbols that represent controllers may be placed on a wiresheet. A link may be constructed between the controllers by connecting the symbols with a line drawn between them. The resulting link information may lead to a compile and download of binding tables to the pertinent controller. The designer or user need not setup several levels of mapping by populating multiple tables to effect the binding for a link between the controllers. This binding may be done automatically under a hood without the designer or user needing to be aware of the binding activity. This approach for graphically constructing a link may be particularly applicable to BACnet controllers.

Abstract: A priority selection mechanism for driving outputs from control logic which can be automatically translated to controllers of various protocols. The priority selection mechanism may assign a priority to the outputs and select the output having the highest priority as the output of the control logic. There may be an abstract representation of the priority logic which may permit a protocol mechanism to be used in the logic without the designer or user needing to know the details of the mechanism.

Abstract: A protocol independent programming tool for constructing control logic. The control logic may be constructed without dealing in the details of an underlying protocol. The protocol details may be abstracted and exposed and generic points used in constructing the logic. The tool may automatically map or translate the points used in the logic to protocol specific entities.

Abstract: A graphical approach to setup data sharing between two controllers. Symbols that represent controllers may be placed on a wiresheet. A link may be constructed between the controllers by connecting the symbols with a line drawn between them. The resulting link information may lead to a compile and download of binding tables to the pertinent controller. The designer or user need not setup several levels of mapping by populating multiple tables to effect the binding for a link between the controllers. This binding may be done automatically under a hood without the designer or user needing to be aware of the binding activity. This approach for graphically constructing a link may be particularly applicable to BACnet controllers.