Patent Description:
Building control systems are used to control systems of a building, and often include one or more building control devices that control one or more building control components. Such building control systems can include Heating, Ventilation and/or Air Conditioning (HVAC) systems, building security systems, building lighting control systems and/or any other suitable building control system. In many instances, a building control system includes a building controller that receives sensor and/or other data, and in response, provides control signals to control various building control components in the building in accordance with a control algorithm. In some cases, the building controller may be operatively coupled to one or more input/output modules, which may be wired or otherwise connected to the one or more building control components. In some cases, a user interface may be integrated into the building controller. In other cases, a separate user interface module may be provided for interfacing with the building controller. A need remains for improved the usability of such building control systems.

Examples of currently used systems can be found in the following: <CIT>, which discloses a local thermostat for controlling an HVAC unit may include a controller programmed to execute a remote access function for remotely accessing and communicating with at least one remote thermostat over a communication channel. The remote access application may be configured to display at least one thermostat setting of at least one of the remote thermostats on the display of the user interface of the local thermostat. In some cases, the remote access application may allow a user to change one or more thermostat settings of at least one remote thermostat using the user interface of the local thermostat.

<CIT>, which discloses an intelligent-thermostat-controlled environmental-conditioning system in which computational tasks and subcomponents with associated intelligent-thermostat functionalities are distributed to one or more of concealed and visible portions of one or more intelligent thermostats and, in certain implementations, to one or more intermediate boxes. The intelligent thermostats are interconnected to intermediate boxes by wired and/or wireless interfaces and intelligent thermostats intercommunicate with one another by wireless communications. Wireless communications include communications through a local router and an ISP, <NUM> and <NUM> wireless communications through a mobile service provider. Components of the intelligent-thermostat-controlled environmental-conditioning system may also be connected by wireless communications to remote computing facilities.

<CIT>, which discloses a navigation approach having a data filtering and sorting for a user interface with a small screen display. The user interface may be used with a building control system. The sorting may be accomplished with a single button filter/sort key which when clicked opens up a floating window containing various sorting options. The single button takes little screen real estate but provides a user the flexibility to arrange data in such a way that results in high speed of access and productivity.

The present disclosure relates to a building control system according to independent claim <NUM>. In some cases, the building controller is configured to be wall mountable and includes a plurality of ports for controlling one or more points that are associated with one or more plants of a building. The building controller controls the one or more points in accordance with one or more programmable point control values that are associated with one or more points. The user interface device may be configured to provide a user interface for operating the building controller and may be configured to display a plurality of menu screens on a display that allow a user to view one or more of the points, change the programmable control value for one or more of the points, and/or view one or more alarms generated by the building controller for one or more of the points.

An unclaimed example is a building control system that includes a building controller that is configured to be wall mountable and a user interface device that is separate from the building controller but is also configured to be wall mountable and operatively coupled to the building controller. The building controller includes a plurality of ports for controlling one or more points that are associated with one or more plants of a building. The building controller controls the one or more points in accordance with one or more programmable point control values that are associated with the one or more points. The user interface device is configured to provide a user interface for operating the building controller and is configured to display one or more screens on a display that displays information received from the building controller and/or solicits information for the building controller.

Another unclaimed example is a building control system that includes a building controller that is configured to be wall mountable and includes a plurality of ports for controlling one or more points associated with one or more plants of a building, the building controller controlling the one or more points in accordance with one or more programmable point control values that are associated with the one or more points. A user interface device is operatively coupled to the building controller and is configured to provide a user interface for operating the building controller. The user interface device is configured to display a plurality of menu screens on a display, including at least one screen that allows a user to select one or more points that are to be displayed on a home screen of the user interface device, wherein after selection, the user interface device displays current information regarding the selected one or more points on the home screen, wherein the home screen is displayed following a period of no user interaction with the user interface device.

The preceding summary is provided to facilitate an understanding of some of the features of the present disclosure and is not intended to be a full description. A full appreciation of the disclosure can be gained by taking the entire specification, claims, drawings, and abstract as a whole.

The disclosure may be more completely understood in consideration of the following description of various illustrative embodiments of the disclosure in connection with the accompanying drawings, in which:.

The following description should be read with reference to the drawings wherein like reference numerals indicate like elements. The drawings, which are not necessarily to scale, are not intended to limit the scope of the disclosure. In some of the figures, elements not believed necessary to an understanding of relationships among illustrated components may have been omitted for clarity.

It is noted that references in the specification to "an embodiment", "some embodiments", "other embodiments", etc., indicate that the embodiment described may include a particular feature, structure, or characteristic, but every embodiment may not necessarily include the particular feature, structure, or characteristic. Further, when a particular feature, structure, or characteristic is described in connection with an embodiment, it is contemplated that the feature, structure, or characteristic may be applied to other embodiments whether or not explicitly described unless clearly stated to the contrary.

<FIG> is a schematic view of an illustrative building control system <NUM>. It is contemplated that the building control system <NUM> may include an Heating, Ventilation and/or Air Conditioning (HVAC) system, a building security system, a building lighting control system and/or any other suitable building control system. Wherein the building control system <NUM> includes one or more building control devices. The one or more building control devices may include, for example, a building controller <NUM>, input/output modules <NUM> and <NUM>, and/or any other suitable building control device. In the example shown, the building controller <NUM> is configured to receive sensor and/or other data, and in response, provide control signals in accordance with a control algorithm to control various building control components 18a-18d in the building. In some cases, the building controller <NUM> may receive the sensor and/or other data and provided control signals to building control components 18a-18d via one or more input/output modules <NUM> and <NUM>. When so provided, the one or more input/output modules <NUM> and <NUM> may be operatively connected to the building controller <NUM> and wired or otherwise connected to the one or more building control components 18a-18d. It is contemplated that the one or more building control components 18a-18d may include, for example, fans, blowers, dampers, sensors and/or detectors, actuators and/or any other suitable building control components.

A user interface device <NUM> is provided for interfacing with the building control devices. In the example shown, the user interface device <NUM> is operatively connected to the building controller <NUM>. The user interface device <NUM> may include a housing that houses a display. The display may be a touch screen display. In some cases, the user interface device <NUM> may include one or more tactile buttons for use by the user in interacting with the user interface device <NUM>.

It is contemplated that the user interface device <NUM> may provide a rich user interface for local access to the building controller <NUM>, thereby providing a convenient way for a user to locally control/check the operation of the building control system <NUM>. In some cases, a user may user the user interface module to view and command building control components 18a-18d (points), view and acknowledge alarms, view and program schedules/calendars, provide password protection, displaying/creating fast access lists, and/or perform any other desired task. These are just examples.

<FIG> is a schematic view of an illustrative building control system <NUM> mounted on a DIN rail <NUM>. Wherein the claimed building control system includes a building controller <NUM> and a user interface device <NUM>. In the example shown, the building controller <NUM> does not include a dot matrix display. Instead, the building controller <NUM> includes a light ring <NUM> that, for example, can be animated and/or changes color to provide an operational status of the building controller <NUM>. For example, the light ring <NUM> may be green to indicate that the building controller <NUM> is operating normally, yellow to indicate that the building controller <NUM> has one or more minor faults and red to indicate that the building controller <NUM> has one or more major faults that need a user's immediate attention. A set of LED lights <NUM> may also be used to indicate the connection status of each of a number of I/O pins. In some cases, the user interface device <NUM> may serve as a user interface for the building controller <NUM>, thereby providing additional functionality. In some cases, the user interface device <NUM> may display a replica of the light ring <NUM>.

<FIG> is a schematic view of an illustrative building control system <NUM>. The building control system <NUM> includes the building controller <NUM> and the user interface device <NUM> as previously shown in <FIG>. The building controller <NUM> and the user interface device <NUM> may be operably coupled such that the user interface device <NUM> provides a user interface for the building controller <NUM>, thereby providing additional communication functionality beyond the light ring <NUM> and the LED lights <NUM> (<FIG>). In some cases, the user interface device <NUM> may be separate from the building controller <NUM> (yet still operably coupled thereto). In some cases, the building control system <NUM> may be considered as being part of the building control system <NUM>. In some instances, the building control system <NUM> may be considered as being a stand-alone system.

As illustrated, the building controller <NUM> includes a controller <NUM> that is operably coupled with a memory <NUM>. The memory <NUM> may store information regarding one or more points that are associated with one or more plants that are being controlled by the building controller <NUM>, including but not limited to programmable control values, alarm values and the like. The controller <NUM> is also operably coupled with a plurality of ports 46a, 46b, 46c and 46d. While a total of four ports <NUM> are shown, it will be appreciated that the controller <NUM> may be operably coupled with any number of ports <NUM>. In some cases, the ports <NUM> may provide direct wired or wireless communication to the one or more points. In some instances, at least some of the ports <NUM> may instead be in communication with other intermediate devices such as but not limited to the Input/Output Modules <NUM> and <NUM> as shown in <FIG>. An I/O port <NUM> permits communication with the user interface device <NUM>.

The user interface device <NUM> includes a controller <NUM> that is operably coupled with a user interface <NUM>. In some cases, the user interface <NUM> includes a display <NUM> and may include one or more buttons or other input devices (not illustrated). In some cases, the display <NUM> may be a capacitive touch screen display, which may provide both input and display capabilities. The controller <NUM> is also operably coupled with an I/O port <NUM>. The I/O port <NUM> may, for example, permit the user interface device <NUM> to communicate with the building controller <NUM>, such as via the I/O port <NUM> of the building controller <NUM>. The user interface device <NUM> may be configured to display a plurality of menu screens on the display <NUM> that allow a user to view one or more of the points, change the programmable control value for one or more of the points, and view one or more alarms generated by the building controller <NUM> for one or more of the points.

In some cases, the user interface device <NUM> may be configured to display on the display <NUM> one or more screens that display a list of points that are currently in alarm. For example, the one or more screens that display a list of points that are currently in alarm may include one or more of a user-defined name for each of the points in alarm, a status indicator for each of the points in alarm and a current value and/or a setpoint for each of the points in alarm. The status indicator for each of the points in alarm may, for example, be one of a high priority alarm indicator, a mid or medium priority alarm indicator and a low priority alarm indicator. In some cases, the user interface device <NUM> may be configured to display one or more screens providing additional information regarding a particular point that is currently in alarm in response to a user selecting the particular point from the list of points that are currently in alarm. In some cases, the one or more screens providing additional information regarding the particular point that is currently in alarm may allow the user to manually change a setpoint for the particular point in alarm.

The user interface device <NUM> may be configured to display on the display one or more screens that display a list of points that are controlled by the building controller <NUM>. In some cases, the user interface device <NUM> may be configured to display one or more screens providing additional information regarding a particular point in response to a user selecting the particular point from the list of points. The user interface device <NUM> may be configured to display one or more screens that permit the user to select a particular point and then manually adjust a programmable point control value of the particular point. The user interface device <NUM> may be configured to display one or more screens that provide a list of points that have been manually adjusted as well as to display one or more screens that permit the user to selectively choose points that have been manually adjusted to return to an auto mode.

The user interface device <NUM> may be configured to display one or more screens that permit the user to filter the one or more points by a user selected filter criteria. In some cases, each of the one or more points has a point type, and wherein the user selected filter criteria identifies those points of one or more selected point types. In some instances, each of the one or more points is associated one of the one or more plants, and wherein the user selected filter criteria identifies those points that are associated with one or more selected plants.

The user interface device <NUM> may be configured to display one or more screens that provide a Fast Access List that enables particular points to be accessed more easily. One or more points may be added to the Fast Access List in several different ways. For example, a point may be added to the Fast Access List by activating an add to Fast Access List button on a Fast Access List screen that displays a listing of points that are on the Fast Access List. A point may also be added to the Fast Access List by activating an add to Fast Access List button on an information screen for a particular point. In some cases, in response to activating the add to Fast Access List button on the Fast Access List screen that displays the listing of points that are on the Fast Access List, the user interface device <NUM> may be configured to display one or more screens that permit the user to filter the one or more points by a user selected filter criteria.

<FIG> provide a number of illustrative screen shots that illustrate some of the functionality of the user interface device <NUM>, and how the user interface device <NUM> may provide a desirable and useful user interface for the building controller <NUM>. As will be shown in the illustrative screen shots, the user interface device <NUM> provides a way for the building controller <NUM> to communicate vast amounts of information to a user via a user-friendly, inexpensive device (the user interface device <NUM>). The user interface device <NUM> also provides an effective way for a user to communicate information to the building controller <NUM> without having to connect up a computer or similar device.

<FIG> provides a screen <NUM> that may be displayed by the user interface device <NUM>. The screen <NUM> may be considered as being a lock screen to which the user interface device <NUM> may return when there is no current interaction with a user, for example, and there has not been any interaction for a period of time. For security purposes, the user interface device <NUM> may display the screen <NUM> if there has been no interaction for a period of time such as <NUM> minutes. In some cases, this period of time may be user-adjustable. The screen <NUM> may include any desired information. As illustrated, the screen <NUM> includes a current DATE and TIME icon <NUM> and a CONTROLLER NAME icon <NUM>. In some cases, and as will be discussed with respect to subsequent Figures, the user may have the ability to place one or more points directly on the screen <NUM>. As a result, particular points may be immediately visible, even without having to unlock the screen. To illustrate this, the screen <NUM> includes a DATA POINT icon <NUM> that may include a name of the displayed point as well as a current setpoint or current value for the displayed point. While a single DATA POINT icon <NUM> is shown, it will be appreciated that the screen <NUM> may include none, or may include two, three or more distinct DATA POINT icons <NUM>. In some instances, the particular information displayed on the DATA POINT icon <NUM> may be user-selectable.

To gain access, a user may slide an UNLOCK bar <NUM>. In response, the user interface device <NUM> may display one or more screens (not illustrated) that enable a user to enter a username and/or a password, for example. The user interface device <NUM> may provide provisions for someone to enter additional usernames and passwords, and to optionally enter security levels for individuals. For example, some users may have more limited rights as to what they can see or alter while other users may have more extensive rights. Once the user has successfully logged in to the user interface device <NUM>, the user interface device <NUM> may display a screen <NUM>, as shown in <FIG>.

As seen in <FIG>, the screen <NUM> may be considered as being a home screen, or perhaps a main menu screen. The screen <NUM> may include any number of different icons, depending on how the building controller <NUM> is configured, what sort of plants are being operated by the building controller <NUM>, as well as any variety of user-defined settings or parameters. As illustrated, the screen <NUM> includes an ID bar <NUM> that may, for example, name the specific building controller <NUM>, include the user's name, and the time. These are just examples, and are not intended as being limiting. The screen <NUM> includes a FAST ACCESS icon <NUM>, an ALARMS icon <NUM>, a DATA POINT icon <NUM>, a POINTS IN MANUAL icon <NUM>, a TIME PROGRAMS icons <NUM>, a SETTINGS icon <NUM> and an INFORMATION icon <NUM>. In some cases, the screen <NUM> may include descriptive text accompanying each icon <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>. In some cases, as shown, the ALARMS icon <NUM> also includes an indication 76a that provides an indication of how many points are currently in alarm. It will be appreciated that in response to a user selecting any of these icons <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, or other icons not presently illustrated, that the user interface device <NUM> may display one or more screens that either provide the user with additional information or enable the user to enter information to be transmitted to the building controller <NUM>.

The TIME PROGRAMS icon <NUM>, if selected, will cause the user interface device <NUM> to display one or more screens pertaining to scheduling. The INFORMATION icon <NUM>, if selected, will cause the user interface device <NUM> to display one or more screens that provide additional general information to the user. At least some aspects of each of the icons <NUM>, <NUM>, <NUM>, <NUM> and <NUM> will be discussed, in turn. In particular, illustrative but non-limiting screen shots pertaining to the FAST ACCESS icon <NUM> may be found in <FIG>. Illustrative but non-limiting screen shots pertaining to the ALARMS icon <NUM> may be found in <FIG>. Illustrative but non-limiting screen shots pertaining to the DATA POINT icon <NUM> may be found in <FIG>. Illustrative but non-limiting screen shots pertaining to the POINTS IN MANUAL icon <NUM> may be found in <FIG>. Illustrative but non-limiting screen shots pertaining to the SETTINGS icon <NUM> may be found in <FIG>.

Selecting the FAST ACCESS icon <NUM> will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. <FIG> will show screens displayable by the user interface device <NUM> in working with FAST ACCESS lists. In <FIG>, the screen <NUM> includes a COMMAND bar <NUM> that includes a HOME button <NUM> which, if selected, will cause the user interface device <NUM> to revert to the main menu page as shown in the screen <NUM> (<FIG>). The COMMAND bar <NUM> includes text informing the user where they are in the menu, as well as a CREATE button <NUM>. The screen <NUM> also includes a generic list including List <NUM>, List <NUM>, and so on, representing lists that can be named and populated if desired. To illustrate, selecting the CREATE button <NUM> will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. As seen in <FIG>, the COMMAND bar <NUM> now includes a BACK icon <NUM> which, if selected, will cause the user interface device <NUM> to revert to the previous screen <NUM> (<FIG>), as well as text informing the user where they are in the menu. A CANCEL button <NUM> may be used to cancel what the user is doing while a SAVE button <NUM> may be used to save what the user is doing. The screen <NUM> includes an ACTION bar <NUM> that displays the name that the user is typing using the QWERTY keyboard <NUM>.

As seen in a screen <NUM> (<FIG>), the ACTION bar <NUM> now reads that the FA LIST NAME is now FAL <NUM>, as entered by the user. Assuming that the user is happy with this name, and did not make any typographical or spelling errors, the user may save the new name by selecting the SAVE button <NUM>. In response to the user selecting the SAVE button <NUM>, the user interface device <NUM> will display a screen <NUM> (<FIG>). The screen <NUM> is identical to the screen <NUM> (<FIG>), but includes the new name "FAL <NUM>" displayed within the list. Once the list has been named, it can be accessed in order to, for example, at data points to that list. Selecting the FAL <NUM> icon <NUM> (<FIG>) causes the user interface device <NUM> to display a screen <NUM> (<FIG>).

In the screen <NUM>, the COMMAND bar <NUM> includes the HOME button <NUM>, the CREATE button <NUM> as well as an indication of where the user is in the menu. The user may select an FA list, such as the FAL <NUM> list by selecting the FAL <NUM> icon <NUM>. In response, the user interface device <NUM> will display a screen <NUM>, as shown in <FIG>. In the screen <NUM>, the COMMAND bar <NUM> includes the BACK icon <NUM> and an EDIT button <NUM>. The screen <NUM> includes a list <NUM> of data points as well as an accompanying list <NUM> of current values or current set points for the corresponding data points. The user may select the EDIT button <NUM> to cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>.

