Recreational vehicle interactive telemetry, mapping, and trip planning system

IS 2 675 019 Τ3

DESCRIPTION

Recreational Vehicle Interactive Telemetry, Mapping and Route Planning System

Background and summary

Recreational vehicles, such as motorcycles, or off-road vehicles such as all-terrain vehicles (ATVs) and snowmobiles, are widely used for recreational purposes. These vehicles could be used both on roads and trails, or only on trails. The trails often pass through a combination of private and public property, which can stretch for hundreds of miles in many directions and through different areas. Such trails generally run through rural areas, but can connect to gas stations, restaurants, bars, maintenance sites, scenic areas, and other potential points of interest for outdoor adventurers.

Currently, clubs in areas where such trails exist maintain the trails on which such off-road vehicles are used. For example, a snowmobile club in a particular geographic area will maintain a relationship with the owners of the land through which the trails pass, and they will monitor and maintain trail conditions (for example, monitoring snow conditions and trails, maintaining signs, clearing obstacles, etc.). That club will generally also create a map that can be purchased by visitors to the area. The map will generally include points of interest in the area, and advertisements and coupons associated with the businesses that appear on the map. Those maps can be sold at gas stations, bars, restaurants, and online for use by pilots planning to visit the area. The cost of the map and the cost of the advertisements are used to fund the club's maintenance of the trail system in that area.

This arrangement is convenient for trail maintenance, but can be inconvenient for trail users. There are several reasons for this. For example, trail maps are generally organized by region, and riders may wish to travel between multiple regions whose maps are maintained by different clubs. Additionally, trail riders may wish to have coordinated POI maps that are not limited to the regions covered by a particular club, and limited to those businesses that choose to advertise with that club.

In relation to these difficulties, trail riders will often choose to purchase and download an electronic copy of the trail map, and plan their routes before beginning that journey. However, once the course is planned, the user will typically print the trail map for use on the RV for use.

Additionally, recreational vehicle use, as typically occurs in rural, off-road areas, can result in a driver being immobilized in a location remote from any other individual, and away from a maintenance facility for that vehicle. For example, in the case of a snowmobile, a user may have an equipment breakdown or other problem far from a repair shop, or even off a highway. In such cases, even if that pilot had a cell phone with him (and even if that pilot had service in the rural area where such a maintenance problem occurs) it can be difficult to diagnose problems with the RV.

Beyond these existing problems in the use of recreational vehicles and navigation, there is also no convenient way to coordinate route plans between pilots, despite the fact that it is common to do such trips in groups. Consequently, improvements in the driver experience, and in the integration of the vehicle with the driver experience, are desired.

Document US2004048598 describes a vehicle comprising an on-board communication system that sends and / or receives wireless signals from an external communication system.

As of 01/28/2013, the website http://www.trakmaps.com/L¡stGPSProducts.aspx?p=s offered for sale downloadable GPS trail maps for ATVs and snowmobiles.

Document WO2006110805 describes a vehicle navigation system including a vehicle-mounted data display and a portable global positioning system unit that can interact with the vehicle-mounted data display.

Document US2004220730 describes a navigation system for an off-road vehicle that helps the user to choose a suitable trail by displaying various possible trails on a map.

In an illustrated example of the present disclosure, an interactive system for use in connection with the use of recreational vehicles includes a server system. The server system includes an off-road trail database containing trail data, trail condition information, and POI information, as well as a trail mapping system accessible by any of a plurality of pilots,

ES 2 675 019 T3 allowing the trip mapping system for a pilot to create a planned route based on the off-road trip database data and navigate the planned route. The server system further includes a trail maintenance interface accessible by users affiliated with an authorized group to edit at least a portion of the trail data, trail condition information, and point of interest information associated with the authorized group. The server system includes a location data management system configured to receive location data, the location data management system allowing a pilot to publish his or her location information to one or more other pilots within the mapping system. The server system further includes a user feedback interface configured to receive data from the pilots' journey for publication to one or more other pilots using the interactive system, the journey data including information describing an actual route and user data. associated with the actual path.

In another illustrated example of the present description, a method of facilitating the use of a recreational vehicle includes receiving, from users affiliated with a plurality of authorized groups, trail data, trail condition information, and information on points of interest from areas affiliated with authorized groups, respectively. The procedure further includes receiving a request from a user device to define a planned off-road route in one or more of the areas, and generating a map associated with the planned off-road route, the map including the condition information of the trail and POI information received. The method also includes receiving location information from a communications device at a location of a recreational vehicle driven by the user during the trip along the planned off-road route, and publishing the location information for one or more others. users based on the permissions set by the user. The procedure includes receiving user feedback information associated with the planned off-road route from the user.

In yet another illustrated example of the present disclosure, an application embedded in a computer-readable medium is described that is executable on a computing device and includes program instructions that, when executed, are configured to cause the computing device to receive input. requesting an off-road route, including user input one or more ride parameters. The computing device is also configured to define an off-road route based at least in part on the one or more driving parameters and trail condition data received from one or more third sources, and present the off-road route to the user at through a cartographic display, including presenting a plurality of route variations to the user, including route variations the display of one or more driving parameters of the route variations compared to the off-road route. The computing device is further configured to receive user selection of a desired off-road route for the ride.

In yet another illustrated example of the present disclosure, a computer-readable medium is described comprising computer-executable instructions that, when executed, carry out a procedure to integrate the experience of the pilot with the performance of the recreational vehicle. The method includes receiving from a user a selection of a planned route for a recreational vehicle on a computing device associated with the recreational vehicle, and receiving on the computing device, through a communication interface connected to a control unit of a vehicle recreational vehicle, data regarding the operation of the recreational vehicle. The method further includes displaying a user interface to a user, the user interface including information associated with the planned route and at least a portion of the data regarding the operation of the recreational vehicle, and communicating the data to a remote system from the device. computer, and at least part of the data regarding the operation of the recreational vehicle. The method also includes receiving from the remote system one or more instructions to display to the user regarding maintenance or repair tasks to be carried out on the recreational vehicle.

In an illustrated embodiment of the present disclosure, an indicating instrument is mounted on a recreational vehicle. The indicating instrument includes a large color display. The indicating instrument is coupled to an on-board vehicle computer such as an engine control unit, to a remote computer network through a mobile device, and to accessory elements. The vehicle indicating instrument provides interactive vehicle information, telemetry, mapping, and route planning to a vehicle operator.

In another illustrated example of the present disclosure, a method of facilitating the use of an off-road vehicle comprises providing a vehicle indicating instrument having a display, a processor, at least one user input, and a communication link. ; receiving through the communication link trail information from a remote computing device related to a selected off-road trail for travel by the off-road vehicle; and displaying a user interface on the display of the indicating instrument. The user interface includes information associated with trail information including a trail map for the selected off-road trail and trail conditions on the selected off-road trail.

In the illustrated embodiment of the present description, an indication instrument for an off-road vehicle comprises at least one processor; a memory accessible by the at least one processor; a

ES 2 675 019 T3 display coupled to the processor; a Wireless data link coupled to the processor to provide communication between the indicating Instrument and a portable mobile device such that the indicating Instrument transmits information to the portable mobile device and receives information from the portable mobile device; and software stored in memory and configured for execution by the at least one processor. The software comprises instructions that provide a user selectable menu to receive user input to selectively display vehicle operating information on the indicating instrument display including vehicle speed, RPM, fuel level, coolant temperature; receiving user input to selectively display information from a mobile device on the display of the indicating instrument including phone call information, text message information, and cellular signal strength; and receiving a user input to selectively display trail information on the display of the indicating instrument. The trail information includes a trail map for a selected off-road trail and information related to trail conditions on the selected off-road trail.

In another illustrated embodiment, the software further comprises instructions that provide a user-selectable menu for receiving user input to selectively display off-road vehicle-related service information on the display of the indicating instrument. The service information includes a service interval and a number of hours remaining until service is required.

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 aspects that exemplify the best mode of carrying out the invention as currently perceived.

Brief description of the drawings

Fig. 1 illustrates an interactive system for use in connection with the use of an recreational vehicle, according to an example of the present disclosure;

FIG. 2 illustrates an example server and database usable in the interactive system of FIG. 1;

Fig. 3 illustrates an example application usable on a mobile device and integrable with the interactive system of Fig. 1;

Fig. 4 illustrates an example arrangement for integrating a recreational vehicle into an interactive system as illustrated in Fig. 1;

Fig. 5 illustrates an alternative arrangement for integrating a recreational vehicle into an interactive system as illustrated in Fig. 1;

Fig. 6 illustrates an example data stream for managing usable trail data within the interactive system of Fig. 1;

Fig. 7 illustrates an example user interface used to manage trail data by an RV rider or user;

Fig. 8 illustrates an example user interface used to plan a route by a recreational vehicle user or pilot;

FIG. 9 illustrates an example user interface used to view route data by a recreational vehicle user or pilot;

FIG. 10 illustrates an example user interface used to view points of interest along a planned route by a recreational vehicle user or pilot;

FIG. 11 illustrates an example user interface for following a route by a recreational vehicle user or pilot;

Fig. 12 illustrates a second example user interface used to follow a route by a recreational vehicle user or pilot;

FIG. 13 illustrates an example user interface used to create a new route by a recreational vehicle user or pilot;

Fig. 14 illustrates an example user interface used to display hazards along a route to a recreational vehicle user or pilot;

FIG. 15 illustrates a second example user interface used to display hazards along a route to a recreational vehicle user or pilot;

FIG. 16 illustrates an example user interface used to display locations of other selected individuals along a route to a recreational vehicle user or pilot;

FIG. 17 illustrates an example user interface used to display details regarding a selected individual to a recreational vehicle user or pilot;

Fig. 18 illustrates an example user interface used to display weather data along a trail to an RV user or pilot;

FIG. 19 illustrates an example user interface used to display trail details to an RV rider or user;

FIG. 20 illustrates an example user interface used to integrate social media features within a trail driving system for use by an RV rider or user; FIG. 21 illustrates an example user interface used to display recreational vehicle speed data to a recreational vehicle user or pilot;

ES 2 675 019 T3 Fig. 22 illustrates an example user interface used to display RV fuel utilization to an RV user or driver;

Fig. 23 illustrates a flow chart of a method for facilitating the use of a recreational vehicle, according to one example;

Fig. 24 illustrates a flow chart of a method for integrating pilot experience with recreational vehicle performance, in accordance with one example.

FIG. 25 is a block diagram illustrating components of a multi-function indicating instrument having a full-color display screen that interacts with a mobile device and other vehicle components;

Fig. 26 is a block diagram illustrating vehicle sensors coupled to an electronic control unit (ECU) and vehicle components controlled by the ECU through the indicating instrument or device. mobile;

Figs. 27 and 28 illustrate additional details of a multi-function indicating instrument of an embodiment of the present disclosure;

Figs. 29 and 30 illustrate display screens and control buttons of the indicating instrument of Figs. 27 and 28;

