GOLF VEHICLE WITH ADAPTIVE PERSONS WITH DISABILITY MODE

Description

BACKGROUND

Historically, golf has been an inclusive sport. Courses are designed with multiple tee options and distances allowing players of varying skill levels and ages participate. Golf vehicles, however, do not accommodate all players, making it difficult for some to participate and engage in the sport. Golf vehicles, for example, do not provide accommodations for persons with various disabilities or other unique qualities or characteristics of a person that may limit their participation. In addition, systems and methods to configure the golf vehicles uniquely for each operator, driver, or passenger while they participate are absent from golf vehicle fleets available.

SUMMARY

One embodiment relates to a golf vehicle system for configuring a golf vehicle. The golf vehicle system includes one or more memory devices having instructions stored thereon. The instructions, when executed by one or more processors, cause the one or more processors to perform operations. The operations include acquiring a user profile associated with a user of the golf vehicle where the user profile includes a user attribute and adjusting a setting of the golf vehicle from a default setting to an adjusted setting based on the user attribute. Players with disabilities Another embodiment relates to a golf vehicle system for enhancing an experience of a user having a disability with a golf vehicle. The golf vehicle system includes one or more memory devices having instructions stored thereon. The instructions, when executed by one or more processors, cause the one or more processors to perform operations. The operations include acquiring an indication of the disability of the user and performing an adjustment to a setting of the golf vehicle based on the indication. The adjustment facilitates improved accommodation of the user having the disability.

Still another embodiment relates to a golf vehicle system for enhancing an experience of a user having a disability with a golf vehicle. The golf vehicle system includes the golf vehicle and one or more memory devices having instructions stored thereon. The golf vehicle includes a steering wheel, a brake pedal, an accelerator pedal, a display, and a speaker. The instructions, when executed by one or more processors, cause the one or more processors to perform operations. The operations include performing an adjustment to functionality of at least one of the steering wheel, the brake pedal, the accelerator pedal, the display, or the speaker of the golf vehicle based on an indication of the disability of the user. The adjustment facilitates improved accommodation of the user having the disability.

This summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the devices or processes described herein will become apparent in the detailed description set forth herein, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a perspective view of a vehicle, according to an exemplary embodiment.

FIG. 2 is a schematic block diagram of the vehicle of FIG. 1, according to an exemplary embodiment.

FIG. 3 is a schematic block diagram of a fleet monitoring and control system including a plurality of the vehicles of FIG. 1, according to an exemplary embodiment.

FIG. 4 is another schematic block diagram of the fleet monitoring and control system of FIG. 3 including the vehicle of FIG. 1 and a user configuration system providing user profiles, according to an exemplary embodiment.

FIG. 5 is a table indicating attributes and the respective settings that the attribute may affect if transmitted to the vehicle, according to an exemplary embodiment.

FIG. 6 is a flow of operations for adjusting a setting based on an attribute in a user profile, according to an exemplary embodiment.

FIG. 7 is flow of operations for improving vehicle accommodations for a person with a disability by adjusting settings of the vehicle based on an indication of a disability of the user, according to an exemplary embodiment.

FIG. 8 is flow of operations for acquiring, by the vehicle, a user profile, attribute, setting, or an indication of a disability of a user, according to some embodiments.

FIG. 9 is a flow of operations for emitting an alert, message, or notification from a speaker of a vehicle based on persons with disabilities modes, according to some embodiments.

DETAILED DESCRIPTION

Before turning to the figures, which illustrate certain exemplary embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the figures. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.

Overall Vehicle

As shown in FIGS. 1 and 2, a machine or vehicle, shown as vehicle 10, includes a chassis, shown as frame 12; a body assembly, shown as body 20, coupled to the frame 12 and having an occupant portion or section, shown as occupant seating area 30; operator input and output devices, shown as operator controls 40, that are disposed within the occupant seating area 30; a drivetrain, shown as driveline 50, coupled to the frame 12 and at least partially disposed under the body 20; a vehicle suspension system, shown as suspension system 60, coupled to the frame 12 and one or more components of the driveline 50; a vehicle braking system, shown as braking system 70, coupled to one or more components of the driveline 50 to facilitate selectively braking the one or more components of the driveline 50; one or more first sensors, shown as sensors 90; and a control system, shown as vehicle control system 100, coupled to the operator controls 40, the driveline 50, the suspension system 60, the braking system 70, and the sensors 90. In some embodiments, the vehicle 10 includes more or fewer components.

According to an exemplary embodiment, the vehicle 10 is an off-road machine or vehicle. In some embodiments, the off-road machine or vehicle is a lightweight or recreational machine or vehicle such as a golf cart, an all-terrain vehicle (“ATV”), a utility task vehicle (“UTV”), a low speed vehicle (“LSV”), a personal transport vehicle (“PTV”), and/or another type of lightweight or recreational machine or vehicle. In some embodiments, the off-road machine or vehicle is a chore product such as a lawnmower, a turf mower, a push mower, a ride-on mower, a stand-on mower, aerator, turf sprayers, bunker rake, and/or another type of chore product (e.g., that may be used on a golf course).

According to the exemplary embodiment shown in FIG. 1, the occupant seating area 30 includes a plurality of rows of seating including a first row of seating, shown as front row seating 32, and a second row of seating, shown as rear row seating 34. In some embodiments, the occupant seating area 30 includes a third row of seating or intermediate/middle row seating positioned between the front row seating 32 and the rear row seating 34. According to the exemplary embodiment shown in FIG. 1, the rear row seating 34 is facing forward. In some embodiments, the rear row seating 34 is facing rearward. In some embodiments, the occupant seating area 30 does not include the rear row seating 34. In some embodiments, in addition to or in place of the rear row seating 34, the vehicle 10 includes one or more rear accessories. Such rear accessories may include a golf bag rack, a bed, a cargo body (e.g., for a drink cart), and/or other rear accessories.

According to an exemplary embodiment, the operator controls 40 are configured to provide an operator with the ability to control one or more functions of and/or provide commands to the vehicle 10 and the components thereof (e.g., turn on, turn off, drive, turn, brake, engage various operating modes, raise/lower an implement, etc.). As shown in FIGS. 1 and 2, the operator controls 40 include a steering interface (e.g., a steering wheel, joystick(s), etc.), shown steering wheel 42, an accelerator interface (e.g., a pedal, a throttle, etc.), shown as accelerator 44, a braking interface (e.g., a pedal), shown as brake 46, and one or more additional interfaces, shown as operator interface 48. The operator interface 48 may include one or more displays and one or more input devices. The one or more displays may be or include a touchscreen, a LCD display, a LED display, a speedometer, gauges, warning lights, etc. The one or more input device may be or include buttons, switches, knobs, levers, dials, etc.

According to an exemplary embodiment, the driveline 50 is configured to propel the vehicle 10. As shown in FIGS. 1 and 2, the driveline 50 includes a primary driver, shown as prime mover 52, an energy storage device, shown as energy storage 54, a first tractive assembly (e.g., axles, wheels, tracks, differentials, etc.), shown as rear tractive assembly 56, and a second tractive assembly (e.g., axles, wheels, tracks, differentials, etc.), shown as front tractive assembly 58. In some embodiments, the driveline 50 is a conventional driveline whereby the prime mover 52 is an internal combustion engine and the energy storage 54 is a fuel tank. The internal combustion engine may be a spark-ignition internal combustion engine or a compression-ignition internal combustion engine that may use any suitable fuel type (e.g., diesel, ethanol, gasoline, natural gas, propane, etc.). In some embodiments, the driveline 50 is an electric driveline whereby the prime mover 52 is an electric motor and the energy storage 54 is a battery system.

In some embodiments, the driveline 50 is a fuel cell electric driveline whereby the prime mover 52 is an electric motor and the energy storage 54 is a fuel cell (e.g., that stores hydrogen, that produces electricity from the hydrogen, etc.). In some embodiments, the driveline 50 is a hybrid driveline whereby (i) the prime mover 52 includes an internal combustion engine and an electric motor/generator and (ii) the energy storage 54 includes a fuel tank and/or a battery system.

According to the exemplary embodiment shown in FIG. 1, the rear tractive assembly 56 includes rear tractive elements and the front tractive assembly 58 includes front tractive elements that are configured as wheels. In some embodiments, the rear tractive elements and/or the front tractive elements are configured as tracks.

According to an exemplary embodiment, the prime mover 52 is configured to provide power to drive the rear tractive assembly 56 and/or the front tractive assembly 58 (e.g., to provide front-wheel drive, rear-wheel drive, four-wheel drive, and/or all-wheel drive operations). In some embodiments, the driveline 50 includes a transmission device (e.g., a gearbox, a continuous variable transmission (“CVT”), etc.) positioned between (a) the prime mover 52 and (b) the rear tractive assembly 56 and/or the front tractive assembly 58. The rear tractive assembly 56 and/or the front tractive assembly 58 may include a drive shaft, a differential, and/or an axle. In some embodiments, the rear tractive assembly 56 and/or the front tractive assembly 58 include two axles or a tandem axle arrangement. In some embodiments, the rear tractive assembly 56 and/or the front tractive assembly 58 are steerable (e.g., using the steering wheel 42). In some embodiments, both the rear tractive assembly 56 and the front tractive assembly 58 are fixed and not steerable (e.g., employ skid steer operations).

In some embodiments, the driveline 50 includes a plurality of prime movers 52. By way of example, the driveline 50 may include a first prime mover 52 that drives the rear tractive assembly 56 and a second prime mover 52 that drives the front tractive assembly 58. By way of another example, the driveline 50 may include a first prime mover 52 that drives a first one of the front tractive elements, a second prime mover 52 that drives a second one of the front tractive elements, a third prime mover 52 that drives a first one of the rear tractive elements, and/or a fourth prime mover 52 that drives a second one of the rear tractive elements. By way of still another example, the driveline 50 may include a first prime mover 52 that drives the front tractive assembly 58, a second prime mover 52 that drives a first one of the rear tractive elements, and a third prime mover 52 that drives a second one of the rear tractive elements. By way of yet another example, the driveline 50 may include a first prime mover 52 that drives the rear tractive assembly 56, a second prime mover 52 that drives a first one of the front tractive elements, and a third prime mover 52 that drives a second one of the front tractive elements.

According to an exemplary embodiment, the suspension system 60 includes one or more suspension components (e.g., shocks, dampers, springs, etc.) positioned between the frame 12 and one or more components (e.g., tractive elements, axles, etc.) of the rear tractive assembly 56 and/or the front tractive assembly 58. In some embodiments, the vehicle 10 does not include the suspension system 60.

According to an exemplary embodiment, the braking system 70 includes one or more braking components (e.g., disc brakes, drum brakes, in-board brakes, axle brakes, etc.) positioned to facilitate selectively braking one or more components of the driveline 50. In some embodiments, the one or more braking components include (i) one or more front braking components positioned to facilitate braking one or more components of the front tractive assembly 58 (e.g., the front axle, the front tractive elements, etc.) and (ii) one or more rear braking components positioned to facilitate braking one or more components of the rear tractive assembly 56 (e.g., the rear axle, the rear tractive elements, etc.). In some embodiments, the one or more braking components include only the one or more front braking components. In some embodiments, the one or more braking components include only the one or more rear braking components. In some embodiments, the one or more front braking components include two front braking components, one positioned to facilitate braking each of the front tractive elements. In some embodiments, the one or more rear braking components include two rear braking components, one positioned to facilitate braking each of the rear tractive elements. In some embodiments, electric regenerative braking is employed (e.g., via the prime mover 52, an electric motor, etc.) in combination with or instead of using the braking system 70 to facilitate braking of one or more components of the driveline 50.

The sensors 90 may include various sensors positioned about the vehicle 10 to acquire vehicle information or vehicle data regarding operation of the vehicle 10 and/or the location thereof. By way of example, the sensors 90 may include an accelerometer, a gyroscope, a compass, a position sensor (e.g., a GPS sensor, etc.), an inertial measurement unit (“IMU”), suspension sensor(s), wheel sensors, an audio sensor or microphone, a camera, an optical sensor, a proximity detection sensor, a Doppler sensor, and/or other sensors to facilitate acquiring vehicle information or vehicle data regarding operation of the vehicle 10 and/or the location thereof. According to an exemplary embodiment, one or more of the sensors 90 are configured to facilitate detecting and obtaining vehicle telemetry data including position of the vehicle 10, whether the vehicle 10 is moving, travel direction of the vehicle 10, slope of the vehicle 10, speed of the vehicle 10, vibrations experienced by the vehicle 10, sounds proximate the vehicle 10, suspension travel of components of the suspension system 60, and/or other vehicle telemetry data.

The vehicle control system 100 may be implemented as a general-purpose processor, an application specific integrated circuit (“ASIC”), one or more field programmable gate arrays (“FPGAs”), a digital-signal-processor (“DSP”), circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. According to the exemplary embodiment shown in FIG. 2, the vehicle control system 100 includes a processing circuit 102, a memory 104, and a communications interface 106. The processing circuit 102 may include an ASIC, one or more FPGAs, a DSP, circuits containing one or more processing components, circuitry for supporting a microprocessor, a group of processing components, or other suitable electronic processing components. In some embodiments, the processing circuit 102 is configured to execute computer code stored in the memory 104 to facilitate the activities described herein. The memory 104 may be any volatile or non-volatile or non-transitory computer-readable storage medium capable of storing data or computer code relating to the activities described herein.

According to an exemplary embodiment, the memory 104 includes computer code modules (e.g., executable code, object code, source code, script code, machine code, etc.) configured for execution by the processing circuit 102. In some embodiments, the vehicle control system 100 may represent a collection of processing devices. In such cases, the processing circuit 102 represents the collective processors of the devices, and the memory 104 represents the collective storage devices of the devices.

In one embodiment, the vehicle control system 100 is configured to selectively engage, selectively disengage, control, or otherwise communicate with components of the vehicle 10 (e.g., via the communications interface 106, a controller area network (“CAN”) bus, etc.).

According to an exemplary embodiment, the vehicle control system 100 is coupled to (e.g., communicably coupled to) components of the operator controls 40 (e.g., the steering wheel 42, the accelerator 44, the brake 46, the operator interface 48, etc.), components of the driveline 50 (e.g., the prime mover 52), components of the braking system 70, and the sensors 90. By way of example, the vehicle control system 100 may send and receive signals (e.g., control signals, location signals, etc.) with the components of the operator controls 40, the components of the driveline 50, the components of the braking system 70, the sensors 90, and/or remote systems or devices (via the communications interface 106 as described in greater detail herein).

Fleet Monitoring and Control System

As shown in FIG. 3, a monitoring and control system, shown as fleet monitoring and control system 200, includes one or more vehicles 10; one or more second sensors, shown as user sensors 220, positioned remote or separate from the vehicles 10; an operator interface, shown as user portal 230, positioned remote or separate from the vehicles 10; an external or remote user device, shown as user device 232, positioned remote or separate from the vehicles 10; and one or more external processing systems, shown as remote systems 240, positioned remote or separate from the vehicles 10. The vehicles 10, the user sensors 220, the user portal 230, and the remote systems 240 communicate via one or more communications protocols (e.g., Bluetooth, Wi-Fi, cellular, radio, through the Internet, etc.) through a network, shown as communications network 210. In some embodiments, the fleet monitoring and control system 200 does not includes the user portal 230 and/or the user device 232.

The user sensors 220 may be or include one or more sensors that are carried by or worn by an operator of one of the vehicles 10. By way of example, the user sensors 220 may be or include a wearable sensor (e.g., a smartwatch, a fitness tracker, a pedometer, a heart rate monitor, etc.) and/or a sensor that is otherwise carried by the operator (e.g., a smartphone, etc.) that facilitates acquiring and monitoring operator data (e.g., physiological conditions such a temperature, heartrate, breathing patterns, etc. ; location; movement; etc.) regarding the operator. The user sensors 220 may communicate directly with the vehicles 10, directly with the remote systems 240, and/or indirectly with the remote systems 240 (e.g., through the vehicles 10 as an intermediary).

The user portal 230 may be configured to facilitate operator access to dashboards including the vehicle data, the operator data, information available at the remote systems 240, etc. to manage and operate the site (e.g., golf course) such as for advanced scheduling purposes, to identify persons breaking course guidelines or rules, to monitor locations of the vehicles 10, etc. The user portal 230 may also be configured to facilitate operator implementation of configurations and/or parameters for the vehicles 10 and/or the site (e.g., setting speed limits, setting geofences, etc.). As shown in FIG. 3, the user portal 230 is accessible via the user device 232. The user device 232 may be or include a computer, laptop, smartphone, tablet, or the like. The user portal 230 and the user device 232 may communicate via one or more communications protocols (e.g., Bluetooth, Wi-Fi, cellular, radio, through the Internet, wired connection, etc.) through a network (e.g., a CAN bus, the communications network 210, etc.). The user device 232 includes a display (e.g., a screen, etc.) configured to display one or more graphical user interfaces (“GUIs”) of the user portal 230.

As shown in FIG. 3, the remote systems 240 include a first remote system, shown as off-site server 250, and a second remote system, shown as on-site system 260 (e.g., in a clubhouse of a golf course, on the golf course, etc.). In some embodiments, the remote systems 240 include only one of the off-site server 250 or the on-site system 260. As shown in FIG. 3, (a) the off-site server 250 includes a processing circuit 252, a memory 254, and a communications interface 256 and (b) the on-site system 260 includes a processing circuit 262, a memory 264, and a communications interface 266.

According to an exemplary embodiment, the remote systems 240 (e.g., the off-site server 250 and/or the on-site system 260) are configured to communicate with the vehicles 10 and/or the user sensors 220 via the communications network 210. By way of example, the remote systems 240 may receive the vehicle data from the vehicles 10 and/or the operator data from the user sensors 220. The remote systems 240 may be configured to perform back-end processing of the vehicle data and/or the operator data. The remote systems 240 may be configured to monitor various global positioning system (“GPS”) information and/or real-time kinematics (“RTK”) information (e.g., position/location, speed, direction of travel, geofence related information, etc.) regarding the vehicles 10 and/or the user sensors 220. The remote systems 240 may be configured to transmit information, data, commands, and/or instructions to the vehicles 10. By way of example, the remote systems 240 may be configured to transmit GPS data and/or RTK data based on the GPS information and/or RTK information to the vehicles 10 (e.g., which the vehicle control systems 100 may use to make control decisions). By way of another example, the remote systems 240 may send commands or instructions to the vehicles 10 to implement.

According to an exemplary embodiment, the remote systems 240 (e.g., the off-site server 250 and/or the on-site system 260) are configured to communicate with the user portal 230 via the communications network 210. By way of example, the user portal 230 may facilitate (a) accessing the remote systems 240 to access data regarding the vehicles 10 and/or the operators thereof and/or (b) configuring or setting operating parameters for the vehicles 10 (e.g., geofences, speed limits, times of use, permitted operators, etc.). Such operating parameters may be propagated to the vehicles 10 by the remote systems 240 (e.g., as updates to settings) and/or used for real time control of the vehicles 10 by the remote systems 240.

User Profiles and Persons With Disability Mode

FIG. 4 shows the fleet monitoring and control system 200. According to an exemplary embodiment, the fleet monitoring and control system 200 is configured to update the settings of a vehicle 10 based on user profiles associated with the vehicle 10 using a configurator, shown as user configuration system 300. In some embodiments, the remote systems 240 include the user configuration system 300. By way of example, the user configuration system 300 may be implemented by the off-site server 250 and/or the on-site system 260. In some embodiments, the vehicle control system 100 is configured to include the user configuration system 300. In some embodiments, any of the features, components, or instructions included in the user configuration system 300 may be distributed across the vehicle control system 100, the on-site system 260, the off-site server 250, or any off-vehicle system included in the remote systems 240.

As shown in FIG. 4, the user configuration system 300 is communicably connected (e.g., via communications network 210) to one or more user devices 232 and one or more vehicles 10. According to some embodiments, the general configuration of the user configuration system 300 is to acquire attributes related to the users of the vehicle 10 (e.g., age, preferences, presence of any disability, etc.), configure a user profile with the attributes, associate one or more user profiles with the vehicle 10, and communicate, to the vehicle 10, the settings related to the attributes within the user profile. In some embodiments, the user profile may be communicated to the vehicle 10, the attributes may be delivered to the vehicle 10, or the settings may be delivered to the vehicle 10 depending on how the functionality of the user configuration system 300 is distributed between the vehicle 10 and the remote systems 240. In some embodiments, the user configuration system 300 is configured to receive user profiles, attributes and/or settings from the one or more user devices 232. For example, the user configuration system 300 may provide a web application programming interface (“API”) that allows a user to associate a user profile with the vehicle 10, associate an attribute with a user profile, etc.

As shown in FIG. 4, the vehicle 10 includes a settings manager 110, a setting storage 112, a profile storage 114, user attribute definitions 116, and a role identifier 118. In some embodiments, the setting storage 112 is configured to maintain (e.g., store, save, etc.) the settings of the vehicle 10. The vehicle settings may be configured to include a default setting (e.g., after resetting the vehicle control system 100, if no user profile is associated with the vehicle 10, etc.). The setting storage 112 may be configured to communicate the settings to the respective components, controls, modules, and/or systems of the vehicle 10. For example, the setting storage 112 may communicate a sensitivity to the braking system 70 or the brake 46 of the operator controls 40 based on a stored pedal sensitivity value. As another example, the setting storage 112 may communicate a color palette to the operator interface 48 that has been applied to accommodate colorblindness.

In some embodiments, the settings manager 110 is configured to adjust (e.g., change, modify, etc.) the setting storage 112 of the vehicle 10. The settings manager 110 may be configured to provide callback functions or other programming interfaces to the operator interface 48. The callback functions may provide the user with the ability to directly adjust the settings of the vehicle 10 using a menu on the operator interface 48. In some embodiments, the settings manager 110 is configured to adjust settings based on a user profile. A user profile may include various attributes related to a user (e.g., driver or passenger) of the vehicle 10. The attributes, for example, may be indicative of the age of the user, the relative experience of a user, a status of the user (e.g., VIP, member, etc.), a disability of a user (e.g., a mobility disability, impaired hearing or vision, colorblindness, arthritis, autism spectrum disorder, etc.), or any other attribute of a user that may be used to determine settings for the vehicle 10 that accommodate the user.

In some embodiments, the settings manager 110 receives user profiles, attributes, or specific settings from the user configuration system 300 or the user device 232 and adjusts the respective settings stored in the setting storage 112 to cause the accommodation for the user of the vehicle 10. In some embodiments, the settings manager 110 maintains user profiles, attributes, or specific settings for one or more users of the vehicle 10. The settings manager 110 may receive an indication of the user that is driving the vehicle 10 (e.g., from the role identifier 118), the user that is currently a passenger, and/or the user that is currently taking on any specific role (e.g., operator, driver, passenger, crew, etc.) of the vehicle 10 that may have settings associated with the role. Settings specific to a role may only be applied if the user associated with the user profile has taken on the role. For example, the sensitivity of the operator controls 40 may only be applied based on the user profile of the driver of the vehicle 10, whereas a color palette of the operator interface 48 may be determined by an attribute in the user profile of the driver, an attribute in the user profile of a passenger, and/or a function of an attribute in both user profiles.

In some embodiments, when a particular user is done with the vehicle 10 (e.g., when the session is over, or when profile storage 114 is about to be deleted to make room for a new user), changes that have been made to the settings (e.g., by the settings manager 110) are communicated to the user configuration system 300 to be saved in a repository of profiles of all users (e.g., a global profile storage 308), for use next time that same user is using the vehicle 10.

In some embodiments, received user profiles are stored in profile storage 114. The user profiles may be accessed by the settings manager 110 to apply the settings defined by the attributes in the user profiles. The settings manager 110 may access the user profiles to change the respective settings each time they are updated (e.g., by the user configuration system 300) and/or each time a user associated with the user profile changes roles. A user profile stored by the profile storage 114 may include attributes associated with the user and individual settings.

The user may have preferred settings saved to their user profile that are not associated with an attribute or are different than the settings associated with the attribute. For example, a user profile that identifies a person having arthritis may also contain a preferred setting that reduces pedal sensitivity to the default value, cancelling the increase in sensitivity that may be applied based on the arthritis attribute.

In some embodiments, the settings manager 110 may receive conflicting settings. For example, a user profile that identifies a person having arthritis and, based on that attribute, prescribes a 50% increase in pedal sensitivity may also include (in the same user profile) a preferred setting for the pedal sensitivity. The settings manager 110 may choose to apply the preferred setting instead of the setting specified by the attribute. In some embodiments, conflicting setting can be associated with user profiles of two or more profiles associated with the vehicle 10. The settings manager 110 may choose to apply a specific setting based on several criteria. For some settings, the settings manager 110 may choose the settings associated with attributes (e.g., rather than preferred settings) if settings conflict between multiple user profiles. For example, the color palette of the operator interface 48 may be modified to accommodate a user profile with a colorblindness attribute regardless of other users' preferred settings. In some embodiments, conflicting settings are chosen based on the maximum or minimum setting value (e.g., the highest lighting intensity is applied, etc.). In some embodiments, each setting has associated rules for determining which of the settings across multiple user profiles of different roles, etc. should be applied. For example, the settings manager 110 may include a setting determination function for each setting.

In some embodiments, the settings can be modified using the operator interface 48 (e.g., via callbacks provided by the settings manager 110). Some settings may be modified by the user and some settings may be locked and only modified using the operator interface 48 with a credential (e.g., password, certificate, key card, etc.). Certain settings (and/or attributes) may be locked and are only available for change (or addition to a user profile) in the user configuration system 300. For example, turning off locations restrictions may only be performed using the user configuration system 300 (e.g., only golf club operators may be able to provide users access to a setting that would allow them to enter restricted areas closer to the green). In some embodiments, the operator interface 48 is configured to unlock all or a particular set of vehicle settings by way of a special key, access card, biometric, etc.

In some embodiments, the role identifier 118 is configured to identify a person associated with a user profile and temporarily associate that user profile with the vehicle 10. For example, a camera in the vehicle 10 may use an artificial intelligence model (e.g., convolutional neural network, etc.) to perform facial recognition to associate a user profile (e.g., stored in the profile storage 114 or global profile storage 308) to the vehicle 10. In response, the settings manager 110 may apply the settings associated with the identified user profile. In some embodiments, the role identifier 118 is configured to identify a specific role of a user. For example, the role identifier 118 may identify a person and where that person is sitting to determine if they are a passenger or a driver of the vehicle 10. It is contemplated that any type of biometric (e.g., facial recognition, voice recognition, fingerprints, palm or hand geometry, gait analysis, iris recognition, etc.) can be used to associate a user profile with a vehicle and/or role.

In some embodiments, the user attribute definitions 116 is configured to store a mapping that maps an attribute (e.g., of a user profile) to respective vehicle setting values. FIG. 5 shows an example of an attribute mapping in table 400. Table 400 shows seven example attributes that may be entered into a user profile. The attributes may include, but are not limited to: impaired mobility, impaired hearing, impaired vision, colorblindness, autism spectrum disorder, arthritis, and non-adult. Non-adult, for example, can be determined by comparing the age of a user with a threshold (e.g., eighteen years old, twenty-one years old, twenty-five years old, etc.). Table 400 also shows respective vehicle settings and vehicle setting values associated for the respective settings. Values, for example, may be specified in terms of a relative (e.g., percentage or ratio) change from a default setting or the values may be specified in terms of their absolute value.

An impaired mobility attribute may be provided as shown in table 400. The impaired mobility attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) including location restrictions, pedal sensitivity, and/or steering sensitivity to accommodate a user with impaired mobility. For example, the location restrictions setting of the vehicle 10 may be turned off in response to the impaired mobility attribute, allowing the user to enter restricted areas with the vehicle 10. After location restrictions are off, the vehicle 10 (e.g., a golf vehicle) may be able to enter restricted areas closer to a tee box and/or green that are typically restricted to prevent erosion, wear, and/or damage. The impaired mobility attribute may also cause the sensitivity of the accelerator 44, brake 46, and/or steering wheel 42 to be increased.

