Link ECU + AI: Analyse PCLink Datalogs with Claude

The workflow on Link

Log

Record a pull or cruise with the right channels.

Export

CSV from PCLink, all channels.

Analyse

The agent finds issues, with evidence.

You decide

Apply small changes to a map copy, re-log.

The full method is in reading datalogs with AI. This page covers what's specific to Link.

Logging on Link

Link gives you two ways to log. PC logging records to the laptop while you're connected. ECU logging records onboard on supported models, so you can log a real drive and download it later. Both open in the PCLink log viewer, and both work for AI analysis.

Log fuel and ignition channels at 20 Hz or faster for pulls and transients. If closed-loop lambda is enabled, log the CLL trim channels too. Otherwise lambda can look perfect while the trims are quietly doing the work.

Use the channel checklist to decide what to log.

Exporting PCLink logs to CSV

AI agents read CSV best. Native log formats generally need the vendor's software to open. Menu labels move between versions, so here's the general pattern:

Open the log in the PCLink log viewer.
Use its export option and choose CSV.
Select all channels. If you only export the ones on screen, that's all the agent will see.
Name it with context, e.g. 2026-11-02_g4x_cruise-3rd.csv.

Can't find it? Let a computer-use agent find the export option for you. Finding things on screen is what it's good at.

Typical Link channel names

Put the exact names from your export into the channel dictionary in your skill file. These are what you'll usually see:

What	Often appears as	Watch out for
RPM	Engine Speed
Load	MAP, TP / TPS (Main)	Which one your fuel table's load axis uses
Lambda	Lambda 1, Lambda Target	CLL trim channels if closed loop is on
Ignition	Ign Angle
Knock	Knock Level, per-cylinder knock	Knock threshold tables differ per cylinder
Trims	CLL Fuel Trim / closed-loop correction	Must be logged to judge the base map

Names vary by firmware and configuration. Always check them against your own export.

A starter prompt for Link logs

prompt · first look at a Link log

Attached is a PCLink CSV export from my [Link G4X] on a
[engine / fuel / boost]. It's a [3rd-gear WOT pull, 2,500-7,000 rpm].

1. Load it with code. Report rows, sample rate and channels; flag
   anything from my channel dictionary that's missing.
2. Sanity-check the sensors first (flat lines, pinned or impossible values).
3. Segment into idle / cruise / tip-in / full load / overrun.
4. Compare lambda to target in each segment; report regions > 3% off
   with time, RPM and load.
5. Check knock and ignition for timing pulled.
6. Rank findings HIGH / MED / INFO with evidence.

Diagnosis only. Don't suggest changes until I agree.

Computer use in PCLink

Online = live. When PCLink is connected, a table edit can take effect in the ECU straight away, while the engine is running. Keep computer-use agents on offline map files unless you are watching every step, and tell them to stop on any connect or store prompt.

Offline, PCLink is ideal for L2 work. The agent can open a saved map, navigate to a table, stage the exact cell changes you approved, and list table, cell, old → new for your records.

Paste the guarded session starter at the start of every session, and set the autonomy level before the agent touches anything.

See the same channels live

KrispyGauge for Link

The KrispyGauge reads the Link generic dash CAN stream (500 kbit/s, 11-bit IDs) from G4X and G4+ ECUs. It also reads the Link Dash 2 Pro stream, so an ECU already set up for a Dash 2 Pro works without changing its CAN output. Lambda, MAP, knock and temperatures go straight to your dash.

Link ECU supported signals · CAN bus termination guide

See KrispyGauge → ECU installs: Krispy Workshop

Link + AI: FAQ

Can Claude read Link ECU PCLink logs?

Yes, once exported. Open the log in the PCLink log viewer, export it to CSV with all channels, and give the CSV to Claude. It will load it with code rather than skimming it.

Is it safe to let an AI agent use PCLink?

When PCLink is online, table edits can take effect in the ECU straight away. Keep agents on an offline map file, approve every change, and stop the session if a connect or store prompt appears.

Does onboard ECU logging work for AI analysis?

Yes. Logs from PC logging or ECU logging both open in the PCLink log viewer, and both can be exported to CSV for an agent to analyse.

What channels should I log on a Link G4X?

Engine speed, MAP, throttle, Lambda 1, lambda target, ignition angle and knock level as a minimum, plus closed-loop lambda trims if closed loop is enabled, and IAT, coolant temperature and injector duty.