-
Notifications
You must be signed in to change notification settings - Fork 2
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 SOM: Add logging and debugging section #37
Charge SOM: Add logging and debugging section #37
Conversation
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Signed-off-by: Moritz Barsnick <[email protected]>
Signed-off-by: Moritz Barsnick <[email protected]>
Signed-off-by: Fabian Hartung <[email protected]>
Should be merged after #32 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since the content (at least of this last commit versus the referenced branch) is identical to what is already upstream for CCC), this looks good.
docs/source/troubleshooting.rst
Outdated
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
No, the Control Pilot interface on ChargeSOM is not able to operate as an EV. Please look at | ||
our `website <https://www.chargebyte.com/>`_ for more suitable products. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Technically this is not 100% correct. I would say that the hardware of the ChargeSOM is not designed for the EV use case.
docs/source/troubleshooting.rst
Outdated
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The ChargeSOM doesn't have an `EVerest admin panel <https://github.com/EVerest/everest-admin-panel>`_ | ||
because of its limited resources. Please use your development environment to set up your configuration |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is a bad argument, because the ChargeSOM has enough resources.
docs/source/troubleshooting.rst
Outdated
Does EVerest on ChargeSOM support ISO 15118-20 yet? | ||
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ | ||
|
||
The required module for ISO 15118-20 has been included in the image since the chargebyte EVerest 0.2.0 release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest to call it Charge SOM EVerest release to be more clear.
Github Actions complains about undefined labels, could you please check that? undefined label: 'firmware_customization' |
… issues Signed-off-by: Fabian Hartung <[email protected]>
This message is expected, because the firmware section is not yet integrated. I would merge it as soon as the firmware section it integrated. |
No description provided.