|
Software Tuning Discuss all software tuning topics. |
|
Thread Tools | Search this Thread |
12-06-2017, 11:03 PM | #1 |
Member
Join Date: Mar 2017
Drives: 2014 BRZ
Location: Pittsburgh
Posts: 21
Thanks: 14
Thanked 14 Times in 5 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
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 |
12-07-2017, 05:31 AM | #2 |
Senior Member
Join Date: Jan 2013
Drives: Toyota 86
Location: South Korea
Posts: 267
Thanks: 127
Thanked 200 Times in 115 Posts
Mentioned: 5 Post(s)
Tagged: 0 Thread(s)
|
Did you compare it with VASC tables?
__________________
/* Custom underbody panels and diffuser
Custom electric water pump and PWM controller HKS GT EL header, 17MY intake manifold */ |
12-07-2017, 08:59 AM | #3 |
Member
Join Date: Mar 2017
Drives: 2014 BRZ
Location: Pittsburgh
Posts: 21
Thanks: 14
Thanked 14 Times in 5 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
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? |
12-07-2017, 04:03 PM | #4 |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
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 |
09-03-2021, 08:18 AM | #5 |
Member
Join Date: Jul 2020
Drives: Subaru BRZ 2016
Location: Québec
Posts: 33
Thanks: 4
Thanked 11 Times in 9 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
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.
|
09-03-2021, 10:58 PM | #6 | |
Banned
Join Date: Dec 2013
Drives: FT86
Location: Australia
Posts: 7,998
Thanks: 1,035
Thanked 4,987 Times in 2,981 Posts
Mentioned: 598 Post(s)
Tagged: 2 Thread(s)
|
Quote:
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 |
|
The Following User Says Thank You to steve99 For This Useful Post: | NicFromTheNorth (09-06-2021) |
09-10-2021, 04:50 PM | #7 |
Member
Join Date: Jul 2020
Drives: Subaru BRZ 2016
Location: Québec
Posts: 33
Thanks: 4
Thanked 11 Times in 9 Posts
Mentioned: 0 Post(s)
Tagged: 0 Thread(s)
|
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?
|
|
|
|
|
Similar Threads | ||||
Thread | Thread Starter | Forum | Replies | Last Post |
AVCS IDLE PATCHED | aagun | Software Tuning | 52 | 03-09-2023 01:32 PM |
AVCS Explained | Rennmeister | Engine, Exhaust, Transmission | 3 | 03-15-2016 03:12 AM |
AVCS tuning | Turdinator | Software Tuning | 9 | 11-24-2015 01:31 PM |
Turbo AVCS/VVT settings | ztan | Forced Induction | 8 | 05-10-2015 04:17 AM |
AVCS failures? | hmong337 | Forced Induction | 26 | 02-12-2015 03:01 PM |