![]() |
|
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
|
||||
|
||||
![]()
Opps, my mistake, I also forgot to mention the files I was looking at, it was a DAC3/VOAA7P6(dad's pickup). Looking at those parameters the Max MFD is 100. Just seems to go against my thinking of one X input and one Y input with multiple Z values being a problem, I'm guessing the PCM has someway of picking, just don't know how. I'll likely just try setting the normalizer like normal before I re-burn that chip, maybe even have it both ways and see if there's a difference.
![]() So out of my curiosity I checked the files for my pickup, MLE1, and that shows a Mass fuel minimum of 80 and a max of 100. Does the minimum come into play or not?
__________________
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
|
||||
|
||||
![]()
That's something I don't know, Thomas.
You're right though about the DAC3/VOAA7 definition. I have that one in my Sniper stuff and it mimics the MFD map you posted. However, with my Minotaur, I use VXY2/VKAE3 and it is already "properly scaled" from the factory. That's why your screenshot had me puzzled.....I've never really looked at DAC3.
__________________
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. |
#3
|
||||
|
||||
![]()
What happens when you transpose two maps with different normalizers?
What are the Normalize All, and Autoscale All functions do? |
#4
|
||||
|
||||
![]() Quote:
From what I've tried, if you copy a map it will only copy the values. If the normalizers are different, I've found myself bringing up the normalizers and doing a "select all, copy, and paste" for the x and y normalizer. And if you load a second file up, looks like it will take the x and y normalizers from the first file. The other questions I don't know, and I still don't after tryin to monkeyin around with them.
__________________
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 |
#5
|
||||
|
||||
![]() Quote:
Depending on the disparity of the map values as far as the normalizers go, you can end up with some pretty fishy stuff. Remember this? http://forum.gopowerhungry.com/21935-post11.html It will actually work out to the computer thinking WFO at 585 A/D counts. Hang on!!! Some maps aren't as sensitive to changes and will go unnoticed if the map values are transposed without fixing the normalizers.
__________________
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. |
#6
|
||||
|
||||
![]() Quote:
Change the normalizers to make them the same, now values are not represented right. This is aggravating because I see no way to make different files "comparable". |
#7
|
||||
|
||||
![]()
Two separate projects.
__________________
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
|
||||
|
||||
![]() |
![]() |
|
|