search

lincomatic / open_evse

Firmware for Open EVSE
GNU General Public License v3.0
114 stars 163 forks source link

Set temporary (single session only) charging current #80

Closed glynhudson closed 6 years ago

glynhudson commented 6 years ago

As far as I'm aware using the volatile flag when setting charging current e.g $ SC [amps] V only restores the original current after a reboot.

Would it be possible to add a RAPI flag to set a temporary (single session only) current? After the session ends (car is unplugged) the current would restore back to default.

Maybe a S flag could be used for this to denote session? e.g.

$ SC [amps] S

lincomatic commented 6 years ago

Could you help me understand the use case for this feature ?

Sent from my iCrap

On Dec 28, 2017, at 8:34 AM, Glyn Hudson notifications@github.com<mailto:notifications@github.com> wrote:

As far as I'm aware using the volatile flag when setting charging current e.g $ SC [amps] V only restores the original current after a reboot.

Would it be possible to add a RAPI flag to set a temporary (single session only) current? After the session ends (car is unplugged) the current would restore back to default.

Maybe a S flag could be used for this to denote session? e.g.

$ SC [amps] S

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/lincomatic/open_evse/issues/80, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABWzajch_eIYnz3zyFs1jDXb0p6aBQjpks5tE8MPgaJpZM4ROd8v.

glynhudson commented 6 years ago

It's a common use case of users on site renewable generation or variable available power to want to charge at a particular rate for a particular season e.g user is home when solar pv is generating therefore set charging rate to 6A/10A for that charging session. Then when another session is started later in the evening the default (faster) charging rate should he restored to allow the EV to charge normally again.

Or the opposite: a user may choose to charge at a higher rate than usual since they are desperate for a quick topup charge, this charging current may not be suitable for normal use if other applications are running.

The final usecase I've come across is users using the openevse as a portable evse therefore the charging current is set at each location depending on what electrical outlet the EVSE is connected to.

On 29 Dec 2017 20:10, "lincomatic" notifications@github.com wrote:

Could you help me understand the use case for this feature ?

Sent from my iCrap

On Dec 28, 2017, at 8:34 AM, Glyn Hudson <notifications@github.com<mailto: notifications@github.com>> wrote:

As far as I'm aware using the volatile flag when setting charging current e.g $ SC [amps] V only restores the original current after a reboot.

Would it be possible to add a RAPI flag to set a temporary (single session only) current? After the session ends (car is unplugged) the current would restore back to default.

Maybe a S flag could be used for this to denote session? e.g.

$ SC [amps] S

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHubhttps://github.com/ lincomatic/open_evse/issues/80, or mute the threadhttps://github.com/ notifications/unsubscribe-auth/ABWzajch_eIYnz3zyFs1jDXb0p6aBQjpks5tE8M PgaJpZM4ROd8v.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/lincomatic/open_evse/issues/80#issuecomment-354494891, or mute the thread https://github.com/notifications/unsubscribe-auth/AAuUPBVS9MLAsHOXSqFG2JKmY-8C99Neks5tFUdKgaJpZM4ROd8v .

lincomatic commented 6 years ago

Couldn't this be implemented on the RAPI client side? A notification is sent out whenever the EVSE changes state. The RAPI client could act upon this and reset the max current using the existing framework.

glynhudson commented 6 years ago

Yeah sure, it could be. There are more important features more worthy implementing e.g #81 I will close this issue.