VibeTuners
MaxxECU · Race, Pro, Sport, Street · MTune

MaxxECU + AI

MaxxECU ECUs are tuned in MTune and are known for strong internal logging and a huge number of tables. That suits AI agents well, provided you help them with long logs and channel names. This is the MaxxECU version of the VibeTuners workflow.

Updated By the KrispyGauge team4 min read

The workflow on MaxxECU

01

Log

Record a pull or cruise with the right channels.

02

Export

CSV from MTune, all channels.

03

Analyse

The agent finds issues, with evidence.

04

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 MaxxECU.

Logging on MaxxECU

Internal logging is a MaxxECU strength. Long sessions at high sample rates are easy, which also means big files. Don't paste a huge log into a chat and hope. Ask the agent to load it with code, then filter to the conditions you care about (e.g. TPS > 90% or a specific RPM band) before analysing.

On V engines, log both lambda banks. A bank-to-bank difference is often the most useful thing an agent can find.

Use the channel checklist to decide what to log.

Exporting MTune 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:

  1. Open the log in MTune's log view.
  2. Export it to CSV with all channels.
  3. For long logs, ask the agent to downsample or slice by time with code before analysing.
  4. Name it with context, e.g. 2026-11-02_maxx-pro_track-session2.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 MaxxECU channel names

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

WhatOften appears asWatch out for
RPMRPM
LoadMAP, TPSLoad axis source per table
LambdaLambda A / Lambda B, targetBank A vs B on V engines
IgnitionIgnition AngleApplied corrections vs base
KnockKnock level / knock retard channelsRaw level vs retard applied
TrimsShort-term fuel trim per bankLambda correction, not a base-map value

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

A starter prompt for MaxxECU logs

prompt · first look at a MaxxECU log
Attached is a MTune CSV export from my [MaxxECU Pro] 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.

More in the prompt library.

Computer use in MTune

MTune exposes a lot of settings, which is great for tuners but makes it easy for an agent to wander. Two tips:

  • Give exact table names and ask the agent to search for them rather than browse menus.
  • Keep it on an offline copy of the map, and stop it before anything that writes to the ECU.

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 MaxxECU

The KrispyGauge reads the MaxxECU CAN dash output (500 kbit/s, 11-bit IDs), including the FAST 50 Hz group (RPM, TPS, MAP, lambda, ignition angle, fuel trims, knock) and the SLOW 10 Hz group for temperatures and pressures. The channels your agent analyses are the ones you see live.

MaxxECU supported signals · Running multiple KrispyGauges

See KrispyGauge → ECU installs: Krispy Workshop

MaxxECU + AI: FAQ

Can Claude analyse MaxxECU logs?

Yes. Export the log from MTune's log view to CSV and give it to Claude. For very long internal logs, ask it to filter or downsample with code first.

Why do MaxxECU logs need a channel dictionary?

MaxxECU exposes a lot of tables and channels, often with separate bank A and B lambda and both raw knock levels and retard channels. A dictionary that maps each CSV column to its meaning and units stops the agent mixing them up.

Can computer use operate MTune?

Yes, it works through the screen like a person. Because MTune has so many settings, give it exact table names and ask it to search rather than browse, and keep it on an offline map copy.

Can AI tune my MaxxECU for me?

It can find problems and propose small, capped changes with evidence. You still review and apply every change and verify with a new log.