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

Energy Limit on a transaction - Advice #20

Open
billywatsy opened this issue Aug 16, 2022 · 1 comment
Open

Energy Limit on a transaction - Advice #20

billywatsy opened this issue Aug 16, 2022 · 1 comment

Comments

@billywatsy
Copy link

hi All

Is it possible to send to the OCCP client using the energy value, after which the charger will automatically stop charging?

anyways to which might work

Here is what l think

1: Charge profiles -
{
"connectorId": 0,
"idTag": "xxxxxxxxxxxx",
"chargingProfile": {
"chargingProfileId": 10,
"transactionId": null,
"stackLevel": 0,
"chargingProfilePurpose": "TxProfile",
"chargingProfileKind": "Relative",
"recurrencyKind": "Daily",
"validFrom": "2022-02-18T10:18:46.000Z",
"validTo": "2022-08-18T10:18:46.000Z",
"chargingSchedule": {
"duration": 4200,
"startSchedule": "2022-08-18T10:18:46.000Z",
"chargingRateUnit": "W",
"chargingSchedulePeriod": [
{
"startPeriod": 0,
"limit": 50
},
{
"startPeriod": 120,
"limit": 0
}
]
}
}
}

The last one will send zero currents and probably that time will stop

2: Custom Data Transfer , but this is more of confirming with the vendor right?

@profnimrod
Copy link

This is essentially the same as #19 - basically how do we do server -> client messaging?

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