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

Charge Control C: move list of supported peripherals into own list #45

Merged
merged 3 commits into from
Apr 2, 2025

Conversation

mhei
Copy link
Member

@mhei mhei commented Mar 28, 2025

Note: this PR can only be merged as-is if #44 is merged via fast-forward.

@mhei mhei requested review from simonseres, barsnick and FaHaGit March 28, 2025 08:53
@mhei mhei changed the title Move list of supported peripherals into own list Charge Control C: move list of supported peripherals into own list Mar 28, 2025
Copy link
Contributor

@barsnick barsnick left a comment

Choose a reason for hiding this comment

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

Basically just one minor format nit, and a note.

.. note::
The Charge Control C boards use a Qualcomm Atheros QCA700x chip for Green PHY communication on CP line.
The shipped QCA700x firmware configuration contains a default set of prescalers which influence the
CP signal level (,,loudness”).
Copy link
Contributor

Choose a reason for hiding this comment

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

The ,, quotation marks still render as two commas. I'm not sure that's intended.

Since Charge Control C can be freely programmed, it is possible that customers add additional device
support on their own, either by writing a customer EVerest module or adapting a model for GenericPowermeter.

The following table documents the default communication parameters for supported Modbus peripherals.
Copy link
Contributor

Choose a reason for hiding this comment

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

With this PR, we now no longer document the defaults. This is probably okay, so just a note that this is a change.

Copy link
Member Author

Choose a reason for hiding this comment

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

The default stuff was copied over from Truffle but it does not fit EVerest at all. In Truffle we depending on the meter type different presets, but in EVerest you have to configure it directly.

@mhei mhei force-pushed the feature/ccc_hcl branch from 2373ac9 to 78f4941 Compare March 28, 2025 10:15
mhei added 2 commits March 31, 2025 12:43
Get rid of the nasty "documentation" suffix in rendered HTML titles.

Signed-off-by: Michael Heimpold <[email protected]>
@mhei mhei force-pushed the feature/ccc_hcl branch from 78f4941 to e7a2fd9 Compare March 31, 2025 11:38
Signed-off-by: Michael Heimpold <[email protected]>
@mhei mhei merged commit fef881a into everest/charge_control_c Apr 2, 2025
1 check failed
@mhei mhei deleted the feature/ccc_hcl branch April 2, 2025 06:49
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.

4 participants