Figs. 31-34 illustrate the position of the multi-function indicating instrument and display screen located inside utility vehicles, off-road vehicles, and snowmobiles;

Fig. 35 illustrates a display screen on the indicating instrument along with indicators showing items displayed on the display of the indicating instrument;

Figs. 36A and 36B illustrate menus displayed on the display screen of an indicating instrument;

Figs. 37-42 illustrate a plurality of different formats for displaying vehicle operating data on the display screen of an indicating instrument;

Figs. 43-45 illustrate display screens related to service reminders for the vehicle;

Figs. 46-49 illustrate indicating instrument display screens with fault detection indicators;

Fig. 50 illustrates dynamic indication bars displayed on the display screen of an indicating instrument;

Figs. 51-58 are exemplary display screens shown on the indicating instrument related to wireless connectivity and telephone functions;

Fig. 59 is a menu for selecting off-road tracks or trails, managing waypoints, and checking the status of the satellites displayed on the display screen of an indicating instrument; Fig. 60 is a menu for selecting fuel type, locking the indicating instrument and changing a security code of the indicating instrument;

Figs. 61-69 illustrate exemplary display screens displayed on the indicating instrument related to cartographic features and functions;

Fig. 70 is a satellite status screen shown on the display screen of an indicating instrument;

Figs. 71A and 71B illustrate a control button for navigating through menus or functions displayed on the indicating instrument and / or mobile device; and Figs. 72 and 73 are logic diagrams related to the rocker switch controller of Figs. 71A and 71B showing logic for navigating through the various menus.

Detailed description of the drawings

Various examples of the present invention will be described in detail with reference to the drawings, in which like reference numerals represent like parts and assemblies throughout the various views. Reference to various examples does not limit the scope of the invention, which is limited only by the scope of the claims appended hereto.

The logical operations of the various examples of the description described herein are implemented as: (1) a sequence of computer-implemented steps, operations, or procedures that are executed on a programmable circuit within a computer, and / or ( 2) a sequence of computer-implemented steps, operations, or procedures that are executed on a programmable circuit within a directory system, a database, or a compiler.

As briefly described above, embodiments of the present invention are directed to systems and methods that provide an interactive, guided user experience for use in off-road or recreational vehicle use. This may include, for example, use in connection with a motorcycle, off-road vehicle, snowmobile, or other types of recreational vehicle, and involves the aggregation of user comments regarding trail information and waypoint data. interest, club information regarding trail conditions, and vehicle, hazard and weather data to enrich the rider experience. Providing users with shared information regarding trail conditions, length, difficulty, weather conditions, and data on points of interest, while also showing a pilot various data regarding their vehicle on a display along with data weather conditions and hazards and locations of other riders along a particular trail, the

ES 2 675 019 T3 experience of that user, ensuring that the user is connected to the people, places and experiences of the vehicle that will encourage the user to continue using recreational vehicles.

Referring now to Fig. 1, an interactive system 100 is shown for use in connection with the use of an recreational vehicle, in accordance with an example of the present disclosure. Interactive system 100 includes a server system, shown as RV portal server 102, that houses a trail and driver database 104. The RV portal server 102, referred to herein as the server 102, generally corresponds to one or more computer systems configured to store and process data associated with one or more RV drivers, as well as data associated with trails. interest to those pilots. Such data may be located in the trail and pilot database 104, or it may be received from any of a plurality of data providers, such as data providers 106a-e, discussed below.

In the example shown, server 102 is accessible by any of a plurality of recreational vehicle users 108, which may include off-road vehicles, such as ATVs or snowmobiles, and may also include other types of recreational vehicles such like motorcycles. It is observed that, although in the example illustrated in Fig. 1 only snowmobiles are shown, it is understood that other types of recreational vehicles could also be used, based on various aspects of the present disclosure.

Server 102 is also accessible through a plurality of other computing devices, such as a mobile device 110 (eg, a mobile phone or tablet device) and / or a computing device 112 that has a web browser installed on the server. same. However, for some users of the server 102, a computing device 112 and associated web browser may be required to enable some functionality, while, in other examples, an application installed on a mobile device 110 may be required. For example, as discussed in connection with some user interface examples discussed below, location-based services where a user's location is posted, and where loyalty and location-based social networking services are provided , may require the use of a mobile device 110, while some features, such as the entry of maintenance data and / or trail conditions may require entry through a specific web interface by private individuals (eg, authorized members of a club responsible for trail maintenance). In the example shown, a first and a second computing device 112a-b are shown, representing a user acting as a pilot (computing device 112a) and a second computing device associated with a member of a trail management club ( computing device 112b), respectively.

In the example shown, a plurality of third-party data services are integrated with the information supplied to users of devices 110, 112a-b. The data services, provided by the data providers 106a-e, allow the integration of a variety of data types into a user interface coordinated by the server 102. In the example shown, data providers 106a-e include a mapping data provider 106a, a meteorological data provider 106b, a GIS data provider 106c, an advertising data provider 106d, and a trail condition data provider. 106e.

The mapping data provider 106a supplies mapping services to the server 102, whereby various data overlay services may be provided including trail or route data, trail or route plans, GIS data, or other types of information such as is discussed in this document. In some cases, the meteorological data provider 106b may provide meteorological data such as forecast data, or it could alternatively (or in addition) provide current weather or radar data for overlay on the cartographic data received from the cartographic data provider 106a, for delivery to a user who is a pilot of a recreational vehicle 108, for example to allow the pilot to view the forecast or current inclement weather conditions. The GIS data provider 106c also provides overlay information that allows the definition of topography, property locations, city / town locations, trails, roads, and other information.

In some examples, the advertising data provider 106d serves advertisements to users who are pilots. The advertising systems of the present disclosure can take various forms. For example, in some cases, when a particular route is being displayed, the user may be shown advertisements that correspond to businesses located along that route. In such cases, advertising is managed by server 102, or specific advertising businesses are selected by one or more trail riding clubs managing a particular area of ​​a trail system. Consequently, and as discussed in more detail below, advertising proceeds can be allocated to the area's trail driving club based on the advertising display frequency, or other metric. As such, trail riding clubs may continue to receive revenue from currently received advertising based on the placement of advertisements on printed trail maps associated with the area maintained by the trail riding club.

In the example shown, trail condition data provider 106e provides trail condition data to server 102. This trail condition data illustratively includes data reported from trail riding clubs or users, but typically corresponds to data from

ES 2 675 019 T3 third-party trail conditions, such as those that may be monitored by a government organization (eg, the department of natural resources for the state in which the trail is located), or other regional groups.

In an illustrated example, other data providers are also integrated with such a system. For example, in the case where social media services are provided for pilots using the services provided by the system 100, such services are either integrated into the server 102 or provided by an additional data provider 106.

In addition to data providers and third party contributors, a dealership 114 may be illustratively provided access to server 102, for example, to manage, store, and access vehicle maintenance records associated with particular vehicles. In such examples, dealer 114 stores such records locally, and receives maintenance and / or repair information for a vehicle 108 from server 102, or alternatively stores all such maintenance and repair information in database 104, associated with the server 102.

As illustrated in FIG. 1, the various data providers 106e are communicatively interconnected with the server 102 through a network 116, such as the Internet. Furthermore, such a network is used by users of mobile device 110 or computing devices 112a-b, as well as dealers 114 for communicative interconnection to server 102.

Referring now to Fig. 2, additional details are shown regarding the server 102 and the trail and pilot database 104 of Fig. 1. The server 102 generally provides a plurality of interfaces and services by which to aggregate and provide data to users who are RV drivers. As discussed further in this document, the interfaces and services provided to those users include journey planning, navigation, social media and trail feedback, and vehicle repair and maintenance services, among others.

In the example shown, the server 102 includes a mobile application interface 202 and a web interface 204 that provide user access to various mapping, planning, and trail data services. Web interface 202 allows a user to connect to server 102 through computing device 112, and register their recreational vehicle with server 102. Mobile application interface 202 provides analogous functionality through a downloadable application stored on a smartphone or tablet device, such as mobile device 110. In addition, through web interface 204 or mobile application interface 202 , the user plans a route that the user intends to take in his recreational vehicle, and the server 102, based on the trail condition data, confirms that the selected route is passable. The web interface also allows users to select their skill level, and presents various possible available routes based on the user-defined vehicle type (snowmobile, off-road vehicle, motorcycle, etc.) and the associated skill levels for those routes. For example, a beginning motorcyclist is shown routes that are limited to non-technical street routes, whereas a snowmobile rider is only routed on trails, since snowmobiles are not normally driven on roads. The displayed route includes, for example, a distance and the expected time to travel the route based on the skill level of the user. Other data is also provided, such as the fuel required along the route, or the display of nearby alternative routes. Various other path selection features are also possible, as discussed further below.

In addition to the route selection features, the mobile application interface 202 and the web interface 204 each allow the user to "preview" the course being selected, for example, by providing a "flyover" view from the perspective of the driver. user or simulation of a selected route, based on photos or videos of the trail collected in database 104. In addition, a user feedback interface available in the mobile application interface 202 and the web interface allows a user to indicate that they have taken a particular route, and allows that user to enter a review of their experience taking that route. This information is used by subsequent pilots, during route planning, as it can be made visible in association with the route planning features discussed above.

Mobile application interface 202 and web interface 204 also allow the locations of one or more other individuals along a trail to be tracked, for example, to track where fellow riders are along a trail, or to monitor the progress of friends or family who are taking a walk on a trail. Additional details regarding the features presented by the mobile application interface 202 are discussed below in connection with Fig. 3, and examples of user displays generated by such interfaces are discussed in greater detail below in connection with Figs. 7-22.

In addition to the web and mobile application interfaces 202-204, in the example shown the server 102 includes a plurality of data interfaces. These data interfaces may include, for example, a third party data provider interface 206, which receives and manages data associated with data providers 106a-e, as well as a club portal interface 208. The club portal interface 208 is configured to manage communication with

ES 2 675 019 T3 members of regional trail riding clubs. These trail riding clubs generally maintain and monitor the condition of the trails in a particular geographic area. Members of the trail riding club can therefore use portal interface 208 to update trail routes, trail conditions, provide advice to trail riders (for example, instructions to avoid straying trails through private land, tips for scenic locations or routes, etc.), and notes on local regulations. An ad manager component 210 coordinates with the club portal to communicate with an ad provider 106a, to control the types of ads provided to users of the mobile or web interfaces 202, 204, thus limiting the ads shown to a user to those approved by the club, or those from the same geographic area as the club. As discussed further below in connection with Fig. 6, the ad manager also manages revenue sharing through trail driving clubs and other entities, to provide incentives to contribute to the global system 100.

In addition, a dealer interface 212 may be included, which associates one or more of the pilots using the services of the server 102 with a particular dealer. The dealer interface 212 is used to communicate error codes or diagnostic data received from one or more recreational vehicles 108, for example, to receive in response repair instructions or maintenance advice from the associated dealer (s). (s) with those vehicles. Accordingly, RV drivers are assured of vehicle repair assistance during trail rides, while dealers are notified of potential repairs, allowing the dealership to provide additional value to customers using such vehicles that support communication of diagnostic data through server 102.

The database 104 stores various types of data used by the server 102, including the various interfaces 202-210, to generate, together with the data providers 106a-e, services to be presented to users who are vehicle pilots. recreational. In the example shown, the database 104 includes data from trail 220 used for route planning purposes, which may include routes, property details, and trail condition data such as can be received from a club member or a third party data provider. The database 104 may also include photos of trails 222, either submitted by pilots who have previously traveled along the trails, or from a trail photographic capture system usable to generate a sequential "flyover" photographic replay. ”Which simulates the route along the path. Database 104 also includes user comments 224, which may include trail reviews as well as trail ratings (e.g., difficulty, time required to walk, etc.) as well as notes regarding points of interest, or Other features.

In the example shown, database 104 includes pilot location data 226, which can be received from a mobile device hosting a companion application through mobile interface 202, or directly from a GPS-equipped recreational vehicle. Pilot location data 226 is used to provide turn-by-turn navigation along road and off-highway routes, and is also selectively published for other pilots, for example, other pilots in a group of pilots who wish to track the progress of each along a path. In addition, 228 POI data is received from users or club members, and includes specific scenic locations or businesses along the trails. POI data is displayed to users. For example, the data is overlaid on a map display as illustrated below.

In some examples, the database 104 includes vehicle maintenance data 230 and vehicle repair data 232. The vehicle maintenance data 230 includes information associated with general vehicle maintenance tips that are provided to the user, as well as records. specific maintenance associated with the user's recreational vehicle. Vehicle repair data 232 includes instructions to respond to various breakdowns that may occur in such vehicles, for example, including instructions to physically repair vehicles, or to respond to error codes received at server 102 that are generated by a drive. electronic control system of a recreational vehicle, as discussed further below in connection with Figs. 4-5. This maintenance and repair data is provided, for example, by the user through the mobile application or web interfaces 202, 204, or from a dealer 114 as illustrated in Fig. 1.

In operation, the server 102 uses the data stored in the database 104 for a variety of applications that are provided to a user through the web or mobile application interfaces 204, 202, respectively. Consequently, in Fig. 3, an example of a mobile application 300 is illustrated, depicting functionality that is made available to the user of a mobile device (eg, device 110) that is communicatively connected to server 102.

In the example shown, the mobile application 300 resides in a memory 302 of a mobile device 110, which typically includes a programmable circuit, a display, a camera, and a global positioning system (GPS) antenna. system). Generally, mobile application 300 is configured to interact with mobile application interface 202 of FIG. 2, on server 102. Through this communicative connection, the mobile application 300 provides a number of services to a user who is a

ES 2 675 019 T3 pilot of a recreational vehicle. In particular, the mobile application includes, in the example shown, a route planner component 304, a companion tracker component 306, a route flyover component 308, and a points of interest component 310. The mobile application 300 also includes , for use on the go, a turn-by-turn navigation component 312 and a vehicle interface 314.

The route planner component 304 provides a mechanism by which a user selects and plans one or more routes for which to take his or her recreational vehicle for a ride. The route planner component 304 includes a rule engine that functions to automatically plan a "best" route for a user given a set of parameters. For example, the route planner component 304 determines a distance, a duration, a level of difficulty, and an expected fuel consumption of a particular ride, based, for example, on the map and GIS data received by the data providers. The route planner 304 includes selectable options that allow a user to either select a particular destination (in which case the best route between a starting point and that destination is provided) or to route a user on a circuit of a predetermined duration, based on the skill of the user and the starting location. In some examples, the route planner component 304 is configured to search and / or present to a user a set of routes from which that user can select a desired route, the routes varying in duration and / or difficulty. In such examples, the user instructs the route planner component 304 to select only "safe" or "demanding" rides to display to the user, and is configured according to the skill level of the pilot.

In some examples, the route planner component 304 further includes a ride finder, which locates routes previously taken from that user / pilot or other pilots. In such examples, the route planner component 304 causes the display of trails and / or destinations that are recommended by other pilots, and includes, for example, text describing the ride or trail, images, and featured videos provided by other pilots. for viewing by the user of the application 300, to allow that user to select a walk or trail recommended by others. Additionally, the route planner component 304 allows users to save and share their own historical routes, as well as upload images, videos, and descriptions of those routes to the server.

