code help...

**ericjon262** · 01-25-2014

Originally Posted by EagleMark

I still don't have the skills to be helping you. With luck some of the guys may have time, this is no short term project. Have you read a couple of threads in GearHead section on this subject when I did have time to get started? Lots of good info there.

somehow I missed this....

No, I hadn't, I'll take a look!

**ericjon262** · 02-02-2014

so I've been looking through the code bit by bit, very slowly as I try and make sense of what I'm looking at. and the one thing I can say for sure, is that the code is, for the most part, the same between many different years, makes, models, and even engine families. keep in mind, all of what I am looking at is late 90's, early 00's GM V6's.

so far, I've looked at the code for the

L67 (3800 supercharged 90* V6)
L36 (3800 n/a, 5 speed 90* V6)
LX5 (3.5 DOHC "shortstar" 90* V6)
LA1 (3.4 "3400 SFI 60* V6)

with the exception of the camaro L36 file, when opened in winOLS, each file was listed as 81% identical. after modifying the LX5 bin for a manual trans, it showed 87% similar to a stock LX5 bin, which leads me to believe most of the differences in the bins, are in the calibrations, and not in the actual OS.

**Caleditor** · 02-04-2014

Instead of sharing this information privately I will post it. It is probably not a good idea

Screw it
Hey find a copy of DHP PowerTuner or that free tuner. Open the program or download the latest dbf. This is a simple MS Access file.
In the file you will find a column of numbers from 1 through 30. The V6 cars have 30 different def files. I think you can find a reference for OS to the ID in that column. If you cannot I can pull it. I also have them linked to the VDF's that TC uses.
posting this could cause TT to encrypt the files.

**RobertISaar** · 02-04-2014

i doubt that they'll encrypt it.... the authors have essentially encouraged people to open it up and add/change stuff if necessary.

**ericjon262** · 02-07-2014

I can't speak for DHP, but tiny tuner source code is made available with the program, along with software to edit the database, I see no reason why they wouldn't want you to expand on it. I can get the osid easy enough, tiny tuner will display it on the program for you. most of these bin files were different OSID's, so I think the differences are very minor, but I haven't been able to see yet for sure, I'm still trying to figure out the exact differences. again, I think the overall big picture differences between the different files lies almost solely in the calibrations for each different engine.

I haven't had a stable internet connection over the past few days, I'll try and get the OSID and bin files posted here(may already be in the DL section), along with a disassembly.

Originally Posted by Caleditor

Instead of sharing this information privately I will post it. It is probably not a good idea

Screw it
Hey find a copy of DHP PowerTuner or that free tuner. Open the program or download the latest dbf. This is a simple MS Access file.
In the file you will find a column of numbers from 1 through 30. The V6 cars have 30 different def files. I think you can find a reference for OS to the ID in that column. If you cannot I can pull it. I also have them linked to the VDF's that TC uses.
posting this could cause TT to encrypt the files.

**Caleditor** · 02-07-2014

The guy that is updating TT told me that he did not want a bunch of hacked up copies floating around on the internet

**Caleditor** · 02-07-2014

List of supported OS's --- It took me a few attempt to post it

**ericjon262** · 02-10-2014

the osid is supported, I'm using tiny tuner software to edit the file already. I'm wanting to edit the actual os to expand the RPM ranges

also, FWIW, I don't think the tiny tuner database is correct for the OSID I'm working with, I could be wrong, because I don't really know 100% what I'm looking at, but some things just aren't matching up like I would expect. when I get my computer back, I'll post some info I've compiled that could prove helpful.