Tuning the AEM Infinity, check out this helpful tool...

[David Borden]

There seems to be a reasonable interested in the AEM Infinity Stand Alone FI system here on Pelican so figured it was worth posting this.

A great friend of mine Trevor and I cut our teeth on the AEM Infinity system and have found it to be solid platform from both a hardware and software perspective.

One of the things that can a bit time consuming is logging the VE error and applying it to the VE table after a session. This is particularly true when trying to tune in part throttle fueling. The "NewVE" virtual channel works well and goes a long way to help, but you still have to step through the log and make changes one cell at a time.

From using HPTuners, I found the ability to build a table that duplicates the VE load and RPM axis/cells and have it generate a VE error table very useful. This table can then be applied to the existing VE table and correct the current error.. It's somewhat of a manually implemented autotune.

I wanted to figure out how to do the same thing with the AEM Infinity tuning software, but after several hours experimenting, it became apparent the Excel skills to pull it off were not in my toolbox.

When talking with Trevor about the idea, he volunteered to try his hand at it... Little did I know, he is a bit of a Excel guru!

After a few days of work building the formulas and tables etc, he had something for us to try… and it worked! Since then, he’s refined the formulas, added instructions, and some additional features. In addition, and we have tested it fairly well.

How it works...

Drive and log the required channels. Download your log into the AEMData software, export just the channels that are needed to CSV, then copy and paste that data into the spreadsheet.

A copy of the CSV data as its exported from AEMData.


The first page of the spreadsheet with instructions.


Same data from the export pasted into the spreadsheet.


The modified cells populated with the “NewVE” data. Before your data is useable, you need to specify whether your load is throttle or MAP based. You also need to make sure your breakpoints for both load and RPM matching your VE table exactly.


Simply copy the data from this table, and paste into your Actual VE table like so.


At this point, you want to look at the data and see if it all makes sense. You can even scrub through the log and verify the logs NewVE is matching what you copied in. Wash, rinse, repeat…

Does anyone have an interest in using this? If so, we can throw it up on a google drive for people to check out and use.

Let us know your thoughts.

David

[Pehlen]

I am vey interested. I have not gotten to this point yet in my project, but have been researching and reading about the tuning process and this tool fills a gap. I expect to be at a point to start tuning before the end of Jan and would be happy to be a Beta partner.

[jnberry]

Also interested!

[Knockdown]

My ITB project is a bit off into the future but would very much appreciate adding your spreadsheet to my library. Thanks for sharing!

[metalracer]

I'd have a real interest in this!

[acme911]

I'm interested. Thanks David

[tirwin]

I am hoping to go ITB/EFI and I've been looking at the AEM. This looks like a fantastic idea!

[al lkosmal]

nice David.............

regards,
al

[David Borden]

Ok guys, great to hear there is an interest in this! Try this link out to download the file. I will also copy a CSV template that you can use to make sure you export the correct channels to CSV. I'll get those up tonight or tomorrow morning.

https://drive.google.com/open?id=0B0GQlfZHOrn_bUZKNlF6VzVUVVU

Also, you need to make sure you are logging the needed channels. I would recommend that you know it is working from logging to importing into the spread sheet and getting back into the Infinity tuning software. Nothing more frustrating than going out and logging for an hour and find out you missed a channel required.

We may run into some areas that need some tweaking. After you download and take a look, please ask your questions in this thread so everyone will benefit from the dialog.

Looking forward to hearing what everyone thinks of it once its being used.

David

[David Borden]

Once you have logged your proper channels, you open your log file in AEM Data.

File > Export CSV. You should see a screen like this

Use these if you are using MAP for load


Use these if you use throttle for load


You want to uncheck select all/none so nothing is selected. You can verify by check "show exported only"

You can either find and check the channels needed in the image above, or load the CSV template that I will post in the same directory that was posted earlier.

What I need to figure out, is how we deal with the 2nd lambda channel which Im guessing most of you will not be using.

I'll check on this and let you know.

David

[Knockdown]

Got it, many thanks!!!

[Tippy]

Unless I'm missing something here, and I've been pretty heavily involved with reading pro tuner websites, I really appreciate the VEAnalyze Live! and MegaLogViewer from TunerStudio/MegaSquirt.

It does these functions for you.

[David Borden]

Originally Posted by Tippy

Unless I'm missing something here, and I've been pretty heavily involved with reading pro tuner websites, I really appreciate the VEAnalyze Live! and MegaLogViewer from TunerStudio/MegaSquirt.

It does these functions for you.

Tippy, do those tools work with AEM Infinity tuning software ECUs? Had no idea if so...

[Tippy]

Originally Posted by David Borden

Tippy, do those tools work with AEM Infinity tuning software ECUs? Had no idea if so...

Phil Tobin, the creator of TunerStudio has mentioned years ago, that if there was enough interest, he'd develop for any ECU platform.

[jpnovak]

Nicely done. This will certainly help the AEM community.

MegalogViewer should work with any csv file type to import the data. I use a modified CSV file to import GPS and accelerometer data along with the engine output from the Megasquirt ECU. The challenge will be that the imported tune file will have different memory allocation locations for direct VE value and target AFR. Basically, the MS software will be looking in the wrong spot for the tune information from AEM.

The system has a (simplified discussion) function to read the instantaneous AFR, compare this to the target AFR, determine if rich or lean, calculate how much rich or lean (ratio of AFR actual to AFR target) then read the amount of fuel delivered, and scale the existing fuel delivery by the magnitude of offset from target AFR.

In the Megasquirt community there is a real-time live version of this script and also a secondary, post-process version. I like the real time driving version when roughing in a VE table and then the post-process version to fine tune.

Phil Tobin (Author of MLV and TS software) can be found at efianalytics.com. He is easy to communicate with. Since you have the math done for the spreadsheet algorithm you might be closer than you think to having a version that works with AEM. It is worth talking to him about.

BTW, some of the analysis tools are why I prefer the MS systems.

[David Borden]

Thanks guys... all credit goes to my friend Trevor for this tool!

Im guessing most people will be running a single wide band channel on a 911. Trevor re-spun the XLS so that it will support a single channel and not require any tweaking of your Exported CSV data to make it work.

The new XLS and AEM Data templates are in the shared folder. I moved the folder on my google drive to better organize the data. If you cant access it, please let me know and I will get a new link posted asap.

Interesting about the TS stuff. Ive always been impressed with MS and its community of developers. It may make sense to ping him about it.

David

[Ipe]

Nice work David! Thanks for sharing.

[Pehlen]

I've been using this for the past week with some basic street tuning, and it's been a huge help for a novice. I'm currently using MAP x RPM, but am thinking about switching to TPS. Or... I've been reading up on a blended TPS/MAP x RPM. Any thoughts?


Sent from my iPad using Tapatalk

[David Borden]

Originally Posted by Pehlen

I've been using this for the past week with some basic street tuning, and it's been a huge help for a novice. I'm currently using MAP x RPM, but am thinking about switching to TPS. Or... I've been reading up on a blended TPS/MAP x RPM. Any thoughts?


Sent from my iPad using Tapatalk

Great to hear!! Re your question, what kind of Intake system are you running? If stock Intake, MAP is probably going to work fine for you. If you have ITB or big cams, TPS may be better for you.

One thing to keep in mind, if you choose to use TPS mode, the Infinity uses the TPS position for load, but still uses MAP for fueling calcs and baro/altitude changes. This may be why it works so well on this system.

Even though Im running a stock manifold on my Coyote, we chose to move to TPS based load and the car runs great and Trevor and I have no plans of going back to MAP.

David

[Pehlen]

Originally Posted by David Borden

Great to hear!! Re your question, what kind of Intake system are you running? If stock Intake, MAP is probably going to work fine for you. If you have ITB or big cams, TPS may be better for you.



One thing to keep in mind, if you choose to use TPS mode, the Infinity uses the TPS position for load, but still uses MAP for fueling calcs and baro/altitude changes. This may be why it works so well on this system.



Even though Im running a stock manifold on my Coyote, we chose to move to TPS based load and the car runs great and Trevor and I have no plans of going back to MAP.



David

I have ITBs and have already switched over to TPS for load on the VE table. With three tuning rounds under my belt today, I hope to arrive a a well tuned base MAP by mid week. I'll post more as that progresses.


Sent from my iPad using Tapatalk