View raw and manually adjust microbits per second

[chevyeater]

I don't know why the decision was made to delete these excellent features from the new software but, can we have them back please?

[Mello]

I complained about this on the first public test releases of Tuner.  This was while Samy was doing the programming.
All AEM did was remove the post.

I very much prefer AEMPro over Tuner for tuning cars.  When you're needing to get a car up and running AEMPro is much faster to use.  So far Tuner does not have any new features over AEMPro and Tuner has to much visually garbage cluttering up the interface.  This is besides the fact that AEM is removing access to need option setting.

Reminds me of Microsoft's most recent Vista mistake.  Microsoft had to open up a feedback page on their forum asking users to tell them why Vista was such garbage.  They were already told but wouldn't listen.  Now their bring us Windows 7 which is suppose to correct all these goofs.  Oh well, at least Vista made them more revenues at the cost of hurting Windows name.  Look at all the advertisements they made trying to push their product.

I suppose we now have AEM "mojave" Tuner.  Looks like AEM is trying to protect me from myself.  They must know what I what better than I with their "full programmable" EMS.  Not so "full programmable" with Tuner, now is it?

I guess the bottom line is AEM is trying to make their EMS's user safe so they can market product to people who are not qualified to have it.  And we know there are a lot of people with these that are way over their heads.

[chevyeater]

Yeah, it seems the general consensus was that if you take 20 random cars that are AEM EMS equipped, 15 of them will run like **** because of poor tuning so, we must have to make this easier to tune next time. Let's take away anything complicated and replace it with a big glossy pictograph to make everyone happy.

I'd be extatic if AEMPro worked on the series 2 EMS.

[NS]

http://forum.aempower.com/forum/index.php/topic,19845.0.html

[SB]

Thanks for the feedback.

I don't think anyone woke up one morning and said "hey let's make interface software that will make life difficult for some of our best customers."  I'm pretty sure the thought process was more along the lines of "why on earth does anyone need to know that the fuel map scaling is 0-255 unless it's not being used effectively? What if we decide to change it someday to use more bits, should tuners have to know that 255 is max for some boxes but for other boxes the scale might go higher and 255 isn't even half of the max value?"  


I think the concensus here at AEM is there are only a few reasons to know microsec/bit existed in the first place... it's not so much a feature as it is a limitation. People who've been using AEMPro for years know that you adjust microsec/bit or select "rescale fuel map" to avoid flattening out the top of the fuel map and not being able to increase the pulsewidth beyond whatever the current microsec/bit setting would allow (or to increase the resolution at the lower end of the fuel map). The AEMTuner software does this for you automatically... whenever you change the min or max value in the fuel map (or the Crank Injector time table) it will check to see if the results of your change will cause the raw fuel values to go above (max acceptable) or below [i/](min acceptable)[/i]. If your change could cause the raw values in either table to exceed the limits, AEMTuner re-scales the microsec/bit and fuel map and Crank Injector time table for you... just like an experienced tuner would.


If you want to get a feel for what the raw values are, the scaling of the maps should show that, both in the 3D graphical and 2D table views. Open Tools>>Preferences  (or press CTRL+P... or whatever other hotkey you may have assigned this to).  In the Display Preferences, there is a checkbox for Auto Size Y-Axis... when this is un-checked the 3D graph y-axis will use the 0-255 scale and that should be an easy way to get a feel for what the raw values look like. Additionally, the color of the 2D fuel map cells is decided based on the raw values.

If you feel you absolutely need to see microseconds/bit there are a few hidden tabs in the default workspace supplied with the current version of AEMTuner... poke around and you should be able to find it (right-click any tab and select Show Hidden Tabs).  You can view and adjust microsec/bit as well as a few other options that weren't included in the standard menus... you can play with the TPS-Based Fuel Map option, speed density or MAF fuel strategies while you're in there.

[HamsMKIV]

I think the frustration, personally speaking, is that the AEMTuner is forcing the guys who have been using AEMPro for years to learn a new software. I realize there is a learning curve for the new features of the Gen.2 ECU; it just adds a new dimension when we have to learn the new software suite too.

- Chris

[chevyeater]

The new way is simply worse than the old way. If I view raw, I can quickly see every change that I make. In pulse width or duty cycle modes, those changes do not even show up half of the time. Almost all of the cars I tune have huge injectors and very small fuel demand at low speeds (that the owners expect them to not only run cleanly thru but get excellent fuel economy in).

Blindfolding me to the changes I need to make just makes my job harder, because someone couldn't figure out how to properly scale thier fuel map with AEMPro...  

I did find how to change microbits per second (ah the joy of navigating the new software) but, that was more minor than not being able to view raw in the numerical view of the main fuel map. I also dug around and found the significant digits setting for the tables. This clutters the crap out of most other tables so I can see changes in the fuel map. GRRRR....

[tastyratz]

I can see both points of view.
I think viewing raw is something people want... so let em have it.
We have had to adapt and make adjustments when firmware changed before, and this is a totally new software package.
If the scaler gets updated beyond 255 (would be nice) then post a revision note and we can figure it out. Balance could be leaving the behind the scenes advanced options available through sub menu's/options while not putting it on the forefront for people who arent specifically looking for it.

[JR]

Due to popular demand we will be adding in an option to disable automatic rescaling and we will make raw a map display option again like in AEMPro. Expect it within a week or so.

 

[chevyeater]

Thanks JR!

[SB]

FYI, the latest version of AEMTuner software now allows users to do the following things:

Disable fuel map auto-rescaling (go to Tools>>Preferences),
Rescale the fuel map manually (right-click on the fuel map, select Rescale Fuel Map),
Choose to rescale when the engine is running, and select 'do not show this warning again.'
view raw fuel units (right-click on the fuel map, select Fuel Units)
and view or adjust the microsec/bit option.


Thanks for bringing these things to our attention. If there are other things that you feel would make AEMTuner quicker, easier to use, more intuitive, or just plain better please continue to let us know.

[Mello]

Thanks.  I really find these, and the ability to use them, very helpful during my initial start up & rough tuning phase of just getting to where things will idle and limp around without stalling.

Next request I have, when your time permits, is getting AEMTuner so it supports the Gen 1 boxes as well.  Currently AEMPro & AEMTuner are basically functionally equal.  As AEMTuner evolves and things are added (like map tracing, etc.) I would like to be able to use it with Gen 1 boxes too.

 

[jonbar87]

I copied and pasted this from mellow's post (thanks mellow) and think it would be a great idea if this was possible. This is what he said:

"After I get my fuel map roughed in enough to drive around I setup O2 feedback and log fuel pulse, load, engine speed.  Next I find the fuel pulse that O2 feedback corrected to and paste this value into each appropriate cell of my fuel map.  Pretty quick and easy to do because O2 feedback is showing the pulse widths for the target AFR's, requires no math.

I would really like to see something similar that is automatic in the software.  Simplest way I've found to do fuel tuning."

Basically it would work like automapping only it would be accomplished while in O2 feedback mode. I really hope to see this in AEMTuner for the 1st gen units.