Method and apparatus for configuring the return angle of a steering wheel
By combining the driver's torque input and path following request with a virtual reinforced curve steering controller, the final steering angle is generated, which solves the problem of unstable steering control in autonomous driving mode and enables the vehicle to travel along the desired trajectory and provide an intuitive steering feel.
Patent Information
- Application Number
- CN202610623446.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2025-05-15
- Filing Date
- 2026-05-08
- Publication Date
- 2026-11-17
AI Technical Summary
Existing technologies struggle to effectively combine the driver's steering wheel torque input with the path-following controller's angle request in autonomous driving mode, leading to unstable and delayed steering control.
The Virtual Enhancement Curve (VBC) steering controller generates incremental angle requests by recognizing the driver's torque input and combines them with path following (PF) angle requests to generate a final steering angle request, thereby achieving steering wheel return to center (R2C) angle offset.
It provides robust steering control, ensuring the vehicle follows the desired trajectory. The driver's torque input is intuitive, avoiding the potential delay when making minor adjustments in autonomous driving mode, and providing a clear steering feel.
Smart Images

Figure CN123104758A_ABST
Abstract
Description
Technical Field
[0001] This disclosure relates generally to vehicle control, and more specifically to methods and apparatus for configuring the return-to-center (R2C) angle of a steering wheel. Background Technology
[0002] In recent years, some vehicles have been equipped with automated driving systems that can automatically drive or manipulate the vehicle in autonomous driving mode. These systems include path-following controllers that analyze the road ahead (e.g., using one or more cameras and / or map-based systems) and determine, based on the analysis, how to steer the vehicle along a target path. The path-following controller determines the torque to be applied to the steering system by the steering motor to steer the vehicle. In some cases, even in autonomous driving mode, the driver may still need to manually steer the vehicle. Summary of the Invention
[0003] An example vehicle disclosed herein includes: a steering wheel; a steerable wheel operably coupled to the steerable wheel; and a steering motor for being activated when the vehicle is in autonomous driving mode to control the steering angle of the steering wheel. The vehicle also includes a steering controller comprising instructions and a programmable circuitry system for executing the instructions to: access a path following (PF) angle request, the PF angle request including curvature; determine a return-to-center (R2C) angle based on the PF angle request and vehicle speed; and cause the steering motor to bias the steering angle toward the R2C angle in response to the steering wheel receiving a torque input from the driver.
[0004] This document discloses an example non-transitory machine-readable storage medium comprising instructions for causing a programmable circuit system to perform at least the following operations: identifying a trajectory plan for a vehicle; determining a return-to-center (R2C) angle of a steering wheel based on the trajectory, the R2C angle being non-zero; and causing a steering motor to bias the steering wheel toward the R2C angle in response to the steering wheel receiving a torque input from the driver.
[0005] The example methods disclosed herein include: identifying a vehicle trajectory plan; determining a return-to-center (R2C) angle based on the trajectory plan; and causing the steering motor to offset the steering angle toward the R2C angle in response to the steering wheel receiving a torque input from the driver. Attached Figure Description
[0006] Figure 1 An example vehicle in which the example methods and devices disclosed herein may be implemented is shown.
[0007] Figure 2Ayes Figure 1 A schematic diagram of an example steering system for an example vehicle, the example steering system including an example steering controller for steering the vehicle in autonomous driving mode.
[0008] Figure 2B yes Figure 1 A schematic diagram of another example steering system for an example vehicle, the example steering system including an example steering controller for steering the vehicle in autonomous driving mode.
[0009] Figure 3 yes Figures 2A to 2B The block diagram of the example return-to-center (R2C) angle determination circuit system for the example steering controller.
[0010] Figure 4 yes Figures 2A to 2B A block diagram of an example steering controller.
[0011] Figure 5 yes Figures 2A to 2B The example steering controller is shown in the block diagram of the example Virtual Enhancement Curve (VBC) circuit system.
[0012] Figure 6 yes Figures 2A to 2B A block diagram of an example angle hybrid circuit system for an example steering controller.
[0013] Figure 7 It shows the result of Figures 2A to 2B The example of the final angle request generation operation performed by the example steering controller.
[0014] Figure 8 This is a flowchart illustrating example machine-readable instructions and / or example operations that can be executed, instantiated, and / or implemented by an example programmable circuit system. Figure 3 The R2C angle determination circuit system.
[0015] Figure 9 This indicates that it can be implemented by executing, instantiating, and / or carrying out by the example programmable circuit system. Figures 2A to 2B , Figure 3 , Figure 4 , Figure 5 and / or Figure 6 The flowchart shows example machine-readable instructions and / or example operations of an example steering controller.
[0016] Figure 10 This indicates that it can be implemented by executing, instantiating, and / or carrying out by the example programmable circuit system. Figures 2A to 2B , Figure 3 , Figure 4 , Figure 5 and / or Figure 6The flowchart shows example machine-readable instructions and / or example operations of an example steering controller.
[0017] Figure 11 This is a block diagram of an example processing platform, which includes components structured for executing, instantiating, and / or implementing example machine-readable instructions and / or executing... Figure 8 , Figure 9 and / or Figure 10 Example operations to implement Figures 2A to 2B , Figure 3 , Figure 4 , Figure 5 and / or Figure 6 Example of a programmable circuit system for a steering controller.
[0018] Generally, the same reference numerals will be used throughout the accompanying drawings and written description to refer to the same or similar parts. The drawings are not necessarily drawn to scale. Detailed Implementation
[0019] Most vehicles include a power steering system, which uses a motor (such as a hydraulic or electric motor) to assist in applying torque to the steering system and reduce the torque input required from the driver to steer the vehicle. In such vehicles, the electronic control unit uses an 'assistance curve' to determine the amount of auxiliary torque to be applied to the motor based on the driver's torque input to the steering wheel. The assist curve defines the static relationship between the input torque applied by the driver and the auxiliary torque generated by the motor at the vehicle's steerable wheels.
[0020] The vehicle disclosed herein also possesses autonomous driving capabilities, referred to herein as autonomous driving mode, assisted driving mode, path-following mode, or automated driving mode. When the vehicle is in autonomous driving mode, the path-following (PF) circuitry of the electronic control unit (e.g., the PF controller) determines the vehicle's target path and provides a torque request to the motor to automatically control the vehicle's yaw direction, thereby steering the vehicle along the target path. The PF circuitry receives sensor feedback (such as yaw values) and uses this feedback to further steer the vehicle along the target path. Additionally, an auxiliary torque from an enhancement curve (e.g., based on the input torque from the driver) can be superimposed on the torque request from the PF circuitry. This allows the driver to still provide input and at least partially steer the vehicle while it is in autonomous driving mode. Similar to power steering, the input torque applied to the steering wheel is equivalent to the larger torque to be applied by the motor via the enhancement curve. The torque value from the enhancement curve is combined with the torque input to the motor from the PF circuitry to steer the vehicle.
[0021] To provide more stringent and robust lateral control, the vehicles disclosed herein utilize steering angle docking with the steering wheel input, rather than torque docking. In some of the disclosed examples, the PF circuitry calculates the steering angle required to keep the vehicle on its path and then converts the steering angle into torque to be applied to the steering wheel by the motor to achieve the steering angle. As used herein, the terms steering angle and steering wheel angle (SWA) are used interchangeably and refer to the angle at which the steering wheel has been rotated relative to a neutral or central position (e.g., by the driver). As used herein, the term road wheel angle (RWA) refers to the angle at which a steerable wheel (such as the front two wheels) has been rotated relative to a neutral or central position (e.g., turned left or right). Many of the example operations disclosed herein calculate the steering angle used to turn the vehicle's steering wheel and thus steer the vehicle. However, in most vehicles, the steering wheel is mechanically connected to the front wheels via a fixed gear relationship (e.g., via rack and pinion). This gear relationship can be implemented as a fixed steering ratio or a variable steering ratio. For example, for every 12° to 20° rotation of the steering wheel, the front wheels rotate 1°, and vice versa. Therefore, any example operation disclosed herein can instead be described as calculating the road wheel angle, since the steering angle is equivalent to the road wheel angle, and vice versa.
[0022] In some examples, the PF circuitry provides a PF angle request corresponding to the target steering angle. However, this angled interface between the PF circuitry and the steering gear (e.g., a steerable wheel, rack and pinion, etc.) makes it difficult to superimpose the driver input torque onto the PF angle request. In other words, the auxiliary torque from the enhancement curve cannot be easily combined with the PF angle request. Therefore, in these angle-based following platforms, the enhancement curve is typically disabled during autonomous driving mode, resulting in no torque superposition between the torque output of angle control (e.g., the PF circuitry) and the enhancement curve output. This increases the robustness of the vehicle's path-following operation by eliminating amplified torque noise from the input torque. However, this also represents a need to superimpose the driver input at the angle request level, rather than the torque level.
[0023] This document discloses an example steering controller and associated method for determining a steering angle (referred to herein as a VBC angle request) based on a driver torque input using a Virtual Enhancement Curve (VBC). In some examples, the steering controller determines a differential or incremental steering angle based at least on the driver torque input and adds the differential angle to the current SWA to generate the VBC angle request. The example steering controller combines the VBC angle request with a PF angle request to generate a final steering angle request. Therefore, the steering angle is determined or output using the VBC instead of a torque-based enhancement curve output, and then said steering angle is combined with the PF angle request. The angle controller of the example steering controller translates the final steering angle request into a final torque request, which the steering system's motor uses to adjust the steering wheel angle to steer the vehicle along the desired path.
[0024] In some examples, the steering controller includes a VBC circuitry and / or implements a VBC method to enable manual steering while still in autonomous driving mode. The example steering controllers disclosed herein use input torque (e.g., torsion bar (T-bar) torque) to generate an incremental angle, add the incremental angle to the current SWA, and generate a VBC request, which is then combined with a PF request to generate a final angle request for the angle controller. In some examples, the torque source is the raw T-bar torque, rather than a filtered torque, such as driver torque based on a Kalman filter. That is, the examples disclosed herein use the raw torque input to generate the VBC angle request because the hysteresis associated with filtered torque would produce a sluggish steering feel when using VBC. The examples disclosed herein also combine the VBC angle request with the PF angle request to generate the final angle request. In some examples, the VBC angle request is combined with the PF angle request after appropriate adjustment.
[0025] The examples disclosed herein provide methods and apparatus for configuring a steering wheel return-to-center (R2C) angle that offsets the steering wheel toward a desired trajectory (e.g., trajectory planning, target path) recognized by the autonomous driving system. The examples disclosed herein result in torque sensation during autonomous driving based on a combination of return-to-center pushback and through pushback from a PF angle request. This combination of torque sensation can provide the driver with an intuitive steering feel, where the torque applied by the driver while cornering is used solely to generate and manage the offset, rather than to maintain the corner. Furthermore, the examples disclosed herein provide active R2C determination that provides a clear steering feel and avoids potential delays when adjusting the final angle request with small adjustments in an engaged interactive state.
[0026] As used in this patent, a statement that any part (e.g., layer, film, region, area, or plate) is located on another part in any way (e.g., positioned on it, situated on it, disposed on it, or formed on it, etc.) indicates that the referenced part is in contact with the other part, or that the referenced part is above the other part, wherein one or more intermediate parts are located between them.
[0027] As used herein, unless otherwise indicated, a connection reference (e.g., attachment, coupling, linking, and linking) may include intermediate components between the elements referenced by the connection reference and / or relative movement between these elements. Therefore, a connection reference does not necessarily imply that two elements are directly connected and / or fixed to each other. As used herein, a statement that any part is “in contact” with another part is defined as meaning that there is no intermediate part between the two parts.
[0028] Unless otherwise specifically stated, descriptors such as “first,” “second,” and “third” used herein do not in any way impose or otherwise indicate any meaning of priority, physical order, arrangement in a list, and / or sorting, but are merely used as labels and / or arbitrary names to distinguish elements in order to facilitate understanding of the disclosed examples. In some examples, the descriptor “first” may be used to refer to an element in the detailed description, while different descriptors such as “second” or “third” may be used in the claims to refer to the same element. In such cases, it should be understood that such descriptors are only used to clearly identify those elements within the context of the discussion (e.g., within the claims), in which those elements may otherwise share the same name, for example.
[0029] As used herein, “approximately” and “about” modify their subject / value to identify the potential presence of variations that occur in real-world applications. For example, “approximately” and “about” may modify dimensions that may be imprecise due to manufacturing tolerances and / or other real-world defects, as will be understood by one of ordinary skill in the art. For example, unless otherwise specified in the following description, “approximately” and “about” may indicate that such dimensions are within tolerances of + / - 10%.
[0030] As used herein, the phrase “to communicate” (including its variations) encompasses direct communication and / or indirect communication via one or more intermediate components, and does not require direct physical (e.g., wired) communication and / or continuous communication, but additionally includes selective communication at periodic intervals, scheduled intervals, aperiodic intervals and / or one-off events.
[0031] As used herein, “programmable circuit system” is defined to include: (i) one or more special-purpose circuits (e.g., application-specific integrated circuits (ASICs)) that are structured to perform specific operations and include one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors); and / or (ii) one or more general-purpose semiconductor-based circuits that can be programmed with instructions to perform specific functions and / or operations and include one or more semiconductor-based logic devices (e.g., electrical hardware implemented by one or more transistors). Examples of programmable circuit systems include programmable microprocessors, such as a central processing unit (CPU) capable of executing a first instruction to perform one or more operations and / or functions; an FPGA programmable by a second instruction to cause configuration and / or structured field-programmable gate array (FPGA) to instantiate one or more operations and / or functions corresponding to the first instruction; a graphics processing unit (GPU) capable of executing a first instruction to perform one or more operations and / or functions; a digital signal processor (DSP) capable of executing a first instruction to perform one or more operations and / or functions; an XPU; a network processing unit (NPU); and one or more microcontrollers and / or integrated circuits (such as application-specific integrated circuits (ASICs)) capable of executing a first instruction to perform one or more operations and / or functions. For example, an XPU can be implemented by a heterogeneous computing system that includes a variety of types of programmable circuit systems (e.g., one or more FPGAs, one or more CPUs, one or more GPUs, one or more NPUs, one or more DSPs, etc., and / or any combination thereof) and orchestration techniques (e.g., application programming interfaces (APIs)) that can assign computational tasks to any one or more of the various types of programmable circuit systems that are suitable and available for performing the computational tasks.
[0032] As used herein, an integrated circuit / circuit system is defined as one or more semiconductor packages containing one or more circuit elements, such as transistors, capacitors, inductors, resistors, current paths, diodes, etc. For example, an integrated circuit can be implemented as one or more of an ASIC, FPGA, chip, microchip, programmable circuit system, semiconductor substrate connecting multiple circuit elements, system-on-a-chip (SoC), etc.
[0033] As used herein, the terms “desired trajectory,” “trajectory planning,” and “target path” encompass a path to be followed by a vehicle, determined based on at least one of (i) a reference path or (ii) at least the vehicle’s current trajectory (e.g., instantaneous trajectory) and a look-ahead distance that may be based on the vehicle’s speed (e.g., a predetermined look-ahead distance). The reference path can be a time- and vehicle-position-independent, map-based or vision-based path to be followed. For example, when a vehicle is in lane-keeping mode or state, where the maneuver being performed keeps the vehicle in the same lane it currently occupies, “trajectory planning” is based on a reference path rather than the current trajectory or look-ahead distance. Furthermore, when a vehicle is in lane-changing mode or state, “trajectory planning” is based on a reference path, the vehicle’s current trajectory (e.g., instantaneous trajectory), and a look-ahead distance.
[0034] Figure 1 An example vehicle 100 in which the examples disclosed herein can be implemented is shown. The example vehicle 100 includes an example steering controller, shown in further detail herein, operable to automatically steer and / or guide the vehicle along a target path. This automated operation is referred to herein as path following (PF), assisted driving mode, or autonomous driving mode or operation. In some examples, the driver can activate and deactivate the assisted driving mode by pressing a button and / or interacting with a display in the vehicle. During assisted driving mode, the steering controller of vehicle 100 generates a PF angle request (e.g., independent of driver input) to guide vehicle 100 along the target path. If the driver applies torque input to the steering wheel of vehicle 100, the steering controller generates a VBC angle request. The steering controller combines the VBC angle request with the PF angle request to generate a final angle request and converts the final angle request into a torque request or output for adjusting the steering angle of vehicle 100. Additionally, the steering controller determines a return-to-center (R2C) angle to bias the steering angle of vehicle 100 to the desired trajectory, as discussed in further detail herein. For example, the R2C angle can cause vehicle 100 to follow a curvature associated with the desired trajectory, rather than simply returning the vehicle's heading to a straight or neutral position. The following is illustrated in Figures 2 to 3. Figure 9 To provide a further description of the steering controller of vehicle 100. Figure 1 The example of vehicle 100 shown is merely one example of a sport utility vehicle (SUV) from which the examples disclosed herein can be implemented. However, the examples disclosed herein can also be implemented in combination with other types of vehicles (e.g., pickup trucks, sedans, semi-trucks, etc.).
[0035] Figure 2A It is possible Figure 1 A schematic diagram of an example steering system 200 implemented in an example vehicle 100. Figure 2AIn the example shown, the steering system 200 includes: an electronic control unit 202 including a steering controller 204, a steering wheel 206, a steering column 208, a pinion 210, a rack and pinion 212, a steering motor 214, a housing 216, a first steerable wheel 218, a second steerable wheel 220, a torque sensor 222, and a SWA sensor 224. The example steering wheel 206 is mechanically connected to the first steerable wheel 218 and the second steerable wheel 220 (e.g., in vehicle 100...). Figure 1 (The front wheels). Specifically, the steering wheel 206 is connected to the first steerable wheel 218 and the second steerable wheel 220 via the steering column 208, pinion 210 and rack 212. Therefore, in Figure 1 When the driver of vehicle 100 inputs torque to adjust the SWA of steering wheel 206, the steering angle of the first steerable wheel 218 and the second steerable wheel 220 is correspondingly adjusted (e.g., turned left or right). Rack 212 and pinion 210 may implement a fixed gear ratio or a variable gear ratio. In some examples, the steering column is a single shaft extending between steering wheel 206 and pinion 210. In other examples, steering column 208 is a mechanical linkage comprising two or more interconnected shaft segments. For example, steering column 208 may include a first steering shaft coupled to a second steering shaft via a universal joint (universal joint). Therefore, steering column 208 may be straight and / or angled between steering wheel 206 and steerable wheels 218, 220. In some examples, vehicle 100 includes, as in combination... Figure 2B The steer-by-wire system under discussion.
[0036] exist Figure 2A In the illustrated example, pinion 210 is coupled to and / or meshes with rack 212. For example, the teeth of pinion 210 mesh with the teeth of rack 212. Therefore, when pinion 210 rotates based on the driver's input torque to steering wheel 206, rack 212 translates laterally relative to steering column 208. In some examples, pinion 210 is positioned within housing 216. In some examples, pinion 210 is positioned outside housing 216.
[0037] exist Figure 2AIn the illustrated example, the steering system 200 includes a motor 214. The motor 214 is operatively coupled to a steering wheel 206 and a first steerable wheel 218 and a second steerable wheel 220. For example, the motor 214 may be coupled to a rack and pinion 212. When activated, the motor 214 causes the rack and pinion 212 to move or translate, thereby causing the steering wheel 206 and the steerable wheels 218, 220 to rotate or angle. Thus, the motor 214 operates to adjust the steering angle of the steering wheel 206, and therefore also adjusts the road wheel angles of the first steerable wheel 218 and the second steerable wheel 220 to steer the vehicle 100. In some examples, the motor 214 may be used to provide power steering assistance. For example, in conventional driving mode, based on the torque input to the steering wheel 206, the electronic control unit 202 may activate the motor 214 to provide additional torque assistance for steering the vehicle 100. Additionally, when the vehicle 100 is in an assisted driving mode, the motor 214 may be activated to control the steering angle of the steering wheel 206. The steering controller 204 can also control the motor 214 to cause the steering wheel 206 to be offset toward an R2C angle associated with the trajectory planning or reference path of the vehicle 100. As discussed in further detail herein, the steering controller 204 can provide the motor 214 with a PF angle request and / or torque request so that the motor 214 adjusts the steering angle accordingly.
[0038] Example steering controller 204 can operate in assisted driving mode to control motor 214 and adjust the steering angle of vehicle 100, and its example operation is disclosed in further detail herein. Figure 2A The steering controller 204 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by a programmable circuit system (such as a central processing unit (CPU) that executes first instructions). Alternatively or concurrently, Figure 2A The steering controller 204 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA), the FPGA being structured and / or configured to perform operations corresponding to the first instruction in response to the execution of the second instruction. It should be understood that... Figure 2A Some or all of the circuit system can therefore be instantiated at the same or different times. Figure 2A Some or all of the circuitry can be instantiated, for example, in one or more threads that execute concurrently on hardware and / or serially on hardware. Furthermore, in some examples, Figure 2A Some or all of the circuitry in the system can be implemented by executing instructions through a microprocessor circuitry and / or performing operations through an FPGA circuitry to implement one or more virtual machines and / or containers.
[0039] In some examples, Figure 2A The steering controller 204 includes instructions and a programmable circuitry system for executing the instructions to determine an R2C angle, which enables the vehicle to respond appropriately to different driving maneuvers. Utilizing the R2C angle helps reduce the delay in returning to the desired trajectory after performing an evasive maneuver. Furthermore, the steering controller 204 can adjust the steering wheel angle at least in part based on the determined R2C angle. In some examples, the steering controller 204 can adjust the steering wheel angle based on the determined R2C angle and... Figure 1 The example vehicle 100's steering wheel 206 torque input is used to generate a VBC angle request. Additionally, the steering controller 204 determines the angle blending weights based on the torque input and the vehicle 100's speed. The example steering controller 204 can determine the final angle request based on a combination of the VBC angle request, the PF angle request, and the angle blending weights. The example steering controller 204 converts the final angle request into a torque request for adjusting the vehicle 100's steering angle. The steering controller 204 can determine the R2C angle request based on the PF angle request, torque input, vehicle speed, vehicle configuration (e.g., steering ratio, wheelbase, etc.), and / or the maneuver to be performed by the vehicle 100, as discussed in further detail below. The following section combines... Figures 3 to 11 This section provides a further description of the structure and operation of the steering controller 204.
[0040] exist Figure 2A In the example shown, the steering system 200 includes a torque sensor 222 that detects or measures the input torque on the steering wheel 206. For example, when the driver is... Figure 1 When the vehicle 100 is in autonomous driving mode and the steering wheel 206 is turned or attempted to be turned, the torque sensor 222 detects the torque input. In some cases, the torque applied by the motor 214 is very strong when in autonomous driving mode. However, the torque sensor 222 can still detect the torque applied at the steering wheel 206, which can then be converted into a desired steering angle, as disclosed in further detail herein. In some examples, the steering controller 204 analyzes the sensor output to determine the torque input by the driver. Example torque sensor 222 can detect static torque input at a point in time and / or dynamic torque input over a period of time. Therefore, torque sensor 222 can be a counter-torque sensor including a fixed or non-rotating sensor. Example torque sensor 222 can also be a rotary torque sensor including a rotating sensor that measures the torque input. In some examples, torque sensor 222 is coupled to a torsion bar (T-bar) of steering system 200. The torque on the T-bar can be equivalent to the torque applied at the steering wheel 206. In other examples, the torque sensor 222 is connected to another location on the steering system 200 (e.g., at the steering wheel 206).
[0041] exist Figure 2A In the illustrated example, the steering system 200 includes a SWA sensor 224 that detects the SWA of the steering wheel 206, steering column 208, and / or pinion 210. The example SWA sensor 224 may be coupled to the steering column 208 and / or pinion 210 in a contact or non-contact arrangement. In some examples, the SWA sensor 224 is implemented as a rotary position sensor, which enables precise angular measurements of the steering wheel 206. For example, the SWA sensor 224 may convert a mechanical rotary position into an electrical signal. Thus, the example SWA sensor 224 may correspond to an incremental encoder or rotary encoder that detects changes in the SWA, angular velocity, and / or direction of rotation of the steering wheel 206. In some examples, the steering controller 204 receives the SWA in the form of a digital signal generated by the SWA sensor 224 (e.g., a mechanical motion sensor) based on the movement of the steering wheel 206, steering column 208, and / or pinion 210.
[0042] Figure 2B It is possible Figure 1 A schematic diagram of an example steering system 250 implemented in an example vehicle 100. Figure 2B In the example shown, the steering system 250 includes Figure 2A The system includes an electronic control unit 202, a steering controller 204, a steering wheel 206, a first steerable wheel 218, a second steerable wheel 220, a torque sensor 222, and a SWA sensor 224. The steering system 250 also includes a first steerable wheel motor 252, a second steerable wheel motor 254, a first steerable wheel position sensor 256, a second steerable wheel position sensor 258, and a torque feedback motor 260 (e.g., a steering wheel motor 260).
[0043] exist Figure 2B In the illustrated example, torque sensor 222 and SWA sensor are operatively coupled to steering wheel 206 to detect or measure input torque and SWA of steering wheel 206, respectively. First steerable wheel motor 252 is operatively coupled to first steerable wheel 218 to control its angular position. Second steerable wheel 254 is operatively coupled to second steerable wheel 220 to control its angular position. First steerable wheel motor 252 and second steerable wheel motor 254 may be implemented by electric motors and / or electromechanical actuators. In some other examples, first steerable wheel motor 252 and second steerable wheel motor 254 may be implemented by hydraulic motors.
[0044] exist Figure 2BIn the illustrated example, a first steerable wheel position sensor 256 is operatively coupled to a first steerable wheel 218 and / or a first steerable wheel motor 252. A second steerable wheel position sensor 258 is operatively coupled to a second steerable wheel 220 and / or a second steerable wheel motor 254. The first steerable wheel position sensors 256 and 258 detect or measure the angular position and / or rotational speed of the first steerable wheel 218 and the second steerable wheel 220.
[0045] exist Figure 2B In the example shown, torque feedback motor 260 is operatively coupled to steering wheel 206 to provide torque feedback (e.g., steering feel). For example, torque feedback motor 260 may be implemented by a motor operatively coupled to steering wheel 206.
[0046] exist Figure 2B In the illustrated example, ECU 202 identifies driver input based on signals from torque sensor 222 and / or SWA sensor 224. ECU 202 determines a control signal based on the driver input and transmits the control signal to the first steerable wheel motor 252 and the second steerable wheel motor 254. Alternatively, ECU 202 may determine the control signal based on a final angle request determined by steering controller 204, as discussed in further detail below. Furthermore, ECU 202 may monitor the first steerable wheel position sensors 256, 258 to obtain real-time feedback on the actual position and movement of the steerable wheels 218, 220 to ensure accurate and responsive steering. In some examples, ECU 202 determines the torque feedback (e.g., magnitude and direction) to be provided by torque feedback motor 260, as discussed in further detail below. In some examples, ECU 202 causes torque feedback motor 260 to adjust SWA to match the final angle request in the assisted driving mode.
[0047] Figure 3 It is a block diagram of an ECU 202 that includes an example path planning circuit system 302 associated with vehicle 100 for determining the R2C angle. Figure 3 The ECU 202 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by a programmable circuit system. For example, the programmable circuit system can be implemented by a central processing unit (CPU) that executes first instructions, a field-programmable gate array (FPGA), a programmable logic device (PLD), a general-purpose array logic (GAL) device, a programmable array logic (PAL) device, a complex programmable logic device (CPLD), a simple programmable logic device (SPLD), a microcontroller (MCU), a programmable system-on-a-chip (PSoC), etc. Alternatively or concurrently, Figure 3The ECU 202 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA) (e.g., another form of programmable circuit system) that can be structured and / or configured to perform operations corresponding to the first instruction in response to the execution of the second instruction. It should be understood that... Figure 3 Some or all of the circuit system can therefore be instantiated at the same or different times. Figure 3 Some or all of the circuitry can be instantiated, for example, in one or more threads that execute concurrently on hardware and / or serially on hardware. Furthermore, in some examples, Figure 3 Some or all of the circuitry in the system can be implemented by executing instructions through a microprocessor circuitry and / or performing operations through an FPGA circuitry to implement one or more virtual machines and / or containers.
[0048] In this example, the path planning circuitry 302 is implemented by a portion of the ECU 202 that is different from and communicatively coupled to the path planning circuitry 302 of the steering controller 204, such as in combination. Figure 4 The subject of discussion. For example, Figure 3 The path planning circuit system 302 and / or one or more other parts of the ECU 202 depicted may be implemented by another controller of the ECU 202. Alternatively, Figure 3 The path planning circuit system 302 and / or one or more other parts of the ECU 202 depicted may be implemented by the steering controller 204.
[0049] exist Figure 3 In the illustrated example, the path planning circuit system 302 includes a trajectory source recognition circuit system 306, a trajectory generation circuit system 308, a return-to-center (R2C) angle calculation circuit system 310, and a sample path following (PF) circuit system 316. The path planning circuit system 302 can obtain vehicle speed, which can be measured by the speed sensor 312 of vehicle 100; vehicle configuration parameters (e.g., wheelbase parameters, steering ratio parameters, understeer gradient parameters, etc.), which can be stored in a vehicle configuration database 314; and / or a reference path and location (e.g., geographic location) of vehicle 100, which can be determined by a reference path circuit system 318.
[0050] When vehicle 100 is in assisted driving mode, example reference path circuitry system 318 determines a reference path (e.g., a target path) to be followed by vehicle 100. The reference path is a vector (e.g., an xy vector), which can be used to determine the steering angle of vehicle 100 to steer or guide the vehicle along the target path and / or determine the return-to-center (R2C) angle of steering wheel 206, as discussed in further detail below. Reference path circuitry system 318 may utilize a Global Positioning System (GPS) or similar to identify the position of vehicle 100. Reference path circuitry system 318 transmits the reference path and the position of vehicle 100 to path planning circuitry system 302.
[0051] exist Figure 3 In the illustrated example, example maneuver recognition circuitry 304 determines the type of maneuver to be performed by vehicle 100. Maneuver recognition circuitry 304 may determine whether vehicle 100 is performing an evasive maneuver (e.g., vehicle 100 is in an evasive maneuver mode or state), a lane-keeping maneuver (e.g., vehicle 100 is in a lane-keeping mode or state), or a lane-changing maneuver (e.g., vehicle 100 is in a lane-changing mode or state). In some examples, maneuver recognition circuitry 304 determines the type of maneuver based on input from the driver (e.g., turn signal indication), a reference path and position determined by reference path circuitry 318, and / or input from another component of ECU 202. For example, maneuver recognition circuitry 304 may determine that vehicle 100 will perform a lane-changing maneuver based on a reference path and / or the activation of a turn signal. In some examples, maneuver recognition circuitry 304 identifies an upcoming evasive maneuver based on a reference path.
[0052] In some examples, the maneuver recognition circuitry 304 identifies an impending evasive maneuver in response to a rapid deviation of the reference path from the current heading of vehicle 100 (e.g., sudden movement within the lane). In other examples, the maneuver recognition circuitry 304 may determine that the driver is performing an evasive maneuver in response to detecting a steering wheel acceleration that meets (e.g., greater than, greater than, or equal to) an acceleration threshold. The maneuver recognition circuitry 304 may determine the steering wheel acceleration based on changes in SWA and / or torque input. Specifically, high steering wheel acceleration during an evasive maneuver may cause a torsion of the upper steering column's inertia and exhibit torque input exceeding the driver interaction activation threshold implemented by steering controller 204, resulting in a switch from a fully autonomous driving mode to a shared driving mode between the driver and steering controller 204. In the shared driving mode, the influence of inputs from the PF circuitry 316 on the final steering angle is reduced. However, after the evasive maneuver, inputs from the PF circuitry 316 may still correspond to the driver's intended target path. By detecting evasive maneuvers, the path planning circuitry 302 can cause the steering controller 204 to react appropriately to the evasive maneuver by determining the R2C angle based on the PF angle request. In some examples, the maneuver recognition system 304 is instantiated by a programmable circuitry that executes maneuver recognition instructions and / or is configured to perform actions such as those initiated by... Figure 8 The flowchart represents the operations performed.
[0053] Example path planning circuitry 302 determines the R2C angle to be implemented at steering wheel 206 based on vehicle configuration parameters, vehicle speed, and / or trajectory planning (e.g., target path). The trajectory planning used to determine the R2C angle may correspond to a reference path determined by reference path circuitry 318 and / or another trajectory determined by path planning circuitry 302, as discussed in further detail below. The R2C angle represents the desired SWA associated with the target path that the vehicle 100 is expected to follow. Therefore, even on curved roads or during maneuvers such as lane changes, path planning circuitry 302 provides a natural and intuitive steering feel. Additionally, in assisted driving operations where PF circuitry 316 has low privileges (e.g., at least partially ignored due to driver input), path planning circuitry 302 enables the R2C angle to reflect a non-neutral angle associated with the desired trajectory during non-straight maneuvers.
[0054] The path planning circuit system 302 includes a trajectory source recognition circuit system 306 to determine the source of the trajectory planning (e.g., target path) for the vehicle 100 based on the type of maneuver being performed by the vehicle 100. In some examples, when the maneuver recognition circuit system 304 determines that the vehicle 100 is performing an evasive maneuver, the trajectory source recognition circuit system 306 determines a path following (PF) trajectory. In some examples, the ECU 202 and / or another component of the path planning circuit system 302 determine the PF trajectory. The PF trajectory is represented by a vector (e.g., an xy vector). The trajectory source recognition circuit system 306 transmits the PF trajectory to a PF circuit system 316, which determines a path following (PF) angle request corresponding to the determined trajectory. Furthermore, the trajectory source recognition circuit system 306 causes the PF circuit system 316 to transmit the PF angle to an R2C angle calculation circuit system 310, which uses the PF angle request to determine the R2C angle when the vehicle is performing an evasive maneuver. Therefore, the trajectory source recognition circuit system 306 causes the trajectory planning source to correspond to the PF angle request.
[0055] exist Figure 3 In the illustrated example, when the maneuver recognition circuitry 304 determines that vehicle 100 is performing lane-keeping maneuvers, the trajectory source recognition circuitry 306 causes the R2C angle calculation circuitry 310 to determine the R2C angle based on a reference path. For example, the trajectory source recognition circuitry 306 may relay the reference path and position from the reference path circuitry 318 to the R2C angle calculation circuitry 310. As mentioned above, the reference path corresponds to a trajectory in vector form (e.g., an xy vector) similar to a PF trajectory. However, when vehicle 100 is not currently on the reference path, the reference path vector differs from the PF trajectory vector.
[0056] exist Figure 3 In the illustrated example, when the maneuver recognition circuitry 304 determines that vehicle 100 is performing a lane change maneuver, the trajectory source recognition circuitry 306 causes the trajectory generation circuitry 308 to determine the trajectory plan for vehicle 100. That is, in a lane change state, the trajectory source recognition circuitry 306 triggers the trajectory generation circuitry 308 to determine a trajectory plan different from the PF angle request and reference path. In some examples, the trajectory source recognition circuitry 306 and / or the maneuver recognition circuitry 304 transmit the identified lane change state (e.g., lane change state versus lane keeping state) to the trajectory generation circuitry 308. In some examples, the trajectory source recognition circuitry 306 is instantiated by a programmable circuitry system that executes trajectory source recognition instructions and / or is configured to perform actions such as those initiated by... Figure 8 The flowchart represents the operations performed.
[0057] When vehicle 100 is in assisted driving mode, example path following (PF) circuitry 316 determines a PF angle request, which is used to adjust the steering angle of vehicle 100 to steer vehicle 100 along a target path or guide vehicle along a target path. Figure 3 In this diagram, the PF circuitry 316 is shown separate from the steering controller 204. For example, the PF circuitry 316 may be implemented by another controller of the ECU 202. However, in other examples, the PF circuitry 316 may be part of the steering controller 204. When the driver of vehicle 100 does not interact with the steering wheel 206 during autonomous driving mode (e.g., zero input torque), the PF circuitry 316 controls the yaw, direction, and / or steering angle of vehicle 100. For example, when the driver input torque is zero when vehicle 100 is operating in assisted driving mode, the final angle request may consist solely of the PF angle request. In some examples, the PF circuitry 316 is based on the target path of vehicle 100, the speed of vehicle 100, and... Figure 2A The current steering angle of the steering wheel 206 and / or the expected path of the vehicle 100 determine the PF angle request. The target path determined by the PF circuit system 316 can be map-based and / or vision-based. The path planning circuit system 302 obtains the target path (e.g., a map-based reference path and / or a vision-based reference path) from the PF circuit system 316 and / or another component of the ECU 202. In some examples, the PF circuit system 316 is instantiated by a programmable circuit system that executes PF instructions and / or is configured to perform actions such as those described by the steering wheel 206 and / or the vehicle 100. Figure 8 The operations shown in the flowchart of Figure / 9.
[0058] The path planning circuit system 302 includes a trajectory generation circuit system 308 to determine the trajectory planning of vehicle 100 in response to being triggered by the trajectory source identification circuit system 306. For example, the trajectory generation circuit system 308 may determine the curvature that vehicle 100 will follow in the trajectory planning. In some examples, the trajectory generation circuit system 308 determines the curvature when vehicle 100 is performing a lane change, and refers to the path circuit system 318 to determine the curvature when the vehicle is maintaining the same lane. In some other examples, the trajectory generation circuit system 308 determines the curvature for both lane-keeping and lane-changing states. For example, the trajectory source identification circuit system 306 may transmit the type of maneuver being performed to the trajectory generation circuit system 308. In such examples, the trajectory generation circuit system 308 determines how to determine the curvature based on the type of maneuver being performed.
[0059] When vehicle 100 is about to change lanes, trajectory generation circuitry system 308 calculates a trajectory plan for vehicle 100 based on vehicle 100's current trajectory (e.g., instantaneous trajectory), instantaneous position of vehicle 100, and look-ahead distance (e.g., predetermined look-ahead distance). The look-ahead distance can be a function of time and vehicle speed, such as the distance vehicle 100 will travel in one second at instantaneous vehicle speed. For example, trajectory generation circuitry system 308 can identify the instantaneous trajectory based on the rear axle spatial path. Trajectory generation circuitry system 308 can determine the rear axle spatial path based on information from various sensors (e.g., wheel speed sensors, SWA sensors, accelerometers, yaw rate sensors, GPS, etc.). In some examples, another component of ECU 202 determines the rear axle spatial path, which can be transmitted to trajectory generation circuitry system 308. In some examples, trajectory generation circuitry system 308 can calculate the curvature associated with trajectory planning based on the pure tracking law, as represented in Equations 1 and 2 below: Equation 1: ;as well as Equation 2: .
[0060] In Equation 1, γ is the curvature. It is the forward-looking distance, and θ is the yaw difference. Equation 2 is used to calculate the yaw difference Δθ. In Equation 2, (x2, y2) is the look-ahead point, θ1 is the rear axle spatial path (e.g., the yaw at the first trajectory point), and (x1, y1) is the instantaneous position of vehicle 100 (e.g., the first trajectory point).
[0061] In some examples, when vehicle 100 maintains the same lane currently occupied by vehicle 100 (e.g., in a lane-keeping state), reference path circuitry system 318 and / or trajectory generation circuitry system 308 determine a vector representing the curvature associated with the reference path. To determine the curvature of the trajectory planning while vehicle 100 maintains the same lane currently occupied by vehicle 100, reference path circuitry system 318 and / or trajectory generation circuitry system 308 determine whether the source of the reference path is map-based or vision-based. When the source is map-based, reference path circuitry system 318 and / or trajectory generation circuitry system 308 determine the curvature of the trajectory planning based on the map-based reference path associated with the current lane occupied by vehicle 100 and the look-ahead distance.
[0062] exist Figure 3In the example shown, when the source is vision-based, the reference path circuitry system 318 and / or the trajectory generation circuitry system 308 determine the curvature based on the polynomial coefficients (e.g., cubic polynomial coefficients, visual path coefficients, etc.) of the vision-based reference path corresponding to the look-ahead distance. For example, the reference path circuitry system 318 and / or the trajectory generation circuitry system 308 can determine the curvature using equations 3, 4, and 5 based on the vision-based polynomial coefficients.
[0063] Equation 3: ; Equation 4: ;as well as Equation 5: In equations 3 to 5, y' represents the first derivative of the vision-based path-multiplexed polynomial function; coeffs. cubic, coeffs. quadratic, and coeffs. linear are the polynomial coefficients from the polynomial function; l d y'' is the look-ahead distance; y'' is the second derivative of the polynomial function; and the curvature is the determined curvature associated with the trajectory planning.
[0064] exist Figure 3 In the example shown, the trajectory source identification circuit system 306, the trajectory generation circuit system 308, the PF circuit system 316, and / or the reference path circuit system 318 transmit the determined trajectory plan to the R2C angle calculation circuit system 310. Figure 3 In this embodiment, trajectory generation circuitry 308 is shown as part of path planning circuitry 302. However, in other examples, trajectory generation circuitry 308 may be implemented in another area of vehicle 100 communicatively coupled to path planning circuitry 302. For example, path planning circuitry 302 may be implemented by a different part of steering controller 204 and / or another controller of ECU 202. In such examples, the output of trajectory generation circuitry 308 may be transmitted to path planning circuitry 302. In some examples, trajectory generation circuitry 308 is instantiated by a programmable circuitry system that executes trajectory generation instructions and / or is configured to perform actions such as those generated by... Figure 8 The flowchart represents the operations performed.
[0065] The path planning circuit system 302 includes an R2C angle calculation circuit system 310 to calculate the R2C angle. When the maneuver recognition circuit system 304 determines that the vehicle 100 is performing an evasive maneuver, the R2C angle calculation circuit system 310 configures the R2C angle to be equal to the PF angle request. For example, the R2C angle calculation circuit system 310 may cause the R2C angle to match the steering angle in the PF angle request.
[0066] When the maneuver recognition circuit system 304 determines that the vehicle 100 is performing lane keeping or lane changing maneuvers, the R2C angle calculation circuit system 310 calculates the R2C angle based on the curvature, wheelbase, vehicle speed, understeer gradient, and steering ratio determined by trajectory planning. For example, the R2C angle calculation circuit system 310 can access a vector representing the curvature of the trajectory planning from the trajectory source recognition circuit system 306, the trajectory generation circuit system 308, and / or the reference path circuit system 318. Furthermore, the R2C angle calculation circuit system 310 can use Equation 6 to determine the road wheel angle (roadWheelAngle.rad) in radians.
[0067] Equation 6: In Equation 6, wheelbase.m is the wheelbase of vehicle 100 in meters; understeerGradientRad.mps2 is the understeer gradient of vehicle 100 in radians multiplied by meters per square second; velocity.mps is the speed of vehicle 100 in meters per second; and curvature_radpm is the curvature determined in radians per meter associated with trajectory planning. Furthermore, the R2C angle calculation circuitry 310 converts roadWheelAngle.rad from radians to degrees and multiplies the road wheel angle in degrees by the steering ratio of vehicle 100 to obtain the R2C angle associated with trajectory planning. In some examples, the R2C angle calculation circuitry 310 is instantiated by a programmable circuitry system that executes angle calculation instructions and / or is configured to perform actions such as those derived by... Figure 8 The flowchart represents the operations performed.
[0068] The path planning circuitry 302 transmits the R2C angle to another component of the steering controller 204 and / or ECU 202. For example, the path planning circuitry 302 can transmit the R2C angle to a software driver that allows the vehicle communication module (VCM) to communicate with a controller area network (CAN) bus, which is communicatively coupled to another component of the steering controller 204 and / or ECU 202. Therefore, the steering controller 204 can use the R2C angle to determine when to steer the vehicle 100 in assisted driving mode by the motor 214 (…). Figure 2A ) or torque feedback motor 260 ( Figure 2BThe position and / or torque provided. The following discusses in further detail exemplary ways in which vehicle 100 can utilize the determined R2C angle. However, it should be understood that the determined R2C angle can be utilized in different ways to facilitate driver assistance. For example, path planning circuitry 302 can provide the determined R2C angle to motor 214 or torque feedback motor 260, which can cause the driver to encounter mirrored torque resistance on the opposite side of the R2C angle. That is, motor 214 or torque feedback motor 260 provides a counter-torque resistance that acts in the opposite direction to the torque input relative to the R2C angle, causing the steering angle to be biased toward the R2C angle. Therefore, path planning circuitry 302 enables motor 214 or torque feedback motor 260 to provide a more intuitive steering feel in driver assistance, especially when the R2C angle is non-zero.
[0069] Figure 4 yes Figures 2A to 2B Example block diagram of steering controller 204. When vehicle 100 is in assisted driving mode, steering controller 204 operates to control motor 214 ( Figure 2A ) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B The steering controller 204 adjusts the steering of vehicle 100 so that vehicle 100 steers along a target path. The steering controller 204 can also adjust the steering wheel 206 during assisted driving modes, such as when the driver attempts to manually turn the steering wheel. Figures 2A to 2B When the vehicle 100 includes a first steerable wheel motor 252, a second steerable wheel motor 254, and / or a torque feedback motor 260, the motor 214 or the first steerable wheel motor 252, the second steerable wheel motor 254, and / or the torque feedback motor 260 are controlled based on the driver's input torque (thereby controlling the steering angle). Figure 2A When the steering system 200 is used, the steering controller 204 includes or communicates with a motor 214. When the vehicle 100 includes Figure 2B When the steering system 250 is configured, the steering controller 204 includes a first steerable wheel motor 252, a second steerable wheel motor 254, and / or a torque feedback motor 260, or communicates with them. In some examples, the steering controller 204... Figures 2A to 2B The electronic control unit 202 is implemented therein. Alternatively, the steering controller circuit 204 may be implemented in another control system, control unit, and / or computing system of the vehicle 100.
[0070] exist Figure 4 In the example shown, the steering controller 204 includes an example virtual reinforcement curve circuit system 402 (VBC circuit system 402), an example angle mixing circuit system 406, and an example conversion circuit system 408. The conversion circuit system 408 and the motor 214 ( Figure 2A) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B This can be referred to as angle controller 410. That is, when vehicle 100 includes... Figure 2A When the steering system 200 is in use, the angle controller 410 includes a motor 214. When the vehicle 100 includes... Figure 2B When the steering system 250 is engaged, the angle controller 410 includes a first steerable wheel motor 252, a second steerable wheel motor 254, and / or a torque feedback motor 260. As mentioned above, the torque sensor 222 outputs a sensor signal corresponding to the original T-stick torque, which indicates the driver input torque applied to the steering wheel 206. The path planning circuitry 302 determines the R2C angle based on the maneuver to be performed by the vehicle 100 identified by the maneuver recognition circuitry 304, the reference path from the reference path circuitry 318, the vehicle speed from the speed sensor 312, and / or vehicle configuration parameters (e.g., wheelbase, understeer gradient, steering ratio, etc.) accessed via the vehicle configuration database 314, as described above. Figure 3 The subject of discussion.
[0071] exist Figure 4 In the example shown, the VBC circuit system 402 obtains the R2C angle from the path planning circuit system 302. The VBC circuit system 402 also obtains a signal from the torque sensor 222 and uses a Kalman filter method and Figures 2A to 2B The input torque is determined by models of steering systems 200 and 250. In other examples, different types of filters may be used, or unfiltered torque may be used. Additionally, VBC circuitry 402 obtains the current SWA associated with steering wheel 206 from SWA sensor 224. Example VBC circuitry 402 determines a VBC angle request based on the input torque, SWA, and R2C angle determined by path planning circuitry 302. The VBC angle request represents the desired driver steering angle, based on the current SWA and the driver torque applied to steering wheel 206. In some examples, the VBC angle request is also based at least in part on vehicle speed, which may be measured by speed sensor 312 of vehicle 100. The VBC angle request includes a combination (e.g., summation) of incremental angle and current SWA. In some examples, VBC circuitry 402 is instantiated by a programmable circuitry that executes VBC instructions and / or is configured to perform actions such as those described by... Figure 9 The operations shown in the flowchart of Figure / 10.
[0072] When vehicle 100 is in assisted driving mode, the example PF circuit system 316 of path planning circuit system 302 ( Figure 3A PF angle request is determined, which is used to adjust the steering angle of vehicle 100 to steer vehicle 100 along a target path or guide vehicle along a target path. Figure 4 In this diagram, the path planning circuitry 302 is shown separate from the steering controller 204. For example, the path planning circuitry 302 may be implemented by another controller of the ECU 202. However, in other examples, the path planning circuitry 302 may be part of the steering controller 204. When the driver of vehicle 100 does not interact with the steering wheel 206 during assisted driving mode (e.g., zero input torque), the PF circuitry 316 controls the yaw, direction, and / or steering angle of vehicle 100. For example, when the driver input torque is zero during assisted driving mode, the final angle request may consist solely of the PF angle request. In some examples, the PF circuitry 316 is based on a reference path of vehicle 100, the speed of vehicle 100, and... Figures 2A to 2B The current steering angle of the steering wheel 206 and / or the expected path of the vehicle 100 are used to determine the PF angle request.
[0073] exist Figure 4 In the illustrated example, the steering controller 204 includes an angle blending circuitry 406 to determine the final angle request based on a combination of the VBC angle request, the PF angle request, and the angle blending weight. In some examples, the angle blending weight is an internal signal with a value ranging from 0 to 1, where an angle blending weight of 0 corresponds to no driver input or interaction, and an angle blending weight of 1 corresponds to fully engaged driver interaction. Therefore, when the driver has no interaction (e.g., the angle blending weight is equal to 0), the angle control of the vehicle 100 is based solely on the PF angle request.
[0074] To generate the angle blending weights, the angle blending circuitry 406 allows the driver input torque to pass through a VBC weight lookup table, which provides a VBC weight of 0 or 1 (e.g., a preliminary weight). That is, the preliminary weight is 0 when the input torque does not meet the VBC weight threshold, and 1 when the input torque does meet the VBC weight threshold. Additionally, the angle blending circuitry 406 multiplies the VBC weights by the output of a speed-based weight lookup table, which corresponds to the speed-based weights. The angle blending circuitry 406 has access to the vehicle speed measured by the speed sensor 312. In some examples, the angle blending circuitry 406 inputs the vehicle speed into the speed-based weight lookup table to determine the speed-based weights. As the input vehicle speed increases, the output speed-based weights decrease. In some examples, the value of the angle blending weights and the contribution of the VBC angle request are higher at lower speeds and lower at higher speeds. For example, if the driver input torque and the VBC weights are sufficiently high (e.g., a value of 1), the speed-based weights are higher at lower speeds and lower at higher speeds. In some examples, the speed-based weight is 0 when the vehicle speed exceeds a threshold (e.g., 30 mph, 45 mph, 60 mph, etc.). In some examples, the angle blending circuitry 406 is instantiated by a programmable circuitry that executes angle blending instructions and / or is configured to perform actions such as those initiated by... Figure 9 The flowchart represents the operations performed.
[0075] exist Figure 4 In the illustrated example, the steering controller 204 includes a conversion circuitry 408 to convert a final angle request into a torque request for adjusting the steering angle of the vehicle 100. For example, the conversion circuitry 408 may obtain the final angle request from the angle mixing circuitry 406 and determine the torque to be applied to the steering systems 200, 250 (e.g., to the rack 212, pinion 210, steering column 208, first steerable wheel 218, second steerable wheel 220, etc.) by the motor 214 or the first steerable wheel motor 252, the second steerable wheel motor 254, and / or the torque feedback motor 260 to achieve the steering angle associated with the final angle request. In some examples, the conversion circuitry 408 uses and / or generates... Figures 2A to 2BThe model of steering systems 200, 250 is used to convert the final angle request into a torque request. For example, conversion circuitry 408 may take into account the size, geometry, orientation, materials, structure, or other characteristics of steering systems 200, 250 to generate and / or implement the model. In some examples, the model used by conversion circuitry 408 is generated based on the size and power of motor 214, the length and tooth pitch of rack 212, the diameter of steering column 208, the size of steerable wheels 218, 220, the power of steerable wheel motors 252, 254, the power of torque feedback motor 260, etc. In some examples, conversion circuitry 408 is instantiated by a programmable circuitry system that executes conversion instructions and / or is configured to perform actions such as those by… Figure 9 The flowchart represents the operations performed.
[0076] Figure 5 yes Figure 4 A block diagram of an example implementation of the VBC circuit system 402 generating a VBC angle request. Figure 4 and Figure 5 The VBC circuit system 402 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by a programmable circuit system (such as a central processing unit (CPU) that executes the first instruction). Alternatively or concurrently, Figure 4 and Figure 5 The VBC circuit system 402 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA), the FPGA being structured and / or configured to perform operations corresponding to the first instruction in response to the execution of the second instruction. It should be understood that... Figure 5 Some or all of the circuit system can therefore be instantiated at the same or different times. Figure 5 Some or all of the circuitry can be instantiated, for example, in one or more threads that execute concurrently on hardware and / or serially on hardware. Furthermore, in some examples, Figure 5 Some or all of the circuitry in the system can be implemented by executing instructions through a microprocessor circuitry and / or performing operations through an FPGA circuitry to implement one or more virtual machines and / or containers.
[0077] exist Figure 5In the illustrated example, VBC circuit system 402 includes an example primary increment angle determination circuit system 502, an example derivative increment angle determination circuit system 504, an example homing increment angle determination circuit system 506 (R2C increment angle determination circuit system 506), an example damping increment angle determination circuit system 508, and an example VBC angle determination circuit system 510. In some examples, one or more of the primary increment angle determination circuit system 502, derivative increment angle determination circuit system 504, R2C increment angle determination circuit system 506, damping increment angle determination circuit system 508, and / or VBC angle determination circuit system 510 are combined and / or implemented by steering controller 204 in a circuit system different from VBC circuit system 402. Figure 3 and Figure 4 Example VBC circuit system 402 determines and / or accesses multiple incremental angles (e.g., four incremental angles) and adds these incremental angles to the current SWA to generate a final VBC angle request.
[0078] exist Figure 5 In the illustrated example, the steering controller 204 includes a principal increment angle determination circuitry 502 to determine a principal torque-based increment angle for the VBC angle request. The principal increment angle serves as the base value for the VBC angle request. To determine the principal increment angle, the example principal increment angle determination circuitry 502 passes the input torque through a VBC torque vs. differential SWA lookup table. For example, the principal increment angle determination circuitry 502 inputs the torque into the lookup table and outputs the differential SWA. In some examples, the principal increment angle determination circuitry 502 implements a virtual wall lookup table to ensure that driver input does not cause… Figure 1 The vehicle 100 moves too far off the path. Additionally, in some examples, the principal incremental angle determination circuitry 502 implements a speed-based weighted lookup table to adjust the angle as needed. Figure 1 The value of the principal increment angle decreases as the speed of vehicle 100 increases. In some examples, the principal increment angle determination circuitry 502 is instantiated by a programmable circuitry system that executes principal increment angle determination instructions and / or is configured to perform actions such as those by... Figure 10 The flowchart represents the operations performed.
[0079] exist Figure 5In the illustrated example, the steering controller 204 includes a derivative increment angle determination circuitry 504 to determine the torque derivative-based increment angle of the VBC angle request. In some examples, the VBC angle determination circuitry 510 adds the derivative increment angle to the principal increment angle to provide some leading action when the steering wheel 206 is moved. In other words, the derivative increment angle determination circuitry 504 determines the derivative increment angle to increase the response time of the steering controller 204. Therefore, the derivative increment angle determination circuitry 504 causes the VBC angle request to have a greater impact on the angle control of the vehicle 100 than the PF angle request. Furthermore, the derivative increment angle determination circuitry 504 limits the gain of the principal increment angle to increase responsiveness and maintain... Figures 2A to 2B The stability of the steering systems 200 and 250. In some examples, the derivative increment angle determination circuitry 504 is instantiated by a programmable circuitry that executes derivative increment angle determination instructions and / or is configured to perform actions such as those by... Figure 10 The flowchart represents the operations performed.
[0080] exist Figure 5 In the example shown, the steering controller 204 includes an R2C increment angle determination circuitry 506 to determine the R2C increment angle requested for the VBC angle. In some examples, to enable the steering wheel 206 ( Figures 2A to 2B Returning to the reference position (e.g., automated vehicle path), the R2C increment angle is subtracted from the principal increment angle and the derivative increment angle to determine the VBC angle request. Example R2C increment angle determination circuitry 506 generates the R2C increment angle based on the difference between the current SWA and the R2C reference. As used herein, the R2C reference is the path planning circuitry 302 (…). Figures 3 to 4 The R2C increment angle is determined by the path planning circuitry 302. In some examples, the R2C increment angle determination circuitry 506 includes the path planning circuitry 302. That is, the R2C reference is the SWA angle corresponding to the trajectory planning. Therefore, when the vehicle 100 is operated in assisted driving mode, the steering wheel 206 is pushed toward the R2C reference (e.g., the R2C angle output by the path planning circuitry 302). For example, when the driver applies input torque to the steering wheel 206, the driver feels resistance imposed on the steering wheel 206 by the R2C increment angle determination circuitry 506 and / or the path planning circuitry 302 based on the position of the R2C increment angle and / or the R2C reference. When driving without automated steering based on angle control, the mechanical components of the steering system 200 (e.g., steerable wheels 218, 220, tires, suspension, etc.) or the torque feedback motor 260 ( Figure 2B This causes the steering wheel 206 to naturally return to the center position. However, because the VBC circuit system 402 continuously controls the motor 214 ( Figure 2A) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B To steer the vehicle 100, the steering systems 200 and 250 may not naturally return the vehicle 100 to center when in assisted driving mode. Therefore, the path planning circuit system 302 and the R2C incremental angle determination circuit system 506 are implemented in the steering controller 204 to return the steering wheel 206 and the steerable wheels 218 and 220 to a position guiding the vehicle 100 along a defined trajectory plan, including a center / neutral position when the trajectory plan includes zero curvature.
[0081] In the examples disclosed in this article, an R2C reference is used instead of steering wheel 206 ( Figures 2A to 2B The center position of the VBC angle (e.g., zero SWA). The VBC angle determination circuit system 510 subtracts the R2C increment angle from the main increment angle to determine the final VBC angle request. Therefore, the path planning circuit system 302 ( Figures 3 to 4 The R2C reference is determined, and the R2C increment angle determining circuit system 506 determines the R2C increment angle to provide resistance and / or reaction to the driver's input torque. For example, when the steering wheel 206 ( Figures 2A to 2B When the driver input torque is removed, the R2C increment angle still has a non-zero value and causes motor 214 ( Figure 2A ) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B ) Make the vehicle 100 ( Figure 1 The system then redirects back to the target path. In some examples, the R2C incremental angle determination circuitry 506 is instantiated by a programmable circuitry that executes R2C incremental angle determination instructions and / or is configured to perform actions such as those initiated by... Figure 10 The flowchart represents the operations performed.
[0082] exist Figure 5 In the example shown, steering controller 204 includes a damping increment angle determination circuitry 508 to determine the damping increment angle for the VBC angle request. The damping increment angle determination circuitry 508 determines the damping increment angle to provide a natural steering feel for the VBC angle request. As mentioned above in conjunction with the R2C increment angle determination circuitry 506, steering systems 200, 250 ( Figures 2A to 2BThe mechanical components of the steering wheel 206 may not provide feedback to the driver during autonomous driving mode (e.g., centering movement). Additionally, the steering systems 200 and 250 may not mechanically suppress steering movement to limit uncontrolled movement and / or oscillation of the steering wheel 206. Therefore, the damping increment angle determining circuitry 508 generates a damping increment angle to provide negative feedback on the steering wheel speed (e.g., the rate of change of SWA). In other words, while the principal increment angle and the derivative increment angle cause the steering wheel 206 ( Figures 2A to 2B The steering wheel 206 rotates (e.g., based on input torque), but the R2C increment angle and damping increment angle cause the steering wheel 206 to "bounce" back toward the angle associated with trajectory planning (e.g., PF control).
[0083] In some examples, the magnitude of the damping increment angle is based on vehicle speed, such that higher vehicle speeds result in lower damping increment angles. Additionally, in some examples, the magnitude of the damping increment angle is based on the direction of the SWA (Side Aspect). For example, the damping increment angle is lower when the steering wheel 206 turns away from the center at the same rate compared to when the steering wheel 206 is turned towards the center at a certain rate. In some examples, the damping increment angle determination circuitry 508 is instantiated by a programmable circuitry that executes damping increment angle determination instructions and / or is configured to perform actions such as those by… Figure 10 The flowchart represents the operations performed.
[0084] exist Figure 5 In the illustrated example, the steering controller 204 includes a VBC angle determination circuitry 510 to determine the final VBC angle request. In some examples, the final VBC angle request is determined based on a combination of four incremental angles and the current SWA (or instantaneous SWA), the four incremental angles including (1) the principal incremental angle; (2) the derivative incremental angle; (3) the R2C incremental angle; and (4) the damping incremental angle. In some examples, the VBC angle determination circuitry 510 obtains the incremental angles (e.g., principal, derivative, R2C, damping) from the corresponding circuitry and from the SWA sensor 224 ( Figures 2A to 2B The current SWA is obtained. In some examples, to determine the combination of increment angles, the example VBC angle determination circuit system 510 sums the principal increment angle and the derivative increment angle and subtracts the R2C increment angle and the damping increment angle. The combination of increment angles is then added to the current SWA to generate the final VBC angle request.
[0085] In some examples, in response to the determination of the final VBC angle request, the VBC angle determination circuitry 510 provides the final VBC angle request to the angle mixing circuitry 406 to combine it with the PF angle request and generate the final angle request. Alternatively or concurrently, the VBC angle determination circuitry 510, after determining the final VBC angle request, sends a signal to the motor 214 (…). Figure 2A) or the first steerable wheel motor 252, the second steerable wheel motor 254, and the torque feedback motor 260 ( Figure 2B The final VBC angle request is provided by another component of the steering system 200, 250 and / or the steering system 200, 250. In some examples, the VBC angle determination circuitry 510 is instantiated by a programmable circuitry system that executes the final VBC angle determination instructions and / or is configured to perform actions such as those provided by the steering system 200, 250 and / or the steering system 200, 250. Figure 10 The flowchart represents the operations performed.
[0086] Figure 6 yes Figure 4 Angle blending circuit system 406 generates angle blending weights and determines the final angle request for use in generating motor 214. Figure 2A ) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B A block diagram of an example implementation of the torque response. Figure 4 and Figure 6 The angle-based hybrid circuit system 406 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by a programmable circuit system (such as a central processing unit (CPU) that executes the first instruction). Alternatively or concurrently, Figure 4 and Figure 6 The angle-based hybrid circuit system 406 can be instantiated (e.g., instantiated, formed, materialized, implemented, etc.) by (i) an application-specific integrated circuit (ASIC) and / or (ii) a field-programmable gate array (FPGA), the FPGA being structured and / or configured to perform operations corresponding to the first instruction in response to the execution of the second instruction. It should be understood that... Figure 6 Some or all of the circuit system can therefore be instantiated at the same or different times. Figure 5 Some or all of the circuitry can be instantiated, for example, in one or more threads that execute concurrently on hardware and / or serially on hardware. Furthermore, in some examples, Figure 6 Some or all of the circuitry in the system can be implemented by executing instructions through a microprocessor circuitry and / or performing operations through an FPGA circuitry to implement one or more virtual machines and / or containers.
[0087] exist Figure 6 In the illustrated example, the angle blending circuit system 406 includes an example angle blending weight determination circuit system 602 and an example final angle determination circuit system 604. In some examples, one or more of the angle blending weight determination circuit system 602 and / or the final angle determination circuit system 604 are combined and / or implemented by the steering controller 204 in a circuit system different from the angle blending circuit system 406. Figure 4and Figure 6 The example angle blending circuit system 406 determines the angle blending weights based on the driver's input torque and the vehicle 100. The example angle blending circuit system 406 applies the angle blending weights to the PF angle request and the VBC angle request to determine the final angle request. Therefore, the angle blending circuit system 406 can adjust the influence of the VBC circuit system 402 and the PF circuit system 316 on automatic angle control during autonomous driving mode. For example, when the vehicle 100 is at a lower speed, the angle blending circuit system 406 can increase the VBC angle request and decrease the PF angle request in the final angle request, and vice versa when the vehicle 100 is at a higher speed.
[0088] Send to angle controller 410 (e.g., Figure 3 The conversion circuit system 408 and / or motor 214 ( Figure 2A ) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B The final angle request is a combination of the VBC angle request and the PF angle request, and / or based on the VBC angle request and the PF angle request. In some examples, if the driver does not interact with the steering wheel 206, the final angle request only includes the PF angle request. In some examples, the angle blending weight represents the degree of driver interaction with the steering wheel 206 and ranges from 0 to 1, where 1 corresponds to fully engaged driver interaction. In some examples, the angle blending weight determination circuitry 602 is instantiated by a programmable circuitry system that executes angle blending weight determination instructions and / or is configured to perform actions such as those by... Figure 10 The flowchart illustrates the operations of those actions. In some examples, the final angle determination circuitry 604 is instantiated by a programmable circuitry that executes the final angle determination instructions and / or is configured to perform actions such as those described by... Figure 10 The flowchart represents the operations performed.
[0089] Figure 7 Figure 2 to Figure 6 The example steering controller 204 performs and / or executes an example final angle generation operation 700 to determine the example final angle request 714. As mentioned, the final angle request 714 is converted into a response to motor 214 ( Figure 2A ) or the first steerable wheel motor 252, the second steerable wheel motor 254 and / or the torque feedback motor 260 ( Figure 2B The torque request is applied to the steering system 200, 250 of the vehicle 100 (e.g., steering wheel 206, rack and pinion 212, pinion 210, steering column 208, steerable wheels 218, 220, etc.) to achieve the final steering angle.
[0090] exist Figure 7 In the example shown, the path planning circuit system 302 ( Figure 3 The R2C reference 702, the actual SWA 704 measured by the SWA sensor 224, and the T-bar torque 706 from the torque sensor 222 are transmitted to the VBC circuit system 402. The VBC circuit system 402 then determines four incremental angles, including (1) the principal incremental angle, (2) the derivative incremental angle, (3) the R2C incremental angle, and (4) the damping incremental angle, and uses these to determine the VBC angle request 708. The VBC circuit system 402 provides the VBC angle request to the angle mixing circuit system 406. The angle mixing circuit system 406 also accesses the T-bar torque 706, the torque measured by the PF circuit system 316, and the torque measured by the PF circuit system 316. Figure 3 The driver interaction activation signal 712 (DI activation signal 712) is determined by the PF angle request 710. The angle mixing circuit system 406 determines the final angle request 714 and transmits the final angle request to the conversion circuit system 408. When the driver is performing evasive maneuvers, considering the PF angle request in the R2C reference 702 helps guide the vehicle 100 back to the target path, although the T-stick torque 706 and the DI activation signal 712 cause the effect of the PF angle request 710 on the final angle request 714 to be reduced.
[0091] Despite Figures 3 to 6 The implementation is shown in the figure. Figures 2A to 2B The example shown is ECU 202, but in Figures 3 to 6 One or more elements, processes, and / or devices shown may be combined, divided, rearranged, omitted, eliminated, and / or implemented in any other way. Furthermore, Figures 2A to 2B Example steering controller 204, example path planning circuit system 302, example maneuver recognition circuit system 304, example trajectory source recognition circuit system 306, example trajectory generation circuit system 308, example R2C angle calculation circuit system 310, example PF circuit system 316, example reference path circuit system 318, example VBC circuit system 402, example angle mixing circuit system 406, example conversion circuit system 408, example main increment angle determination circuit 502, example derivative increment angle determination circuit 504, example R2C increment angle determination circuit 506, example damping increment angle determination circuit 508, VBC angle determination circuit system 510, example angle mixing weight determination circuit system 602, example final angle determination circuit system 604, and / or more generally example ECU 202 can be implemented individually by hardware or by a combination of hardware and software and / or firmware. Therefore, for example, Figures 2A to 2BExample steering controller 204, example path planning circuit system 302, example maneuver recognition circuit system 304, example trajectory source recognition circuit system 306, example trajectory generation circuit system 308, example R2C angle calculation circuit system 310, example PF circuit system 316, example reference path circuit system 318, example VBC circuit system 402, example angle mixing circuit system 406, example conversion circuit system 408, example main increment angle determination circuit 502, example derivative increment angle determination circuit 504, example R2C increment angle determination circuit 506, example damping increment angle determination circuit 508, VBC angle determination circuit system 510, example angle mixing weight determination circuit system 602, example final angle determination circuit system 604, and / or more general example ECUs. Any of 202 can be implemented through a combination of programmable circuit systems with machine-readable instructions (e.g., firmware or software), processor circuit systems, analog circuits, digital circuits, logic circuits, programmable processors, programmable microcontrollers, graphics processing units (GPUs), digital signal processors (DSPs), ASICs, programmable logic devices (PLDs), and / or field-programmable logic devices (FPLDs) (such as FPGAs). Furthermore, as Figures 3 to 6 The supplements or alternatives shown Figures 2A to 2B The example steering controller 204 may include one or more elements, processes and / or devices, and / or may include more than one of any or all of the elements, processes and devices shown.
[0092] Figure 8 , Figure 9 and Figure 10 The diagram shows a flowchart representing example machine-readable instructions (which can be implemented and / or instantiated by a programmable circuit system). Figures 2A to 2B ECU 202) and / or represent example operations (the example operations can be implemented and / or instantiated by a programmable circuit system). Figures 2A to 2B The flowchart of ECU 202). Machine-readable instructions can be provided to programmable circuit systems (such as those described below). Figure 11 The programmable circuit system 1112 shown in the example processor platform 1100 discussed herein executes one or more executable programs or portions of one or more executable programs and / or may be one or more functions or portions of functions to be executed by other example programmable circuit systems (such as FPGAs). In some examples, machine-readable instructions cause operations, tasks, etc., to be performed and / or executed in an automated manner in the real world. As used herein, “automation” means without human intervention.
[0093] The program may be embodied in instructions (e.g., software and / or firmware) stored in one or more non-transitory computer-readable and / or machine-readable storage media, such as cache memory, magnetic storage devices or disks (e.g., floppy disks, hard disk drives (HDDs), etc.), optical storage devices or optical discs (e.g., Blu-ray discs, compact discs (CDs), digital versatile discs (DVDs), etc.), redundant arrays of independent disks (RAID), registers, ROM, solid-state drives (SSDs), SSD memory, non-volatile memory (e.g., electrically erasable programmable read-only memory (EEPROM), flash memory, etc.), volatile memory (e.g., random access memory (RAM) of any type), and / or any other storage device or disk. The instructions of the non-transitory computer-readable and / or machine-readable media may be programmed and / or executed by a programmable circuit system located in one or more hardware devices, but the entire program and / or portions thereof may alternatively be executed and / or instantiated by one or more hardware devices rather than a programmable circuit system, and / or embodied in dedicated hardware. Machine-readable instructions can be distributed across multiple hardware devices and / or executed by two or more hardware devices (e.g., server and client hardware devices). For example, client hardware devices can be implemented by endpoint client hardware devices (e.g., hardware devices associated with human and / or machine users) or by an intermediate client hardware device gateway (e.g., a radio access network (RAN)) that facilitates communication between the server and endpoint client hardware devices. Similarly, non-transitory computer-readable storage media can include one or more media. Furthermore, although references... Figures 8 to 10The flowchart shown describes an example program, but many other methods of implementing the example steering controller 204 can be used alternatively. For example, the execution order of the flowchart blocks can be changed, and / or some of the described blocks can be changed, deleted, or combined. Additionally or alternatively, any or all of the flowchart blocks can be implemented by one or more hardware circuits (e.g., processor circuitry, discrete and / or integrated analog and / or digital circuitry, FPGA, ASIC, comparator, operational amplifier, logic circuitry, etc.) structured to perform the corresponding operation without executing software or firmware. The programmable circuitry can be distributed across different network locations and / or local to one or more hardware devices (e.g., a single-core processor (e.g., a single-core CPU), a multi-core processor (e.g., a multi-core CPU, XPU, etc.)). For example, the programmable circuitry can be a CPU and / or FPGA located in the same package (e.g., the same integrated circuit (IC) package or in two or more separate housings), one or more processors in a single machine, multiple processors distributed across multiple servers in a server rack, multiple processors distributed across one or more server racks, and / or any combination thereof.
[0094] The machine-readable instructions described herein can be stored in one or more of the following formats: compressed format, encrypted format, segmented format, compiled format, executable format, and packaged format. As described herein, machine-readable instructions can be stored as data (e.g., computer-readable data, machine-readable data, one or more bits (e.g., one or more computer-readable bits, one or more machine-readable bits, etc.), bit streams (e.g., computer-readable bit streams, machine-readable bit streams, etc.)) or data structures (e.g., stored as parts of instructions, code, representations of code, etc.). For example, machine-readable instructions can be segmented and stored on one or more storage devices, disks, and / or computing devices (e.g., servers) located in the same or different locations (e.g., in the cloud, at an edge device, etc.) within a network or network set. Machine-readable instructions may require one or more of the following processes: installation, modification, rewriting, updating, combination, supplementation, configuration, decryption, decompression, unpacking, distribution, reallocation, compilation, etc., to enable them to be directly read, interpreted, and / or executed by computing devices and / or other machines. For example, machine-readable instructions may be stored in multiple parts, which are individually compressed, encrypted, and / or stored on separate computing devices, wherein the parts, when decrypted, decompressed, and / or combined, form a set of computer-executable and / or machine-executable instructions that together can form one or more functions and / or operations of a program such as those described herein.
[0095] In another example, machine-readable instructions may be stored in a state that can be read by a programmable circuit system, but require the addition of libraries (e.g., dynamic link libraries (DLLs)), software development kits (SDKs), application programming interfaces (APIs), etc., to execute the machine-readable instructions on a specific computing device or other device. In yet another example, it may be necessary to configure the machine-readable instructions (e.g., store settings, input data, record network addresses, etc.) before they can be executed in whole or in part. Therefore, as used herein, machine-readable media, computer-readable and / or machine-readable media may include instructions and / or programs, regardless of their specific format or state.
[0096] The machine-readable instructions described in this article can be represented by any past, present, or future instruction language, scripting language, programming language, etc. For example, machine-readable instructions can be represented using any of the following languages: C, C++, Java, C#, Perl, Python, JavaScript, Hypertext Markup Language (HTML), Structured Query Language (SQL), Swift, etc.
[0097] As mentioned above, it can be implemented using executable instructions (e.g., computer-readable instructions and / or machine-readable instructions) stored on one or more non-transitory computer-readable and / or machine-readable media. Figure 8 , Figure 9 and / or Figure 10Example operation. As used herein, the terms non-transitory computer-readable medium, non-transitory computer-readable storage medium, non-transitory machine-readable medium, and / or non-transitory machine-readable storage medium are expressly defined to include any type of computer-readable storage device and / or storage disk, excluding propagated signals and transmission media. Examples of such non-transitory computer-readable media, non-transitory computer-readable storage media, non-transitory machine-readable media, and / or non-transitory machine-readable storage media include optical storage devices, magnetic storage devices, HDDs, flash memory, read-only memory (ROM), CDs, DVDs, caches, any type of RAM, registers, and / or any other storage device or storage disk in which information is stored for any duration (e.g., extended time period, permanently, for temporary cases, for temporary buffering, and / or for caching information). As used herein, the terms "non-transitory computer-readable storage device" and "non-transitory machine-readable storage device" are defined to include any physical (mechanical, magnetic, and / or electrical) hardware that retains information for a period of time, but excluding propagated signals and transmission media. Examples of non-transitory computer-readable storage devices and / or non-transitory machine-readable storage devices include any type of random access memory, any type of read-only memory, solid-state memory, flash memory, optical disk, magnetic disk, disk drive, and / or redundant array of independent disks (RAID) system. As used herein, the term "device" refers to a physical structure, such as mechanical and / or electrical equipment, hardware, and / or circuitry, that can be configured and / or may be manufactured or may not be manufactured to execute computer-readable instructions, machine-readable instructions, etc., whether or not by computer-readable instructions, machine-readable instructions, etc.
[0098] "Comprising" and "including" (and all their forms and tenses) are used herein as open-ended terms. Therefore, whenever a claim uses any form of "comprising" or "including" (e.g., encompassing, having, etc.) as a preamble or within any kind of claim statement, it should be understood that additional elements, items, etc., may be present without exceeding the scope of the corresponding claim or statement. As used herein, the phrase "at least" is open-ended when used, for example, as a transitional term in the preamble of a claim, in the same way that the terms "comprising" and "including" are open-ended. The term "and / or" refers to any combination or subset of A, B, C when used, for example, in the form of A, B, and / or C, such as (1) only A, (2) only B, (3) only C, (4) A and B, (5) A and C, (6) B and C, and (7) A and B and C. As used herein in the context of describing structures, components, articles, objects, and / or things, the phrase "at least one of A and B" is intended to refer to an implementation that includes any one of (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. Similarly, as used herein in the context of describing structures, components, articles, objects, and / or things, the phrase "at least one of A and B" is intended to refer to an implementation that includes any one of (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. As used herein in the context of describing the conduct or execution of processes, instructions, actions, activities, etc., the phrase "at least one of A and B" is intended to refer to an implementation that includes any one of (1) at least one A, (2) at least one B, or (3) at least one A and at least one B. Similarly, as used herein in the context of describing the conduct or execution of processes, instructions, actions, activities, etc., the phrase "at least one of A and B" is intended to refer to an implementation that includes any one of (1) at least one A, (2) at least one B, or (3) at least one A and at least one B.
[0099] As used herein, singular references (e.g., "a," "an," "first," "second," etc.) do not exclude plurals. As used herein, the term "a" (or "an") object refers to one or more of that object. The terms "a" (or "an"), "one or more," and "at least one" are used interchangeably herein. Furthermore, although listed separately, multiple components, elements, or actions may be performed by, for example, the same entity or object. Additionally, while individual features may be included in different examples or claims, they may be combined, and inclusion in different examples or claims does not imply that the combination of features is impractical and / or disadvantageous.
[0100] Figure 8This is a flowchart representing example machine-readable instructions and / or example operations 900 that can be executed, instantiated, and / or performed by a programmable circuit system to determine the R2C angle. Figure 8 The example operation assumes that vehicle 100 is in assisted driving mode. Figure 8 Example machine-readable instructions and / or example operations 800 begin at box 802, where ECU 202 ( Figures 2A to 2B Access or obtain PF angle requests, torque inputs, current SWA, vehicle speed, and vehicle configuration data. For example, the path planning circuit system 302 ( Figure 3 The reference path circuit system 318 can query the reference path circuit system 318 for the instantaneous reference path that vehicle 100 should follow. Furthermore, the path planning circuit system 302 can cause the PF circuit system 316 ( Figure 3 The instantaneous PF angle request associated with the instantaneous reference path is determined. In some examples, when the PF circuitry 316 is implemented by a component of the ECU 202 other than the path planning circuitry 302, the path planning circuitry 302 can request the PF circuitry 316 ( Figure 3 ) Query instantaneous PF angle request. In some examples, the path planning circuit system 302 accesses the torque sensor 222 ( Figures 2A to 2B The path planning circuit system 302 obtains the output from the SWA sensor 224 and determines the torque input based on the sensor output. In some examples, the path planning circuit system 302 obtains the torque input from the SWA sensor 224. Figures 2A to 2B The path planning circuit system 302 can access the current SWA from the speed sensor 312. Figure 3 The path planning circuit system 302 can access vehicle speed via the vehicle configuration database 314. Figure 3 Access vehicle configuration data (e.g., wheelbase, understeer gradient, etc.).
[0101] At box 804, ECU 202 determines whether an evasive maneuver is planned. For example, maneuver recognition circuitry 304 may identify an impending evasive maneuver in response to a rapid deviation of the reference path from the current heading of vehicle 100 (e.g., sudden movement within the lane). In some examples, maneuver recognition circuitry 304 determines that the driver is performing an evasive maneuver in response to detecting a steering wheel acceleration that meets (e.g., greater than, greater than, or equal to) an acceleration threshold. Maneuver recognition circuitry 304 may determine the steering wheel acceleration based on changes in SWA and / or torque input. When steering controller 204 determines that an evasive maneuver is planned, the operation proceeds to box 806. Otherwise, when steering controller 204 determines that no evasive maneuver is planned, the operation proceeds to box 808.
[0102] At box 806, ECU 202 configures the R2C angle to match the PF angle request. For example, when the maneuver recognition circuitry 304 determines that vehicle 100 is performing an evasive maneuver, R2C angle calculation circuitry 310 configures the R2C angle to be equal to the PF angle request determined by PF circuitry 316.
[0103] At block 808, ECU 202 determines whether a lane change mode is detected. For example, path planning circuitry 302 and / or maneuver recognition circuitry 304 may determine that vehicle 100 is about to perform a lane change maneuver based on a reference path from reference path circuitry 318, activation of a steering signal, and / or input from another component of ECU 202. When path planning circuitry 302 and / or maneuver recognition circuitry 304 determines that a lane change mode is detected, operation 800 proceeds to block 810. Otherwise, when path planning circuitry 302 and / or maneuver recognition circuitry 304 determines that no lane change mode is detected (e.g., lane keeping mode is active), operation 800 proceeds to block 812.
[0104] At box 810, ECU 202 calculates the curvature associated with the trajectory planning of vehicle 100. For example, when vehicle 100 is about to perform a lane change, path planning circuitry 302 and / or trajectory generation circuitry 308 ( Figure 3 The trajectory planning of vehicle 100 is calculated based on the instantaneous trajectory of vehicle 100, the instantaneous position of vehicle 100, and the look-ahead distance (e.g., a predetermined look-ahead distance). In some examples, the trajectory generation circuit system 308 uses Equations 1 and 2 to calculate the curvature associated with the trajectory planning.
[0105] At box 812, ECU 202 calculates curvature based on a reference path that vehicle 100 will follow while maintaining the lane currently occupied by vehicle 100. For example, when the source is map-based, reference path circuitry 318 and / or trajectory generation circuitry 308 determine the curvature of the trajectory planning based on the map-based reference path and look-ahead distance associated with the lane instantaneously occupied by vehicle 100. When the source is vision-based, reference path circuitry 318 and / or trajectory generation circuitry 308 determine the curvature based on polynomial coefficients (e.g., cubic polynomial coefficients, visual path coefficients, etc.) of the vision-based path from reference path circuitry 318 corresponding to the look-ahead distance. For example, reference path circuitry 318 and / or trajectory generation circuitry 308 can use Equations 3, 4, and 5 to determine the curvature based on the vision-based polynomial coefficients.
[0106] At box 814, ECU 202 calculates the steering angle based on the calculated curvature. When the maneuver recognition circuit system 304 determines that vehicle 100 is performing lane keeping maneuver or lane change maneuver, R2C angle calculation circuit system 310 calculates the steering angle based on the determined curvature, wheelbase, vehicle speed, understeer gradient, and steering ratio from trajectory planning.
[0107] At box 816, the ECU 202 outputs the calculated steering angle as the R2C reference angle. For example, the path planning circuit system 302 can transmit the R2C reference angle to the VBC circuit system 402. Figure 4 ) and / or angle controller 409 ( Figure 4 ).
[0108] Figure 9 This is a flowchart representing example machine-readable instructions and / or example operations 900 that can be executed, instantiated, and / or performed by a programmable circuit system to adjust the steering angle of a vehicle. Figure 9 The example operation assumes that vehicle 100 is in autonomous driving mode. Figure 9 Example machine-readable instructions and / or example operations 900 begin at blocks 902, 904, where the steering controller 204 monitors torque input. For example, torque sensor 222 measures the torque applied by the driver to steering wheel 206. At block 902, VBC circuitry 402 accesses the signal from torque sensor 222 and can determine the torque input (if any) based on the output signal of torque sensor 222. At block 904, VBC circuitry 402 determines whether any torque input has been detected. If no torque input is detected, control reverts to block 902, and VBC circuitry 402 continues to monitor torque input. In some examples, VBC circuitry 402 performs this check at a specific frequency set by a clock (e.g., 100 Hz).
[0109] If torque input is detected, then at box 906, steering controller 204 ( Figures 2A to 2B ) Access or obtain PF angle request, Figure 8 The R2C angle (e.g., R2C reference), torque input, and current SWA are determined in the circuit. For example, the angle mixing circuit system 406 can query the PF circuit system 316 for an instantaneous PF angle request. The VBC circuit system 402 can obtain the instantaneous PF angle request from the path planning circuit system 302 ( Figure 3 Access to R2C angle. VBC circuit system 402 can access torque sensor 222 ( Figures 2A to 2B The VBC circuit system 402 can access the current SWA from the SWA sensor 224 and determine the torque input based on the sensor output.
[0110] At box 908, steering controller 204 generates a VBC angle request. For example, VBC circuitry 402 determines various incremental angles and combines them with the current SWA to generate the VBC angle request. (The following is in conjunction with...) Figure 10 Let's describe further details about box 908.
[0111] At box 910, steering controller 204 determines the angle blending weight. For example, angle blending circuitry 406 and / or angle blending weight determination circuitry 602 calculate the angle blending weight based on driver input torque and vehicle speed.
[0112] At box 912, steering controller 204 determines the final angle request. For example, angle blending circuitry 406 and / or final angle determination circuitry 604 blend the VBC angle request, PF angle request, and angle blending weights to calculate the final angle request.
[0113] At box 914, the steering controller 204 translates the final angle request into a torque request. For example, Figure 4 The conversion circuit system 408 calculates the torque that will cause the steering wheel 206 to rotate or turn to the steering angle associated with the final angle request.
[0114] At frame 916, steering controller 204 causes motor 214 ( Figure 2A ) or the first steerable wheel motor 252 ( Figure 2B ), second steerable wheel motor 254 ( Figure 2B The torque feedback motor 260 applies a torque request to the steering systems 200, 250 of the vehicle 100 (e.g., on rack 212, on steerable wheels 218, 220, and on steering wheel 206) to achieve a final angle request. For example, the conversion circuitry 408 sends a torque request to motor 214 as a command to apply the torque request to rack 212, thereby adjusting the steering angle of the vehicle 100 to the steering angle associated with the final angle request. Alternatively, the conversion circuitry 408 may send a torque request to a first steerable wheel motor 252 and a second steerable wheel motor 254 to adjust the steering angle of the vehicle 100 to the steering angle associated with the final angle request. In some examples, the conversion circuitry 408 sends a torque request to torque feedback motor 260, which adjusts the SWA and / or torque provided to steering wheel 206 based on the steering angle associated with the final angle request.
[0115] In some examples, control proceeds back to block 902, and steering controller 204 continues to monitor additional torque input, such as when the driver applies torque to steering wheel 206. The example process can be repeated continuously when vehicle 100 is in assisted driving mode. However, if autonomous driving mode is deactivated and / or vehicle 100 is turned off, the example process and / or operation 900 ends.
[0116] Figure 10 This is a flowchart representing example machine-readable instructions and / or example operations 1000 that can be executed, instantiated, and / or performed by a programmable circuit system to generate a VBC angle request. Figure 10 Example machine-readable instructions and / or example operations 1000 may correspond to in Figure 9 The operation performed at box 908. Figure 10 Example machine-readable instructions and / or example operations 1000 begin at box 1002, where the steering controller 204 ( Figures 2A to 2B Determine the incremental angle based on the main torque. For example, VBC circuit system 402 ( Figure 4 ) and / or the main incremental angle determination circuit system 502 ( Figure 5 )based on Figure 10 The operation 1000 is used to determine the main incremental angle.
[0117] At box 1004, steering controller 204 determines the incremental angle based on the torque derivative. For example, Figure 4 The VBC circuit system 402 and / or the derivative increment angle determination circuit system 404 determine the derivative increment angle.
[0118] At box 1006, steering controller 204 determines the R2C increment angle. For example, VBC circuitry 402 and / or Figure 5 The R2C increment angle determination circuit system 506 determines the R2C increment angle based on the R2C reference and the current SWA. Path planning circuit system 302 ( Figure 3 ) can be based on Figure 8 The operation 800 determines the R2C reference.
[0119] At box 1008, steering controller 204 determines the steering wheel damping increment angle. For example, VBC circuitry 402 and / or Figure 5 The damping increment angle determination circuit system 508 determines the damping increment angle.
[0120] At box 1010, the steering controller 204 combines the principal increment angle, derivative increment angle, R2C increment angle, and damping increment angle. For example, the VBC circuit system 402 and / or Figure 5 The VBC angle determination circuit system 510 combines incremental angles.
[0121] At block 1012, steering controller 204 sums the combination of blocks 1012 with the current SWA. For example, VBC circuit system 402 ( Figure 4 The VBC angle determination circuitry 510 adds a combination to the current SWA. After block 1014, control returns to... Figure 9 Frame 910.
[0122] Figure 11 This is a block diagram of an example programmable circuit system platform 1100, which is structured to execute and / or instantiate example machine-readable instructions and / or Figures 8 to 10 Example operations to implement Figures 2A to 2B ECU 202. Programmable circuit system platform 1100 can be, for example, a server, personal computer, workstation, self-learning machine (e.g., neural network), mobile device (e.g., mobile phone, smartphone, such as iPad). TM Tablet computers, personal digital assistants (PDAs), internet devices, DVD players, CD players, digital video recorders, Blu-ray players, game consoles, personal video recorders, set-top boxes, headsets (e.g., augmented reality (AR) headsets, virtual reality (VR) headsets, etc.) or other wearable devices or any other type of computing device.
[0123] The illustrated programmable circuit system platform 1100 includes a programmable circuit system 1112. The illustrated programmable circuit system 1112 is hardware. For example, the programmable circuit system 1112 can be implemented by one or more integrated circuits, logic circuits, FPGAs, microprocessors, CPUs, GPUs, VPUs, DSPs, and / or microcontrollers from any desired family or manufacturer. The programmable circuit system 1112 can be implemented by one or more semiconductor-based (e.g., silicon-based) devices. In this example, programmable circuit system 1112 implements example ECU 202, example steering controller 204, example path planning circuit system 302, example maneuver recognition circuit system 304, example trajectory source recognition circuit system 306, example trajectory generation circuit system 308, example R2C angle calculation circuit system 310, example PF circuit system 316, example reference path circuit system 318, example VBC circuit system 402, example angle mixing circuit system 406, example conversion circuit system 408, example main increment angle determination circuit 502, example derivative increment angle determination circuit 504, example R2C increment angle determination circuit 506, example damping increment angle determination circuit 508, VBC angle determination circuit system 510, example angle mixing weight determination circuit system 602 and / or example final angle determination circuit system 604.
[0124] The programmable circuit system 1112 of the example shown includes local memory 1113 (e.g., cache, registers, etc.). The programmable circuit system 1112 of the example shown communicates via bus 1118 with main memories 1114, 1116, including volatile memory 1114 and non-volatile memory 1116. Volatile memory 1114 may be implemented by synchronous dynamic random access memory (SDRAM), dynamic random access memory (DRAM), RAMBUS® dynamic random access memory (RDRAM®), and / or any other type of RAM device. Non-volatile memory 1116 may be implemented by flash memory and / or any other desired type of memory device. Access to the main memories 1114, 1116 of the example shown is controlled by a memory controller 1117. In some examples, the memory controller 1117 may be implemented by one or more integrated circuits, logic circuits, microcontrollers, or any other type of circuit system from any desired family or manufacturer to manage data flows to and from the main memories 1114, 1116.
[0125] The programmable circuit system platform 1100 shown in the example also includes an interface circuit system 1120. The interface circuit system 1120 can be implemented in hardware according to any type of interface standard, such as an Ethernet interface, a Universal Serial Bus (USB) interface, a Bluetooth® interface, a Near Field Communication (NFC) interface, a Peripheral Component Interconnect (PCI) interface, and / or a Peripheral Component Interconnect High Speed (PCIe) interface.
[0126] In the illustrated example, one or more input devices 1122 are connected to the interface circuitry 1120. Input devices 1122 may include a torque sensor 222, an SWA sensor 224, a speed sensor 312, a first steerable wheel position sensor 256, and / or a second steerable wheel position sensor 258. Input devices 1122 allow users (e.g., human users, machine users, etc.) to input data and / or commands into the programmable circuitry 1112. Input devices 1122 may be implemented using, for example, audio sensors, microphones, cameras (still or video), keyboards, buttons, mice, touchscreens, trackpads, trackballs, isotope devices, and / or voice recognition systems.
[0127] One or more output devices 1124 are also connected to the interface circuitry system 1120 of the illustrated example. Output devices 1124 may include a motor 214, a first steerable wheel motor 252, a second steerable wheel motor 254, and / or a torque feedback motor 260. Output devices 1124 may be implemented, for example, via display devices (e.g., light-emitting diode (LED), organic light-emitting diode (OLED), liquid crystal display (LCD), cathode ray tube (CRT) display, in-situ switch (IPS) display, touchscreen, etc.), haptic output devices, printers, and / or speakers. Therefore, the interface circuitry 1120 of the illustrated example typically includes a graphics driver card, a graphics driver chip, and / or graphics processor circuitry, such as a GPU.
[0128] The interface circuit system 1120 of the example shown also includes communication devices, such as transmitters, receivers, transceivers, modems, residential gateways, wireless access points, and / or network interfaces, to facilitate data exchange with external machines (e.g., any type of computing device) via network 1126. Communication can be carried out via, for example, Ethernet connections, digital subscriber line (DSL) connections, telephone line connections, coaxial cable systems, satellite systems, beyond-line-of-sight wireless systems, line-of-sight wireless systems, mobile phone systems, optical connections, etc.
[0129] The programmable circuit system platform 1100 illustrated also includes one or more mass storage disks or devices 1128 for storing firmware, software, and / or data. Examples of such mass storage disks or devices 1128 include magnetic storage devices (e.g., floppy disks, drives, HDDs, etc.), optical storage devices (e.g., Blu-ray discs, CDs, DVDs, etc.), RAID systems, and / or solid-state storage disks or devices, such as flash memory devices and / or SSDs.
[0130] can be Figure 8 , Figure 9 and / or Figure 10 The machine-readable instructions 1132 implemented by the machine-readable instructions may be stored in mass storage device 1128, in volatile memory 1114, in non-volatile memory 1116, and / or on at least one non-transitory computer-readable storage medium (such as a CD or DVD) that may be removable.
[0131] As can be understood from the foregoing, example systems, apparatuses, and methods for determining the R2C angle of assisted (e.g., autonomous, semi-autonomous, etc.) driving vehicles have been disclosed. R2C angle determination enables the vehicle to react appropriately to different driving maneuvers it may encounter. Furthermore, R2C angle utilization helps reduce the delay in returning to the desired trajectory after performing evasive maneuvers. In addition, the example systems, apparatuses, and methods adjust the vehicle's steering wheel angle at least in part based on the determined R2C angle. The disclosed systems, apparatuses, articles, and methods improve the efficiency of the vehicle's computing devices and steering systems by enabling an angle control interface to the vehicle's angle-based autonomous driving control system.
[0132] This article discloses a method and apparatus for configuring the return angle of a steering wheel. Further examples and combinations thereof include the following: Example 1 includes a vehicle comprising: a steering wheel; a steerable wheel operably coupled to the steerable wheel; a steering motor for being activated when the vehicle is in an assisted driving mode to control the steering angle of the steering wheel; and a steering controller including instructions and a programmable circuit system for executing the instructions to access a trajectory plan of the vehicle, the trajectory plan including curvature; determining a return-to-center (R2C) angle of the steering wheel based on the trajectory plan and vehicle speed, the R2C angle being non-zero; and causing the steering motor to bias the steering angle of the steering wheel toward the R2C angle in response to the steering wheel receiving a torque input from the driver.
[0133] Example 2 includes the vehicle according to Example 1, wherein the steering motor provides a reaction torque resistance that acts relative to the R2C angle in a direction opposite to the torque input to deflect the steering angle toward the R2C angle.
[0134] Example 3 includes a vehicle according to any of the foregoing examples, wherein the programmable circuitry is used to convert the curvature into the R2C angle based on wheelbase parameters, steering ratio parameters, understeer gradient, vehicle speed, and the curvature.
[0135] Example 4 includes a vehicle according to any of the foregoing examples, wherein the programmable circuitry is configured to determine whether an evasive maneuver will occur, and when the evasive maneuver is about to occur, causes the R2C angle to correspond to a path following (PF) angle request, the PF angle request including the curvature.
[0136] Example 5 includes a vehicle according to any of the foregoing examples, wherein the programmable circuitry is configured to determine whether the trajectory planning includes a lane change of the vehicle, and when the trajectory planning includes the lane change, to calculate the curvature of the trajectory planning based on the vehicle’s current trajectory and a look-ahead point on the current trajectory, and to determine the R2C angle based on the curvature.
[0137] Example 6 includes a vehicle according to any of the foregoing examples, wherein the programmable circuitry is used to calculate the curvature based on the pure tracking law.
[0138] Example 7 includes a vehicle according to any of the foregoing examples, wherein when the trajectory planning includes maintaining the vehicle's current lane, the instructions are used to cause the programmable circuitry to calculate the R2C angle based on a reference path, wheelbase, vehicle speed, understeer gradient, and steering ratio.
[0139] Example 8 includes a non-transitory machine-readable storage medium comprising instructions for causing a programmable circuit system to perform at least the following operations: identifying a trajectory plan for a vehicle; determining a return-to-center (R2C) angle of a steering wheel based on the trajectory, the R2C angle being non-zero; and causing a steering motor to bias the steering wheel's steering angle toward the R2C angle in response to the steering wheel receiving a torque input from the driver.
[0140] Example 9 includes a non-transitory machine-readable storage medium according to any of the foregoing examples, wherein, in order to identify the trajectory planning of the vehicle, the instructions are configured to cause a programmable circuit system to determine whether an evasive maneuver will occur, and when the evasive maneuver is about to occur, cause the R2C angle to correspond to a path-following (PF) angle request, the PF angle request including curvature.
[0141] Example 10 includes a non-transitory machine-readable storage medium according to any of the foregoing examples, wherein the instructions are configured to cause a programmable circuit system to determine whether the trajectory planning includes a lane change of the vehicle, and when the trajectory planning includes the lane change, to calculate the curvature of the trajectory planning based on the vehicle’s current trajectory and look-ahead point, and to determine the R2C angle based on the curvature.
[0142] Example 11 includes a non-transitory machine-readable storage medium according to any of the foregoing examples, wherein the instructions are used to cause a programmable circuit system to calculate the curvature based on the pure trace law.
[0143] Example 12 includes a non-transitory machine-readable storage medium according to any of the foregoing examples, wherein when the trajectory planning includes maintaining the vehicle's current lane, the instructions are used to cause a programmable circuit system to calculate the R2C angle based on a reference path, wheelbase, vehicle speed, understeer gradient, and steering ratio.
[0144] Example 13 includes a non-transitory machine-readable storage medium according to any of the foregoing examples, wherein the trajectory planning of the vehicle includes curvature, wherein the instructions are used to cause a programmable circuit system to determine the curvature based on a map-based reference path at a look-ahead distance and to convert the curvature into a steering angle to determine the R2C angle.
[0145] Example 14 includes a non-transitory machine-readable storage medium according to any of the foregoing examples, wherein the trajectory planning of the vehicle includes curvature, wherein the instructions are used to cause a programmable circuit system to determine polynomial coefficients based on a vision-based reference path and look-ahead distance, determine the curvature based on the polynomial coefficients, and convert the curvature into a steering angle to determine the R2C angle.
[0146] Example 15 includes a method comprising identifying a trajectory plan of a vehicle; determining a return-to-center (R2C) angle based on the trajectory plan; and causing a steering motor to bias a steering angle toward the R2C angle in response to a torque input received by the steering wheel from the driver.
[0147] Example 16 includes the method according to any of the foregoing examples, wherein identifying the trajectory planning of the vehicle includes determining whether an evasive maneuver will occur, and when the evasive maneuver will occur, causing the R2C angle to correspond to a path following (PF) angle request, the PF angle request including curvature.
[0148] Example 17 includes the method according to any of the foregoing examples, further comprising determining whether the trajectory planning includes lane changes of the vehicle, and when the trajectory planning includes lane changes, calculating the curvature of the trajectory planning based on the vehicle’s current trajectory and a look-ahead point on the current trajectory, and determining the R2C angle based on the curvature.
[0149] Example 18 includes the method according to any of the foregoing examples, further comprising determining that the trajectory planning includes maintaining the current lane occupied by the vehicle, and calculating the R2C angle based on a reference path, wheelbase, vehicle speed, understeer gradient, and steering ratio.
[0150] Example 19 includes the method according to any of the foregoing examples, wherein the trajectory planning of the vehicle includes curvature, and the method further includes determining the curvature based on a map-based reference path at a look-ahead distance, and converting the curvature into a steering angle to determine the R2C angle.
[0151] Example 20 includes the method according to any of the foregoing examples, wherein the trajectory planning of the vehicle includes curvature, and the method further includes determining polynomial coefficients based on a vision-based reference path and look-ahead distance, determining the curvature based on the polynomial coefficients, and converting the curvature into a steering angle to determine the R2C angle.
[0152] The appended claims are hereby incorporated by reference into this specific embodiment. While certain example systems, devices, articles of manufacture, and methods have been disclosed herein, the scope of this patent is not limited thereto. Rather, this patent covers all systems, devices, articles of manufacture, and methods that fall fully within the scope of the claims of this patent.
Claims
1. A vehicle comprising: steering wheel; Steering wheels, the steering wheel being operably coupled to the steering wheels; A steering motor, which is activated when the vehicle is in an assisted driving mode to control the steering angle of the steering wheel; as well as Steering controller, the steering controller including instructions and a programmable circuit system, the programmable circuit system being used to execute the instructions to: Access the trajectory plan of the vehicle, the trajectory plan including curvature; The return-to-center (R2C) angle of the steering wheel is determined based on the trajectory planning and vehicle speed; as well as In response to receiving a torque input from the driver, the steering motor causes the steering wheel to deflect the steering angle toward the R2C angle.
2. The vehicle of claim 1, wherein the steering motor provides a reaction torque resistance that acts relative to the R2C angle in a direction opposite to the torque input to deflect the steering angle toward the R2C angle.
3. The vehicle according to claim 1 or claim 2, wherein the programmable circuit system is used to convert the curvature into the R2C angle based on the wheelbase parameter, steering ratio parameter, understeer gradient, vehicle speed, and curvature.
4. The vehicle according to claim 1 or claim 2, wherein the programmable circuit system is used for: Determine whether evasive manipulation will occur; and When the evasion maneuver is about to occur, the R2C angle is caused to correspond to a path following (PF) angle request, which includes the curvature.
5. The vehicle of claim 1, wherein the programmable circuit system is used for: Determine whether the trajectory planning includes the vehicle's lane change; When the trajectory planning includes the lane change: The curvature of the trajectory planning is calculated based on the vehicle's current trajectory and the look-ahead point on the current trajectory; and The R2C angle is determined based on the curvature.
6. The vehicle of claim 5, wherein the programmable circuit system is used to calculate the curvature based on the pure tracking law.
7. The vehicle of claim 5 or claim 6, wherein when the trajectory planning includes maintaining the vehicle's current lane, the instructions are used to cause the programmable circuitry to calculate the R2C angle based on a reference path, wheelbase, vehicle speed, understeer gradient, and steering ratio, the reference path including the curvature.
8. The vehicle according to claim 1 or claim 6, wherein the R2C angle is non-zero.
9. A non-transitory machine-readable storage medium comprising instructions for causing a programmable circuit system to perform at least the following operations: Identify vehicle trajectory planning; The steering wheel return-to-center (R2C) angle is determined based on the trajectory, and the R2C angle is non-zero; and In response to receiving torque input from the driver, the steering motor causes the steering wheel to deflect the steering angle toward the R2C angle.
10. The non-transitory machine-readable storage medium of claim 9, wherein, in order to identify the trajectory planning of the vehicle, the instructions are used to cause the programmable circuit system to: Determine whether evasive manipulation will occur; and When the evasion maneuver is about to occur, the R2C angle is caused to correspond to a path following (PF) angle request, which includes curvature.
11. The non-transitory machine-readable storage medium of claim 9, wherein the instructions are used to cause a programmable circuit system: Determine whether the trajectory planning includes the vehicle's lane change; When the trajectory planning includes the lane change: The curvature of the trajectory planning is calculated based on the vehicle's current trajectory and look-ahead point; and The R2C angle is determined based on the curvature.
12. The non-transitory machine-readable storage medium of claim 11, wherein the instructions are used to cause a programmable circuit system to calculate the curvature based on the pure tracking law.
13. The non-transitory machine-readable storage medium of claim 11 or claim 12, wherein when the trajectory planning includes maintaining the vehicle's current lane, the instructions are used to cause the programmable circuitry system to calculate the R2C angle based on a reference path, wheelbase, vehicle speed, understeer gradient, and steering ratio.
14. The non-transitory machine-readable storage medium of claim 9 or claim 10, wherein the trajectory planning of the vehicle includes curvature, wherein the instructions are for causing the programmable circuit system: The curvature is determined based on a map-based reference path at the look-through distance; and The curvature is converted into a steering angle to determine the R2C angle.
15. The non-transitory machine-readable storage medium of claim 9 or claim 10, wherein the trajectory planning of the vehicle includes curvature, wherein the instructions are for causing the programmable circuit system: The polynomial coefficients are determined based on a vision-based reference path and look-ahead distance. The curvature is determined based on the polynomial coefficients; and The curvature is converted into a steering angle to determine the R2C angle.
