openevse_esp32_firmware
openevse_esp32_firmware copied to clipboard
OpenEVSE
OCPP - unlock connector via command
In case the locking actuator of the plug fails, the CPO should be able to use the OCPP command UnlockConnector to trigger the EVSE to retry unlocking the connector. It is okay for the moment to reply with a NotImplemented message if the EVSE doesn't support it, but it would be really helpful to allow a more extensive remote management via OCPP.
This would need some support from the OpenEVSE firmware, we started a discussion in https://github.com/lincomatic/open_evse/issues/141 but there was no conclusion. @chris1howell / @glynhudson any thoughts?
Apologies, I dropped the ball on getting the MennekesLock implemented. I've just replied to https://github.com/lincomatic/open_evse/issues/141 . The lock should be automatic but there should be a manual overide via RAPI which can be called via OCPP.
Hmm.. seems we need a RAPI lock/unlock command for Mennekes? If we do that, then I agree, we should just leave it to WiFi to control it. But if we're doing that, it really seems more logical to just take the EVSE out of the equation completely and connect the lock motor to the WiFi. For non-Mennekes scenarios, the AUTH_LOCK code alone can handle the access control of charging
Hello, Can someone suggest how unlock feature could realised on a charger, i.e. upon reception of "unlock connector" command over OCPP (from back-end), the charger should send some "unlock" command to connector over CAN bus ... something like this ?
@pavel167
In Europe, it is common to bring your own cable, the cable has a connector on both ends. The station locks the connector to the station when the charge starts. Once the vehicle end is unlocked and unplugged the station unlocks the station side connector.
OCPP connector unlock allows a command to unlock the station side connector.
On Wed, Nov 3, 2021 at 10:44 AM pavel167 @.***> wrote:
Hello, Can someone suggest how unlock feature could realised on a charger, i.e. upon reception of "unlock connector" command over OCPP (from back-end), the charger should send some "unlock" command to connector over CAN bus ... something like this ?
— You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub https://github.com/OpenEVSE/ESP32_WiFi_V4.x/issues/230#issuecomment-959294762, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAN5QH647ORYN5CY3LVCPJTUKFDC3ANCNFSM5BO7YUGQ . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
@matth-x this is now implemented in the OpenEVSE firmware, #289 covers adding the generic handling in the WiFi firmware