Troubleshooting

Frequently Asked Questions

Does the Charge SOM have a CE certification?

Currently, the Charge SOM doesn’t have any certification yet.

Does the Charge SOM have Wifi support?

The Charge SOM doesn’t have builtin Wifi support, but it provides suitable interfaces (SDIO / USB 2.0 ) via its connectors. For instance the Charge SOM Single Channel DC Carrier Board provides a mini PCIe connector, which is connected to USB.

Is it possible to use the Charge SOM as an EV simulator?

The Charge SOM hardware is not designed to be used as an EV simulator. Please refer to our website for more suitable products.

I want to control EVerest via CAN, how can I achieve this?

Currently, there is no such EVerest module available, you will need to implement it on your own. But at least there is a module and a library, which uses the CAN interface.

How can I access the EVerest admin panel on Charge SOM?

Currently, the Charge SOM does not have integrated the EVerest admin panel Please use your development environment to set up your configuration file. Alternatively, you can use a plain text editor.

Does EVerest on Charge SOM support ISO 15118-20 yet?

The required module for ISO 15118-20 has been included in the image since the Charge SOM EVerest release 0.2.0. Please note that the implementation is still under development.

How do I set up OCPP 2.0.1 on Charge SOM with EVerest?

To support OCPP 2.0.1, the EVerest OCPP201 module must be integrated into the EVerest configuration. This module uses the libocpp library to implement the OCPP 2.0.1 protocol. The OCPP201 module documentation already contains some information about the module parameters, the provided and required interfaces, and the initial creation of the OCPP 2.0.1 database.

The most important points are summarised here:

  1. The OCPP201 module must be included in your EVerest configuration.

  2. The CbSystem module can be used to fulfill the requirement of the system interface.

  3. While configuring the OCPP 2.0.1 module, ensure that you are using OCPP configuration and database paths which are covered by the update mechanism. The following paths are recommended:

    • CoreDatabasePath: /var/lib/everest/ocpp201

    • DeviceModelDatabasePath: /var/lib/everest/ocpp201/device_model_storage.db

    • DeviceModelConfigPath: /var/lib/everest/ocpp201/component_config

    Otherwise, if you don’t want to use a persistent storage, you can also deploy those files in your RAUC image.

  4. The CoreDatabasePath is used, among other things, to store OCPP transaction data.

  5. The OCPP 2.0.1 device model initialization is done automatically by the OCPP201 module after the first start of EVerest. The database is stored the DeviceModelDatabasePath.

  6. The component config files are stored in the DeviceModelConfigPath. Component config files are used to initialize or update the device model database. To update a component config file, just the place a component config file in the same directory structure in the DeviceModelConfigPath and change the values accordingly. Important keys of the component config files are:

    • standardized/InternalCtrlr.json: ChargePointId: In “attributes” adapt the “value” key to configure the ChargePointId. Used to identify the Charging Station.

    • standardized/InternalCtrlr.json: NetworkConnectionProfiles: In “attributes” adapt the “ocppCsmsUrl” key. The URL in “ocppCsmsUrl” is used to connect to the CSMS.

    • standardized/SecurityCtrlr.json: SecurityCtrlrIdentity: In “attributes” adapt the “value” key to configure the SecurityCtrlrIdentity. It is the Charging Station identity.

    For further information about the device model initialization, please refer to the libocpp documentation.

I tried to compile chargebyte’s Hardware EVerest Modules, but it fails to build. How can it fix this?

The EVerest mainline development is very dynamic and doesn’t guarantee any stable API along the EVerest modules. So after almost every EVerest release, chargebyte needs to adapt their modules to the latest API changes.

Please have a look at the compatibility matrix to see which EVerest release works with which chargebyte EVerest Modules release.

I would like to implement a custom Modbus device in EVerest. Where should I start?

EVerest already has a module which takes care of Modbus communication. Please have a look at SerialCommHub, and let your module interact with this module via the serial_communication_hub interface.

Contact

Support

EVerest is an open-source project with a lot of modules, which is supported by a big community. chargebyte is an active part of this community. However chargebyte is not able to provide support for every aspect of EVerest. In order to get quick answers, here are some suggestions:

Do you have general questions about EVerest, please use the EVerest community’s Zulip.

Do you have questions about the chargebyte BSP (incl. Yocto), please use our support desk.

Note

Before submitting a support request, make sure that all relevant log files have been captured. The chapter Logging and Debugging describes the debugging options EVerest offers and shows which logs are relevant for the respective case.

Address

chargebyte GmbH

Bitterfelder Straße 1-5

04129 Leipzig

Germany

Website: https://chargebyte.com