Evcharger
[Residential loads (residential)]
There are only two types of electric vehicles supported:. More...
Typedefs | |
|
typedef struct s_evdemandprofilelist | EVPROFILEITEM |
| EV Demand Profiles. | |
Functions | |
| EVPROFILEITEM * | add_demand_profile (EVDEMAND *data) |
| Add an EV demand profile. | |
| EVDEMAND * | find_demand_profile (char *name) |
| Find an EV demand profile. | |
Detailed Description
There are only two types of electric vehicles supported:.
- ELECTRIC pure electric vehicle with limited range based on battery capacity
- HYBRID hybrid electric vehicle with longer range based on fuel capacity
The evcharger simulation is based on demand state profile of the vehicle. When the vehicle is at home, it has a probability of leaving on one of 3 trips.
Figure 1 - EV charger state diagram
- WORK trip to work (standard distance defined by trip.d_work)
- SHORTTRIP random trip up to 50 miles (battery will not be fully discharged)
- LONGTRIP random trip over 50 miles (battery will be discharged up to 25%) but only possible for HYBRID vehicles
Figure 2 - EV charger home/work arrival/departure statistics
When away, the probability of a return is used to determine when the vehicle returns.
The charger power can have one of three levels:
- LOW 120V/15A charger
- MEDIUM 240V/30A charger
- HIGH 240V/60A charger
The trip distances is used to estimate the battery charge upon return according to the following rules:
1. A work trip discharges the battery depending on whether charge_at_work is defined. If charging at work is allowed, the battery will discharge for 1 trip, otherwise it will discharge for 2 trips.
2. A short trip discharges the battery based on the distance traveled.
3. A long trip discharges the battery to 25%, but is only possible with hybrids.
In all cases, if the trip distance is greater than 50 miles and the car is a hybrid, the discharge will be down to 25%.
Heat fraction ratio is used to calculate the internal gain from plug loads.
- Demand profiles
The format of the demand profile is as follows:
[DAYTYPE] DIRTRIP,DIRTRIP,... #.###,#.###,... #.###,#.###,... . . . #.###,#.###,...
where DAYTYPE is either WEEKDAY or WEEKEND, DIR is either ARR or DEP, and TRIP is either HOME, WORK, SHRT, or LONG. There must be 24 rows of numbers, the numbers must be positive numbers between 0 and 1, and each column must be normalized (they must add up to 1.000 over the 24 hour period).
You may introduce as many daytype blocks as are supported simultaneously (2 max at this time).
- Todo:
- the 24 rows are not check for compliance with the 24 hour rule, the 0-1 rule, or the normalized rule.
Function Documentation
| EVPROFILEITEM* add_demand_profile | ( | EVDEMAND * | data | ) |
Add an EV demand profile.
- Returns:
- pointer to the new EVPROFILEITEM structure
Definition at line 112 of file evcharger.cpp.
| EVDEMAND* find_demand_profile | ( | char * | name | ) |
Find an EV demand profile.
- Returns:
- pointer to the matching EVPROFILEITEM structure
- Parameters:
-
name name of profile
Definition at line 98 of file evcharger.cpp.