As shown in <FIG>, the COMMAND bar <NUM> displayed in the screen <NUM> includes the BACK icon <NUM>, a REMOVE button <NUM>, an ADD button <NUM> and an OK button <NUM> as well as an indication of where the user is in the menu. The screen <NUM> includes a list <NUM> of data point names and an accompanying list <NUM> of corresponding values. Selecting the ADD button <NUM> will enable a user to add a new data point to the FAL <NUM> list, and will cause the user interface device <NUM> to display a screen <NUM> as seen in <FIG>. In <FIG>, the COMMAND bar <NUM> can be seen as including a NEXT button <NUM>. The screen <NUM> includes a list <NUM> of point types along with radio buttons that can be used to select any or all of the point types.

<FIG> shows a screen <NUM>, which is the result of the user selecting particular point types, as indicated by the filled in radio buttons alongside some of the point types. At this point, the user can select the NEXT button <NUM> to move to a screen <NUM>, as shown in <FIG>. As seen in the screen <NUM>, the COMMAND bar <NUM> includes the BACK icon <NUM> and the ADD button <NUM>. The screen <NUM> includes a list <NUM> of data points as well as an accompanying list <NUM> of plants that correspond to the data points. In order to add the Data point name <NUM>, for example, the user may select that data point as indicated by the filled in radio button shown in a screen <NUM> (<FIG>). The user may then select the ADD button <NUM> to add the selected data point.

<FIG> show illustrative screens that pertain to deleting a list. <FIG> shows a screen <NUM> in which the COMMAND bar <NUM> includes the HOME button <NUM> and the CREATE button <NUM> as well as an indication of where the user is in the menu. The screen <NUM> includes a list <NUM> of FA lists. The user may select the List <NUM> by sliding left near a LIST <NUM> icon <NUM>, causing the user interface device <NUM> to display a screen <NUM> (<FIG>). As can be seen, the list <NUM> no longer includes the LIST <NUM> icon <NUM>. A DELETE button <NUM> may be selected in order to delete the LIST <NUM> from the list of FA lists. Pressing the DELETE button <NUM> causes the user interface device <NUM> to display a screen <NUM> (<FIG>) that includes a NO icon <NUM> and a DELETE icon <NUM>, along with an alphanumeric message <NUM> that asks the user to confirm whether they wish to proceed with the deletion. Pressing the DELETE icon <NUM> will cause the selected List <NUM> to be deleted.

<FIG> show illustrative screens that pertain to removing one or more points. <FIG> shows a screen <NUM> that includes a list <NUM> of data point names as well as an accompanying list <NUM> of corresponding values for the data points. Selecting the EDIT button <NUM> causes the user interface device <NUM> to display a screen <NUM> (<FIG>) that includes the list <NUM> as well as a list <NUM> of plant types. The user may delete the data point name <NUM> by selecting a corresponding radio button. This can be seen in <FIG>, which shows a screen <NUM> in which the radio button corresponding to the data point <NUM> has been selected. Pressing the REMOVE button <NUM> will delete the selected data point.

<FIG> and <FIG> show illustrative screens that pertain to renaming a FA list. In <FIG>, a screen <NUM> includes a list <NUM> of data points and a list <NUM> of corresponding plant types. The COMMAND bar <NUM> includes a FAL <NUM> icon <NUM>. By selecting the FAL <NUM> icon <NUM>, the user interface device <NUM> displays a screen <NUM> that enables the user to rename the selected FA list. The ACTION bar <NUM> includes an identification of which Fast Access list is being renamed, and the COMMAND bar <NUM> includes an indication that the user is to proceed with amending the name. They can use the QWERTY keyboard <NUM> to enter a new or revised name, and can then select the SAVE button <NUM> to save the new name.

<FIG> are screen shots of illustrative ALARM screens that may be displayed by the user interface device <NUM>. Pressing the ALARMS icon <NUM> on the main menu screen (<FIG>) will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. The screen <NUM> includes a listing of all data points that are in alarm. It can be seen that the COMMAND bar <NUM> includes an IN ALARM icon <NUM>, an UNACKNOWLEDGED icon <NUM> and a HISTORY icon <NUM>. As can be seen, the IN ALARM icon <NUM> has been selected, and thus the screen <NUM> includes a list <NUM> of all current alarms. The screen <NUM> includes a list <NUM> of current values for the data points that are listed in the list <NUM>, as well as a list <NUM> of alarm frequency and a list <NUM> of alarm seriousness for each of the data points that are listed in the list <NUM> as being in alarm.

Selecting, for example, the first data point listed in the list <NUM> causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. As can be seen, the COMMAND bar <NUM> includes an INFORMATION button <NUM> that may be selected to provide additional information, for example, as well as the name of the selected data point. The ACTION bar <NUM> includes an indication that the data point is in alarm, as well as an indication that the alarm is URGENT. The screen <NUM> includes additional information <NUM> regarding the data point and the corresponding alarm.

