System and method for adjusting vehicle operating parameters by processing trailer information

Abstract

A system and method for adjusting operating parameters of a vehicle by processing trailer information includes a sensor and a controller. The vehicle includes a traction hitch device configured to couple with a trailer. The sensor is configured to detect whether the trailer is coupled to the traction hitch. The controller includes data processing hardware and memory hardware storing instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations that include processing the trailer information to change the vehicle operating parameter to a predetermined operating parameter if the trailer is coupled to the hitch.

Description

[0001] The information provided in this section is for the purpose of generally presenting the context of the present disclosure. The work of the presently named inventors, to the extent it is described in this section and in aspects of the description that may not qualify as prior art at the time of filing, is neither explicitly nor implicitly admitted to be prior art against the present disclosure. Technical Field

[0002] The present disclosure generally relates to a vehicle having a towing hitch configured to couple with a trailer. Background Art

[0003] A trailer is towed by a vehicle, and the load from the trailer may affect the driving operation of the vehicle. Therefore, many vehicles include a driving mode for operating the vehicle without towing a trailer (conventional hauling mode) and a driving mode for operating the vehicle when the vehicle is towing a trailer (trailer hauling mode). In conventional hauling mode, the vehicle powertrain may be configured to produce less torque during acceleration relative to trailer hauling mode. Currently, driving modes are manually selected by a user, and therefore, the user's driving experience may not be desirable when a trailer is towed and the vehicle is in conventional hauling mode. For example, if the combined weight of the trailer and cargo exceeds a predetermined value, a delay in acceleration may occur if the vehicle is in conventional hauling mode.

[0004] In addition, towing hitches are configured to couple with a variety of different trailers and loads, such as a simple flatbed trailer, a horse trailer, a recreational vehicle, a boat trailer, etc. Each trailer may have different characteristics, such as weight, width, height, and length, and the characteristics of the trailer may affect various vehicle operating parameters, such as braking, acceleration, available routes, etc. In addition, the characteristics of the trailer may affect the operation of the vehicle differently. For example, the weight of the trailer may affect the stopping distance of the brakes and the acceleration of the vehicle, while physical characteristics such as the length and width of the trailer may inhibit driving around sharp turns. In addition, the height of the trailer may prevent the trailer from driving on roads with underpasses or bridges with height restrictions.

[0005] Accordingly, it is desirable to tune vehicle operating parameters of a vehicle based on trailer information. Additionally, it is desirable to have a system and method in which trailer information can be stored to facilitate adjustment of vehicle operating parameters. Summary of the invention

[0006] In one configuration, a system for adjusting operating parameters by processing trailer information includes a sensor and a controller. A vehicle includes a towing hitch configured to couple with a trailer. The sensor is configured to detect whether a trailer is coupled to the towing hitch of the vehicle. The controller includes data processing hardware and memory hardware, the memory hardware storing instructions that, when executed on the data processing hardware, cause the data processing hardware to perform operations, the operations including: if a trailer is coupled to the hitch, processing the trailer information to change the vehicle operating parameters to predetermined operating parameters.

[0007] The system may include one or more of the following optional features. For example, the trailer information may be one of trailer type, trailer length, trailer height, trailer width, and trailer weight. For example, in one aspect, the sensor is configured to detect trailer weight. In another aspect, the sensor is configured to detect trailer width and trailer height. In yet another aspect, the sensor is an optical device configured to detect trailer height and width.

[0008] In one configuration of the system, the predetermined operating parameter is a driving mode. In such a configuration, the driving mode may be a trailer hauling mode.

[0009] In one configuration, the vehicle operating parameter may be a cruise control function, whereby the controller is configured to turn off the cruise control function of the vehicle if a trailer is coupled to the hitch. It should be understood that the predetermined operating parameters disclosed herein are not exhaustive, but rather illustrative. For example, the predetermined operating parameter of the vehicle may be a navigation route and / or a braking coefficient. In the case where the predetermined operating parameter is a navigation route, the controller generates the navigation route by processing the trailer information. In the case where the predetermined operating parameter is a braking coefficient, the controller may adjust the braking coefficient based on the trailer information.

[0010] In another configuration, a method for adjusting operating parameters of a vehicle having a towing hitch configured for coupling with a trailer is provided. The operating parameters of the vehicle may be adjusted by processing trailer information. The method includes detecting whether a trailer is coupled to the hitch of the vehicle, and if the trailer is coupled to the hitch, processing the trailer information to change the vehicle to a predetermined operating parameter. The trailer information may be at least one of a trailer type, a trailer length, a trailer height, a trailer width, and a trailer weight.

[0011] In one configuration, the predetermined operating parameter is a driving mode. In such a configuration, the driving mode may be a trailer mode.

[0012] Additionally or alternatively, the method may include determining whether the vehicle is in a regular haul mode or a trailer haul mode, and alerting the user that the vehicle is in regular haul mode when a trailer is coupled to the hitch.

[0013] In one arrangement, the method may include determining whether a cruise control function of the vehicle is on, and automatically turning off the cruise control function if a trailer is coupled to the hitch.

