Coverage
Which ECUs, and what we read from them.
FT450, FT500, FT550 and FT600 — the PowerFT line, tuned in FTManager — from the CSV datalog FTManager exports. FT700 and FT700PLUS are the VisionFT line and are not supported today.
| Model | Line | Tuned in | What we read | Status |
|---|---|---|---|---|
| FT450 | PowerFT | FTManager | CSV datalog export | Supported |
| FT500 | PowerFT | FTManager | CSV datalog export | Supported |
| FT550 | PowerFT | FTManager | CSV datalog export | Supported |
| FT600 | PowerFT | FTManager | CSV datalog export | Supported |
| FT700 | VisionFT | FuelTech Vision | A different export from different software. Not validated, so not claimed. | Not yet |
| FT700PLUS | VisionFT | FuelTech Vision | A different export from different software. Not validated, so not claimed. | Not yet |
This table lists the models we have actually loaded logs from. The reader works from the CSV header row rather than from a model identifier, so a PowerFT unit that isn't listed will very likely load — but "very likely" is not the same as tested, and only tested gets a row here.
The input
One file: the CSV log.
FTT loads the official CSV datalog export from FTManager. It reads the header row and you choose which column is which — the X and Y axis channels, the lambda channel, the coolant and throttle channels the filters use. Nothing is guessed from a channel name, because channel names differ between setups and every wrong guess would be silent.
There is no firmware version to match. We read the file your software wrote, not the ECU, so a firmware update on the ECU does not change what FTT can open.
What it doesn't do
It never touches the ECU.
FTT does not connect to the ECU. No USB, no CAN, no Bluetooth, no flashing, no writing. It is a desktop application that opens a log file and produces numbers you copy into your own tuning software yourself.
That is a design decision rather than a missing feature. The moment a tool can write to an ECU it needs to be right about a great deal more than arithmetic, and we would rather be a tool you check than a tool you trust.
The output
A clipboard, and one XML file.
A selected rectangle copies as tab-separated values, in the same shape as the grid — the format a tuning table paste expects. The project itself saves as a single XML file on your own disk: breakpoints, base fuel, %change, targets, filter settings, and the columns you mapped.
That file is yours, it is plain text, and it stays readable whether or not you are still a customer. What happens if you stop paying.
Fullsend Tuner Toolkit is not affiliated with, endorsed by, or supported by FuelTech. FuelTech, FTManager, PowerFT and VisionFT are trademarks of their respective owners. The ECU manufacturer is at fueltech.net.
Running something that isn't on this list? Send us a log — that is how rows get added, and it comes to a real person.