<FIG> shows a screen <NUM> that shows unacknowledged alarms. As can be seen, the UNACKNOWLEDGED icon <NUM> has been selected. It will be appreciated that the data point names shown in the Figures are illustrative only, and are not intended to be unique. The screen <NUM> includes a list <NUM> showing date and time for when each of the listed data points went into alarm. Selecting the first listed data point, for example, will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. As can be seen, the COMMAND bar <NUM> includes the INFORMATION button <NUM>, an ACKNOWLEDGE button <NUM> that may be used by the user to acknowledge a particular alarm as well as the name of the selected data point. The ACTION bar <NUM> includes an indication that the data point is in alarm, as well as an indication that the alarm is URGENT. The screen <NUM> includes additional information <NUM> regarding the data point and the corresponding alarm.

In <FIG>, the user interface device <NUM> is displaying a screen <NUM> that lists alarm history, as indicated by the HISTORY icon <NUM> being selected. Again, it will be appreciated that the data point names shown in the Figures are illustrative only, and are not intended to be unique. The screen <NUM> includes a list <NUM> of data points that have previously been in alarm. A list <NUM> shows the severity of each alarm, and the list <NUM> showing date and time for when each of the listed data points went into alarm. Selecting the first listed data point, for example, will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. As can be seen, the COMMAND bar <NUM> includes the INFORMATION button <NUM> and the name of the selected data point. The screen <NUM> includes additional information <NUM> regarding the data point and the corresponding alarm.

<FIG> illustrate how to proceed from an alarm detail page to point detail. <FIG> shows a screen <NUM> that is similar to the screen <NUM> shown in <FIG>. Selecting the first listed data point causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. As can be seen, the COMMAND bar <NUM> includes the INFORMATION button <NUM> and the name of the selected data point. The ACTION bar <NUM> includes an indication that the data point is in alarm, as well as an indication that the alarm is URGENT. The screen <NUM> includes additional information <NUM> regarding the data point and the corresponding alarm. Selecting the INFORMATION button <NUM> causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. The COMMAND bar <NUM> includes a SET TO MANUAL button <NUM> that may be used to manually adjust the particular data point that is in alarm.

<FIG> shows a screen <NUM> that may be displayed by the user interface device <NUM> in response to selecting the DATA POINT icon <NUM> in <FIG>. The screen <NUM> includes a list <NUM> of data points as well as a list <NUM> of the corresponding values of each of the data points. Selecting the first listed data point causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. The COMMAND bar <NUM> includes the SET TO MANUAL button <NUM> and the screen <NUM> includes additional information <NUM> pertaining to the selected data point. If the user selects the SET TO MANUAL button <NUM>, the user interface device <NUM> displays a screen <NUM>, as shown in <FIG>. In <FIG>, the ACTION bar <NUM> includes the current value for the data point. A numeric keypad <NUM> is displayed so that the user can change the value for the selected data point. Once they have adjusted the value, they can select the SAVE button <NUM> to save the new value. Alternatively, they can select the CANCEL button <NUM> if they do not wish to change the value of the selected data point. <FIG> shows a screen <NUM> that illustrates that the user interface device <NUM> is able to display up to two lines of alphanumeric text for each of the data points. It will be appreciated that the text shown is intended to be merely illustrative.

<FIG> show screens pertaining to adding data points to the Fast Access list. <FIG> shows a screen <NUM> including a list <NUM> of data points and a list <NUM> of the corresponding values for each of the listed data points. A user may select one of the data points (as illustrated the user is selecting the top listed data point) by sliding left on the desired data point. In response, the user interface device <NUM> displays a screen <NUM>. The ACTION bar <NUM> includes an indication of the current value of the selected data point. The ACTION bar <NUM> also includes an ADD TO LOCK SCREEN icon <NUM> and an ADD TO FA LIST icon <NUM>. It will be appreciated that the ACTION bar <NUM> has been superimposed over or has otherwise replaced the selected data point within the list <NUM> and the list <NUM>.

Selecting the ADD TO FA LIST icon <NUM> causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. The COMMAND bar <NUM> includes instructions that the user is to choose a list to add. The user can select one of the data points shown in a list <NUM>, which causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. In <FIG>, the ACTION bar <NUM> includes the ADD TO LOCK SCREEN icon <NUM> and includes an FA LIST icon <NUM> that includes a check mark to indicate that the data point was successfully added to the selected list.

<FIG> show screens pertaining to adding a data point to the LOCK SCREEN (the screen <NUM> as shown in <FIG>). <FIG> shows a screen <NUM> that is similar to the screen <NUM> (<FIG>). A data point may be selected by sliding left on the desired data point. As a result, the user interface device <NUM> displays a screen <NUM>, as shown in <FIG>. If the user selects the ADD TO LOCK SCREEN icon <NUM>, the user interface device <NUM> will display a screen <NUM>, as seen in <FIG>. As can be seen, the ACTION bar <NUM> now includes a LOCK SCREEN icon <NUM> that includes a check mark indicating that the selected data point has been added to the lock screen. As noted with respect to <FIG>, this means that the particular data point will be visible on the lock screen.

