For the predictive calculation of possible operating states and the subsequent determination of the most efficient engine operation, it is necessary to estimate the upcoming driving demands and calculate the power required by the drivetrain. Future operating points are therefore dependent on the vehicle, driver, and route. To calculate driving demands using driving resistances, vehicle parameters such as the drag coefficient (cw-value), vehicle mass, road gradient, and vehicle speed are required. [7]
3.1 Necessary Data set
Vehicle Dependency:
The vehicle parameters can be measured or are determined by the vehicle manufacturer based on the installed hardware components, such as the internal combustion engine and electric motor, and based on their respective operation through the ECU. These parameters are fixed data sets that need to be defined once and stored in the control software of the operating strategy, where they can be retrieved during calculations. The vehicle load plays an important role in computing the power demand and is assumed to computed based on driving conditions.
Route Dependency:
The gradient, which depends on the geographic position of the vehicle, can be calculated using online map data. If information about a planned route is available, an elevation profile can be created for prediction purposes. In navigation systems, route information is already retrieved to calculate travel time and the optimal route. Thus, these data are generally available if a destination is defined at the start of the journey. Using machine learning algorithms, this step can also be automated, for example, if the driver takes the same route to work every morning.
Driver Dependency:
By building a driver model, the speed profile for the predicted route can also be created based on the route data. This driver model requires defining driver characteristics such as desired speed, lateral, and longitudinal acceleration. Measurements from real-world driving are used beforehand to evaluate these parameters. The driver model can then calculate a speed profile for the route, taking physical constraints into account.
The speed and elevation profiles together form the predictive driving demand, which is subsequently used to determine the necessary operating points.
3.2 Vehicle model
Instead of a completely data-driven approach the vehicle model is equation based where parameters are identified using experimental data. Therefore a vehicle model was developed based on measurement data from real-world driving tests and examined on the engine test bench in a hardware-in-the-loop (HiL) simulation. Validation of the simulation model was carried out using various test scenarios, enabling further investigations in the simulation. First, the driving resistance coefficients were measured through coast-down tests, and the drivetrain components were modeled as in the vehicle. The test scenarios included driving the WLTC on a chassis dynamometer and conducting an RDE test drive. For comparison, the energy consumption at the wheels was calculated for each test. To achieve this, the power delivered to the wheels was calculated at each time step from the driving resistances and then integrated to determine the total energy consumption. [8]
3.3 Online data request
In online available Digital Mapping Services such as Google-Maps or HereWeGo, the beforehand described route information is stored and accessible. This includes not only geographic coordinates and elevation data but also speed limits and average vehicle speeds at specific route points. Additionally, information about intersections or traffic lights is available and can be retrieved. These data can also be used to improve the accuracy of speed prediction calculations.
For data retrieval in the simulation, a Python-based application (API) was developed to fetch the required route data via a JSON interface from the internet. During the initialization of the simulation, a GUI opens where, similar to a navigation system, the route can be defined, and some settings for data retrieval can be configured.
In the fields "Departure" and "Arrival," the start and destination points of the route are entered. These can either be simple city names, as shown in the illustration, or alternatively, full addresses or coordinates can be provided. Under "Routing Options," the traffic influence can be enabled or disabled. When enabled, the retrieved "traffic speed" is adjusted to the selected day and time. Activating the "Loading GPX from File" function opens a separate window for selecting a GPX file, and instead of using the "Departure" and "Arrival" fields, the route is retrieved along the GPS points specified in the GPX file.
The "Submit" button allows modifications to the settings for saving the data, and the retrieval process is then initiated. The data is also saved in an Excel spreadsheet, which, as shown in Figure 5, assigns the corresponding details to each data point. These details consist partly of raw data from the retrieval process and partly of calculated values, as previously mentioned.
3.4 Data-preprocessing
The key data for the driving strategy include latitude and longitude, elevation, curve curvature, speed limit, traffic speed, and the so-called intersection bit. The data points are typically located at relevant points on the route, such as intersections, speed limit change points, or curve apexes. Since these points are solely dependent on the infrastructure, the data points are distributed along the route at non-equidistant intervals. Therefore, a calculated "Travel Distance" variable is stored to provide the total distance in meters. This distance can be calculated from the geocoordinates using the Haversine formula and is directly transmitted by the map provider during data retrieval. This enables distance-based assignment of boundary conditions for the subsequent speed calculation. However, gaps of over 50 meters between consecutive points can occur. A speed profile calculation at this resolution is insufficient for the subsequent calculation of operating points, as the dynamic operation of the engines leads to rapid changes in operating states. Therefore, an interpolation to 5-meter intervals is performed, which also allows for case-dependent differentiation in the calculation of the curve radius. This improves the determination of curvature, which is necessary for speed prediction in curves. The curvature is calculated from the coordinates of three consecutive points using the circle equation. As mentioned, the distances between data points can vary, particularly in urban areas, where data points might only exist at the midpoints of two adjacent intersections. In such cases, a curve radius would be calculated that is significantly too large. With 5-meter intervals between the three points used in the circle equation, practically all tight curve radii in typical road traffic can be calculated. However, this approach presents a challenge for long curves in rural areas. Due to the interpolation, many points lie on straight lines where the curvature is zero, and only the points between these straight sections yield overly tight curve radii. This issue can be resolved through a combination of the curvature calculations. For tight urban curves, the radius calculated after interpolation is used, while for rural areas, the values calculated before interpolation are applied. The case differentiation is based on traffic speed: if the traffic speed exceeds a defined threshold, the pre-interpolation calculation is used. [8]
For elevation data, it is common to encounter a resolution of only 1 meter, which can result in very high gradient values for closely spaced points. This would lead to short, high load demands in subsequent calculations, which do not reflect the real driving profile. The issue of the low-resolution elevation profile can be mitigated using a smoothing function. However, configuring the smoothing factors proves challenging: overly high factors smooth out too many road irregularities, while overly low factors fail to address the existing problem. An alternative solution is to replace the retrieved elevation profile with a more accurate one, such as one recorded during a real drive along the route using an inertial navigation system (INS).