**I Built an AI Assistant for ECU Master EMU Black Studio**

Quick one - not a tuning tool, doesn’t know anything about engines, doesn’t touch your tune
for you. If you’re after help actually tuning your car, this isn’t that.

What it actually is: I’ve been using an AI coding assistant (Claude) to help me dig through
my own EMU Black project - auditing settings, checking tables, that kind of thing. Problem
is, normally that means constantly screenshotting Studio, describing what’s on screen,
waiting for a click, screenshotting again… it gets old fast, especially going through a
lot of tables.

So I built a small bridge tool that lets the AI assistant drive Studio directly instead -
open a settings window by name, read/export a table as a file instead of a screenshot, edit
a value, that sort of thing. It’s just plumbing between an AI assistant and Studio’s UI, not
a tuning tool itself - it makes the back-and-forth faster, it doesn’t make any tuning
decisions.

Sound familiar? Hundreds of settings buried in a tree and no idea what half of them do. A
table full of numbers with no clear sense of what “normal” looks like for your combo. Every
tutorial you find is for someone else’s engine, not yours. You know an AI assistant could
probably help you make sense of it all - if only it could actually see what you’re looking
at instead of you describing it screenshot by screenshot. That’s the gap this closes. Your
AI assistant still isn’t deciding what your tune should be, that’s still on you to verify -
it just isn’t working blind anymore.

Built it purely for my own RX8 K24 swap project, wasn’t originally planning on doing anything
with it, but figured if it saved me a load of screenshotting it might save someone else the
same hassle. Put it up here: EMU Black Bridge - the price on it is
just to claw back a bit of the time I put into building it, not trying to make a business out
of it.

Happy to answer questions if anyone wants to know more about how it works.

Interesting. I went he other way when using Claude and got it to understand (most of) the XML format and scalars of the map (when saved in XML of course). That way if I gave Claude logs to look at, it could give me the XML values for an adjusted table, to save me having to copy it cell by cell etc. I haven’t made a decision on whether Claude or the built in autotune is better yet, when it comes to tuning VE maps for example.