Skip to content

Conversation

@FaHaGit
Copy link
Contributor

@FaHaGit FaHaGit commented Mar 5, 2025

This is the preparation to integrate the chapters in Charge SOM user guide.

@FaHaGit FaHaGit requested review from barsnick and lategoodbye March 5, 2025 09:55
`Zulip <https://lfenergy.zulipchat.com/>`_.

Do you have questions about the chargebyte BSP (incl. Yocto), please use
`our support desk <https://chargebyte.com/support>`_.
Copy link
Member

Choose a reason for hiding this comment

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

Maybe we should guide them directly to:
https://chargebyte.atlassian.net/servicedesk/customer/portal/13

The custom image should now include the new EVerest module.
.. include:: ../../includes/development.inc

.. _cross_compiling_for_tarragon:
Copy link
Member

Choose a reason for hiding this comment

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

Please make this section more generic e.g. Cross compiling, so we can reference it from generic pages

lategoodbye

This comment was marked as resolved.

@lategoodbye
Copy link
Member

lategoodbye commented Mar 5, 2025

Just a note, in case you make text changes. Please make it a separate commit, otherwise it's impossible to review after moving the complete content to includes.

@FaHaGit FaHaGit force-pushed the everest/ccc_introduce_generic_chapters branch 2 times, most recently from 582f52a to 3a3dfed Compare March 6, 2025 10:47

**DummyTokenProvider** (`view on GitHub <https://github.com/EVerest/everest-core/tree/main/modules/DummyTokenValidator>`__)

This module listens to AuthRequired event from evse_manager module and then publishes one token.
Copy link
Contributor

Choose a reason for hiding this comment

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

This module is used for automatically providing an authorization token, instead of requiring e.g. an actual RFID reader.

It listens to the AuthRequired...

Copy link
Contributor

Choose a reason for hiding this comment

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

I would still like the "the". ;-)

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Done

.. figure:: ../../includes/_static/images/cbenergy/discover.png
:height: 600px

If the discovery has not found any wallbox in the local network you can try to setup an manual connection as described in :ref:`connection_option`.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
If the discovery has not found any wallbox in the local network you can try to setup an manual connection as described in :ref:`connection_option`.
If the discovery has not found any wallbox in the local network you can try to setup n manual connection as described in :ref:`connection_option`.

.. figure:: ../../includes/_static/images/cbenergy/user.png
:height: 600px

It is time to create login credentials to keep the CB energy setup protected. When connecting to the system for the first time, it will prompt for a username and a password. Optionally, you can also provide your name and E-Mail address.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
It is time to create login credentials to keep the CB energy setup protected. When connecting to the system for the first time, it will prompt for a username and a password. Optionally, you can also provide your name and E-Mail address.
It is time to create login credentials to keep the CB energy setup protected. When connecting to the system for the first time, it will prompt for a username and a password. Optionally, you can also provide your name and e-mail address.

Setup of ecosystem
=========================

In the next step, nymea:core starts a discovery for EV Chargers. This might be the same machine (localhost) or any other supported Charger in the local network.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
In the next step, nymea:core starts a discovery for EV Chargers. This might be the same machine (localhost) or any other supported Charger in the local network.
In the next step, nymea:core starts a discovery for EV chargers. This might be the same machine (localhost) or any other supported charger in the local network.

If you are trying CB energy on a chargebyte controller an EVerest connector will be discovered.


After discovering and setting up the wallbox, CB Energy tries to discover other assets like solar inverters and meters. If there aren't any of these devices around, you can skip this step.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
After discovering and setting up the wallbox, CB Energy tries to discover other assets like solar inverters and meters. If there aren't any of these devices around, you can skip this step.
After discovering and setting up the wallbox, CB Energy tries to discover other assets like solar inverters and meters. If there aren't any of these devices around, you can skip this step.

Manual connection option
========================

If Discovery between CB energy app (client) and nymea:core (server) fails for some reason (e.g. blocked UPnP/ZeroConf in company network), you can still enter the endpoints manually.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
If Discovery between CB energy app (client) and nymea:core (server) fails for some reason (e.g. blocked UPnP/ZeroConf in company network), you can still enter the endpoints manually.
If discovery between CB energy app (client) and nymea:core (server) fails for some reason (e.g. blocked UPnP/ZeroConf in company network), you can still enter the endpoints manually.

@FaHaGit FaHaGit force-pushed the everest/ccc_introduce_generic_chapters branch from a89239b to 07bd9ef Compare March 6, 2025 12:21
FaHaGit added 12 commits March 6, 2025 13:49
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
Signed-off-by: Fabian Hartung <fabian.hartung@chargebyte.com>
@FaHaGit FaHaGit force-pushed the everest/ccc_introduce_generic_chapters branch from 07bd9ef to 99ac1ab Compare March 6, 2025 12:49
@FaHaGit FaHaGit merged commit a85afd2 into everest/charge_control_c Mar 6, 2025
1 check passed
@FaHaGit FaHaGit deleted the everest/ccc_introduce_generic_chapters branch March 6, 2025 12:51
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