"Interlocked" state required for Connectors

XMLWordPrintable

    • Type: Task
    • Resolution: Unresolved
    • Priority: Minor
    • None
    • Affects Version/s: None
    • Component/s: spec
    • None
    • Hide

      "Connector" level "State" enumeration should contain a new value ( called “Interlocked”, or similar), to explicitly signal that a Connector is currently unusable, (only) because one of the other Connectors on the same EVSE is “in use” (Preparing, … Charging … Finishing, and also Reserved).

      Show
      "Connector" level "State" enumeration should contain a new value ( called “Interlocked”, or similar), to explicitly signal that a Connector is currently unusable, (only) because one of the other Connectors on the same EVSE is “in use” (Preparing, … Charging … Finishing, and also Reserved).

      There needs to be an unambiguous way for charge points to inform the Central System that a logical Connector, under a logical EVSE, is un-usable when a different Connector under the same EVSE is in use.

      The need for such functionality is so pressing that many charge point vendors have (knowingly?) incorrectly “hijacked” the ChargePointStatus value of “Unavailable” (in OCPP 1.2/1.5/1.6) to signal this state, even though that is clearly contrary to the single intended purpose of that value, according to the specification text.

            Assignee:
            Unassigned
            Reporter:
            brendan.mcmahon
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated: