AVCS logging on OFT question
 

I'm trying to experiment a bit with the AVCS system (at lower RPMs), intending to use it with the MAF Scaling Tool's VVT tool, and have run into a puzzle with my Open Flash Tablet: "vvt intake" seems to be super noisy, though "vvt int at" seems to be fine. In contrast, "vvt exhaust" seems to be fine.

Any suggestions? Should I just use "vvt int at" as the current intake angle and ignore whatever "vvt intake" is trying to present?

https://datazap.me/u/baront/log-1512...4&zoom=510-731

Did you compare it with VASC tables?

Yes. "vvt int at" compares very well with my Intake Cam Advance Angle (both my "normal" and "safe" are the same currently). So closely that this could be the computer requested angle as opposed to the current observed angle. Just comparing numbers, it looks like "vvt int at" is what I should use for Kodename47's tool.

I'm mostly just curious about "vvt intake" because "vvt exhaust" seems to be fine. So is "vvt intake" just logging some junk value, or is my cam angle sensor messed up?

Looks like that vvt intake log parameter is logging rubbish

If your 2012-2016 you need to go to a bo1c or d rom to get correct logging in mamy cases

I have the same Intake AVCS logging issue. @steve99, in your links it is stated that ZA1JA700C ,900C, A00C ,A01C , B00C are all compatible with ZA1JB01C. However I am using ZA1JF00C... do you think it is also compatible with B01C? I just want to check before I start porting all my maps to a ZA1JB01C rom.

Yes any USA 2012-2016 manual car is compatible with ZA1JB01C firmware


also make sure oft is updated and you manually update the Template File from oft support site

One last question: to make a B01C rom appear as a F00C rom, can I just modify the bits corresponding to the ASCII representation of ZA1JB01C? Or is there more to be modified?