In some examples, the route planner component 304 also explains, when helping to plan a route, whether that route will cross some private terrain. In some examples, the route planner component 304, when determining a route to be displayed to a user, is configured (eg, at a user's option) to only display routes that avoid crossing private terrain.

The buddy tracker component 306 allows a user to publish their location so that it can be seen by others during a journey, and also allows the user to view the locations of others in a cartographic interface, for example, as illustrated in Fig. 16, discussed later. In some examples, the buddy tracker component 306 coordinates with the route planner to determine if the pilot, during the course of a ride, is on a collision course with another pilot, and can alert that pilot accordingly. For example, a second pilot may be ahead of the pilot who has the application running, but that second pilot may have stopped, to rest, or due to equipment failure. The pilot, if traveling at a high speed, may not have adequate time to see that second pilot stopped on a trail before he has to stop.

In addition, the route flyover component 308 allows the playback and pause of a traveled route, as well as the management of a virtual "flyover" or simulation of a route. This "flyover" corresponds to a projected 360-degree view of a route, based on images captured along a route. In some cases, trail photos 222 stored in database 104 include a set of photos or videos used for such a "flyover" feature.

Points of interest component 310 is configured to display one or more points of interest associated with a selected route. In some such examples, the POI component 310 includes a feature where the POI component associates specific POIs with a particular trail driving club along which those POIs are located. In such examples, the POI information displayed is limited to the specific POIs provided by that trail riding club, or in the area managed by the trail riding club.

The turn-by-turn navigation component 312 provides, once a user has selected a particular route, turn-by-turn directions to follow that route, analogous to those turn-by-turn directions available through current road-based navigation systems, but managed based on GIS and trail data received from a plurality of data sources and providers.

Vehicle interface 314 also provides additional functionality during a ride, and receives data from a vehicle that indicates a current or historical operating status of the vehicle. For example, in some examples, the vehicle interface 314 receives data from an electronic control unit of a vehicle, and is configured to display such information on a display of a mobile device (for example, in the case of fuel consumption, speed, throttle position, or other similar operating parameters), or communicates such data, such as error codes and other problems, to a server for retransmission to a dealer or

ES 2 675 019 T3 a mechanic. In those cases, the dealer or mechanic contacts the user of the application 300, for example, to provide information regarding how to troubleshoot the recreational vehicle.

The audible interface 316 can be used in a variety of contexts, and simplifies the operation of the mobile application by presenting the user with audible updates regarding the route, turn-by-turn directions, partner locations along the trail, or points of interest that they are approaching. This allows the user to keep their eyes on the trail while traveling.

In addition to the above, the mobile application also includes a user feedback component 318. The user feedback component 318 is used during or after a ride, for example, to provide information from that user regarding perceived difficulty, length, or comments regarding points of interest found during the tour. In some examples, the user comments component 318 includes a social media aspect in which the user “logs in” or comments on businesses that are located along a trail, and provides advice to other pilots regarding to those points of interest.

In accordance with the various components and interfaces of Fig. 3, it is seen that the mobile application is configured to generate a plurality of user interfaces, examples of which illustrate the functionality described above being shown in Figs. 7-22, described later. In addition, while the functionality of the mobile application 300 is discussed in terms of a mobile device system, it is recognized that most of the same functionality, if not all, is provided through a web interface accessible through a web browser. a desktop or laptop computer system. In some cases, when using mobile device functionalities such as GPS or camera features, the corresponding features of the mobile application 300 may not be available through a browser-based version of the application.

Referring now to Figs. 4-5, example examples of systems that integrate communication from a recreational vehicle to server 102 are shown. In general, the examples illustrated herein communicate with server 102, or directly as illustrated in Fig. 1 or are coordinated through the vehicle interface 314 of the mobile application 300, to provide that user with information "on the trail".

In the embodiment shown in Fig. 4, a first embodiment of communication integration of a recreational vehicle 108 is shown within the system 100 of Fig. 1. In the embodiment shown, the recreational vehicle 108 has an electronic control unit (ECU) 402, which is communicatively connected, as is known, to various subsystems of the vehicle, such as an engine 404, user inputs 406 (e.g. , throttle, braking information, or other input information), as well as data from sensors 408 (eg, ambient and exhaust temperatures, fuel levels, component sensors, etc.). The eCu 402 is typically communicatively connected to a Controller Area Network (CAN) interface 410, which exposes various operating parameters of the vehicle 108. In the embodiment shown in Fig. 4, an integrated controller 412 is communicatively connected to an indicating or display instrument 414 and a communication interface 416, which is, for example, a cellular or satellite communication interface, communicatively connectable to server 102. Controller 412 illustratively includes programmable circuitry and memory, and as such cooperates with display 414 to provide much of the functionality discussed above with respect to mobile application 300. In addition, various other components, such as a GPS or an interface. audible, are also included in the overall RV system, to provide additional functionality that is natively desired within the RV. Additional details of this embodiment are described below with reference to Fig. 25.

Unlike Fig. 4, in Fig. 5 a mobile device 110 is used, with integration into the CAN 410 interface. This is achieved, for example, by connecting an electronic key 420 or another wired connection to wireless or direct wired between ECU 402 and mobile device 110. In some embodiments, dongle 420 implements a Bluetooth, radio frequency (RF) standard, or some other short-range wireless standard for wireless communication between the ECU and a communication interface 450 of mobile device 110. In such an arrangement, the mobile device 110 includes a controller 452 that receives data from the ECU 402, and integrates a display 454 and various peripheral devices 456 (eg, GPS, camera, etc.), for integration of vehicle operating data. with data received in the mobile device, according to the functionality previously discussed in relation to Fig. 3.

It is noted that, through the CAN interface 410, a variety of types of information are provided for display in the vehicle, or for communication to the server 102. In various embodiments, vehicle data received from ECU 402 includes, for example: engine revolutions per minute; vehicle speed; coolant temperature; battery voltage; fuel level; throttle position; pedal position; fuel consumption index; vehicle range; engine load; barometric pressure; air intake temperature; exhaust air temperature; gear indication; spark timing; operating hours; driving status; and trouble codes. Other types of information are received through the CAN 410 interface, depending on the particular type of vehicle and the characteristics included in it. Examples of display information that integrates route and vehicle information are illustrated in the user interfaces of Figs. 21-22.

ES 2 675 019 T3

Referring now to Fig. 6, an example data management arrangement 600 is shown that is usable in connection with the system 100 of Fig. 1, and illustrates how various types of incoming data are received and managed. from users of various types (eg drivers, trail riding club members, advertisers, etc.), and also how the revenue they bring is managed and distributed by those entities. In the example shown, clubs 602, which generally include trail maintenance organizations that typically receive revenue from trail map ads, are validated as recognized organizers (step 604). The validated clubs and associate members can then provide trail data, including new and / or updated trail data, which will be stored in database 102 (step 606). That trail data is validated (step 608), the validated trail data is then combined with trail data managed by a larger trail data aggregator, such as trail maps maintained by USTRAILS.org or some other organization. analogous (step 610), before storing data from trail 220 in database 102. For example, aggregated trail data includes trails generally entirely on public land, while club-maintained trails may include trails on private land where a club has negotiated a right-of-way or route of way with the land owner.

In addition to receiving trail data from the club and third parties, users provide information regarding trails (stage 612), either in addition to the club trail data (for example, by providing club-provided trail reviews, or by directly providing additional comments regarding public trails. Information regarding club-sponsored trails includes, for example, information on trail conditions, review information regarding quality, difficulty, or other information regarding trails (stage 614).

To aid trail data aggregation, a revenue model is incorporated within the overall data management on the server, and is included, for example, as part of the ad manager component 210 of the server 102. In the example shown, the revenue model includes revenue generation 620 from various sources, such as original equipment manufacturers (OEMs) 652 that want to integrate into such a system, as well as revenue from 300 mobile app downloads (shown as 652 app revenue), and 654 ad revenue. In the arrangement shown, trail driving clubs and other trail aggregators are compensated for this revenue, either directly by advertisers or as subsidized by OEMs or app downloads directly.

Furthermore, it is observed that a mobile application 300 is downloadable by various individuals, such as a vehicle owner 660, a pilot 662, or a third party owner of vehicle 654, representing an owner of a recreational vehicle that is not supported by the system. global 100, for example, because it is manufactured by a non-participating OEM. It is noted that some features and functionality discussed above, which are typically provided to users of a mobile application, may not be available to users of a mobile application in connection with a recreational vehicle manufactured by a non-participating OEM. For example, the integration of vehicle data and application data, as used to display vehicle data within application 300, or to send error codes to server 102 for assistance with repair and maintenance in the trail is not provided in such cases. However, in such a case, the app is used by these individuals 660-664 to provide trail reviews, as well as up-to-date condition information (stage 666), which is integrated with club or third party information, as discussed above. in connection with steps 612-614.

Referring now to Figs. 7-22, various example user interfaces of a mobile application 300 are illustrated, showing some example operations that are provided by the system 100 of Fig. 1, as reflected on a display. of a mobile device 110, before, during, and after a ride by means of an recreational vehicle. As discussed above, the various features and functionalities illustrated in Figs. 7-22 can, at least in part, be made, through a web interface, available to a user of a computing device and associated web browser, or through a display integrated into a recreational vehicle (as illustrated in Fig. Fig. 4). In an embodiment shown in Fig. 25, the features of Figs. 722 are displayed on an indicating instrument display 414 located inside the vehicle.

Referring first to FIG. 7, an example user interface 700 used to manage trail data by a recreational vehicle user or pilot is shown. User interface 700 represents a general menu interface that allows a user to use a route tracing component of the web or mobile application to view or plan various routes. In the example shown, user interface 700 includes a route trace option 702, a route planning option 704, and a route import option 706.

Route tracking option 702 allows a user to select from a plurality of previously saved routes, or to create a new route using a mapping and address creation feature. Route planning option 704 allows the same user to view a set of shared predefined routes, and view points of interest, levels of difficulty, and other types of information associated with that route. A choice of

ES 2 675 019 T3 route import 706 allows the user to import data, such as that which can be included in a route description file (for example, a flat file or a markup language file that defines route coordinates). will be used as a route to be traversed.

In the example shown in Figure 7, several additional mapping options are also displayed on the user interface 700. A route option 708 allows the display of alternative routes between a start point and an end point, and a route point option 710 allows a user to define one or more route points along a selected trail that are used as rest locations, or define the desired trail for the automatic mapping features of the system. An event option 712 allows a user to define specific rest times, locations and times, or specific events along a trail that may be of interest. An information option 714 allows the user to provide descriptive information about the path to be traveled, for example, to provide that path to others who will be ahead on the path.

In addition, general options that allow user navigation within application 300 are also included in the illustrated user interface. These include general information that may be of interest to the user, such as the weather conditions option 720, a dealer option 722, a service option 724, and a route option 726. Additional option types include, for example, a hidden menu that can be reached via a "more" option (displayed as 728 ellipses). Weather option 720 displays a screen of weather conditions, for example, the weather conditions in an area near a selected route, as illustrated in Fig. 18. The dealership option 722 allows a user to view nearby dealerships or that particular individual's dealership, for example, to allow that individual to contact the dealership while on the trail. In one embodiment, a parts check option allows the user to check the availability of a certain repair part or accessory at an identified dealership on the trail route. The services option allows the user to view additional services available to the user, for example, regarding maintenance or repair services.

FIG. 8 illustrates an example user interface 800 that is used to plan a route by the recreational vehicle user or pilot. The user interface 800 includes saved routes 802 of the pilot, as well as routes marked as favorites 804 of other pilots, and nearby routes 806 that have been published by other pilots. A list of 808 routes shows the available routes, and a new route option 810 allows the user to initiate an auto-mapping process whereby the user defines a new route between points, or point-to-point, using route points defined by the option. of waypoints discussed earlier in figure 7.

FIG. 9 illustrates an example user interface 900 that is used to view route data by a recreational vehicle user or pilot, for example, once a particular route has been selected. In the example shown, a route use option 902 illustrates a frequency of use of that route, and an edit route option allows the user to change the route based on their preferences. Interface 900 also includes a route map 906 (shown schematically), and route contours 908 that illustrate the elevation and distance of a particular route.

FIG. 10 illustrates an example user interface 1000 that is used to view points of interest along a planned route by a recreational vehicle user or pilot. Interface 1000 includes a start point and an end point 1002a-b of a route 1003, as well as marked points of interest 1004 along route 1003, in a map display interface 1006. Points of interest 1004 illustratively include views Pictures, businesses, or other information. An information panel 1008 provides information regarding the route in general; Upon selection of one or more of the POIs, panel 1008 displays additional details regarding that POI, or reviews from other users.

Figs. 11-12 illustrate an example user interface 1100 used to trace a route by a recreational vehicle user or pilot. The route tracing user interface provides a replay of a route traveled by a user, for example, to allow that user to revisit their route after the completion of the route. Additional details of storing and replaying the route are discussed later. The track trace interface 1100 displays the map display interface 1006, but includes location information as well as a play / pause option 1102. The route tracking interface 1100 includes an information bar 1104 that illustrates the distance traveled, the time traveled, and optionally includes a variety of other types of information, such as fuel consumed, speed at each location (if data is available from the vehicle) or other information associated with the ride. As seen in Fig. 12, a route management option 1106 allows a user to save or delete the route that was traveled.

FIG. 13 illustrates an example user interface 1300 used to create a new route by a recreational vehicle user or pilot, as well as illustrate historical information regarding the routes. The user interface includes an add new path option 1302 that initiates the route planning features described above. User interface 1300 also includes a history 1304 of recorded tracks, which is selected for tracking and playback as illustrated in user interface 1100 of Figs. 11-12. Also I know

ES 2 675 019 T3 display cumulative statistics 1306, showing, for example, the total miles logged by the pilot, as well as typical ride times, distances, and other historical information.

Figs. 14-15 illustrate a further example user interface 1400 that is used to display hazards along a route to a recreational vehicle user or pilot. User interface 1400 generally illustrates a map area 1402, as discussed above in connection with route planner and POI data, but in this view, one or more hazards 1404 are displayed along a selected route. Example hazards are marked, such as reported accidents, downed trees, closed roads, or other dangerous conditions such as trail snow preparation equipment. Following the selection of hazard 1404, additional details regarding the type and duration of the hazard are displayed, as seen in Fig. 15. Additionally, an alternate route option 1406 allows a user to have an alternate route generated to avoid the hazard, using the routing components discussed above.

FIG. 16 illustrates an example user interface 1600 used to display locations of other selected individuals along a route to a recreational vehicle user or pilot. User interface 1600 accordingly implements a "buddy tracker" component of the system in which a user selects one or more other pilots to track along a preselected route. The buddy tracker illustrates relative positions of those riders along the trail. As seen in FIG. 16, upon selection of one of the icons 1602 in a map display 1604 illustrating other pilots, information about that pilot, such as their name and relative location, is displayed. In some examples, the buddy tracker feature implemented using the 1600 user interface integrates with the hazard visualization, for example in case a user drives too close to another driver, thus transforming the buddy tracker into a visualization Hazard, which displays a warning to those pilots (and nearby pilots).

FIG. 17 illustrates yet another example user interface 1700 used to display details regarding a selected individual to a recreational vehicle user or pilot. The user interface 1700 is displayed, for example, after selecting a partner or viewing a user profile to display additional information about that other pilot. The illustrated user interface includes an information area 1702 that includes the name and photograph of the pilot, as well as statistics 1704 regarding that pilot, such as miles traveled, frequency or times of the last ride, or shared routes 1706 with that pilot. Optionally, a 1706 “follow” option is also included, which allows the user to track that pilot, for example, to add that pilot to their buddy tracker, or view additional details regarding that user, or integrate various network features usable social media in relation to that user (analogous to a "friend" or follower in various currently available social media systems).

In another illustrated example, the buddy tracker feature provides a notification to vehicles in a group when one of the vehicles leaves a desired trail. In other words, if one of the monitored vehicles in the buddy tracking system takes a wrong turn and leaves the trail, messages are sent to the other vehicles participating in the buddy tracking system so that other drivers can locate to the driver who left the trail.

FIG. 18 illustrates an example user interface 1800 used to display weather data along a trail to a recreational vehicle user or pilot. User interface 1800 includes a map display 1802 that includes a user-selected route 1804, and optionally includes an icon 1806 that illustrates that user's current location on the route. Map display 1802 includes a weather information overlay 1808, either as an icon (as shown) or as radar data, illustrating locations and details regarding portions of the trail that experience inclement weather. Other information such as, for example, warnings (displayed large and then reduced in the display), snow depth, dealer locations, trail overlays, location of prep equipment, trail readiness status, and routes approved rural areas can be provided in the map display. Additional points of interest that can be displayed on the visualization include lodging, medical, shelter, rest areas, gasoline, and landmarks.

The trail condition information includes specific information applicable to off-road trails. For example, snow depth is received and indicated on the indicating instrument display at various locations along the trail. The real-time open or closed status for the trail and the detour due to hazardous trail conditions are sent to the indicating instrument from a remote computer. The wet conditions of the trail are also included in another illustrated example. Operators can determine if a trail is too dusty or too muddy or if ideal wet conditions exist on the trail.

FIG. 19 illustrates an example user interface 1900 used to display and notify trail details to an RV rider or user. The user interface 1900 is therefore integrated with a route planning feature as discussed above, in relation to the display of difficulty and distance information for a particular route, and is also used to provide feedback to a club. from

ES 2 675 019 T3 driving on trails or other pilots relative to a route, as discussed above in relation to Fig. 6.

In the example shown, user interface 1900 includes a trail classification section 1902 in which the user enters trail classifications regarding trail conditions, difficulty, and trail scenery, and views a set classification of other riders on that trail. The 1900 UI also includes a 1904 trail riding club region showing the name of the trail riding club managing the trail, as well as 1906 options for the rider to donate amounts to the trail riding club. variables, as well as once or repeatedly.

FIG. 20 illustrates an example user interface 2000 used to integrate social media features into a trail rider system for use by an RV rider or user. User interface 2000 includes a check-in option 2002, which allows the user to "check-in" to a particular trail or point of interest, analogous to many other location-based social media systems currently available (eg, Foursquare, Facebook, Google+, etc.). In accordance with the present description, it is understood that various other features of such a system could also be included, such as "city halls" or various locations, as well as the inclusion of a recommendation system as part of the trail commentary.

A 2004 community option allows the user to view a group of users in the area, or on the trail, at a particular time, as well as the recent activity of the users that user is connected to (for example, using the option of "Continue" 1708 discussed above). Additionally, a 2006 safety option allows the display of safety-related information regarding the ride or operation of a particular recreational vehicle, or features that may be specific to the trail you are traveling on. In addition, a 2008 rewards option is included, and is used by businesses or other points of interest to reward repeated visits or “check-ins” to that business as a point of interest, or includes incentives that the business wishes to provide to pilots. of recreational vehicles to encourage them to visit the point of interest.

Figs. 21-22 illustrate user interfaces 2100, 2200, respectively, displaying information including embedded vehicle information, such as some of the types of information available from a vehicle ECU, as discussed above in connection with Figs. 4-5. In the embodiment shown in Fig. 21, a user interface 2100 includes a speedometer 2102, as well as indication instruments 2104a-c showing acceleration, power, and torque, respectively. It is understood that other types of indicating instruments, and other data, could also be included in the display. Additional indicating instrument data is discussed below. In Fig. 22, a fuel user interface 2200 is shown that includes a fuel profile 2202. The fuel profile includes a current fuel consumption 2204, an average fuel consumption 2206, as well as a fuel level 2208 and a range 2210 based on the expected fuel consumption for the remainder of the planned route. In addition, a fuel flow indicating instrument 2212 is provided, illustrating a fuel flow rate to the engine. In an illustrated embodiment, terrain maps are used to help determine the estimated fuel range. If the trail is steep, the processor takes the terrain into account when estimating the fuel range for the vehicle.

Both Fig. 21 and Fig. 22 include options that allow navigation between the available vehicle data. For example, in the embodiments shown, the user interfaces 2100, 2200 include a speed option 2120 that causes the display of the user interface 2100, as well as a fuel option 2122 that causes the display of the user interface 2200. Additional options cause the display of other displays; In the example shown, a route option 2124 returns the user to the route planning and trace user interfaces of Figures 7-18, while an engine option 2126 displays additional engine parameters to the user, such as the listing of parameters discussed above as available from the ECU and vehicle 110 of Figs. 4-5. Additional menu options are accessible through a "more" option 2128 (displayed as ellipses).

Referring now to Figs. 23-24, procedures for facilitating the use of a recreational vehicle are analyzed, according to an example of the present description, including procedures for planning and traveling various routes for recreational vehicles (including off-road routes), as well as for integrating planning data. route and vehicle in one comprehensive view to enhance the rider experience.

In the example shown in Fig. 23, a procedure 2300 is generally instantiated by receiving trail data, for example, from a trail data aggregator or from a plurality of trail riding clubs (step 2302). . Based on the trail data, one or more users of an application or web interface then request trail data, to automatically search or generate a trail that the user wishes to traverse (step 2304). This includes, for example, user-entered parameters, such as trail difficulty, travel time, specific points of interest or route points to be visited, or other options. The mobile application 300 and / or the server 102 generate and cause the display of one or more route options based on the parameters provided by the user (step 2306). After viewing the one or more routes, a user selects a route he wishes to travel (step 2308).

ES 2 675 019 T3

Once the user has selected a desired route, a map is generated illustrating the route, as illustrated in the user interfaces of Figs. 7-18, generally (step 2310). The map is selected to display additional options related to that route, such as points of interest (as in Fig. 10), hazards (as in Figs. 14-15), companions located along the route (as in Fig. 16), weather information (as in Fig. 18), or other types of information (step 2312). In the example shown, the map shows a current location of the user in that user's display (step 2314), and optionally publishes that information for other users to track in their applications, for example in app peer tracker features. associated with other pilots (step 2316). Once the user has completed their ride, that user then provides feedback regarding the ride, such as providing feedback regarding the route, including text or ratings regarding difficulty or scenery of the path taken (step 2318).

Referring now to FIG. 24, a method 2400 is provided for integrating such user-based information as discussed above with vehicle information. In procedure 2400, a route selection is received from a user (step 2402), and data is also received from a recreational vehicle, for example from vehicle 108 to server 102 as seen in Fig. 4, or on a mobile device 110, as seen in Fig. 5 (step 2404). A display is provided to the user, as seen in Figs. 21-22, displaying vehicle information to a user in an application combining vehicle and user information (step 2406). Optionally, vehicle information and operational parameters may also be supplied to the server 102 for other purposes, such as transmitting an error code or maintenance information (steps 2408 and 2410). In response, maintenance or repair information is received either at vehicle 108 or mobile device 110, for presentation to a user (eg, a person who needs to repair their vehicle while on the trail) (step 2412).

Another embodiment of the present disclosure is illustrated in Fig. 25. In the embodiment of Fig. 25, a human machine interface (HMI) includes a multi-function indicating instrument 414 having a display. full color display. The 414 indicating instrument includes a 2010 accessory connector that includes the 2012 USB connector port configured to be connected to a 2014 USB drive. The USB drive 2014 illustratively provides software updates, GPS data, special mapping layers, or other data to the indicating instrument 414. In addition, the USB drive 2014 receives data from the indicating instrument 414 such as to record information of route and "driving data" as discussed in this document.

The 2010 accessory connector also includes a 2016 video connector configured to be coupled to a 2018 video camera. Additionally, the 2010 accessory connector includes a 2020 CAN network connection and a 2022 auxiliary audio output connector. The auxiliary output connector 2022 is illustratively connected to an audio output device such as a black box radio 2024 to provide audible alerts or other information to an operator through one or more speakers 2026.

The 414 indicating instrument also includes 2028 input / output connectors including power, ground, eight digital input / output connections, three analog input / output connections, and one CAN network connection as illustrated in block 2030. As discussed Previously, the indicating instrument 414 is connected to a vehicle ECU 402 via a CAN 410 interface. The CAN 410 interface can also be coupled to the black box radio or other audio device 2024.

The indicating instrument 414 is illustratively connected to the user portable mobile device 110 by a suitable connection, preferably a wireless connection such as the Bluetooth data link 2032, to provide communication between the indicating instrument 414 and the mobile device 110. Therefore, the indicating instrument 414 is connected to the Internet 116 or other communication network to the plurality of data sources discussed herein through the mobile device 110. In an illustrated embodiment, the indicating instrument 414 is displays phone call and text information from a mobile phone 110 as illustrated at block 2034. Information displayed on a display of indicating instrument 414 illustratively includes cellular signal strength, call notification, text information, a phonebook, or other information from mobile phone 110. User inputs in indicating instrument 414 are used to control functions of the mobile device 110. Music can also be played from mobile device 110, through indicating instrument 414, and speakers 2026.

Audio streaming is provided to mobile device 110 as illustrated in block 2036. When a black box radio 2024 does not have Bluetooth capability, audio streaming data is transmitted from mobile device 110 to indicating instrument 414 and then through the 2022 audio output to the 2024 black box radio.

A mobile application 38 discussed above with reference to Figs. 1-24 provides information such as map data, route information, location information, or buddy tracking, and other information to the mobile device 110. In the embodiment of FIG. 25, data from mobile app 2038 is transferred

ES 2 675 019 T3 to the Indication Instrument 414 for its display. Inputs from Indication Instrument 414 are transferred to mobile device 110 to control features of mobile application 2038.

In mobile device 110, a real-time route planning mobile application 2040 is used to plan and display route information using inputs on an indicating instrument 414. For example, route planning software can be used in application 2040. of Primordial. In addition, a vehicle data recording and diagnostic application 2042 such as a mobile digital wrench is controlled and viewed on the indicating instrument 414 through the mobile device 110.

A GPS disk from module 2044 is also coupled to indicating instrument 414. GPS module 2044 provides location data to indicating instrument 414 for mapping, route planning, or other functions described herein.

Referring now to Fig. 26, in another example of the present disclosure, a vehicle 3010 has a suspension located between a plurality of ground contact members 3012 and a vehicle frame 3014. The ground contact members 3012 they include wheels, skis, guide tracks, treads, or the like. The suspension typically includes springs 3016 and shock absorbers 3018 coupled between ground contact members 3012 and frame 3014. Springs 3016 may include, for example, coil springs, leaf springs, air springs, or other gas springs. The 3016 air or gas springs can be adjustable. See, for example, US Patent No. 7,950,486. Springs 3016 are often coupled between vehicle frame 3014 and ground contact members 3012 through an A-arm link mechanism or other type of link mechanism. Adjustable shock absorbers 3018 are also coupled between the ground contact members 3012 and the vehicle frame 3014. In an Illustrated example, a spring 3016 and a shock absorber 3018 are located adjacent each of the ground contact members 3012. On an ATV, for example, four springs 3016 and adjustable dampers 3018 are provided adjacent to each wheel 3012. Some manufacturers offer 3016 adjustable springs in the form of either air springs or hydraulic preload rings. These 3016 adjustable springs allow the operator to adjust body height on the fly. However, a majority of the ride comfort comes from the damping provided by the 3018 shocks.

In an Illustrated example, the adjustable dampers 3018 are electrically controlled dampers to adjust the damping characteristics of the dampers 3018. An ECU or other controller 402 provides signals to adjust the damping of the dampers 3018 continuously or dynamically. Adjustable dampers 3018 are illustratively adjustable to provide different compression damping, rebound damping, or both. Additional control details of the adjustable ride control system are described in US application No. 61 / 723,623, filed November 7, 2012, owned by the assignee of the present application.

In an illustrated embodiment of the present disclosure, an indicating instrument 414 provides a man-machine user interface provided in a location readily accessible to the driver operating the vehicle. Preferably, the Indication Instrument 414 is mounted adjacent to the driver's seat on the dashboard or integrated on a display within the vehicle. The indicating instrument 414 includes user inputs discussed below to allow the driver or a passenger to manually adjust the damping of the shock absorber 3018 during vehicle operation based on the road conditions encountered. The display of the indicating instrument 414 shows information related to the damping settings of the damper.

In the Illustrated embodiment of Fig. 26, the ECU 402 also controls an electronic continuously variable transmission (ECTV) 3024 and an electronic power steering (EPS) 3025. vehicle 3010. In an illustrated embodiment, mobile device 110 or indicating instrument 414 is used to monitor performance characteristics of vehicle 3010 including adjustable dampers 3018, ECVT 3024, EPS 3025, or other electronically controllable performance functions of the vehicle.

The ECU 402 receives inputs from the Indication Instrument 414 or mobile device 110 to adjust the damping characteristics of the 3018 adjustable dampers or control the 3024 ECVT or 3025 EPS. The 3018 front and rear dampers are independently adjustable to adjust characteristics driving the vehicle 3010.

A plurality of sensors are also coupled to the ECU 402. For example, a global shift accelerometer 3025 is coupled adjacent to each ground contact member 3012. The accelerometer 3025 provides an output signal coupled to the ECU 402. The accelerometers 3025 provide an output signal indicating the movement of the ground contact members and suspension components 3016 and 3018 as the vehicle traverses different terrain.

Additional sensors may include a 3026 vehicle speed sensor, a 3028 steering sensor, and a

ES 2 675 019 T3 3030 chassis accelerometer all having output signals coupled to ECU 402. The 3030 accelerometer is illustratively a three-axis accelerometer located on the chassis to provide an indication of forces on the vehicle during operation. Additional sensors include a 3032 brake sensor, 3034 throttle position sensor, 36 wheel speed sensor, and 3038 gear select sensor. Each of these sensors has an output signal coupled to ECU 402. ECU 402 detects when a vehicle is upside down using accelerometer 3030 and sends a distress signal through mobile device 110.

In an illustrated embodiment, the indicating instrument 414 is used in a demonstration mode on the floor of a showroom. Indication instrument 414 illustratively receives video or other information via USB port 12, video connection 16, or via portable mobile device 110 to provide videos or other information on the display of indication instrument 414 for promotional purposes.

In another embodiment of the present invention, the indicating instrument 414 facilitates tracking of a vehicle. The indicating instrument 414 receives information from the various sensors shown in FIG. 26 and location data from the GPS input 2044 to track how the vehicle was driven and where it was driven. This "driving data" is stored locally and retrieved, for example, via USB port 12 or the data is sent via mobile device 110 to a remote location for storage and processing. Additional details of driving data monitoring, storage, and playback are discussed in US Patent Publication No. 2010/0090797, owned by the assignee of the present application.

In an illustrated embodiment, an owner can monitor a fleet of vehicles to determine a location of each vehicle and how the vehicles have been driven. In another embodiment, the indicating instrument 414 is used to adjust vehicle settings, such as springs 3016 or adjustable dampers 3018 of a suspension system or to adjust a continuously variable electronic transmission (ECVT) 3024 through the indicating instrument. 414. Vehicle settings are illustratively based on an experience level of a vehicle driver, a route the vehicle is driven on, or other factors. For example, different settings are provided for the ECVT 3024, suspension system 3016, 3018, or other systems depending on whether the vehicle is being driven on the highway, off-road, or off-road. In an illustrated embodiment, vehicle components 3010 automatically adjust based on a detected vehicle location using GPS data.

In another embodiment, mobile device 110 provides a security device or security key for the vehicle through its communication with indicating instrument 414. In an illustrated embodiment, mobile device 110 includes a driver profile that includes age and the level of experience. Indication instrument 414 receives driver profile information from mobile device 110 and automatically sets vehicle settings such as vehicle suspension, gear shift patterns, etc. based on the driver's profile.

In another illustrated embodiment, the indicating instrument 414 receives vehicle information from the sensors shown in FIG. 26 and provides a time indication on the received vehicle kinematic data. This "driving data" is linked to a vehicle location on the route via GPS data and a timestamp of the time the vehicle was at the different locations. Therefore, the vehicle can store all the information associated with a ride and the user can repeat the ride after it has finished as discussed above.

In another embodiment of the present disclosure, mobile device 110 and indicating instrument 414 will track and manage a vehicle. The 2038 mobile app tracks and locates a vehicle. A planning system prioritizes and allocates the use of the vehicle.

Additional details of an illustrated embodiment of the indicating instrument 414 are shown in Figs. 27 and 28. The indicating instrument 414 includes a body portion 3040 that houses a display 3042. A plurality of select buttons 3044 allow the user to control various features and functions of the present system as described herein. In an illustrated embodiment, the center button 3046 is a menu key button. Buttons 3048 and 3050 provide up and down scroll functionality. Buttons 3052 and 3054 provide selections for various items as discussed below.

An illustrated embodiment of the display screen on the indicating instrument 414 is shown in Figs. 29 and 30. For example, the 414 indicating instrument is used to display speed, fuel level, coolant temperature, RPM, gear shift position, trip odometer, compass, and gauges. of the turn signals. A display screen includes a top 3060 that provides header information. The main section 3062 of the display shows information related to the various parameters discussed above. Section 3064 shows witness information. As shown in FIG. 30, when menu key button 3046 is pressed, the main menu appears on display screen 3042 of indicating instrument 414. The user then selects different screens to

ES 2 675 019 T3 visualization and control. The LEDs in section 3064 of the display illustratively include an Engine Trouble Alert, Low Fuel, Coolant Temperature / Level Alert, Oil Pressure Alert, Low Voltage Alert, Parking Brake Indicators, and Lights long.

Figs. 31-34 illustrate various mounting positions for the indicating instrument 414 of the present disclosure. In Fig. 31, the indicating instrument 414 is mounted below an existing display 3070. Fig. 32 illustrates the indicating instrument 414 mounted on a front dash of a utility vehicle. FIG. 33 illustrates the indicating instrument 414 mounted within a snowmobile. FIG. 34 illustrates the indicating instrument 414 mounted on an ATV.

The indicating instrument 414 includes a body portion that houses a display. A plurality of physical selection buttons allow the user to control various features and functions of the present system as described herein. In an illustrated embodiment, the center button is a menu key button. Other buttons provide up and down scrolling functionality. The buttons also provide selections for various items as discussed later. In another embodiment, virtual control buttons are provided on a touch screen.

An illustrated embodiment of the display screen on the indicating instrument 414 is shown in FIG. 35. For example, the indicating instrument 414 is used to display vehicle speed, fuel level, coolant temperature, RPM, gear shift position, trip odometer, compass, and turn signal indicators. A display screen includes a top that provides header information including cell phone battery status, cell phone signal strength, missed calls, number of text messages, a clock, a signal strength Bluetooth, a compass, and turn signals. Trouble codes are located under the heading and are displayed only when a problem arises such as coolant temperature, low fuel, engine trouble, battery trouble, or the like. Other icons provide additional information, including fuel level, ADC icon, AWD icon, gear shift position, coolant temperature, high beam indicator, parking indicator, fuel percentage remaining, trip odometer, and engine temperature. refrigerant. The indicating instrument also provides radio integration.

A first main menu screen is shown in Fig. 36A. The controls or buttons or 4010 are shown at the bottom of the display. Buttons 4010 are actuated through a touch screen or physical buttons located below the gauges. The 4012 button controls the screen brightness. Up arrow 4014 and down arrow 4016 allow the operator to navigate through the menu on the display screen. For example, the user can navigate between a main menu to display vehicle operating data, a new menu item to display navigation / map information, a menu item to display phone information, and a menu item to display information on diagnostics, a menu item to display gPs settings, and a menu item to display system settings. Once the appropriate item is highlighted, the operator makes a selection with button 4018. Button 4020 returns to the previous screen.

Illustrative embodiments of the main display screens for indicating instrument 4014 for displaying vehicle operating data are shown in Figs. 37-42. In Fig. 37, the leftmost button 4022 toggles the main screen display. In a first configuration, shown in fig. 37, miles per hour are displayed larger and located above the RPM display. Fuel is displayed on the left and system voltage on the right. Toggling the main screen by pressing button 4022 changes to the display setting of Fig. 38 with RPMs higher and at the top and MPH at the bottom. Fuel is displayed on the left while engine temperature is displayed on the right. Toggling the main screen can also change the display to the fast go screen shown in Fig. 39.

The next button 4024 in the main menu of Fig. 37 toggles between an odometer reading, trip 1, trip 2, fuel economy and range. The trip odometer is shown in Fig. 40. Fuel economy is shown in Fig. 41 with a graphical indicator. The fuel range is shown in Fig. 42.

Center button 4026 in the main menu shown in Fig. 37 causes additional menu items to be displayed as shown in Fig. 36A. The next 4028 button to the right of the center toggles between the display of the engine coolant temperature and the system voltage. The rightmost button 4030 enters the Bluetooth menu as discussed below with reference to Fig. 51-58.

A menu of system settings is illustrated in Fig. 36B. The leftmost button 4012 in the footer controls the brightness setting and the rightmost button 4020 returns to the previous menu. Center button 4018 selects a menu item while up and down arrow buttons 4014, 4016 move the cursor to select menu options. System settings include display, service, units, time, system information, and vehicle settings.

ES 2 675 019 T3

Display settings are used to set day and night brightness levels or change the language used in the display. The service screen is used to view engine hours and reset service intervals as shown in Fig. 44. The units setting changes the speedometer and temperature units and changes the clock type between 12 hour time. and 24 hours. The time settings select either a real time clock or a GPS clock, set the time, time zone or daylight saving time. The system information screen shows technical information and basic vehicle information.

The vehicle settings menu is shown in more detail in Fig. 60. Again, the leftmost icon or button 4012 controls the brightness setting while the rightmost button 4020 returns to the main menu. The center select button 4018 and the up and down arrow buttons 4014, 4016 navigate the menu. The vehicle settings menu includes a fuel type, a vehicle lock, and a code change. The type of fuel allows the user to select the type of fuel that is used. The lock button allows the user to enter a code to lock the vehicle's ECU. A dealer can lock or unlock this feature. Lock code change is also available if unlocked by dealer.

FIG. 43 shows an exemplary service reminder indicator displayed on the display of the indicating instrument 414. The operator may press OK to remove the reminder. Fig. 44 indicates the number of hours the engine has run, the interval for service, and the hours remaining until service. Fig. 45 allows the operator to reset the service hours after the service has been performed.

FIG. 46 is an illustrated embodiment of an advanced user notification and description such as an indication that detonation has been detected. Other notifications are provided such as when engine power is reduced in an "emergency run" mode after certain serious malfunctions are detected. Fig. 47 illustrates an icon in the lower right corner indicating the detection of an engine fault. When selected, the display screen provides an error or malfunction code and a written description of the problem such as the temperature being too high, for example, as shown in Fig. 48. The display also shows a correction For the problem that is illustratively contact a dealer. In another embodiment, a description of a possible correction for the fault is provided to the operator so that the fault can be corrected on site without contacting the dealer. Providing the fault description rather than just the fault code allows the operator to diagnose problems and take corrective action.

In another embodiment, an image is shown on the display screen showing where in the vehicle the breakdown or problem has occurred. For example, the location of a faulty sensor may be displayed. In another embodiment, an electronic copy of the owner's manual or service manual for the vehicle is stored in memory so that when a particular fault code is generated, specific instructions for correcting the fault are shown on the display. In other embodiments, drawings or illustrations are also shown. In other embodiments, video tutorials can also be provided on the display screen showing the actual repair of the problem. Figs. 49 and 50 illustrate additional dynamic indicator bars for low fuel, engine problems, parking brake, high beams, and the like.

In another embodiment of the present invention, the vehicle records the times at which the error or fault codes occur during the operation of the vehicle. The stored operational parameters or attributes of the vehicle such as speed, engine RPM, temperature, fuel consumption, or any of the other vehicle parameters described herein are stored so that these vehicle characteristics are determined. at the time the error occurred. Additionally, desired weather, geography, or other stored data can be linked to the time the error code occurred. In other words, the technician can determine the vehicle's operating parameters, as well as the type of terrain the vehicle was traversing and the current weather conditions at the time the error occurred to aid with diagnosis. When fault or error codes occur, the indicating instrument 414 can also encourage the user to email or call the dealer to discuss corrective actions or make an appointment. Parts availability at locations close to the trail can be checked using an inventory management system.

FIG. 51 illustrates a phone menu for indicating instrument 414. Middle button 4040 enables or disables the Bluetooth or other wireless connection to the phone. With wireless enabled, the leftmost button 4042 displays phone recording information, including toggling to text messages, displaying a list of missed calls to allow the operator to navigate to the most recently missed calls and update the call list losses. The rightmost button 4048 returns to the previous menu. the text recordings indicator button 4044 causes the lists of missed text messages to be displayed on the indicating instrument and allows navigation through received text messages. User can switch to missed calls or return to previous menu from text message list.

Button 4046 displays a list of available devices. The user can navigate to an available device and connect / disconnect a device or pair / unpair a device. The user can also display a

ES 2 675 019 T3 device priority list to navigate to a paired device or change connection priority using the middle button to move a selected device to priority number 1. Additional details of Bluetooth wireless connectivity are shown in Figs. 52-58. Fig. 52 shows a list of devices. Figs. 53 and 54 illustrate a pairing request and the pairing completed screen. Figs. 55 and 56 are additional Bluetooth wireless connectivity displays. Fig. 57 shows missed calls while Fig. 58 shows the call to a particular number.

In one embodiment, the user can read text messages on the display screen of the indicating instrument, but only when the vehicle is not moving. The system is linked to GPS 2044 or an engine speed or RPM detector to determine if the vehicle is moving and to block the viewing and sending of text messages and / or phone calls. Vehicle speed, RPM, or GPS signals can be used to reconnect the wireless signal if the signal has been lost. Again, the system will wait until the vehicle is not moving to make the connection. Any desired feature of the indicating instrument can be locked out when the vehicle is in motion. Viewing text messages, or using the maps discussed below, or any undesirable feature to use while the vehicle is in motion may be blocked. A security code can block phone information while driving, disable maps, or other features depending on the particular operator. A rental fleet, for example, can block certain features. Young drivers may also be prohibited from using certain features.

A menu of maps is illustrated in Fig. 61. The central button 4050 opens the main menu while the buttons on the left side 4052, 4054 allow you to zoom in and out on the map as illustrated in Figs. 61 and 62. Vehicle direction, destination and trail map are displayed on the map regardless of zoom level. Therefore, the desired path remains visible on the display as the zoom effect occurs. An arrow indicator on the compass shown in the display of Figs. 61 and 62 show a direction of travel of the vehicle. Button 4056 opens a pan menu that allows the user to pan west, north, south, and east. Figs. 63 and 64 illustrate the panorama on the maps. The rightmost button 4058 opens additional map menu options, including centering the display screen on the current vehicle location, setting a waypoint at a current location, or panning the vehicle (the waypoint also added to the waypoint manager), save the current track to a USB memory device (adding the current track to the track manager), and delete the track that is currently being recorded.

Fig. 59 is a GPS settings menu. The leftmost button 4060 controls the brightness selection, while the middle button 4062 and the up and down arrow buttons 4064, 4066 to navigate the menu. The rightmost button 4068 returns to the previous menu. The GPS settings menu includes a track manager, a waypoint manager, and satellite settings menu items. The track manager allows the user to select a stored track or trail, or edit a track name, show or hide the track on the map, delete the track, import a track from USB memory, or export a track to USB memory. .

The waypoint manager allows the user to select a desired waypoint or open a waypoint editor. The waypoint editor allows the user to change a waypoint name, change a waypoint color on the map, activate and deactivate the "go to" function, view a waypoint on the map, delete a point route, import a waypoint from USB memory or export a waypoint to USB memory.

The satellite status menu selection brings up a display screen of Fig. 70 showing satellite signals. The satellite status illustratively includes the number of satellites, latitude and longitude, and satellite error comments.

Figs. 65-67 illustrate adding a waypoint that is displayed on the map. The cursor is positioned at a desired location as shown in Fig. 66. The waypoint is named in Fig. 65 and then the entered waypoint is displayed on the map in Fig. 66. The details of the Waypoint is shown in Fig. 67. The “go to” function is disabled in Fig. 67. With the “go to” function selected, the word “disabled” in Fig. 67 changes to the word “enabled”. ”. A first compass arrow 4070 of FIG. 68 shows a current vehicle location and a current vehicle heading. A second arrow 4072 displayed on the compass shows a desired or necessary direction to reach the next waypoint 4074. This arrow helps guide the vehicle operator to waypoint 4074.

Fig. 69 shows an example for saving or importing tracks. In Fig. 69, the current track is shown with the ability to show or hide the track on the display screen. The track can also be deleted or exported. A new track can also be imported. The map can be displayed on the display screen in different colors. Again, the track or trail map is visible regardless of the zoom in or out on the map and remains highlighted in the display as the zoom is increased or decreased. For route points, all route points, only specific route points, or no route points can be displayed selectively. A distance to the next waypoint can be displayed. An estimated travel time to the next waypoint or final destination can also be displayed.

ES 2 675 019 T3

Figs. 71A and 71B illustrate a rocker switch control 4090 preferably located on a handlebar or other vehicle steering control. The rocker switch 4090 is a rocker switch having a "mode" selection part 4092 and a "set" selection part 4094 depending on which direction the button is pressed. If the set part 4094 is pressed for a long time, longer than 2 seconds, for example, it cycles through a main screen. If the setting part 4094 is pressed quickly, a specific screen option 1 opens. If the mode part 4092 is pressed for a long time, greater than 2 seconds, a specific screen option 3 opens. 4092 mode is pressed quickly, a specific display option is selected 2.

The switch control logic for maps is shown in Fig. 32. Exemplary switch control logic for other display screens is shown in Fig. 74. It is understood that other logic may be used to scroll through the various display screens. menu.

FLEET MANAGEMENT

The system and method of the present disclosure can be used to facilitate fleet management of a plurality of vehicles. GPS tracking allows vehicles to be tracked and routes taken by vehicles during operation to be stored. Routes can be planned, and vehicles can be programmed. You can register the entry or exit of vehicles as when renting vehicles in a resort. Campus or urban areas may also include vehicle check-out and return. The fleet manager can track maintenance needs, vehicle battery charge status, vehicle location, etc. An estimate of vehicle drag can be provided based on power and speed. Self-diagnostic cycle monitor for correct wheel alignment, bearings, low tire pressure, etc. Indicators are provided to fleet operators and managers when a service is required. Fleet managers can track position and locate every vehicle in the fleet. A planning system is used to prioritize and assign vehicle use. A display of the state of charge for electric vehicles or the fuel level of vehicles in the fleet can also be provided and sent to a remote computer accessible by the fleet manager. An operator's phone or other device can be used as a key or security device for the vehicle. Alternatively, a key card or security badge can be used to activate the vehicle.

Recreational shared transportation by campus, urban, by trails

In another illustrative example of the present disclosure, a system and method is provided for shared transportation particularly on college campuses, in a city, near trails or other recreational locations. Illustratively, recreational vehicles such as motorcycles, off-road vehicles such as all-terrain vehicles (ATVs), UTVs, and snowmobiles can be shared. Furthermore, electric vehicles can be shared according to the system and procedure described.

An illustrated example of the procedure includes the following features:

1. Reservation system, check-in, check-out.

a) The entry and exit of vehicles is recorded and left in the parking lot and / or charging stations. Vehicle utilization is planned as a resource in a wireless capable application. The application provides data for vehicle locations, availability, scheduling conflicts, charge level, charge status, destinations, charging stations, autonomy to destinations, as well as allowing vehicle reservation and vehicle check-out.

b) Post-check-out applications can also be used for additional route planning, and range monitoring.

