# Concept for Generating Energy Demand in Electric Vehicles with a Model Based Approach
## 5 Simulation and Result
### Results  
As in the previous presented validation, the same vehicle model and the same route were used here for the real measurement under approximately the same conditions as in the simulation. For the simulation of a real test drive, a round trip from Bruchsal to Karlsruhe and back to Bruchsal (BR-HKA-BR Circuit) was selected and modeled. In order to approach a typical real trip as realistically as possible, the route included highway, urban and extra-urban roads and thus covered all common speed ranges (see Figure 12) [18; 41]. This covers 16.7 km of urban roads, 22.2 km of extra-urban roads and 18.2 km of highway. There are 44 speed limits and 33 traffic lights on the route. The speed limits are shown in Figure 12 for the route layout. The topology of the route is shown in Figure 13, where the maximum altitude difference is 25 m.  
The conditions for the simulation were adapted to those of the real test drives. The automatic climate control was activated at the medium level. The temperature of the surrounding area was 20 \({}^{\circ}\)C. The speed profile of the simulation was implemented by the speed limits set in the _RouteGenerator_ and the driver model. This virtual driver shows a normal driving behavior with medium accelerations and adapted maneuvers in curves. \begin{table}
\begin{tabular}{l c c c c} \hline \hline  & **Unit** & **Literature** & **Simulation** & **Deviation in (\%)** \\ \hline
**Distance** & km & 10.93 & 11.01 & 0.73 \\
**Duration** & s & 1180 & 1180 & 0.00 \\
**Range** & km & 190 & 188 & \(-\)1.05 \\ \hline
**Energy Demand** & kWh/100 km & 11.58 & 11.72 & 1.21 \\ \hline \hline \end{tabular}
\end{table} 
Table 5: Validation of the determined simulation results of the NEDC. Figure 12: Route from Bruchsal to Karlsruhe and back to Bruchsal with indicated speed limit [18]. Figure 14 shows the speed profile of the real vehicle and the simulated vehicle. By using the real route data and traffic data, traffic influences are included in the speed profile in addition to the pure speed limits. It can be seen that the dynamic course of the simulation corresponds closely to the real measured course. The simulation shows that during the highway section, traffic-induced speed reductions have been taken into account. In the simulation, this occurs somewhat earlier than in the real measurement due to the available traffic data. Additionally, stop-and-go situations due to traffic were depicted in the simulation in the urban area (around the 30 km mark). The speed profile also allows conclusions to be drawn, to a certain extent, about the dynamic behavior of the energy consumption characteristic. The comparison of the simulated values and the real measured values results in a deviation of the covered distance of 2.19%. This results, on the one hand, from the difference of the actual driving line of the vehicle (lane center in the simulation and possible lane changes in the real driving) and, on the other hand, from the accuracy of the GPS track data over the API and the real track. The deviation of 4.63% which occurs in the driving time can be explained by the differences between the traffic light times of the simulation  
Figure 14: Measured and simulated speed profile of the route from Bruchsal to Karlsruhe and back. Figure 13: Altitude data of the route from Bruchsal to Karlsruhe and back [41]. and the real traffic light phases and the deviation between the retrieved traffic data and the actual traffic volume. For more representative results, the route was driven several times for the real measurement, and the respective parameters were recorded. Due to the mentioned influencing parameters, there were differences in driving duration during the real measurement, which in the minimum amounted to \(-0.23\%\) and in the average to the used \(4.63\%\). The difference in average speed traveled of \(4.24\%\) between simulation and real measurement is due to the adaptive driver model and the simulated traffic volume.