Segment Swap utility
Re: Segment Swap utility
0.15.36
Minimal change to TableSeek return values (inform if no config is available)
XDF Templates for V6
Minimal change to TableSeek return values (inform if no config is available)
XDF Templates for V6
Re: Segment Swap utility
Tested the v6 xdf export and looks really nice. I am having troubles with the v6 checksum plugin. On older version of tunerpro it crashes on stratup. On latest xp version it throughs an error when I try saving bin. The checksum module is also not visible in the edtor.
Not sure if it is tunerpro problem or plugin issue. I am still getting some vcruntime140D.dll not found, which is really weird.
Not sure if it is tunerpro problem or plugin issue. I am still getting some vcruntime140D.dll not found, which is really weird.
Re: Segment Swap utility
D = Debug.kur4o wrote:Tested the v6 xdf export and looks really nice. I am having troubles with the v6 checksum plugin. On older version of tunerpro it crashes on stratup. On latest xp version it throughs an error when I try saving bin. The checksum module is also not visible in the edtor.
Not sure if it is tunerpro problem or plugin issue. I am still getting some vcruntime140D.dll not found, which is really weird.
Sorry, uploaded wrong file.
0.1-1 is compiled without debug, should work better.
Re: Segment Swap utility
I tested some random bins, and it worked great. Awesome.
Confirmed the checksums updated by tunerpro and it matches perfectly.
Snce we already have the maf and ve table address hardcoded in the v-6 info, might add that to xdf export.
Confirmed the checksums updated by tunerpro and it matches perfectly.
Snce we already have the maf and ve table address hardcoded in the v-6 info, might add that to xdf export.
Re: Segment Swap utility
Do you know other parameters for tables?kur4o wrote:I tested some random bins, and it worked great. Awesome.
Confirmed the checksums updated by tunerpro and it matches perfectly.
Snce we already have the maf and ve table address hardcoded in the v-6 info, might add that to xdf export.
rows, columns, byte/word/dword, signed/unsigned ?
Re: Segment Swap utility
It should be very similar math to ls1 bins, but I will take a look. For ve table rows are ripped form the bin, not sure on the columns count.
EDIT:
We can borrow some info from tinytuner source code.
It have all the needed data.
It will be awesome to generate some xdf template from it, minus the table address.
EDIT:
We can borrow some info from tinytuner source code.
It have all the needed data.
It will be awesome to generate some xdf template from it, minus the table address.
- Attachments
-
- Class1.rar
- (192.47 KiB) Downloaded 139 times
Re: Segment Swap utility
Some info extracted from tinytuner
VE 15 rows
VE 15 rows
VE 13 rowsTable_Information(0, 38) = "NO"
Table_Information(1, 38) = "Volumetric Efficiency"
Table_Information(2, 38) = "6F334"
Table_Information(3, 38) = "2"
Table_Information(4, 38) = "0.0002441406"
Table_Information(5, 38) = "Multiplier"
Table_Information(6, 38) = "17"
Table_Information(7, 38) = "15"
Table_Information(10, 38) = "NO"
Table_Information(12, 38) = "0,400,800,1200,1600,2000,2400,2800,3200,3600,4000,4400,4800,5200,5600,6000,6400,6800"
Table_Information(13, 38) = "0,10,20,30,40,50,60,70,80,90,100,110,120,130,140,150"
Table_Information(14, 38) = "Fuel"
Table_Information(15, 38) = "MAF"
MAFTable_Information(0, 53) = "NO"
Table_Information(1, 53) = "Volumetric Efficiency"
Table_Information(2, 53) = "705A8"
Table_Information(3, 53) = "2"
Table_Information(4, 53) = "0.0002441406"
Table_Information(5, 53) = "Multiplier"
Table_Information(6, 53) = "17"
Table_Information(7, 53) = "13"
Table_Information(10, 53) = "NO"
Table_Information(12, 53) = "0,400,800,1200,1600,2000,2400,2800,3200,3600,4000,4400,4800,5200,5600,6000,6400,6800"
Table_Information(13, 53) = "20,30,40,50,60,70,80,90,100,110,120,130,140,150"
Table_Information(14, 53) = "Fuel"
Table_Information(15, 53) = "MAF"
LegendTable_Information(0, 44) = "NO"
Table_Information(1, 44) = "MAF Table - Airflow vs Frequency"
Table_Information(2, 44) = "704BA"
Table_Information(3, 44) = "2"
Table_Information(4, 44) = "0.0078125"
Table_Information(5, 44) = "GPS"
Table_Information(6, 44) = "1"
Table_Information(7, 44) = "81"
Table_Information(10, 44) = "NO"
Table_Information(13, 44) = "1500,by,125"
Table_Information(14, 44) = "Fuel"
Table_Information(15, 44) = "MAF"
'DisplayWholeNumbers = 0
'Table_Name = 1
'Start_Position = 2
'Element_Size = 3 [Value size-byte count 1,2,4]
'Factor = 4 [scaling]
'Units = 5
'Column_Count = 6
'Row_Count = 7
'Row_Header_Step = 8
'Row_Header_Start = 9
'AllowNegative = 10 [Signed/not signed]
'Table_Description = 11
'Table_Column_Headers = 12
'Table_Row_Headers = 13
'Main_Category = 14
'Sub_Category = 15
Re: Segment Swap utility
0.15.37
V6 VE & MAF tables to TableSeek
Fixed bug in xdf export, tables with row/col count reading from bin was not exported correctly.
V6 VE & MAF tables to TableSeek
Fixed bug in xdf export, tables with row/col count reading from bin was not exported correctly.
Re: Segment Swap utility
0.15.39
TinyTuner DB reader in TableSeek tab, for V6 files.
TinyTuner DB reader in TableSeek tab, for V6 files.
Re: Segment Swap utility
Great work.
Some bugs in the new v6 features.
Sometimes the ve and maf tables are defaulted to 000440 for some reason. On some bins the bug shows on others not. Some of the imported tables also shows that 440 for address.
Hitting the load db button accumulates tables in the list and some confusion can happen if you hit it multiple times.
The ve and maf can benefit for different settings. Both unsigned, Maf 4 decimal points, Ve 6 decimal points.
There is some precompiled databases of tiny tuner. You can take a look at them and see if they can be used or, are of similar format.
I have some special request for compare different Os from the same xml.
For example compare 2 different OS from ls1 files.
Make a force compare checkbox that will ungrey the segment checkboxes ON different p/ns, and compare if they are of the same size.
Some bugs in the new v6 features.
Sometimes the ve and maf tables are defaulted to 000440 for some reason. On some bins the bug shows on others not. Some of the imported tables also shows that 440 for address.
Hitting the load db button accumulates tables in the list and some confusion can happen if you hit it multiple times.
The ve and maf can benefit for different settings. Both unsigned, Maf 4 decimal points, Ve 6 decimal points.
There is some precompiled databases of tiny tuner. You can take a look at them and see if they can be used or, are of similar format.
I have some special request for compare different Os from the same xml.
For example compare 2 different OS from ls1 files.
Make a force compare checkbox that will ungrey the segment checkboxes ON different p/ns, and compare if they are of the same size.
- Attachments
-
- Active_TTDB_09-20-13.rar
- (392.44 KiB) Downloaded 152 times