EVerest API definition for EV board support 1.0.0

API for EVerest API clients implementing ev board support.

  • #EVerest
  • #ev_board_support

Servers

  • mqtt://localhost:1883/everest_api/1/ev_board_support/{module_id}mqttdefault

    default local MQTT

    object
    module_id
    required
    string

    The ID of the module as defined in the EVerest config file.

Operations

  • RECEIVE e2m/enable

    Direction: EVerest to Module

    Operation IDreceive_enable

    Available only on servers:

    Accepts the following message:

    Receive enable or disablereceive_enable

    Enables or disables the EV simulation.

    Message IDreceive_enable
    Payload
    boolean

    True: enabled. False: disabled.

    Examples

  • RECEIVE e2m/set_cp_state

    Direction: EVerest to Module

    Operation IDreceive_set_cp_state

    Available only on servers:

    Accepts the following message:

    Receive CP Statereceive_set_cp_state

    Receive the CP State that should be set by the EV board support driver (controlled by S2)

    Message IDreceive_set_cp_state
    Payload
    string

    ControlPilot state

      Allowed values:
    • "A"
    • "B"
    • "C"
    • "D"
    • "E"

    Examples

  • RECEIVE e2m/allow_power_on

    Direction: EVerest to Module

    Operation IDreceive_allow_power_on

    Available only on servers:

    Accepts the following message:

    Receive permission to switch relays onreceive_allow_power_on

    If false, contactor must never be switched on.

    Message IDreceive_allow_power_on
    Payload
    boolean

    True: allow power on, false: do not allow power on.

    Examples

  • RECEIVE e2m/diode_fail

    Direction: EVerest to Module

    Operation IDreceive_diode_fail

    Available only on servers:

    Accepts the following message:

    Receive diode failure statereceive_diode_fail

    If true, simulator should set a diode failure.

    Message IDreceive_diode_fail
    Payload
    boolean

    True: Diode failure, false: no failure.

    Examples

  • RECEIVE e2m/set_ac_max_current

    Direction: EVerest to Module

    Operation IDreceive_set_ac_max_current

    Available only on servers:

    Accepts the following message:

    Receive the max AC currentreceive_set_ac_max_current

    Maximum AC current to be requested from the EV.

    Message IDreceive_set_ac_max_current
    Payload
    number

    Max current requested from the EV.

    Examples

  • RECEIVE e2m/set_three_phases

    Direction: EVerest to Module

    Operation IDreceive_set_three_phases

    Available only on servers:

    Accepts the following message:

    Receive three or one phase supportreceive_set_three_phases

    Wether the EV should indicate single or three phase support.

    Message IDreceive_set_three_phases
    Payload
    boolean

    True: Three phase support, False: One phase support.

    Examples

  • RECEIVE e2m/set_rcd_error

    Direction: EVerest to Module

    Operation IDreceive_set_rcd_error

    Available only on servers:

    Accepts the following message:

    Setting set RCD error.receive_set_rcd_error

    Setting a rcd error. Only for simulation purpose.

    Message IDreceive_set_rcd_error
    Payload
    number

    RCD current in mA.

    Examples

  • SEND m2e/bsp_event

    Direction: Module to EVerest

    Operation IDsend_bsp_event

    Available only on servers:

    Accepts the following message:

    Send BSP eventsend_bsp_event

    Events from CP/Relais

    Message IDsend_bsp_event
    object

    Event stream from ControlPilot signal/relais.

    Examples

  • SEND m2e/bsp_measurement

    Direction: Module to EVerest

    Operation IDsend_bsp_measurement

    Available only on servers:

    Accepts the following message:

    Send BSP Measurementssend_bsp_measurement

    Instantaneous BSP measurements

    Message IDsend_bsp_measurement
    object

    Bsp Measurement

    Examples

  • SEND m2e/ev_info

    Direction: Module to EVerest

    Operation IDsend_ev_info

    Available only on servers:

    Accepts the following message:

    Send EV Infosend_ev_info

    Details about the EV if available

    Message IDsend_ev_info
    object

    Information about the connected EV if available

    Examples

  • SEND m2e/raise_error

    Direction: Module to EVerest

    Operation IDsend_raise_error

    Available only on servers:

    Accepts the following message:

    Send raise errorsend_raise_error

    Signal to EVerest that an error happened.

    Message IDsend_raise_error
    object

    Error object with type, subtype and message.

    Examples

  • SEND m2e/clear_error

    Operation IDsend_clear_error

    Available only on servers:

    Accepts the following message:

    Send clear errorsend_clear_error

    Signal to EVerest that a previously raised error is no longer active.

    Message IDsend_clear_error
    object

    Error object with type, subtype and message.

    Examples

  • RECEIVE e2m/heartbeat

    Direction: EVerest to Module

    Operation IDreceive_heartbeat

    Available only on servers:

    Accepts the following message:

    Receive heartbeatreceive_heartbeat

    Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration

    Message IDreceive_heartbeat
    Payload
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached

    Examples

  • SEND m2e/communication_check

    Operation IDsend_communication_check

    Available only on servers:

    Accepts the following message:

    Send communication checksend_communication_check

    Signal to EVerest that communication is good or check shall be stopped

    Message IDsend_communication_check
    Payload
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

    Examples

Messages

  • #1Receive enable or disablereceive_enable

    Enables or disables the EV simulation.

    Message IDreceive_enable
    Payload
    boolean

    True: enabled. False: disabled.

  • #2Receive CP Statereceive_set_cp_state

    Receive the CP State that should be set by the EV board support driver (controlled by S2)

    Message IDreceive_set_cp_state
    Payload
    string

    ControlPilot state

      Allowed values:
    • "A"
    • "B"
    • "C"
    • "D"
    • "E"
  • #3Receive permission to switch relays onreceive_allow_power_on

    If false, contactor must never be switched on.

    Message IDreceive_allow_power_on
    Payload
    boolean

    True: allow power on, false: do not allow power on.

  • #4Receive diode failure statereceive_diode_fail

    If true, simulator should set a diode failure.

    Message IDreceive_diode_fail
    Payload
    boolean

    True: Diode failure, false: no failure.

  • #5Receive the max AC currentreceive_set_ac_max_current

    Maximum AC current to be requested from the EV.

    Message IDreceive_set_ac_max_current
    Payload
    number

    Max current requested from the EV.

  • #6Receive three or one phase supportreceive_set_three_phases

    Wether the EV should indicate single or three phase support.

    Message IDreceive_set_three_phases
    Payload
    boolean

    True: Three phase support, False: One phase support.

  • #7Setting set RCD error.receive_set_rcd_error

    Setting a rcd error. Only for simulation purpose.

    Message IDreceive_set_rcd_error
    Payload
    number

    RCD current in mA.

  • #8Send BSP eventsend_bsp_event

    Events from CP/Relais

    Message IDsend_bsp_event
    object

    Event stream from ControlPilot signal/relais.

  • #9Send BSP Measurementssend_bsp_measurement

    Instantaneous BSP measurements

    Message IDsend_bsp_measurement
    object

    Bsp Measurement

  • #10Send EV Infosend_ev_info

    Details about the EV if available

    Message IDsend_ev_info
    object

    Information about the connected EV if available

  • #11Send raise errorsend_raise_error

    Signal to EVerest that an error happened.

    Message IDsend_raise_error
    object

    Error object with type, subtype and message.

  • #12Send clear errorsend_clear_error

    Signal to EVerest that a previously raised error is no longer active.

    Message IDsend_clear_error
    object

    Error object with type, subtype and message.

  • #13Receive heartbeatreceive_heartbeat

    Heartbeat produced by EVerest as configured via cfg_heartbeat_interval_ms in the EVerest configuration

    Message IDreceive_heartbeat
    Payload
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached

  • #14Send communication checksend_communication_check

    Signal to EVerest that communication is good or check shall be stopped

    Message IDsend_communication_check
    Payload
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

Schemas

  • Enabled
    boolean

    True: enabled. False: disabled.

  • EvCpState
    string

    ControlPilot state

      Allowed values:
    • "A"
    • "B"
    • "C"
    • "D"
    • "E"
  • PowerOnOff
    boolean

    True: allow power on, false: do not allow power on.

  • DiodeFailure
    boolean

    True: Diode failure, false: no failure.

  • AcMaxCurrent
    number

    Max current requested from the EV.

  • ThreePhaseSupport
    boolean

    True: Three phase support, False: One phase support.

  • RCDCurrent
    number

    RCD current in mA.

  • object

    Bsp Measurement

  • ErrorEnum
    string

    Type of error

    • CommunicationFault: The communication to the hardware or underlying driver is lost or has errors.
    • VendorError: Vendor specific error code. Will stop charging session.
    • VendorWarning: Vendor specific error code. Charging may continue.
      Allowed values:
    • "CommunicationFault"
    • "VendorError"
    • "VendorWarning"
  • object

    Error object with type, subtype and message.

  • CommunicationCheck
    boolean

    Send 'true' at least every 'cfg_communication_check_to_s' seconds to signal module is alive. Send 'false' to stop communication check'

  • HeartBeatId
    integer

    64bit unsigned integer. The id of every heartbeat increases by 1 and overflows when the maximum representable value is reached