c) Security enabled with mobile application or badge.

d) Requires the vehicle to be properly parked and, where applicable, properly connected to the charging system for entry to be recorded as a returned vehicle.

e) Reserve parking and charging station at the destination.

f) Ensures adequate autonomy for the journey.

g) The security system checks the credentials and tracks the vehicle.

two. Fleet management

a) Fleet management with wireless capability. The machines are registered at the end of each day, transmit the conditions and service needs and confirm the correct load connection.

b) It allows remote monitoring of the use, maintenance, load status and safety of the fleet.

c) Maintenance is recorded and tracked. Alerts sent when vehicle maintenance is required.

d) Vehicle drag profile during known driving cycles to determine when maintenance is needed such as tire pressure, alignment, hanging brakes.

ES 2 675 019 T3

e) Vehicle efficiency diagnostic profile and vehicle trends that will be uploaded to a supervisory system.

f) Wireless or cellular upload of use profiles, maintenance notices, and efficiency profiles. The monitoring system records state of charge, battery aging, efficiency drops, and specific diagnostic codes such as low tire pressure, motor and / or controller overheating or overloading.

3. Route planning

a) State of charge, the energy information comes from the VCM. Match the route plan to ensure adequate autonomy to complete the journey.

b) Route planning on a campus, urban center, trail, or recreational setting. More detail of the map, locations of charging stations, monitoring of vehicle autonomy and notification of critical charge levels, etc.

c) The autonomy monitoring allows the user to enable the economy mode to help ensure that the user reaches a destination point or a charging station.

In alternative embodiments, features or applications available on a smartphone can be integrated into the vehicle or the indicating instrument through the wireless connection and the display. For example, the RiderX applications made available by Polaris Industries can be implemented on the indicating instrument using the RiderX applications.

As discussed in US Application Serial No. 61 / 769,378, users can enter trail information and other data as they traverse a particular trail. Hazards, trail conditions, or other information are transmitted via cell phone to a remote computer location. Updated information is sent to the vehicle from a central server. Information regarding which trails have been prepared as well as the current location of the preparation equipment is provided on the display screen of the indicating instrument in an illustrated embodiment of the present disclosure. Therefore, the operator can select trails based on recent preparation or make sure to take care of the trail preparation equipment.

The display of the indicating instrument is capable of switching between vehicle information and maps on the same display with the push of a button. This improves the rider experience, especially for off-road vehicles. The user can quickly switch between important vehicle information and map screens on the same display with a quick, easy-to-use interface.

In another embodiment, a camera 2018 is coupled to the indicating instrument through the video connector 2016 shown in Fig. 1. The display of the camera image is provided on the display of the vehicle indicating instrument to allow the operator adjust a camera position to make sure it is positioned in the best position to capture images while riding.

A server or website can be accessed to provide access to different trails available for drivers of different skill levels. The website allows users to share their experiences on the trail and rate the trail.

In another example, the system stores snow trails accessible by snowmobiles and non-snow trails. The operator can select a user input to display only nearby snow trails, non-snow trails, or both types of trails on the display of the indicating instrument for selection of a desired trail by an operator.

In another example of the present description, the wireless connection is used to carry out accessory functions such as opening garage doors, opening gates, turning on lights, remote starting the vehicle, or the like.

The system and method of the present disclosure extends the motor sports experience by allowing vehicle users to plan a step, experience a step, and then relive the step. Before the step, users plan the route and view simulations based on photos, videos, or other route information discussed earlier. Illustrative simulation modes include:

Walk along the path

Explore globally

Compete with the pros

Simulated sound and feel of a private vehicle

Play, compete with the professionals in motocross on snow, motocross, etc.

Links to allow online purchases. The user can purchase equipment and accessories for the user's vehicle online.

ES 2 675 019 T3

The system and method of the present disclosure raises a user's excitement and anticipation before a ride. The user plans the route with cartographic software that includes information on trails for snowmobiles and ATVs. The trail database includes images of points of interest, linked to the map. The user also plans entertainment, music and information, weather radio, etc., and liaison between the trail leader and his companions. The user simulates all or part of the ride on a personal computer, or the display of the indicating instrument, which provides a simulation of the ride, landscape, trail conditions and obstacles.

The user uses a stored tour plan that includes route information, entertainment, and information flow by uploading the stored plan within the vehicle's systems such as via the 2012 USB connector. A 2018 digital camera or camcorder allows the user to record the highlights of the ride linked to the GPS position. During the ride, the system generates a trip log that records the current route, digital photos or videos. Entertainment and communications are timed and recorded. Sensor readings are also time indexed to show the vehicle's performance on the ride.

After the ride, the user relives the experience and shares it with others. The user returns an electronic record to the personal computer based on the simulation so that the experience can be relived and shared with others. Indexed with respect to time, the simulation includes:

GPS position

Trail conditions

Weather conditions

Communication when it happens

The music or entertainment that was playing

Photos and videos taken at points of interest

Cell phone coverage is often not available in locations where RVs travel. A traffic alert and navigation system is provided for recreational vehicle applications, such as off-road vehicles, ATVs, UTVs, and snowmobiles. The system identifies the location, direction, and speed of other similar vehicles on roads, trails, and in open terrain. This enables buddy tracking, fleet management, and traffic alerts to similarly equipped vehicles remotely or in organized driving park environments. The illustrated system manages the available communication networks based on their availability to provide the best available information:

to. Vehicle systems links to smartphones, GPS, and other devices through a Bluetooth link or other similar communication links to share information and access local and global information networks.

b. The system continually evaluates available networks and uses the best available network to transfer data for vehicle use and remote services. Examples of links could include cellular service, satellite communications, Wi-Fi, GMRS radio, and any other available data service.

c. When no other vehicle-to-vehicle communication source is available, the system of the present disclosure establishes a local radio transceiver-based network using frequencies such as the GMRS band to share vehicle location, direction, and speed with similarly equipped vehicles. This enables group ride companion tracking, park management, and alerts each vehicle to approaching other vehicles and safety hazards. Alternatively, a fixed base radio transceiver could be used in a driving park as a setting to share data with vehicle transceivers to facilitate two-way communications. Additional information such as radar weather conditions or general traffic and trail conditions is relayed to all vehicles on the network and displayed and / or used as appropriate.

d. When external network data is not available, potentially including GPS or other locator data, the system predicts, or estimates vehicle locations, obstacles, and other traffic.

and. An illustrated example of the system incorporates a feature similar to 406 MHz distress transmitters to provide a distress call when no other communications are available.

In a further example of the present invention, the system sets a maximum speed for the vehicle based on the experience of the driver or a location of the vehicle on a planned route. Furthermore, the maximum speed can be set depending on an operation carried out by the vehicle such as mowing or fertilizing. A fleet owner can set a maximum speed for users of a fleet of vehicles.

Different vehicle components, such as the 3018 adjustable dampers, the ECVT 3024, the EPS 3025 or other system components such as an electronic transmission control can be adjusted on the fly during a ride. For example, a street mode, a trail mode, an off-trail mode, a rock climbing mode, or other modes may be set for particular driving conditions. These settings are made automatically when the vehicle passes over a route or are selected by the user using the mobile device 110 or the indicating instrument 414. In addition, a fuel economy mode can be set for highway or trail use, while A maximum performance mode can be set for off-trail sections of the route. A clutch diagram for snowmobiles is provided at

ES 2 675 019 T3 different elevations.

In an illustrated embodiment, detected engine malfunctions are displayed on the display screen of the indicating instrument 414 or mobile device 110. A probable cause of the malfunction and possible corrective actions to be taken on the trail are also displayed in the indicating instrument 414 or mobile device 110. The integrated mapping system shows dealer locations and additional information such as phone numbers to provide service, assistance or parts along the route. The mapping system provides a distance to the closest dealership from the vehicle location. In one embodiment, a dealer inventory is checked to determine if a particular part is available from a particular dealer.

As discussed above, the system provides instant updates via mobile device 110 to indicating instrument 414 for road or weather conditions and provides overlays on the route map. For example, snow conditions, weather alerts, traffic alerts, or avalanche warnings are provided.

The indicating instrument 414 is integrated into the vehicle in certain embodiments. In other embodiments, the indicating instrument 414 is modular and can be removed from a vehicle, such as a utility vehicle, an off-road vehicle, or a snowmobile and placed in another vehicle. Security is provided such as using vehicle identification numbers to reduce theft of the 414 modular indicating instrument.

In another embodiment, mobile device 110 includes a control option to remotely start the vehicle or open a garage door by communicating with the indicating instrument 414. A GPS watch or a smart phone watch is illustratively used to control contrast. on a display of the indicating instrument 414.

Data displayed on the indicating instrument and recorded in the vehicle is stored internally so that no connection to a telephone is required for operation. Updates occur the next time a wireless connection is made to the central server network.

In another illustrated embodiment of the present disclosure, a user or technician sets a vehicle to enter a diagnostic mode. When an accelerator is pressed the vehicle follows a diagnostic profile. The diagnostic profile comprises driving the vehicle through at least one of preconfigured controlled speeds, accelerations, and / or torques, or a profile consisting of a combination of controlled speeds, accelerations, or torques. The profile can run in one or more iterations and in more than one direction. Directions can include forward and reverse or multiple forward orientations across terrain. Running the profile in multiple iterations can be used to compensate for terrain quality or can be used in obtaining additional vehicle diagnostics.

A controller with a memory records performance data from vehicle sensors as discussed herein. Vehicle sensors can measure metrics such as force, power, engine torque, engine current, battery current, battery voltage, engine speed, vehicle speed, accelerometer readings , among other things. In addition, the user can enter any combination of additional characteristics into the vehicle such as vehicle weight, estimated vehicle weight, tire type, tire pressure, or other characteristics as a result of vehicle customization.

Recorded data from the sensors is used to calculate various vehicle diagnostics or can be compared to a profile of known metrics. For example, the data can be compared to a maximum of acceptable vehicle metrics related to constant speed. Data values ​​that exceed the maximum value for a specific metric can detail various aspects of vehicle performance.

In an embodiment related to a vehicle diagnostic profile, a vehicle is driven at a constant speed, the vehicle data is recorded, then the vehicle speed is increased by a fixed amount at a steady acceleration, and another set of data is recorded. vehicle. The vehicle diagnostic profile can then be repeated in reverse or other forward operational direction. Vehicle sensors can then, for example, indicate a tire, suspension or alignment problem. In another embodiment, the vehicle diagnostics can include various aspects of vehicle performance including: alignment, brake performance, suspension performance, range performance, battery performance, and others.

In accordance with the mobile application, the web application, the vehicle interface, and the general system discussed herein, a number of additional features can also be integrated for both in-vehicle and out-of-vehicle services. This may include, for example, identifying preferred service partners for OEMs or specific trail riding clubs, as well as advertising embedded in one of the interface.

ES 2 675 019 T3 web and mobile interface or both. It is understood that, in some cases, advertising may be limited to the web interface or certain user interface screens due to screen area limitations relative to a mobile device or display of the indicating instrument, and to avoid displaying advertising to a user of a mobile device or a display of the indicating instrument while that user is operating a recreational vehicle. In an illustrated example, the revenue generated from such advertisements is provided to trail driving clubs and the maintenance of the system 100 in general.

The embodiments of the present disclosure are practiced on various types of electrical circuits comprising discrete electronic elements, compact or integrated electronic chips containing logic gates, a circuit using a microprocessor, or on a single chip containing electronic elements or microprocessors. The embodiments of the description can also be practiced using other technologies capable of performing logical operations such as, for example, AND, OR, and NOT, including but not limited to mechanical, optical, fluidic, and quantum technologies. In addition, aspects of the procedures described herein can be practiced within a general purpose computer or in any other circuit or system.

The embodiments of the present disclosure are implemented as a computer process (method), a computer system, or as an article of manufacture, such as a computer program product or computer-readable media. The computer program product may be a computer storage medium readable by a computer system and encoding a computer program of instructions for executing a computer process. Accordingly, embodiments of the present disclosure can be incorporated into hardware and / or software (including firmware, resident software, microcode, etc.). In other words, the embodiments of the present disclosure may take the form of a computer program product on a computer-usable or computer-readable storage medium that has computer-readable or computer-usable program code embedded in the medium for use by or in connection with an instruction execution system. A computer-usable or computer-readable medium includes any medium that includes media capable of containing or storing the program for use by or in connection with the instruction execution system, apparatus, or device.

Embodiments of the present disclosure, for example, are described above with reference to block diagrams and / or operational illustrations of procedures, systems, and computer program products according to embodiments of the disclosure. The functions / acts annotated in the blocks can occur out of the order shown in any flowchart. For example, two blocks displayed in succession may, in fact, run substantially simultaneously or the blocks may sometimes run in the reverse order, depending on the functionality / acts involved.

Although the embodiments of the present disclosure have been described as being associated with data stored in memory and other storage media, the data may also be stored on or read from other types of computer-readable media. Furthermore, the phases of the described processes can be modified in any way, including rearranging the phases and / or inserting or deleting phases, without departing from the general concept of the present description.