Patent Publication Number: US-8543243-B2

Title: System and method of use for a user interface dashboard of a heating, ventilation and air conditioning network

Description:
CROSS-REFERENCE TO RELATED APPLICATIONS 
     This application claims the benefit of U.S. Provisional Application Ser. No. 61/167,135, filed by Grohman, et al., on Apr. 6, 2009, entitled “Comprehensive HVAC Control System” and U.S. Provisional Application Ser. No. 61/852,676, filed by Grohman, et al., on Apr. 7, 2009, and is also a continuation-in-part application of application Ser. No. 12/258,659, filed by Grohman on Oct. 27, 2008, entitled “Apparatus and Method for Controlling an Environmental Conditioning Unit,” all of which are commonly assigned with this application and incorporated herein by reference. This application is also related to the following U.S. patent applications, which are filed on even date herewith, commonly assigned with this application and incorporated herein by reference: 
     
       
         
           
               
               
               
             
               
                   
               
               
                 Ser. No. 
                 Inventors 
                 Title 
               
               
                   
               
             
            
               
                 12/603,464 
                 Grohman, et 
                 “Alarm and Diagnostics System and 
               
               
                   
                 al. 
                 Method for a Distributed-Architecture 
               
               
                   
                   
                 Heating, Ventilation and Air 
               
               
                   
                   
                 Conditioning Network” 
               
               
                 12/603,534 
                 Wallaert, 
                 “Flush Wall Mount Controller and In-Set 
               
               
                   
                 et al. 
                 Mounting Plate for a Heating, 
               
               
                   
                   
                 Ventilation and Air Conditioning 
               
               
                   
                   
                 System” 
               
               
                 12/603,449 
                 Thorson, et 
                 “System and Method of Use for a User 
               
               
                   
                 al. 
                 Interface Dashboard of a Heating, 
               
               
                   
                   
                 Ventilation and Air Conditioning 
               
               
                   
                   
                 Network” 
               
               
                 12/603,382 
                 Grohman 
                 “Device Abstraction System and Method 
               
               
                   
                   
                 for a Distributed-Architecture Heating, 
               
               
                   
                   
                 Ventilation and Air Conditioning 
               
               
                   
                   
                 Network” 
               
               
                 12/603,526 
                 Grohman, et 
                 “Communication Protocol System and 
               
               
                   
                 al. 
                 Method for a Distributed-Architecture 
               
               
                   
                   
                 Heating, Ventilation and Air 
               
               
                   
                   
                 Conditioning Network” 
               
               
                 12/603,527 
                 Hadzidedic 
                 “Memory Recovery Scheme and Data 
               
               
                   
                   
                 Structure in a Heating, Ventilation and 
               
               
                   
                   
                 Air Conditioning Network” 
               
               
                 12/603,490 
                 Grohman 
                 “System Recovery in a Heating, 
               
               
                   
                   
                 Ventilation and Air Conditioning 
               
               
                   
                   
                 Network” 
               
               
                 12/603,473 
                 Grohman, et 
                 “System and Method for Zoning a 
               
               
                   
                 al. 
                 Distributed-Architecture Heating, 
               
               
                   
                   
                 Ventilation and Air Conditioning 
               
               
                   
                   
                 Network” 
               
               
                 12/603,525 
                 Grohman, et 
                 “Method of Controlling Equipment in a 
               
               
                   
                 al. 
                 Heating, Ventilation and Air 
               
               
                   
                   
                 Conditioning Network” 
               
               
                 12/603,512 
                 Grohman, et 
                 “Programming and Configuration in a 
               
               
                   
                 al. 
                 Heating, Ventilation and Air 
               
               
                   
                   
                 Conditioning Network” 
               
               
                 12/603,431 
                 Mirza, et 
                 “General Control Techniques in a 
               
               
                   
                 al. 
                 Heating, Ventilation and Air 
               
               
                   
                   
                 Conditioning Network” 
               
               
                   
               
            
           
         
       
     
    
    
     TECHNICAL FIELD 
     This application is directed, in general, to HVAC systems and, more specifically, to a user interface dashboard and installer interface dashboard for a distributed-architecture heating, ventilation and air conditioning (HVAC) network, and methods of use thereof. 
     BACKGROUND 
     Climate control systems, also referred to as HVAC systems (the two terms will be used herein interchangeably), are employed to regulate the temperature, humidity and air quality of premises, such as a residence, office, store, warehouse, vehicle, trailer, or commercial or entertainment venue. The most basic climate control systems either move air (typically by means of an air handler, or more colloquially, a fan or blower), heat air (typically by means of a furnace) or cool air (typically by means of a compressor-driven refrigerant loop). A thermostat is typically included in the climate control systems to provide some level of automatic temperature control. In its simplest form, a thermostat turns the climate control system on or off as a function of a detected temperature. In a more complex form, a thermostat may take other factors, such as humidity or time, into consideration. Still, however, the operation of a thermostat remains turning the climate control system on or off in an attempt to maintain the temperature of the premises as close as possible to a desired setpoint temperature. Climate control systems as described above have been in wide use since the middle of the twentieth century. 
     SUMMARY 
     In a first aspect the disclosure provides an HVAC graphical interface dashboard. In an embodiment the dashboard includes a weather tab, wherein invoking the weather tab advances to a weather screen. The dashboard also includes an indoor humidity tab, wherein invoking the indoor humidity tab advances to a humidity screen which displays at least a current indoor humidity. The dashboard further includes an alerts tab, wherein invoking the alerts tab advances to an alerts screen. The dashboard also further includes a help tab, wherein invoking the help tab advances to a help screen that provides context sensitive help that presents at least one dialog box related to a function of a current screen. The dashboard yet also further includes an indoor settings tab, wherein invoking the indoor settings tab advances to an indoor settings screen which includes a current indoor temperature. The dashboard still further includes a programs tab, wherein invoking the programs tab advances to a programs screen wherein the programs screen includes a display of a plurality of pre-populated program schedule settings. The dashboard yet still further includes a home tab, wherein invoking the home tab advances to a home screen which provides a summary of indoor conditions. 
     In another aspect the disclosure provides a method for operating an HVAC interface having a plurality of tabs. In an embodiment the method includes: providing a weather tab, wherein invoking the weather tab advances to a weather screen. The method also includes providing an indoor humidity tab, wherein invoking the indoor humidity tab advances to a humidity screen which displays at least a current indoor humidity. The method further includes providing an alerts tab, wherein invoking the alerts tab advances to an alerts screen. The method yet further includes providing a help tab, wherein invoking the help tab advances to a help screen that provides context sensitive help that presents at least one dialog box related to a function of a current screen. The method yet still further includes providing an indoor settings tab, wherein invoking the indoor settings tab advances to an indoor settings screen which includes a current indoor temperature. The method also yet further includes providing a programs tab, wherein invoking the programs tab advances to a programs screen wherein the programs screen includes a display of a plurality of pre-populated program settings. The method also includes providing a home tab, wherein invoking the home tab advances to a home screen which provides a summary of indoor conditions. The method also yet still further includes invoking one of the screens. 
     A third aspect provides an HVAC system including a graphical interface dashboard and at least one coupled device. In an embodiment the dashboard includes a weather tab, wherein invoking the weather tab advances to a weather screen. The dashboard also includes an indoor humidity tab, wherein invoking the indoor humidity tab advances to a humidity screen which displays at least a current indoor humidity. The dashboard further includes an alerts tab, wherein invoking the alerts tab advances to an alerts screen. The dashboard further includes a help tab, wherein invoking the help tab advances to a help screen that provides context sensitive help that presents at least one dialog box related to a function of a current screen. The dashboard yet also further includes an indoor settings tab, wherein invoking the indoor settings tab advances to an indoor settings screen which includes a current indoor temperature. The dashboard still further includes a programs tab, wherein invoking the programs tab advances to a programs screen wherein the programs screen includes a display of a plurality of pre-populated program settings. The dashboard yet still further includes a home tab, wherein invoking the home tab advances to a home screen which provides a summary of indoor conditions. The second aspect further includes at least one coupled device selected from the group including: a) an air handler, b) a furnace, c) an evaporator coil, d) a condenser coil and e) a compressor, wherein at least one coupled device is viewable from at least one of the tabs. 
    
    
     
       BRIEF DESCRIPTION 
       Reference is now made to the following descriptions taken in conjunction with the accompanying drawings, in which: 
         FIG. 1  is a high-level block diagram of an HVAC system within which a device abstraction system and method may be contained or carried out; 
         FIG. 2  is a high-level block diagram of one embodiment of an HVAC data processing and communication network  200 ; 
         FIG. 3A  is a diagram of a series of steps in an event sequence that depicts a device commissioning in an HVAC network having an active subnet controller; 
         FIG. 3B  is a diagram of a series of steps that occur in relation to a commissioning of a subnet including an addressable unit; 
         FIG. 3C  is a diagram of the above series of steps of  FIG. 3B  to be followed by a subnet controller to synchronize with a device of the HVAC system; 
         FIG. 3D  is a high-level block diagram of one embodiment of a dashboard of a user interface for an HVAC system having a plurality of tabs, each tab configured to invoke one or more corresponding screens; 
         FIGS. 3E-1  and  3 E- 2  illustrate a table that discloses subject matter of screens correlated to tabs of  FIG. 3D ; 
         FIG. 4  is a high-level flow diagram of exemplary transitions, for both a user and an installer, between various screens corresponding to various tabs of the dashboard of  FIG. 3  and various screens of an interface dashboard of  FIGS. 7A and 7B , and an inter-relationship between  FIG. 3D  and  FIGS. 7A and 7B ; 
         FIG. 5  is an exemplary flow diagram of the user interface screens of  FIG. 4 , illustrated in more detail; 
         FIG. 5A  illustrates one embodiment of exemplary screens that bold a selected item when that selected item is compared to other selected items in a list of a tab of the dashboard of  FIG. 3D ; 
         FIG. 5B  illustrates, in one embodiment, a partial and complete locking of a screen of the dashboard of  FIG. 3D ; 
         FIG. 5C  illustrates, in one embodiment, an employment of icons for various devices instead of text entries of the dashboard of  FIG. 3D ; 
         FIGS. 5D-1  through  5 D 5  illustrate an employment of an embodiment of a motion detector for use with the dashboard of  FIG. 3 ; 
         FIG. 5E  illustrates a selection in an exemplary screen of the dashboard  350  of an item through an employment of a text item itself as a button to select the item to which the text item correlates; 
         FIG. 6A  illustrates an exemplary employment of a humidity graphic to set humidity and de-humidity setpoints of a humidity screen of the humidity tab of  FIG. 3D ; 
       FIGS.  6 B- 1 - 6 B- 4  illustrates an exemplary employment of screen selectable settings for setting a humidity point in a humidity screen of  FIG. 3D  that is dependent upon equipment installed in the HVAC system of  FIG. 1 ; 
       FIGS.  7 Ai- 7 Aiv and  7 Bi- 7 Biv illustrate an exemplary flow of various transitions of a help screen that arise as a result of a previous screen of  FIG. 3D ; 
         FIGS. 8A-8D  illustrates exemplary screens of found equipment that appears in an indoor settings tab of  FIG. 3D  as dependent upon equipment being found in the HVAC system of  FIG. 1 ; 
         FIG. 9A  illustrates an exemplary plurality of program schedule setpoints displayed on one screen of a programs tab of  FIG. 3 ; 
         FIGS. 9B-1  and  9 B- 2  illustrates an exemplary persistent color inversion for a selected button until a next button press within the programs screen of the programs tab of  FIG. 3D ; 
         FIG. 9C  illustrates an exemplary deactivation of a time period within the programs screen of  FIG. 3D ; 
         FIGS. 9D-1  and  9 D- 2  illustrate embodiments of a virtual analog clock in a programs screen of  FIG. 3D ; 
         FIG. 9E  illustrates one embodiment of a program screen that allows for a reset of at least one value related to the dashboard of  FIG. 3D ; 
         FIG. 9F  illustrates one embodiment of a slider for setting a comfort point for a programs screen of  FIG. 3D ; 
       FIGS.  9 Fi and  9 Fii illustrate exemplary flows of a transition of a programs screen of the dashboard of  FIG. 3D ; 
         FIG. 10A  illustrates an exemplary movement of a finger across a home screen to allow access to either an installer or a zone screen for an embodiment of the dashboard of  FIG. 3D ; 
         FIG. 10B  illustrates an exemplary invocation of a plurality of dashboard tabs from a home screen of  FIG. 3D ; 
         FIGS. 11A-1  and  11 A- 2  illustrate embodiments of an installer dashboard that employs screens of  FIG. 4 ; 
         FIG. 11B  illustrates an exemplary display of minimum, maximum and default values for one embodiment of an installer screen of FIGS.  11 A 1  and  11 A 2  for a device connected to the HVAC system of  FIG. 1 ; 
         FIG. 11C  illustrates an exemplary underlining of default value for one embodiment of an installer screen of an installer screen of FIGS.  11 A 1  and  11 A 2 ; 
         FIGS. 11D-1  and  11 D- 2  illustrates an exemplary moving a device icon for an item to be diagnosed to a right side of a diagnostic screen of an embodiment of the installer dashboard of an installer screen of FIGS.  11 A 1  and  11 A 2 ; 
         FIG. 12  illustrates an exemplary method for providing an interface for an HVAC system of  FIG. 1 ; and 
         FIGS. 13A and 13B  illustrate a subnet controller teaching a user interface how to interpret data on a network within bounds earlier defined as a user interface screen. 
     
    
    
     DETAILED DESCRIPTION 
     As stated above, conventional climate control systems have been in wide use since the middle of the twentieth century and have, to date, generally provided adequate temperature management. However, it has been realized that more sophisticated control and data acquisition and processing techniques may be developed and employed to improve the installation, operation and maintenance of climate control systems. 
     Described herein are various embodiments of an improved climate control, or HVAC, system in which at least multiple components thereof communicate with one another via a data bus. The communication allows identity, capability, status and operational data to be shared among the components. In some embodiments, the communication also allows commands to be given. As a result, the climate control system may be more flexible in terms of the number of different premises in which it may be installed, may be easier for an installer to install and configure, may be easier for a user to operate, may provide superior temperature and/or relative humidity (RH) control, may be more energy efficient, may be easier to diagnose and perhaps able to repair itself, may require fewer, simpler repairs and may have a longer service life. 
       FIG. 1  is a high-level block diagram of an HVAC system, generally designated  100 . The HVAC system may be referred to herein simply as “system  100 ” for brevity. In one embodiment, the system  100  is configured to provide ventilation and therefore includes one or more air handlers  110 . In an alternative embodiment, the ventilation includes one or more dampers  115  to control air flow through air ducts (not shown.) Such control may be used in various embodiments in which the system  100  is a zoned system. In the context of a zoned system  100 , the one or more dampers  115  may be referred to as zone controllers  115 . In an alternative embodiment, the system  100  is configured to provide heating and, therefore, includes one or more furnaces  120 , typically associated with the one or more air handlers  110 . In an alternative embodiment, the system  100  is configured to provide cooling and, therefore, includes one or more refrigerant evaporator coils  130 , typically associated with the one or more air handlers  110 . Such embodiment of the system  100  also includes one or more compressors  140  and associated condenser coils  142 , which are typically associated in one or more so-called “outdoor units”  144 . The one or more compressors  140  and associated condenser coils  142  are typically connected to an associated evaporator coil  130  by a refrigerant line  146 . In an alternative embodiment, the system  100  is configured to provide ventilation, heating and cooling, in which case the one or more air handlers  110 , furnaces  120  and evaporator coils  130  are associated with one or more “indoor units”  148 , e.g., basement or attic units. 
     For convenience in the following discussion, a demand unit  155 , sometimes referred to as a unit  155 , is representative of the various units exemplified by the air handler  110 , furnace  120 , and compressor  140 , and more generally includes an HVAC component that provides a service in response to control by the control unit  150 . The service may be, e.g., heating, cooling, or air circulation. The demand unit  155  may provide more than one service, and if so, one service may be a primary service, and another service may be an ancillary service. For example, for a cooling unit that also circulates air, the primary service may be cooling, and the ancillary service may be air circulation (e.g. by a blower). 
     The demand unit  155  may have a maximum service capacity associated therewith. For example, the furnace  120  may have a maximum heat output (often expressed in terms of British Thermal Units (BTU) or Joules), or a blower may have a maximum airflow capacity (often expressed in terms of cubic feet per minute (CFM) or cubic meters per minute (CMM)). In some cases, the demand unit  155  may be configured to provide a primary or ancillary service in staged portions. For example, blower may have two or more motor speeds, with a CFM value associated with each motor speed. 
     One or more control units  150  control one or more of the one or more air handlers  110 , the one or more furnaces  120  and/or the one or more compressors  140  to regulate the temperature of the premises, at least approximately. In various embodiments to be described, the one or more displays  170  provide additional functions such as operational, diagnostic and status message display and an attractive, visual interface that allows an installer, user or repairman to perform actions with respect to the system  100  more intuitively. Herein, the term “operator” will be used to refer collectively to any of the installer, the user and the repairman unless clarity is served by greater specificity. 
     One or more separate comfort sensors  160  may be associated with the one or more control units  150  and may also optionally be associated with one or more displays  170 . The one or more comfort sensors  160  provide environmental data, e.g. temperature and/or humidity, to the one or more control units  150 . An individual comfort sensor  160  may be physically located within a same enclosure or housing as the control unit  150 . In such cases, the commonly housed comfort sensor  160  may be addressed independently. However, the one or more comfort sensors  160  may be located separately and physically remote from the one or more control units  150 . Also, an individual control unit  150  may be physically located within a same enclosure or housing as a display  170 . In such embodiments, the commonly housed control unit  150  and display  170  may each be addressed independently. However, one or more of the displays  170  may be located within the system  100  separately from and/or physically remote to the control units  150 . The one or more displays  170  may include a screen such as a liquid crystal display (not shown). 
     Although not shown in  FIG. 1 , the HVAC system  100  may include one or more heat pumps in lieu of or in addition to the one or more furnaces  120 , and one or more compressors  140 . One or more humidifiers or dehumidifiers may be employed to increase or decrease humidity. One or more dampers may be used to modulate air flow through ducts (not shown). Air cleaners and lights may be used to reduce air pollution. Air quality sensors may be used to determine overall air quality. 
     Finally, a data bus  180 , which in the illustrated embodiment is a serial bus, couples the one or more air handlers  110 , the one or more furnaces  120 , the one or more evaporator coils  130 , the one or more condenser coils  142  and compressors  140 , the one or more control units  150 , the one or more remote comfort sensors  160  and the one or more displays  170  such that data may be communicated therebetween or thereamong. As will be understood, the data bus  180  may be advantageously employed to convey one or more alarm messages or one or more diagnostic messages. 
       FIG. 2  is a high-level block diagram of one embodiment of an HVAC data processing and communication network  200  that may be employed in the HVAC system  100  of  FIG. 1 . One or more air handler controllers (“AHCs”)  210  may be associated with the one or more air handlers  110  of  FIG. 1 . One or more integrated furnace controllers (“IFCs”)  220  may be associated with the one or more furnaces  120 . One or more damper controller modules  215 , also referred to herein as a zone controller module  215 , may be associated with the one or more dampers  114  that interface the one or more dampers to the data bus  180 . One or more unitary controllers  225  may be associated with one or more evaporator coils  130  and one or more condenser coils  142  and compressors  140  of  FIG. 1 . The network  200  includes an active subnet controller (“aSC”)  230   a  and an inactive subnet controller (“iSC”)  230   i . The aSC  230   a  is responsible for configuring and monitoring the system  100  and for implementation of heating, cooling, air quality, ventilation or any other functional algorithms therein. Two or more aSCs  230   a  may also be employed to divide the network  200  into subnetworks, or subnets, simplifying network configuration, communication and control. The iSC  230   i  is a subnet controller that does not actively control the network  200 . In some embodiments, the iSC  230   i  listens to all messages passed over the data bus  180 , and updates its internal memory to match that of the aSC  230   a . In this manner, the iSC  230   i  may backup parameters stored by the aSC  230   a , and may be used as an active subnet controller if the aSC  230   a  malfunctions. Typically there is only one aSC  230   a  in a subnet, but there may be multiple iSCs therein, or no iSC at all. Herein, where the distinction between an active or a passive SC is not germane, the subnet controller is referred to generally as an SC  230 . 
     A user interface (“UI”)  240  provides a means by which an operator may communicate with the remainder of the network  200 . In an alternative embodiment, a user interface/gateway (UI/G)  250  provides a means by which a remote operator or remote equipment may communicate with the remainder of the network  200 . Such a remote operator or equipment is referred to generally as a remote entity. A comfort sensor interface  260 , referred to herein after simply as a comfort sensor, may provide an interface between the data bus  180  and each of the one or more comfort sensors  160 . 
     Each of the components  210 ,  220 ,  225 ,  230   a ,  230   i ,  240 ,  250 ,  260  may include a general interface device configured to interface to the data bus  180 , as described below. (For ease of description any of the networked components, e.g., the components  210 ,  220 ,  225 ,  230   a ,  230   i ,  240 ,  250 ,  260 , may be referred to generally herein as a device  290 . In other words, the device  290  of  FIG. 2  is a proxy for any of a furnace, a heat pump, a subnet controller, etc, and that device&#39;s associated interface means.) The data bus  180  in some embodiments is implemented using the Bosch CAN (Controller Area Network) specification, revision 2, and may be synonymously referred to herein as a residential serial bus (“RSBus”)  180 . The data bus  180  provides communication between or among the aforementioned elements of the network  200 . It should be understood that the use of the term “residential” is nonlimiting; the network  200  may be employed in any premises whatsoever, fixed or mobile. In wireless embodiments, the data bus  180  may be implemented, e.g., using Bluetooth™ or a similar wireless standard. 
     Generally, the network  200  allows for the remote comfort sensors  160 , the control unit  150 , and user display  170  and/or remote user displays  170  to operate independently as separate logical units, and can be located in separate locations within the network  200 . This is unlike the prior art, wherein these functionalities were required to be located within a single physical and logical structure. 
     Turning now to  FIG. 3A , illustrated is a diagram of a commissioning process  300  of a series of steps that occur in relation to a commissioning of the demand unit  155 . The commissioning process  300  includes an enter state  301 , a device commissioning state  303 , and an exit state  305 . The HVAC system  100  can be described as being partitioned into a plurality of subnets, each subnet controlled by its own active subnet controller  230 . 
     Device commissioning can generally be defined as setting operational parameters for a device in the network of the HVAC system, including its installation parameters. Generally, the commissioning process  300  is used by the subnet controller  230  when it is active to: a) set operating “Installer Parameters” for a networked device, such as air handlers  110 , (henceforth to be referred to collectively, for the sake of convenience, as the demand unit  155 , although other devices are also contemplated), b) to load UI/Gs  240 ,  250  with names and settings of “Installer Parameters and Features” of the demand units  155 , c) to configure replacement parts for the demand units  155 , and d) to restore values of “Installer Parameters and Features” in the demand units  155  if those “Parameters and Features” were lost due to memory corruption or any other event. Device commissioning is a process used in the HVAC system  100 , either in a “configuration” mode or in a “verification” mode. 
     In the “configuration” mode, the demand unit  155  shares its information with the active subnet controller  230   a  in an anticipation of being employable in the HVAC system  100 , and an appropriate subnet. Generally, the commissioning process  300  provides a convenient way to change or restore functional parameters, both for the active subnet controller  230   a  and the demand unit  155 . 
     In both the “verification” mode and the “configuration” mode, the demand unit  155  is checked for memory errors or other configuration or programming errors. There are differences in device  290  behavior between the “configuration” mode and in the “verification” mode, to be detailed below. 
     The “subnet startup” mode programs the subnet controller  230  to be active. The “subnet startup” mode enables subnet communications, (i.e., communication within a subnet), and also deactivates a “link” sub-mode. A “link” mode may be generally defined as a mode that allows a number of subnets to work together on the same HVAC network  200 , and that assigns subnet numbers for each subnet to allow this communication. 
     The “installer test” mode is employed when an installer installs and tests aspects and demand units  155  of the HVAC system  100 . The “normal operations” mode is an ongoing operation of devices  290  of the HVAC system  100  in a normal use. 
     More specifically, the device commissioning process  300  can be employed with: a) the “configuration” mode, which is invoked when transitioning to the commissioning state  303  from the “subnet startup mode” or “installer test” mode, or the “normal mode” (see below), or b) a “verification” mode. The “verification” mode is invoked when transitioning to the commissioning state  303  from the “subnet startup” mode. 
     The following describes an illustrative embodiment of a using the process  300  to commission the demand unit  155 , first for a “commission” mode, and then for a “verification” mode. The process of commissioning differs from a “subnet startup,” in that commissioning requires that the network configuration, including configuration and activation of subnet controllers  230 , has already been completed before the commissioning process  300  for the device  290  can start. Please note that there can be more than one subnet controller  230  on a subnet, but only one subnet controller  230   a  is active at any one time. 
     In one embodiment, in order to enter into a state  320  of a state machine  310  (described in detail below with respect to  FIG. 3B ) in the “configuration” mode, the unit  155  receives either: a) an “aSC” (‘active subnet controller’) Device Assignment message”, having “Assigned State” bits set to “Commissioning”; or b) a receipt of an “aSC Change State” message, with “New aSC State” bits set to “Commissioning,” from the active subnet controller  230 . For both “configuration” and “verification” modes, an “aSC Device Assignment” message can be generally regarded as a message that assigns the unit  155  to a particular active subnet controller  230   a . For both “configuration” and “verification” modes, an “aSC Change State” message can be generally regarded as a message that starts and ends employment of the commissioning process  300  for the devices  290 . 
     In one embodiment, in the state  320  in the configuration mode, all units  155  respond to the “aSC Device Assignment” message with their respective “Device Status” messages, indicating that the units  155  are now in the commissioning process  300  due to their response to this previous message. For both “configuration” and “verification” modes, the “Device Status” message can be generally defined as a message that informs the active subnet controller  230   a  of what actions are being taken by the unit  155  at a given time. 
     However, alternatively in other embodiments, in the state  320  in the “configuration” mode, if the units  155  are instead busy, as indicated by “aSC Acknowledge” bits of the “Device Status” message sent to the active subnet controller  230   a  set as a “Control Busy,” the active subnet controller  230   a  waits for the busy units  155  to clear their “aSC Acknowledge” bits before proceeding with further elements of the Commissioning process  300 . The units  155  then resend their “Device Status” messages as soon as they are no longer busy. 
     From this point on, all units  155  send their “Device Status” messages periodically and on any status change, both during and after the commissioning process  300 . If the unit  155  does not clear its “aSC Acknowledge” bits within a minute, the active subnet controller  230   a  sends an “Unresponsive Device2” alarm for each such unit  155 . If in “configuration” mode, the active subnet controller  230   a  remains in the waiting mode indefinitely, until the unit  155  responds correctly, or the subnet is reset manually or after a timeout is reached. In “verification” mode the active subnet controller  230   a  proceeds further to exit the state. 
     In the “configuration” mode, each unit  155  remembers all of its optional sensors that are currently attached to it. Furthermore, each unit  155  may store a local copy in its non-volatile memory (“NVM”) of any other unit features that it is dependent on. A unit  155  feature can be generally defined as any datum that is fixed and cannot be changed by the installer, serviceman or the home owner. Changing of a “Feature” value normally involves reprogramming of the unit&#39;s  155  firmware. 
     In at least some embodiments, a feature is something that is a fixed value, that is hard-wired into a device. In other words, no installer or home owner can change it. Features are programmed into the unit  155  during a manufacturing or an assembly process. Features can be recovered in a home, during a Data non-volatile memory (“NVM”) recovery substate of Commissioning state only—the recovery substate happens automatically and without installer or user intervention. In a further embodiment, parameters can be changed by the installers only. In a yet further embodiment, the network  200  of the HVAC system  100  employs “variables”—those can be changed by the installers and also the home owners. 
     In some embodiments, a “Parameter List” is normally a Feature that contains a special list of specific parameters included in the unit  155 . Parameter values can be changed, and their state can be changed also (from enabled to disabled and vice-versa), but their presence is set once and for all in a given firmware version. Therefore, a list of Parameters (not their values) is also fixed, and is thus treated as a “Feature.” 
     However, although elements of the “configuration” mode commissioning and “verification” mode commissioning are similar, when the active subnet controller  230  is in “verification” mode instead of in “configuration” mode, the active subnet controller  230   a  can exit commissioning process  300  regardless of the value of the alarms of the units  155 . However, alternatively, if the active subnet controller  230   a  is in “configuration” mode, the active subnet controller  230   a  will not exit from its commissioning process  300  for as long as at least one unit&#39;s  155  “aSC Acknowledge” flags are set to “Control Busy.” In one embodiment of the “verification” mode, the active subnet controller  230   a  timeouts the installation and resets the subnet to default parameters. 
     In the “verification” mode, assuming the unit  155  operates with a non-corrupted (original or restored copy) NVM, each unit  155  checks any of its attached sensors to see if they match with the parameters that were present in a most recent configuration of the unit  155 . In some embodiments, alarms are generated by the unit  155  for missing or malfunctioning sensors as soon as the faulty condition is detected, to be employed by the user interfaces and gateways present on the subnet to notify the installer or homeowner of the encountered problem. The unexpected absence of certain sensors may inhibit the operation of the unit  155  or the subnet. This is normally manifested by the signaling of the appropriate Service Bits in the Device Status message used by the active subnet controller  230   a , to determine the operational viability or health of the subnet&#39;s systems. 
     In some embodiments, the device commissioning process  300  (via the state machine  310 ) then transitions into a link-mode startup state  330  ( FIG. 3B ), and then ends, upon either: a) the last unit  155  receiving all of unit  155  parameters that it is dependent on, when in “verification” mode; or b) upon a request by a user, when in “configuration” mode. The active subnet controller  230  then proceeds to ensure that no subnet unit  155  has its “aSC Acknowledge” flag set to a “Control Busy” state. The “aSC Acknowledge” flag not being set indicates that all of a non-volatile memory of a given unit  155  had been written to with the necessary parameters. If no “Control Busy” state is detected, the active subnet controller  230   a  then issues the “aSC Change State” message, which forces the unit  155  from a commissioning state to a non-commissioning state, in either a “configuration” or a “verification” mode. 
     In some embodiments, when the unit  155  in the process  300  fails its NVM data integrity check in an “NVM Check State,” and the active subnet controller is unable to perform NVM Recovery, the unit  155  instead employs its default data stored in its non-volatile (Flash) memory and/or uses default calculations to initialize the data dependent on other devices in the system. The other device data to be used for commissioning could have been obtained in either the “verification” or “configuration” mode. For data or other parameters that were not transferred or generated as part of that session of the commissioning process  300 , default values are used. 
     In one embodiment, upon a detection of a system configuration error, such as a missing device whose features or parameters the unit  155  depends upon, it uses the locally stored copy of the other device&#39;s features that it depends upon, and ignores any potential feature value conflicts. In another embodiment, the unit  155  uses the locally stored copy of other parameters of the unit  155  that it depends on and ignores any potential dependent parameter value conflicts. In other words, the unit  155  employs a first installed parameter as a template for a second installed parameter on a second device. In a third embodiment, the unit  155  will change its parameter or feature values only if explicitly instructed by the active subnet controller  230  or the UI/G  240 ,  250 . 
     Turning now to  FIG. 3B , illustrated is the HVAC device state machine  310  illustrated for a subnet, including the unit  155 , in more detail. Solid lines indicate normal state transitions when the subnet is transitioning from one state to another state, dashed lines indicate a subroutine call and red lines, alternating dotted and dashed lines indicate unexpected yet valid transitions. All states other than a state  326  represent device states, and the state  326  represents a message handling routine. 
     As is illustrated in the present embodiment, a reset state  312  of a subnet advances to a NVR CRC check  316  for a given device (such as unit  155 ). If the device fails the test, the device advances to a device hard disable  314 . If the device passes, however, then in the subnet startup state  320 , various features and parameters of the unit  155  are shared with the subnet. Then, in substate  324 , device commissioning as described in  FIG. 3A  occurs. This then leads to an installer test sub-mode  328 . This, in turn, then leads to the link mode start-up  330 , as described above. Finally, then in a step  334 , normal system operation occurs, although the system can reset to state  312  or have error messages in the state  326 . 
     In a further embodiment, during the NVM CRC check  316 , the state machine  310  can advance to a NVM programming state  318 . This can occur due to such factors as a failure of a non-volatile memory, or an initial programming of the NVM. In a yet further embodiment, each of these units  155  is programmed to deal with one form of a diagnostic message regarding system errors in the state  326 , and from there to testing the device  290  itself in an OEM test mode  332 . 
     Turning now to  FIG. 3C , illustrated is a state flow diagram  340  for the active subnet controller  230   a  in relation to the unit  155 . Generally, it is the responsibility of the active subnet controller  230   a  to implement proper state transitions. The other units  155  follow the explicit direction of the aSC  230   a  for all valid transactions. These state diagrams are included to help ensure that a state of the unit  155  is the same as the subnet controller. The aSC  230   a  is responsible for device synchronization. If the unit  155  is detected out of synch with the rest of the system, the aSC  230   a , in some embodiments, immediately tries to bring the unit  155  to the current system state, if possible. 
     If an addressable unit  155  is detected in subnet startup  344 , the active subnet controller  230   a  applies asynchronous startup rules, which generally pertain to how many parameters are to be passed between device  290  and the active subnet controller  230 . 
     If an addressable unit  155  is detected in commissioning  345 , installer test  346 , link mode  347  or normal operation  348  substates, the unit  155 , in some embodiments, is brought to the current state via a resend of an “aSC Change State” message, which involves transitioning from a first current aSC state to a second current aSC state. 
     In some embodiments, if a unit  155  is detected in the OEM Test mode  332  or a Soft Disabled state  322  ( FIG. 3B ), the unit  155  shall be reset by the active subnet controller  230   a  in the step  312 . If a unit  155  is detected in “Hard Disabled” or “NVM Programming” state, the active subnet controller  230   a  assumes that it is not available on the subnet. 
     In a further embodiment, inactive subnet controllers  230   i  are required to keep the most up to date subnet and HVAC system configuration information. Inactive subnet controllers  230   i  listen to all UI/G and aSC messages and continuously update their non-volatile memory to attempt to be as consistent as possible with the settings stored in active subnet controller  230 . 
     Aspects of Interface 
       FIG. 3D  illustrates an exemplary HVAC user interface dashboard (“dashboard”)  350  to the user interface  240  to both read and program the active subnet controllers  230   a ,  230   i  and other elements of the HVAC network  200  of the HVAC system  100 . The dashboard  350  can be included within the displays  170 . 
     In the illustrated embodiment, the dashboard  350  includes a weather tab  355 , an indoor humidity tab  360 , an alerts tab  365 , a help tab  370 , an indoor settings tab  375 , a program schedule tab  380 , sometimes referred to herein as a programs tab  380 , a zones tab  385  and a home tab  390 , each of which invokes its own corresponding user or installer interface screen or screens. There can be some redundancy of information or functionality between screens corresponding to the different tabs, but each tab includes screens that contain at least some information or functionality that is not found in any other single tab. Furthermore, each tab can be either invoked by a user, such as through touching a tab, or each tab can be invoked remotely, such as by an installer. 
     Reviewing  FIG. 3D  with aid of  FIGS. 3E-1  and  3 E- 2 , generally, pressing the weather tab  355  advances a user to an exemplary weather screen. The weather screen displays current outdoor weather if a current outdoor temperature and/or humidity is available. 
     Pressing the exemplary indoor humidity tab  360  advances a user to an indoor humidity screen. The humidity screen allows for the user to change a system dehumidify mode. Dehumidify mode selections include: humidify, dehumidify, humidify and dehumidify and off. A user can cycle through these selections. 
     The exemplary indoor humidity screen allows a user to view both absolute and relative humidity, and also to set “setpoints” for absolute and relative humidity (i.e., points at which a humidifier or dehumidifier is turned on and off). In one embodiment, relative humidity (“RH”) can range from 15% to 45% RH and can be either programmed or humidification on demand. Similarly, dehumidification can be from 40-40% RH and can be either programmed dehumidification or demand. 
     An indoor humidity screen also allows a user to view humidification and dehumidification comfort zones. In this context, a comfort zone can be generally defined as a zone of a HVAC system that has separate setpoints for temperature and humidity, etc. 
     Pressing the exemplary alerts tab  365  advances a user to an alerts screen. The alerts screen allows a user to obtain dealer information about currently active alerts and set the dashboard  350  to remind a user later for service alerts. In some embodiments, a select button of the alerts screen of the alerts tab  365  allows the user to obtain a dealer&#39;s contact information. The select button allows the user to clear an active alert (all service alerts and specified critical alerts, and also allows the user to clear an active alert (service or critical)). In some embodiments, when a “new service/critical alert” occurs or “remind later” extension time expires, the dashboard  350  floods any current screen with an alert, in other words, the alert overlays any other screen. 
     An alarm message displays alerts visible to the user, whereas all alerts are visible to the installer. The installer can learn of these alerts either viewing the alerts tab  365  of the dashboard  350  in person or remotely through a message conveyed through the user interface/gateway  250 . 
     Pressing the exemplary help tab  370  advances a user to a help screen. The help screen can include context sensitive help, an option to clear a screen and user system configuration. The context sensitive help presents dialog boxes relating to a current screen&#39;s functions, and user system configurations can provide access to all user local settings (i.e., any setting that does not require an installer to make a change, but can instead by made by a user.) 
     In some embodiments, there can be a time-based notification of consumables in the help screen, either for the user or for an installer. These consumables can include, in some embodiments: media filters, UV bulbs and humidifier pads. All information concerning consumables can be accessible by both the installer as well as the user via the help screen. In some embodiments, a user and installer can enable and manually change the time settings for any timer of the HVAC system  100  through the help screen. Similarly, a maintenance reminder can be accessible by the installer, as well as the user, via the help screen. 
     Pressing the exemplary indoor settings tab  375  advances a user to an indoor settings screen. In one embodiment, the indoor settings screen display indoor temperature measurement and temperature settings. The indoor settings also display the system mode settings and fan mode settings. In one embodiment, system mode selections include: heat, cool, heat and cool, off and emergency heat. Fan mode selections include: automatic, on and circulate. The dashboard  350  allows the user to change the system mode and the fan mode through cycling through various choices. 
     In one embodiment, equipment employed within the system mode dictates which system modes (heat, cool, heat &amp; cool, emergency heat) are visible. For example, a “Heat &amp; Cool” selection of the system mode is visible only when both heating equipment and cooling equipment are present in the system. Typically, the system mode selection of “Off” is always visible. 
     The indoor temperature settings screen also allows a user to change current temperature setpoints, (i.e., points at which a heater or air conditioner is turned on and off) unless this would override a programmed setting, in which case, a hold occurs until an end of the programmed time occurs and the new setpoints become the operating values of the HVAC system  100 . 
     The exemplary dashboard  350  also allows its system mode settings and fan mode settings to be obtained and changed via RSBus devices (e.g. User Interface/Gateway  250  coupled to the bus  180 ) remotely. If the dashboard  350  is requested, remotely or locally, to change the system mode to an invalid setting, the system mode is not changed. 
     Furthermore, the indoor settings tab  375  allows for a user/installer to view all system information and comfort settings (i.e., temperature and humidity) and allow editing of all current settings, as well as fan mode settings. The indoor settings tab  375  allows the fan mode (on, auto, circulate) to be obtained and changed via the RSBus (e.g., via bus  180  and user interface/gateway  250 .) 
     Pressing the exemplary programs tab  380  advances a user to a programs schedule screen. The programs schedule screen allows for viewing/editing/enabling future program schedule events (e.g., temperature setpoints, system modes and fan modes) in the HVAC system  100 . The programs screen allows a programming of event times, temperature setpoints and fan mode for each pre-defined period. A program schedule does not run when the system mode is set to “off.” 
     In one embodiment, the programs screen is seven-day programmable with the ability to select multiple days for programming. In one embodiment, the programs screen is capable of programming up to four (4) events per 24-hour period. In one embodiment, program schedules for temperature setpoints are programmed for a seven day schedule, up to four periods per day and are stored in non-volatile memory. In one embodiment, program schedule events can be set in 15-minute increments of time. The scheduled events execute in order based on time of day. In one embodiment, the user interface  240  provides the capability to enable/disable any period of any given day by pressing the corresponding time button for two seconds. 
     Generally, if a mode changes, such as a fan mode change, is made within the program schedule screen is made while a program schedule of the programs tab  380  is actively executing, a program schedule “hold” mode is invoked until a next program schedule event, at which time the new setpoint is acted upon. If a temperature setpoint change is made while the program schedule of the programs tab  380  is not active, the dashboard  350  updates the display with the new setpoint and acts upon this new setpoint. 
     Generally, the exemplary dashboard  350  allows its programmed temperature setpoints (heat, cool) and modes to be obtained/changed via RSBus devices (e.g. User Interface/Gateway  250  over the bus  180 ) remotely. If the dashboard  350  is requested (remotely or locally) to change either setpoint, either temperature or humidity, to a setting beyond the setpoint limits, the setpoint is not changed. If the dashboard  350  is requested remotely or locally to change the fan mode or system mode to an invalid setting, the fan mode or system mode is not changed. 
     In some embodiments, the cooling setpoint is shown only when cooling equipment is present in the system. Likewise, the heating setpoint is shown only when heating equipment is present in the system. The dashboard  350  may not allow two program scheduled events to begin at the same time. In other words, there can be only one setpoint for either a humidity or a temperature for a given time period—one for each. 
     In one embodiment, up and down arrows of a program screens of the programs tab  380  allows the user to edit a selected box information. A save button allows the user to save changes to the program schedule. A cancel button allows the user to quit the program schedule edit screen without saving changes. A back button returns the user to the program schedule day selection screen. (Not illustrated.) 
     In some embodiments, pressing the zones tab  385  advances a user to a zone screen which, in one embodiment, is accessible only by an installer with a proper key. Generally, the zone screen deals with information that is pertinent to programming HVAC equipment for various environmental “zones” within the HVAC system (e.g., living room, bedroom, kitchen, etc.) The zone screen therefore advises the user to contact the manufacture for more information regarding the zone screen. The zones tab  385  then either advances to a home screen of the programs tab  380  or back to the overall user dashboard  350 . 
     Generally, the home screen of the home tab  390  includes a summary of indoor environmental conditions for a user. A home screen indicates a status of the program schedule (ON, OFF). The home screen indicates temperature control status (heating, cooling, off, waiting) as well as humidity control (humidifying, dehumidifying, waiting) of the HVAC system  100 . In one embodiment, when a given system is set to “off,” only “system is off” is displayed in the home screen. 
     In some embodiments, the dashboard  350  returns to the home screen after 30 seconds has elapsed since a last screen or tab press, including from any other tab of the dashboard  350 . In some embodiments, after a 30 second period of inactivity, any changes made to a screen requiring an active “set” or “save” button press are lost. The dashboard  350  instead returns to the home screen. In some further embodiments, after a user-selectable time period of inactivity, an initial screen press, even upon a tab, causes only a backlight to activate with the home screen as the initial screen shown. The home tab  390  can include a series of screens that are navigable from the home screen via an icon press. 
     Although not illustrated in  FIG. 3D , an installer dashboard including installer screens can also be accessed through the home screen by an installer with a proper key. Generally, the installer screens allow for an installation and configuration of various pieces of equipment in the HVAC system  100 . The installer screens can also enable various default values as parameters of operation. 
     In some embodiments, when a button of a screen of the dashboard  350  is held, the dashboard  350  initially displays an update to the value being changed at a rate of change of 0.5 seconds. After a button hold of 3 seconds, the rate of change is increased to 0.25 seconds. 
     The user dashboard  350  can itself be a color and touch-screen. The dashboard  350  can include a dynamic full color dot matrix LCD display. A touch pad may be built into/over the dashboard  350 . Typically, a maximum delay between any key press and display feedback (indication by selected button, screen change, etc.) is 0.2 seconds. 
       FIG. 4  illustrates a high-level flow diagram  400  of exemplary transitions, for both user and installer, between user interface screens corresponding to various tabs of the exemplary dashboard of  FIG. 3D  and various exemplary interface screens of an interface dashboard of FIGS.  11 A 1  and  11 A 2 . 
     The exemplary flow  400  has an installer screen flow  401  and a user screen flow  451 . The installer screen flow  401  of the dashboard  350  provides access to all installer screens (including subnet start up, configuration, commissioning, installer tests, alerts and diagnostics). The screens of the user screen flow  451  are accessible through the tabs  355 - 390  of  FIG. 3D , with the exception of a new alert screen  452 , which the dashboard  350  generates upon a new alert. In a further embodiment, the dashboard  350  allows each screen of the flow  400  to be invoked remotely by a user and/or installer via the User Interface/Gateway  250 . 
     Upon power-up of the HVAC system  100 , an installation tab  402  of the installer flow  401  appears. Unless an installer inputs a correct key code within a given time period, the flow  400  transitions to a home screen  450 . However, if the installer inputs the correct key, an installer screen corresponding to the installer test tab  404  appears. The installer can then install and configure various devices in the HVAC system  100 . After installation, the installer flow  401  then advances to the home screen  450 . 
     In one embodiment, the installer flow  401  includes a series of screens that are accessible from the home screen  450  via both a) an icon press; and then b) a correct entry of a correct key sequence. In one embodiment, pressing a dealer logo, such as a “Lennox™” logo, on the home screen  450  for 5 seconds allows an installer to execute system startup processes, as well as view/edit the alerts and diagnostics via the installer configuration screens of the flow  401 . 
     Generally, the home screen  450  provides a high level overview of the current indoor conditions. The home screen  450 , in some embodiments, displays the indoor temperature, indoor relative humidity status, outdoor temperature and system status (e.g. heating, cooling, off, humidifying, dehumidifying, etc.) of the HVAC system  100 . 
     From the home screen  450 , a warning screen  412  for an installer can be generated by the dashboard  350 . This warning screen  412  can be conveyed to an installer either directly when installer is present, or through a remote communication, such as over the bus  180  through gateway  250 , and then perhaps through the Internet to the installer. The warning screen  412  generally states that there is a type of problem that should be addressed by an installer, but may not give all details. Once the warning screen  412  is acknowledged by an installer, an alerts tab  408  has a screen that is the default screen for the dashboard  350 . 
     From the warning screen  412 , the installer can also advance to either a diagnostics screen of a diagnostics tab  406 , a contextual help screen of the installer help tab  414 , the installer screen of the installation setup tab  402 , or an installer screen of the installer test tab  404 . 
     In some embodiments, for a user, from the home screen  450 , the new alert screen  452  can arise upon a first detection by the HVAC system  100  of an alert. Similarly, the alerts tab  365  can be used to invoke and view an alerts screen. In one embodiment, the alerts tab  365  can be used to access every other tab in the dashboard  350 . 
     In the illustrated exemplary flow  400 , the home screen  450  transitions to either the alerts tab  365  if an active alert exists or the indoor settings tab  375 . From the indoor settings tab  375 , all other user tabs are also accessible. These include the weather tab  355 , the indoor humidity tab  360 , the alerts tab  365 , the help tab  370 , the programs tab  380  and the zones tab  385 . Please note that, in some embodiments, the zones tab  385  can transition to the home screen  450 , and the zones of the zones tab  385  are typically set by an installer of the HVAC system  100 . 
     Regarding the alerts screen  452 , in one embodiment, if the dashboard  350  is displaying a popup alert at the time when another alert (to be displayed to the user) occurs, the dashboard  350  continues to display the current alert screen  452 . When a current alert has been addressed, the dashboard then overwrites the screen with the newest alert. If multiple popup alerts exist simultaneously, the dashboard  350  displays each (in order of occurrence—timestamp) one-by-one after the previous new alert is addressed. There is not a time-out for a new alert flooding the screen. The new alert remains on the screen of the dashboard  350  until addressed by the user/installer. 
     Turning briefly now to  FIG. 5 , illustrated are exemplary corresponding screens of the tabs of  FIGS. 3D and 4  illustrated in more detail. The weather tab  355  can display weather info when available. The indoor humidity tab  360  enables a user to set humidity modes and setpoints. The alerts tab  365  can display alert info. The home screen  450  can interact with the other illustrated tabs. The indoor settings tab  375  can set display and set temperature conditions and settings (setpoints), overall system mode and fan mode. The programs tab  380  enables a user to program various times. The zones tab  385  forwards an admonition to the user to request more information from the manufacturer, and then transfers back to the home screen  450 . 
     Generally, FIGS.  5 A through  5 D- 2 , to be discussed below, illustrate aspects of the present disclosure that are applicable to at least some, and can be to all, of the user screens of  FIG. 3D  and  FIG. 4 . 
     Turning now to  FIG. 5A , illustrated is an embodiment of the screen  500  of the dashboard  350  that bolds a selected item  501 ,  503 ,  505 ,  507  relative to other selected items in a list in the dashboard  350 . The user can highlight a selected item in white; the other selected items are in grey. 
     Turning now to  FIG. 5B , illustrated is an embodiment of an unlocked screen mode  521 , a partially locked screen mode  523 , and a fully locked screen mode  525  of the dashboard  350 . The partially locked screen mode  523  places a lock-pad icon  526  over a text  524  that states “press for more,” and also deactivates all buttons except up-down arrows  529 . Partially locked mode has a limited functionality. 
     In one embodiment, the fully locked mode  525  deactivates all buttons and removes the up/down arrows from a screen. To unlock the partially locked screen mode  523  or the fully locked screen mode  525 , a user presses and holds the lock-pad icon  526  for a selected period of time, such as five seconds. In one embodiment, the fully locked screen mode  525  can also occur due to a passage of a pre-selected amount of time. The partially locked screen mode  523  or the fully locked screen mode  525  can display control parameters for an extended period of time. 
     Turning to  FIG. 5C , illustrated is an exemplary screen  530  of the dashboard  350  illustrating a display of discovered equipment in the HVAC system  100 . Generally, in prior art interfaces, a text list is used to inform a user/installer about found communicating devices in an HVAC system. However, in  FIG. 5C , icons or pictures of equipment  531 - 535  are used instead to help a user/installer understand what devices and/or equipment is connected to the HVAC system  100 . In the exemplary screen of  FIG. 5C , each of the discovered devices or equipment  531 - 535  has a graphical user interface (“GUI”) for employment by the installer, although other tabs of the dashboard  350  can also employ icons for found or discovered equipment. 
     Turning now to  FIG. 5D-1 , illustrated is an exemplary embodiment of a dashboard  350  having a lighting system  551  including a) a screen  555  that needs a backlight to display information to b) a backlight  557  and c) a motion detector  559 , wherein the backlight is turned on by the motion detector  559  upon a detection of motion within a selected range. The screen  555  can be an LCD screen. 
     Generally, the lighting system  551  allows a user to view indoor settings, without having to touch a button on the dashboard  350 , through employment of the sensor  559  and the backlight  557 . With one embodiment of the system  551 , a home owner can view indoor settings when passing by a dashboard  350 , which activates the sensor  559  which then turns-on the backlight. This allows a viewer to view settings of the dashboard, although indoor, from a distance, as determined by the sensor  559 . This can make for a convenient way for a user to view indoor settings when the backlight  557  is initially off, as it is switched on by the motion detector  559 . Furthermore, the system  551  can conserve energy and screen  555  life when the backlight  557  is not on. 
     When the exemplary dashboard  350  is not being actively engaged by the user (i.e., not being touched through a touch-screen interface and no motion has been detected by the motion detector  559 ), the backlight  557  is off. The screen  555  is then perceived as substantially dark  560 , and no information can be read by a user, as is illustrated in  FIG. 5D-2 . 
     In the system  551 , the motion detector  559  detects movement within a specified distance of the dashboard  350  and commands the backlight  557  to turn on, but otherwise does not allow the backlight  557  to turn on if no motion is detected. For example, in  FIG. 5D-3 , the backlight is off because no movement, such as of a user  562 , is detected within a movement detection zone  561 , and the screen is dark  560 . 
     However, once the movement is detected in the movement detection zone  561  by the motion detector  559 , such as a movement of the user  562 , then the dashboard  350  turns on the backlight  557  so that information can be read from the screen  555  of the dashboard  350 , such as illustrated in  FIG. 5D-4 . The user  562  may, therefore, be able to read the dashboard  350  data on the screen  555  without having to walk up to the dashboard and touch the screen of the dashboard. This can also allow the user  562  to press the dashboard  350  one less time, which can prolong a touch-screen life of the dashboard  350 . When the user  562  walks close enough to the motion detector  559  for the motion detector  559  to detect the user&#39;s movement within the movement detection zone  561 , then the backlight  557  turns on and all buttons and tabs of the dashboard  350  are enabled. However, when the user  562  is out of range of the detection range  561 , the system  551  again disables the backlight  557  and the various tabs, buttons, etc., and the screen is typically again dark  560 , as illustrated in  FIG. 5D-2 . 
     Turning now to  FIG. 5E , illustrated is an exemplary flow of screens  570  of the dashboard  350 . In the exemplary flow, an installer selects an item of the screen  570  of an installer screen through an employment of text  563 , which itself can be a button to select the text. In other flows, the text can be used in other screens of the dashboard  350 . 
     In a further embodiment, the dashboard  350  has a screensaver that activates after a selected amount of inactivity from a user. In this embodiment, the dashboard  350  allows a user to download an image for the dashboard  350  to display when it is idle. Thus, the dashboard  350  can become an equivalent of a digital photo-frame when its controls are not active. In one embodiment, through pressing anywhere on a touch-screen of the dashboard  350  dismisses the screensaver image and re-displays the dashboard  350  controls. 
     Turning now to  FIG. 6A , an exemplary humidity graphic  601  can be used to set humidify and de-humidify setpoints. In humidity screens  617 ,  619  of the humidity tab  360 , a humidity status and RH humidity are both displayed on a same screen of the humidity tab  360 . Generally, a user may not understand what XX % of humidity denotes on his or her dashboard  350 . Therefore, this embodiment of the screens  617 ,  619  both displays the RH and also interprets the RH. 
     In a further embodiment, below 36% the humidity graphic  601  reads “INDOOR RH XX %—DRY,” actual values can be between 35%-37%. Above 49%, the humidity graphic  601  reads “INDOOR RHXX %”—HUMID., actual value can be between 48% and 50%. Between 36% and 49% RH, the display reads “INDOOR RH XX %—NORMAL” or “INDOOR RH XX % OK”, actual values can be between 35% and 50%. 
     An exemplary indoor humidity graphic shows a single bar  602  with relative humidity (“RH”) being a calibrated item. A left side  603  of the bar  602  displays a current indoor RH level with the use of a triangle  605 , and a right side  604  uses a triangle  607  to show a current humidify or dehumidify setpoint. Two up/down arrows  608  adjust a humidity setpoint, and a switch button  613  transitions the humidity graphic  601  to display either humidify comfort range setpoint or a de-humidify comfort range setpoint. In other words, the humidity graphic  601  can transition from the humidity screen  617  to a dehumidify screen  619 . 
     Turning now to  FIGS. 6B-1  through  6 B- 4 , illustrated is an employment of one a plurality of exemplary screens  631  of a humidity tab  360  of  FIG. 3D  that is dependent upon equipment installed in the HVAC system  100  of  FIG. 1 . In other words, if a given piece of equipment is not installed in the HVAC system  100 , an indicia of that piece of equipment is not illustrated on the humidity screen of the humidity tab  360 . 
     For example, the indoor humidity tab  360  can be dependent on humidifiers and cooling equipment. Without cooling, equipment, de-humidification is not an option. Furthermore, the indoor settings tab  375  is dependent on heating and cooling equipment, and so is the programs tab  380 . Therefore, the dashboard  350  removes modes, system setting options, and control setpoints (humidity and temperature) based upon which pieces of equipment to be discovered during an “installation and set-up process” are not actually discovered. Therefore, if a given piece of humidification or dehumidification equipment is not present, it may not be displayed in the screens  631 . 
     For example,  FIG. 6B-1  shows an indoor humidity screen  633   a , an indoor setting screen  633   b , a programs summary screen  633   c  and a programs input screen  633   d  with all options and services available.  FIG. 6B-2  shows equivalent screens, here designated  635   a - 635   d , based on only heating equipment and a humidifier being installed.  FIG. 6B-3  shows equivalent screens, here designated  637   a - 637   d , based on only cooling equipment being installed, without a humidifier. Finally,  FIG. 6B-4  shows the indoor humidity screen, here designated  639 , for which only heating equipment is installed, without a humidifier. As is illustrated, equipment that is not available is not illustrated. In further embodiments, interface screens correlating to indoor settings tab  375  and programs tab  380  do not display indicia of devices not installed in the HVAC system  100 , either. 
     In a further embodiment, the humidity tab  360  allows users to have and configure different humidity levels during different periods of a day. These periods could be a wake, leave, return and sleep period, for example. For an exemplary instance of use, a user can have 40% humidity level in the morning, and 45% humidity level at night in the same day. Additionally, users can have different humidity levels for different days or group of days. Some parts of the country can have changes in its humidity level throughout the day, so therefore users who reside in these areas can maintain their comfort inside of their homes by using this feature. 
     Turning now to FIGS.  7 Ai through  7 Aiv and FIGS.  7 Bi through  7 Biv, illustrated are an exemplary flows of various transitions of a help screen having a help tab  370  of the dashboard  350  that are dependent upon or otherwise determined at least in part by a screen displayed before the help tab  370  is activated. 
     Generally, a purpose of interactive help for the HVAC system  100  is for a user or installer to navigate throughout the dashboard  350  without the user or installer having to go find a manual and look up a particular function or dashboard  350  screen shot. Discussed below are an exemplary flow  710  and a flow  750 , both to help accomplish this goal of navigation. 
     FIGS.  7 Ai through  7 Aiv, collectively referred to as  FIG. 7A  corresponds to an example flow  710 . FIGS.  7 Bi though  7 Biv, collectively referred to as  FIG. 7B , corresponds to an example flow  750 , Both the flows  710 ,  750  allow a user to get help on current dashboard screens without changing his or her current dashboard  350  settings. A help interface can therefore be located in the dashboard  350 , and the user/installer does not necessarily have to find or use an independent manual. 
     An approach of the exemplary flow  710  of  FIG. 7A  is directed towards dependent settings for help screen sequences. The flow  710  illustrates help screens that progress in a predetermined sequence depending on the screen shown before the help tab  370  is pressed. Generally, help is supposed to teach a user and not confuse them more; therefore, help in the flow  710  does not display information about possible settings that were not displayed on the screen before the help tab was pressed. 
     For example, the exemplary flow  710  displays  3  different screens  711  (FIG.  7 Ai),  712  (FIG.  7 Aii),  713  (FIG.  7 Aiii) that could be displayed to a user before a help tab  370  is pressed. After the help tab  370  is pressed, the screen transitions as follows: the screen  711  transitions to a screen  714  (FIG.  7 Ai); the screen  712  transitions to a screen  715  (FIG.  7 Aii); and the screen  713  transitions to a screen  716  (FIG.  7 Aiii). Thus, each screen  711 ,  712 ,  713  progresses to its corresponding particular screen  714 ,  715 ,  716 , respectively, that contains information specific to the screen transitioned from. The help screens  714 ,  715 ,  716  each contain a text box and arrows that give information about a particular area of the screen that was present before the help was invoked. 
     Pressing anywhere on a help screen  714 ,  715 ,  716  transitions the help screen to a screen  717  (FIG.  7 Aiv). This particular screen  717  is used for all the screens  711 ,  712 ,  713 , because the screen  717  row C provides information about a common item for all the screens  711 ,  712 ,  713 . 
     Touching the screen  717  transitions to a screen  718 , (FIG.  7 Aiv). This is yet another screen that displays common information for all the screens  711 ,  712 ,  713 . A screen  718  (FIG.  7 Aiv) is the last screen in the help sequence  710 . Pressing the screen  717  of the dashboard  350  transitions back to the screen displayed before the help tab  370  was pressed, via a step  720 . 
     Turning now in a further embodiment to FIGS.  7 Bi through  7 Biv, collectively referred to as  FIG. 7B , help screens of the help tab  370  allows a user to adjust settings on a help screen without saving changes to the settings to the HVAC system  100 . Generally, once the user exits a help screen, all the settings or screen changes return to their previous state before the help tab  370  was pressed, which allows a user to experiment with settings of a screen without saving them to the HVAC system  100 . 
     An exemplary screen  751  of the flow  750  of  FIG. 7B  is the screen displayed on the dashboard before a help tab  370  press. A screen  752  is the screen displayed immediately after a help tab  370  is pressed. A difference between screen  751  and  752  of flow  750  is a text box. 
     The text box on screen  752  gives a brief explanation about a current screen, and tells the user to touch an area of interest to get more information. Assuming that a user wants to know more about “current temp” and pressed in this area, for example, then the screen progresses to a screen  753  (FIG.  7 Bii) with a new text box listing information about “current temp.” 
     A screen  754  is shown after the “fan setting” area is touched. However, this area of the screen contains a select button. In one embodiment, pressing the select button changes the screen to a screen  755  (FIG.  7 Biii) with a new text box listing information about the new setting. The transition from the screen  754  to the screen  755  not only shows a new text box, but it also changes the highlighted setting from “on” to “circulate.” In one embodiment, the screen  755  transitions to a screen  756  (FIG.  7 Biii) if the system setting area is pressed. In one embodiment the screen  756  transitions to a screen  757  (FIG.  7 Biv) if the select button is pressed. However, the screen  757  transitions back to the screen  751  of FIG.  7 Bi, the screen displayed on the dashboard before the help tab  370  press. 
     Turning now to  FIGS. 8A-8D , illustrated are various views of a screen  831  dependent upon equipment being found in the HVAC system  100  of  FIG. 1 , as discussed regarding the screens  631  of  FIGS. 6B-1  through  6 B- 4 , above. In  FIG. 8A-8C , a screen  83 *a is an indoor humidity screen, a screen  83 *b is an indoor settings screen, a screen  83 *c is a program summary screen, and a screen  83 *d is a program input screen. 
     Regarding  FIG. 8A , screens  833   a - 833   d  show the screen  831  all options and services available. In  FIG. 8B , screens  835   a - 835   d  illustrate the screen  831  for the case in which no cooling equipment is installed. In  FIG. 8C , screens  837   a - 837   d  illustrate the screen  831  for the case in which no heating equipment is installed. And  FIG. 8D  illustrates an indoor humidity screen  839  reflecting the case in which heating equipment is installed but no humidifier is installed. As is illustrated, equipment that is not available is not shown in the screen  831 . 
     Turning to  FIG. 9A , illustrated is an exemplary programs screen  910  of the programs tab  380  that displays all program time periods and programmed temperature setpoints for the programs tab  380 . In this embodiment, all program schedule setpoints  912 ,  914 ,  916 ,  918  are displayed on one programs screen  910 . All time periods for a program schedule are displayed as well. In the illustrated embodiment of the screen  910  of the programs tab  380 , time is listed first, then heat temperature, cool temperature, and fan settings are last. The screen  910  can be a 4×4 matrix with only one setpoint area/button being selectable at a time. In one embodiment, once a setpoint area is touched, the box turns an inverse of its current color. In the illustrated embodiment, up/down arrows  921  are used to adjust each setpoint/setting. 
     Turning now to  FIGS. 9B-1  and  9 B- 2 , illustrated is an exemplary flow  930  of programs screens. The screens of the programs tab  380  include buttons  933  that turn an inverse color as a selection and touch reaction. For example,  FIG. 9B-1  illustrates a programs screen  932  with a particular button  933  not being touched. A programs screen  934  illustrates the case that a button  935  being touched, and turning an inverse color. In  FIG. 9B-2 , a screen  936  illustrates the button  935  staying an inverse color, and an arrow button  937  turning an inverse color. A screen  938  illustrates that the button  935  stays the inverse color, but an arrow button  939  reverts to its previous color. 
     In one embodiment, any touched button of the buttons  933  of the flow  930  turns an inverse color while being touched. If the button could be adjusted to another value, then the button/selection box remains inverted as to color even when the user is no longer touching the button, such as the button  935 . However, if the button is an up/down arrow, for example the button  937 , then the button only turns inverse while the user is touching that button. In other words, when the user releases the button, such as an up/down button, then the button returns to its normal color/state, as illustrated by the button  939 . In other embodiments, the button color inverse can occur in other tabs, such as the home tab, the humidity tab, and so on. 
     Turning now to  FIG. 9C , illustrated is a program schedule in a programs screen  940  of the programs tab  380  partitioned into a plurality of time zones wherein, upon a button corresponding to a time zone  941  being pressed for a set period of time: a) a temperature setpoint for that time period is deactivated, b) a display of the deactivated setpoints of the deactivated time period now appears dim relative to a display of the time period&#39;s setpoints before deactivation; and c) the deactivated time period&#39;s setpoints  943  appear dimmer relative to an active time period&#39;s setpoints. 
     In the illustrated embodiment of  FIG. 9C , if one of the time zones  941  is pressed and held for approximately two seconds, then the setpoints for that time period  943  is deactivated. In one embodiment, the time period  943  is then controlled by the previous time period&#39;s setpoints. 
     Turning now to  FIG. 9D-1 , illustrated is an interface  950  for setting a system time for an HVAC system  100 , such as through a programs screen of the programs tab  380 . Setting a system time involves 6 boxes. Each box contains a particular aspect of time and date. Only one box can be changed by a user at a time.  FIG. 9D-1  generally discloses an analog clock interface  950  with date and time selection boxes. The date and time selection boxes are as follows: hour box  961 , minute box  962 , AM/PM box  963 , month box  964 , day box  965  and year box  966 . 
     Generally, in the clock interface  950 , the hands  958 ,  959  of the clock interface  950  are moved by touching them and dragging them to a desired position, either through a touch screen or with a device such as a trackball. The hour hand  958  and the minute hand  959  are linked to their corresponding boxes  961 ,  962 , and the boxes  961 ,  962  change if their corresponding hands are adjusted. For example, if the hour hand  958  is changed from “12” to “6,” then the hour box  961  changes from “12” to “6.” The up and down arrows  960  can also be used to adjust each interface box. Typically, in the interface  950 , at least one value of at least one interface box is changed as a user drags at least one clock hand of the analog clock. Generally, in the interface  950 , at least one value of at least one number itself is used as an input to a box, and the analog clock face maps to the changed value. 
     Turning now to the clock interface  965  of  FIG. 9D-2 , the clock face numbers themselves are used as buttons, a selection of any of which define where clock hands  973 ,  974  point and values in boxes  971 ,  972 . Either the hour  971  or minute  972  box is selected, and then the desired number on the clock face is pressed, upon which both the hour hand  973  or minute hand  974  jump to that setting, and boxes  971 ,  972  fill in for that value. For example, if the hour box  971  is selected and the current setting is “5,” and then the clock face number “10” is pressed, then both the hour hand  973  jumps to “10” and the hour box  971  adjusts to “10.” The up and down arrows  960  can be used to adjust each box. 
     Turning now to  FIG. 9E , illustrated is an embodiment of a programs screen of the programs tab  380  and a reset interface  975  for the same. Generally, the reset interface  975  of  FIG. 9E  can help a user reset to predetermined default setting, such as a factory setting  976  or another custom setting  977 , when a user inadvertently changes one or more settings, or otherwise wishes to go back to these settings. Without the reset interface  975 , a user might have to spend a considerable amount of time reviewing an owner manual and/or scrolling through a plurality of menus to locate the erroneous or unwanted settings, and may not know what the reset settings even are. As is illustrated, there are different selections for settings, temperature, clock, daylight savings time, display and backlight. 
     All buttons in  FIG. 9E  that are in grey represent an exemplary set of employed reset values or parameters as currently selected in the illustrated exemplary reset interface  975  upon an exit from the reset interface  975 . These reset selections are employed by the HVAC system  100 . These reset values over-ride whatever is currently being employed in the HVAC system  100 . However, any reset value may be changed, as described below. 
     Generally, the reset interface  975  can select from a default value among the following values: a user can reset the dashboard  350  to the factory setting  976  or to another value, such as the custom value  977  programmed by an installer. For example, if programming or operating becomes confusing or other issues occur, the customer can reset the values to these prior settings. The reset screen  975  provides a reset unit of measurement in either the British unit (Fahrenheit)  978  or a S.I.  979  unit (Celsius). 
     The user may select a reset to a 12 hour  980  or 24 hour  981  clock. If users prefer the 24 hour clock rather than the “12” hour clock, he or she can do so via this change. The user can also adjust or correct the time, for any reason, including daylight savings times  982 ,  983 . 
     A user may also set the default language: the consumer or dealer can reset to an exemplary preferred language  984 - 987  or change it, if needed. The customer can reset the backlight brightness, such as backlighting for high  991 , medium  990 , low  989 , or off  988 . 
     Generally, when the installer first installs the equipment, the installer will be able to set all parameters outlined above as part of the initial set up and commissioning of the dashboard and system. An installer or user can save the settings through a save button  992 , or exit with an exit button  993 . When the settings are saved, this over-rides any other programming or configuration in the HVAC system  100 . 
     Turning now to  FIG. 9F , illustrated is an exemplary programs screen that further includes a display of a plurality of pre-populated program schedule settings. The pre-populated program settings selection choices range from a maximum comfort  994  to a maximum energy savings  998  of the range. The settings employ a slider  992  between the maximum comfort setting  994  to the maximum energy savings  998  of the selection based upon a selector  999 . Furthermore, based on a selection of a user, a program schedule of the programs tab  380  automatically populates temperature and humidity settings for each program scheduled event, to achieve a desired selection. This can occur in the programmed setpoints for both temperature and humidity, and further embodiments can include the activation or deactivation of pieces of various environmental equipment, such as heaters, coolers, fan blowers, humidifiers, dehumidifiers, etc. 
     Turning now to FIGS.  9 Fi and  9 Fii, illustrated are exemplary flows of programming screens that can be used with this embodiment. In flow  1000  of FIG.  9 Fi, for a dashboard  350  that is running a program schedule, and flow  1006  of FIG.  9 Fii, for an embodiment of the dashboard  350  that is not running a program schedule, instead of a user directly entering the necessary values, the user instead sets the slider  992  of  FIG. 9F , and the values are entered into these screens by the slider  992 . The flow  1000  has a screen  1001 ,  1002 ,  1003 ,  1004 , and  1005 . The flow  1006  has a screen  1007 ,  1008  and  1009 . 
     In one embodiment, if a change of operating parameters is made in the programs screen of the programs tab  380  while a current program is running which employs previously entered parameters, a hold time can be programmed within the programs tab  380 , wherein the hold time is entered as exactly what time the previous parameters are to stop taking effect. 
     In a further embodiment, the dashboard  350  has to set parameters/settings for all devices in the HVAC system  100 . There are a few parameters, such as for a blower, that have large ranges that can be very time consuming to set with up and down arrows. Therefore, a coarse scroll bar and a fine scroll bar can be used to adjust such settings (not illustrated). First, the coarse bar is adjusted to get close to the desired range, and then the fine bar is adjusted to get to the exact and precise settings. This can be done by a dashboard  350  that is or includes a touch-screen. 
     Turning now to  FIG. 10A , illustrated is an exemplary flow  1010  employing the home screen  450 . In a first screen  1015 , a particular icon  1017 , such as the “Lennox”™ icon, is placed on the home screen  450  to enable an access of an installer screen. In  FIG. 10A , in order to access an installer screen from the home screen  450 , an installer is to both a) press and hold the icon  1017  with a finger for at least five seconds; and then b) drag the finger across the interface, as illustrated in screen  1020 . The button hold and drag is to be performed without lifting a finger for the installer screens to be accessible from the home screen. Otherwise, the screen  1015  generates a warning screen  1025 . 
     In a further embodiment, the dashboard  350 , such as in the home screen  450 , has a single alert icon  1018  that gives a user an indication that there is at least one alert present. In one embodiment, the alert icon  1018  is one of three colors: a) a first color to indicate that the HVAC system  100  is currently running in an energy efficient mode; b) a second color to indicate that a filter of the HVAC system  100  needs to be replaced; and c) a third color to indicate that a piece of equipment is no longer working. 
     Pressing the alert icon  1018  directly navigates to a display page on the dashboard  350 , such as found in the alerts tab  365 , giving a user: a) more information about at the least one alert; b) the ability to clear the at least one alert; or c) to set a reminder time for a later date for the at least one alert. 
     Furthermore, a color of the alert icon  1018  can be changed to signal a different level of severity alert that is present. For example, a “green” alert icon  1018  could signal that the HVAC system  100  is currently running in an energy efficient mode. A “yellow” alert icon  1018  could signal that a filter needs to be replaced. A “red” alert icon  1018  could signal that a critical piece of equipment is no longer working. 
     Turning to  FIG. 10B , illustrated is an exemplary flow  1030  that transitions from a home screen  450  to a tabbed interface  1040 . In  FIG. 10B , if a user touches anywhere that is not a button, such as an area  1035 , a tabbed interface  1040  arises, each of the interfaces (humidity screen, help screen, etc.) accessible through its corresponding tab  355 - 390 . 
     Generally, the flow  1030  gives a user a straightforward interface that can easily get indoor settings and system information. With a simple screen press, such as in an area  1035 , a user can get the tabbed interface  1040 , thereby allowing a change of a system or mode setting, or to otherwise get more detailed information about aspects of the HVAC system  100 . 
     The home screen with the tabbed interface  1040  of  FIG. 10B  also allows the user to change a current temperature setpoint without necessarily having to deal with much further information. Therefore, all a user needs to do is press anywhere inside an “indoor conditions” area (that is not a button) and the home screen  450  transitions to the tabbed interface  1040  where all indoor settings can be changed in the indoor settings tab  375  and more detailed information can be obtained. 
     In a further embodiment, the home screen  450  can be a “default screen” for the dashboard  350  and gives the user general information about indoor conditions. In a still further embodiment, an icon of the home screen  450  is correlated to at least one HVAC system mode or fan mode. In this embodiment, for example, a fan icon can be used to represent a touch area for a user to press if the user wants to change a fan schedule in the dashboard  350 . Similarly, in some embodiments, a “flame and flake” icon can be used to represent a system mode button that a user may wish to change. 
     In a yet further embodiment of the home screen  450 , at least one attribute of a presentation of the home screen is selectable by a user. For example, differing presentations can be mode of comfort backgrounds. One example could be a black and white screen for a background of the home screen  450 ; another example could be use of a larger font size on the home screen  450 , etc. 
     Turning now to  FIGS. 11A-1  and  11 A- 2 , illustrated are two exemplary embodiments of an installer dashboard  1030  to be used in conjugation with the installer flow  401  and its various tabs and screens. The installer dashboard  1030  can be considered a subset of the dashboard  350 , and is contained within the dashboard  350 , although both the dashboard  350  and the installer dashboard  1030  are accessible remotely. 
     Pressing the installation setup tab  402  can change the active tab to an installation setup screen of the installer screen flow  401 . In some embodiments, when accessing the installer screens, the dashboard  350  defaults to showing the installation setup tab  402  as active. 
     Pressing the tests tab  404  can change the active tab to an installer tests screen of the installer screen flow  401 . Pressing the installer help tab  414  provides “context sensitive” help that presents dialog boxes relating to current screen functions regarding installation of the installer screen flow  401 . Pressing the alerts tab  408  changes the active tab to the (installer) alerts screen of the installer screen flow  401 . The diagnostic tab  406  is only active once the HVAC system  100  has been configured. Pressing the diagnostic tab  406  changes the active tab to the diagnostics screen of the installer screen flow  401 . Pressing the exit tab  1107  advances the installer to the home screen  450 —leaving the installer screens. If available, pressing the start tab  1105  allows the HVAC system  100  to begin operating. 
     Turning now to  FIG. 11B , illustrated is an installation and setup screen  1120  that displays minimum  1127 , maximum  1129 , current  1130  and default  1131  values on one screen for a device setting in an installation screen of the installer screen flow  401  for a particular device in the HVAC network  200  of the HVAC system  100 . In one embodiment, the device to be installed sends a message to the dashboard  350  with the minimum, maximum and factory default values. In a further embodiment, the device to be installed can send increment values. The setup screen  1120  then displays all of this information to the installer. This gives the installer better information to set device parameters. 
     Turning now to  FIG. 11C , illustrated is an exemplary installer screen  1140  illustrating an underlining  1141  of factory default settings for device parameters of the HVAC system  100 . Generally, when multiple settings are displayed on one screen, under-lining  1141  one of the listings allows an installer to know what the factory default setting is, even when a separate entry  1142  is an option that is currently installed. 
     Turning now to  FIGS. 11D-1  and  11 D- 2 , illustrated is a flow  1155  wherein a device within the HVAC system  100  to be diagnosed in the installer screen  1140  is moved as text by a finger movement from a left part  1191  of the installer screen  1140  to a right part  1196  of the installer screen  1140 . 
     In some embodiments, this approach does not need a select button or a remove button. Instead, an installer touches a desired item/device, such as item  1194  ( FIG. 11D-1 ), and drags the text or icon to the right part  1196 , creating an absence  1195 , and then releases ( FIG. 11D-2 ). Once the device is on the right part  1196 , it is no longer on the left part  1191 , and a start button  1197  appears, letting the installer know that the installer may proceed with diagnostics. To remove the selected item, simply drag it back to a list on the left part  1191 . 
     Turning now to  FIG. 12 , illustrated is an exemplary method  1200  for operating and/or providing a visual interface for an HVAC network of an HVAC system, such as the HVAC network  200 . 
     In a step  1201 , a weather tab that invokes a weather screen is provided. In a step  1220 , an indoor humidity tab that invokes an alert screen is provided, wherein invoking the indoor humidity tab advances to a humidity screen which displays at least a current indoor humidity. In step  1230 , an alerts tab that invokes an alerts screen is provided. In a step  1240 , a help tab that invokes a help screen is provided, wherein invoking the help tab advances to a help screen that provides context sensitive help that presents at least one dialog box related to a function of a current screen. In a step  1250 , an indoor settings tab invokes an indoor setting screen which includes a current indoor temperature. In a step  1260 , a programs tab that invokes a programs screen is provided which can program at least one of a) time b) temperature setpoints and c) heating/cooling setpoints. In a step  1270 , a home tab provides a summary of indoor conditions. In a step  1280 , at least one of the screens from the above steps is invoked. 
     In a further embodiment of the method  1200 , step  1270  further provides wherein the home tab can advance to an installer dashboard that can be accessed only by an entry of a key, wherein the key is entered by an installer. In a further embodiment of method  1200 , step  1260  further provides that, upon a time zone being pressed for a set period of time in the programs screen: a) a temperature setpoint for that time period is deactivated; b) a display of the deactivated setpoints of the deactivated time period appear dim relative to a display of the time period setpoints before deactivation; and c) the deactivated time period&#39;s setpoints appear dimmer relative to an active time periods setpoints. Step  1260  also still further provides a display of a plurality of pre-populated program schedule settings. 
     The method  1200  yet further includes a further embodiment of step  1240 , wherein the help screen further displays settings dependent upon a screen displayed before the help screen is invoked. A still further embodiment of the method  1220  includes a further embodiment of step  1220 , wherein the humidity screen allows users to program different humidity levels for different periods of a day. A yet still further embodiment of step  1250 , wherein for a given piece of equipment to be offered to a user, a corresponding piece of equipment is installed in the HVAC dashboard. 
     Turning now to  FIGS. 13A and 13B , illustrated is an exemplary flow diagram  1300  illustrating a subnet controller controlling a user interface display, which in some embodiments can be used in conjunction with or as a further embodiment of the method  1200 . 
     Message(s)  1 : subnet controller  1310  tells UI  1320  to display a specific screen and instructs it how to fill the data fields (TITLE, FIELDx, VALUEx, UNITx field as well as instructions on Buttons—how many there are, what their caption is). For example, to fill FIELD2 use UI string numbers 1234, to fill VALUE2 field, look at message with ID 12093 and starting bit 16 (3 rd  byte of the message) take 16 bits out and interpret them as unsigned int (16 bit), to fill UNIT2 field, use units of F/C (indicates temperature, for example.) 
     Message(s)  2 : subnet controller  1310  tells device(s)  1330  to start operating—performing whatever test they are to perform. 
     Message(s)  3 : device(s)  1330  broadcast their status and/or diagnostic messages and the UI  1320  interprets and displays the data, as it was taught by message(s)  1 . 
     Message(s)  4 : UI  1320  lets the subnet controller  1310  know which button was pressed, the subnet controller  1310  interprets this as either a SKIP TEST (go to the next one, or if on the last one, go to the results page), TEST PASSED or TEST FAILED, as appropriate. After this, the whole process repeats for all tests. An exemplary user interface screen shot after completion of a test can be seen in  FIG. 13B . 
     Those skilled in the art to which this application relates will appreciate that other and further additions, deletions, substitutions and modifications may be made to the described embodiments.