spikes in maps

[GTS]

So looking through some of the maps I see there are some spikes in some of the graphs that really make me wonder if they are supposed to be like that or not. I just don't get how you would be going smooth then all of a sudden max out a value then back to the previous curve in a couple hundred rpm. For example my Inferred Throttle Position map, the verticle incriments sem to represent Throttle A/D counts, the incriments on the bottom left appear to be engine RPM and the ones on the right bottom appear to be MFD. On the lowest MFD line if you follow it along the RPM side it curves upsomewhat gradually to peak at 1024 A/D counts at 2500 rpm then drops back down to almost 0 A/D counts up to about 3800 rpm then spikes back up to 1024 A/D counts.

On my torque table it appears that FT/LBS is the verticle axis, the lower right is RPM and I have no idea what the other is. Anyway right at 1400 rpm the tq drops to 0 along that whole lower left axis then spikes right back up again. I can't imagine why this would spike down like that at 1400rpm. Is this correct or should these be more of a smooth transition?

[Power Hungry]

Picture examples...

[F-127]

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.

[907DAVE]

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.

[GTS]

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.

[GTS]

OK I hope I did this right. If so the pic of the map should be below.

[907DAVE]

Wow, you OBS guys dont have much resolution on that map!

As for the shape, I could not tell ya.

[Power Hungry]

Originally Posted by F-127

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.

The spike in the middle of that map is obviously not supposed to be there. Hey, Ford's not perfect either. As to the definite ridge in the middle of the map, this is because the X-Axis transfer function for the map only addresses the first 10 columns and disregards the rest. This is where transfer functions can get tricky. You can actually correct the transfer function to address the full scale of the map and provide greater resolution, but you just need to be really careful or you can cause all sorts of oddities. For the most part (on this map at least) there really isn't any advantage in expanding the resolution so there no reason to even bother.

Originally Posted by GTS

OK I hope I did this right. If so the pic of the map should be below.

The map in this example is not addressed correctly so the start of the map is shifted. This could be due to a problem with the binary file, the definition file, or a mismatched binary/definition combination. I see this when using a VDAB0 file with a VCAB0 definition, and vice-versa. If you could let me know what binary and definition file you're using, we can clear that up for you.

Take care.