Tools in the analyzer

Negotiation, charging curve, timers, capture quality, compare, OCPP, certificates, custom checks, exporting frames, the message codec and the command line.

The groups of the side panel

Under Findings, Message, Checks and Notes, the analyses and tools sit in six groups: Protocol (Timing, Negotiation, Timers), Energy (Power, Curve, Grid), Link (SLAC, CP quality, Alignment), Security (TLS, Security), Backend (OCPP, OCPI) and Testing (Capture, Compare, Test cases, AFIR). Pick a group to see its tabs; a link from a finding opens the right group by itself. In Simple mode the groups stay folded behind More analyses until you open them; Expert, beside Simple in the top bar, shows them at once, with the limits and the scope.

  • Negotiation: what the car asked for next to what the charger offered, with the value both can live with. A pair that cannot both hold is marked as a conflict, and every refused answer links to what its code means.
  • Curve: target against delivered current and voltage, the power, the state of charge and the energy, with how closely the charger followed the target.
  • Timers: every interval the checks timed against its limit, the closest to its limit first. A bar shows the share used; the mark on it is where the watchdog starts calling a timer close (tools.timerCloseShare in the limit profile).
  • Capture: whether the capture itself is complete. An answer the car clearly received but the capture lacks, TCP bytes that never arrived or a side the sniffer never heard mean a finding may be about the capture rather than the cable.
  • Compare: this session beside another session of the file, a demo or a file of yours. The list of messages shows where the two part ways; below it the stages, the parameters and the response times that differ.
  • OCPP: drop the OCPP log of the charger with the capture, or add it here, to see the connector status and the transaction on the same timeline as the cable. The tab names the OCPP version the messages speak (1.6, 2.0.1 or 2.1) and lists the OC checks: every message against the OCA JSON schema of that version, every call answered in time, one call at a time, defined error codes, unique message ids, the boot accepted first, and the transactions in order. The XL checks in the same table hold the log against the cable: charging reported when the energy transfer starts and stops, the energy billed against the meter the car was shown, no energy after a rejected ID, and the stop reason against the verdict. The log and the capture should run on synchronised clocks.
  • Security: the Security tab shows what the car asked for in SDP and what it got, the TLS session, and the SLAC matches with the network key they handed over (hidden until you ask). SEC-01 to SEC-04 check who confirmed the match, that the MAC addresses stayed the same, that a request for TLS was not answered without it, and that the key is not trivial or reused. The capture holds that key, so share it with care.
  • Pilot faults: with a Control Pilot log, PF-01 to PF-04 name a missing diode, a pilot that opens while energy flows, a pilot held at 0 V and an open proximity pin.
  • OCPI: drop the charge detail record (CDR) or the OCPI session with the capture, or add it in the OCPI tab. The tab lists the records beside the session they overlap, and CDR-01 to CDR-04 check the required fields, that times, energy and cost add up, that the record matches the cable and the OCPP transaction, and signed values inside the CDR.
  • Signed meter values: OCMF records in the OCPP log are listed in the OCPP tab with their readings, and their signatures are checked in the browser with the key the charger sent, or with the key you paste from the charger or the register. SM-01 to SM-03 check the signature, the readings and that the records make up a whole transaction.

Certificates, custom checks and exporting frames

  • The TLS tab shows the certificate chain from the trust anchor the car must hold down to the charger certificate, with the validity on the day of the session and the problems of each certificate.
  • Limits, Custom checks: write a condition such as name = "ChargingStatusRes" and responseMs > 250. The editor says as you type whether it reads and how many messages of the open session match. Custom checks add findings; they never change the verdict. They are saved with the profile.
  • Export frames, next to the report buttons, saves the frames of this session as a small pcapng for a bug report. In the scope, Export A to B saves the frames between the two cursors.
  • Each finding travels with the exported pcapng as a packet comment on the frames it points to, and the verdict as the file comment. In Wireshark they show under Packet comments and in the Expert Info; the display filter frame.comment contains "V2G Session Analyzer" lists them.

Bookmarks and comments

  • In the Notes tab, pin a comment to the selected message, to scope cursor A, to a finding or to the start or end of the session. It shows as a flag on the time axis; point at the flag to read it.
  • Comments carry your name: the signed in name in the hosted edition, else the name you type once in this browser.
  • Your own comments can be edited; a merged note says whose it is. Comments stay with their session even when a different profile or alignment splits the file differently.
  • In the hosted edition, tick Share with my team to keep a comment on the server for your team instead of in this browser. Only the comment and the SHA-256 of the capture are sent; the capture is not.
  • To share them, save the project and send it. A colleague opens it with the same capture, adds theirs and saves it again. Merge comments from a project adds what is new; a project saved for another capture is refused, since its comments would point at the wrong moments.

Message codec and command line

  • Message codec, under Learn in the top bar: paste a V2G message as hex, read it, change a value in the document and encode it again, with or without the V2GTP header.
  • The command line runner gives the same analysis for test pipelines: node dist-cli/v2g-analyze.mjs capture.pcapng --junit results.xml. It exits with 1 when a session did not complete (or, with --fail-on, had errors or warnings).
  • Batch mode adds trends over the files: how sessions ended, per charger and per car, and which checks fail most often. Files are analysed side by side, up to four at a time.
  • Cars against chargers: a table of every car (EVCCID or MAC) against every charger (EVSEID or modem) of the batch, as a test event reports it, with the sessions completed of all for each pair; hover a cell for its most common problem. Beside it the share completed of the batch stands next to published field figures, with their sources; they measure other things than a batch of captures, and the page says so.
  • ChargeX KPIs: for OCPP 2.0.1 and 2.1 logs the OCPP tab shows Session Success, Charge Start Success, Charge End Success and Charge Start Time with the transactions they count. In batch mode an OCPP log may come without a capture; the KPIs of every OCPP log of the run are added up below the table. A log in the device_ID,message,timestamp table of the INL calculator keeps its chargers apart.
  • ChargeX error codes and port uptime: the OCPP tab lists each fault the charger reported with the Minimum Required Error Code (MREC, CX001 to CX026) it carried, the class and the party to resolve it, and OC-09 notes a fault sent without one (OCPP 1.6 vendorErrorCode with vendorId https://chargex.inl.gov, OCPP 2.0.1 techCode of a NotifyEvent). Below it, the uptime of each charging port as the log shows it, after the formula of 23 CFR 680.116 for NEVI funded chargers: minutes available or in use, faulted, unavailable and unknown, the share of the known minutes, the share with every unknown minute counted as outage, and where the port stands against the 97 percent of the rule. A silence of the charger longer than ocpp.uptimeMissedHeartbeats heartbeat intervals (ocpp.uptimeGapS without one) is unknown. The outages the rule leaves out (utility, vehicle, scheduled maintenance, vandalism, natural disasters, closed hours) need the operator records, so nothing is left out and the figure is no regulatory verdict. Batch mode lists every port of every OCPP log of the run in one sortable table and joins the logs of the same charger.
  • Short summary, next to Export report, makes a one page report for a ticket: the verdict, why, the errors that matter, your notes and the file hashes. On the command line, add --short to --html.