AI ECU File Analyzer

Identification

What the analyzer extracts

Every file uploaded through the request wizard is scanned. The analyzer pulls available ECU metadata, normalises it against the seeded ECU type catalogue, and tags the request with what it found. Your tuner sees the match instantly, or a clearly flagged “no confident match” so they can decide manually.

• ECU family + manufacturer + variant
• Software / hardware identifier
• VIN extraction where present in the dump
• Confidence score per attribute

AI File Match

A file you’ve solved before delivers itself

Every upload is fingerprinted and read for its software and hardware numbers, then matched against every job on your portal, and, if you run a network, across it. An eligible match is delivered, completed and charged automatically. Everything else lands with your tuner as a suggestion, never a silent guess.

• Three tiers: exact byte match · same factory ECU read by a different tool · ECU-software fallback
• Strict safety gates, a Stage 1 file never ships to a Stage 2 request
• Instant re-delivery + auto-charge; pure margin on work you already own
• New, unseen work always goes to a human tuner

Library Import

Ten years of desktop projects, working for you again

Your map editor has quietly built the most valuable asset in your workshop: every original you ever read, paired with the tune you saved on it. Right now it lives in a database on one PC, and it does nothing for the job that came in this morning.

Library Import brings that archive into your portal. You point a small tool at your ECM Titanium projects folder. It reads them where they sit, pairs every original with the tunes saved against it, files them by make and model, and prepares the lot for your portal’s file library. From then on AI File Match treats a job from eight years ago exactly like yesterday’s, same fingerprint, same software and hardware numbers, same instant delivery.

• Your archive is opened read-only, nothing in it is moved, renamed or changed
• A scan pass runs first, so you see what can and cannot be read before anything is imported
• Your own naming survives: every modification name in your archive is mapped to your portal’s list, not guessed
• An original used across many jobs is stored once, not once per job
• Anything unreadable is set aside with the reason and the run carries on, you get the list
• Run as a guided import with us and quoted on the size of the archive, the tool stays with you for whatever you save next

Team copilot

An assistant that does the work, on your confirm

Ask in plain language and it takes the action: add credits, refund an order, assign a tuner, change a status, draft a dyno sheet, look up a plate, pull live revenue or server stats. Every action that moves money or data waits for one explicit confirm click, nothing runs silently. It answers from your live portal data and your own knowledge base, in a dockable in-app chat with a command palette.

• Real actions with a confirm step, not just chat
• Answers from your live dashboard: revenue, workload, queue
• In the file editor too, grounded on your workshop knowledge base
• Reads diagnostic logs: boost target vs actual, fault codes, where to look

Customer-facing AI

A branded assistant your customers talk to, 24/7

On Telegram and in the file-request chat, under your name: a customer sends a number plate, or just a photo of the car, and gets the exact vehicle, your stages and gains from your own catalogue, and a branded quote PDF. Questions are answered only from the knowledge base you curate, in your voice, and handed to a human the moment the AI is unsure.

• Plate or photo → full vehicle report + quote PDF; every quote saved as a lead
• Live order status, the “any update, mate?” messages stop
• It informs and hands off, it never touches files, orders or money
• Ships OFF by default; runs on your own AI key; per-customer daily limits and per-dealer switches you control