Patent Description:
Recreational vehicles, such as motorcycles, all-terrain vehicles (ATVs), side-by-side vehicles, utility vehicles, and snowmobiles, are widely used for recreational purposes. These vehicles might be used on both roads and trails, or only on trails. <CIT> relates to a wireless communication system for a vehicle comprising wireless communication devices attached to a plurality of helmets worn by vehicle occupants, wherein the wireless communication devices are configured to communicate with each other via a relay device mounted on the vehicle.

The present application discloses systems and methods to connect and transmit audio information between a driver portable communication device and a driver audio interface device through the recreational vehicle and audio information between a passenger portable communication device and a passenger audio interface device.

In the present invention a recreational vehicle for use by a driver and at least a first passenger is disclosed. The driver has a driver portable communication device and a driver audio interface device having a microphone and a speaker. The first passenger has a first passenger portable communication device and a first passenger audio interface device having a microphone and a speaker. The recreational vehicle comprises a plurality of ground engaging members, a frame supported by the plurality of ground engaging members, a prime mover supported by the frame and operatively coupled to at least one of the plurality of ground engaging members to power movement of the recreational vehicle, and a steering system supported by the frame and operatively coupled to at least a portion of the plurality of ground engaging members to move the portion of the plurality of ground engaging members relative to the frame. The steering system includes a steering member adapted to be grasped by the operator of the recreational vehicle, the steering member being movable relative to the frame. The vehicle further comprises at least one controller supported by the frame. The at least one controller is adapted to be operatively coupled to the driver portable communication device, the driver audio interface device, the passenger portable communication device, and the passenger audio interface device. The at least one controller is configured to communicate audio information between the driver portable communication device and the driver audio interface device through the at least one controller and to communicate audio information between the passenger portable communication device and the passenger audio interface device through the at least one controller.

In another embodiment of the present disclosure, a method of communicating information to a driver and at least a first passenger of a recreational vehicle is disclosed. The driver has a driver portable communication device and a driver audio interface device having a microphone and a speaker. The first passenger has a first passenger portable communication device and a first passenger audio interface device having a microphone and a speaker. The method comprises the step of operatively coupling at least one controller of the recreational vehicle with the driver portable communication device, the driver audio interface device, the first passenger portable communication device, and the first passenger audio interface device. The method also comprises the step of routing audio information through the at least one controller of the recreational vehicle between one of (a) the driver portable communication device and the driver audio interface device and (b) the first passenger portable communication device and the passenger audio interface device, wherein audio information is routed between the driver portable communication device and the driver audio interface device in response to a driver call being established with the driver portable communication device and wherein audio information is routed between the first passenger portable communication device and the first passenger audio interface device in response to a first passenger call being established with the first passenger portable communication device.

Additional features of the present invention will become more apparent to those skilled in the art upon consideration of the following detailed descriptions of illustrative embodiments exemplifying the best mode of carrying out the invention as presently perceived.

Advantages and features of the embodiments of this invention will become more apparent from the following detailed description of exemplary embodiments when viewed in conjunction with the accompanying drawings, wherein:.

Various embodiments of the present invention will be described in detail with reference to the drawings, wherein like reference numerals represent like parts and assemblies throughout the several views. Reference to various embodiments does not limit the scope of the invention, which is limited only by the scope of the claims attached hereto. Additionally, any examples set forth in this specification are not intended to be limiting and merely set forth some of the many possible embodiments for the claimed invention.

Referring to <FIG>, a recreational vehicle <NUM> is represented. Recreational vehicle <NUM> includes a plurality of ground engaging members <NUM>. Exemplary ground engaging members include skis, endless tracks, wheels, and other suitable devices which support vehicle <NUM> relative to the ground. Recreational vehicle <NUM> further includes a frame <NUM> supported by the plurality of ground engaging members <NUM>. In one embodiment, frame <NUM> includes cast portions, weldments, tubular components or a combination thereof. In one embodiment, frame <NUM> is a rigid frame. In one embodiment, frame <NUM> has at least two sections which are moveable relative to each other.

An operator support <NUM> is supported by frame <NUM>. Exemplary operator supports include straddle seats, bench seats, bucket seats, and other suitable support members. In addition to operator support <NUM>, recreational vehicle <NUM> may further include a passenger support. Exemplary passenger supports include straddle seats, bench seats, bucket seats, and other suitable support members.

A power system <NUM> is supported by frame <NUM>. Power system <NUM> provides the motive force and communicates the same to at least one of the ground engagement members <NUM> to power movement of recreational vehicle <NUM>.

Referring to <FIG>, one embodiment of power system <NUM> is illustrated. Power system <NUM> includes a prime mover <NUM>. Exemplary prime movers <NUM> include internal combustion engines, two stroke internal combustion engines, four stroke internal combustion engines, diesel engines, electric motors, hybrid engines, and other suitable sources of motive force. To start the prime mover <NUM>, a power supply system <NUM> is provided. The type of power supply system <NUM> depends on the type of prime mover <NUM> used. In one embodiment, prime mover <NUM> is an internal combustion engine and power supply system <NUM> is one of a pull start system and an electric start system. In one embodiment, prime mover <NUM> is an electric motor and power supply system <NUM> is a switch system which electrically couples one or more batteries to the electric motor.

A transmission <NUM> is coupled to prime mover <NUM>. Transmission <NUM> is illustrated as having a shiftable transmission <NUM> and a continuously variable transmission ("CVT") <NUM>. CVT <NUM> is coupled to prime mover <NUM>. Shiftable transmission <NUM> is in turn coupled to CVT <NUM>. In one embodiment, shiftable transmission <NUM> includes a forward high setting, a forward low setting, a neutral setting, a park setting, and a reverse setting. The power communicated from prime mover <NUM> to CVT <NUM> is provided to a drive member of CVT <NUM>. The drive member in turn provides power to a driven member through a belt. Exemplary CVTs are disclosed in <CIT>; <CIT>; <CIT>; <CIT>; and <CIT>. The driven member provides power to an input shaft of shiftable transmission <NUM>. Although transmission <NUM> is illustrated as including both shiftable transmission <NUM> and CVT <NUM>, transmission <NUM> may include only one of shiftable transmission <NUM> and CVT <NUM>.

In the illustrated embodiment, transmission <NUM> is further coupled to at least one differential <NUM> which is in turn coupled to at least one ground engaging members <NUM>. Differential <NUM> may communicate the power from transmission <NUM> to one of ground engaging members <NUM> or multiple ground engaging members <NUM>. In an ATV embodiment, one or both of a front differential and a rear differential are provided. The front differential powering at least one of two front wheels of the ATV and the rear differential powering at least one of two rear wheels. In a utility vehicle embodiment, one or both of a front differential and a rear differential are provided. The front differential powering at least one of two front wheels of the utility vehicle and the rear differential powering at least one of multiple rear wheels of the utility vehicle. In one example, the utility vehicle has three axles and a differential is provided for each axle. In a motorcycle embodiment, a differential <NUM> and CVT <NUM> are not generally included. Rather, shiftable transmission <NUM> is coupled to at least one rear wheel through a chain or belt. In another motorcycle embodiment, a differential <NUM> is not included. Rather, CVT <NUM> is coupled to at least one rear wheel through a chain or belt. In a snowmobile embodiment, a differential <NUM> is not included. Rather, CVT <NUM> is coupled to an endless track through a chain case. In one golf cart embodiment, a transmission is not included. Rather, an electric motor is coupled directly to a differential <NUM>. An exemplary differential is a helical gear set. The motor can be run in a first direction for forward operation of the golf cart and in a second direction for reverse operation of the golf cart. Although mentioned in connection with a golf cart, the concepts described herein may be used in connection with any electric vehicle.

Recreational vehicle <NUM> further includes a braking/traction system <NUM>. In one embodiment, braking/traction system <NUM> includes anti-lock brakes. In one embodiment, braking/traction system <NUM> includes active descent control and/or engine braking. In one embodiment, braking/traction system <NUM> includes a brake and in some embodiments a separate parking brake. Braking/traction system <NUM> may be coupled to any of prime mover <NUM>, transmission <NUM>, differential <NUM>, and ground engaging members <NUM> or the connecting drive members therebetween.

Returning to <FIG>, recreational vehicle <NUM> further includes a steering system <NUM>. Steering system <NUM> is coupled to at least one of the ground engagement members <NUM> to direct recreational vehicle <NUM>. Steering system <NUM> generally includes a steering member adapted to be grasped by an operator of vehicle <NUM>. Exemplary steering members include handlebars and steering wheels.

Further, recreational vehicle <NUM> includes a vehicle controller <NUM> having at least one associated memory <NUM>. Vehicle controller <NUM> provides the electronic control of the various components of recreational vehicle <NUM>. Further, vehicle controller <NUM> is operatively coupled to a plurality of sensors <NUM> (see <FIG>) which monitor various parameters of recreational vehicle <NUM> or the environment surrounding vehicle <NUM>. Vehicle controller <NUM> performs certain operations to control one or more subsystems of other vehicle components, such as one or more of a fuel system <NUM>, an air handling system <NUM>, CVT <NUM>, shiftable transmission <NUM>, prime mover <NUM>, differentials <NUM> and other systems. In certain embodiments, controller <NUM> forms a portion of a processing subsystem including one or more computing devices having memory, processing, and communication hardware. Controller <NUM> may be a single device or a distributed device, and the functions of controller <NUM> may be performed by hardware and/or as computer instructions on a non-transient computer readable storage medium, such as memory <NUM>.

Vehicle controller <NUM> also interacts with an operator interface <NUM> which includes at least one input device <NUM> and at least one output device <NUM>. Exemplary input devices <NUM> include levers, buttons, switches, soft keys, and other suitable input devices. Exemplary output devices include lights, displays, audio devices, tactile devices, and other suitable output devices. Operator interface <NUM> further includes an interface controller <NUM> and an associated memory <NUM>. Interface controller <NUM> performs certain operations to control one or more subsystems of operator interface <NUM> or of other vehicle components, such as one or more of input devices <NUM> and output devices <NUM>. In one example, operator interface <NUM> includes a touch screen display and interface controller <NUM> interprets various types of touches to the touch screen display as inputs and controls the content displayed on touch screen display. In certain embodiments, interface controller <NUM> forms a portion of a processing subsystem including one or more computing devices having memory, processing, and communication hardware. The interface controller <NUM> may be a single device or a distributed device, and the functions of the interface controller <NUM> may be performed by hardware and/or as computer instructions on a non-transient computer readable storage medium, such as memory <NUM>.

Referring to <FIG>, operator interface <NUM> is included as part of an instrument cluster <NUM>. Interface controller <NUM> controls the operation of output devices <NUM> and monitors the actuation of input devices <NUM>. In one embodiment, output devices <NUM> include a display and interface controller <NUM> formats information to be displayed on the display and displays the information. In one embodiment, output devices <NUM> include a touch display and interface controller <NUM> formats information to be displayed on the touch display, displays the information, and monitors the touch display for operator input. Exemplary operator inputs include a touch, a drag, a swipe, a pinch, a spread, and other known types of gesturing.

As illustrated in the embodiment of <FIG>, vehicle controller <NUM> is represented as including several controllers. These controllers may each be single devices or distributed devices or one or more of these controllers may together be part of a single device or distributed device. The functions of these controllers may be performed by hardware and/or as computer instructions on a non-transient computer readable storage medium, such as memory <NUM>.

In one embodiment, vehicle controller <NUM> includes at least two separate controllers which communicate over a network. In one embodiment, the network is a CAN network. In one embodiment, the CAN network is implemented in accord with the J1939 protocol. Details regarding an exemplary CAN network are disclosed in PCT Patent Application No. <CIT>. Of course any suitable type of network or data bus may be used in place of the CAN network. In one embodiment, a two wire serial communication is used.

Referring to <FIG>, controller <NUM> includes a power system controller <NUM> which controls the operation of at least one of prime mover <NUM>, transmission <NUM>, and differentials <NUM> (if included). In one example, prime mover <NUM> is an internal combustion engine and power system controller <NUM> controls the provision of fuel, provision of spark, engine performance, reverse operation of vehicle, locking differential, all wheel drive, ignition timing, electrical power distribution, and transmission control. Further, power system controller <NUM> monitors a plurality of sensors. Exemplary sensors include a temperature sensor which monitors the temperature of a coolant which circulates through the engine, throttle position sensor (TPS), exhaust gas temperature sensor (EGT), crank position sensor (CPS), detonation sensor (DET), airbox pressure sensor, intake air temperature sensor, and other parameters as required to control the engine performance.

Controller <NUM> further includes a braking/traction controller <NUM> which controls the operation of braking/traction system <NUM>. In one example, braking/traction controller <NUM> controls pressure and frequency of the actuation of the brake caliper. Further, braking/traction controller172 monitors a plurality of sensors. Exemplary sensors include a vehicle speed sensor which monitors vehicle speed relative to the ground, an altitude sensor, and an engine RPM sensor.

Controller <NUM> further includes a steering controller <NUM> which controls the operation of steering system <NUM>. In one example, steering controller <NUM> controls an amount of assist provided by a power steering unit of recreational vehicle <NUM>. Further, power steering controller <NUM> monitors a plurality of sensors. Exemplary sensors and electronic power steering units, including speed profiles, examples of which are provided in PCT Patent Application Serial No. <CIT>.

Controller <NUM> further includes a network controller <NUM> which controls communications between recreational vehicle <NUM> and other devices through one or more network components <NUM>. In one embodiment, network controller <NUM> of recreational vehicle <NUM> communicates with paired devices over a wireless network (e.g., via a wireless or wifi chip). An exemplary wireless network is a radio frequency network utilizing a BLUETOOTH protocol. In this example, network components <NUM> include a radio frequency antenna. Network controller <NUM> controls the pairing of devices to recreational vehicle <NUM> and the communications between recreational vehicle <NUM> and the remote devices. An exemplary remote device is a driver portable communication device <NUM>, a driver audio interface device <NUM>, a passenger portable communication device <NUM>, and a passenger audio interface device <NUM>. Exemplary portable communication devices include cellular telephones, satellite telephones, and other devices capable of sending and receiving communications through external networks. Exemplary cellular phones include both IOS and android devices, for example the IPHONE brand cellular phone sold by Apple Inc. , located at <NUM> Infinite Loop, Cupertino, CA <NUM> and the GALAXY brand cellular phone sold by Samsung Electronics Co. , Ltd, respectively. Exemplary communications include audio calls, short message system texts, and other types of communication. Exemplary audio interface devices include headsets including a microphone to receive audio and convert the audio to electronic signals and a speaker to convert electronic signals into audio.

Controller <NUM> further includes a location determiner <NUM> which determines a current location of recreational vehicle <NUM>. An exemplary location determiner <NUM> is a GPS unit which determines the position of recreational vehicle <NUM> based on interaction with a global satellite system.

Although vehicle controller <NUM> and interface controller <NUM> are illustrated separately in <FIG>, their functionality may be combined. Further, a portion or all of the functionality of one or more of network controller <NUM> and location determiner <NUM> may be included as part of interface controller <NUM>. In one embodiment, it is desired to include the functionality of network controller <NUM> and location determiner <NUM> as part of interface controller <NUM> to provide an instrument cluster <NUM> that is easily replaceable or upgradable. Throughout this application, various features and functionality are described in connection with vehicle controller <NUM>, interface controller <NUM>, or generally a vehicle associated controller. Either one or both of vehicle controller <NUM> and interface controller <NUM> may provide the described features and functionality.

Memory <NUM> (<FIG>) may be representative of multiple memories which are provided locally with power system controller <NUM>, braking/traction controller <NUM>, steering controller <NUM>, network controller <NUM>, and location determiner <NUM>. The information recorded or determined by one or more of power system controller <NUM>, braking/traction controller <NUM>, steering controller <NUM>, network controller <NUM>, and location determiner <NUM> may be stored on memory <NUM>. Memory <NUM> (<FIG>) is one or more non-transitory computer readable medium. Memory <NUM> may be representative of multiple memories which are provided locally with interface controller <NUM>, and one or more of network controller <NUM> and location determiner <NUM> when included as part of interface controller <NUM>. The information recorded or determined by one or more of interface controller <NUM>, network controller <NUM> and location determiner <NUM> may be stored on memory <NUM>.

Referring to <FIG>, an exemplary motorcycle <NUM> is shown. Motorcycle <NUM> includes a front ground-engaging member <NUM> with a front axis of rotation <NUM> (<FIG>), a rear ground-engaging member <NUM> with a rear axis of rotation (not shown), a frame assembly <NUM> supported by ground-engaging members <NUM>, <NUM> and extending longitudinally between the ground engaging members <NUM>, <NUM>. Referring to <FIG>, front ground-engaging member <NUM> and rear ground-engaging member <NUM> are inline and centered along a longitudinal centerline plane (L) of motorcycle <NUM>. Motorcycle <NUM> further includes a powertrain assembly <NUM> supported by frame assembly <NUM>. Powertrain assembly <NUM> includes an engine <NUM> and a transmission <NUM>. Transmission <NUM> may be a shiftable transmission or a continuously-variable transmission or both. Engine <NUM> is operably coupled to transmission <NUM> and includes at least one cylinder <NUM> and, illustratively, includes two cylinders <NUM>. A fuel tank <NUM> is fluidly coupled to engine <NUM> and positioned generally above cylinders <NUM>.

Referring to <FIG>, a seat assembly <NUM> is coupled to frame assembly <NUM> and is positioned generally above at least a portion of powertrain assembly <NUM>. Seat assembly <NUM> includes an operator seat <NUM>, defined by a seat bottom <NUM> and a seat back <NUM>, and a passenger seat <NUM>, defined by a seat bottom <NUM> and a seat back <NUM>.

Referring to <FIG>, vehicle <NUM> includes an operator area <NUM> positioned generally forward of seat assembly <NUM> and rearward of at least a portion of a front fairing <NUM> of vehicle <NUM>. Fairing <NUM> includes an upper extent defined by an upper lip <NUM>. A center point of upper lip <NUM> aligns with longitudinal centerline plane (L). Fairing <NUM> extends rearwardly to a rear extent <NUM> which is positioned generally above an upper extent of fuel tank <NUM>. Fairing <NUM> is coupled to a front fork assembly <NUM> of vehicle <NUM> and supports a headlight <NUM> forward of front fork assembly <NUM>. Front fork assembly <NUM> is operably coupled to a steering assembly <NUM>. Additional details of fairing <NUM> and front fork assembly <NUM> are disclosed in PCT Patent Application No. <CIT>.

Operator area <NUM> includes steering assembly <NUM> including a handlebar <NUM> which moves with the front fork, a right hand grip <NUM>, and a left hand grip <NUM>. Operator area <NUM> is protected by a windshield <NUM>.

Operator area <NUM> further includes a user interface assembly <NUM>. User interface assembly <NUM> includes a first portion <NUM> supported by faring <NUM>, a second portion <NUM> supported by handlebar <NUM> and positioned adjacent left hand grip <NUM>, a third portion <NUM> supported by handlebar <NUM> and positioned adjacent right hand grip <NUM>, and a fourth portion <NUM> supported by fuel tank <NUM>. Second portion <NUM> and third portion <NUM> move with handlebar <NUM>. Thus, when a driver of motorcycle <NUM> rotates handlebar <NUM>, front fork assembly <NUM>, front ground-engaging member <NUM>, second portion <NUM>, and third portion <NUM> all rotate with handlebar <NUM>. In one embodiment, faring <NUM> and hence first portion <NUM> of user interface assembly <NUM> also rotates with handlebar <NUM> due to faring <NUM> being supported by front fork assembly <NUM>.

User interface assembly <NUM> includes a plurality of input devices and output devices. Exemplary input devices include buttons, switches, touch displays, dials, and other devices which receive input from a driver of motorcycle <NUM>. Exemplary output devices include gauges, displays, touch displays, lights, and other devices that provide one or more of a visual output, an audio output, and a tactile output to a driver of motorcycle <NUM>.

First portion <NUM> of user interface assembly <NUM> includes a first display <NUM>, a second display or gauge <NUM>, and a third display or gauge <NUM>. In one embodiment, displays <NUM>, <NUM>, <NUM> may be movable or configured to tilt between upper and lower positions to accommodate the preferences of the operator. First display <NUM> is positioned intermediate second and third displays <NUM>, <NUM> and is positioned along longitudinal centerline plane (L) of motorcycle <NUM>. Display <NUM>, along with display <NUM>, display <NUM>, and along with display or gauge <NUM> of fourth portion <NUM> and display or gauge <NUM> of fourth portion <NUM> are configured to display various data or information about the operating conditions of vehicle <NUM>, ambient conditions, infotainment (e.g., GPS, radio, wireless connectivity, Bluetooth® connectivity, audio settings), and/or any other information that may be useful to the driver during operation of motorcycle <NUM>.

In one embodiment, at least display <NUM> is a touch-screen display with a plurality of pixels configured to change in response to an operator input. For example, the operator may use his/her finger to select options on first display <NUM> and receive information about motorcycle <NUM>, ambient conditions, etc. In one embodiment, first display <NUM> has a generally rectangular cross-section defined by a width <NUM> and a height <NUM>. Illustratively, width <NUM> may be approximately <NUM>-<NUM> inches, for example <NUM> inches, and height <NUM> may be approximately <NUM>-<NUM> inches, for example <NUM> inches. Second and third displays <NUM> and <NUM> also may define a rectangle in cross-section, however, illustrative first and second displays <NUM> and <NUM> define a circle in cross-section.

Additional details regarding motorcycle <NUM> are provided in PCT Patent Application No.<CIT>.