<FIG> show screens pertaining to POINTS IN MANUAL. These screens may be reached, for example, by selecting the POINTS IN MANUAL icon <NUM> as shown in <FIG>. Selection of the POINTS IN MANUAL icon <NUM> will cause the user interface device <NUM> to display a screen <NUM> (<FIG>). On the screen <NUM>, the COMMAND bar <NUM> includes a SELECT button <NUM>. Selecting the SELECT button <NUM> will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. The COMMAND bar <NUM> as seen in the screen <NUM> includes the CANCEL button <NUM>, a SET TO AUTO button <NUM> and an indication of where the user is in the menu. The COMMAND bar <NUM> also includes a THREE DOTS icon <NUM> that may, as will be discussed, be used to automatically select all of the data points. A set of radio buttons <NUM> is displayed adjacent the list <NUM> of data points. A user may select one or more of the radio buttons <NUM>, as shown in a screen <NUM> (<FIG>). Pressing the SET TO AUTO button <NUM> will cause the selected data points to be switched from manual to auto control.

<FIG> are similar, but illustrate a method of easily selecting all of the data points to be changed from manual to auto control. <FIG> shows a screen <NUM> that is similar to the screen <NUM> (<FIG>). Selecting the SELECT button <NUM> will cause the user interface device <NUM> to display a screen <NUM>. Selecting the THREE DOTS icon <NUM> will cause the user interface device <NUM> to automatically select all of the displayed data points and to display a screen <NUM> (<FIG>) that includes a SET ALL TO AUTO button <NUM>. Selecting the SET ALL TO AUTO button <NUM> will cause the user interface device <NUM> to do so.

<FIG> shows a screen <NUM> that includes the list of data points <NUM> and accompanying list <NUM> of current values. Selecting one of the listed data points will cause the user interface device <NUM> to display a screen <NUM> in which the COMMAND bar <NUM> includes the name of the selected data point. The screen <NUM> includes additional information <NUM> regarding the selected data point. If the user desires, they can select the SET TO AUTO button <NUM> to change control of the selected data point from manual to auto.

<FIG> shows a screen <NUM> in which the COMMAND bar <NUM> includes the name of the selected data point. The screen <NUM> includes additional information <NUM> regarding the selected data point. If the user desires, they can select the edit button <NUM> to edit the selected data point. Selecting the edit button <NUM> causes the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>. The current value of the selected data point is shown in the ACTION bar <NUM>. The screen <NUM> includes the numeric keypad <NUM> so that the user can edit the numeric value of the data point.

In some cases, it will be appreciated that in many of these illustrated screens, there may be considerably more data to display than can fit on a single screen. While the user interface device <NUM> may be built to be any desired size, in some cases the user interface device <NUM> itself or at least the display <NUM> (<FIG>) may be relative small. For example, the display <NUM> may have a rectilinear shape having a width that ranges from about <NUM> or <NUM> inches to about <NUM> or <NUM> inches and a height (perpendicular to its width) that ranges from about <NUM> or <NUM> inches to about <NUM> or <NUM> inches. However, the building controller <NUM> may control hundreds of points that pertain to a number of plants. Accordingly, there needs to be a way to sequentially display this data. In some cases, a user may be able to scroll line by line up or down through displayed data. In some instances, however, the user interface device <NUM> may instead display data page by page, and let the user page through.

<FIG> shows a screen <NUM> that shows LIST pagination. The screen <NUM> includes a list <NUM> of data points along with a list <NUM> of the corresponding current values of the data points. The screen <NUM> includes a PAGE icon <NUM> that informs the user that the current screen includes more than one page. In some cases, the PAGE icon <NUM> is only displayed transiently. For example, the PAGE icon <NUM> may only be displayed for about <NUM> seconds or so. The user is able to page through by scrolling up, as schematically illustrated by the arrow <NUM>. <FIG> shows a screen <NUM> that represents page <NUM> of the data initially displayed in <FIG>. It can be seen that the PAGE icon <NUM> has been updated to indicate that the screen <NUM> shows page <NUM>. <FIG> shows a screen <NUM> pertaining to data point detail pagination. The screen <NUM> includes additional details <NUM> regarding the particular data point (named within the COMMAND bar <NUM>). <FIG> shows a screen <NUM> that results once the user has advanced to page <NUM>, by scrolling vertically on the screen <NUM>.

<FIG> shows a screen <NUM> that may be displayed by the user interface device <NUM> when paging through filter pages. The screen <NUM> includes a CLEAR button <NUM> and an APPLY button <NUM> in the COMMAND bar <NUM>. The screen <NUM> includes a listing <NUM> of point types and corresponding radio buttons and of course includes the PAGE icon <NUM>. <FIG> shows a screen <NUM> that includes a listing <NUM> of plant types, and of course includes the PAGE icon <NUM> so that the user knows to scroll vertically.

