Increasingly, electronic components are being relied upon to facilitate the operation of a vehicle. These electronic components aid in the development of sophisticated vehicle systems such as collision detection systems, automated cruise control systems, global positioning navigation, and the like. In this regard, systems have been developed that allow electronic components to communicate in accordance with standard protocols. For example, a sensor, which may have been developed by an engine manufacturer, may encapsulate and transmit data in accordance with a standard protocol. A cab-mounted electronic control unit developed by a different entity may receive and process the received data. Since standard communication protocols exist, components from different manufacturers are able to communicate so that readings may be presented to a vehicle operator.
A graphical display within an interior surface of a vehicle is provided to convey information to a vehicle operator. With the continued development of sophisticated vehicle systems, increasing amounts of information about vehicle conditions should be accessible to a vehicle operator. However, limitations in display area size may preclude the display of some readings that describe all vehicle conditions.
This summary is provided to introduce a selection of concepts in a simplified form that are further described below in the Detailed Description. This summary is not intended to identify key features of the claimed subject matter nor is it intended to be used as an aid in determining the scope of the claimed subject matter.
Aspects of the disclosed subject matter are directed to a graphical display that efficiently conveys information to a vehicle operator. In accordance with one embodiment, a method is provided that presents scrollable graphical elements on a shared screen area. More specifically, the method includes assigning a priority level to scrollable graphical elements that convey vehicle readings on the graphical display. Then, the one or more scrollable graphical elements are rendered on the graphical display at locations that change locations periodically. When an abnormal vehicle reading is identified, the method dynamically assigns an enhanced priority level to the scrollable graphical element that is configured to convey the abnormal vehicle reading. If the scrollable graphical element is currently assigned an off-screen location, the method causes the scrollable graphical element to be rendered.
The foregoing aspects and many of the attendant advantages of the disclosed subject matter will become more readily appreciated as the same become better understood by reference to the following detailed description, when taken in conjunction with the accompanying drawings, wherein:
Prior to discussing the details of the graphical display with scrollable graphical elements, it should be understood that the following description is presented largely in terms of logic and operations that may be performed by conventional components. These components, which may be grouped in a single location or distributed over a wide area, generally include processors, memory, storage devices, display panels, input devices, etc. In circumstances where the components are distributed, the components are accessible to each other via communication links. In the following description, numerous specific details are set forth in order to provide a description of the graphical display with scrollable graphical elements. It will be apparent to one skilled in the art, however, that the disclosed subject matter may be practiced without some or all of the specific details.
As further illustrated in
In the illustrative embodiment depicted in
In the illustrative embodiment depicted in
As further illustrated in
As will be appreciated by those skilled in the art and others,
Now, with reference to
In the exemplary embodiment depicted in
In the exemplary embodiment depicted in
In one embodiment, the locations in which the graphical elements are rendered on the shared screen area 206 transition after a predetermined period of time. In addition or alternatively, a vehicle operator may activate a hardware-based control to scroll through and access desired readings. For example, a revolving hardware wheel (not illustrated) may be provided within the console of the vehicle. The vehicle operator may rotate the hardware-based wheel in order to cause corresponding transitions to the graphical elements that are displayed on the shared screen area 206. Those skilled in the art and others will recognize that other types of controls may be used to obtain user input without departing from the scope of the claimed subject matter.
Now with reference to
While specific configurations of the graphical display 108 have been described above with reference to
Now with reference to
As illustrated in
As further illustrated in
The graphical elements rendered, at block 306, include at least one scrollable graphical element that is selectively displayed as described above with reference to
At block 308 of the display method 300, a triggering event is detected that will instigate a change in how scrollable graphical elements are rendered. As described above with reference to
At decision block 310 of the display method 300, a test is performed to determine whether the triggering event, detected at block 308, relates to an abnormal vehicle condition. To determine whether an abnormal vehicle condition exists, data collected by the electronic control unit 106 may be compared to a set of data that define normal operating parameters. For example, a component or vehicle manufacture may establish normal operating parameters for various components and systems. These parameters may be compared to actual readings being reported by the information generating components 110. In instances when an actual reading is outside a normal range, the result of the test performed at block 310 is “Yes.” In this instance, when an abnormal vehicle condition is the triggering event, the display method 300 proceeds to block 312. In contrast, if the triggering event relates to the periodic rotation of scrollable graphical elements, then the result of the test performed at block 310 is “No.” In this instance, the display method 300 proceeds to block 314, described in further detail below.
At block 312 of the display method 300, a scrollable graphical element associated with the abnormal vehicle condition is assigned an enhanced priority level. The priority levels assigned may depend on which vehicle component or system experienced the abnormal vehicle condition. In addition, the priority level assigned may depend on the extent in which a reading diverges from normal parameters. For example, the detection of a transmission temperature that diverges substantially from a normal reading may be assigned an enhanced priority level that is indicative of a critical condition. A tire pressure reading that diverges a small amount from normal parameters may be assigned an enhanced priority level that is lower than a high transmission temperature. Moreover, a manufacturer, fleet operator, and/or user may define which priority levels will be assigned to various abnormal vehicle conditions. In any event, upon detection of an abnormal vehicle condition, a scrollable graphical element associated with the abnormal condition is assigned an enhanced priority level at block 312.
At block 314 of the display method 300, logic for implementing a transition to the rendering of scrollable graphical elements is executed. In one type of transition, scrollable graphical elements are moved to successive locations on a “virtual” wheel. In this instance, the scrollable graphical elements are depicted at a particular location for a predetermined period of time (i.e., two seconds). Then, a transition occurs in which one or more of the scrollable graphical elements move to the next successive location. This type of transition will typically result in at least one scrollable graphical element transitioning to an “off-screen” location. Moreover, at least one scrollable graphical element that was not previously displayed is moved to an “on-screen” location.
In another embodiment, the transition performed at block 314 involves displaying a scrollable graphical element to convey information about an abnormal vehicle condition. In the example described above with reference to
The logic for implementing a transition executed at block 314 may involve setting/changing the visual attributes of a scrollable graphical element. The visual attributes of a scrollable graphical element may be based on an assigned priority level. For example, if a scrollable graphical element (i.e., “TRANS. TEMP.” graphical element 220) is associated with an enhanced priority level that is critical, it may be displayed in a first color (i.e., red) to provide a strong visual indicator of the critical condition. On the other hand, if the condition is less critical but still abnormal, the scrollable graphical element may be displayed in a second color (e.g., yellow) to provide a warning to the vehicle operator. Moreover, logic for implementing the transition executed at block 314 may affect the visual attributes of scrollable graphical elements in other ways. For example, upon detection of an abnormal vehicle condition, the transition may change other visual attributes (i.e., size, contrast ratio, flashing, opacity, etc.) of a scrollable graphical element. Then, once the logic for implementing the transition is executed, the display method 300 proceeds to block 316, where it terminates.
It should be well understood that the display method 300 described above with reference to
While illustrative embodiments have been illustrated and described, it will be appreciated that various changes can be made therein without departing from the spirit and scope of the disclosed subject matter.
Number | Name | Date | Kind |
---|---|---|---|
4072924 | Pomerantz | Feb 1978 | A |
4287503 | Sumida | Sep 1981 | A |
4621306 | Sell | Nov 1986 | A |
4787039 | Murata | Nov 1988 | A |
4787040 | Ames | Nov 1988 | A |
4809177 | Windle | Feb 1989 | A |
5241295 | Madau | Aug 1993 | A |
5347260 | Ginzel | Sep 1994 | A |
5371487 | Hoffman | Dec 1994 | A |
5453939 | Hoffman | Sep 1995 | A |
5555502 | Opel | Sep 1996 | A |
5757268 | Toffolo | May 1998 | A |
5764139 | Nojima | Jun 1998 | A |
5949346 | Suzuki | Sep 1999 | A |
5982352 | Pryor | Nov 1999 | A |
6008800 | Pryor | Dec 1999 | A |
6009355 | Obradovich | Dec 1999 | A |
6119060 | Takayama | Sep 2000 | A |
6289332 | Menig | Sep 2001 | B2 |
6429845 | Unseld | Aug 2002 | B1 |
6434450 | Griffin, Jr. | Aug 2002 | B1 |
6564112 | Factor | May 2003 | B1 |
6667726 | Damiani | Dec 2003 | B1 |
6693523 | Abel | Feb 2004 | B1 |
6788196 | Ueda | Sep 2004 | B2 |
6812942 | Ribak | Nov 2004 | B2 |
6819056 | Lin | Nov 2004 | B2 |
6870469 | Ueda | Mar 2005 | B2 |
6874012 | St. Pierre | Mar 2005 | B1 |
6959223 | Ogasawara | Oct 2005 | B2 |
6972665 | Wang | Dec 2005 | B2 |
6990922 | Ichikawa | Jan 2006 | B2 |
7009504 | Banter | Mar 2006 | B1 |
7015891 | Lo | Mar 2006 | B2 |
7084859 | Pryor | Aug 2006 | B1 |
7310071 | Cuprys | Dec 2007 | B2 |
7499778 | Obradovich | Mar 2009 | B2 |
7609152 | Crowe | Oct 2009 | B2 |
7642901 | Kato | Jan 2010 | B2 |
7683771 | Loeb | Mar 2010 | B1 |
7730401 | Gillespie | Jun 2010 | B2 |
8125346 | Ballard | Feb 2012 | B2 |
20010012976 | Menig | Aug 2001 | A1 |
20040140948 | Cuprys | Jul 2004 | A1 |
20040200923 | Lee | Oct 2004 | A1 |
20040207334 | Lin | Oct 2004 | A1 |
20040212579 | Lo | Oct 2004 | A1 |
20050177287 | Wang | Aug 2005 | A1 |
20060036335 | Banter | Feb 2006 | A1 |
20060218051 | Westberg | Sep 2006 | A1 |
20060274213 | Saier | Dec 2006 | A1 |
20070063980 | Eich | Mar 2007 | A1 |
20070069880 | Best | Mar 2007 | A1 |
20070101290 | Nakashima et al. | May 2007 | A1 |
20070132572 | Itoh | Jun 2007 | A1 |
20080122799 | Pryor | May 2008 | A1 |
20080129684 | Adams | Jun 2008 | A1 |
20080129707 | Pryor | Jun 2008 | A1 |
20080133133 | Abels | Jun 2008 | A1 |
20080192024 | Mita | Aug 2008 | A1 |
20080211652 | Cope | Sep 2008 | A1 |
20080238838 | Cunningham | Oct 2008 | A1 |
20080244460 | Louch | Oct 2008 | A1 |
20090112389 | Yamamoto | Apr 2009 | A1 |
20090174533 | Bowden | Jul 2009 | A1 |
20090174682 | Bowden | Jul 2009 | A1 |
20090300548 | Sullivan et al. | Dec 2009 | A1 |
20110175754 | Karpinsky | Jul 2011 | A1 |
Number | Date | Country |
---|---|---|
2005-67406 | Mar 2005 | JP |
Entry |
---|
Office Action mailed Dec. 9, 2011, in U.S. Appl. No. 12/711,076, filed Feb. 23, 2010, 27 pages. |
Office Action mailed Jul. 13, 2012, in U.S. Appl. No. 12/711,090, filed Feb. 23, 2010, 11 pages. |
Office Action mailed Oct. 16, 2012, in U.S. Appl. No. 12/711,013, filed Feb. 23, 2010, 15 pages. |
Notice of Allowance mailed Apr. 2, 2013, in U.S. Appl. No. 12/711,013, filed Feb. 23, 2010, 8 pages. |
Office Action mailed Mar. 4, 2013, in U.S. Appl. No. 12/711,054, filed Feb. 23, 2010, 24 pages. |
Notice of Allowance mailed Mar. 21, 2013, in U.S. Appl. No. 12/711,090, filed Feb. 23, 2010, 9 pages. |
Final Office Action Dated May 9, 2014, in U.S. Appl. No. 14/054,737, filed Oct. 15, 2013, 40 pages. |
Office Action dated Jun. 19, 2014, in in U.S. Appl. No. 12/711,076, filed Feb. 23, 2010, 34 pages. |
“Microsoft Windows User Experience: Official Guidelines for User Interface Developers and Designers,” © 1999 Microsoft Press, Redmond, Wash., pp. 52, 53, 122-124, 135, 207, 209-215, 222, 242-247, and 250. |
Office Action dated Jan. 14, 2014, in U.S. Appl. No. 14/054,737, filed Oct. 15, 2013, 19 pages. |
Final Office Action mailed Sep. 12, 2012, in U.S. Appl. No. 12/711,076, filed Feb. 23, 2010, 30 pages. |
Restriction Requirement mailed Mar. 23, 2012, in U.S. Appl. No. 12/711,054, filed Feb. 23, 2010, 8 pages. |
Office Action mailed Apr. 26, 2012, in U.S. Appl. No. 12/711,054, filed Feb. 23, 2010, 17 pages. |
Final Office Action mailed Sep. 26, 2012, in U.S. Appl. No. 12/711,054, filed Feb. 23, 2010, 15 pages. |
Number | Date | Country | |
---|---|---|---|
20110209092 A1 | Aug 2011 | US |