Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

mA current steps for EVSE DIN #2054

Closed
premultiply opened this issue Dec 16, 2021 Discussed in #2053 · 11 comments
Closed

mA current steps for EVSE DIN #2054

premultiply opened this issue Dec 16, 2021 Discussed in #2053 · 11 comments
Labels
devices Specific device support enhancement New feature or request

Comments

@premultiply
Copy link
Member

Discussed in #2053

Originally posted by RTTTC December 16, 2021
So I have asked EvRacing.cz if smaller than 1A steps are planned for the future, and got this response:

Yes you can actually change this step to 0.01A. You will need to enable bit 7 from register 2005. Then you will be able to change current in register 1000 in smaller steps (16A -->1600)

So great news for those that have firmware revision 17 and later! http://evracing.cz/evse/evse-wallbox/evse-wb-din_latest.pdf
I have changed bit7 using "Modbus pool" and charge controller can now be controlled in small steps using direct modbus commands :)
Will EVCC be able to detect and handle this change automatically? (don't have a car to test..)

@premultiply premultiply added devices Specific device support enhancement New feature or request labels Dec 16, 2021
@schenlap
Copy link
Contributor

For evse wifi (smartwb), which uses evse din internally, high resolution mode is already in evcc.
The question is for https://docs.evcc.io/docs/devices/chargers#simple-evse ?

@andig
Copy link
Member

andig commented Jan 17, 2022

Ja, so was das gemeint. Fraglich ob sicher der Aufwand für die wenigen Bastler lohnt. Ich würde lieber zu machen.

@premultiply
Copy link
Member Author

Neben der Premium-Variante mit Fallunterscheidung nach Firmware-Version usw. könnte man die einfache Version machen und die mA-Regelung einfach fest umsetzen.

Nach dem Motto: Wer die EVSE-DIN hat wird wohl auch in der Lage sein die Firmware zu aktualisieren und die entsprechenden Registereinstellungen vorzunehmen.

Das wäre mit minimalem Aufwand umzusetzen.

@andig
Copy link
Member

andig commented Jan 17, 2022

Stimmt. Aber damit machen wir es für alle die das nicht können kaputt. Wenn niemand Kapa dafür hat würde ich hier zu machen, es läuft ja nicht weg…

@RTTTC
Copy link
Contributor

RTTTC commented Jan 17, 2022

For evse wifi (smartwb), which uses evse din internally, high resolution mode is already in evcc.
The question is for https://docs.evcc.io/docs/devices/chargers#simple-evse ?

BTW controller in this link is named incorrectly, (Simple EVSE has no RS485)
Appropriate name is EVSE DIN
http://evracing.cz/simple-evse-wallbox

@premultiply
Copy link
Member Author

@RTTTC Looks like you are one of the very few users using this controller under direct control of evcc.
Wouldn't you like to try an appropriate PR for this controller to close this issue?

@andig
Copy link
Member

andig commented Jan 17, 2022

Closing until someone feels like picking this up.

@andig andig closed this as completed Jan 17, 2022
@RTTTC
Copy link
Contributor

RTTTC commented Jan 18, 2022

@RTTTC Looks like you are one of the very few users using this controller under direct control of evcc.
Wouldn't you like to try an appropriate PR for this controller to close this issue?

I don't have the necessary skills.

@RTTTC
Copy link
Contributor

RTTTC commented Jan 18, 2022

Stimmt. Aber damit machen wir es für alle die das nicht können kaputt. Wenn niemand Kapa dafür hat würde ich hier zu machen, es läuft ja nicht weg…

What if there are simply two templates : EVSE DIN and EVSE DIN mA ?

@andig
Copy link
Member

andig commented Jan 18, 2022

We‘re not going to change it right now.

@RTTTC
Copy link
Contributor

RTTTC commented May 1, 2022

@RTTTC Looks like you are one of the very few users using this controller under direct control of evcc.
Wouldn't you like to try an appropriate PR for this controller to close this issue?

Am I the only one ? :DD

Could someone point me in the right direction - where would I look into, what files need to be changed / added to create PR for this?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
devices Specific device support enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants