Difference between revisions of "Open Source Tuning"
(Created page with "= What is it = Open source tuning is, generally, the use of openly available tools to tune a car. Some would argue that you can even consider it open source tuning if you're...") |
|||
Line 16: | Line 16: | ||
#The ability to flash files to the ECU | #The ability to flash files to the ECU | ||
##Using some commercially provided solution | ##Using some commercially provided solution | ||
− | ##Using some open source solution like @bri3d's [[https://github.com/bri3d/VW_Flash | + | ##Using some open source solution like @bri3d's [[https://github.com/bri3d/VW_Flash VW_FLASH]] |
#The ability to edit the calibration | #The ability to edit the calibration | ||
##Using software like RomRaider or TunerPro AND | ##Using software like RomRaider or TunerPro AND | ||
− | ##definitions files for the calibration (which point to where tables/maps/values are located in the raw bin) [[https://github.com/joeFischetti/SimosDefinitions | + | ##definitions files for the calibration (which point to where tables/maps/values are located in the raw bin) [[https://github.com/joeFischetti/SimosDefinitions Simos Definitions]] |
Definitions by and large are built by other enthusiasts that have taken the time to locate the maps. There are *factory* definitions files (called A2L) that provide everything, but those will only be used with other commercial software. They're also not openly available. | Definitions by and large are built by other enthusiasts that have taken the time to locate the maps. There are *factory* definitions files (called A2L) that provide everything, but those will only be used with other commercial software. They're also not openly available. | ||
− | |||
= Why should I open source tune? = | = Why should I open source tune? = |
Revision as of 22:37, 3 January 2021
Contents
What is it
Open source tuning is, generally, the use of openly available tools to tune a car. Some would argue that you can even consider it open source tuning if you're using commercial tools since we're all relying on openly shared information.
Who is it for
How does it work
The process follows along with the overview provided in other pages on here. To recap:
- Flash an application software to your ECU that allows for modified blocks
- Edit the calibration
- Flash the modified calibration
- Log the modifications and see what changed
In the case of open source tuning we really need to rely on two things:
- The ability to flash files to the ECU
- Using some commercially provided solution
- Using some open source solution like @bri3d's [VW_FLASH]
- The ability to edit the calibration
- Using software like RomRaider or TunerPro AND
- definitions files for the calibration (which point to where tables/maps/values are located in the raw bin) [Simos Definitions]
Definitions by and large are built by other enthusiasts that have taken the time to locate the maps. There are *factory* definitions files (called A2L) that provide everything, but those will only be used with other commercial software. They're also not openly available.
Why should I open source tune?
Nobody can tell you why you should or shouldn't.... but in general:
- You'll learn more about your car/engine and how things work
- You'll feel better about the changes that you've made because you can learn how to optimize them
- You won't have anybody to point a finger at when something breaks
- You can make the community better by learning and sharing
What are the risks?
Total ECU brick and or broken hardware. Nobody guarantees anything.
How can I contribute
If you want to help contribute to the open source project, start by getting acquainted with the process. Check out the github repos for the flasher tool and the definitions. And reach out to webmaster@simoswiki.com