we have to stay strong and
before I find time to fully explain everything take a look at this video Sir:
https://youtu.be/DBFn1RDa3eM?si=3Xha1i8Swh9_c8DI
The biggest "problem" is the ECU doesn't export target AFR as soon as it exits the closed loop, so approach as in video by HP academy is not possible
also MegaLogViewer HD is something that is great for pro users, and ones that can afford it.
I'm going to acquire it to speed up my work as a professional tuner.
seams that you can try it now for free (I don't know how much is "open" and how much it is useful in demo/free version)
So far I have been using a self made excel table which made me take car and be much more understanding of the work that is done.
1st
You need a high speed logger.
You have the Obd Link SX I assume or Versa Link (I hope you are not doing any ECU remapping with remote connection)
if you have the obd Link SX, get a usbA>usbC adapter to use it with your phone and install the OBD Link app. if you have an iphone, get an android
2nd
Prior to this you need to make your car run like "shit"
Ie, you need to make the car ready to be Logged.
1st table - clear the Closed loop enrichment table - make it all 0
set a AFR target table at the rich side (oem one is quite goodfor this purpose) but make it "smother"
now here you have two options, do once at all ore part in closed loop part in open loop:
2.1: - disable closed loop altogether, flash , record
ONLY #1, "2 and #5 from list in step 3. (which makes it faster) be careful and monitor the AFR as low load and high rpm is off on the ECU map (VE is underestimated, and engine gets way to lean).
2.2: - split the logging in to two areas. closed loop, open loop.. this is how I did it initially but I would argue it is much more complicated and more prone to errors in calculations.
3rd
You need to select several PID's to log (will check them all later and confirm if I used more than I have here listed) and this is irrespective of the table editor / visualizer you are going to use, but obviosly MegaLog will require slightly diferent setup.
- Engine speed - RPM
4th
drive, drive as much as you can in various loading conditions / rpm, but try to avoid fast transitions of load to avoid transient enrichment / leaning.
5th
when you obtain data, depending on the approach 2.1 or 2.2 you need to analyze the data.
in either case you need to setup the excel to group the data in to the RPM / Load table cells , in same format as it is in the Versa tune target. That will generate the "achieved AFR" table. this is THE MOST complicated step in the manual data analysis.
if you are doing it with 2.2 approach you have to in addition to this modified the archived AFR by the LTFT and STFT to show what would have been the achieved AFR if those corrections were not applied as you want to applied the correction to the VE so that the ECU doesn't need them (you will have them active, but wont need them)...
now when you have your achieved, you compare it to the target AFR table you copy from Versa, and you appli those corrections to the VE table..
repeat 4th and 5th step!
after the VE setup is finished, update the AFR target tables to the appropriate and enable closed loop. I would keep the closed loop enrichment table disabled and Enjoy
I am working and need to write down an additional step to recognize if it is the MAF calibration that is out of alignment and not the VE table. For that MAF would be to be logged and compare to the corrections, that would require different excursive on the target AFR data vs maf (which we dont have in "native" form)
afterthought,
Enabling Closed loop up to high load / high rpm but have to think what would be the implication with such.
PS, if you find this excessive, I can provide you with an e-tuner service and explanation why and how has been modified