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

Bugfix: Make Solax no longer get stuck with open contactors at 0%SOC #226

Merged
merged 2 commits into from Mar 18, 2024

Conversation

dalathegreat
Copy link
Owner

@dalathegreat dalathegreat commented Mar 17, 2024

What

This PR makes Solax inverters more robust on double LilyGo setups

Why

Solax inverters opens the contactors if the battery is at the minimum charge level but there is no PV power available or grid power allowed to charge it. This is a problem, since we have been treating it as an ERROR, requiring reboot to get out of this state.

How

  • Inverter contactor opening changed from Error -> Info event
  • CAN interface is now restarted incase Solax has timed out

Copy link
Collaborator

@rjsc rjsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This only works with dual lilygo setups (inverter connected to the ESP32 CAN)
For Dual CAN (MCP2515) setups its not needed and it simply resets the battery communications.
Please add ans #ifndef DUAL_CAN to this block.

@rjsc rjsc merged commit 45fc637 into main Mar 18, 2024
42 checks passed
@dalathegreat
Copy link
Owner Author

@rjsc did you test this change already, or just merge it? 😅

@rjsc
Copy link
Collaborator

rjsc commented Mar 18, 2024

Just reviewed the code and merged it.
My inverter is a FoxESS H1, also uses the Solax protocol but behaves a little differently.

@dalathegreat dalathegreat deleted the bugfix/solax-contactor-can branch March 27, 2024 15:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants