1Driver subsystem {#vehicle_driver} 2================================== 3 4\tableofcontents 5 6 7Driver inputs (steering, throttle, and braking) are provided from a driver subsystem with available options in Chrono::Vehicle including interactive, data-driven, and closed-loop (e.g., path-following based on PID controllers). 8 9The base class for a driver system, [ChDriver](@ref chrono::vehicle::ChDriver), imposes minimal requirements from a driver system template, in particular the ability to return throttle input (normalized in the \f$[0,1]\f$ range), steering input (normalized in the \f$[-1, +1]\f$ range, with a negative value indicating steering to the left), and braking input (normalized in the \f$[0,1]\f$ range). In addition, a driver system can receive information from any other system (e.g., the vehicle state) through its `Synchronize` method and may have internal dynamics (implemented in its `Advance` method). Specific templates for a driver system may extend the set of vehicle inputs generated, for example including the current selected gear for a manual transmission, enabling/disabling the cross-drive capability on a tracked vehicle, etc. 10 11Chrono::Vehicle includes several templates for driver systems. For interactive simulations, run in soft real-time, it provides a template for a driver system which produces the vehicle inputs based on user controls, either keyboard and mouse, or a game controller. 12 13For design of experiment simulations, it provides a driver system template that is based on inputs provided through a text data file, with the vehicle inputs obtained through linear interpolation. Such data files can also be automatically generated by data collected during interactive runs. 14 15Finally, Chrono::Vehicle includes several closed-looped driver system models, based on underlying support for PID controllers. These include speed controllers (which adjust the throttle and braking input simultaneously to maintain a constant vehicle speed) and path-follower controllers. The latter adjust the steering input so that the vehicle follows a user-defined path specified as a Bezier curve. 16 17 18## Interactive driver {#vehicle_driver_interactive} 19 20The interactive driver [ChIrrGuiDriver](@ref chrono::vehicle::ChIrrGuiDriver) can control (steer/accelerate/brake) a simulated vehicle through user input. Since it relies on Irrlicht to handle keyboard events, it is only available with Irrlicht based programs. 21- key `A` increases left turn steering wheel angle 22- key `D` increases right turn steering wheel angle 23- key `W` accelerate 24- key `S` decelerate 25 26The throttle and braking controls are coupled, in the sense that acceleration first drives braking to zero before increasing throttle input (and vice-versa for deceleration). 27 28Other features of this driver subsystem model include: 29- experimental joystick support 30- ability to lock/unlock driver inputs to their current values (controlled through key `J`) 31- ability to record and playback user inputs (using an embedded data-based driver; see below) 32 33## Data-based (open-loop) driver {#vehicle_driver_data} 34 35Some important vehicle test maneuvers are based on time-dependent steering/throttling/brake signals. No feedback of any kind is considered. This driver model is implemented in [ChDataDriver](@ref chrono::vehicle::ChDataDriver). 36 37An ASCII data file with driver inputs contains four columns, for time (s), steering input (a non-dimensional quantity in \f$[-1,1]\f$, with \f$-1\f$ indicating full steering to the left), throttle input (a non-dimensional quantity between \f$[0,1]\f$, with \f$1\f$ indicating full throttle), and braking (a non-dimensional quantity between \f$[0,1]\f$, with \f$1\f$ indicating full braking force). 38 39A sample driver data file is listed below 40\include "../../data/vehicle/generic/driver/Sample_Maneuver.txt" 41 42<img src="http://www.projectchrono.org/assets/manual/vehicle/curves/DataDriver.png" width="500" /> 43 44At any given time, the current driver inputs (steering, throttle, and braking) are obtained by piece-wise linear interpolation of the provided data. Beyond the last time entry, driver inputs are kept constant at their last values. 45 46 47## Close-loop driver models {#vehicle_driver_closed_loop} 48 49Close-loop driver models need a control strategy and consider feedback. Feedback can lead to instable behavior, so the controller parameters have to be chosen wisely. The example parameters have been working in a wide range of use. The user should start with one of the given example parameter sets and only modify it if necessary. 50 51### Path-follower controller 52 53To make the vehicle follow a given path it is necessary to measure the lateral path deviation and to generate a steering wheel angle that minimizes the deviation. A well known solution for this problem is the PID controller (P=proportional, I=Integral, D=Differential). Taking the pure P variant one only needs to set the P-gain. This will work in many cases but pure P controllers can never reduce the lateral deviation to zero. The residual deviation decreases with increasing P-gain. If the P-gain is too large, the vehicle begins to oscillate around the demanded vehicle path. A residual path deviation can be eliminated by setting the I-gain to a value of around 5% to 10% of the P-gain. By setting the D-gain it is possible to apply damping if a path oscillation occurs. If the I-gain is used, the simulated maneuver should not take longer than about 2 minutes. If it takes more time, the controller states should be reset every 2 minutes to avoid instabilities. 54 55The next chart (Wikipedia) shows how Chrono implements the PID controllers: 56 57<img src="https://upload.wikimedia.org/wikipedia/commons/thumb/4/43/PID_en.svg/2880px-PID_en.svg.png" width="500"/> 58 59- r(t) = demanded path signal 60- e(t) = lateral path deviation 61- y(t) = actual path signal 62- u(t) = steering signal 63 64This chart (Wikipedia) shows the influence of the gain factors: 65 66<img src="https://upload.wikimedia.org/wikipedia/commons/3/33/PID_Compensation_Animated.gif" width="500"/> 67 68A human driver does not only react on deviation changes, he is able to anticipate. In Chrono this ability is simulated by taking a reference point for measuring the deviation in front of the vehicle body. The distance of the reference point from the vehicle reference system is called look-ahead-distance and is an important controller input parameter. 69 70The desired path is specified as a Bezier curve (see [ChBezierCurve](@ref chrono::ChBezierCurve)). The error is defined as the deviation between a "sentinel point" (a point located at the look-ahead distance in the vehicle forward direction) and a "target point" (the projection of the sentinel point onto the desired path). 71 72### Constant-speed controller 73 74To maintain a given vehicle speed the PID controller can be used. The difference to the path controller is that it uses a speed deviation instead of the lateral path deviation. 75 76- r(t) = demanded speed signal 77- e(t) = speed deviation 78- y(t) = actual speed signal 79- u(t) = throttle/brake signal 80 81The class [ChPathFollowerDriver](@ref chrono::vehicle::ChPathFollowerDriver) implements the PID lateral controller in combination with a PID speed controller. It works well at extreme maneuvers like double lane change. 82 83An interesting alternative for standard road driving maneuvers is [ChPathFollowerDriverSR](@ref chrono::vehicle::ChPathFollowerDriverSR). It has a PID speed controller but takes lateral control strategy that considers human and vehicle properties. The anticipation uses look-ahead time instead of a look-ahead distance which means the effective look-ahead distance varies with the speed. 84 85### Optimal-speed controller 86 87The constant-speed controller is good for many standard driving maneuvers. For driving on a long and curved road it is interesting how fast the vehicle can negotiate the whole course. For cases like this the [ChHumanDriver](@ref chrono::vehicle::ChHumanDriver) class has been developed. Both the lateral and the speed controllers use human behavior, vehicle properties, and anticipation as well as field of view of the driver. The lateral controller is identical to the one implemented in [ChPathFollowerDriverSR](@ref chrono::vehicle::ChPathFollowerDriverSR). 88 89 90 91