Referring to <FIG>, display <NUM> is part of an instrument cluster <NUM>. Instrument cluster <NUM> additionally includes a riding screen input button <NUM>, an audio selection input button <NUM>, a power button <NUM>, a connectivity button <NUM>, a navigation button <NUM>, and a configuration button <NUM> (<FIG>). Although described or illustrated as buttons <NUM>-<NUM>, other input devices may be used including switches, touch screen regions of display <NUM>, and other suitable devices for providing an input to instrument cluster <NUM>. By selecting any one of input buttons <NUM>-<NUM>, the operator interface controller <NUM> of instrument cluster <NUM> changes the layout presented on display <NUM>. In addition to input buttons <NUM>-<NUM>, operator interface controller <NUM> additionally may change the screen layout presented on display <NUM> in response to inputs provided as part of second portion <NUM> of user interface assembly <NUM> and inputs that are part of third portion <NUM> of user interface assembly <NUM>.

As illustrated in <FIG>, second portion <NUM> of user interface assembly <NUM> includes a left-hand trigger input button <NUM>, a plurality of audio inputs <NUM>, and a plurality of toggle inputs <NUM>. The plurality of audio inputs <NUM> includes a volume up input <NUM>, a volume down input <NUM>, a scroll back input <NUM>, a scroll forward input <NUM>, and an accept selection input <NUM>. Alternatively, in one embodiment, accept selection input <NUM> may be an audio input selection to control various audio options, for example a sound-mute option and/or an option to play/pause the audio. When accept selection input <NUM> controls audio input, accept selection functions may be controlled through additional inputs, as disclosed further herein. The plurality of toggle inputs <NUM> includes a toggle up input <NUM> and a toggle down input <NUM>. Additional details regarding the use of left-hand trigger input button <NUM>, audio inputs <NUM>, and toggle inputs <NUM> are provided herein. The third portion <NUM> of user interface assembly <NUM> includes a right-hand trigger input button <NUM>. When accept selection input <NUM> controls audio input, accept selection functions may be controlled through inputs any of <NUM>, <NUM>, <NUM>, <NUM>. Additional details regarding the interaction between the inputs of third portion <NUM>, user interface assembly <NUM>, and instrument cluster <NUM> are disclosed herein.

Referring to <FIG>, three riding screen layouts <NUM>, <NUM>, and <NUM> are illustrated for display screen <NUM>. Each riding screen layout is a customized screen selected by an operator of vehicle <NUM>. Referring to <FIG>, a representation of a first screen layout <NUM> is shown. Screen layout <NUM> includes a first region <NUM> and a second region <NUM>. Regions <NUM>, <NUM> are positioned side by side in a non-overlapping arrangement on display <NUM>. In other embodiments, region <NUM> is positioned above <NUM> on display <NUM>. Each of region <NUM> and region <NUM> are customizable by the operator of vehicle <NUM>. The operator can select the information to be displayed in each of region <NUM> and <NUM> from a preset list of options. In one embodiment, the predefined of options for regions <NUM> and <NUM> include a trip <NUM> screen layout, a trip <NUM> screen layout, a ride data screen layout, a vehicle status screen layout, a vehicle information screen layout, an audio screen layout, a connectivity status screen layout, a map/navigation screen layout, and a custom image screen layout.

Referring to <FIG>, a selection screen layout <NUM> is shown. The selection screen layout <NUM> provides the various options for regions <NUM> and <NUM> to the operator of vehicle <NUM> for selection. An operator of vehicle <NUM> navigates to first region <NUM> by selecting configuration button <NUM> (<FIG>). In one embodiment, the operator may scroll through a left-hand list of selections <NUM> which correspond to region <NUM> and a right-hand list of selections <NUM> which correspond to region <NUM> by swiping their finger on the touch screen of display <NUM>. The operator than selects by touch the desired option screen to be shown in regions <NUM> and <NUM>, as indicated by the outlined options shown in second region <NUM> and selections <NUM>. Once the selections are made, the operator will touch the done region <NUM> of first region <NUM> to select the highlighted options. The selected options are stored in memory <NUM> of instrument cluster <NUM>.

Referring to <FIG>, a first trip option screen layout <NUM> is shown. This screen layout may be used for both a trip <NUM> option and a trip <NUM> option. As shown in <FIG>, first trip option screen layout <NUM> includes an indication <NUM> of a distance traveled since the trip odometer was set, a distance to empty indicator <NUM> which provides an indication of the remaining miles that may be traveled based on fuel levels in fuel tank <NUM>, an average miles per gallon indicator <NUM>, an instantaneous miles per gallon indicator <NUM>, a time elapsed indicator <NUM>, and an average speed indicator <NUM>. In addition, a reset input <NUM> is provided in the upper left corner of first trip option screen layout <NUM>. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a second trip option screen layout <NUM> is shown. This screen layout may be used for both a trip <NUM> option and a trip <NUM> option. As shown in <FIG>, second trip option screen layout <NUM> includes an indication <NUM> of a distance traveled since the trip odometer was set, a distance to empty indicator <NUM> which provides an indication of the remaining miles that may be traveled based on fuel levels in fuel tank <NUM>, an average miles per gallon indicator <NUM>, an instantaneous miles per gallon indicator <NUM>, a time elapsed indicator <NUM>, and an average speed indicator <NUM>. In addition, a reset input <NUM> is provided in the lower center portion of reset input <NUM>. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a first exemplary screen layout <NUM> of a ride data screen is shown. First exemplary screen layout <NUM> includes a heading indicator <NUM>, a moving time indicator <NUM>, a stop time indicator <NUM>, an altitude indicator <NUM>, and an altitude change indicator <NUM>. Moving time indicator <NUM> provides an indication of the elapsed time that vehicle <NUM> has been in motion. Stop time indicator <NUM> provides an elapsed time of the amount of time that vehicle <NUM> has been stopped. Altitude change indicator <NUM> provides an indication of the change between the highest and lowest altitude readings of vehicle <NUM> during the current power on of vehicle <NUM>. In addition, a reset input <NUM> is provided in the upper left corner of first trip option screen layout <NUM>. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a first exemplary screen layout <NUM> of a ride data screen is shown. First exemplary screen layout <NUM> includes a heading indicator <NUM>, a moving time indicator <NUM>, a stop time indicator <NUM>, an altitude indicator <NUM>, and an altitude change indicator <NUM>. Moving time indicator <NUM> provides indication of the elapsed time that vehicle <NUM> has been in motion. Stop time indicator <NUM> provides an elapsed time of the amount of time that vehicle <NUM> has been stopped. Altitude change indicator <NUM> provides an indication of the change between the highest and lowest altitude readings of vehicle <NUM> during the current power on of vehicle <NUM>. In addition, a reset input <NUM> is provided in the upper left corner of first trip option screen layout <NUM>. In addition, a reset input <NUM> is provided in the lower center portion of reset input <NUM>. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a first exemplary vehicle information screen layout <NUM> is shown. The vehicle information screen layout <NUM> includes miles per hour indicator <NUM>, a distance to empty indicator <NUM>, a rpm indicator <NUM>, and a gear indicator <NUM>. Gear indicator <NUM> provides an indication of the current gear setting for the transmission <NUM> of vehicle <NUM>. The current gear is a different color than the remaining gear indicators. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a second exemplary vehicle information screen layout <NUM> is shown. Screen layout <NUM> includes miles per hour indicator <NUM>, a distance to empty indicator <NUM>, a current gear indicator <NUM>, a front tire pressure indicator <NUM>, a rear tire pressure indicator <NUM>, and a power level indicator <NUM> for an accessory of vehicle <NUM>. Exemplary accessories include heated grips provided for right hand grip <NUM> and left hand grip <NUM> of vehicle <NUM> and a heater for seat bottom <NUM>. In one embodiment, screen layout <NUM> may display controls and inputs for managing operation of the heated grips and/or the heater for seat bottom <NUM>. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a first exemplary vehicle status screen layout <NUM> includes a front tire pressure indicator <NUM>, a rear tire pressure indicator <NUM>, an oil life indicator <NUM>, a vehicle accessory status indicator <NUM>, a lapse engine hours indicator <NUM>, and a miles to oil change indicator <NUM>. Exemplary vehicle accessories include heated grips for right hand grip <NUM> and left hand grip <NUM>. The miles to oil change indicator <NUM> provides an indication of the expected number of miles that vehicle <NUM> may travel prior to needed its next oil change. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>. As shown in <FIG>, screen layout <NUM> may further display an image of vehicle <NUM> at <NUM>. In one embodiment, image <NUM> of vehicle <NUM> shown in screen layout <NUM> changes with each vehicle <NUM> to correctly identify the type of vehicle the user is operating (e.g., a touring motorcycle, a cruiser motorcycle, a utility vehicle, etc.). For example, image <NUM> may be changed by sending a CAN or other signal to VCU <NUM> or another component of vehicle <NUM> to identify the type of vehicle the user is operating. Once the vehicle identifying information has been obtained, the correct image will be shown in screen layout <NUM> to match vehicle <NUM>.

Referring to <FIG>, a second exemplary vehicle status screen layout <NUM> is shown. Vehicle status layout <NUM> includes a front tire pressure indicator <NUM>, a rear tire pressure indicator <NUM>, a vehicle accessory status indicator <NUM>, an oil life indicator <NUM>, and a miles to oil change indicator <NUM>. Exemplary vehicle accessories include heated grips. The miles to oil change indicator <NUM> provides an indication of the expected number of miles that vehicle <NUM> may travel prior to needed its next oil change. It will be understood by one of skill in the art the values reported in indicators <NUM>-<NUM> are based on computations made by one or more of the controllers of vehicle <NUM> based on sensor values received from one or more sensors <NUM> of vehicle <NUM>.

Referring to <FIG>, a first exemplary audio screen layout <NUM> is shown. Audio screen layout <NUM> includes an audio band indicator <NUM>, a station indicator <NUM>, a song indicator <NUM>, a genre indicator <NUM>, a frequency indicator <NUM>, a mute input <NUM>, a previous stored favorite input <NUM>, and a next stored preset input <NUM>. In one embodiment, audio band indicator <NUM> allows the operator to change audio sources when display <NUM> displays multiple layouts or regions of information.

Referring to <FIG>, a second exemplary audio screen layout <NUM> is shown. Audio screen layout <NUM> includes a song or album graphic indicator <NUM>, a song duration indicator <NUM>, a song title indicator <NUM>, an artist indicator <NUM>, an album indicator <NUM>, and a pause input <NUM>.

Referring to <FIG>, an exemplary connectivity screen layout <NUM> is shown. Connectivity screen layout <NUM> includes a first region <NUM> and a second region <NUM>. First region <NUM> includes a driver portable communication device connection status indicator <NUM> for the driver portable communication device <NUM>, a signal strength indicator <NUM> for the driver portable communication device <NUM>, a battery life indicator <NUM> for the driver portable communication device <NUM>, a call status indicator <NUM> for the driver portable communication device <NUM>, and a text message status indicator <NUM> for the driver portable communication device <NUM>. Second region <NUM> provides a driver audio interface device connection status indicator <NUM> for the driver audio interface device <NUM>. In one embodiment, connectivity screen layout <NUM> further includes indicators for passenger portable communication device <NUM> and passenger audio interface device <NUM>. It will be understood by one of skill in the art the values reported in indicators for regions <NUM> and <NUM> are received from the respective driver portable communication device <NUM> and driver audio interface device <NUM> by one or more of the controllers of vehicle <NUM>. Driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and passenger audio interface device <NUM> may be connected to motorcycle <NUM> through one or more wired connections or through one or more wireless connections. Exemplary wired connections include through one or more USB inputs on motorcycle <NUM>. Exemplary wireless connections include through a BLUETOOTH protocol over a radio frequency network.

Referring to <FIG>, an exemplary map/navigation screen layout <NUM> is shown. Map/navigation screen layout <NUM> includes a map <NUM>, a vehicle location indicator <NUM>, a zoom out input <NUM>, and a zoom in input <NUM>. It will be understood by one of skill in the art that the location indicator <NUM> is based on information received by one or more of the controllers of vehicle <NUM> from location determiner <NUM>. Further, the zoom out and in inputs <NUM> and <NUM> control the zoom level associated with map <NUM>. Map <NUM> may display additional information including points of interest information, traffic information, and other types of information. Exemplary information for presentation through map/navigation screen layout <NUM> is disclosed in PCT Patent Application No. <CIT>, entitled "RECREATIONAL VEHICLE INTERACTIVE TELEMETRY, MAPPING, AND TRIP PLANNING SYSTEM" (Attorney Docket No.: PLR-00TC-<NUM>-04P-WO-E). Further, motorcycle <NUM> may be associated with a group of other recreational vehicles and information regarding the group may be presented through map/navigation screen layout <NUM>. Exemplary group information is disclosed in PCT Patent Application No. <CIT>.

Referring to <FIG>, a representation of a first screen layout <NUM> for display <NUM> is shown. Screen layout <NUM> includes a first region <NUM>, a second region <NUM>, a third screen region <NUM>, and a fourth screen region <NUM>. Regions <NUM>-<NUM> are positioned in a non-overlapping arrangement on display <NUM>. Each of regions <NUM>-<NUM> are customizable by the operator of vehicle <NUM>. The operator can select the information to be displayed in each of regions <NUM>-<NUM> from a preset list of options.

In one embodiment, the predefined of options for regions <NUM> and <NUM> include a map screen layout, a trip <NUM> screen layout, a trip <NUM> screen layout, and an audio screen layout. <FIG> illustrates the selection of a map screen layout <NUM> for region <NUM>. <FIG> illustrates a selection screen layout <NUM> for one of regions <NUM> and <NUM>. An operator selects region <NUM> through the touch screen of display <NUM> and sub-menu <NUM> is presented on display <NUM>. The operator then selects through the touch screen of display <NUM> the desired screen layout. The selected options are stored in memory <NUM> of instrument cluster <NUM>.

In one embodiment, the predefined of options for regions <NUM> and <NUM> include a vehicle speed screen layout, a vehicle rpm screen layout, a vehicle battery volt screen layout, a distance to empty screen layout, a gear indicator screen layout, an engine status screen layout, a fuel level screen layout, a connectivity screen layout, a tire pressure screen layout, and a vehicle accessory screen layout. <FIG> illustrates the selection of a distance to empty screen layout <NUM> for region <NUM>. <FIG> illustrates a selection screen layout <NUM> for one of regions <NUM> and <NUM>. An operator selects region <NUM> through the touch screen of display <NUM> and sub-menu <NUM> is presented on display <NUM>. The operator then selects through the touch screen of display <NUM> the desired screen layout. The selected options are stored in memory <NUM> of instrument cluster <NUM>.

Returning to <FIG>, the first riding screen layout <NUM> (<FIG>) includes first trip option screen layout <NUM> for first region <NUM> and map/navigation screen layout <NUM> for second region <NUM>, the second riding screen layout <NUM> (<FIG>) includes first exemplary audio screen layout <NUM> for first region <NUM> and a custom image screen layout <NUM> for second region <NUM>, and the third riding screen layout <NUM> (<FIG>) includes first exemplary screen layout <NUM> for first region <NUM> and first exemplary vehicle status screen layout <NUM> for second region <NUM>. The custom image screen layout <NUM> displays either a present image stored in memory <NUM> or a user supplied image which is also stored in memory <NUM>. An operator can sequentially cycle through the three riding screens <NUM>, <NUM>, <NUM> presented in <FIG> by repeatably selecting riding screen input button <NUM> of instrument cluster <NUM>.

Referring to <FIG>, an audio screen layout <NUM> for display <NUM> of instrument cluster <NUM> is shown. Audio screen layout <NUM> is presented on display <NUM> when the operator selects audio selection input button <NUM> of instrument cluster <NUM>. Audio screen layout <NUM> includes an audio source selection input <NUM> wherein the operator may select between an FM band, an AM band, a weather source, an audio source from a Bluetooth connected device, and an audio source from a USB connected device. Audio screen layout <NUM> further includes a volume down input <NUM>, a volume up input <NUM>, and a mute input <NUM>. Further, audio screen layout <NUM> includes a plurality of favorites <NUM> listed across a bottom portion of audio screen layout <NUM>. Additional favorites may be displayed through selection input <NUM> of audio screen layout <NUM>. Audio screen layout <NUM> further presents a genre selection input <NUM> and a discovery input <NUM>. By selecting a specific genre through input <NUM> and selecting discovery input <NUM>, the controller of vehicle <NUM> scans the FM frequency band to discover radio stations matching the selected genre. In this way, an operator of vehicle <NUM> can populate their presets with stations corresponding to a desired genre when they are located outside of their home traveling area.

Referring to <FIG>, a power off screen layout <NUM> for display <NUM> of instrument cluster <NUM> is illustrated. Power off screen layout <NUM> is displayed in response to an operator selecting power button <NUM> of instrument cluster <NUM>. A selection of power button <NUM> for a first duration results in power off screen layout <NUM> being displayed. Additionally, a selection of power button <NUM> for a second, longer duration results in display <NUM> being turned off (i.e., a black screen) however audio may be still be played or otherwise distributed to the user. This allows a user to turn off display <NUM>, for example at night to avoid glare, while still allowing the user to have music, phone, or other audio input. Also, a selection of power button <NUM> for a third and still longer duration results in display <NUM> of instrument cluster <NUM> being completely turned off, including both display <NUM> and all audio input. In this way, power off screen layout <NUM> allows the operator to have three different power off options. Further, as illustrated in <FIG>, power off screen layout <NUM> includes an indication of the current time.

Referring to <FIG>, an exemplary connectivity screen layout <NUM> is shown. Connectivity screen layout <NUM> includes a first region <NUM> and a second region <NUM>. First region <NUM> includes a driver portable communication device connection status indicator <NUM> for the driver portable communication device <NUM>, a signal strength indicator <NUM> for driver portable communication device <NUM>, a battery life indicator <NUM> for driver portable communication device <NUM>, a place call selection input <NUM>, and a compose text message input <NUM>. The place call input <NUM> sends instructions to driver portable communication device <NUM> requesting that a call be placed. In a similar fashion, selection of compose text message input <NUM> sends a request to driver portable communication device <NUM> to begin a new text message. Second region <NUM> provides a driver audio interface connection status identifier <NUM> for driver audio interface device <NUM>. In one embodiment, connectivity screen layout <NUM> further includes indicators for passenger portable communication device <NUM> and passenger audio interface device <NUM>. It will be understood by one of skill in the art that the values reported in the indicators for regions <NUM> and <NUM> are received from the respective driver portable communication device <NUM> and driver audio interface device <NUM> by one or more controllers of vehicle <NUM>.

Referring to <FIG>, an exemplary map/navigation screen layout <NUM> for display <NUM> of instrument cluster <NUM> is shown. The map/navigation screen layout is presented on display <NUM> in response to the user selecting navigation button <NUM> of instrument cluster <NUM>. Through the map/navigation screen layout <NUM>, an operator may be provided turn by turn navigation instructions, point of interest and address lookup functionality, and pinch to zoom functionality.

In addition to being able to navigate between first riding screen layout <NUM>, second riding screen layout <NUM>, third riding screen layout <NUM>, audio screen layout <NUM>, connectivity screen layout <NUM>, and map/navigation screen layout <NUM> through the use of riding screen input button <NUM>, audio selection input button <NUM>, connectivity button <NUM>, and navigation button <NUM>, an operator of motorcycle <NUM> may further cycle through the screens through inputs provided as part of second portion <NUM> of user interface assembly <NUM> and/or third portion <NUM> of user interface assembly <NUM>.

Referring to <FIG>, an exemplary processing sequence of one or more of the controllers of vehicle <NUM> is shown. As indicated in <FIG>, an operator of vehicle <NUM> may cycle through sequentially first riding screen layout <NUM>, second riding screen layout <NUM>, third riding screen layout <NUM>, audio screen layout <NUM>, connectivity screen layout <NUM>, and map/navigation screen layout <NUM> by repeatedly selecting left-hand trigger input button <NUM> of second portion <NUM> of user interface assembly <NUM>. In this manner an operator may view each screen without having to remove his or her hands from handlebar <NUM>. It is of further note that with this arrangement motorcycle <NUM> does not include a home screen but rather provides easy navigation between a plurality of different screen layouts. In one embodiment, connectivity screen layout <NUM> may be omitted.

When map/navigation screen layout <NUM> is presented on display <NUM>, an operator of motorcycle <NUM> may select other features of map/navigation screen layout <NUM> as detailed in the processing sequence <NUM> illustrated in <FIG>. The operator of vehicle <NUM> enters the sub-features of map/navigation screen layout <NUM> through actuation of right-hand trigger input button <NUM> of third portion <NUM>. Upon actuation of right-hand trigger input button <NUM>, the point of interest input is highlighted as represented by block <NUM>. By actuating right-hand trigger input button <NUM> a second time, a point of interest listing is displayed as represented by block <NUM>, such as gas stations, restaurants, campgrounds, etc. The points of interest option also may allow an operator to identify favorite points of interests and may store those locations by name, geographic information (e.g., geographic coordinates), or any other identifying information for easy access to the operator when searching for a favorite point of interest. An operator may toggle down the point of interest list through the actuation of toggle input <NUM> as indicated by block <NUM> or toggle up the point of interest list through the actuation of toggle input <NUM> as indicated by block <NUM>. Alternatively, an operator may return to the main map screen to the highlighted points of interest input through actuation of left-hand trigger input button <NUM> or bring up a category listing through actuation of right-hand trigger input button <NUM> as represented by block <NUM>. Once a category listing is displayed, an operator may toggle down categories through actuation of toggle down input <NUM> as represented by block <NUM> and toggle up the category listing through actuation of toggle up input <NUM> as represented by block <NUM>. Alternatively, an operator may select a destination through actuation of input <NUM> as represented by block <NUM>. A further actuation of input <NUM> results in navigation instructions to be initiated as represented by block <NUM>. The navigation instructions provide one or more of audio and visual cues to direct an operator of vehicle <NUM> to the destination based on a current location of vehicle <NUM>. Alternatively, an operator may return to the category listing through actuation of input <NUM>.

