US20160121990A1

US20160121990A1 - Reduced Size Tachometer Display

Info

Publication number: US20160121990A1
Application number: US14/531,850
Authority: US
Inventors: Jeremiah Clark; Paul Butterworth; Michael Clancy
Original assignee: Navico Holding AS
Current assignee: Navico Holding AS
Priority date: 2014-11-03
Filing date: 2014-11-03
Publication date: 2016-05-05

Abstract

Various implementations described herein are directed to a non-transitory computer readable medium having stored thereon computer-executable instructions which, when executed by a computer, may cause the computer to display a first page having a first set of marine vessel data. The first set of marine vessel data includes a full size tachometer. The computer may receive a request to display a second page. The computer may also display a second page having a second set of marine vessel data. The second set of marine vessel data includes a reduced size tachometer.

Description

RELATED APPLICATIONS

This application is related to commonly owned U.S. patent application Ser. No. ______, filed on the same day as the present application and titled AUTOMATIC DATA DISPLAY SELECTION, the entire disclosure of which is incorporated herein by reference.

BACKGROUND

Discussion of the Related Art

This section is intended to provide background information to facilitate a better understanding of various technologies described herein. As the section's title implies, this is a discussion of related art. That such art is related in no way implies that it is prior art. The related art may or may not be prior art. It should therefore be understood that the statements in this section are to be read in this light, and not as admissions of prior art.
Operators of marine vessels may use gauges or displays to monitor information while operating a vessel. A gauge or display may be used to display engine information, vessel speed, location, maps or charts, heading, fuel levels, trim information, or other data relevant to a vessel operator.

SUMMARY

Described herein are implementations of a method. The method may include displaying a first page having a first set of marine vessel data. The first set of marine vessel data includes a full size tachometer. The method may include receiving a request to display a second page. The method may also include displaying the second page having a second set of marine vessel data. The second set of marine vessel data includes a reduced size tachometer.
Described herein are also implementations of various technologies for displaying vessel data. In one implementation, a non-transitory computer-readable medium having stored thereon computer-executable instructions which, when executed by a computer, cause the computer to perform various actions. The actions may include displaying a first page having a first set of marine vessel data. The first set of marine vessel data includes a full size tachometer. The actions may include receiving a request to display a second page. The actions may also include displaying the second page having a second set of marine vessel data. The second set of marine vessel data includes a reduced size tachometer.
Described herein are also implementations of various technologies for a system for displaying vessel data. The system includes a display and a computer system having a processor and memory. The memory has a plurality of executable instructions. When the executable instructions are executed by the processor, the processor may display a first page having a first set of marine vessel data. The first set of marine vessel data includes a full size tachometer. The processor may receive a request to display a second page. The processor may also display a second page having a second set of marine vessel data. The second set of marine vessel data includes a reduced size tachometer.

BRIEF DESCRIPTION OF THE DRAWINGS

Implementations of various technologies will hereafter be described with reference to the accompanying drawings. It should be understood, however, that the accompanying drawings illustrate only the various implementations described herein and are not meant to limit the scope of various technologies described herein.

FIG. 1A illustrates a vessel data page in accordance with implementations of various techniques described herein.

FIG. 1B illustrates a dual-motor vessel data page in accordance with implementations of various techniques described herein.

FIG. 2A illustrates an engine monitoring page in accordance with implementations of various techniques described herein.

FIG. 2B illustrates a dual-motor engine monitoring page in accordance with implementations of various techniques described herein.

FIG. 3A illustrates a fuel data page in accordance with implementations of various techniques described herein.

FIG. 3B illustrates a dual-motor fuel data page in accordance with implementations of various techniques described herein.

FIG. 4 is a flow diagram of a method for displaying a reduced size tachometer in accordance with implementations of various techniques described herein.

FIG. 5 illustrates a schematic diagram of a computing system in which the various technologies described herein may be incorporated and practiced.

DETAILED DESCRIPTION

Various implementations of a reduced size tachometer described herein will now be described in more detail with reference to FIGS. 1-5.

I. Tachometer

A tachometer may display the speed of a shaft of a motor in revolutions per minute (RPM). Many vessels are equipped with one or more motors in the rear of the vessel. The motors may be internal combustion engines, electric engines, hybrid engines, or any other type of engine or motor. The internal combustion engines may rotate shafts, giving thrust to the vessel.
The tachometer may be displayed on a gauge or display device and monitored by a vessel operator. In addition to the tachometer, a vessel operator may monitor vessel speed, fuel remaining, fuel used, fuel economy, or other vessel data. In certain instances, a vessel operator may wish to view a tachometer display while also viewing other data types.

II. Display Device for a Motor Vessel

FIG. 1A illustrates a vessel data page display in accordance with implementations of various techniques described herein. A display device 100 is illustrated with a plurality of buttons 110-113 for user input. The display device 100 may display one or more vessel data pages.
The display device 100 may receive vessel data. For example, the display device 100 may receive data compliant with or similar to the National Marine Electronics Association (NMEA) 2000 standard, or any other communication protocol, including a J1939 network, a proprietary network such as SmartCraft™, Command Link™ and Command Link PIus™, or a Bombardier Recreational Products™ Network. The display device 100 may receive data over an NMEA 2000 bus. The display device 100 may receive data from one or more sensors or electronic systems in a marine vessel. For example, the display device 100 may receive data from one or more engines, a Global Positioning System (GPS), vessel control systems, or other electronics.
The display device 100 may display vessel data as vessel data pages. Vessel data pages may be graphical user interfaces that display vessel data specific to a particular category such as, but not limited to, a motor, engine monitoring, and fuel monitoring. A motoring vessel data page 105 is illustrated in FIG. 1A. An engine monitoring page 205 is described in FIG. 2A. A fuel page 305 is described in FIG. 3A. The user may select which vessel data page will be displayed. For example, a user may select a vessel data page using the buttons 110-113. The buttons 110-113 may be any shape or size, and may include any symbol. For example, buttons 112 and 113 may include an upward facing and downward facing arrow.
As described above, a motoring page 105 may display a full size tachometer 120. The full size tachometer 120 may include a circular dial 125. The dial 125 may be used to display a number of RPMs. The dial 125 may use hash marks and numbers to indicate the number of RPMs. For example, the number ‘5’ may correspond to 5000 RPMs. An indicator 135, such as a virtual needle, may indicate motor RPMs by pointing to the dial 125.
In certain implementations, the motoring page 105a may include other data, such as speed 145, and water depth 150. Additionally, the motoring page 105 may display an engine trim level 155 and an engine temperature level 160. The levels 155 and 160 may display data relative to predetermined ranges. For instance, the engine trim may be displayed relative to a predetermined low angle and a predetermined high angle. The engine temperature may be displayed relative to a predetermined low temperature and predetermined high temperature. It is noted that although specific data is illustrated in FIG. 1 on the motoring page 105, any other data or indicators may be displayed on the motoring page 105.
In one implementation, the motoring page may display data corresponding to two or more engines. FIG. 1B illustrates an example of a motoring page for two engines 107. A dual engine tachometer 170 may be displayed in the motoring page for two engines 107. The dual engine tachometer 170 may display tachometer data for multiple engines. Trim levels 190 and engine temperature levels 180 may also be displayed with data for multiple engines.
It is noted that although specific data is shown on the motoring pages 105 and 107, other data may also be shown. Additionally, in certain implementations, the motoring pages 105 and 107 may omit some of the described data. As noted above, the user may select another display page to display by making a selection.
FIG. 2A illustrates an engine monitoring page 205 in accordance with implementations of various techniques described herein. The engine monitoring page 205 may display data related to an engine on a vessel. For example, the engine monitoring page 205 may display engine temperature.
In one implementation, the engine monitoring page 205 may also display a reduced size tachometer 230. The reduced size tachometer 230 may be located at one edge of the display and may consume a relatively small portion of the engine monitoring page 205, thereby allowing other data to be displayed on the engine monitoring page 205. The reduced size tachometer 230 may include an arc and hash marks spread evenly about the arc. The reduced size tachometer 230 may include an indicator 245, such as a virtual needle, to indicate the motor RPMs. The reduced size tachometer 230 may also include a numerical display 250 of the motor RPMs. A level 255 displaying trim and a level 270 displaying engine temperature may be displayed in a reduced size along with the reduced size tachometer 230.
In one implementation, the engine monitoring page may display data corresponding to two or more engines. FIG. 2B illustrates an example of an engine monitoring page for two engines 207. A reduced size dual engine tachometer 280 may be displayed in the engine monitoring page for two engines 207. Reduced size trim levels 290 and engine temperature levels 285 may also be displayed with data for multiple engines.
It is noted that although specific data is shown on the engine monitoring pages 205 and 207, other data may also be shown. Additionally, in certain implementations, the engine monitoring pages 205 and 207 may omit some of the described data. As noted above, the user may select another display page to display by making a selection.
FIG. 3A illustrates a fuel data page 305 in accordance with implementations of various techniques described herein. The fuel data page 305 may include data related to the fuel supply. In one implementation, the fuel data page 305 may further include a reduced size tachometer 330. The fuel data page 305 may also display a reduced size engine trim level 355 and a reduced size engine temperature level 370.
The data related to the fuel supply may include a number of gallons of fuel used 306, and an estimate of the nautical miles a vessel can travel (range) with the fuel remaining 310. The fuel page 305 may include a fuel level 315 and a fuel economy level 320. The fuel level 315 may indicate the amount of fuel in a fuel tank relative to the maximum capacity of the fuel tank. The fuel level 315 may include a marker 325 that indicates the remaining fuel as a percentage of maximum capacity of the fuel tank. The fuel economy level 320 may indicate the rate of fuel consumption in units of miles per gallon relative to a predetermined maximum amount of miles per gallon. The fuel economy level 320 may include a marker 328 that indicates fuel consumption measured in miles per gallon.
In one implementation, the fuel page 305 may display data corresponding to two or more engines. FIG. 3B illustrates an example of a fuel data page for two engines 307. A reduced size dual engine tachometer 380 may be displayed on the fuel data page for two engines 307. Reduced size trim levels 390 and engine temperature levels 385 may also be displayed with data for multiple engines.
It is noted that although specific data is shown on the fuel data pages 305 and 307, other data may also be shown. Additionally, in certain implementations, the fuel data pages 305 and 307 may omit some of the described data. As noted above, the user may select another display page to display by making a selection.
As illustrated in FIGS. 1A-3B, a user of a display device 100 may view any one display page of a number of display pages, such as a motoring page 105 or 107, an engine monitoring page 205 or 207, or a fuel page 305 or 307. However, regardless of which page the user selects, either a full size tachometer 120 or 170 or a reduced size tachometer 230, 280, 330, or 380 is displayed. Thus, a tachometer is visible regardless of which page is displayed. Additionally, a numerical RPM value may be displayed with the reduced size tachometer 230, 280, 330, or 380. In one implementation, either a full size trim level 155 or levels 190 or a reduced size trim level 255 or 355 or levels 290 or 390 may be displayed at all times. In another implementation, either a full size engine temperature level 160 or levels 180 or a reduced size engine temperature level 270 or 370 or levels 285 or 385 may be displayed at all times.
The operation of a display device 100 will now be described in FIG. 4, with references to FIGS. 1A, 1B, 2A, 2B, 3A, and 3B.

III. Method for Displaying Reduced Size Tachometer

FIG. 4 is a flow diagram of a method 400 for displaying a reduced size tachometer in accordance with implementations of various techniques described herein. In one implementation, method 400 may be performed by any computer system 500, including a marine electronics device, marine gauge, and the like. It should be understood that while method 400 indicates a particular order of execution of operations, in some implementations, certain portions of the operations might be executed in a different order, and on different systems. Further, in some implementations, additional operations or steps may be added to the method 400. Likewise, some operations or steps may be omitted.
At block 410, the method 400 may display a motoring page 105 or 107, as illustrated in FIG. 1A and FIG. 1B. For example, the motoring page 105 may be displayed on a display device 100. The motoring page 105 may include a full size tachometer 120 or 170.
At block 420, the method 400 may receive a user request to display a new page on the display device 100. For example, the user request may be input from buttons 110-113 on a display device 100.
As an example, the new page selected for display may be the engine monitoring data page. As such, at block 430, the method 400 may display an engine monitoring data page 205 or 207, as illustrated in FIGS. 2A and 2B. In one implementation, the engine monitoring data page may display engine monitoring data as well as a reduced size tachometer 230 or 280. In this implementation, the engine monitoring data page may also display a numerical RPM value corresponding to the tachometer. The reduced size tachometer 230 or 280 may be displayed at the bottom of the engine monitoring data page. In another implementation, the engine monitoring data page may display a reduced size trim level 255 or levels 290, and a reduced size engine temperature level 270 or levels 285.
At block 440, the method 400 may receive another user request. Other actions similar to those performed at block 420 may be performed at block 440.
As another example, the next new page selected for display may be the fuel data page. As such, at block 450, the method 400 may display a fuel data page 305 or 307 as shown in FIGS. 3A and 3B. In one implementation, the fuel data page may display fuel supply data as well as a reduced size tachometer 330 or 380. In this implementation, the fuel data page may also display a numerical RPM value corresponding to the tachometer. The reduced size tachometer 330 or 380 may be displayed at the bottom of the fuel data page. In another implementation, the fuel data page may display a reduced size trim level 355 or levels 390, and a reduced size engine temperature level 370 or levels 385.
Although method 400 is described as displaying a motoring page 105 or 107, an engine monitoring page 205 or 207, or a fuel data page 305 or 307, any pages may be displayed using method 400 with any data. Regardless of which page is displayed using method 400, a full size or reduced size tachometer will be displayed. A numerical RPM value may be displayed along with the reduced size tachometer. Additionally, regardless of which page is displayed using method 400, a full size or reduced size trim level and engine temperature level may be displayed.

IV. Computer System

Implementations of various technologies described herein may be operational with numerous general purpose or special purpose computing system environments or configurations. Examples of well-known computing systems, environments, and/or configurations that may be suitable for use with the various technologies described herein include, but are not limited to, personal computers, server computers, hand-held or laptop devices, multiprocessor systems, microprocessor-based systems, set top boxes, programmable consumer electronics, network PCs, minicomputers, mainframe computers, smart phones, tablets, wearable computers, cloud computing systems, virtual computers, marine electronics devices, and the like.
The various technologies described herein may be implemented in the general context of computer-executable instructions, such as program modules, being executed by a computer. Generally, program modules include routines, programs, objects, components, data structures, etc. that performs particular tasks or implement particular abstract data types. Further, each program module may be implemented in its own way, and all need not be implemented the same way. While program modules may all execute on a single computing system, it should be appreciated that, in some implementations, program modules may be implemented on separate computing systems or devices adapted to communicate with one another. A program module may also be some combination of hardware and software where particular tasks performed by the program module may be done either through hardware, software, or both.
The various technologies described herein may be implemented in the context of marine electronics, such as devices found in marine vessels and/or navigation systems. Ship instruments and equipment may be connected to the computing systems described herein for executing one or more navigation technologies. As such, the computing systems may be configured to operate using sonar, radar, GPS and like technologies.
The various technologies described herein may also be implemented in distributed computing environments where tasks are performed by remote processing devices that are linked through a communications network, e.g., by hardwired links, wireless links, or combinations thereof. In a distributed computing environment, program modules may be located in both local and remote computer storage media including memory storage devices.
FIG. 5 illustrates a computing system 500 in accordance with implementations of various techniques described herein. Computing system 500 may be a conventional desktop, a handheld device, a wearable device, a controller, a personal digital assistant, a server computer, an electronic device/instrument, a laptop, a tablet, or part of a navigation system, marine electronics, or sonar system. It should be noted, however, that other computer system configurations may be used.
The computing system 500 may include a central processing unit (CPU) 530, a system memory 526, a graphics processing unit (GPU) 531 and a system bus 528 that couples various system components including the system memory 526 to the CPU 530.
Although only one CPU 530 is illustrated in FIG. 5, it should be understood that in some implementations the computing system 500 may include more than one CPU 530.
The CPU 530 may include a microprocessor, a microcontroller, a processor, a programmable integrated circuit, or a combination thereof. The CPU 530 can comprise an off-the-shelf processor such as a Reduced Instruction Set Computer (RISC), or a Microprocessor without Interlocked Pipeline Stages (MIPS) processor, or a combination thereof. The CPU 530 may also include a proprietary processor. The CPU may include a multi-core processor.
The GPU 531 may be a microprocessor specifically designed to manipulate and implement computer graphics. The CPU 530 may offload work to the GPU 531. The GPU 531 may have its own graphics memory, and/or may have access to a portion of the system memory 526. As with the CPU 530, the GPU 531 may include one or more processing units, and each processing unit may include one or more cores.
The CPU 530 may provide output data to the GPU 531. The GPU 531 may generate graphical user interfaces that present the output data. The GPU 531 may also provide objects, such as menus, in the graphical user interface. A user may provide inputs by interacting with the objects. The GPU 531 may receive the inputs from interaction with the objects and provide the inputs to the CPU 530. A video adapter 532 may be provided to convert graphical data into signals for a monitor 534. The monitor 534 includes a screen 505. In certain implementations, the screen 505 may be sensitive to touching by a finger. In other implementations, the screen 505 may be sensitive to the body heat from the finger, a stylus, or responsive to a mouse.
The system bus 528 may be any of several types of bus structures, including a memory bus or memory controller, a peripheral bus, and a local bus using any of a variety of bus architectures. By way of example, and not limitation, such architectures include Industry Standard Architecture (ISA) bus, Micro Channel Architecture (MCA) bus, Enhanced ISA (EISA) bus, Video Electronics Standards Association (VESA) local bus, and Peripheral Component Interconnect (PCI) bus also known as Mezzanine bus. The system memory 526 may include a read only memory (ROM) 512 and a random access memory (RAM) 516. A basic input/output system (BIOS) 514, containing the basic routines that help transfer information between elements within the computing system 500, such as during start-up, may be stored in the ROM 512. The computing system may be implemented using a printed circuit board containing various components including processing units, data storage memory, and connectors.
Certain implementations may be configured to be connected to a GPS and/or a sonar system. The GPS and/or sonar system may be connected via the network interface 444 or Universal Serial Bus (USB) interface 442. In one implementation, the computing system 400, the monitor 434, the screen 405 and buttons may be integrated into a console.
The computing system 500 may further include a hard disk drive interface 536 for reading from and writing to a hard disk 550, a memory card reader 552 for reading from and writing to a removable memory card 556, and an optical disk drive 554 for reading from and writing to a removable optical disk 558, such as a CD ROM, DVD ROM or other optical media. The hard disk 550, the memory card reader 552, and the optical disk drive 554 may be connected to the system bus 528 by a hard disk drive interface 536, a memory card reader interface 538, and an optical drive interface 540, respectively. The drives and their associated computer-readable media may provide nonvolatile storage of computer-readable instructions, data structures, program modules and other data for the computing system 500.
Although the computing system 500 is described herein as having a hard disk, a removable memory card 556 and a removable optical disk 558, it should be appreciated by those skilled in the art that the computing system 500 may also include other types of computer-readable media that may be accessed by a computer. For example, such computer-readable media may include computer storage media and communication media. Computer storage media may include volatile and non-volatile, and removable and non-removable media implemented in any method or technology for storage of information, such as computer-readable instructions, data structures, program modules or other data. Computer storage media may further include RAM, ROM, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other solid state memory technology, including a Solid State Disk (SSD), CD-ROM, digital versatile disks (DVD), or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the computing system 500. Communication media may embody computer readable instructions, data structures, program modules or other data in a modulated data signal, such as a carrier wave or other transport mechanism and may include any information delivery media. The term “modulated data signal” may mean a signal that has one or more of its characteristics set or changed in such a manner as to encode information in the signal. By way of example, and not limitation, communication media may include wired media such as a wired network or direct-wired connection, and wireless media such as acoustic, RF, infrared and other wireless media. The computing system 500 may also include a host adapter 533 that connects to a storage device 535 via a small computer system interface (SCSI) bus, a Fiber Channel bus, an eSATA bus, or using any other applicable computer bus interface.
The computing system 500 can also be connected to a router 564 to establish a wide area network (WAN) 566 with one or more remote computers 574. The router 564 may be connected to the system bus 528 via a network interface 544. The remote computers 574 can also include hard disks 572 that store application programs 570.
In another implementation, the computing system 500 may also connect to the remote computers 574 via local area network (LAN) 576 or the WAN 566. When using a LAN networking environment, the computing system 500 may be connected to the LAN 576 through the network interface or adapter 544. The LAN 576 may be implemented via a wired connection or a wireless connection. The LAN 576 may be implemented using Wi-Fi™ technology, cellular technology, Bluetooth™ technology, satellite technology, or any other implementation known to those skilled in the art. The network interface 544 may also utilize remote access technologies (e.g., Remote Access Service (RAS), Virtual Private Networking (VPN), Secure Socket Layer (SSL), Layer 9 Tunneling (L2T), or any other suitable protocol). These remote access technologies may be implemented in connection with the remote computers 574. It will be appreciated that the network connections shown are exemplary and other means of establishing a communications link between the computer systems may be used.
A number of program modules may be stored on the hard disk 550, memory card 556, optical disk 558, ROM 512 or RAM 516, including an operating system 518, one or more application programs 520, and program data 524. In certain implementations, the hard disk 550 may store a database system. The database system could include, for example, recorded points. The application programs 520 may include various mobile applications (“apps”) and other applications configured to perform various methods and techniques described herein. The operating system 518 may be any suitable operating system that may control the operation of a networked personal or server computer, such as Windows® XP, Mac OS® X, Unix-variants (e.g., Linux® and BSD®), Android®, iOS®, and the like.
A user may enter commands and information into the computing system 500 through input devices such as buttons 562, which may be physical buttons, virtual buttons, or combinations thereof. Other input devices may include a microphone, a mouse, or the like (not shown). These and other input devices may be connected to the CPU 530 through a USB interface 542 coupled to system bus 528, but may be connected by other interfaces, such as a parallel port, or game port.
Certain implementations may be configured to interface to sensors in a vessel. In one implementation, the one or more application programs 520 or 570 stored in the computer-readable media can include a plurality of instructions that when executed by a processing unit, such as a CPU 530, cause the computing system to perform any of the techniques, or portions thereof, that are described herein.
It is to be understood that the discussion above is only for the purpose of enabling a person with ordinary skill in the art to make and use any subject matter defined now or later by the patent “claims” found in any issued patent herein.
It is specifically intended that the claimed invention not be limited to the implementations and illustrations contained herein, but include modified forms of those implementations including portions of the implementations and combinations of elements of different implementations as come within the scope of the following claims. Nothing in this application is considered critical or essential to the claimed invention unless explicitly indicated as being “critical” or “essential.”
Reference has been made in detail to various implementations, examples of which are illustrated in the accompanying drawings and figures. In the detailed description, numerous specific details are set forth in order to provide a thorough understanding of the present disclosure. However, it should be apparent to one of ordinary skill in the art that the present disclosure may be practiced without these specific details. In other instances, well-known methods, procedures, components, circuits and networks have not been described in detail so as not to unnecessarily obscure aspects of the implementations.
It will also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another. For example, a first object or step could be termed a second object or step, and, similarly, a second object or step could be termed a first object or step, without departing from the scope of the invention. The first object or step, and the second object or step, are both objects or steps, respectively, but they are not to be considered the same object or step.
The terminology used in the description of the present disclosure herein is for the purpose of describing particular implementations only and is not intended to be limiting of the present disclosure. As used in the description of the present disclosure and the appended claims, the singular forms “a,” “an” and “the” are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term “and/or” as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items. It should be further understood that the terms “includes,” “including,” “comprises” and/or “comprising,” when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but should not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and/or groups thereof.
As used herein, the term “if” may be construed to mean “when” or “upon” or “in response to determining” or “in response to detecting,” depending on the context. Similarly, the phrase “if it is determined” or “if [a stated condition or event] is detected” may be construed to mean “upon determining” or “in response to determining” or “upon detecting [the stated condition or event]” or “in response to detecting [the stated condition or event],” depending on the context.
“Alternatively” should not be construed to only pertain to situations where the number of choices involved is exactly two, but rather refers to another possibility among many other possibilities.
Additionally, various technologies and techniques described herein include receiving user requests for a number of different operations. In certain instances, the user request for a particular operation will be explicitly described. It should be understood that a “request” or “can request” can also include, but are not limited to, touching a screen, double tapping a screen (tapping the screen twice in rapid succession), pressing a particular physical or virtual button, making a selection from a menu, swiping the screen (placing a finger towards an edge of the screen and traversing the screen while maintaining contact between the finger and the screen) placement of a cursor at a particular location, stylus pointing, mouse selection, an audible command, as well as the explicit description of the “request” for the particular operations.
While the foregoing is directed to implementations of various techniques described herein, other and further implementations may be devised without departing from the basic scope thereof, which may be determined by the claims that follow. Although the subject matter has been described in language specific to structural features and/or methodological acts, it is to be understood that the subject matter defined in the appended claims is not necessarily limited to the specific features or acts described above. Rather, the specific features and acts described above are disclosed as example forms of implementing the claims.

Claims

What is claimed is:

1. A method for displaying vessel data, the method comprising:

displaying a first page having a first set of marine vessel data, wherein the first set of marine vessel data comprises a full size tachometer;

receiving a request to display a second page; and

displaying the second page having a second set of marine vessel data, wherein the second set of marine vessel data comprises a reduced size tachometer.

2. The method of claim 1 wherein the full size and reduced size tachometers display data corresponding to a plurality of motors.

3. The method of claim 1 wherein the second set of marine vessel data further comprises a numerical tachometer.

4. The method of claim 1 wherein the reduced size tachometer comprises less than half of a total display area of the second page.

5. The method of claim 1 wherein the reduced size tachometer is displayed at the bottom of the second page.

6. The method of claim 1, wherein the second page displays fuel data for a marine vessel.

7. The method of claim 1, wherein the second page displays engine data for a marine vessel.

8. The method of claim 1, wherein:

the first set of marine vessel data further comprises a full size engine temperature level; and

the second set of marine vessel data further comprises a reduced size engine temperature level.

9. The method of claim 1, wherein:

the first set of marine vessel data further comprises a full size trim level; and

the second set of marine vessel data further comprises a reduced size trim level.

10. A non-transitory computer readable medium having stored thereon a plurality of computer-executable instructions which, when executed by a computer, cause the computer to:

display a first page having a first set of marine vessel data, wherein the first set of marine vessel data comprises a full size tachometer;

receive a request to display a second page; and

display a second page having a second set of marine vessel data, wherein the second set of marine vessel data comprises a reduced size tachometer.

11. The non-transitory computer readable medium of claim 10, wherein the computer-executable instructions further cause the computer to:

receive a request to display a third page; and

display a third page having a third set of marine vessel data, wherein the third set of marine vessel data comprises a reduced size tachometer.

12. The non-transitory computer readable medium of claim 10, wherein the full size and reduced size tachometers display data corresponding to a plurality of motors.

13. The non-transitory computer readable medium of claim 10, wherein the second page displays engine data for a marine vessel.

14. The non-transitory computer readable medium of claim 10, wherein the second page displays fuel data for a marine vessel.

15. The non-transitory computer readable medium of claim 10, wherein:

16. The non-transitory computer readable medium of claim 10, wherein:

17. The method of claim 10 wherein the second set of marine vessel data further comprises a numerical tachometer.

18. A system for displaying vessel data, said system comprising:

a display; and

a computer system having a processor and memory having stored thereon a plurality of executable instructions which, when executed by the processor, cause the processor to:

receive a request to display a second page; and

19. The system of claim 18, wherein the request to display a second page is received from a selection of a button displayed on the first page.

20. The system of claim 18, wherein the reduced size tachometer is displayed at the bottom of the second page.