Code development platform for open source projects from the European Union institutions

Skip to content
Snippets Groups Projects
Commit 866e1467 authored by Markus Quaritsch's avatar Markus Quaritsch
Browse files

Pull request #104: Develop

Merge in VECTO/vecto-dev from VECTO/mq_vecto-dev:develop to develop

* commit '8f803c33':
  bugfix sum-container: initialize output field
  bugfix PEV shift strategy: consider battery state, use correct EM response field for estimating power demand
  postprocessing correction: write energy missing due to ess in sum-file, add dummy correction class for PEV vehicles
  bugfix: engineering data adapter - set overload torque correctly in case of multiple EMs
  fix testcase: set driver acceleration - needed in shift strategy
  correct typo in mission profiel names (verification test)
  add validation that shift parameters are available (GUI)
  effshift: do not upshift if acceleration is negative
  torque converter: in case an operating point has been set in the driver model, ignore acceleration limits reset gearbox disengaged state if set by driver model after the simulation interval
  make check for IsBetween tolerante against mixing min/max values
  initialize clutch losses to 0 in constructor
  Allow emergency shift if engine speed is already 1rpm below max speed (driver model searches to this operating point in case the engine speed is too high)
  use correct SI type
  adapt expected values in testcase
  correct testname
  bev simulation: keep signal for ICE on always false (in case of BEV) - DummyEngine Info
  correct testname
  naming of mod-files in testcase
  rename testcases to avoid duplicate names
  hybrid controller: split calculation of cost and gearshift penalty for debugging purpose allow emergencyshift if ICE is off so that EM speed stays with in range of ICE
parents cf10bec7 8f803c33
No related branches found
No related tags found
No related merge requests found
Showing
with 494 additions and 293 deletions
Loading
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment