# EV charger OCPP1.6 protocol choice of integration with ignition **URL:** \ **Category:** Ignition\ **Created:** [November 28, 2022, 1:11pm UTC](https://forum.inductiveautomation.com/t/ev-charger-ocpp1-6-protocol-choice-of-integration-with-ignition/66970 "2022-11-28T13:11:21Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![Emile\_Laplante](https://avatars.discourse-cdn.com/v4/letter/e/c57346/32.png) [@Emile\_Laplante](https://forum.inductiveautomation.com/u/Emile_Laplante)\ **Post date:** [November 28, 2022, 1:11pm UTC](https://forum.inductiveautomation.com/t/ev-charger-ocpp1-6-protocol-choice-of-integration-with-ignition/66970/1 "2022-11-28T13:11:21Z")
Hi! I'm trying to implement a HMI for an EV charger. The protocol of communication used by the charger is OCPP1.6 : > **[ocpp-1.6.pdf](https://www.oasis-open.org/committees/download.php/58944/ocpp-1.6.pdf)** > > 13.34 MB The OCPP1.6 protocol of the charger is based on JSON over WebSocket. Currently I'm able to communicate between ignition and the charger with a hardware gateway modbus to OCPP1.6: [https://www.intesis.com/fr/produits/protocol-translators/modbus-gateways/ocpp-to-modbus-tcp-rtu-gateway](https://www.intesis.com/fr/produits/protocol-translators/modbus-gateways/ocpp-to-modbus-tcp-rtu-gateway) But I found some python drivers parsing OCPP1.6 transactions that makes me wonder the necessity of the hardware gateway to communicate with ignition: [https://ocpp.readthedocs.io/en/latest/central\_system.html](https://ocpp.readthedocs.io/en/latest/central_system.html) So, do you have any suggestions on how I could communicate with an EV charger directly with ignition over websockets without the need of the physical gateway modbus? A solution that I see is to create a python software modbus OCPP1.6 gateway running outside of the ignition project, but is there any more straight forward solution? Thank you! ---
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [November 28, 2022, 1:14pm UTC](https://forum.inductiveautomation.com/t/ev-charger-ocpp1-6-protocol-choice-of-integration-with-ignition/66970/2 "2022-11-28T13:14:00Z")
Sounds like an opportunity to make a new driver module with the SDK. (: Might be doable in jython with jetty's websocket support. ---
**Author:** ![Pascal\_Dubois](https://avatars.discourse-cdn.com/v4/letter/p/4da419/32.png) [@Pascal\_Dubois](https://forum.inductiveautomation.com/u/Pascal_Dubois)\ **Post date:** [May 8, 2023, 8:25pm UTC](https://forum.inductiveautomation.com/t/ev-charger-ocpp1-6-protocol-choice-of-integration-with-ignition/66970/3 "2023-05-08T20:25:08Z")
Hello Emile, I would realy be interested to communication with you and know how does the Intesis work. I could also show you what I have done with Ignition. (CSMS solution) ---
**Author:** ![pridesleap](https://avatars.discourse-cdn.com/v4/letter/p/f4b2a3/32.png) [@pridesleap](https://forum.inductiveautomation.com/u/pridesleap)\ **Post date:** [September 4, 2023, 6:20pm UTC](https://forum.inductiveautomation.com/t/ev-charger-ocpp1-6-protocol-choice-of-integration-with-ignition/66970/4 "2023-09-04T18:20:25Z")
I'm going to reactivate this thread because I have found myself int he same situation. Has anyone else been able to get Ignition to connect to OCPP v1.6 or 2.0 chargers? ---
**Author:** ![Pascal\_Dubois](https://avatars.discourse-cdn.com/v4/letter/p/4da419/32.png) [@Pascal\_Dubois](https://forum.inductiveautomation.com/u/Pascal_Dubois)\ **Post date:** [October 18, 2023, 6:22pm UTC](https://forum.inductiveautomation.com/t/ev-charger-ocpp1-6-protocol-choice-of-integration-with-ignition/66970/5 "2023-10-18T18:22:27Z")
for your information there is a new OCPP driver for Ignition made by Baudrate IO [Open Charge Point Protocol for Ignition SCADA (baudrate.io)](https://baudrate.io/open-charge-point-protocol-ocpp-ignition)