Interface ChargingTarget

This field represents the amount of energy that the user would like to have added to the vehicle before the TargetTimeMinutesPastMidnight.

This represents a positive value in mWh that SHOULD be added during the session (i.e. if the vehicle charging is stopped and started several times, this equates to the total energy since the vehicle has been plugged in).

The maximum value (500kWh) is much larger than most EV batteries on the market today. If the client tries to set this value too high then the EVSE will need to start charging immediately and continue charging until the vehicle stops demanding charge (i.e. it is full). Therefore the maximum value should be set based on typical battery size of the vehicles on the market (e.g. 70000Wh), however this is up to the client to carefully choose a value.

NOTE

If the EVSE can obtain the Battery Capacity of the vehicle, it SHOULD not limit this AddedEnergy value to the Battery Capacity of the vehicle, since the EV may also require energy for heating and cooling of the battery during charging, or for heating or cooling the cabin.

This field represents the target SoC that the vehicle should be charged to before the TargetTimeMinutesPastMidnight.

If the EVSE can obtain the SoC of the vehicle:

• the TargetSoC field shall take precedence over the AddedEnergy field.

• the EVSE SHOULD charge to the TargetSoC and then stop the charging automatically when it reaches that point.

• if the TargetSoC value is set to 100% then the EVSE SHOULD continue to charge the vehicle until the vehicle decides to stop charging.

If the EVSE cannot obtain the SoC of the vehicle:

• in this case, the AddedEnergy field shall take precedence over the TargetSoC field, and the TargetSoC field may only take the values null or 100%.

• if the AddedEnergy field has not been provided, the EVSE SHOULD assume the vehicle is empty and charge until the vehicle stops demanding a charge.

This field shall indicate the desired charging completion time of the associated day. The time will be represented by a 16 bits unsigned integer to designate the minutes since midnight. For example, 6am will be represented by 360 minutes since midnight and 11:30pm will be represented by 1410 minutes since midnight.

This field is based on local wall clock time. In case of Daylight Savings Time transition which may result in an extra hour or one hour less in the day, the charging algorithm should take into account the shift appropriately.

Note that if the TargetTimeMinutesPastMidnight values are too close together (e.g. 2 per day) these may overlap. The EVSE may have to coalesce the charging targets into a single target. e.g. if the 1st charging target cannot be met in the time available, the EVSE may be forced to begin working towards the 2nd charging target and immediately continue until both targets have been satisfied (or the vehicle becomes full).

The EVSE itself cannot predict the behavior of the vehicle (i.e. if it cannot obtain the SoC from the vehicle), so should attempt to perform a sensible operation based on these targets. It is recommended that the charging schedule is pessimistic (i.e. starts earlier) since the vehicle may charge more slowly than the electrical supply may provide power (especially if it is cold).

If the user configures large charging targets (e.g. high values of AddedEnergy or SoC) then it is expected that the EVSE may need to begin charging immediately, and may not be able to guarantee that the vehicle will be able to reach the target.