Schneider Charge Pro EVB4S22N40MG support

[Patoullins]

Description

Schneider Charge Pro EVB4S22N40MG support

Model: EVB4S22N40MG
Firmware: 3.6.2
Modbus TCP: enabled
Host: 192.168.0.27
Port: 502
Server ID: 255

The existing schneider-evlink-v3 template fails with:

current limit: modbus: exception '2' (illegal data address), function '3'

According to Schneider Charge Pro Modbus Connectivity Guide
NAT3046700-03, Charge Pro uses function 0x04 for register reads
and function 0x10 for setpoint writes.

The existing EVlink Pro driver uses ReadHoldingRegisters (FC03)
and WriteSingleRegister (FC06), so a dedicated Charge Pro driver
appears necessary.

Steps to Reproduce

cannot create charger type 'template:schneider-evlink-v3': cannot create charger type 'schneider-v3': current limit: modbus: exception '2' (illegal data address), function '3'

Version

v0.315.2

System

linux/amd64, CEST +02:00

[mfuchs1984]

If your provide the modbus specs, there is a chance to implement an interface for the charger.

[mfuchs1984]

Do you think thats the best approach? I think it’s better to have a new driver.

Since the registers are the same, maybe one is enough. But both is possible. Feel free to create a pull request.

[estimadarocha]

Ocpp for setpoint isnt slow?

[mfuchs1984]

Nope, no difference.

[Patoullins]

Thanks for the clarification.

Using OCPP only is not really an option in my case, because the charger must remain connected to the Monta backend for authentication and company charging reimbursement.

My goal is therefore to keep Monta connected through OCPP while evcc controls the charging current locally through Modbus TCP.

If extending the existing Schneider driver to use FC04/FC16 is the simplest solution, that would be perfectly fine for me; I do not specifically need a separate driver.

I’m not a Go developer, so I probably can’t create the pull request myself, but I can test development builds on my Charge Pro with firmware 3.6.2 and provide Modbus traces or any other diagnostic information required.

Would simultaneous OCPP operation with Monta and local Modbus control by evcc be acceptable from evcc’s point of view?

[estimadarocha]

That’s algo my use case… ocpp for company cms and modbus to set charge strategy.

I have also one of this Chargers on the last version of fw and will have this week the addon for
15118.

I think there’s more changes than a simple change from FC06 to FC16

[estimadarocha]

@mfuchs1984 #34165