UCAN Studio

Analysis

Trace analysis, full-stack protocol decoding, signal plotting, and reporting — one workflow for every source.

UCAN Studio trace analysis perspective with decoded frames, protocol detail, and signal plot

Trace From Four Sources, One Workflow

File imports, live hardware capture, and automatic capture from every simulation and test run all land in the same trace perspective with the same analysis tools. Monitor mode adds live entity tracking across CAN, V2G, and SLAC.

File import

PCAPNG, PCAP, ASC, MDF4, CSV, candump

Live hardware

Capture directly from the bench

Simulation runs

Auto-captured with every simulation

Test runs

Auto-captured as attached evidence

Full-Stack Decoding, L2 to L7

Protocol decoding spans every layer. Decode contexts combine DBC, ARXML, ODX, CDD, LDF, and TLS keys as named, project-wide presets — so the same context applies consistently across every session, including retroactive TLS decryption from a keylog.

L7
V2G (ISO 15118-2/-3), SLAC, SDP, DoIP, UDS, OBD, SOME/IP
L4 + security
TCP, UDP, TLS (keylog decryption)
L3
IPv4, IPv6, ARP, NDP
L2
Ethernet, VLAN, HomePlug GP, CAN / CAN FD (DBC)
Signal plot with stacked lanes during a live capture and dual-cursor measurement

Signal Plotting on One Timeline

  • Multi-axis plots, dual-cursor measurement, and computed signals
  • Any communication signal — CAN, LIN, or Ethernet via DBC — plus built-in V2G, SLAC, and SDP fields
  • FMU model variables, environment variables, and MDF channels on the same timeline
  • Trace ↔ plot synchronization — selecting a point on a plot jumps to the matching frame row in the trace view

Databases & Formats

  • Databases: DBC, LDF, ODX, CDD, PDX, DEXT, A2L
  • Import: PCAPNG, PCAP, ASC, MDF4, CSV, candump

Reproducible & Shareable

Computed signals, plot presets, and filter presets persist in the .ucprj project, versioned with the repository and shared across the team and CI.

AI-native

Ask the uCAN Engineer to Read the Trace

Decoded frames, signals, and plots are all programmatic tools, so the uCAN Engineer agent can analyze a capture the way you would — in plain language. Ask it to find a value, correlate signals across nodes, or explain what happened, and it works directly on the live trace session.

  • Query decoded signals and protocol fields across every node on the bus
  • Correlate behavior between sources and summarize findings with the evidence rows
  • Stay in the same window — no export, no separate analysis tool
uCAN Engineer agent analyzing a trace to identify the CHAdeMO protocol number from the EV and SE nodes

Analyze Your Own Captures

Bring a trace from your bench and see UCAN Studio decode, plot, and report on it.

Contact Our TeamBack to UCAN Studio