Everest/charge som adaptations for 2025.8.0

docs/source/_static/files/bsp-only-dc.yaml

@@ -11,10 +11,43 @@ active_modules:
       error_history:
         - module_id: error_history
           implementation_id: error_history
+      evse_energy_sink:
+        - module_id: grid_connection_point
+          implementation_id: external_limits
+  rpc_api:
+    module: RpcApi
+    connections:
+      evse_manager:
+        - module_id: connector
+          implementation_id: evse
+      energy_listener:
+        - module_id: connector
+          implementation_id: energy_grid
+      evse_energy_sink:
+        - module_id: grid_connection_point
+          implementation_id: external_limits
+      charger_information:
+        - module_id: charger_info
+          implementation_id: main
+  charger_info:
+    module: ChargerInfo
+    config_module:
+      firmware_version_file: /usr/share/secc/VERSION
+    connections:
+      kvs:
+        - module_id: kvs
+          implementation_id: main
+  kvs:
+    module: YamlStore
+    config_module:
+      file: /etc/everest/charger_info.yaml
   bsp:
     module: CbChargeSOMDriver
   connector:
     module: EvseManager
+    mapping:
+      module:
+        evse: 1
     config_module:
       connector_id: 1
       charge_mode: DC
@@ -33,6 +66,9 @@ active_modules:
       powersupply_DC:
         - module_id: powersupply_dc
           implementation_id: main
+      powermeter_car_side:
+        - module_id: powersupply_dc
+          implementation_id: powermeter
       imd:
         - module_id: imd
           implementation_id: main
@@ -47,6 +83,9 @@ active_modules:
           implementation_id: energy_grid
   grid_connection_point:
     module: EnergyNode
+    mapping:
+      module:
+        evse: 1
     config_module:
       fuse_limit_A: 16
       phase_count: 3
@@ -92,6 +131,13 @@ active_modules:
       evse_manager:
         - module_id: connector
           implementation_id: evse
+      kvs:
+        - module_id: persistent_store
+          implementation_id: main
+  persistent_store:
+    module: PersistentStore
+    config_module:
+      sqlite_db_file_path: /var/lib/everest/everest_persistent_store.db
   powersupply_dc:
     module: DCSupplySimulator
   imd:

docs/source/everest_charging_stack.rst

@@ -19,6 +19,7 @@ The use case described in this configuration file includes the following:
 * 3 phase, 16A fuse limit
 * Simulation of the IMD (Insulation Monitoring Device)
 * Simulation of the DC Supply Device
+* Energy management via JSON-RPC API
 
 An overview of the EVerest modules is shown in the next section.
 

docs/source/getting_started.rst

@@ -108,6 +108,7 @@ content of the configuration file, you will see that it is only a reference to t
 .. note::
    If you create an own configuration file, you can also store it in the "/etc/everest" directory
    and create a symbolic link to it like "ln -sf /etc/everest/my-config.yaml /etc/everest/config.yaml".
+   The file where the "config.yaml" symbolic link points to is preserved during the update process.
 
 .. code-block:: bash
 

docs/source/troubleshooting.rst

@@ -92,7 +92,13 @@ 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.
+Please note that the implementation is still under development and integrated into the image only for test purposes.
+
+EVerest integrates the `libiso15118 <https://github.com/EVerest/libiso15118>`_ library to provide support for ISO 15118-20.
+Here you can find more information about the current status of the ISO 15118-20 implementation.
+Please note, however, that the range of functions described in the linked `libiso15118` library documentation may not
+correspond to those already integrated in EVerest, as the library has not yet been fully integrated.
+Implementation gaps may exist, particularly in the case of BPT (bidirectional power transfer) functionality.
 
 
 How do I set up OCPP 2.0.1 on Charge SOM with EVerest?
@@ -135,8 +141,8 @@ The most important points are summarised here:
    `libocpp documentation <https://github.com/EVerest/libocpp/blob/main/doc/v2/ocpp_201_device_model_initialization.md>`_.
 
 
-I tried to compile chargebyte's Hardware EVerest Modules, but it fails to build. How can it fix this?
-^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
+I tried to compile chargebyte's Hardware EVerest Modules, but it fails to build. How can I 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,