Control Pilot logs
The CSV shapes the tool understands and how it lines them up with the capture.
Two shapes
| Shape | Columns | Example header |
|---|---|---|
| Raw waveform | time and the Control Pilot voltage, sampled fast enough to see the PWM | time,cp_v |
| Processed | time with state and duty cycle, optionally frequency, high and low level | timestamp,state,duty,freq_hz |
Column names are matched loosely (time, timestamp, zeit; cp, pilot, u_cp; state, zustand; duty, pwm). Separators can be comma, semicolon, tab or bar. When the columns are not clear, a mapping dialog asks.
Current, voltage and power
Either shape may carry measured channels: currents (I_L1, I_DC, current), voltages (U_L1, U_DC, voltage) and active power (P, P_total, power), with the unit in the name or in brackets (I_DC [A], P [kW]). The Power tab draws them, the Curve tab puts them beside what the protocol reports, and the power checks use them.
A power analyzer or data logger export with no pilot column at all is read as a measurement log: nothing to map, and the pilot checks report not applicable. Give it absolute timestamps so it lines up with the capture. On DC, PW-07 then holds the present current and voltage the charger reports against what was measured.
Alignment
Absolute timestamps are aligned directly. Relative logs are aligned on anchors: the 5 % duty cycle against the first SLAC message, and, on AC, the change from B to C against PowerDeliveryReq Start. The Alignment tab shows the offset and lets you adjust it before the CP checks that compare both clocks run.