Using your TunerStudio files in efi2000
efi2000 reads the same ECU definition, tune and log files TunerStudio uses. This guide covers which file is which and how to bring them over.
The three files
Tuning software for Speeduino, rusEFI, epicEFI and MegaSquirt works from the same files, in the ECU definition format published by EFI Analytics.
- INI, the ECU definition. Written by the firmware's developers, it describes the ECU's settings, tables, menus, dialogs, gauges and live data. Each firmware version has its own INI.
- MSQ, the tune. Your settings and table values, saved as XML. It is the file you back up and share.
- MLG, the log. A recorded datalog of live channels, which MegaLogViewer and TunerStudio open.
In a TunerStudio project folder, the INI is usually projectCfg/mainController.ini, the current tune is CurrentTune.msq, and logs are in DataLogs.
Bringing a project into efi2000
- Create a free account and create a project in your Garage.
- Under Project → ECU definition, upload the INI, or connect the ECU and let efi2000 look up the matching INI. For some firmware you download the INI yourself.
- Under Project → Tunes & backups, import your MSQ.
- Under Logs, import any MLG logs you want in the project.
- Open Tuning. ECU menus shows the INI's own menu tree, and Guided shows the same settings in first-tune order.
Project properties can also be imported from a TunerStudio project properties file, under Project → Project properties.
What carries over
- Menus, dialogs, tables and settings, built from the INI.
- Gauges and dashboards from the INI's [GaugeConfigurations].
- Every setting and table value in the MSQ.
- VE autotune settings from the INI's [VeAnalyze].
- MLG log playback.
The parser follows the ECU definition specification. Expressions it can't evaluate stay unresolved rather than guessed.
Going back to TunerStudio
Tunes save back to MSQ, and logs efi2000 records are standard MLG files, so they open in TunerStudio and MegaLogViewer again. You can use both tools on the same tune. Each time the ECU connects, efi2000 compares the ECU's tune with the project's, and you choose which one to keep.
What efi2000 adds
- It runs in desktop Chrome or Edge and connects to the ECU over USB with Web Serial, so there's nothing to install.
- Projects are saved to your account, with revision history, restore points and automatic backups.
- Table generation, including the boost table generator, Spotter tune checks and autotune all use the vehicle specs you enter once.
- Every log efi2000 records notes the tune it started on and each ECU write and burn.
- Editing, table generation and tune checks work with no ECU connected.
Current limits
- Writing and burning are confirmed on Speeduino hardware. rusEFI, epicEFI and MegaSquirt are supported through their INI files. The Compatibility page has the current status for each.
- Connecting to an ECU needs Web Serial: desktop Chrome or Edge over HTTPS. Logs and the library work in any browser.
- Exporting a whole project at once is on the roadmap. Tunes and logs export as files today.
TunerStudio and MegaLogViewer are products of EFI Analytics. efi2000 is independent and isn't affiliated with EFI Analytics.
Questions
- Do I need to convert my TunerStudio tune?
- No. efi2000 reads the MSQ directly and saves back to MSQ.
- Can I keep using TunerStudio alongside efi2000?
- Yes. Both use the same INI, MSQ and MLG files. When the ECU connects, efi2000 compares its tune with the project's and you choose which one to keep.
- Which browsers work with efi2000?
- Connecting to an ECU needs Web Serial, which desktop Chrome and Edge have. Logs and the library work in any browser.
- Which ECUs work?
- Speeduino, rusEFI, epicEFI and MegaSquirt, using their published INI files. Writing and burning are confirmed on Speeduino hardware.