Scaling?

[F-127]

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?

[cleatus12r]

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.

[907DAVE]

What happens when you transpose two maps with different normalizers?

What are the Normalize All, and Autoscale All functions do?

[F-127]

Originally Posted by F-127

..... Looks like at 500 A/D it the stock shift was about 2.5 MPH lower, as you probably see. So whats that feel like, well if you were cruising along at 55MPH, you now only have to push down the throttle to 500 A/D to get a down shift when before you would have had to push the throttle to the 570ish range.
....

Pretty sure I screwed up in my explaination. The function shown was for the 3-4 shift, unrelated to a 4-3 downshift. The 2.5 MPH lower stock shift was right, but not the downshift part, maybe you already knew that.

Originally Posted by 907dave

What happens when you transpose two maps with different normalizers?

What are the Normalize All, and Autoscale All functions do?

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.

[cleatus12r]

Originally Posted by F-127

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.

Ding!! Ding!! Ding!!

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.

[907DAVE]

Originally Posted by F-127

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.

Seems like comparing files with different normalizers is useless. The first binary's normalizers take presidence over all others, which makes the second and third binary's values BS if the normalizers are changed.

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".

[cleatus12r]

Two separate projects.

[907DAVE]

Originally Posted by cleatus12r

Two separate projects.

yup...