We are using two ABL 1W2201 wall boxes, also known as type 1W or eMH1. I could only find a component EVCS OCPP ABL, but according to ABL the ABL 1W2201 does not support OCPP. Thus I’d like to ask if anyone is using the ABL 1W2201 with OpenEMS?
I am not aware of anyone using this setup or currently implementing it.
With new EVSE infrastructure it should become much easier to implement new wallboxes. Can you provide a link to the protocol definition?
Thanks,
Stefan
Sorry for the late reply, @stefan.feilmeier! I did find following document(s):
Also, but probably not so relevant:
Is this already available, or do you have a time horizon?
From FENECON-side we do not enforce implementation of RS485-connected Wallboxes, because in most cases they are not compatible with our systems.
We are currently working on a read-only implementation of “ABL eM4”. But I don’t think that is compatible with eMH1.
Yes, it’s already there and working nicely. I use it personally since a few months. But it does not yet have all the features of the old EVCS implementations. Details → openems/io.openems.edge.evse.api at develop · OpenEMS/openems · GitHub
1 Like
Our idea is to use a Modbus RTU to Modbus TCP transducer, to make the inverter available to OpenEMS via Modbus TCP.
Probably not.
@sjjh Be aware that the ABL eMH1 is communicating via Modbus/ASCII, not Modbus/RTU.
Its implementation of Modbus/ASCII even deviates from standard as implemented in j2mod (as used by openems for serial modbus communication (established: Modbus/RTU).
The PR io.openems.edge.bridge.modbus.ascii - adding support for Modbus/ASCII over serial by janklostermann · Pull Request #3632 · OpenEMS/openems · GitHub provides openems with the capability to communicate via Modbus/ASCII and contains that ABL-specific quirk as a config parameter.
I have implemented an io.openems.edge.evse.chargepoint.abl for the eMH1, which uses this PR, but no PR for that yet.