Connected helmet, system and method for operating the helmet

Abstract

A helmet (20) for communicating with a vehicle function controller (16) and an operating method thereof, wherein the helmet has a first memory (512), a first transmitter (532), a first receiver (530) and a first controller (510), wherein the first controller communicates with the first memory (512), the first transmitter (532) and the first receiver (530). The first receiver (530) receives a plurality of vehicle (10) function settings. The first memory (512) stores the vehicle (10) function settings in the memory (512) of the helmet (20). The first transmitter (532) transmits the vehicle (10) function settings from the first memory (512) to the vehicle function controller (16). A system including a helmet (20) and a vehicle (10) is further configured to enable the vehicle to start in response to an identifier transmitted by the helmet (20) to the vehicle controller (610).

Description

[0001] This application is a divisional application with an international application date of October 31, 2019, an international application number of PCT / US2019 / 059071, an application number of 201980082368.8, and an invention name of “Connected helmet, system and method for operating the helmet”. Technical Field

[0002] The present disclosure relates to a helmet for use with a vehicle, and more particularly, to a helmet that allows function settings to be communicated to a vehicle operating system. Background Art

[0003] This section provides background information related to the present disclosure which is not necessarily prior art.

[0004] All-terrain vehicles, snowmobiles, and other types of off-road vehicles may be used by both adults and children. Some vehicles allow the user to adjust settings through a menu display on the vehicle. However, multiple users may use the vehicle and, therefore, the settings may have to be adjusted if another user changes a user's favorite settings.

[0005] Since children also use various types of off-road vehicles, parents may wish to restrict the operation of various functions of the vehicle. However, there is no known method for restricting such functions. Summary of the invention

[0006] This section provides a general summary of the disclosure, and is not a comprehensive disclosure of its full scope or all of its features.

[0007] The present disclosure provides a system for adjusting operating functions of a vehicle so that the operating functions are set and adjusted based on stored settings transmitted from a helmet while the driver is operating or approaching the vehicle.

[0008] In one aspect of the present disclosure, a system includes a controller and a vehicle controller disposed within a vehicle. The helmet transmits an identifier to the vehicle. The controller enables the vehicle to start in response to the identifier.

[0009] In another aspect of the disclosure, a helmet for communicating with a vehicle function controller has a first memory, a first transmitter, a first receiver, and a first controller that communicates with the first memory, the first transmitter, and the first receiver. The first receiver receives a plurality of vehicle function settings. The first memory stores the vehicle function settings in a memory of the helmet. The first transmitter transmits the vehicle function settings from the first memory to the vehicle function controller.

[0010] In yet another aspect of the disclosure, a method includes receiving a plurality of vehicle function settings at a first receiver disposed within a helmet; storing the vehicle function settings in a first memory of the helmet; transmitting the vehicle function settings to a vehicle function controller using a first transmitter disposed within the helmet; receiving the vehicle function settings, a second receiver associated with the vehicle function controller; storing the vehicle function settings in a second memory associated with the vehicle function controller; and controlling a vehicle function in response to the vehicle function settings.

[0011] Further scope of applicability will become apparent from the description provided herein.The description and specific examples in this summary are intended for purposes of illustration only and are not intended to limit the scope of the present disclosure. BRIEF DESCRIPTION OF THE DRAWINGS

[0012] The drawings described herein are for illustrative purposes only of selected examples and not all possible implementations, and are not intended to limit the scope of the present disclosure.

[0013] Figure 1 is a perspective view of a vehicle configuration system according to the present disclosure.

[0014] Figure 2 is a diagrammatic block diagram of a functional control system according to the present disclosure.

[0015] Figure 3 is a diagrammatic block diagram of a programming device according to the present disclosure.

[0016] Figure 4A is an example of the initial screen of the helmet control application.

[0017] Figure 4B is the on-screen display for each helmet used to enable or disable the system.

[0018] Figure 4C It is the helmet control screen display used to activate various function settings.

[0019] Figure 4D is a screen display used to set geographic boundaries.

[0020] Figure 4E This is a screen display for setting personal characteristics.

[0021] Figure 5 is a diagrammatic block diagram of a helmet control system according to the present disclosure.

[0022] Figure 6 is a diagrammatic block diagram of a vehicle function controller.

[0023] Figure 7 is a schematic block diagram of a screen display for a vehicle function controller.

[0024] Figure 8 is a flow chart of a method for setting vehicle settings on an application for programming a device.

[0025] Fig. 9 is a flow chart of a method for operating a vehicle and transferring function settings from a helmet to a vehicle function controller.

[0026] Fig.10 is a flow chart of a method for operating with multiple helmets.

[0027] Fig.11 It is the method used to initiate pairing of the helmet with the vehicle.

[0028] Fig.12 is a detailed flow chart of the pairing method.

[0029] Corresponding reference characters indicate corresponding parts throughout the several views of the drawings. DETAILED DESCRIPTION

[0030] Example embodiments will now be described more fully with reference to the accompanying drawings. Although the following description includes several examples of motorcycle applications, it should be understood that the features herein can be applied to any suitable vehicle, such as snowmobiles, all-terrain vehicles, utility vehicles, mopeds, automobiles, scooters, etc. The examples disclosed below are not intended to be exhaustive or to limit the disclosure to the precise forms disclosed in the following detailed description. Rather, these examples are selected and described so that others skilled in the art can take advantage of their teachings.

[0031] The present disclosure provides a system that uses a helmet and electronics within the helmet to communicate function settings to a controller of a vehicle. By providing function settings and storing them within the helmet, the function settings of the vehicle can be updated and operated accordingly. A function setting is a data type that corresponds to a desired operating range for a particular function. A function setting can set a maximum or minimum value for a function (e.g., speed, radio volume). A function setting can set a geographic boundary or set a desired preset (one or more data values) for a function (e.g., radio settings, suspension pre-height).

[0032] Reference now Figure 1 , shows a vehicle 10, such as a utility vehicle, having wheels 12 and a body 14 housing a vehicle function controller 16. The vehicle function controller 16 communicates with a helmet 20. The helmet 20 includes a helmet control system 22. A programming device 30 includes an application 32 for programming limitations of functions of the vehicle 10 and transmitting data corresponding thereto to the helmet control system 22.

[0033] Reference now Figure 2, shows a diagrammatic block diagram of a vehicle function control system 50 of a vehicle 10 having a vehicle function controller 16. The vehicle function controller 16 communicates with a helmet control system 22 of a helmet 20. A programming device 30 has an application 32 for communicating with the helmet control system 22 or for enabling the programming device to communicate with the helmet control system. The programming device 30 can enable or disable interaction of the helmet with the vehicle function controller 16. Details of the communication functionality are further elaborated below.

[0034] Reference now Figure 3 , further showing the programming device 30 in detail. The programming device 30 can be a cellular phone, a tablet computer, a computer, or another type of device. The programming device 30 includes a receiver 310 and a transmitter 312, both of which can be included in a transceiver 314. That is, the receiver 310 and the transmitter 312 can be formed on a single chip and can be referred to as a transceiver 314. However, a separate receiver 310 and a separate transmitter 312 can be provided within the programming device. The receiver 310 and the transmitter can use various types of technology, including Bluetooth, Wi-Fi, short-range or long-range communication, cellular communication, etc., for communicating with the helmet and vehicle function controller. The programming device includes a controller 320. The controller 320 can be a microcomputer or a discrete circuit system. The controller 320 communicates with a memory 322 such as a solid-state device or a hard drive.

[0035] The controller 320 may also communicate with a user interface 324. The user interface 324 is used to transmit signals to the controller 320. The user interface 324 may include a series of buttons, switches, or dials, and may include a keyboard. The user interface 324 provides various types of signals for controlling function settings.

[0036] Display 326 can also communicate with controller 320. Display 326 can be a touch screen display, which also acts as a user interface. Display 326 displays various settings and queries for making these settings. In conjunction with user interface 324, various display items can be selected or adjusted, as described in more detail below. Controller 320 receives a selection signal from user interface 324 to store the control function settings in memory 322.

[0037] The controller 320 may include a restriction application 340 that may be used to generate displays and receive and transmit various menus so that different types of functional restrictions may be selected. The functional restrictions may take the form of data stored in the memory 322 .

[0038] Reference now Figure 4A, the restricted application 340 can make itself visible within the screen display 410. The screen display 410 can provide a method for securely accessing the application by requesting an identifier to be entered within a box 412. Figure 3 The illustrated user interface 324 enters the identifier. If a touch screen display is provided, the display 410 itself may be used.

[0039] Reference now Figure 4B , the system may enable each helmet using an enable box 414 or a disable box 416, two of which are illustrated, "A" and "B".

[0040] Reference now Figure 4C The helmet function setting control application can provide a user interface 420 for enabling various restrictions on operating the vehicle. The use of application 340 can disable the function settings from the helmet. Figure 3 The illustrated limit application 340 may allow various controls to be preset for the vehicle and ultimately stored within the helmet. By setting limits, parental controls may be provided. Further, adults may also benefit from the system by presetting various settings within the vehicle. In this example, the speed limit may be set via a speed limit selector 422. The speed limit selector 422 may be moved via a button within the user interface 324 or by touching a screen display on a touch screen display. Depending on the design of the system, all selectors set forth below may be changed via the user interface or by touching the touch screen display. After the user has entered a user identifier to access the control app, the user interface 420 may be displayed on the screen display.

[0041] A volume selector 424 may also be provided. The volume selector 424 may set the maximum allowable volume of the vehicle's radio or audio output.

[0042] A ride height selector 426 may also be provided. The ride height selector 426 may set the suspension preload, thereby providing a predetermined ride height for the user. Different uses of the vehicle (such as vehicle loading and different weights of passengers) may make it desirable to change the ride height according to the user's preference.

[0043] A steering force selector 428 may also be provided in the system. The steering force selector 428 may vary the amount of steering force that must be applied to the steering wheel to turn the steering wheel.

[0044] Radio preset selector 430 can provide various numbers of preset radio station frequencies that can be selected or changed. Preset selector 430 can have separate selection control buttons 432A, 432B, 432C and 432D. By touching one of these separate radio selector buttons 432A to 432D, the frequency of the radio can be preselected. In this example, button 432D is selected, and arrows 434D and 432U are provided, and these arrows correspond to the upward frequency or downward frequency selection. The frequency can be displayed in selector button 432D or adjacent to button 432.

[0045] A map setting selector 440 may also be provided within the user interface 420. The map setting selector 440 may initiate Figure 4C The screen shown. Figure 4D , a screen display 450 is illustrated with a map 452 and a geographic boundary 454 that can be moved through a user interface or by touching the display. The boundary 454 can be changed so that the vehicle can only operate within a specific geographic boundary.

[0046] Reference again Figure 4C A send button 460 may also be provided. The send button 460 may allow various settings to be transferred to the memory of the programming device 30. The send button 460 may also be used to send the function settings to the transmitter 312, where the function settings may be transmitted to the Figure 1 and Figure 2 The user interface 420 may also include a personal button 462. When the personal button is selected, a pop-up window will appear. Figure 4E The screen display shown in the user interface 470.

[0047] Reference now Figure 4E , a personal characteristics user interface 470 is provided. In this example, various personal characteristics of the rider can be set. Menu selection 472 allows the operator to select an age. Menu selection 474 allows the operator to select the height of the rider. Menu selection 476 allows the selection of the weight of the rider. Age, height, and weight can all be numeric type inputs. However, a sliding dial, button, or other type of user interface can also be used to select the appropriate age. Menu selection 478 can also allow the rider's ability to be set. Sliding dial 480 can be used to set the level from expert to beginner for a particular rider. After the personal settings are selected, button 482 can set the personal settings for a particular user. The personal settings can ultimately be transferred to the helmet for storage in the helmet and ultimately transferred to the vehicle.

[0048] Reference now Figure 5, further details of the helmet control system 22 are shown. The helmet control system 22 includes a controller 510 in communication with a memory 512. The memory 512 can be a solid-state device. The controller 510 can also be coupled to a display 514. The display 514 can be a simple indicator, such as one or more LEDs, to convey information that various functions have been performed. A power source 516, such as a battery, can also be provided within the helmet control system 22. The controller 510 can be coupled to a user interface 520. The user interface 520 can be one or more buttons, arrows, or other types of selectors for controlling the functions of the controller 510. For example, the user interface 520 can be used to change the helmet control system 22 to an active state in which the helmet control system receives function settings from an application.

[0049] The controller 510 is coupled to a receiver 530 and a transmitter 532. The receiver 530 and the transmitter 532 may be combined in a transceiver 534 as a unit. The receiver 530 may be used to receive signals from a programming device directly or over a network. The transmitter 532 may be used to transmit the function settings stored in the memory 512 to the vehicle function controller 16.

