JRCSTU / CO2MPAS-TA

EU's Type-Approving vehicle simulator predicting NEDC CO2 emissions from WLTP
https://co2mpas.readthedocs.io/
European Union Public License 1.1
25 stars 13 forks source link

Datasync data field titles #21

Closed MaikeruJon closed 7 years ago

MaikeruJon commented 7 years ago

After generating the template to be used for the datasync function, we have a workbook with three worksheets. Looking at the 'dyno' worksheet. What is the data required in such as 'Dyno Engine Coolant Temperature [oC]'? This does not exist. No aspect of the dynamometer is recording engine coolant temperature. Or any other characteristic of the engine, for that matter. Shouldn't this be 'OBD Engine Coolant Temperature', and similarly for all other engine condition data?

gfon commented 7 years ago

@MaikeruJon you don't have to provide any data to the Dyno Engine Coolant Temperature field. It is there rather for engineering purposes (in the beginning of the project before we decided to use OBD signals for ECT there was a discussion on how to measure engine coolant temperature externally).

In any case the idea is to align OBD and dyno datasets and bring them to the same time reference; so the signals provided in the dyno sheet do not have to completely match those of the obd sheet as long as there is one common signal between the two (vehicle speed).

MaikeruJon commented 7 years ago

OK, got it, thanks. So, having done that, the idea is to replace the original data (in the CO2MPAS input file) with the data from the datasync output and then run the CO2MPAS TA simulation, right?

VictorValverde commented 7 years ago

@MaikeruJon Yes that is correct. To summarize:

  1. Populate the datasync template with dyno and OBD series to be synchronized.
  2. Synchronize with the datasync tool
  3. Populate CO2MPAS input file with synched time-series
  4. Run CO2MPAS simulation
MaikeruJon commented 7 years ago

OK, I've got it. Many thanks for your clear guidance.