An impaired hearing attribute may be provided as shown in table 400. The impaired hearing attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) including volume of the speakers, visual alerts, haptic feedback, and/or Bluetooth pairing to accommodate a user with impaired hearing. For example, the volume may be increased for alerts, announcements, or any other sounds that are emitted from speakers of the vehicle 10. A visual alert mode may flash the lights of the vehicle 10 when an audio alert or announcement is received/provided. A haptic feedback mode may cause the steering wheel 42 and/or the seat (e.g., of front row seating 32) to vibrate if an alert or announcement is received/provided. Additionally or alternatively, the haptic feedback mode may cause the touchscreen of the operator interface 48 to vibrate when selections are made (e.g., to confirm their receipt). In some embodiments, the impaired hearing attribute causes the vehicle 10 to enter a Bluetooth pairing mode so hearing devices, hearing aids, etc. can be readily paired with the operator interface 48 of the vehicle 10.

An impaired vision attribute may be provided as shown in table 400. The impaired vision attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) including text size, audio narration mode, and/or voice command mode to accommodate a user with impaired vision. For example, the text size of a menu or any other content presented on a digital display of the operator interface 48 may be increased. An audio narration mode may convert text presented on the display device of the operator interface 48 to audio that is emitted from the speakers. For example, the audio narration mode may read from menu options, or the audio narration mode may report (aurally) the distance and direction to a hole, tee box, green, hazard, or any other element of a golf course. The impaired vision attribute may cause the vehicle 10 to enter a voice command mode allowing the user to select menu options, confirm settings, or perform any other interaction with the operator interface 48 via voice commands. In some embodiments, the voice commands are processed by an artificial intelligence model (e.g., hidden Markov model, transformer network, etc.). In some embodiments, the vehicle 10 is capable of self-navigation and voice commands may be used to initiate navigation to a particular programmed location.

A colorblindness attribute may be provided as shown in table 400. The colorblindness attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) including an alternative color palette to accommodate a user with colorblindness. For example, the color palette of a menu or any other content presented on a digital display of the operator interface 48 may make use of an alternative color palette. For example, a blue-yellow palette may be used to ensure contrast between various objects on the display for persons with colorblindness. In some embodiments, multiple colorblindness attributes are provided for the different types of colorblindness and the color palette is optimized or otherwise chosen for the specific type of colorblindness.

A autism spectrum disorder attribute may be provided as shown in table 400. The autism spectrum disorder attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) including volume, brightness, the color palette, and/or a startle suppression mode to accommodate a user with an autism spectrum disorder. For example, the volume may be decreased for alerts, announcements, or any other sounds that are emitted from speakers of the vehicle 10. Additionally or alternatively, the brightness of lights and/or the operator interface 48 may be decreased. Additionally or alternatively, the color palette of a menu or any other content presented on a digital display of the operator interface 48 may make use of an alternative color palette. For example, a pastel palette or a palette with lower color saturation may be used.

In some embodiments, an autism spectrum disorder attribute causes the vehicle 10 to enter a startle suppression mode. The startle suppression mode causes changes in the environment in the vehicle 10 and/or proximate the vehicle 10 to be less abrupt. A message, announcement, or alert with startle suppression off may begin at the respective volume setting for that type of communication. With startle suppression mode on, the volume of an individual audio communication may increase gradually, over a time period. For example, the volume may increase over a period of 15 seconds or, as an alternative example, the volume may increase with each repetition of the alert. Startle suppression mode may also affect the brightness of the lighting of the vehicle 10 and/or display of the operator interface 48. Any interaction that would cause the display or lighting to illuminate (e.g., activation of the display by touch, entry into the vehicle, exit of the vehicle, etc.) may cause the display to increase in brightness gradually over a time period. For example, the brightness may increase over a time period of three seconds.

An arthritis attribute may be provided as shown in table 400. The arthritis attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) including location restrictions, pedal sensitivity, steering sensitivity, and/or an interface button size to accommodate a user with arthritis. For example, the location restrictions setting of the vehicle 10 may be turned off in response to the arthritis attribute allowing the user to enter restricted areas with the vehicle 10. After location restrictions are off, the vehicle 10 (e.g., a golf vehicle) may be able to enter restricted areas closer to a tee box and/or green that are typically restricted to prevent erosion, wear, and/or damage. The arthritis attribute may also cause the sensitivity of the accelerator 44, brake 46, and/or steering wheel 42 to be increased. In some embodiments, buttons on a digital display (e.g., touch screen display) of the operator interface 48 are increased in size, for example, to facilitate ease of selection for a person with arthritis.

In some embodiments, an age attribute is provided as shown in table 400. By way of example, a non-adult attribute may cause vehicle settings to be adjusted (e.g., by the settings manager 110) to limit the maximum speed, decrease pedal sensitivity, and/or increase steering sensitivity to accommodate a user that is not an adult and/or has less driving experience. The vehicle control system 100 may be configured to limit maximum speed of the vehicle 10 by command to the driveline 50 of the vehicle 10. For example, to limit the speed of the vehicle 10, the settings manager 110 may calculate, based on wheel size and gearing ratios in the driveline 50, a maximum number of rotations per minute of the prime mover 52 of the vehicle 10 for each gearing ratio and communicate the calculated maximum rotations per minute to the driveline 50.

Referring again to FIG. 4, the user configuration system 300 is shown to include a processing circuit 302, memory 304, and a communications interface 306. In some embodiments, the communications interface 306 is configured to provide communications capability over the communications network 210. In FIG. 4 the user configuration system 300 is shown communicably coupled to the user device 232 and the vehicle 10. Additionally or alternatively, the user configuration system 300 may be communicably coupled to other remote systems 240 (e.g., the off-site server 250 and/or the on-site system 260) and/or other cloud compute architectures.

The processors of processing circuit 302 may be a general purpose or specific purpose processors, an ASIC, one or more FPGAs, a group of processing components, or other suitable processing components. The processors may be configured to execute computer code and/or instructions stored in the memories or received from other computer readable media (e.g., CDROM, network storage, a remote server, etc.). The processors may be configured in various computer architectures, such as graphics processing units (“GPUs”), distributed computing architectures, cloud server architectures, client-server architectures, or various combinations thereof. One or more first processors can be implemented by a first device, such as an edge device, and one or more second processors can be implemented by a second device, such as a server or other device that is communicatively coupled with the first device and may have greater processor and/or memory resources.

The memory 304 may include one or more devices (e.g., memory units, memory devices, storage devices, etc.) for storing data and/or computer code for completing and/or facilitating the various processes described in the present disclosure. The memory 304 may include random access memory (RAM), read-only memory (ROM), hard drive storage, temporary storage, non-volatile memory, flash memory, optical memory, or any other suitable memory for storing software objects and/or computer instructions. The memory 304 may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. The memory 304 may be communicably connected to the processors and can include computer code for executing (e.g., by the processors) one or more processes described herein.