[0050] A motion sensor 536 is also in communication with the controller 510. The motion sensor 536 generates a motion signal corresponding to the movement of the helmet. The motion sensor 536 can be one of a variety of different types of sensors including piezoelectric sensors, accelerometers, etc. The motion sensor signal is transmitted to the controller 510 and, as will be described in more detail below, can initiate a pairing process between the helmet and the vehicle.

[0051] Reference now Figure 6 , further details of the vehicle function controller 16 are shown. The vehicle function controller 16 may include a controller 610 in communication with a memory 612 for storing various function settings therein. The controller 610 may be a microprocessor, an integrated circuit, or a discrete circuit. The function settings may be saved until they are changed by a Figure 1 , Figure 2 and Figure 5 The controller 610 can communicate with the display 614. The display 614 can be used to display various RIDE Functions for users to choose. The system can be used as a vehicle function controller. The system has various capabilities enhanced by this example. Function settings can set the maximum or minimum settings of various types of functions. As long as the selected function is between the maximum setting and the minimum setting, the various function settings can be adjusted using the display or user interface 616. The controller 610 can also communicate with a controller area network (CAN) interface 618. The controller area network interface 618 can be used to transmit signals to various vehicle systems, such as suspension systems, steering systems, braking systems, etc. The display 614 can also provide an indicator to warn the vehicle operator that they are trying to operate outside of various parameters.

[0052] The vehicle function controller 16 may incorporate therein the functionality of the programming device 30 and the application 32. In this manner, the programming device 30 may be integrated with the function controller 16 and may be displayed via the display 614. The system may incorporate an application 32. Of course, the application 32 for changing settings may be password protected to prevent unauthorized changes (eg, parental controls).

[0053] The power source 620 can be used to power the vehicle function controller. The power source 620 can be a vehicle battery.

[0054] The controller 610 may also communicate with a receiver 630, a transmitter 632, both of which may be incorporated into a transceiver 634. When the helmet approaches the vehicle, the receiver may be used to receive a signal from the helmet control system 22. The system may be activated by a key or a proximity sensor 640 coupled to the controller 610. That is, the controller 610 may provide a low-power beacon signal through the receiver 630 to sense the proximity of the helmet control system 22, which in turn may generate a response signal, thereby providing the function settings to the controller 610, and ultimately storing them in the memory 612. The vehicle may be subject to start restrictions or may achieve a lower top speed. The proximity sensor 640 may also generate a signal to identify that the helmet is within a certain proximity of the system. The proximity sensor 640 may be, for example, a motion sensor to detect movement near the vehicle or within the passenger compartment of the vehicle, which in turn activates the controller 610 to power the receiver 630 to receive the function settings. The proximity sensor 640 may also be a key or button that is pressed to turn on the vehicle. This indicates that the vehicle operator is in the vehicle and is therefore close to the proximity sensor 640.

[0055] A lock module 642 may also be included in the vehicle function controller. The lock module 642 does not allow the vehicle to start unless a properly authorized helmet is provided. The helmet transmits the identifier to the vehicle function controller, and thus the lock function may be disabled when the helmet is in a position close to the vehicle or in a riding position in the vehicle.

[0056] A global positioning system receiver (GPS) 650 transmits the global position to the controller 610. The global position signal from the global positioning system 650 corresponds to the coordinate position of the vehicle.

[0057] A pairing module 654 is coupled to the controller 610. The pairing module 654 controls the pairing process of the helmet with the vehicle according to the method set forth below. In particular, the pairing module 654, together with various inputs from the vehicle controller and the helmet, allows the helmet and vehicle to communicate through their respective transmitters / receivers. The timer 666 is used to time various functions, such as timeout functions or functions such as tracking the amount of time since the vehicle was ignited.

[0058] The ignition module 668 generates an ignition signal corresponding to the start or opening of the vehicle. The ignition module 668 may generate the ignition signal, for example, in response to a key being turned to an ignition switch. The ignition module 668 may also communicate with a push-button type system that generates the ignition signal in response to the pressing of a button. The timer 666 may be used to time the time since the ignition module 668 was activated and generated the ignition signal.

[0059] Reference now Figure 7 , in one example, illustrates a display 614 of a vehicle feature controller. The display 614 may display or indicate that various features have been activated. In this example, a helmet beacon enabled indicator 710 shows that a helmet beacon has been transmitted by the vehicle feature controller. A helmet battery level indicator 712 may indicate the battery level of the helmet by a word descriptor or by an indicator 714 indicating whether the battery is full or not full. A status indicator 716 may be used to indicate the status of various features of the system. A notification indicator 718 may indicate that a notification is being received from the helmet control system 22. RIDE Indicator 720 may be used to indicate RIDE The vehicle may be subject to various functional limitations. Starting may be completely locked out without an authorized helmet. Speed ​​limit indicator 722 may be activated or illuminated when the speed of the vehicle has reached a commanded setting. Radio volume limit indicator 724 may be illuminated or activated when an attempt is made to set the radio volume beyond a preset functional setting. Operating time limit indicator 726 may provide an indicator of the amount of time or time of day that has exceeded the vehicle's operating hours of the day. Geographic indicator 728 may indicate that a geographic boundary of the vehicle may have been exceeded. This may be indicated by, for example, Figure 6 The described operation of the vehicle's GPS 650 is performed.

[0060] When the display 614 is a touch screen display, the display 614 can be used as a user interface as described above. The confirmation indicator 730 can be illuminated to allow the vehicle operator to confirm the pairing of the vehicle with the helmet. The confirmation indicator 730 can display language such as "Confirming pairing with XYZ helmet." "XYZ" refers to the identifier of the helmet. The identifier can be a name or other alphanumeric identifier. When pairing is desired, the user operator can select the confirmation indicator 730, and the helmet and vehicle will be able to transmit various signals between them. After the helmet and vehicle are paired, the confirmation indicator 730 can continue to be illuminated, change its language, or disappear.

[0061] Reference now Figure 8 , describes a method for operating a system between a programming device 30 and a helmet 20. In this example, in step 810, a helmet control application is selected on the programming device. This can be selected by clicking on an icon, selecting an icon from a screen, or interacting with a user interface such as a directional pad and a selection button. In step 812, an identifier identifying a user of the application can be proposed. The identifier can be entered once and saved within the user device.

[0062] In step 814, a vehicle may be selected from the user interface. That is, multiple vehicles may be associated with a single user. In step 816, a user may be selected. Multiple users may also be associated with a particular account. For example, the owner of a vehicle may have desired settings for children, a spouse, and friends. In step 818, multiple helmets may also be associated with a single account. In this step, the desired helmet to be programmed may be selected. Following step 820, disable / enable functions may be performed for the helmet or user. If disable is selected, previously stored functions of the helmet may be deleted. In step 820, if enable is selected, step 824 is performed. In step 824, the above-described FIG. 4A to FIG. 4C The user interface shown is used to select various functions. In step 826, the previous function settings can be recalled. The function settings can be recalled from an application or memory associated with the programming device or by connecting to the helmet in step 822.

[0063] In step 830, it may be desirable to restrict various functions. A function interface may be displayed. The function interface may change depending on the user or user type. For example, children of different ages may have different types of function restrictions. For other adult users, other types of functions may be set.

[0064] In step 832, a user interface associated with the programming device is used to adjust or set the function settings to form an updated function setting. In step 834, the updated function settings are stored in the application and / or helmet memory. As described above, a store button can be selected to store the settings in the programming device and / or the helmet, or both.

[0065] Reference now Fig. 9 , a method for transmitting function settings to a vehicle is described. In step 900, it is determined whether the helmet is close to the vehicle. As described above, the proximity sensor can detect the proximity of the helmet to the vehicle. The proximity can also be determined when a key is activated in the ignition of the vehicle.

[0066] In its simplest form, when a helmet approaches a vehicle, step 902 may enable the vehicle to be started. The helmet transmits an identifier to the vehicle controller. The identifier may identify the helmet as one that is allowed to be started. The vehicle controller may also identify the identifier as being authorized. Thus, the vehicle will not start unless the helmet / identifier is authorized. That is, when a helmet without the identifier is not present, step 904 may prohibit the vehicle from starting. Alternatively, starting may be allowed, but a very low maximum speed may be set to allow the vehicle to move. In step 906, a warning that a helmet is not present may be displayed, and the vehicle will not start unless a helmet is present. Following step 900, step 912 initiates communication between the helmet and the vehicle function controller 16. This may be done via an RF interface, Or the secure access interface transfers the function settings stored in the helmet to the vehicle.

[0067] In step 916, the function settings can be stored in the vehicle. That is, the function settings from the helmet can be stored in the memory of the vehicle function controller 16.

[0068] In step 918 , the function settings are transmitted to the vehicle. Figure 6 The controllers shown may control the various functions, or these functions may be communicated through the controller area network 618 to various other controllers that control functions such as a power steering unit, a ride height controller, or other types of controllers or functions described above.

[0069] In step 920, the function settings can be Figure 6 The screen shown is displayed in the display.

[0070] In step 922, it is determined whether the function setting has been adjusted or is operating out of range. If the function setting is operating out of range or attempting to operate the vehicle out of range, step 924 will limit the system to operate using the function setting to limit the operation of the vehicle. In step 922, the vehicle is operated according to the function setting when the system is operating within range, or according to the operation of the vehicle as long as the vehicle is operating within the limits of the function setting.

[0071] Reference now Fig.10 , i.e., a method for operating a vehicle when multiple helmets are detected. In step 1010, the system detects multiple helmets. In step 1012, communication between the helmet and the vehicle is initiated for all nearby helmets. In step 1014, the function settings of each helmet are transmitted to the vehicle controller. In step 1016, the functions are adjusted to one or more functions that are the most stringent or the safest. In step 1018, the vehicle is operated with the most stringent functions.

[0072] Reference now Fig.11, a method for initiating pairing of a helmet with a vehicle is described. Although a "helmet" and a "vehicle" are described, pairing is performed between a transceiver of the vehicle and a transceiver of the helmet. In step 1110, movement of the helmet is detected at a controller of the helmet control system. The movement is detected by a movement sensor that generates a movement signal. In step 1110, if no movement is detected, the system repeats at step 1110. In step 1110, if movement is detected in response to the movement signal, step 1112 is performed. Step 1112 determines whether the helmet is unpaired. When the helmet is not unpaired, that is, the helmet is paired, step 1110 is performed again. In step 1112, if the helmet is unpaired, step 1114 is performed. In step 1114, a pairing request signal is transmitted from the transceiver of the vehicle. The pairing request signal may include information such as an identifier of the helmet. Other types of communication data may also be included, such as communication frequency, keys used for communication, encryption schemes, etc. After step 1114, step 1116 determines whether the ignition of the vehicle is started. As described above, the ignition is activated by means such as turning a key cylinder or pressing a button to start the vehicle when the vehicle is started and an ignition signal is generated. In step 1116, it is determined whether the ignition has been activated. If the ignition has not been activated, step 1110 is performed again. When the ignition has been activated, step 1118 starts a pairing timer corresponding to a maximum time allowed for the system to perform pairing. The pairing timer can be a countdown timer or a limit set for the amount of time the vehicle "looks" for a pairing request signal. In step 1120, the receiver of the vehicle transceiver is monitored for a pairing request signal. When a pairing signal is not received in step 1122, step 1124 determines whether the time has exceeded, such as when the time exceeds a threshold. The time corresponds to the start of the timer of step 1118. When the time threshold has not been exceeded, steps 1120 and 1122 are repeated again.

[0073] Referring back to step 1122, when the pairing signal is received, step 1126 generates a screen display at the user interface, such as Figure 7 A confirmation indicator 730 is shown. In step 1128, the user may interact with the user interface, and a confirmation signal may be generated on the user interface in step 1128. After the confirmation signal is generated on the user interface, the confirmation signal is transmitted to the controller 610 of the vehicle. In step 1130, the helmet is paired with the vehicle. That is, as described above, the helmet transceiver is able to communicate with the vehicle transceiver. Fig.12 Describes the details of the pairing process.

[0074] After step 1130, step 1132 allows the transmission of communication signals between the helmet and the vehicle. After step 1124 and after step 1132, the process ends in step 1134.

[0075] Reference now Fig.12 , setting forth details of the pairing process. In step 1210, a first signal, such as a pairing request signal, is transmitted from the helmet, such as in response to movement of the helmet as described above. The first signal may have an identifier key and transmit various parameters, such as a frequency, a key, or other type of encoded or encrypted data. The first parameters allow the helmet transceiver to communicate with the vehicle transceiver. In step 1212, the first signal is received at the transceiver of the vehicle. In particular, a receiver portion of the transceiver receives the first signal and the parameters therein. The transceiver "looks for" a signal, such as Fig.11 As described. In step 1214, a response signal having a second communication signal parameter is generated to the helmet. The second communication parameter may include a confirmation signal, an enable signal, and other parameters for intercommunication between the vehicle and the helmet. Passwords or digital keys may be exchanged via the first communication signal and the second communication signal. Once the communication signals are exchanged, a communication system is established in step 1216. This is called pairing, which allows the vehicles to exchange signals. For example, the helmet may transmit a preset for the vehicle. The vehicle may transmit various data from the vehicle to the helmet. In step 1218, the second communication parameter is stored in the helmet. In step 1220, the first communication parameter is stored in the vehicle. In step 1222, various other types of signals are transmitted between the helmet and the vehicle. More specifically, various types of data signals may be exchanged between the transceiver of the helmet and the transceiver of the vehicle.

[0076] The foregoing description has been provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements and features of a specific example are generally not limited to that specific example, but are interchangeable when applicable and can be used in selected examples even if not explicitly shown or described. It can also be varied in a variety of ways. Such variations are not considered to be departures from the present disclosure, and all such modifications are intended to be included within the scope of the present disclosure.

Claims

1. A system for operating a vehicle function, comprising: A programming device, including an application capable of programming a vehicle function setting of a vehicle according to a specific vehicle user to obtain a customized vehicle function setting, The programming device comprises a first transmitter, via which the customized vehicle function settings are stored to a helmet associated with the specific vehicle user and transmitted to a vehicle receiver of the vehicle via a second transmitter of the helmet, The customized vehicle function settings are transmitted to a vehicle controller via a vehicle receiver of the vehicle, When the controller receives a helmet identifier from the second transmitter via the vehicle receiver, the controller operates the vehicle function according to the customized vehicle function setting; wherein the second transmitter sends the helmet identifier in response to a helmet movement signal, and the helmet movement signal is generated at the helmet in response to sensing movement of the helmet.

2. The system according to claim 1, wherein: The first transmitter communicates using one of Bluetooth, Wi-Fi, short-range or long-range communication, and cellular communication.

3. The system according to claim 1, wherein: The receiver comprises Receiver.

4. The system according to claim 1, wherein: The vehicle function setting limits operation of the vehicle based on the identifier.

5. The system according to claim 1, wherein: The vehicle function settings include disabling starting of the vehicle.

6. The system according to claim 1, wherein: The vehicle function settings also include at least one of a maximum speed setting, a radio volume setting, and a geographic setting.

7. The system according to claim 1, wherein: The vehicle includes a first display that displays settings of vehicle functions.

8. The system according to claim 7, wherein: The programming device includes a second display that displays a plurality of selectors for changing settings of the vehicle functions.

9. The system according to claim 8, wherein: The plurality of selectors includes at least one of a speed limit selector, a radio volume selector, a ride height selector, a radio preset selector, a map setting selector, and a steering effort selector.

10. The system of claim 1 further comprising a proximity sensor that generates a proximity signal, the vehicle controller powering the vehicle receiver in response to the proximity signal.

11. The system according to claim 10, wherein: The proximity sensor includes a key or a button.

12. A method for operating a vehicle function, comprising: For a specific vehicle user, programming the vehicle function settings of the vehicle using a programming device to obtain customized vehicle function settings; storing the customized vehicle function settings to the helmet via a first transmitter of the programming device and transmitting the customized vehicle function settings to the vehicle using a second transmitter of the helmet; receiving the customized vehicle function settings at a vehicle receiver disposed within the vehicle; generating a helmet movement signal at the helmet in response to sensing movement of the helmet, transmitting a helmet identifier by a second transmitter of the helmet and via the receiver to the vehicle controller in response to the helmet movement signal; and Vehicle functions are controlled in response to the customized vehicle function settings.

13. The method of claim 12, further comprising limiting operation of the vehicle in response to the helmet identifier and the vehicle function setting.

14. The method according to claim 12, wherein: Controlling the vehicle includes disabling starting of the vehicle based on the vehicle function setting.

15. The method according to claim 12, wherein: The controlling includes limiting at least one of a maximum speed setting, a radio volume setting, and a geographic setting. 16 . The method of claim 12 , further comprising generating a proximity signal at a proximity sensor, and powering the vehicle receiver in response to the proximity signal.

17. The method according to claim 16, wherein: Generating the proximity signal includes pressing a key or button.

18. The method according to claim 12, wherein: The programming device includes a second display that displays a plurality of selectors for changing the vehicle function settings, wherein the plurality of selectors include at least one of a speed limit selector, a radio volume selector, a ride height selector, a radio preset selector, a map setting selector, and a steering effort selector.

19. The method of claim 12, further comprising storing a functional setting in the helmet and transmitting the functional setting to the vehicle receiver.

Images