3.0 is done
 

I am using TPS mode on the 3.0 i just tuned....works great. This one is done and runs great.



regards,
ahttp://forums.pelicanparts.com/uploa...1485140479.JPG

Bringing this to the top in case it may help another AEM Infinity user.

David

I just downloaded this and looking forward to finding some time to learn and apply.

Anyone have any new info they would like to share since using this?

Thx

Yes... I suck at excel.

This is an impressive tool, but to work well, your car needs to be in a steady state. In other words, you need to filter out all transients. In my opinion, the best tool to do this is Megalogviewer. You can set filters to remove transient conditions. You can even filter out data from when the engine is cold and not appropriate for developing a VE table. It also produces tables which you can copy/paste into the infinity software plus you can do much much more.

When using a usb drive to datalog, does the laptop still need to be inside the car running infinity tuner at the same time?

No need to have the laptop inside to log via usb, but you have to set what parameters you want to log and what is the log start criteria. After you are done running and want to get the data, then you connect the laptop to download the log from the usb to your computer. In other words, you can’t just plug the usb to the laptop and copy the data.

Also, if you log via the laptop, the parameters logged are those for which you show data on any of the tabs. For example. If you don’t have a table, graph or value displayed, and record data but then want to see that value by modifying the layout to include the value, it will show that the data was not recorded.

OK, thanks, I managed to do this.. and recorded a log on my way home from work. I stalled the car twice, so I ended up with 3 small files.
In order to use the spreadsheet, which fields should I be logging?

Have you figured out a way to use Megalogviewer with the AEM Infinity system?

Re tuning on the street using this tool, its actually quite easy to do. Yes, you do need to be smooth, but if you have it setup with a switch to turn the logging on and off, you simply switch it on, drive smoothly in various load ranges and RPMs and then switch it off for each logging session.

We have tuned several cars on the street this way(with no dyno tuning) and have gotten very solid VE maps using it. It makes tuning the Infinity significantly easier than manually doing it. Clearly if you have a load based dyno things become easier with our without the tool.

Do you mean, you can set it up so that a switch in the car, triggers logging to start and stop? Being a PC noob, I kinda wish there was a video tutorial on how to use AEM data, logging with a switch, and then using the spreadsheet....

Yes. You can use Megalogviewer to analyze data from the infinity and really for general data visualization even unrelated to automotive work. It is surprisingly fast handling massive amounts of data. I have no connection to it but was impressed when I used it.

In summary, you collect the data with the infinity software. Then load into AEMdata which allows you to export whichever parameters you recorded as a csv file. Then Megalogviwer can open it and voila, you can analyze your data and get VE tables you can copy/paste. Whether you use MAP or TPS you can still generate a VE. You can even convert from MAP to TPS if you already have one diales in. The ability to create various filters allows you to drive around and automatically remove transients.

Now, if only you could autotune with it like you can with the megasquirt...that would be fantastic.

I'm having trouble using the spreadsheet. Here is the latest log I took. Maybe someone could have a look for me and run the numbers?

https://drive.google.com/open?id=1fEy0BBFlfvRD_ibsPzM5XQNuWJGWwE-J

Mike, I analyzed your data with Megalogviewer and calculated a NewVE based on your data. You will only see values for which there was data. The color code is weighted to number of samples. The light colors have fewer data samples. I plotted TPS vs RPM because that is the strategy you are using. I also matched your values in the X and Y axis (one extraneous column in the RPM can be ignored). I applied two filters: one removes values where there is wall wetting and the other removes values where the lambda is very high, as I see you used fuel cut. Out of a total of 14,044 data points, 7,895 were filtered out. If I used other filters, you lose more data. Here is where it is important to try to hold steady state values whenever possible.

Here is the screen shot. If you can't read it, I can try emailing an Infinity file which you can import.


http://forums.pelicanparts.com/uploa...1548650513.png

This one shows the difference between NewVE and VE to show you how close or how far you are in the values that were analyzed.

http://forums.pelicanparts.com/uploa...1548650632.png

Wow, thank you for going to that trouble. How long does it take? For some reason, I struggle using the software...

I might alter my VE map now, and do some more logging.

When you say, "try to hold steady state values" do you mean to try to drive logging particular cells at a time to?
The other night, I would drive with my throttle around say 30%, and then let it rev right out through the rest of the rpm range, to try to hit all the cells in that row.

No problem. It took me about an hour because I had to understand your data, your y-axis for VE, see what you logged, etc. Now that it is set, probably 15 minutes.

If you take out fuel cut, you can adjust other areas of your VE table.

By holding steady state, what I mean is you want to have slowly varying changes values. You want many measurements at each value of the table to increase the accuracy of the value. The way I do it is go to an expressway with a high speed limit. To log high rpms I use lower gears and accelerate slowly. There are speeds where you can hold the rpm at a certain value and keep it there. I also go to high gear to log higher Throttle values. WOT can be done in high gear until you are driving too fast.

You can stab the throttle to different values but then hold it steady and let the other parameters creep up. If you want you can email me to iterate on your logs.

The values I use are coolant Temp, engine speed, engine speed rate, map, primaryInjDuty, SpkTiming, throttle, throttle rateVE, wall wetting, wall wetting2, lambda and lambda target. You actually need a subset of these bit those are the ones I export.

For you twin pluggers, how much timing at 80-100% open throttle are you dialing in by 2500-3k rpm ish? And at 30-40% cruise? I'm around 31 degrees with light throttle openings and cruise in that rpm range and 24-25 degrees at 80% and above but some tuners have advised they dial in all WOT timing as soon as 2500rpm on a higher compression twin plug motor, some 26-27 degrees.

Well, thanks for reawakening my tuning addiction. I could, and will, lose days inspecting the scatter graphs. My MAP*RPM vs InjDutyCycle is bizarrely shaped. And I thought I had a great tune on.


Sent from my iPad using Tapatalk

I bought Megalogviewer HD... here is a video showing how I used AEM data, and megalog viewer HD to create a new VE table.... am I doing it right??

https://www.youtube.com/edit?o=U&video_id=-ckhtqY9pV8

Anyone here able/willing to walk me through how to create a filter? If it requires being able to write a formula in a separate language, like writing formulas in excel, then I definately need help!