In some embodiments, the user configuration system 300 includes global profile storage 308. The global profile storage 308 may be configured to store (e.g., maintain, save, etc.) a database of user profiles for any user, including users not currently using any of the vehicles 10. In contrast, some embodiments of the profile storage 114 include only profiles of users currently associated with the vehicle 10 (e.g., to reduce memory requirements of the vehicle 10). User profiles from the global profile storage 308 may be associated with (e.g., transmitted to, communicated to) the vehicle 10 when the vehicle 10 is being used by specific users.

In some embodiments, the user configuration system 300 includes the user attribute definitions 116. As described previously, the user attribute definitions 116 may store a mapping that maps an attribute (e.g., of a user profile) to respective vehicle setting values. The user attribute definitions 116 may be included in the user configuration system 300, the vehicle control system 100, or both. The disposition of the user attribute definitions 116 may depend on the data that is communicated between the user configuration system 300 and the vehicle 10. For example, if attributes are communicated between the user configuration system 300 and the vehicle 10, it may not be necessary for the user configuration system 300 to include the user attribute definitions 116 because the vehicle 10 will convert the attribute to vehicle setting adjustments. If the settings are communicated between the user configuration system 300 and the vehicle 10, it may not be necessary for the vehicle 10 to include the user attribute definitions 116 because the user configuration system 300 will have already converted the attribute to the vehicle setting adjustments before communicating the setting information to the vehicle 10.

In some embodiments, the user configuration system 300 includes the user association interface 310. The user association interface 310 may include instructions configured to generate a user interface for associating a user profile with a vehicle 10. The user association interface 310 may include instructions for generating interface images on a local display. For example, the if the user configuration system 300 is implemented on the on-site system 260, the instructions may include generating video signals for the local display to convert into an image. The instructions may include callback functions to process interactions (e.g., typing, mouse clicks, etc.) with the interface. For example, a drag-and-drop interaction (e.g., dragging a user profile from a set of user profiles to a vehicle 10) may activate an association callback that associates the user profile with the vehicle 10.

In some embodiments, the user configuration system 300 is implemented on an off-site server 250. The user association interface 310 may cause instructions (e.g., Javascript, cascading style sheets, etc.) to be delivered to a second device (e.g., a client computer at the club house) to cause the association interface to be created (e.g., in an internet browser or a client-side proprietary application) on the second device. The instructions may include executing (e.g., calling, posting to, etc.) APIs available on the off-site server 250. For example, a drag-and-drop interaction (e.g., dragging a user profile from a set of user profiles to a vehicle 10) may initiate an API post (e.g., communication, call, etc.) that associates the user profile with the vehicle 10. In some embodiments, the user association interface 310 includes instructions for implementation on both or either the off-site server 250 or the on-site system 260.

Associating a user profile with a vehicle 10 may be performed directly or indirectly. In some embodiments, the callbacks or APIs available in the user association interface 310 directly transmit (e.g., communicate, send, etc.) the user profiles to the vehicle 10. In some embodiments, the callbacks or APIs available in the user association interface 310 allow credentials (e.g., magnetic key card, Radio Frequency Identification (“RFID”) tag/card, digital certificate, etc.) to be generated that the user carries to the vehicle 10. For example, a digital certificate may be added to a smartphone and then communicated via Bluetooth to the vehicle 10 by way of a phone application. As another example, attributes of the user profiles may be loaded on to a RFID tag/card and used to initiate the settings manager 110 to adjust the settings associated with the attributes of the user profile.

In some embodiments, the user configuration system 300 includes the user profile manager 312. The user profile manager 312 may include instructions configured to generate a user interface for creating and storing a user profile within user configuration system 300. The user profile manager 312 may allow attributes to be added to a user profile by way of drag-and-drop, selection boxes, text editor, etc. The user profile manager 312 may also allow individual setting preferences to be entered into a user profile. User profile manager may create the interface using the same or similar methods as the user association interface 310. For example, the instructions may include generating video signals for the local display to convert into an image when implemented on the on-site system 260 or instructions for generating a user interface on a second device (e.g., within an internet browser or proprietary application) when implemented on the off-site server 250, or the user profile manager 312 may include both sets of instructions for implementation on any remote system 240. After a user profile has been created with the interface of the user profile manager 312, a button on the interface or similar interface object may be used to initiate a callback and/or API that causes the user interface to be stored in the global profile storage 308. In some embodiments, the user profile created by the user profile manager 312 becomes available for association with a vehicle 10 by the user association interface 310 after it has been stored in the global profile storage 308.

In some embodiments of the fleet monitoring and control system 200 do not make use of user profiles. In some embodiments, the user attributes and/or settings are directly associated with the vehicle 10. As shown in FIG. 4, in such embodiments, the vehicle 10 includes a user attribute interface 120. The user attribute interface 120 may be configured to generate a user interface (e.g., on the operator interface 48). The user interface may provide selections, buttons, etc. to select one or more attributes (e.g., age, preferences, presence of any disability, etc.) associated with users of the vehicle 10. For example, after an attribute is selected, the vehicle control system 100 may determine the settings that are to be adjusted using the user attribute definitions 116. The settings manager 110 may adjust the settings in the setting storage 112 (e.g., those settings defined for the attribute in the user attribute definitions 116). The setting storage 112 may be configured to communicate the settings to the respective components, controls, modules, and/or systems of the vehicle 10. For example, the setting storage 112 may communicate a sensitivity to the braking system 70 or the brake 46 of the operator controls 40 based on a stored pedal sensitivity value. As another example, the setting storage 112 may communicate a color palette to the operator interface 48 that has been applied for this user to accommodate colorblindness.

In some embodiments, the user attribute interface 120 accepts input from credentials (e.g., magnetic key card, RFID tag/card, digital certificate, etc.). The credentials, for example, could be created (e.g., have information loaded onto the credential) using the on-site system 260. In some embodiments, attributes can be communicated to the vehicle control system 100 via the communications network 210.

In some embodiments, certain attributes may be locked and are only available for change in the user configuration system 300. For example, selecting the impaired mobility attribute (thus allowing the vehicle 10 to enter restricted areas near a golf green) may only be performed using the user configuration system 300. In some embodiments, the operator interface 48 is configured to unlock all or a set of attributes by way of a special key, access card, biometric, etc. (e.g., created by the user configuration system 300).

It is contemplated that selecting an attribute may have a similar effect as entering a mode associated with an attribute. Embodiments that describe an attribute being selected at the vehicle 10, communicated to the vehicle 10, or associated with a user of the vehicle 10 may also encompass embodiments for which a mode associated with the attribute is selected at the vehicle 10, or initiated remotely. For example, selecting an impaired vision attribute may have a similar effect as entering an impaired vision mode.

