How to pause the charging process EVSE side?
lovalova1991 opened this issue · 1 comments
lovalova1991 commented
As far as i understand from the ISO15118-2 normative there's no written way to suspend the charging process from the EVSE side. Setting power to zero is not going to work because the car during the charging loop is expecting to receive energy.
Does somebody know how it's possible to implement this behaviour in the project?
Thanks.
tropxy commented
Hi Daniele,
You are right, in -2 there is no way to formally force a pause of the
communication. I think there are only two options..
1. is to do a renegotiation of the schedule and advertise a Schedule in the
ChargeParameterDiscoveryRes that contains a long period with 0 W or close
to it…that may trigger the Pause in the EV
2. second is the one you mentioned and force the min the EVSE can do
(possibly 0 W) in the charge loop.
Neither of the above methods is a guarantee that the EV will request a
Pause, but at least you can influence the amount of power the EV will
consume and by knowing more or less the standby power of the EV, you can
keep the OBC on and yet avoid charging the EV. Unfortantelly, I dont think
there is another way to do something that resembles pausing…
Best regards,
—
[image: signature_1470162048]
*André Duarte*
CTO at Switch <https://switch-ev.com/>
LinkedIn <https://www.linkedin.com/in/andrefilipef1/>
The Ministry, 79-81 Borough Road, London SE1 1DN
…On Tue, 26 Sept 2023 at 20:29, Daniele Lovato ***@***.***> wrote:
As far as i understand from the ISO15118-2 normative there's no written
way to suspend the charging process from the EVSE side. Setting power to
zero is not going to work because the car during the charging loop is
expecting to receive energy.
Does somebody know how it's possible to implement this behaviour in the
project?
Thanks.
—
Reply to this email directly, view it on GitHub
<#303>, or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AC7PVFU2H4DQFLWEGAIEDW3X4MUJZANCNFSM6AAAAAA5IHG64U>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>