Guide: EVSE operations
======================

The EVSE path is the core operator workflow for customer EVCC validation. You pick a charger personality, set transport and TLS policy, and decide whether the run is software-only or tied to a bench profile.

Recommended decision sequence
-----------------------------
.. list-table::
   :header-rows: 1
   :widths: 35 65

   * - Question
     - Recommended action
   * - Which protocol family do I need?
     - Choose ISO 15118-2, DIN 70121, ISO 15118-20, or MCS.
   * - Which charger personality fits?
     - Start with a profile ID such as ``abb_pnc_realistic``, ``abb_iso20_ac_eim_realistic``, ``abb_iso20_dc_pnc``, or ``delta_din70121``.
   * - Is this software-only or bench-linked?
     - If software-only, start without a hardware profile. If bench-linked, register and reference a hardware profile.
   * - Do I need campaign hooks?
     - Use ``--campaign-hooks``, ``--campaign``, and ``--campaign-case`` when you want the live runtime to stay tied to packaged campaign semantics.

Profiles that are useful for first runs
---------------------------------------
- ``abb_pnc_realistic`` for ISO 15118-2 DC PnC with realistic electrical behavior.
- ``abb_iso20_ac_eim_realistic`` for realistic ISO 15118-20 AC EIM.
- ``abb_iso20_dc_pnc`` for ISO 15118-20 DC PnC and BPT-oriented work.
- ``delta_din70121`` for DIN 70121 DC.
- ``mcs_reference_bench`` for MCS bench-linked execution.

When to add a hardware profile
------------------------------
- When you need a bill of materials, an I/O map, or a bench orchestration sequence.
- When you need NI-DAQmx or VeriStand capture and safe-stop evidence.
- When the lab must prove a measured relation between protocol events and bench signals.