-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update to Co2mpas 3.0.1. #43
Comments
Dear @koglerp, Can you please inform us about the reason for re-running the simulations? According to the regulation and the amendment (EU) 2018/2043, We look forward to your reply. |
Dear all,
According the EU COM Note from 05.02.2019 we have to ensure that all correlation files for vehicles placed on the market in 2020 are run with DICE3:
However, for all new vehicles placed on the market in 2020, for which the input data
have not been submitted in accordance with the DICE3 procedures, the correlation files
will have to be up-dated in accordance with a CO2MPAS 3.0.X. execution and submitted
to DICE3 retroactively and no later than 30 April 2021.
We have IP families, which did not run with Dice3 yet but will be placed on the market in 2020, therefore we perform the 3.0.0. simulation with the 3.0.1. inputfile as requested by the Note.
Best regards
|
Dear @koglerp, We understand that you refer to paragraph 2. OFFICIAL VERSION OF THE CO2MPAS CORRELATION TOOL of note in DG Clima's page about the correlation implementation.
This paragraph refers to the vehicles DICEd in the period between 1 February and 29 March 2019 with the CO2MPAS version 2.0.0 and DICE2. Do the Interpolation Families that you refer to fall in this category? We look forward to your reply. |
Dear all,
Yes, I’m referring to that paragraph. Nevertheless, due to the sentence “However, for all new vehicles placed on the market in 2020…” we understand that the update must be made for all 2020 vehicles and not only the ones, which have been diced with the old version in the period Feb – Mar 2019. About 5% of our “before 3.0.1. IPs” have been diced in this period, all others where diced before – and all of them can be registered in 2020 as they are at least EU6dTemp(DG) vehicles.
Best regards
|
Dear @koglerp, Since this question is regulation related, and not technical regarding CO2MPAS, Kind regards. |
Dear all,
due to the fact that an inputfile 3.0.1. must be provided for all vehicles registered in 2020 we run now an update wave for all concerned IP Familys which have been simulated with an older version (mostly 2.2.7.).
The requirements for the older files where different, there was no 10Hz dyno velocity requested for example. In the "development mode" this is not a problem, I can perform the simulation also without this values. But during TA mode our technical service gets an error because of the missing dates. As these values haven't been requested during the original certification runs we don't have these dates.
Do you have a suggestion how we can solve this and run valid simulations?
Thanks and best regards
The text was updated successfully, but these errors were encountered: