diff --git a/docs/latest/_generated/modules/EvseSlac.html b/docs/latest/_generated/modules/EvseSlac.html index 15e7fc3f4..deb8f1053 100644 --- a/docs/latest/_generated/modules/EvseSlac.html +++ b/docs/latest/_generated/modules/EvseSlac.html @@ -47,6 +47,7 @@

Navigation

Implementation of SLAC data link negotiation according to ISO15118-3.
+

For a detailed handwritten documentation see here

11.1.13.1. Provides

diff --git a/docs/latest/_included/modules_doc/EvseManager.html b/docs/latest/_included/modules_doc/EvseManager.html index f373f4005..1a3781a1d 100644 --- a/docs/latest/_included/modules_doc/EvseManager.html +++ b/docs/latest/_included/modules_doc/EvseManager.html @@ -15,7 +15,7 @@ - +

Next topic

-

5.2.2. GenericPowermeter

+

5.2.2. EvseSlac

This Page

@@ -263,7 +263,7 @@

Navigation

index
  • - next |
  • + + + + + + + 5.2.2. EvseSlac — EVerest documentation + + + + + + + + + + + + + + +
    +
    +
    +
    + +
    +

    5.2.2. EvseSlac

    +

    This is an implementation of the ISO 15118-3 EVSE side SLAC protocol. +The general flow of operation will be like this:

    +
      +

    • start of operation begins with a control pilot transition from state +A, E or F to Bx, Cx or Dx. This is indicated by the EvseManager by calling +the commands enter_bcd/leave_bcd.

      • +

    • Once started, it waits for a CM_SLAC_PARM_REQ from the EV side to start the SLAC session.

      • +

    • In case of success, SLAC finishes with a CM_SLAC_MATCH_RES, which sends a new NMK to the EV side. +The EV then joins the logical network and the two modems are paired. A dlink_ready(true) is published +to signal to the EvseManager that the low level PLC link is ready for communication.

      • +
    +

    If not run as root user, this modules requires the capability CAP_NET_RAW.

    +
    +
    +

    5.2.3. Todo

    +
      +

    • make use of the enable flag in the reset command or drop it, if not needed

      • +

    • handle CM_VALIDATE.REQ message

      • +

    • implement PLC chip resetting after unplug or failed SLAC sessions (especially for QCA chips)

      • +
    +
    + + +
    +
    +
    +
    + +
    +
    + + + + \ No newline at end of file diff --git a/docs/latest/_included/modules_doc/GenericPowermeter.html b/docs/latest/_included/modules_doc/GenericPowermeter.html index 5b3525f68..f357cbabf 100644 --- a/docs/latest/_included/modules_doc/GenericPowermeter.html +++ b/docs/latest/_included/modules_doc/GenericPowermeter.html @@ -5,7 +5,7 @@ - 5.2.2. GenericPowermeter — EVerest documentation + 5.2.4. GenericPowermeter — EVerest documentation @@ -15,8 +15,8 @@ - - + +
  • - next |
  • - previous |
  • EVerest documentation »
  • 5. EVerest Module Configurations »
    • -
  • 5.2.2. GenericPowermeter
    • +
  • 5.2.4. GenericPowermeter
    • @@ -42,7 +42,7 @@

    Navigation

    -

    5.2.2. GenericPowermeter

    +

    5.2.4. GenericPowermeter

    See also module’s auto-generated reference.

    The module GenericPowermeter provides a connection to get data from powermeters that are connected via Modbus RTU and whose data is automatically @@ -57,9 +57,9 @@

    Navigation

    file in the models subdirectory which can be copied and filled with the new powermeter’s data from the datasheet.

    -

    5.2.2.1. Datasets in the configuration file

    +

    5.2.4.1. Datasets in the configuration file

    -

    5.2.2.1.1. Available datasets for the module GenericPowermeter

    +

    5.2.4.1.1. Available datasets for the module GenericPowermeter

    This module can read the following parameters from a powermeter:

    (for a description of the parameter values see interface powermeter)

      @@ -73,7 +73,7 @@

      5.2.2.1.1. Available datasets for the mo

    -

    5.2.2.1.2. Dataset description

    +

    5.2.4.1.2. Dataset description

    A typical dataset consists of the following parameters:

    (<start_register> of length <num_registers>) * <multiplier> * 10^(<exponent_register>)

      @@ -92,7 +92,7 @@

      5.2.2.1.2. Dataset description -

      5.2.2.1.3. Structure of datasets in the configuration file

      +

      5.2.4.1.3. Structure of datasets in the configuration file

      Datasets are structured into two levels:

      • first level : contains either DC value or, in AC case, sum total of all corresponding lines (L1/2/3)

        • @@ -100,7 +100,7 @@

        5.2.2.1.3. Structure of datasets in the

    -

    5.2.2.1.4. Other things to note

    +

    5.2.4.1.4. Other things to note

    • if measuring AC, the first level of registers is always “total/sum” of a certain value and the L1/2/3 registers are for the distinct phases

      • @@ -109,17 +109,17 @@

      5.2.2.1.4. Other things to note

    -

    5.2.2.2. Published variables

    +

    5.2.4.2. Published variables

    -

    5.2.2.2.1. powermeter

    +

    5.2.4.2.1. powermeter

    The basic dataset of powermeter values as used in the EVerest powermeter interface. This dataset will be periodically published by the module.

    -

    5.2.2.3. Provided commands

    +

    5.2.4.3. Provided commands

    -

    5.2.2.3.1. get_signed_meter_value

    +

    5.2.4.3.1. get_signed_meter_value

    currently not implemented

    @@ -153,13 +153,13 @@

    Table of Contents

    Previous topic

    -

    5.2.1. EvseManager

    +

    5.2.2. EvseSlac

    Next topic

    5.2.3. LEM DCBM 400/600

    + title="next chapter">5.2.5. LEM DCBM 400/600