Returning to block <NUM>, an operator may select to return to map/navigation screen layout <NUM> through actuation of left-hand trigger input button <NUM> or to advance to highlighting a favorites listing through the selection of toggle up input <NUM> as represented by block <NUM>. In one embodiment the favorites include user selected destinations that are stored in memory associated with one or more controllers of vehicle <NUM>. From block <NUM> an operator can return to block <NUM> through an actuation of toggle down input <NUM>, return to map/navigation screen layout <NUM> through an actuation of left-hand trigger input button <NUM>, or advance to highlight a recent destinations option through actuation of toggle up input <NUM> as represented by block <NUM>. In one embodiment the recent destinations option includes destinations that vehicle <NUM> has recently visited. From block <NUM> an operator can advance to block <NUM> through an actuation of toggle up input <NUM>, return to block <NUM> through an actuation of toggle down input <NUM>, or return to map/navigation screen layout <NUM> through an actuation of left-hand trigger input button <NUM>. Returning to block <NUM>, a user may choose to display a favorites list through the actuation of right-hand trigger input button <NUM> as represented by block <NUM>. A user may toggle down the list of favorites through an actuation of toggle down input <NUM> as represented in block <NUM> or toggle up the list of favorites through an actuation of input <NUM> as represented by block <NUM>. Alternatively, a user can return to block <NUM> through actuation of left-hand trigger input button <NUM> or select a highlighted favorite through the actuation of right-hand trigger input button <NUM> as represented by block <NUM>. From block <NUM> an operator may return to the favorites listing through the actuation of left-hand trigger input button <NUM> or begin navigation to the selected destination through actuation of right-hand trigger input button <NUM>.

Returning to block <NUM>, an operator may elect to display a listing of recent destinations through the actuation of right-hand trigger input button <NUM> as represented by block <NUM>. An operator may toggle down a listing of recent destinations through the actuation of input <NUM> as represented by block <NUM> or toggle up a listing of recent destinations through the actuation of input <NUM> as represented by block <NUM>. Alternatively, an operator may return to block <NUM> through the actuation of input <NUM> or select a recent destination through the actuation of right-hand trigger input button <NUM> as represented by block <NUM>. The operator can select to begin navigation through the actuation of right-hand trigger input button <NUM> or return to the listing of recent destinations through the actuation of input <NUM>. Once navigation has been selected as represented by block <NUM>, display <NUM> returns to map/navigation screen layout <NUM> to provide updates on the location of vehicle <NUM> and instructions to the selected destination.

It may be appreciated that the user can toggle through information on display <NUM> by actuating input buttons <NUM>, <NUM> in a predetermined manner. For example, the user may depress or otherwise actuate input button <NUM> and/or input button <NUM> one or more times (e.g., at least two times) to toggle through information or options shown on display <NUM>. Alternatively, the user may press and hold input button <NUM> and/or input button <NUM> for a predetermined length of time to also effect a change on display <NUM> (e.g., to toggle through information on display <NUM>). In one embodiment, pressing and holding input button <NUM> and/or input button <NUM> for a predetermined length of time may be defined as multiple inputs or actuations on inputs <NUM>, <NUM>. For example, pressing and holding input button <NUM> for a first time period may be considered a first actuation and holding for a second time period may be considered a second actuation, the second time period being longer than the first time period.

Referring to <FIG>, a representation of motorcycle <NUM>, driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and passenger audio interface device <NUM>. Driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and passenger audio interface device <NUM> may be connected to motorcycle <NUM> through one or more wired connections or through one or more wireless connections. Each of driver audio interface device <NUM> and passenger audio interface device <NUM> includes at least one microphone and at least one speaker. Exemplary wired connections include through one or more USB inputs on motorcycle <NUM>. Exemplary wireless connections include through a BLUETOOTH protocol over a radio frequency network. In one embodiment, each of driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and passenger audio interface device <NUM> are paired with motorcycle <NUM> through a BLUETOOTH protocol over a radio frequency network. In one embodiment, vehicle controller <NUM> of motorcycle <NUM> is configured to communicate with at least three of driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and <NUM> through a wireless network. In one embodiment, vehicle controller <NUM> of motorcycle <NUM> is configured to communicate with each of driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and <NUM> through a wireless network.

Referring to <FIG>, vehicle controller <NUM> is configured to communicate with each of driver portable communication device <NUM>, driver audio interface device <NUM>, passenger portable communication device <NUM>, and passenger audio interface device <NUM> through a wireless network. When a call is either initiated by driver portable communication device <NUM> or received by driver portable communication device <NUM>, vehicle controller <NUM> routes the audio information received from driver portable communication device <NUM> to driver audio interface device <NUM> through motorcycle <NUM> and the audio information received from driver audio interface device <NUM> to driver portable communication device <NUM> through motorcycle <NUM>. The audio information is not routed to either of passenger portable communication device <NUM> or passenger audio interface device <NUM>. Referring to <FIG>, when a call is either initiated by passenger portable communication device <NUM> or received by passenger portable communication device <NUM>, vehicle controller <NUM> routes the audio information received from passenger portable communication device <NUM> to passenger audio interface device <NUM> through motorcycle <NUM> and the audio information received from passenger audio interface device <NUM> to passenger portable communication device <NUM> through motorcycle <NUM>. The audio information is not routed to either of driver portable communication device <NUM> or driver audio interface device <NUM>.

Referring to <FIG>, an exemplary processing sequence <NUM> is illustrated for handling an incoming call by vehicle associated controller <NUM>. The processing sequence <NUM> will be described with reference to driver portable communication device <NUM> and driver audio interface device <NUM> although it is equally applicable to passenger portable communication device <NUM> and passenger audio interface device <NUM>. Driver portable communication device <NUM> receives an incoming call as represented by block <NUM>. Driver portable communication device <NUM> then notifies vehicle controller <NUM> of the incoming call as represented by block <NUM>. Vehicle controller <NUM> provides an indication to the user of the incoming call as represented by block <NUM>. Exemplary indications of the incoming call include audio indicators, visual indicators, and tactile indicators.

Referring to <FIG>, an exemplary visual indicator <NUM> which is displayed on display <NUM> is shown. Indicator <NUM> provides information <NUM> regarding the incoming call, an answer input <NUM> to accept incoming call, and an ignore input <NUM> to deny the incoming call. In one embodiment, an operator may provide either an answer indication or ignore indication through driver audio interface device <NUM> as a verbal command.

Returning to <FIG>, a decision is made by the operator to either accept the call or ignore the call as represented by block <NUM>. If the call is not accepted, the call notification indicator <NUM> is removed from first display <NUM> as represented by block <NUM>. If the call is accepted, vehicle controller <NUM> sends a request to accept the call to driver portable communication device <NUM> and through call audio to the vehicle associated controller as represented by block <NUM>. Driver portable communication device <NUM> receives the request to accept the call as represented by block <NUM>. Driver portable communication device <NUM> accepts the call as represented by block <NUM>. Driver portable communication device <NUM> sends and receives audio information from its cellular connection to vehicle controller <NUM> as represented by block <NUM>. Vehicle controller <NUM> sends and receives audio to and from driver portable communication device <NUM> through the Bluetooth wireless network as represented by block <NUM>. vehicle controller <NUM> also sends and receives audio from the driver audio interface device <NUM> as represented by block <NUM>.

Referring <FIG>, an exemplary processing sequence <NUM> for vehicle controller <NUM> is shown. Processing sequence <NUM> details how to place a call with driver portable communication device <NUM>. The processing sequence <NUM> will be described with reference to driver portable communication device <NUM> and driver audio interface device <NUM> although it is equally applicable to passenger portable communication device <NUM> and passenger audio interface device <NUM>. Vehicle controller <NUM> receives a request to place a call as represented by block <NUM>. In one embodiment, the request to place a call is received through first display <NUM>. In one embodiment, the request to place a call is a voice command received from driver audio interface device <NUM>. Vehicle controller <NUM> sends a request to place a call to driver portable communication device <NUM> and a request to route audio back to vehicle controller <NUM> as represented by block <NUM>. Driver portable communication device <NUM> receives the request to place the call as represented by block <NUM>. Driver portable communication device <NUM> places the call as represented by block <NUM>. Driver portable communication device <NUM> sends and receives audio from its cellular connection to vehicle controller <NUM> as represented by block <NUM>. Vehicle controller <NUM> sends and receives audio from driver portable communication device <NUM> through the BLUETOOTH wireless network as represented by block <NUM>. Further, vehicle controller <NUM> sends and receives audio to driver audio interface device <NUM> through the BLUETOOTH network as represented by block <NUM>.

Referring to <FIG>, an incoming text notification indicator <NUM> is shown on display <NUM>. Incoming text notification indicator <NUM> provides information regarding the sender of the text and information <NUM> of the sender of the text. The operator may select either a quick reply input <NUM> or a close input <NUM> provided on display <NUM>.

As can be seen from <FIG>, exemplary visual indicator <NUM> and incoming text notification indicator <NUM> are overlaid over the then currently displayed screen layout of display <NUM>. Referring to <FIG>, exemplary visual indicator <NUM> and incoming text notification indicator <NUM> are displayed regardless of which screen is being shown on display <NUM>. In addition to selecting either answer input <NUM> or ignore input <NUM> for call indicator <NUM> or quick reply input <NUM> or close input <NUM> for incoming text notification indicator <NUM>, an operator can utilize the inputs provided in second portion <NUM> of user interface assembly <NUM> and third portion <NUM> of user interface assembly <NUM>. In response to exemplary visual indicator <NUM>, an operator may choose to ignore the call as represented by block <NUM> by actuating left-hand trigger input button <NUM> or to answer the call as represented by block <NUM> through the actuation of right-hand trigger input button <NUM>. If the call has been answered, the operator may end the call as represented by block <NUM> through the actuation of input <NUM>. In the case of incoming text notification indicator <NUM> being displayed on first display <NUM>, an operator may select to ignore the text as represented by block <NUM> through the actuation of input <NUM> or to activate the quick reply list as represented by block <NUM> through the actuation of input <NUM>. The operator may exit the quick reply list as represented by block <NUM> through the actuation of left-hand trigger input button <NUM>. Further, an operator may toggle up the quick reply list as represented by block <NUM> through actuation of input <NUM> or toggle down the quick reply list as represented by block <NUM> through the actuation of input <NUM>. In addition, once an appropriate reply has been selected, the operator may select to send the selected reply as represented by block <NUM> through the actuation of right-hand trigger input button <NUM>.

Referring to <FIG>, vehicle <NUM> includes power system <NUM>, electrical system <NUM>, a plurality of accessories <NUM>, and sensors <NUM>. Electrical system <NUM> may be electrically coupled to a server system <NUM> to store and/or access various information for vehicle <NUM>. Server system <NUM> is also accessible via a plurality of other computing devices, such as a mobile device (e.g., a mobile phone or tablet device) and/or a computing device having a web browser installed thereon. Server system <NUM>, electrical system <NUM>, and any component of vehicle <NUM> or component or accessory belonging to a user or passenger may be operatively coupled together via any wired or wireless communication system, mechanism, or process, such as through wifi communication, Bluetooth®, cellular system, satellite systems, etc. A plurality of third-party data services may be integrated with the information delivered to an operator of vehicle <NUM> and owner of the mobile or computer devices. The data services, provided by a data provider, allow for integration of a variety of types of data in a user interface coordinated by server system <NUM>. In the embodiment shown, the data providers may include a map data provider, a weather data provider, a GIS data provider, and a trail condition data provider. The various data providers are communicatively interconnected with server system <NUM> via a network, such as the Internet. Additionally, such a network is used by users of the mobile or computing devices for communicative interconnection to server system <NUM>, as disclosed in PCT Patent Application No. <CIT>, entitled "RECREATIONAL VEHICLE INTERACTIVE TELEMETRY, MAPPING, AND TRIP PLANNING SYSTEM" (Attorney Docket No.: PLR-00TC-<NUM>-04P-WO-E).

In one embodiment, as shown in <FIG>, electrical system <NUM> includes a controller area network ("CAN") interface <NUM> electrically coupled to vehicle control unit ("VCU") <NUM> which comprises at least an alternative embodiment display <NUM>, at least one controller <NUM>, and a plurality of sensors <NUM>, such as temperature sensors, speed sensors, pressure sensors, and any other sensor configured to determine a parameter of any component of vehicle <NUM>. As shown in <FIG>, controller <NUM> is operably coupled to power system <NUM>, accessories <NUM>, and display <NUM> to receive information from various components of vehicle <NUM> and transmit information about such components to display <NUM> for the operator's review. For example, controller <NUM> also is coupled to a communication interface <NUM> which may a cellular or satellite communication interface connectable to server system <NUM>. Illustrative display <NUM> is configured to provide various data or information about the operating conditions of vehicle <NUM>, ambient conditions, infotainment (e.g., radio), vehicle location via a global positioning system ("GPS") antenna, wireless connectivity, and/or any other information that may be useful to the operator during operation of vehicle <NUM>.

In one embodiment, as shown in <FIG>, display <NUM> may be supported on vehicle <NUM> like display <NUM> and is positioned longitudinally forward of the operator during operation of vehicle <NUM>, as disclosed in PCT Patent Application No. <CIT>. An illustrative embodiment of display <NUM> is shown in <FIG>. Display <NUM> may be a color, touch-screen display with a plurality of pixels configured to change in response to an operator input. For example, the operator may use his/her finger to select options on display <NUM> and receive information about vehicle <NUM>, ambient conditions, etc. Display <NUM> may include a plurality of sensors, such as pressure sensors or capacitive sensors (not shown), to determine the presence of the operator's finger on display <NUM>. As such, display <NUM> is configured to distinguish between the presence of mud, dirt, or debris thereon and the operator's finger such that only the operator's finger on display <NUM> accesses the various information and options on display <NUM>. In one embodiment, the sensors for display <NUM> allow touch operation of display <NUM> whether the operator is wearing gloves or not.

Additionally, as shown in <FIG>, display <NUM>, fairing <NUM>, and/or handlebars <NUM> may support a plurality of inputs <NUM> which also allows the operator to change the information presented on display <NUM> and also access various features of vehicle <NUM> (e.g., a radio, GPS, Bluetooth® , a power input, and other infotainment options). Illustratively, inputs <NUM> may define hard or push buttons positioned below display <NUM> on fairing <NUM> (<FIG>). Inputs <NUM> may allow for quick access to specific information by touching inputs <NUM> and also may allow the operator to toggle through various screens on display <NUM>. For example, as shown in <FIG>, inputs <NUM> may include a gauge input <NUM> to allow the operator to immediately toggle between the various screens on display <NUM>, as disclosed herein, an infotainment input <NUM> to allow the operator to quickly access music via the radio or other media and provide other entertainment options to the operator, a location input <NUM> which allows the operator immediate access to GPS information and maps, as disclosed herein, a connectivity input <NUM> to allow the operator to immediately access his/her phone or other communications device via CAN interface <NUM>, and a settings input <NUM> to allow the operator to quickly access the various settings for display <NUM> and vehicle <NUM>.

Referring to <FIG>, display <NUM> is configured to display a plurality of screens with various information to the operator and allows the operator to change the output on display <NUM> during operation of vehicle <NUM>. In one embodiment, display <NUM> includes a main or home screen <NUM> which displays current information about the operation of vehicle <NUM>. For example, home screen <NUM> includes a plurality of areas configured to display information about vehicle speed, coolant or oil temperature, battery life or voltage, fuel quantity, transmission gear, etc. Illustratively, home screen <NUM> includes a speed portion <NUM> to output the vehicle to the operator, a tachometer portion <NUM>, an odometer portion <NUM>, a battery portion <NUM>, a fuel quantity portion <NUM>, a gear portion <NUM>, and a drive wheel portion <NUM> indicating if vehicle <NUM> is in an all-wheel drive mode, a four-wheel drive mode, or a two-wheel drive mode.

Additionally, as shown in <FIG>, home screen <NUM> includes a status bar <NUM> in the upper portion of display <NUM>. Status bar <NUM> may include the status of the operator's phone (i.e., whether the phone is connected to vehicle <NUM> through Bluetooth® at connectivity portion <NUM> and if there is a text message or a missed call at phone notifications portion <NUM>). Additionally, status bar <NUM> also may indicate the ambient temperature at temperature portion <NUM>, direction of vehicle <NUM> at compass portion <NUM>, and the time at clock portion <NUM>. Any other features, indicators, notifications, or information may be included in status bar <NUM> and, in one embodiment, display <NUM> is configured for customization by the operator to allow the operator to see any desired information in a given screen of display <NUM>. Status bar <NUM> is configured to be maintained in the upper portion of display <NUM> regardless of the screen or output displayed to the operator. As such, status bar <NUM> is universally used with all screens on display <NUM>.

Additionally, when an operator touches and releases or slides his/her finger downward from status bar <NUM>, display <NUM> may provide a plurality of options for the operator, such as options to switch to another screen, see the status of other components, features, or accessories of vehicle <NUM>, and/or review any notifications about vehicle <NUM> or accessories <NUM>. In this way, status bar <NUM> also may provide a return feature of display <NUM> so that the operator may utilize the drop-down type menu in status bar <NUM> to access other information on previous screens or advance to other screens. Alternatively, display <NUM> may be configured such that when the operator desires to return to a previous screen, for example home screen <NUM>, the operator may slide his/her finger in a right or left direction along display <NUM>. In addition to using his/her finger on display <NUM>, the operator may access other screens on display <NUM> by touching inputs on display <NUM>, fairing <NUM>, and/or handlebars <NUM>.

As shown in <FIG>, one of the screens provided on display <NUM> is an options screen <NUM> which is configured to display a plurality of options to the operator regarding various information that may be output on display <NUM>. For example, options screen <NUM> includes a plurality of inputs <NUM> which may indicate each specific function or information textually or pictorially through words or visual images. In one embodiment, inputs <NUM> listed on options screen <NUM> include a power or on/off input <NUM>, a drive mode input <NUM>, an accessories input <NUM>, a settings input <NUM>, a diagnostics input <NUM>, a suspension settings input <NUM>, a clutch settings input <NUM>, a speed key input <NUM>, and a drive status input <NUM>. Once at options screen <NUM>, the operator may navigate through options screen <NUM> to access a variety of information about vehicle <NUM>, accessories, ambient conditions, etc., as disclosed herein and according to <FIG>.

Display <NUM> may be configured to output various information to the operator in a plurality of manners. For example, display <NUM> may be configured to display information in a dual analog manner, a digital manner, or a standard manner with a manual or digital scroll bar (not shown) on the left and/or right side of display <NUM> to scroll through options on the screen.

It may be appreciated that various illustrative embodiments of the options and information configured to be provided to display <NUM> are disclosed herein, however, the operator may be able to customize or otherwise configure display <NUM> and/or VCU <NUM> to provide any information about vehicle <NUM>. As such, the illustrative embodiments disclosed herein are not intended to be exhaustive and merely provide examples of the information the operator may be able to access via display <NUM>. Additional details of display <NUM> and the illustrative embodiments disclosed herein may be disclosed in PCT Patent Application No. <CIT>, entitled "RECREATIONAL VEHICLE INTERACTIVE TELEMETRY, MAPPING, AND TRIP PLANNING SYSTEM" (Attorney Docket No.: PLR-00TC-<NUM>-04P-WO-E).

Referring to <FIG> and <FIG>, display <NUM> may automatically turn on when vehicle <NUM> is turned on via a key, push button, remote starter, security key, fob, or any other device. Alternatively, display <NUM> may not turn on until the operator expressly turns on display <NUM>. For example, when the operator views display <NUM>, the operator may initially note whether display <NUM> is turned on. If vehicle <NUM> is not turned on, display <NUM> also may not be turned on. However, if vehicle <NUM> is turned on, the operator may turn on display <NUM> through power input <NUM>. In one embodiment, power input <NUM> is displayed on options screen <NUM>, however, display <NUM>, fairing <NUM>, and/or handlebars <NUM> also may include a power input (not shown) within inputs <NUM> (<FIG>) to turn on display <NUM> when options screen <NUM> is not visible.

Referring still to <FIG>, with display <NUM> turned on, the operator may access options screen <NUM> by selecting one of inputs <NUM>, swiping his/her finger left or right on display <NUM>, and/or accessing the drop-down menu from status bar <NUM>. For example, when the operator desires to turn off display <NUM>, the operator may access power input <NUM> on options screen <NUM> or through inputs <NUM> on fairing 244and/or handlebars <NUM> to turn off display <NUM>.

With respect to <FIG>, when display <NUM> turned on, the operator may desire to determine and/or change a drive mode of vehicle <NUM>. For example, the operator may access drive modes input <NUM> on options screen <NUM> or through inputs <NUM> on fairing <NUM> and/or handlebars <NUM> to display the drive modes available for vehicle <NUM>. In one embodiment, and as shown in <FIG>, the drive modes for vehicle <NUM> may be an eco or economy mode to conserve fuel, a normal mode, and/or a sport mode for additional speed and/or power output from power system <NUM>. Additionally, drive modes input <NUM> may allow the operator to select the terrain on which vehicle <NUM> is operating, for example mud terrain, snow terrain, sand terrain, hill climb or ascent, hill decline or descent, and/or any other terrain condition for which vehicle <NUM> is configured. In one embodiment, drive modes input <NUM> also allows the operator to select all-wheel drive, four-wheel drive, or two-wheel drive modes. In this way, the operator may make more than one selection when accessing drive modes input <NUM>. The operator may select the drive mode(s) desired by touching display <NUM> and/or through an input on fairing <NUM> and/or handlebars <NUM>.

When at options screen <NUM> (<FIG>), the operator may select accessories input <NUM> to access accessories <NUM> for vehicle <NUM>, as shown in <FIG> and <FIG>. For example, accessories <NUM> for vehicle <NUM> may include a radio, GPS or mapping function, head lights, fog lights, internal lights, electric power steering ("EPS"), Bluetooth®, a camera, saddle bags, a trunk, a windshield, adjustable suspension assemblies, or any other function, feature, component, or device configured for vehicle <NUM>.

Once the operator selects accessories input <NUM>, the operator may select one or more of accessories <NUM> to access. For example, the operator may select an accessory audio or radio function and display <NUM> may provide options for fade, balance, and any other inputs to control the accessory audio on vehicle <NUM>.

Additionally, as shown in <FIG>, the operator may select a lights option <NUM> to turn on or off the headlight, ground lights, accent lights, underglow lights, fog lights, or internal lights to illuminate a portion of the operator space (e.g., dome or cabin lights) of vehicle <NUM>. In one embodiment, any of the lights on vehicle <NUM> may have color-changing LED lights and lights option <NUM> may allow the operator to change the color of any of the lights on vehicle <NUM>.

Additionally, the operator may select an EPS option <NUM> to utilize the EPS of vehicle <NUM> in a high, medium, or low mode by accessing the accessories input <NUM>.

Additionally, as shown in <FIG>, the operator may access a windshield option <NUM> to adjust the position of the windshield for vehicle <NUM> to move the windshield upward or downward during operation of vehicle <NUM>.

In one embodiment, one of accessories <NUM> of vehicle <NUM> includes a garage door opener which may be electrically coupled to electrical system <NUM> of vehicle through a wireless or a wired connection and accessed and controlled through accessories input <NUM> on display <NUM>. For example, the operator may position a universal garage door opener on any location of vehicle <NUM> (e.g., in a storage console) and a CAN or other type of signal may be sent from display <NUM> to the garage door opener to allow the operator to control opening and closing of the garage door through display <NUM>. Alternatively, a garage door opener may be integrated into the vehicle.

With accessories input <NUM> (<FIG> and <FIG>), the operator also may elect to connect to his/her phone, access the radio, access GPS and/or map information for local terrain and/or location of vehicle <NUM> and/or other riders in the area, etc. For example, as shown in <FIG> and <FIG>, an illustrative embodiment maps option <NUM> provides a map of the location of vehicle <NUM> which is shown on display <NUM>. Additionally, maps option <NUM> allows for turn-by-turn directions or other navigation features during operation of vehicle <NUM>. In one embodiment, when the map is shown on display <NUM>, the speed of vehicle <NUM>, the amount of fuel remaining in the fuel tank of vehicle <NUM>, the coordinates of vehicle <NUM>, and other information also may be displayed.

Because display <NUM> may be operated by the operator's fingers, the operator may pull his/her fingers apart to zoom in to a particular area of the map (<FIG>), push his/her fingers toward each other to zoom out and access more of the location shown on the map (<FIG>), and/or move his/her fingers upward, downward, to the right, or to the left to move the viewing portion of the map to a different area (<FIG>). Additionally, using GPS coordinates of vehicle <NUM> through the operator's phone GPS function or GPS on vehicle <NUM>, the map feature of vehicle <NUM> may allow a rider to pinpoint the current location of vehicle <NUM> (i.e., "drop a pin" on the map) and subsequently name the location for future ride mapping and/or to provide the current location to other vehicles. In this way, maps option <NUM> of vehicle <NUM> may then trace the route of vehicle <NUM> and allow the operator to save, name, or otherwise store and identify information about that route for future ride mapping. Additionally, in one embodiment, maps option <NUM> of vehicle <NUM> has a lockout feature that maintains the output of the map on display <NUM> and does not allow for changes to the map image provided on display <NUM> for at least a period of time or while vehicle <NUM> is operating at specific speeds.

Additionally, as shown in <FIG> and <FIG>, accessories input <NUM> allows the operator to access his/her phone through a phone option <NUM> (<FIG>). The operator's phone may be connected via Bluetooth®, and through phone option <NUM>, an illustrative screen as shown in <FIG> allows the operator to see the connection status, battery voltage, headset connectivity, and signal strength of the phone. Additionally, the operator is able to see any missed calls and/or text messages received on the phone. The illustrative embodiment of display <NUM> allows the operator's phone to be accessed through display <NUM> or by audible commands made into a headset that are transmitted through speakers to controller <NUM> to access the operator's phone. Additionally, more than one headset may be connected to vehicle <NUM>, for example both the driver and a passenger may each connect an individual headset to vehicle <NUM>. In one embodiment, both the driver and passenger headsets may be wirelessly connected to display <NUM> through any wireless, such as wifi, connection or may be connected to display <NUM> through a wired connection. In this way, vehicle <NUM> is configured to allow for simultaneous connection of more than one headset to allow more than one person on vehicle <NUM> to listen to audio, talk to others on vehicle <NUM>, access a phone or other features on or connected to vehicle <NUM>, etc. For example, Additionally, in one embodiment, the headsets may be wirelessly connected to each other to provide the driver and passenger(s) to talk or interconference with each other without going through any connection on vehicle <NUM>. Also, in a further embodiment, electrical system <NUM> of vehicle <NUM> may be configured to connect with more than one phone or device, such as a passenger's phone or an iPod® in addition to the operator's phone.

However, VCU <NUM> of vehicle <NUM> may be programmed to include specific lockout features for phone options <NUM> based on vehicle operating parameters. In one embodiment, phone options <NUM> of vehicle <NUM> may be locked out when vehicle <NUM> is operating above a predetermined speed. For example, phone options <NUM> of vehicle <NUM> may be temporarily disabled when vehicle <NUM> is operating above a predetermined speed such that operator is not aware of incoming phone calls or text messages. Alternatively, or in addition to, phone options <NUM> may include an "Ignore" option to ignore incoming phone calls and text messages while vehicle <NUM> is operating and/or a plurality of quick response messages indicating that the operator is not able to currently access his/her phone (e.g., "Driving. Will call/text you later.

Referring again to <FIG>, by accessing accessories input <NUM>, the operator can elect a camera option <NUM> to turn on and off a camera (not shown) and direct the viewfinder of the camera in a particular direction. The input from the camera is transmitted via controller <NUM> to display <NUM> such that the images being captured by the camera are displayed to the operator on display <NUM>. For example, any camera on vehicle <NUM> may be either directly wired to vehicle <NUM> (e.g., to the VCU and/or display <NUM>) or may be wirelessly connected to display <NUM> through, for example, a Bluetooth® connection. By connecting the camera(s) to display <NUM>, various settings for the camera(s) (e.g., resolution, mode, filter, etc.) may be adjusted via display <NUM>, rather than directly adjusting the settings on the camera itself or through an external device, such as a phone. Additionally, as shown in <FIG>, other information, such as vehicle speed shown at <NUM>, drive mode shown at <NUM>, gear selection shown at <NUM>, fuel level (not shown), music and volume (not shown), error codes (not shown), time (not shown), GPS information (not shown), coolant or oil temperature (not shown), and/or battery level (not shown), may be shown on display <NUM> when images from the camera also are shown. Display <NUM> provides two-way communication between the operator and the camera(s) because display <NUM> allows the operator to control any of the cameras on vehicle <NUM> through inputs associated with display <NUM> and the video and/or images captured by the camera(s) are transmitted to display <NUM> such that the operator can view the images and/or video taken by the camera(s), as shown in <FIG>. In this way, vehicle <NUM> and display <NUM> eliminate the need for the user to operate the camera(s) through his/her phone or other device because the camera(s) are fully integrated into vehicle <NUM>.

In one embodiment, the camera is configured for live photographs and video capabilities. However, once vehicle <NUM> is operating above a predetermined speed, display <NUM> may automatically switch to a different screen such that the complete visual output on display <NUM> is not constantly moving while the operator is driving vehicle <NUM>, as is the case when the input from the camera is shown on display <NUM>.

In one embodiment, at least one camera is provided at the front and/or rear of vehicle <NUM>. In this way, the camera(s) can capture images and video from forward-facing and rearward-facing views. For example, as shown in <FIG>, display <NUM> may include a camera icon <NUM> which allows the user to toggle between any of the cameras on vehicle <NUM>, including a front-facing camera, a rear-facing camera, a side-facing camera, etc. Because the cameras are either directly wired to display <NUM> or are wirelessly connected to display <NUM> via, for example, a Bluetooth® connection, display <NUM> recognizes multiple cameras and allows the user to toggle between the various cameras through icon <NUM> on display <NUM>. As such, a rear camera may be used as a back-up camera for vehicle <NUM>. Additionally, any camera on vehicle <NUM> may be configured to automatically record video once vehicle <NUM> is operating a particular speed so that the ride may be automatically recorded without input from the operator and reviewed later by the operator such that the camera acts as a live action or action sports camera to record the ride of vehicle <NUM>. For example, the camera may automatically begin recording when the vehicle is moving and may automatically stop recording when the vehicle stops moving. Alternatively, the user can control when the camera starts and stops recording through an input on display <NUM> shown at <NUM> in <FIG> and also can take a snapshot or static image shown on display <NUM> by selecting the input at <NUM> in <FIG> while the camera continues to record live images. In a further embodiment, the camera may automatically record images and information for a predetermined period of time (e.g., <NUM> seconds, <NUM> second, <NUM> second, <NUM> seconds, <NUM> seconds, <NUM> seconds, etc.) even if the user does not activate the camera. In this instance, the period of time automatically recorded by the camera may be saved as a loop, which the user may then opt to permanently save to a memory or may opt to overwrite to record additional images, video, and information from a subsequent ride.

In one embodiment, vehicle <NUM> may include any number cameras which may face in any direction into or out of vehicle <NUM>. For example, using a wireless connection (e.g., a Bluetooth® connection) or a USB device, any number of cameras may be connected to vehicle <NUM>. Additionally, once connected to vehicle <NUM>, the camera(s) are known to display <NUM> such that the operator select any/all of the cameras and can take static images and/or record video on any of the cameras by selecting an input on display <NUM>. Additionally, any of the cameras may provide additional information to the operator, such as if a person is approaching vehicle <NUM> quickly, if another vehicle is a "blind spot" of vehicle <NUM>, etc..

When the camera(s) records live video or taking static images, the information and images captured by the camera may be recorded to a memory of vehicle <NUM>, display <NUM>, or the camera itself. More particularly, the memory associated with the camera may be accessed through a USB port on vehicle <NUM> or remotely through Bluetooth® or wireless connectivity to a device. In one embodiment, all of the cameras on vehicle <NUM> may record images, video, and other information to a single memory location of vehicle <NUM> to consolidate the information from the cameras into a single location. Additionally, the images, video, and information captured by the camera(s) may be shared on social media, sent to contacts in a user's phone, or uploaded to a cloud when vehicle <NUM> is connected to a wifi, Bluetooth®, or any other wireless network or system. The images obtained from the camera may be reviewed either on an external device (e.g., a phone) or on display <NUM> via a playback function accessible through display <NUM>. Also, a summary screen may be shown on display <NUM>, as shown in <FIG>, to provide trip information to the rider after the camera has stopped recording a certain portion of the ride, when vehicle <NUM> is in Park, when engine <NUM> has stopped, or when any other parameter has been met. Additionally, the illustrative summary screen shown in <FIG> may be transmitted to a cloud, a memory, social media, or contacts of the rider to display information such as average speed at <NUM>, maximum speed at <NUM>, riding time at <NUM>, moving time at <NUM>, stop time at <NUM>, maximum lean of vehicle <NUM> at <NUM>, maximum climb or elevation of vehicle <NUM> at <NUM>, and maximum descent of vehicle <NUM> at <NUM>.

In a further embodiment, the camera(s) may be supported on a mechanically or electrically-controlled mount on vehicle <NUM> such that the user can manually adjust the position of the viewfinder of the camera or, through display <NUM>, the user may remotely adjust the position of the viewfinder.

Referring still to <FIG>, the operator can also adjust the output of the clock feature through a clock option <NUM>. Also, the operator can turn on and off the radio, change the station played by the radio, and/or access other media, such as iPod® devices, mp3 players, USB connections, etc. by accessing a radio/infotainment option <NUM> within accessories input <NUM>. In one embodiment, radio/infotainment option <NUM> may include a "discoverable" mode which would "learn" the operator's genre, artist, and song preferences and then predetermine playlists, artists, or genres that the operator may wish to listen to during a subsequent ride on vehicle <NUM>. Additionally, radio/infotainment option <NUM> may allow for preset favorites, such as preset radio or satellite stations.

Other of accessories <NUM> of vehicle <NUM> may include a security system for vehicle <NUM>. For example, by accessing a security option <NUM>, as shown in <FIG>, the operator may be able to lock saddle bags, a trunk, or any other storage compartment of vehicle <NUM>. Additionally, the operator may be able to input or change a security key, access security settings, and/or view all other security features of vehicle <NUM>. Additional features of a security system for vehicle <NUM> may be disclosed in PCT Patent Application numbers <CIT> and <CIT>.

Additionally, the security features of vehicle <NUM> may be configured to determine if an accident occurred or if vehicle <NUM> is in a roll-over situation. For example, as shown in <FIG>, if vehicle <NUM> is hit by another vehicle or in a roll-over situation, a sensor (e.g., a position sensor) may be triggered or otherwise determine that the roll-over or accident has occurred. The sensor or other feature of vehicle <NUM> may then transmit a signal to controller <NUM> in order for security option <NUM> to allow for an automatic call for help. In one embodiment, a call may be placed to <NUM> or to a local emergency services unit to alert that vehicle <NUM> has rolled over. Additionally, a call may be placed to a person in the operator's contact list or phone book if an accident or roll-over has occurred. In one embodiment, a call or alert may be provided to any vehicle in the local area based on the proximity of other vehicles to vehicle <NUM>. As such, the security system or security features of vehicle <NUM> is configured to communicate or transmit a signal to the operator's phone which in turn then communicates or places a call to a third-party, such as an emergency services unit, other vehicles in the area, a contact within the user's phonebook, etc..

During the call or through an alert, information about the operator, vehicle <NUM>, and/or the location of vehicle <NUM> may be communicated so that others can go to vehicle <NUM> to assist with the accident situation. However, if an accident or roll-over is not an emergency, security option <NUM> on display <NUM> provides a "CANCEL" input for the operator to cancel the emergency call or alert. In one embodiment, a timer is provided that displays the time in which an emergency call or alert will be placed unless the operator cancels the call or alert by touching the "CANCEL" input. If an operator is injured and not able to cancel the call, the call or alert will proceed to provide assistance to the operator.

When at options screen <NUM> (<FIG> and <FIG>), the operator may select settings input <NUM> to change the settings for display <NUM> and/or other components of vehicle <NUM>. For example, as shown in <FIG>, the operator may change the default brightness or resolution of display <NUM> through a display option <NUM> (also see <FIG>). Additionally, when accessing settings input <NUM>, the operator may change notifications through a notifications option <NUM>, Bluetooth® or phone connectivity settings through a connectivity option <NUM>, power saving settings through a power savings option <NUM>, language settings through a language option <NUM>, and other settings for display <NUM> and/or vehicle <NUM>.

Referring to <FIG>, when at options screen <NUM> (<FIG> and <FIG>), the operator may select diagnostics input <NUM> to run a diagnostics scan of vehicle <NUM> via a diagnostic scan option <NUM> or access diagnostic or repair information about vehicle <NUM> via a diagnostic notifications option <NUM>. For example, as shown in <FIG>, diagnostics input <NUM> may provide trouble codes via a trouble/fault codes option <NUM> to the operator in the event of a needed repair to vehicle <NUM>. More particularly, notifications option <NUM> may provide a notification to the operator which is displayed on display <NUM> indicating a trouble or fault has occurred and identifying the fault by a code. When vehicle <NUM> has stopped moving, the operator may be able to look up the fault code through trouble/fault codes option <NUM> of diagnostics input <NUM> to understand the issue with vehicle <NUM>.

Alternatively, or in addition to, diagnostics input <NUM> may allow the operator to search for common repairs to display tools and procedures for repairing a specific component of vehicle <NUM> via a search option <NUM>. In one embodiment, search option 1098of diagnostics input <NUM> may allow the operator to type a specific keyword or access a menu of common repair procedures to fix a belt, change a tire, change the oil, add coolant, etc..

Referring to <FIG>, when at options screen <NUM> (<FIG> and <FIG>), the operator may select suspension settings input <NUM> to change the parameters of the suspension assemblies of vehicle <NUM>. For example, as shown in <FIG>, the vehicle may include an electronically-controlled front suspension and/or rear suspension. From suspension settings input <NUM>, the operator may able to change various parameters of the front and/or rear suspension of vehicle <NUM>, such as the spring tension to adjust the stiffness in the suspension, by accessing front suspension options <NUM> and/or rear suspension options <NUM>.

Additional details of the suspension assemblies may be disclosed in PCT Patent Application No. <CIT>, and entitled "VEHICLE HAVING SUSPENSION WITH CONTINUOUS DAMPING CONTROL" and PCT Patent Application No.<CIT>, and entitled "VEHICLE HAVING SUSPENSION WITH CONTINUOUS DAMPING CONTROL".

Referring to <FIG>, when at options screen <NUM> (<FIG> and <FIG>), the operator may select clutch settings input <NUM> to change the parameters of the clutch assembly (not shown) or other aspects of power system <NUM> of vehicle <NUM>. For example, as shown in <FIG>, the operator may able to switch between manual and automatic clutch controls via a manual clutching option <NUM> and an automatic clutching option <NUM>. Additionally, clutch settings input <NUM> may display information to the operator about the current clutch settings, such as a fluid level in a clutch master cylinder or parameters of a clutch linkage so that the operator can change such parameters when vehicle <NUM> is not operating, if desired.

Additional details of power system <NUM>, including the transmission, may be disclosed in PCT Patent No. <CIT>, entitled "PRIMARY CLUTCH ELECTRONIC CVT".

With respect to <FIG>, when at options screen <NUM> (<FIG> and <FIG>), the operator may select speed key input <NUM> to change the parameters of the speed key of vehicle <NUM>. For example, as shown in <FIG>, the operator may select the speeds at which vehicle <NUM> may operate for a given rider and the input required to change the speed key parameters (fob, speed limitations, security key, etc.) via a speed key input option <NUM>. In this way, the operator may control operation of vehicle <NUM> when another person is operating vehicle <NUM> based on the person's age, ability, and experience with vehicle <NUM>. For example, speed key input <NUM> may allow the operator to set or change the parameters for a Beginner Rider level via a beginner rider option <NUM>, an Intermediate Rider level via an intermediate rider option <NUM>, and an Advanced Rider level via an advanced rider option <NUM>.

Additionally, speed key input <NUM> may be accessed remotely via a signal or input sent over a wireless network or Bluetooth® to remotely control or change the parameters of the speed key of vehicle <NUM>. For example, speed key input <NUM> may be accessed by the manager of a fleet of vehicles <NUM> to allow for fleet management of vehicles <NUM> from any location at or away from vehicles <NUM>.

Additional details of the speed key of vehicle <NUM> may be disclosed in <CIT>, and entitled "SYSTEM FOR CONTROLLING VEHICLE PARAMETERS" (Attorney Docket No. PLR-<NUM>-<NUM>. 01P) and <CIT>, and entitled "SYSTEM FOR CONTROLLING VEHICLE PARAMETERS" (Attorney Docket No. PLR-<NUM>-<NUM>.

Referring to <FIG>, when at options screen <NUM> (<FIG> and <FIG>), the operator may select drive status input <NUM> to view the status of the driving conditions and/or the status of various components of vehicle <NUM>. For example, as shown in <FIG>, the operator may view details about the speed via a speed data option <NUM>, fuel usage via a fuel data option <NUM>, mileage via a mileage data option <NUM>, and coolant, oil, exhaust, or other temperature information via a temperature data option <NUM>. In one embodiment, each parameter selected by the operator may provide historical, current, and average data to the operator. Alternatively, an output similar to home screen <NUM> (<FIG>) may be provided to the operator such that the operator can view a plurality of parameters at once.

Claim 1:
A recreational vehicle (<NUM>) for operation by a driver and at least a first passenger, the driver having a driver portable communication device (<NUM>) and a driver audio interface device (<NUM>) having a microphone and a speaker, the first passenger having a first passenger portable communication device (<NUM>) and a first passenger audio interface device (<NUM>) having a microphone and a speaker, the recreational vehicle comprising:
a plurality of ground engaging members (<NUM>, <NUM>, <NUM>);
a frame (<NUM>) supported by the plurality of ground engaging members (<NUM>, <NUM>, <NUM>);
a prime mover (<NUM>) supported by the frame and operatively coupled to at least one of the plurality of ground engaging members to power movement of the recreational vehicle;
a steering system (<NUM>) supported by the frame and operatively coupled to at least a portion of the plurality of ground engaging members to move the portion of the plurality of ground engaging members relative to the frame, the steering system including a steering member adapted to be grasped by the operator of the recreational vehicle, the steering member being movable relative to the frame;
at least one controller (<NUM>) supported by the frame, the at least one controller (<NUM>) being adapted to be operatively coupled to the driver portable communication device (<NUM>), the driver audio interface device (<NUM>), the first passenger portable communication device (<NUM>), and the first passenger audio interface device (<NUM>), the at least one controller (<NUM>) being configured to communicate first audio information between the driver portable communication device (<NUM>) and the driver audio interface device (<NUM>) and to communicate second audio information between the first passenger portable communication device (<NUM>) and the first passenger audio interface device (<NUM>),
wherein the at least one controller (<NUM>) is adapted to be operatively wirelessly coupled to at least three of the driver portable communication device (<NUM>), the driver audio interface device (<NUM>), the first passenger portable communication device (<NUM>), and the first passenger audio interface device (<NUM>).