OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

ocpp message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] (OCPP-120) Charging Pool Reservation support

Franc Buve created OCPP-120:

             Summary: Charging Pool Reservation support
                 Key: OCPP-120
                 URL: https://issues.oasis-open.org/browse/OCPP-120
             Project: OASIS OCPP Electric Vehicle Charging Equipment Data Exchange TC
          Issue Type: Improvement
            Reporter: Franc Buve
            Priority: Minor

If a charge point has 2 or more EVSEs then it should be able to accept 2 or more reservations on connector #0 of the charge point, because that still meets the requirement "If the connectorId in the reservation request is 0, then the Charge Point SHALL NOT reserve a specific connector, but SHALL make sure that at any time during the validity of the reservation, one connector remains available for the reserved idTag.”
However, it may clash with the following requirement: “The Charge Point SHALL also return ‘Occupied’ when the Charge Point or connector has been reserved for the same or another idTag.” 
I advise to modify this requirement so as to make multiple charge point reservations (‘connector #0’) possible.
(Please note, that the concept of 'connector' in OCPP 1.6 will be replaced by 'evse' in the new spec.)

This message was sent by Atlassian JIRA

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]