Skip to content
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

Bi fuel vehicles and CO2MPAS - DICE procedure #29

Open
dimitriskomnos opened this issue Jul 3, 2018 · 3 comments
Open

Bi fuel vehicles and CO2MPAS - DICE procedure #29

dimitriskomnos opened this issue Jul 3, 2018 · 3 comments

Comments

@dimitriskomnos
Copy link
Contributor

Dear CO2MPAS users,

Regarding Bi fuel vehicles

We propose that the dice is run only once in the case of an interpolation family consisting of

  • bi-fuel, or
  • flex-fuel vehicles (even though there are two CO2MPAS reports).

If the vehicle is selected for a random test, the test should be performed with the fuel for which the CO2 emission value is taken for the CO2 monitoring in accordance with the table below (taken from the monitoring guidelines for Member States see full document on the following link:
https://circabc.europa.eu/sd/a/015f736b-e2d1-42d0-ac9d-e98ae45b2617/MS%20Guidelines%202016%20data%20FINAL.pdf

"The following table specifies the entries for fuel type and fuel mode for each fuel combination. For the fuel mode the permitted entries are:

  • "M" for mono fuel vehicles;
  • "B" for bi-fuel vehicles;
  • "F" for flex-fuel vehicles.
  • "E" for battery electric vehicles (BEV), i.e. "pure" electric vehicles (NOT hybrid vehicles)

image

Multi-fuel vehicles are capable of running on various combinations of the above fuel types. The lower CO2 figures between all possible combinations of two fuels should be taken. For example for a vehicle capable of running on petrol / LPG / ethanol (E85) the possible combinations are: petrol, petrol-LPG, petrol-E85. The lowest CO2 value between petrol (combined entry) and LPG should be reported and this vehicle should be treated as a petrol-LPG bi-fuel vehicle. Other examples are given below:

  • Petrol / LPG / ethanol (E85) / hydrogen. Considering the relatively scarce availability of hydrogen compared to the other fuels the CO2 values should be the same as for a Petrol / LPG / ethanol (E85) vehicle.
  • Hybrid electric (off vehicle charging, OVC) vehicles ("plug-in hybrid"): the procedure outlined in Regulation (EC) No 692/2008 (Annex XII) for measuring both the fuel (Petrol/ Diesel/ Ethanol 85) consumption and the electricity consumption applies. For these vehicles, the figure to be considered is the weighted combined CO2 emission value of the emission testing.
  • Hybrid electric (not off vehicle charging, NOVC) vehicles are "non plug-in hybrid" vehicles that recuperate energy but cannot take electric energy from external sources. The same testing procedure as for petrol / LPG / ethanol (E85) applies. "
@dimitriskomnos
Copy link
Contributor Author

Example case:

Vehicles are tested with LPG and gasoline.

A regular workflow for this would be:

  1. You run CO2MPAS two times, one for every fuel with its respective data.
  2. After running the 2 Input files, you import in the DICE project the 2 different inputs and outputs.
    Here, an example:
> co2dice project init IP-10-AAA-2017-0000
...
Project(IP-10-AAA-2017-0000: empty)
> co2dice project append -i input_gasoline.xlsx -i input_lpg.xlsx
...
> co2dice project ls . 
* IP-10-AAA-2017-0000: wltp_inp
> co2dice project append -o output_gasoline.xlsx -o output_lpg.xlsx 
...
> co2dice project ls . 
* IP-10-AAA-2017-0000: wltp_iof
> co2dice project report
...

This will generate a DICE report consisting from the 2 output CO2MPAS reports.
Then, you may continue with the regular workflow (stamp, parse...) and as explained in the comment above

@ankostis
Copy link
Member

ankostis commented Jul 3, 2018

Better group the files that are related:

> co2dice project append -  i input_gasoline.xlsx   -o output_gasoline.xlsx 
> co2dice project append   -i input_lpg.xlsx   -o output_lpg.xlsx   --force

@ankostis
Copy link
Member

ankostis commented Jul 3, 2018

Notice that since adding 4 files is not the regular workflow,
you need to add the --force flag the 2nd time you run the append command
(i had forgotten that in my previous message).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants