Calc.VET: correcting MAF and calculating VE (in single log)

[ippielb]

Great tutorial, helped me a lot once i downloaded the PDF and put it in a binder for easy access!

[WeathermanShawn]

Thanks for the compliment. We appreciate it.

For those who want more detailed/advanced information on Tuning via CALC.VET, we have started a page of 'Summary Notes'. Its all preliminary work, but it gives some data on how to blend your MAF and VE Table, along with some other tips..http://forum.efilive.com/showthread....-Summary-Notes

Again, just preliminary notes we are working on..

[WeathermanShawn]

Joecar has come up with an idea to 'reverse' the CALC.VET Equation(s) to solve for MAF Airflow. I think it is a great idea. If there is enough interest we will start another thread.

Here is a brief introduction of the concept..

CALC.VET has been a huge success. One can calculate the VE Table, MAF, and Trims all in one log (simultaneously). However, AUTOVE is still hugely popular. There are some users who have a perfectly tuned VE Table, but who may desire to re-enable the MAF. Previously AUTOMAF has been the only method (unofficially) to calibrate the MAF after AUTOVE.

Now we believe we can take a VE Table and reverse the equation to solve for the MAF Airflow. So AUTOVE users now have a way to calibrate the MAF in the same log.

This may interest some Tuners. We will let you know, probably by starting a new thread shortly..

..Thanks..

[Mr. P.]

...CALC.VET has been a huge success...

Yes it has; however it requires a MAF (not a bad thing!) but is there any of this process/thinking we SD guys can leverage?

Mr. P.

[WeathermanShawn]

Yea, the MAF thing....

Originally it was designed for 'Beginners'..hence the MAF.

Well I didn't want to mention it, but..in reality you can apply a number of CALC.VET concepts to 'straight' Open-loop Tuning or pure SD Tuning.

The nature of SELBENS can be utilized whether doing MAF only, SD only, closed-loop, open loop or a combination of any/all. The easiest parallel would be SDCL. Disable the MAF, and use LTFT and WO2BENS using MAP and RPM as your MAP axis. You would just have to reconfigure the calc_pids.txt file to eliminate some of the Pids.

The reason I have not wanted to introduce all of the possible combinations was quite simply anticipating 'workload' and interest. I do all the Tutorials in my spare time and I hate to do anything half-a.. So, I was waiting until someone showed some interest.

But to answer your question..in reality you do not need a MAF to utilize simultaneous closed & open loop SD tuning. But, it might be nice to have a corresponding MAF airflow. You never know when you or a potential customer might want to go back to the MAF.

Let me know. I can always work something up..

P.S. Attachment shows both LTFTBEN and WO2BEN (AFR/EQ). This was all done in one simple log. So you would apply that BEN to your existing VE Table..and you could easily calculate a corresponding MAF Airflow (just in case)..

[Mr. P.]

Thanks Shawn - yeah I'm definitely interested; I'll digest what you've shared here, I'm still "absorbing". :thumbs:

Mr. P.

[WeathermanShawn]

Mr.P..

Let me think it over (presentation). I'll need to confer with Joecar as far as the calc_pids.txt and a few other issues.

1. If you are doing a pure Open-Loop SD Tune, this method would also calculate a corresponding MAF Airflow vs MAF Frequency. That may or may not be of use to a Tuner.

2. You can however do a simultaneous Closed-Loop SD Tune in combination with a wideband. So in one log you can Tune a VE Table using Trims and actual wideband data. And you could also have a corresponding MAF airflow if you desire.

We will get back to you..

[joecar]

Yes, we want to make the calc_pids.txt file as easy as possible.

[Mr. P.]

...You can however do a simultaneous Closed-Loop SD Tune in combination with a wideband...

Well this is the situation I am personally in. I understand it's unfeasible to go through the effort of crafting a tutorial process covering each conceivable hardware setup, BUT I offer that there are lots of fellas like me using COS-3 in CLSD, especially in the Gen-III truck crowd where it is now more common than not to add a significant power adder and drop the MAF sensor in the process; my point to you being, everyone who spends the dollars and time to run COS-3 should also have a functioning wideband especially when you can get a really good one for under $300 now - I would not even entertain attempting to explain to anyone how to "dial-in" a tune without a wideband, it's accepted best-practice.

...make the calc_pids.txt file as easy as possible.

Understood - not all of us are software developers!

Well I'm seriously game to working on this with you, including testing on my vehicle as well as assisting with dev work and adding documentation; lemme know.

Mr. P.

[WeathermanShawn]

O.K. we will work something up.

Luckily have been thinking about the CLSD for a while, so I think we can get something going. Joecar's brainstorm on solving for the MAF Airflow equivalent is quite an important breakthrough. While I have seen other methods that attempt to 'convert' DYNAIR to CYLAIR, none use the DYNAIRTMP.DMA Pid or concept.

The actual R&D of this method may not be as exhaustive as the MAF-Enabled concept. Its always good to fail the MAF, try it out in both Open and Closed-Loop. Then compare those results to a MAF-only Tune. They should match.

But new ideas and concepts are always exciting. And the SD crowd has not had any new Tuning methods of late.

Look for something in the next few days. Thanks for your interest..