![]() |
|
Minotaur Automotive Tuning Software Tune your own 7.3L Diesel! If you have a question or comment about Minotaur? Post it here. Also, check out our Facebook group: Facebook - Minotaur Tuners |
![]() |
|
Thread Tools | Display Modes |
|
#1
|
||||
|
||||
![]()
I actually asked about the inferred throttle map once before so I know exactly what your talking about there. Working with OBS auto? I haven't seen what your describing for the torque table map though. Usually you can tell what the axis units are if you view the numbers/spreadsheet view using F6. Here is where I asked about the inferred throttle once. I can't find the picture from my photobucket account so I just took another screenshot. Left is a stock, right was from a low HP tuned file for a stock truck. I think the right is the same for all tuned files.
![]()
__________________
Thomas H. '97 F-250 CCSB 7.3L Auto, Gauges, Modded H2E, 285/200% sticks, 7.3L IC, Stealth Dual HPOP, Pheonix chip '03 F-250 CCSB 6.0L Auto, Gryphon CTS, FICM tuning by PHP, Powermax |
#2
|
||||
|
||||
![]()
I had looked at mine to try and see what you were seeing GTS, but mine looks nothing like what Thomas had posted.
![]() That is odd. |
#3
|
|||
|
|||
![]()
Forgive me guys I'm not much of a computer wizard. Never really done much for screenshots so I'm not sure how to do that. But the graph Thomas posted is one that I am talking about. I'll try to figure out how to do a screenshot and post up the other graph in a bit.
|
#4
|
|||
|
|||
![]() |
#5
|
||||
|
||||
![]()
Wow, you OBS guys dont have much resolution on that map!
As for the shape, I could not tell ya. ![]() |
#6
|
||||
|
||||
![]()
That's not right.
Either the definition is corrupt or the binary is corrupt. If you PM me your email address, I will send a stock TDE1 binary to you to see if it's the problem or not.
__________________
Tuning, PCM flashing, and burning chips for 7.3s since 2008. Repairing all aspects of 7.3L Powerstrokes for 25 years. Eight 7.3L PSDs in the driveway including a 1994 Crown Vic and 1973 F100/2002 F350. Looking for the next victim. |
#7
|
||||
|
||||
![]()
Oh, and your inferred APP map is just going to be that way.
__________________
Tuning, PCM flashing, and burning chips for 7.3s since 2008. Repairing all aspects of 7.3L Powerstrokes for 25 years. Eight 7.3L PSDs in the driveway including a 1994 Crown Vic and 1973 F100/2002 F350. Looking for the next victim. |
#8
|
|||
|
|||
![]()
e-mail is gtsmotorsport@yahoo.com.
Thanks for the input. Do you have any explanation as to why the APP map is that way or is it just that it is what it is? If I smooth out that dip is it going to affect the other maps so I'll need to go make adjustments elsewhere as well. This brings up another question, If I make a change on one map that changes things on another map will those changes on the other map show up on the actual map. So if I move something on one map and have the other map that is affected as well pulled up side by side will I see the changes being made by the map I'm working on move things in the other affected map? Or are all the changes to the other map more or less behind the scenes Dave can you please explain a bit what you mean by not much resolution? You mean the increments aren't as fine as in the SD files you have? |
#9
|
||||
|
||||
![]() Quote:
![]() Quote:
Take care.
__________________
Bill Cohron - The Mad Doctor ![]() ![]() ![]() Power Hungry Performance - The ORIGINAL in Ford performance tuning... Since 1997! (678) 890-1110 www.gopowerhungry.com - Home of the Hydra Chip, Minotaur Tuning Software, and the new Orion Reflash System for Navistar! Bring back ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() ![]() Much to my surprise, I'm actually quite enjoying Linux! ![]() |
#10
|
|||
|
|||
![]()
Why do they make the entire map if they are only going to use the first 10 columns???
![]() The Defenition file I'm using is VCAB0_02(216e).mdf and the Bianary I'm using is the one you wrote me when you live tuned my truck. VCAB0_02-Version2\0002_1_224K.bin. I hope this helps figure out what's going on. |
![]() |
|
|