Scaling?

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

[GTS]

OK so I'm just starting on all this tuning stuff and I get what some of the stuff is you guys are talking about but what are the "normalizers" you're all talking about? And what is "Scaling". Is scaling a way to change the min/max values and it scales the curve to those new values? Or is it just a way of smoothing out a section of the map? Or???

[Power Hungry]

Each 3D map has an X and Y axis that control the how the map is tracked. Each X and Y axis have an associated "normalizer" that determine how that axis breaks down and what the separation is between each point on the map. This is an extremely powerful tool as it provides the ability to rescale any map to provide more or less resolution in specific areas or even make the map completely linear. It's this capability that has made the EEC processors (and its successors) very flexible and powerful.

I may need to do some sort of a "webinar" in order to cover some of these topics. I'll set up a schedule after the first of the year and see what topics we can cover.

[GTS]

Thanks for the explanation Bill. I think I get what you're saying. Just not sure how it applies. I guess I need to just get into the files and start messing with them to see what happens. I've just been trying to do a bunch of reading up on here before I go start changing a bunch of stuff.

[jystorey]

Originally Posted by Power Hungry

Each 3D map has an X and Y axis that control the how the map is tracked. Each X and Y axis have an associated "normalizer" that determine how that axis breaks down and what the separation is between each point on the map. This is an extremely powerful tool as it provides the ability to rescale any map to provide more or less resolution in specific areas or even make the map completely linear. It's this capability that has made the EEC processors (and its successors) very flexible and powerful.

I may need to do some sort of a "webinar" in order to cover some of these topics. I'll set up a schedule after the first of the year and see what topics we can cover.

I was re-reading through some older posts trying to find info about normalizers. I came across this post. Is there some info about this subject somewhere I can get to.
If not how do I find out which normalizers go with which maps?