[0014] In yet another configuration, the predetermined operating parameter may be a navigation route and / or a braking coefficient, and the controller generates the navigation route and adjusts the braking coefficient by processing the trailer information. In one aspect, the controller generates a plurality of navigation routes for the user to select, and each of the plurality of navigation routes may include a notification of a sharp turn. BRIEF DESCRIPTION OF THE DRAWINGS

[0015] The drawings described herein are for illustrative purposes only of selected configurations and are not intended to limit the scope of the present disclosure.

[0016] Figure 1 is a perspective schematic diagram of a traction system according to the present disclosure showing a vehicle in communication with a network and a mobile device;

[0017] Figure 2 is a functional block diagram of an exemplary traction system providing communication between a controller and vehicle components according to the present disclosure;

[0018] Figure 3A It is displayed in Figure 1 A depiction of a mobile device with a menu for use in operation of the traction system shown;

[0019] Figure 3B It is displayed in Figure 1 A depiction of the head unit of a menu used in operation of the traction system shown;

[0020] Figure 4A is a depiction of a mobile device that provides a selection for Figure 1 Selection of trailer profile for the towing system shown;

[0021] Figure 4B is a depiction of a head unit for a vehicle, the head unit providing a vehicle to be selected for use Figure 1 Selection of trailer profile for the towing system shown;

[0022] Figure 5A is a depiction of a mobile device that provides the ability to add or remove Figure 1 Options for trailers in towing systems shown;

[0023] Figure 5B is a depiction of a head unit, which provides the ability to add or remove Figure 1 Options for trailers in towing systems shown;

[0024] Fig. 6Ais a depiction of a mobile device providing a list of profiles to be removed from memory hardware;

[0025] Figure 6B is a depiction of a head unit providing a list of profiles to be removed from the memory hardware;

[0026] Fig. 7A is a depiction of a mobile device that provides a means for inputting Figure 1 Selection of trailer information in the towing system shown;

[0027] Figure 7B is a depiction of a head unit, which provides input to Figure 1 Selection of trailer information in the towing system shown;

[0028] Figure 8 is a functional block diagram of exemplary adjustment of vehicle operating parameters by processing trailer information according to the present disclosure; and

[0029] Fig. 9 is a flow chart illustrating a method for adjusting vehicle operating parameters by processing trailer information according to the present disclosure.

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

[0031] Example configurations will now be described more fully with reference to the accompanying drawings. Example configurations are provided so that the present disclosure will be thorough and will fully convey the scope of the present disclosure to those of ordinary skill in the art. Specific details, such as examples of specific components, devices, and methods, are set forth to provide a thorough understanding of the configurations of the present disclosure. It will be apparent to those of ordinary skill in the art that specific details need not be employed, that example configurations may be embodied in many different forms, and that the specific details and example configurations should not be construed as limiting the scope of the present disclosure.

[0032] The terms used herein are only used for the purpose of describing specific exemplary configurations and are not intended to be limiting. As used herein, the singular articles "a", "an" and "the" may also be intended to include plural forms unless the context clearly states otherwise. The terms "comprises", "comprising", "including" and "having" are inclusive and therefore specify the presence of features, steps, operations, elements and / or parts, but do not exclude the presence or addition of one or more other features, steps, operations, elements, parts and / or groups thereof. The method steps, processes and operations described herein should not be interpreted as necessarily requiring them to be performed in the specific order discussed or shown, unless specifically identified as an execution order. Additional or alternative steps may be adopted.

[0033] When an element or layer is referred to as being "on another element or layer," "engaged to," "connected to," "attached to," or "coupled to" another element or layer, it may be directly on, directly engaged with, connected to, attached to, or coupled to another element or layer, or there may be intermediate elements or layers. Conversely, when an element is referred to as being "directly on another element or layer," "directly engaged to," "directly connected to," "directly attached to," or "directly coupled to" another element or layer, there may be no intermediate elements or layers. Other words used to describe the relationship between elements should be interpreted in a similar manner (e.g., "between" versus "directly between," "adjacent" versus "directly adjacent," etc.). As used herein, the term "and / or" includes any and all combinations of one or more associated listed items.

[0034] The terms first, second, third, etc. can be used in this article to describe various elements, components, regions, layers and / or parts. These elements, components, regions, layers and / or parts should not be limited by these terms. These terms can only be used to distinguish an element, component, region, layer or part from another region, layer or part. Unless the context clearly indicates, terms such as "first", "second" and other numerical terms do not imply order or sequence. Therefore, without departing from the teaching of the example configuration, the first element, component, region, layer or part discussed below can be referred to as the second element, component, region, layer or part.

[0035] In this application, including the definitions below, the term "module" may be replaced with the term "circuit". The term "module" may refer to, be a part of, or include an application specific integrated circuit (ASIC); a digital, analog, or mixed analog / digital discrete circuit; a digital, analog, or mixed analog / digital integrated circuit; a combinational logic circuit; a field programmable gate array (FPGA); a processor (shared, dedicated, or group) that executes code; a processor (shared, dedicated, or group) that stores code executed by a memory; other suitable hardware components that provide the described functionality; or a combination of some or all of the above, such as in a system on a chip.

