Yes, but is it accurate for your location?Didn't we have me set baro to 30?
According to online its 29.73Yes, but is it accurate for your location?
Also, that’s temporary until you get the inferred model working right. The isolated mapped points and disabled etc pid feedback loop are also temporary.
I was just checking.Is it on? I think I just have baro set to 30
Looked pretty close to me. Get rid of the cam and IMRC channels. If you haven't already, set the resolution to the highest setting on the air PID's.looks way off still.
Have you tried setting the air charge multiplier table to the maximum air load you are seeing in that MAP? This is for making MAF and desired MAF line up. It may have an effect on the TP MAP estimate and calculated MAP lining up as well.Here is with corrected data. Log and tune attached, looks way off still.
The patterns based on RPM you can quickly see calculated MAP vs Estimated MAP with this is good. MP 19 corrected calculated MAP(left) vs Estimated MAP(right), eliminating points from lower RPMS going to higher RPMS.Here is an updated version that includes a graph (graph requires internet for external API):
https://www.mustang6g.com/forums/threads/tdstuart-tuning-adventure.201824/post-4073334What is this auto SD calculator you guys are using? Something murf made?
Ill try this and report back. I was just comparing the MAP vs TB Estimated MAP.Have you tried setting the air charge multiplier table to the maximum air load you are seeing in that MAP? This is for making MAF and desired MAF line up. It may have an effect on the TP MAP estimate and calculated MAP lining up as well.
I believe the maximum load at WOT tables are the ones that don't do anything, but I get which is which mixed up all the time because of the labels and table descriptions.
A lot of this desired load, desired MAF comes from a desired torque value. If the air just isn't physically in the engine it's never going to meet that torque demand, and the entire rest of the chain is going to be off.
![]()