<FIG> pertain to adding data point filtering while <FIG> pertain to clearing data point filtering. <FIG> shows a screen <NUM> that includes in the COMMAND bar <NUM> a FILTER icon <NUM>. The screen <NUM> includes a list <NUM> of data points and a list <NUM> of the corresponding values of each of the listed data points. Selecting the FILTER icon <NUM> causes the user interface device <NUM> to display a screen <NUM> (<FIG>). The screen <NUM> includes a listing <NUM> of point types and accompanying radio buttons so that a user may select one or more of the point types. <FIG> shows a screen <NUM> in which several of the point types have been selected, as indicated by the filled in radio buttons. Selecting the APPLY button <NUM> causes the user interface device <NUM> to display a screen <NUM> (<FIG>) that shows information <NUM>, resulting from the previous filtering.

<FIG> shows a screen <NUM> that may be displayed by the user interface device <NUM>. If the user selects the FILTER icon <NUM>, the user interface device <NUM> will display a screen <NUM>, as seen in <FIG>. In the screen <NUM>, it can be seen that several of the point types shown in the list <NUM> have been selected, as indicated by the filled in radio buttons. If the user selects the CLEAR button <NUM>, the user interface device <NUM> displays a screen <NUM>, as shown in <FIG>, in which all of the radio buttons have been cleared. Subsequently selecting the APPLY button <NUM> will cause the user interface device <NUM> to display a screen <NUM>, as shown in <FIG>, in which the unfiltered data points are listed in the list <NUM>, along with the corresponding values shown in the list <NUM>.

<FIG> are examples of SETTINGS screens that may be displayed by the user interface device <NUM>. <FIG> shows a screen <NUM> that may be reached by selecting the SETTINGS icon <NUM> (<FIG>). The screen <NUM> includes a list <NUM> of individual settings along with a list <NUM> of their current settings. If a user selects the first setting listed, which is LOCK SCREEN TIME, the user interface device <NUM> will display a screen <NUM> as shown in <FIG>. The screen <NUM> includes a listing <NUM> of available settings for the LOCK SCREEN TIME. The current setting, <NUM> minutes, is highlighted. If the user wishes to change this setting, they can simply select one of the other times, followed by selecting the SAVE button <NUM>. If they decide not to change the time, they can cancel out by selecting the CANCEL button <NUM>.

<FIG> shows a screen <NUM> that includes a list <NUM> of individual settings along with a list <NUM> of their current settings. If a user selects the second setting listed, which is POINT LIST SETTINGS, the user interface device <NUM> will display a screen <NUM> as shown in <FIG>. The screen <NUM> includes a listing <NUM> of possible settings for the POINT LIST SETTINGS, with the current value highlighted. If the user wishes to change this setting, they can simply select one of the other times, followed by selecting the SAVE button <NUM>. If they decide not to change the time, they can cancel out by selecting the CANCEL button <NUM>.

<FIG> shows a screen <NUM> that includes a list <NUM> of individual settings along with a list <NUM> of their current settings. If a user selects the third setting listed, which is LOCK SCREEN DATAPOINT, the user interface device <NUM> will display a screen <NUM> as shown in <FIG> shows a screen <NUM> that may be displayed by the user interface device <NUM> for setting point types to search for. The point types are listed in a list <NUM>. <FIG> shows a screen <NUM> that shows several of the point types selected. <FIG> shows a screen <NUM> that includes a list <NUM> of data point names and a list <NUM> of corresponding values.

Claim 1:
A building control system (<NUM>), comprising:
a) a building controller (<NUM>) including a building controller housing that is structured to mount to a DIN rail, the building controller (<NUM>) including an I/O port (<NUM>) and a plurality of ports (<NUM>) for providing direct wired communication with one or more building control components (18a-18d) of a HVAC system,
b) wherein at least one of the building control components include one or more of a fan, a blower, and an actuator and the building controller (<NUM>) includes colour indication to provide an operational status of the building controller (<NUM>) but does not include a dot matrix display;
c) wherein the building controller (<NUM>) is configured to provide control signals in accordance with a control algorithm to control the one or more building control components via the direct wired communication between the building controller and the one or more building control components of the HVAC system; and
d) a user interface device (<NUM>), separate from the building controller (<NUM>), the user interface device including a user interface device housing structured to be mounted to the DIN rail, the user interface device further comprising a controller (<NUM>) and an user interface (<NUM>) that includes a display (<NUM>) and an I/O port (<NUM>) adapted to permit the user interface device (<NUM>) to communicate with the building controller (<NUM>) via the I/O port (<NUM>) of the building controller (<NUM>), wherein the user interface device (<NUM>) is configured to display on the display (<NUM>) a plurality of menu screens that allow a user to locally interact with the building controller, the user interface device (<NUM>) is configured to display one or more screens that display at least some information received from the building controller (<NUM>) that cannot be displayed by the building controller (<NUM>) and the user interface device (<NUM>) is configured to solicit at least some information for the building controller (<NUM>).