[0036] The term "code" as used above may include software, firmware and / or microcode, and may refer to a program, a routine, a function, a class and / or an object. The term "shared processor" covers a single processor that executes some or all codes from multiple modules. The term "group processor" covers a processor that executes some or all codes from one or more modules in combination with an additional processor. The term "shared memory" covers a single memory that stores some or all codes from multiple modules. The term "group memory" includes a memory that stores some or all codes from one or more modules in combination with an additional memory. The term "memory" may be a subset of the term "computer-readable medium". The term "computer-readable medium" does not include transient electrical signals and electromagnetic signals propagated through the medium, and therefore can be considered to be tangible and non-transient memory. Non-limiting examples of non-temporary memory include tangible computer-readable media, which include non-volatile memory, magnetic memory, and optical memory.

[0037] The apparatus and methods described in this application may be implemented in part or in whole by one or more computer programs executed by one or more processors. The computer program includes processor executable instructions stored on at least one non-transitory tangible computer readable medium. The computer program may also include and / or rely on stored data.

[0038] Software applications (i.e., software resources) may refer to computer software that enables a computing device to perform tasks. Example applications include, but are not limited to, system diagnostic applications, system management applications, system maintenance applications, word processing applications, spreadsheet applications, messaging applications, media streaming applications, social networking applications, and gaming applications.

[0039] Non-transitory memory can be a physical device used to temporarily or permanently store programs (e.g., sequences of instructions) or data (e.g., program state information) for use by a computing device. Non-transitory memory can be volatile and / or non-volatile addressable semiconductor memory. Examples of non-volatile memory include, but are not limited to, flash memory and read-only memory (ROM) / programmable read-only memory (PROM) / erasable programmable read-only memory (EPROM) / electrically erasable programmable read-only memory (EEPROM) (e.g., commonly used for firmware, such as bootloaders). Examples of volatile memory include, but are not limited to, random access memory (RAM), dynamic random access memory (DRAM), static random access memory (SRAM), phase change memory (PCM), and disk or tape.

[0040] These computer programs (also referred to as programs, software, software applications, or code) include machine instructions for a programmable processor and may be implemented in high-level procedural and / or object-oriented programming languages ​​and / or assembly / machine languages. As used herein, the terms "machine-readable medium" and "computer-readable medium" refer to any computer program product, non-transitory computer-readable medium, memory, and / or device (e.g., disks, optical disks, processors, programmable logic devices (PLDs)) for providing machine instructions and / or data to a programmable device, including machine-readable media that receive machine instructions as machine-readable signals. The term "machine-readable signal" refers to any signal used to provide machine instructions and / or data to a programmable processor.

[0041] Various implementations of the systems and techniques described herein can be realized in digital electronic and / or optical circuits, integrated circuits, specially designed ASICs (application specific integrated circuits), computer hardware, firmware, software, and / or combinations thereof. These various implementations may include implementations in one or more computer programs executable and / or interpretable on a programmable system that includes at least one programmable processor, which may be special purpose or general purpose, coupled to receive data and instructions from a storage system, at least one input device, and at least one output device, and to send data and instructions to the storage system, at least one input device, and at least one output device.

[0042] The process and logic flow described in this specification can be performed by one or more programmable processors (also referred to as data processing hardware), which execute one or more computer programs to perform functions by operating on input data and generating outputs. The process and logic flow can also be performed by a dedicated logic circuit (e.g., FPGA (field programmable gate array) or ASIC (application-specific integrated circuit)). As an example, a processor suitable for executing a computer program includes both general-purpose and special-purpose microprocessors, and any one or more processors of any type of digital computer. Typically, the processor will receive instructions and data from a read-only memory or a random access memory or both. The basic elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Typically, a computer will also include one or more large-capacity storage devices (e.g., magnetic disks, magneto-optical disks, or optical disks) for storing data, or be operably connected to receive data from it or transmit data to it or both. However, a computer does not need to have such a device. Computer-readable media suitable for storing computer program instructions and data include all forms of nonvolatile memory, media, and memory devices, including, for example, semiconductor memory devices, such as EPROM, EEPROM, and flash memory devices; magnetic disks, such as internal hard disks or removable disks; magneto-optical disks; and CD ROM and DVD-ROM disks. The processor and memory may be supplemented by, or incorporated in, special purpose logic circuitry.

[0043] To provide interaction with a user, one or more aspects of the present disclosure may be implemented on a computer having a display device (e.g., a CRT (cathode ray tube), LCD (liquid crystal display) monitor, or touch screen) for displaying information to the user and optionally a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the computer. Other kinds of devices may also be used to provide interaction with the user; for example, the feedback provided to the user may be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user may be received in any form, including sound, voice, or tactile input. In addition, the computer may interact with the user by sending documents to and receiving documents from a device used by the user; for example, by sending a web page to a web browser on a user's client device in response to a request received from the web browser.

[0044] A system and method for adjusting operating parameters of a vehicle by processing trailer information includes a sensor and a controller. The vehicle includes a towing hitch configured to be coupled to a trailer. The sensor is configured to detect the coupling of the trailer. The sensor may also be configured to detect trailer information to include length, height, width, weight, etc. The trailer information is processed by the controller to adjust the operating parameters of the vehicle to predetermined operating parameters, thereby adjusting the operation of the vehicle according to the weight, length, width, height and cargo weight of the trailer. In addition, the controller may be configured to automatically select the predetermined operating parameters or prompt the user to select the predetermined operating parameters. As used herein, the term "operating parameters" refers to a vehicle component or system, alone or in combination with other vehicle components and / or systems, that affects the control and / or travel of the vehicle, such as an engine, brakes, a navigation system, a cruise control, etc. Therefore, the operating parameters described herein are illustrative and not exhaustive.

[0045] In addition, the systems and methods described herein can customize and store multiple trailers for a user. Each trailer can be associated with its own trailer information. In such aspects, the systems and methods adjust vehicle operating parameters based on the selected trailer, thereby providing operating parameters tuned to the trailer information of the attached trailer.

[0046] refer to Figure 1 , vehicle 10 includes a body 12 and known systems and components for propelling and controlling the movement of vehicle 10, such as a powertrain 14, brakes 16, a steering wheel (not shown), etc. Vehicle 10 may include systems for controlling vehicle operating parameters, such as a regular hauling mode, a trailer hauling mode, an advanced driver assistance system (“ADAS”), a cruise control system, an anti-lock braking system, a navigation system, etc.

[0047] The vehicle 10 includes a towing hitch 18 configured to couple with a coupling mechanism 20 of a trailer 22. For purposes of illustration, the towing hitch 18 is shown as a receiver-type hitch and includes a support 24 that can be removably inserted into a receiver (not shown) of the vehicle 10. The receiver is mounted to a rear end of a frame or chassis member of the vehicle 10 by bolts or other fasteners. The towing hitch 18 also includes a towing ball 26 that is configured to couple to the coupling mechanism 20 of the trailer 22. The coupling mechanism 20 is illustratively shown as a socket 28 mounted to the tongue 30 of the trailer 22, and may include a mechanism (not shown) for securing the towing ball 26 in the socket 28. It should be understood that other types of hitch systems, such as fixed tow bar hitch systems, may also be used. The towing hitch 18 is provided for exemplary purposes only and does not narrow the scope of the appended claims.

[0048] The vehicle 10 includes a traction system 32 configured to adjust operating parameters of the vehicle 10. The traction system 32 may be implemented in a software application having an operating unit written in a head unit 34 of the vehicle 10. The traction system 32 includes a sensor 36 and a controller 38. The operating unit provides a set of instructions to be executed by the controller 38. The traction system 32 is configured to cause the head unit 34 ( Figure 3B 4 and 5. The head unit 34 may be configured to communicate with a host program 40 in a server 42 and / or a mobile device 44 located outside the vehicle 10 (shown in FIG. 1 ). The head unit 34 may communicate wirelessly with the host program 40 and the mobile device 44 using a transmission device 46 of the vehicle 10. The transmission device 46 may be a transceiver antenna for receiving and transmitting data between the head unit 34, the server 42, and the mobile device 44. The transmission device 46 may also include a Bluetooth transceiver for receiving and transmitting data between the head unit 34 and the mobile device 44. A software application may be downloaded to the mobile device 44 for inputting information into the controller 38 located in the head unit 34.

[0049] The traction system 32 is configured to adjust the operating parameters of the vehicle 10 by processing trailer information. The operating parameters of the vehicle 10 may be a hauling mode, a navigation route, and / or a braking coefficient. As used herein, the term "trailer information" means the condition of the trailer 22, such as whether the trailer 22 is coupled to the towing hitch 18, and the physical characteristics of the trailer 22, such as the weight, height, length, width, and cargo weight of the trailer 22. In one aspect, the traction system 32 is configured to process trailer information and automatically adjust the operating parameters of the vehicle 10. In another aspect, the traction system 32 processes trailer information and provides prompts or notifications to the user, allowing the user to manually select the operating parameters of the vehicle 10. It should be understood that the traction system 32 can be configured to automatically adjust specific vehicle operating parameters while prompting the user to select other vehicle operating parameters. It should be understood that the operating parameters disclosed herein are illustrative and not exhaustive.

[0050] The sensor 36 is configured to detect trailer information, such as whether the trailer 22 is coupled to the towing hitch 18 of the vehicle 10, and the controller 38 is configured to process data from the sensor 36 to adjust the operating parameters of the vehicle 10. The sensor 36 may also be configured to detect at least one or more different types of trailer information. Any sensor 36 currently known or later developed may be modified for use herein, illustratively including load sensors, tension sensors, etc. It should be understood that the sensor 36 may determine whether the trailer 22 is coupled to the towing hitch 18 by measuring the load on the towing ball 26 and / or the support 24. In one aspect, trailer information such as cargo weight or trailer weight may be calculated by processing data detected by the sensor 36 with information related to the operation of the vehicle 10. For example, the weight of the trailer 22 may be processed by the load detected by the sensor 36 and the operation of the engine relative to the acceleration demand of the user. Such calculations are well known to those skilled in the art, and detailed description of such calculations is not required.

[0051] The sensor 36 may be a sensor unit including one or more sensors 36 of different capabilities. For example, the sensor 36 may include a first sensor 36a and a second sensor 36b. The first sensor 36a is configured to detect the load applied to the tow ball 26, and the second sensor 36b is configured to detect the trailer height and width. The second sensor 36b may be an optical sensor, such as a camera or a lidar sensor, in which case image processing is performed by the controller 38 to calculate the width and height of the trailer 22.

[0052] The towing system 32 may also include an input 48 for manually entering trailer information (in Figure 3A-8 ), trailer information may not be calculated or otherwise detected by sensor 36. For example, a user may actuate input 48 to input trailer information, such as trailer length and cargo weight. Towing system 32 may be configured to allow a user to override trailer information detected by sensor 36. For example, when sensor 36 detects trailer information such as the height of trailer 22, a user may manually input the height to override the trailer information obtained by sensor 36. Such an aspect may be beneficial in situations where the tire size of trailer 22 and / or vehicle 10 has changed.

[0053] The controller 38 includes data processing hardware 50 and memory hardware 52. The memory hardware 52 stores instructions that, when executed on the data processing hardware 50, cause the data processing hardware 50 to perform operations, including processing trailer information to change vehicle operating parameters to predetermined operating parameters if the trailer 22 is coupled to the towing hitch 18. In one aspect, the controller 38 is configured to prompt a user to accept the predetermined operating parameters. In another aspect, the controller 38 automatically changes the vehicle operating parameters to the predetermined operating parameters.

[0054] Reference now Figure 2 , the trailer information is retrieved by the controller 38 and transmitted to the controller area network 54 for distribution to at least one of the multiple control units for controlling vehicle operating parameters. For example, the controller 38 can transmit the trailer height, width and length to the navigation control unit 56A. The navigation control unit 56A processes the trailer height, width and length to generate a route that is not hindered by the trailer height, width and length and / or provides the user with locations with sharp turns along the generated route. In such an example, the trailer height can be processed to identify any underpasses or tunnels that may not accommodate the height of the trailer 22, and generate a route that bypasses the identified underpasses and / or tunnels. In addition, the trailer width and length can be processed to locate turns that may require the vehicle 10 to significantly reduce its speed to safely travel through the turn.

[0055] As described above, one of the vehicle operating parameters may be a hauling mode. In such an aspect, the vehicle 10 is configured to be driven in a conventional hauling mode or a trailer hauling mode. In the conventional hauling mode, the components of the vehicle 10 responsible for propulsion and control of the movement of the vehicle 10 (such as the vehicle 10 powertrain 14 and the brakes 16) may be configured to operate without the load associated with the towing trailer 22. For example, in the conventional hauling mode, the powertrain 14 is configured to move through various transmission gears without considering the load of the trailer 22. In the trailer hauling mode, the powertrain 14 is configured to generate a greater torque in order to facilitate pulling the load associated with the trailer 22. In addition, the brake 16 may be set to generate a greater friction coefficient in the trailer hauling mode relative to the conventional hauling mode to shorten the stopping distance of the vehicle 10 when hauling the trailer 22. Accordingly, the controller 38 may transmit trailer information such as trailer weight and cargo weight to the hauling mode ECU 56B and / or the brake ECU 56C.

[0056] In the event that the vehicle 10 includes a cruise control system, the controller 38 transmits the trailer information to the cruise control ECU 56D. In one aspect, the sensor 36 determines that the trailer 22 is coupled to the towing hitch 18, and the controller 38 can be configured to automatically transmit data from the sensor 36 to the cruise control ECU 56D to automatically disable the cruise control operation of the vehicle 10. For example, if the weight of the trailer 22, the weight of the cargo, and the width and length of the trailer 22 (individually or in combination) exceed a predetermined value, the controller 38 can automatically transmit the trailer information to the cruise control ECU 56D to disable the cruise control operation of the vehicle 10. Alternatively, the controller 38 can be configured to notify the user that the cruise control is on, and the user can decide to turn off the cruise control or keep the cruise control on. In such an aspect, the controller 38 can generate a text display on the head unit 48 notifying the user that the cruise control is on. It should be understood that for illustration purposes, the haul mode ECU 56B, brake ECU 56C, and cruise control ECU 56D are shown as separate units, but the haul mode ECU 56B, brake ECU 56C, and cruise control ECU 56D may be integrated into a single unit, such as a body control module of the vehicle 10 .

[0057] Reference now Figure 3A and 3B , the mobile device 44 and / or the head unit 34 can be used as an input 48 for entering trailer information. The software application includes a home page that can be displayed on the display of the head unit 34 and / or the display of the mobile device 44. The home page includes a menu that can be selected by actuating the mobile device 44 or the head unit 34. For example, the display of the head unit 34 and the display of the mobile device 44 can be a touch screen display. It should be understood that the head unit 34 and the mobile device 44 may include other mechanisms and devices for entering trailer information, such as a keyboard, a microphone, an electronic stylus, etc. When a menu is selected, a drop-down menu appears and a list of options is available for selection. For illustrative purposes, the list of options includes an option to "add / remove trailer" and an option to "select trailer 22".

[0058] Reference now Figure 4A and 4B, the user has selected the option "Select Trailer 22", and a list of trailer profiles ("Profile 1", "Profile 2", "Profile 3") that have been saved in the memory hardware 52 is displayed. The user may then select a trailer profile that corresponds to the trailer 22 that is currently coupled to the towing hitch 18 or is intended to be coupled to the towing hitch 18. Upon selecting a trailer profile, the towing system 32 adjusts vehicle operating parameters by processing trailer information associated with the selected trailer profile. In such an aspect, the towing system 32 may be configured to display a confirmation that the selected trailer profile is the appropriate trailer profile when the sensor 36 detects that the trailer 22 is coupled to the towing hitch 18. Additionally, the controller 38 may process the vehicle information to confirm that the selected trailer 22 is actually coupled to the towing hitch 18. For example, if the selected trailer 22 is a horse trailer 22 having a trailer weight of 1,500 pounds and a cargo weight of 1,000 pounds, but the sensor 36 detects that the trailer weight is 500 pounds and the cargo weight is 200 pounds, the controller 38 may prompt the user to confirm that the selected trailer 22 is the actual trailer 22 coupled to the towing hitch 18. It should be understood that other vehicle information may be used to display the prompt to confirm the selected trailer 22, such as the output torque of the engine, the operation of the transmission, etc., where the engine and transmission behave in a manner inconsistent with the trailer information of the selected trailer profile.

[0059] Reference now FIG. 5A to FIG. 8 The traction system 32 is also configured to allow the user to add and remove trailer profiles. Figure 5A and Figure 5B , the display of the mobile device 44 and the display of the head unit 34 include two prompts. One of the prompts is "Add trailer" and the other prompt is "Remove trailer". Now refer to Fig. 6A and 6B , the user has selected the "Remove Trailer" prompt, and a list of trailer profiles is displayed. The user can simply select a trailer profile for removal. The controller 38 can also be configured to display a confirmation of the selected trailer profile to be deleted. For example, a display stating "Confirm Delete" can appear after a trailer profile is selected, and upon touching the display, the controller 38 deletes the selected trailer profile from the memory hardware 52. Such a feature can help reduce the storage requirements of the memory hardware 52.

[0060] Reference now Fig. 7A and 7B, the user has selected the option "Add Trailer" and a list of trailer information is displayed. For illustrative purposes, the list of trailer information is shown as "Trailer Weight", "Trailer Width", "Trailer Height", "Trailer Length", and "Cargo Weight". The user can simply select the information and enter the information using the mobile device 44 or the head unit 34, whereby the information is stored and saved in the memory hardware 52. It should be understood that in the event that the mobile device 44 is used to add a trailer profile and enter trailer information or remove a trailer profile, the information is updated in the head unit 34, the mobile device 44, and the host program 40.

[0061] Reference now Figure 8 , the operation of the traction system 32 is provided. For the purpose of illustration, the operation of the traction system 32 will be described in the context of the mobile device 44 and / or the head unit 34 being used to confirm, select and add information (as appropriate). The vehicle 10 may include an input (not shown), such as a button or dial disposed on the dashboard, steering wheel, etc., for selecting vehicle operating parameters. For example, a user may actuate a button on the dashboard to select between a conventional navigation mode and a trailer navigation mode, or between a conventional hauling mode or a trailer hauling mode. The head unit 34 may also be used to select vehicle operating parameters. In one aspect, the vehicle 10 may be configured to maintain the last mode in which the vehicle was when the vehicle 10 was turned off. For example, if the vehicle 10 was in the trailer navigation mode when it was turned off, the vehicle 10 remains in the trailer navigation mode when it is reopened. In the conventional navigation mode, a route may be generated based on factors such as the shortest distance to the desired destination, the shortest time to the destination, and avoiding tolls to the destination. In the trailer navigation mode, a route may be generated based on the same factors used in the conventional navigation mode and the trailer information to assist the user in reaching the destination safely.

[0062] The harness of the trailer 22 is connected to the vehicle 10, and the controller 38 determines whether a connection signal indicating that the harness is connected is received. The controller 38 transmits the connection signal to various vehicle control units through the gateway of the controller area network 54. The sensor 36 detects that the trailer 22 has been connected to the towing hitch 18. In the case where the user has not yet selected a trailer profile, the controller 38 can process the data from the sensor 36 to select a trailer profile that matches the information detected by the sensor 36. For example, in the aspect that the sensor 36 detects the load on the hitch, the controller 38 can process the load to calculate the trailer weight and select a trailer profile that matches the calculated trailer weight. In the case where the sensor 36 is a sensor unit having a first sensor 36a and a second sensor 36b, the sensor 36 is configured to detect both the load and the width and / or height of the trailer 22, and the controller 38 selects a trailer profile that matches the calculated weight, the detected width, and the detected height of the trailer 22. The controller 38 can also be configured to display a prompt requesting the user to confirm the selected trailer profile.

[0063] The sensor 36 determines whether the trailer 22 is coupled to the towing hitch 18 or disconnected from the towing hitch 18, and the controller 38 transmits the coupling signal and the disconnection signal to various vehicle control units. For example, the controller 38 transmits the coupling signal to the navigation control unit 56A and the body control module 58. The navigation control unit 56A determines the current navigation mode of the vehicle 10. When the trailer 22 is coupled and the current navigation mode is the trailer navigation mode, the controller 38 keeps the vehicle 10 operating in the trailer navigation mode. When the trailer 22 is coupled and the current navigation mode is the conventional navigation mode, the controller 38 instructs the navigation control unit 56A to change the navigation mode to the trailer navigation mode. In the trailer navigation mode, the navigation control unit 56A processes the trailer information to generate a route for the vehicle 10. The route is configured to avoid roads that may have a weight limit that exceeds the combined trailer weight and cargo weight, avoid roads with underpasses or bridges that are less than the height of the trailer 22, and identify turns and corners in the route that require the vehicle 10 to slow down to safely navigate through the turns and corners.

[0064] If the sensor 36 detects that the trailer 22 is not coupled to the towing hitch 18, the controller 38 transmits an uncoupled signal to the navigation control unit 56A, and the navigation control unit 56A determines the current navigation mode of the vehicle 10. If the current navigation mode of the vehicle 10 is in the regular navigation mode, the navigation control unit 56A maintains the vehicle 10 in the regular navigation mode. If the current navigation mode of the vehicle 10 is in the trailer navigation mode, the navigation control unit 56A changes the vehicle 10 to the regular navigation mode. Thus, a route is generated without processing trailer information.

[0065] The controller 38 may also be configured to send an engage signal and a disengage signal to the body control module 58, which may be responsible for determining the hauling mode of the vehicle 10 and the cruise control function of the vehicle 10. If the controller 38 transmits the disengage signal, the body control module 58 may determine the current hauling mode of the vehicle 10. If the vehicle 10 is in the trailer hauling mode, the controller 38 instructs the body control module 58 to change the hauling mode to the regular hauling mode.

[0066] When the controller 38 transmits the connection signal to the body control module 58, the body control module 58 determines whether the cruise control is on or off. If the cruise control is on, the controller 38 can instruct the body control module 58 to automatically turn off the cruise control or send an alert to the user to turn off the cruise control. For example, the controller 38 can generate a display on the head unit 34 to warn the user to turn off the cruise control. The controller 38 can process the trailer information to determine whether to automatically turn off the cruise control or send an alert. For example, if the trailer information exceeds a predetermined value (such as a trailer length greater than 15 feet, a cargo weight greater than 1,500 pounds, or a trailer weight greater than 2,000 pounds), the controller 38 can automatically turn off the cruise control.

[0067] The body control module 58 may also process the coupling signal to determine the hauling mode of the vehicle 10. If it is determined that the vehicle 10 is in the trailer hauling mode, the controller 38 instructs the body control module 58 to remain in the trailer hauling mode. If it is determined that the vehicle 10 is in the regular hauling mode, the controller 38 may instruct the body control module 58 to automatically switch the hauling mode from the regular hauling mode to the trailer hauling mode, or send an alert to the user to manually switch the hauling mode to the trailer hauling mode. The controller 38 may process the trailer information to determine whether to automatically switch the hauling mode from the regular hauling mode to the trailer hauling mode or send an alert. For example, in the event that the trailer information exceeds a predetermined value (such as a cargo weight greater than 1,500 pounds or a trailer weight greater than 2,000 pounds), the controller 38 may automatically switch the hauling mode to the trailer hauling mode.

[0068] In yet another aspect of the towing system 32, the controller 38 may process trailer information to adjust the brake coefficient. As is well known, the brake coefficient affects the stopping distance of the vehicle 10. Currently, the user can manually adjust the brake coefficient by setting a value for the brake 16. For example, the vehicle 10 may provide the user with a range of 1-10, where one (1) is the minimum coefficient and ten (10) is the maximum coefficient. The user may select a value by testing the brake 16 and setting the value that provides the desired output. For example, if the user feels that the trailer 22 is pushing the vehicle 10 when braking, the user may increase the brake coefficient. In the event that the user feels that the trailer 22 is pulling the vehicle 10 when braking, the user may decrease the brake coefficient. The controller 38 may be configured to process trailer information to calculate the brake coefficient and adjust the manually set brake coefficient to the calculated brake coefficient when the sensor 36 detects that the trailer 22 is coupled to the towing hitch 18. For example, if the cargo weight and the trailer weight exceed a predetermined value, such as 5,000 pounds, the brake coefficient may be increased.

[0069] The towing system 32 may also be configured to process trailer information to provide a brake alert. For example, the towing system 32 may process the weight of the trailer 22 and the weight of the cargo along with map information or gyroscope information to warn the user that the vehicle 10 may be parked in an area that is too steep for the load of the trailer 22. As an example, if the vehicle 10 is parked at a 30 degree incline and coupled to a trailer 22 having a combined weight of 10,000 pounds, the controller 38 may display an alert on the head unit 34. Thus, the user may find a parking spot that is more suitable for pulling the 10,000 pound vehicle 10.

[0070] Reference now Fig. 9 , describes a method 100 for adjusting operating parameters of a vehicle 10 by processing trailer information. The method 100 may be implemented by a software application having a controller 38, which processes vehicle information and trailer information to adjust operating parameters of the vehicle 10. At box 102, the method 100 includes receiving a signal indicating that the trailer 22 is electrically connected to the vehicle 10, which may be achieved by connecting a trailer harness to the vehicle 10. At box 104, the method 100 includes detecting whether the trailer 22 is coupled to the towing hitch 18 of the vehicle 10, which may be achieved by a sensor 36 configured to detect a load on the towing hitch 18. At box 106, the method 100 includes processing the trailer information to change the operating parameters of the vehicle 10 to predetermined operating parameters if the trailer 22 is coupled to the towing hitch 18. The trailer information may be at least one of a trailer type, a trailer length, a trailer height, a trailer width, a trailer weight, and a cargo weight.

[0071] At box 108A, the predetermined operating parameter of the vehicle 10 is the hauling mode. For example, the vehicle 10 may be in a regular hauling mode or a trailer hauling mode. In one aspect of the method 100, the vehicle 10 automatically changes from the regular hauling mode to the trailer hauling mode when the trailer 22 is coupled to the towing hitch 18. However, the method 100 may include determining whether the vehicle 10 is in the regular hauling mode or in the trailer hauling mode, and alerting the user that the vehicle 10 is in the regular hauling mode when the trailer 22 is coupled to the hitch.

[0072] At box 108B, the predetermined operating parameter of the vehicle 10 is the cruise control function of the vehicle 10. At box 108B, the method 100 includes determining whether the cruise control is on, and automatically turning off the cruise control function if the trailer 22 is coupled to the towing hitch 18. However, the method 100 may include providing a notification to the user that the cruise control is on and suggesting to the user that the cruise control be turned off. This may be accomplished by a text display on the head unit 34 of the vehicle 10.

[0073] At box 108C, the predetermined operating parameter is a braking coefficient of the vehicle 10. In such an aspect, the braking coefficient is manually set by a user, and the method 100 includes processing trailer information to adjust the braking coefficient set by the user. In one aspect, the braking coefficient is calculated using trailer information (such as the combined weight of the trailer 22 and the cargo), and the method 100 automatically adjusts the braking coefficient to the calculated braking coefficient. In another aspect, the method 100 includes notifying the user of the calculated braking coefficient, and the user can choose to accept the calculated braking coefficient.

[0074] At box 108D, the operating parameter is a navigation route, and the controller 38 generates a navigation route by processing the trailer information. For example, the trailer height can be processed to identify any underpasses or tunnels that may not accommodate the height of the trailer 22, and a route is generated that bypasses the identified underpasses and / or tunnels. In addition, the trailer width and length can be processed to locate turns that may require the vehicle 10 to significantly reduce its speed to safely navigate through the turn. It should be understood that the controller 38 can generate multiple routes for the user to select.

[0075] Accordingly, a system 32 and method 100 are provided for adjusting operating parameters of the vehicle 10 by processing trailer information. The system 32 and method 100 optimize the performance of the vehicle 10 by taking into account trailer information that may affect the operation of the vehicle 10, such as braking coefficients, the driving mode of the vehicle 10, and the route traveled by the vehicle 10. In addition, the system 32 and method 100 are configured to adjust operating parameters of the vehicle 10 based on the trailer information of the selected trailer profile, and thus, the driving experience is tuned to the towed trailer 22.

[0076] Many embodiments have been described. However, it should be understood that various modifications can be made without departing from the spirit and scope of the present disclosure. Therefore, other embodiments are within the scope of the appended claims.

[0077] The foregoing description is provided for the purpose of illustration and description. It is not intended to be exhaustive or to limit the present disclosure. The individual elements or features of a particular configuration are generally not limited to that particular configuration, but are interchangeable where applicable and can be used in a selected configuration, even if not specifically shown or described. It can also be varied in many ways. Such variations should not be considered as departing 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 adjusting operating parameters of a vehicle, the vehicle comprising a hitch configured to couple with a trailer, the system adjusting the operating parameters of the vehicle by processing trailer information, the system comprising: a sensor for detecting a trailer coupled to a hitch of the vehicle; as well as A controller comprising data processing hardware and memory hardware, wherein the memory hardware stores instructions which, when executed on the data processing hardware, cause the data processing hardware to perform operations comprising: If the trailer is coupled to the hitch, the trailer information is processed to change a vehicle operating parameter to a predetermined operating parameter, wherein the vehicle operating parameter is a vehicle component that affects at least one of control and travel of the vehicle. 2 . The system of claim 1 , wherein the trailer information is at least one of trailer type, trailer length, trailer height, trailer width, and trailer weight.

3. The system of claim 2, wherein the sensor is configured to detect the trailer weight.

4. The system of claim 2, wherein the sensor is configured to detect a width of the trailer and a height of the trailer.

5. The system of claim 4, wherein the sensor is an optical device. The system of claim 2 , wherein the predetermined operating parameter is a driving mode. The system of claim 6 , wherein the driving mode is a trailer mode.

8. The system of claim 7, wherein the controller turns off a cruise control function of the vehicle if the trailer is coupled to the hitch.

9. The system of claim 2, wherein the predetermined operating parameter is a navigation route, and the controller generates the navigation route by processing the trailer information.

10. The system of claim 2, wherein the predetermined operating parameter is a braking coefficient.

Images