Reading the results
The verdict, the stage strip, the three views, the timeline, the message table and the findings.
Verdict and stages
The verdict says how the session ended, who is the likely party (car, charger, either or unknown) and how confident the tool is. The stage strip shows how far the session got: passed stages are filled, the stage where it broke is marked, stages the capture cannot show are dashed.
Workspace, Story and Scope
- Workspace: the verdict strip, the timeline, the message table and a side panel with the findings, the selected message, the checks, your notes and every analysis (Power, SLAC, Timing, TLS, CP quality, Alignment).
- Story: where the session stopped, the evidence behind the verdict with the messages around each finding, and what to read next. A session that did not charge opens here; "Show in the workspace" jumps to the messages.
- Scope: a large dark timeline for the bench. Click to set cursor A, shift and click for cursor B; the readout gives the Control Pilot, the current and the last message at each cursor and the time between them. Click a message in the drawer to put cursor A on it.
- Switch with the View control in the verdict strip. The choice holds for the open file; the scope also stays for the next file until you leave it.
Timeline and table
- The timeline puts the stages, Control Pilot, current, SLAC, SDP, TCP and TLS, V2G and CAN on one time axis. Wheel to zoom, drag to pan, shift and drag to measure, 0 to fit.
- The V2G lane folds repeated messages into loops, labelled with their count, period and response times; red ticks mark slow answers. Zoomed in to under 2 s per screen it shows every request and response as a sequence between the car and the charger.
- The Power tab has a Headroom view: the permitted current minus the highest phase. Amber is over the limit within the settling time the standard allows, red is over for longer, where PW-01 fails.
- The message table lists every event. Filter by layer, search in names and field values, and click a row to see its decoded fields and bytes.
- Sequence, beside Table above the message table, draws the V2G messages between the car (left) and the charger (right) with the frame number between them. Each message shows the time since the one before it, and a response its answer time. Three or more pairs of one message in a row fold into one line with the number of cycles, the time they span and the shortest and longest answer; open it to see each message. A message with a finding is outlined red for an error or amber for a warning, with the check id beside it; the id opens the check.
Findings and checks
Findings are what the checks found, sorted by time, with the messages involved. Each finding names its check; open it in the Checks section to see what the check looks at, which standard it comes from and which limits it used.
Group by stage puts the findings under the stage they happened in, the stage where the session stopped first. A finding after the first error is tagged "may follow from" it: one broken step often trips the checks of the steps after it, so start with the first error.
Why this verdict
- The story has a Why this verdict card, and the report a section of the same name: the last stage passed and where the session stopped, the findings the verdict leans on, the category and the party.
- Other readings lists errors the verdict did not lean on, one per category, in case the first cause is not the real one.
- What could make it wrong lists what about the capture could mislead the verdict: lost frames, one side never heard, the two sides announcing different editions, or a verdict the classifier itself rates as low confidence.
Phones, languages and long captures
- On a phone the timeline opens with the stages, the Control Pilot state, V2G and CAN, and each message in the table is a card. The lane chips open the other lanes.
- The language menu in the top bar switches the analyzer screens to German or Chinese. Verdicts, findings and check texts stay English, so they can be quoted in a bug report as they are.
- In a long capture a lane with more messages than pixels draws how dense they are instead of each message; zoom in and the single messages come back. Pointing at the density still names a message.