COVESA / vehicle_signal_specification

Vehicle Signal Specification - standardized way to describe automotive data
Mozilla Public License 2.0
320 stars 164 forks source link

Introduce TimeInUse signal for ElectricMotor #725

Closed JonathanForce closed 6 months ago

JonathanForce commented 7 months ago

Description

It would be interesting to know the engine hours for electric motor.

erikbosch commented 7 months ago

Looks good to me, will bring it up on the VSS meeting today. You need to add a sign-off to the commit, for example with git commit -s --amend and then a force push

See https://covesa.global/contribute

JonathanForce commented 7 months ago

Thank you @erikbosch

erikbosch commented 7 months ago

MoM:

erikbosch commented 7 months ago

MoM:

JonathanForce commented 7 months ago

MoM:

  • Jonathon: For us READY state is that if gas pedal is pressed vehicle will move. But definition can vary
  • Daniel: Unclear from when it is measured
  • J: Total time in use
  • Erik: Shall Park be considered READY?
  • Nick: In my vauxhall when moved out of Park
  • S: Also charging is part of vehicle lifetime
  • Please continue review/discuss, lets continue discussion on next meeting

Let's start from the beginning.

What we want: For electric vehicles, we want to determine a degree of wear on parts based on how long the vehicle has been in use.

What is the trigger: We want this time to increase as soon as the vehicle is ON and the transmission is not in the 'Park' position. So, the condition is 'Transmission.SelectedGear' is not '126=Park’.

A question was about the charging time. If you want this signal to remove an ambiguity, we can add a ‘TimeInCharge’ signal based on the ‘Charging.IsCharging’ signal.

erikbosch commented 7 months ago

MoM:

erikbosch commented 6 months ago

MoM: Merge