Which files the tool reads

Captures, CAN logs and Control Pilot logs, recognised by their content rather than their name.

Network captures

  • pcap and pcapng in both byte orders, with microsecond or nanosecond timestamps.
  • Link types: Ethernet, VLAN tagged Ethernet, Linux cooked capture v1 and v2, and SocketCAN.
  • Wireshark JSON exports with the raw bytes: tshark -r capture.pcapng -T json -x (or -T ek -x), or File, Export Packet Dissections, As JSON with the packet bytes included. A capture filtered or cut in Wireshark then reads like the pcap it came from. Without -x the export holds no bytes, and the tool says so.
  • Contents: HomePlug Green PHY management messages (SLAC), IPv6 and IPv4, UDP (SDP), TCP (V2G) and TLS.

CAN logs

candump logs, Vector ASC and PEAK TRC files, and CAN frames inside a pcap. The format is picked by reading the first bytes of the file, so the extension does not matter.

Control Pilot logs

A CSV export with either the raw Control Pilot voltage over time, or processed rows with state and duty cycle. See Control Pilot logs.