robvas
Well-Known Member
- Thread starter
- #1
Here's some random questions, there's probably a better place to ask them (or maybe where they are already explained), so feel free to point me in the right direction.
If I use an SCT device and use it to download my stock tune file, the resulting file is a little bit over 6 megabytes.
But, if a tuner sends me a file, that I then load on the SCT device, that file is only about 1 megabyte. I assume that it's just patching over my original tune, so it doesn't need to be the full file.
Also, if I use HPTuners to pull my stock tune, the file is only about 1/10th of the size of the 'stock tune file' from the SCT, 563 kilobytes. I am assuming that's because the .hpt files are more of a 'configuration' file and not a full 'tune'? Does that make sense?
I understand that there are things you can get from an aftermarket tuner like a custom operating system, so I realize there's more to a 'tune' than just a bunch of tables. Is there compression involved?
Can anyone shed some light on what's what?
If I use an SCT device and use it to download my stock tune file, the resulting file is a little bit over 6 megabytes.
But, if a tuner sends me a file, that I then load on the SCT device, that file is only about 1 megabyte. I assume that it's just patching over my original tune, so it doesn't need to be the full file.
Also, if I use HPTuners to pull my stock tune, the file is only about 1/10th of the size of the 'stock tune file' from the SCT, 563 kilobytes. I am assuming that's because the .hpt files are more of a 'configuration' file and not a full 'tune'? Does that make sense?
I understand that there are things you can get from an aftermarket tuner like a custom operating system, so I realize there's more to a 'tune' than just a bunch of tables. Is there compression involved?
Can anyone shed some light on what's what?
Sponsored