Gelöste Aufgaben/JUMP/Driver Controls: Unterschied zwischen den Versionen

Aus numpedia
Zur Navigation springen Zur Suche springen
Keine Bearbeitungszusammenfassung
Keine Bearbeitungszusammenfassung
Zeile 4: Zeile 4:
Since we’re in a 2D-simulation environment, the driver controls only “gas” (acceleration) and breaks - no directional control needed to be taken into account.
Since we’re in a 2D-simulation environment, the driver controls only “gas” (acceleration) and breaks - no directional control needed to be taken into account.


= Scope =
== Scope ==
[[Datei:JUMP-driver-blockdiagram.png|mini|Block diagram]]
[[Datei:JUMP-driver-blockdiagram.png|mini|Block diagram]]
The track poses challenges that require the driver to control the driving and breaking torque on the wheel. These track-specific challenges include
The track poses challenges that require the driver to control the driving and breaking torque on the wheel. These track-specific challenges include

Version vom 10. März 2021, 14:02 Uhr

← Back to Start


Since we’re in a 2D-simulation environment, the driver controls only “gas” (acceleration) and breaks - no directional control needed to be taken into account.

Scope

Block diagram

The track poses challenges that require the driver to control the driving and breaking torque on the wheel. These track-specific challenges include

  • achieving maximum acceleration, thus avoiding wheel-skid and adjusting to a slip that provides optimal traction,
  • achieving maximum deceleration when breaking and therefore avoiding wheels becoming locked,
  • avoiding excessive battery-temperatures and thus controlling driving torque.
Driver Controls

Structure

Block-diagram controller

Model

Friction characteristic and desired skid-velocity-range.

Variables

Parameter


>

next workpackage: e-motor and drive-train →


References

  • ...