pub struct ChargingProfile {
pub custom_data: Option<CustomData>,
pub id: i64,
pub stack_level: i64,
pub charging_profile_purpose: ChargingProfilePurposeEnum,
pub charging_profile_kind: ChargingProfileKindEnum,
pub recurrency_kind: Option<RecurrencyKindEnum>,
pub valid_from: Option<DateTime>,
pub valid_to: Option<DateTime>,
pub charging_schedule: Vec<ChargingSchedule>,
pub transaction_id: Option<String>,
}Expand description
Charging_ Profile A ChargingProfile consists of ChargingSchedule, describing the amount of power or current that can be delivered per time interval.
Fields§
§custom_data: Option<CustomData>§id: i64Identified_ Object. MRID. Numeric_ Identifier Id of ChargingProfile.
stack_level: i64Charging_ Profile. Stack_ Level. Counter Value determining level in hierarchy stack of profiles. Higher values have precedence over lower values. Lowest level is 0.
charging_profile_purpose: ChargingProfilePurposeEnum§charging_profile_kind: ChargingProfileKindEnum§recurrency_kind: Option<RecurrencyKindEnum>§valid_from: Option<DateTime>Charging_ Profile. Valid_ From. Date_ Time Point in time at which the profile starts to be valid. If absent, the profile is valid as soon as it is received by the Charging Station.
valid_to: Option<DateTime>Charging_ Profile. Valid_ To. Date_ Time Point in time at which the profile stops to be valid. If absent, the profile is valid until it is replaced by another profile.
charging_schedule: Vec<ChargingSchedule>§transaction_id: Option<String>SHALL only be included if ChargingProfilePurpose is set to TxProfile. The transactionId is used to match the profile to a specific transaction.