In some embodiments, the user configuration system 300 includes the user attribute and settings interface 314. The user attribute and settings interface 314 may include instructions configured to generate a user interface for associating an attribute or a setting with the vehicle 10. The user attribute and settings interface 314 may include instructions for generating interface images on a local display (e.g., the user device 232). For example, if the user configuration system 300 is implemented on the on-site system 260, the instructions may include generating video signals for the local display to convert into an image. The instructions may include callback functions to process interactions (e.g., typing, mouse clicks, etc.) with the interface. For example, a drag-and-drop interaction (e.g., dragging an attribute from a set of attributes to a vehicle 10) may activate an association callback that associates the user attribute with the vehicle 10. As another example, the user interface may provide buttons that adjust individual settings of the vehicle 10. An operator (e.g., of the club house, of the vehicle fleet, etc.) may choose a vehicle 10 from the fleet of vehicles managed by the user configuration system 300 and enter settings and/or choose attributes remotely. For example, settings may be entered using an interface similar to the user interface provided by the operator interface 48 (e.g., with all settings unlocked, available for adjustment, etc.)

In some embodiments, the user configuration system 300 is implemented on an off-site server 250. The user attribute and settings interface 314 may cause instructions (e.g., Javascript, cascading style sheets, etc.) to be delivered to a second device (e.g., a client computer at the club house) to cause the association interface to be created (e.g., in an internet browser or a client-side proprietary application). The instructions may include executing (e.g., calling, posting to, etc.) APIs available on the off-site server 250. For example, a drag-and-drop interaction (e.g., dragging an attribute from a set of attributes to a vehicle 10) may initiate an API post (e.g., communication, call, etc.) that associates the attribute with the vehicle 10. In some embodiments, the user attribute and settings interface 314 includes instructions for implementation on both, or either, the off-site server 250 or the on-site system 260.

Associating a vehicle with attributes and/or settings may be performed directly or indirectly. In some embodiments, the callbacks or APIs available in user attribute and settings interface 314 directly transmit (e.g., communicate, send, etc.) the attributes and/or settings to the vehicle 10. In some embodiments, the callbacks or APIs available in the user association interface 310 allow credentials (e.g., magnetic key card, RFID tag/card, digital certificate, etc.) to be generated that the user carries to the vehicle 10. For example, a digital certificate may be added to a smartphone and then communicated via Bluetooth to the vehicle by way of a phone application. As another example, attributes or settings may be loaded on to a RFID tag/card and used to initiate the settings manager 110 to adjust the settings based on the settings and/or attributes loaded onto the card.

FIG. 6-8 show flows of operations that may be performed to adjust the settings of the vehicle 10, according to some embodiments. The flows of operation may be performed by various components, devices, etc., of the fleet monitoring and control system 200. For example, the operations may be performed by the vehicle 10, the user configuration system 300, or both.

FIG. 6 shows flow of operations 500 for adjusting a setting of a vehicle from a default setting (e.g., current, initial, etc.) to an adjusted setting based on user attributes associated with a user profile. Flow 500 may include acquiring a user profile associated with a user of a vehicle where the user profile includes a user attribute in operation 502. The user profile may be acquired by the vehicle 10. The user of the vehicle 10 may enter a user profile using the operator interface 48 (e.g., by selecting an attribute). The user of the vehicle 10 may use an application on a mobile device (e.g., smartphone, tablet, etc.) to select attributes for their user profile and communicate them to the vehicle 10. For example, the vehicle 10 may provide a Wi-Fi connection to deliver instructions for a user interface from settings manager 110. As another example, the user profile manager 312 and/or the user association interface 310 of the user configuration system may provide instructions for a user interface to create and associate a user profile with the vehicle 10. In some embodiments, APIs available in the user association interface 310 or the user profile manager 312 allow credentials (e.g., magnetic key card, RFID tag/card, digital certificate, etc.) to be generated that the user carries to the vehicle 10. The credential may load the information to the vehicle 10 by swiping, tapping, connecting, etc. In some embodiments, user profiles are transmitted from the user configuration system 300 to the vehicle 10. User profiles may be associated with (e.g., transmitted with, etc.) a biometric that activates the user profile at the vehicle 10.

The flow 500 may include adjusting a setting of the vehicle 10 from a current setting to an adjusted setting based on the user attribute in operation 504. For example, the user attribute can cause the settings manager 110 to adjust the settings based on the configurations shown in table 400. Settings related to any component or system of the vehicle 10 may be adjusted, including the steering wheel 42, the brake 46 (e.g., pedal, hand brake, by release of the accelerator pedal, etc.), the accelerator 44 (e.g., pedal, thumb throttle, etc.), a display (e.g., of the operator interface 48), and/or a speaker (e.g., of the operator interface 48). In some embodiments, the vehicle 10 associates a role with a user profile and adjusts settings based on the user profile that is associated with a particular role. For example, the vehicle 10, may determine the driver (e.g., by the role identifier 118) and adjust the sensitivity of the brake 46, the steering wheel 42, the accelerator 44, etc. based on the user profile of the driver rather than other user profiles that have been associated with the vehicle 10 (e.g., profiles of passengers, etc.).

FIG. 7 shows flow of operations 510 for adjusting a setting of a vehicle from a default setting (e.g., current, initial, etc.) to an adjusted setting based on an indication of a disability.

Flow 510 may include acquiring an indication of the disability of the user in operation 512. The indication of the disability may be communicated to the vehicle 10 by way of a user profile that contains an attribute associated with the disability. The indication of a disability may be communicated to the vehicle 10 by the user configuration system 300. For example, an operator may activate a persons with disability mode (e.g., impaired mobility mode, colorblindness mode, etc.) using the user attribute and settings interface 314 of the user configuration system 300 and the user configuration system 300 may subsequently, communicate the mode to the vehicle 10. In some embodiments, credentials (e.g., magnetic key card, RFID tag/card, digital certificate, etc.) are created (e.g., generated, loaded, etc.) that the user carries to the vehicle 10 as an indication of the disability.

The flow 510 may include performing an adjustment to a setting of the vehicle 10 responsive to the indication of the disability in operation 514. In some embodiments, the adjustment facilitates improved accommodation of the user having the disability. For example, the user attribute can cause the settings manager 110 to adjust the settings based on the configurations shown in table 400. Settings related to any component or system of the vehicle 10 may be adjusted, including the steering wheel 42, the brake 46, (e.g., pedal, hand brake, by release of the accelerator pedal, etc.), the accelerator 44 (e.g., pedal, thumb throttle, etc.), a display (e.g., of the operator interface 48), and/or a speaker (e.g., of the operator interface 48). In some embodiments, the vehicle 10 associates a role with a user profile and adjust settings based on the user profile that is associated with a particular role. To accommodate the person with the disability, various adjustments may be performed, including those listed in table 400 of FIG. 5.

To accommodate impaired mobility, the location restrictions setting of the vehicle 10 may be turned off to allow the vehicle 10 to enter restricted areas closer to a tee box and/or green that are typically restricted to prevent erosion, wear, and/or damage. Impaired mobility may further be accommodated by adjusting the sensitivity of the accelerator 44, the brake 46, and/or the steering wheel 42.

To accommodate impaired hearing, the volume may be increased for alerts, announcements, or any other sounds that are emitted from speakers of the vehicle 10. Impaired hearing may further be accommodated by entering a visual alert mode that flashes the lights of the vehicle 10 and/or provides haptic feedback through the steering wheel 42 and/or the seat when an audio alert or announcement is received. Additionally or alternatively, a haptic feedback mode may cause the touchscreen of the operator interface 48 to vibrate when selections are made (e.g., to confirm their receipt). In some embodiments, impaired hearing is accommodated by entering a Bluetooth pairing mode so hearing devices, hearing aids, etc. can be readily paired with the operator interface 48 of the vehicle 10.

To accommodate impaired vision, the text size of a menu or any other content presented on a digital display of the operator interface 48 may be increased. Impaired vision may be further accommodated by entering an audio narration mode that converts text presented on the display device of the operator interface 48 to audio that is emitted from the speakers. For example, the audio narration mode may read from menu options, or the audio narration mode may report aurally the distance and direction to a hole, tee box, green, hazard, or any other element of a golf course. Impaired vision may be further accommodated by using voice commands for selecting menu options, confirming settings, or performing any other interaction with the operator interface 48 via voice commands.

To accommodate colorblindness, an alternative color palette may be used by the operator interface 48. For example, a blue-yellow palette of a menu or any other content presented on a digital display of the operator interface 48 may be used to ensure adequate contrast for users with colorblindness.

To accommodate an autism spectrum disorder, the volume may be decreased for alerts, announcements, or any other sounds that are emitted from speakers of the vehicle 10. To further accommodate an autism spectrum disorder, the brightness of lights and/or the operator interface 48 may be decreased and/or the color palette of a menu or any other content presented on a digital display may be substituted with colors that are pastel or have a lower color saturation. Additionally or alternatively, the volume of an individual audio communication may increase gradually over a time period to prevent a rapid change in the environment proximate the vehicle 10. Additionally or alternatively, any interaction that would cause the display or lighting to illuminate (e.g., activation of the display by touch, entry into the vehicle, exit of the vehicle, etc.) may cause the display to increase in brightness gradually over a time period (e.g., 2 seconds, 5 seconds, etc.)

To accommodate arthritis, the location restrictions setting of the vehicle 10 may be turned off, for example, to allow the vehicle 10 to enter restricted areas closer to a tee box and/or green that are typically restricted to prevent erosion, wear, and/or damage. Arthritis may be further accommodated by adjusting the sensitivity of the accelerator 44, the brake 46, and/or the steering wheel 42. Additionally or alternatively, buttons on a digital display (e.g., touch screen display) of the operator interface may be increased in size, for example, to facilitate ease of selection for a person with arthritis.

FIG. 8 shows flow of operations 520 for acquiring a user profile, attribute, vehicle setting, or indication of a disability according to some embodiments. Flow 520 may include generating a user interface configured to associate a user profile, attribute, setting, or indication of a disability with a vehicle 10 in operation 522. For example, the user association interface 310 may cause instructions (e.g., Javascript, cascading style sheets, etc.) to be delivered to a second device (e.g., a client computer at the club house) to cause the association interface to be created (e.g., in an internet browser or a client-side proprietary application). The user interface may provide a method (e.g., a drag-and-drop interaction, selection boxes, etc.) to allow the user profile, attribute, setting, or indication of a disability to be associated with a vehicle 10. In some embodiments, after the association is made (e.g., in the user configuration system 300) the user profile, attribute, setting, or indication of a disability with a vehicle is transmitted (e.g., sent, communicated, etc.) to the vehicle 10 in operation 524, allowing for the settings manager 110 to make the appropriate changes to the settings of the vehicle 10.

In some embodiments, flow 520 includes creating a credential with the user profile, attribute, setting, or indication of a disability in operation 526. For example, a magnetic key card, RFID tag/card, digital certificate, etc. may be created (e.g., generated, loaded, etc.) using the user configuration system 300. In some embodiments, the user is given the credential and upon occupying (e.g., using) the vehicle 10, the user loads the user profile attribute, setting, or indication of a disability on to the vehicle in operation 528 using the credential. For example, the information may be loaded from the credential by way of a magnetic card reader, RFID reader, smartphone application, etc. Alternatively, the credential may simply activate the user profile transmitted to the vehicle 10 in operation 524.

FIG. 9 shows flow of operations 600 for announcing an alert, message, or notification according to some embodiments. Flow 600 is an example flow describing how different persons with disabilities modes (including setting changes based on an attribute in a user profile) can be applied within the vehicle 10 and may be executed by the vehicle control system 100. Flow 600 may include acquiring an alert, message, or notification to announce in operation 602. A general announcement, for example, may be transmitted to all vehicles 10. The announcement may be indicative of imminent severe weather, poor environment conditions (e.g., an area on a golf course with poor conditions), or any other announcement for the user of a vehicle 10. Flow 600 may include determining if impaired hearing mode is active in operation 604. If impaired hearing mode is on, flow may continue to operation 606 where the volume setting for alerts, messages, or notifications may be increased. Additionally or alternatively, the vehicle 10 may activate its lights (e.g., turning them on, flashing them, etc.) to visually attract the attention of the user of the vehicle 10. Flow 600 may continue to operation 608 either after operation 606 or operation 604.

In some embodiments, the flow 600 includes determining if startle suppression mode is active (e.g., turned on) in operation 608. If startle suppression mode is on, the volume of the alert, message, or notification may be gradually increased as it is emitted by the speakers of the operator interface 48. For example, the volume may be initially very low and increase over a time period (e.g., over 15 seconds, with each repetition of the alert, etc.) until the sound is at the full level of the current volume setting (e.g., from operation 606 or the original volume setting). In some embodiments, the brightness of any lighting including those used to indicate alerts to persons with impaired hearing may similarly be increased over a time period (e.g., over 2 seconds, etc.) or with each time the light flashes in operation 610. If startle suppression is not active, the alert, message, or notification may be emitted from the speakers at the volume setting (e.g., from operation 606 or the original volume setting) in operation 612 upon receipt.

As utilized herein with respect to numerical ranges, the terms “approximately,” “about,” “substantially,” and similar terms generally mean +/−10% of the disclosed values, unless specified otherwise. As utilized herein with respect to structural features (e.g., to describe shape, size, orientation, direction, relative position, etc.), the terms “approximately,” “about,” “substantially,” and similar terms are meant to cover minor variations in structure that may result from, for example, the manufacturing or assembly process and are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the disclosure as recited in the appended claims.

It should be noted that the term “exemplary” and variations thereof, as used herein to describe various embodiments, are intended to indicate that such embodiments are possible examples, representations, or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).

The term “coupled” and variations thereof, as used herein, means the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly to each other, with the two members coupled to each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled to each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.

References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below”) are merely used to describe the orientation of various elements in the figures. It should be noted that the orientation of various elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.

The hardware and data processing components used to implement the various processes, operations, illustrative logics, logical blocks, modules, and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single-or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit or the processor) the one or more processes described herein.

The present disclosure contemplates methods, systems, and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Although the figures and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the various connection steps, processing steps, comparison steps, and decision steps.

It is important to note that the construction and arrangement of the vehicle 10 and the systems and components thereof (e.g., the body 20, the operator controls 40, the driveline 50, the suspension system 60, the braking system 70, the sensors 90, the vehicle control system 100, etc.) and the fleet monitoring and control system 200 (e.g., the remote systems 240, the user portal 230, the user sensors 220, etc.) as shown in the various exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein.