Assuming everything works properly on startup, vvt should enable within 5 seconds. Typically right away.
Id start with techstream to narrow the possibilities.

@Ultramaroon
i ll show you a log of my car just after the rebuild
I threw a rod and bent intake cam #1 together with 2 intake valves
Subie mechanic didnt want to change the variator of that cam but in the log you can see how much it oscillated

https://datazap.me/u/tommbrz/prova-b...&data=12-30-31

Anyway, vvt activated always and after 30km it fixed itself and engine worked perfectly, as per log of today afternoon I posted before of a cold start

Then i started again the car and now vvt doesn t enable and cam intake #1 oscillates super quickly from - 0.6 to 1.1

Could be the variator that needs to be changed? is that spool valve part of it?

I'm going to try just changing out the oil. I shouldn't have to but it's worth a shot. Thanks for your participation everyone; maybe we can unravel more about the VVT system

I assume you do not have an oil pressure gauge?

Also, if you use techstream, you could rule out the oil as being a potential cause to this issue.

I don't have one, you're correct. I don't have techstream either. Might be worth getting

it definitely is worth getting. Just need a $15 adapter from ebay.
http://www.ft86club.com/forums/showthread.php?p=1920724

I am figuring out how to log using techstream. The UI is not quite... Well, it sucks.

When you say variator, could it be what I understand is called the phasor?

Hi,

I've experiencing non-moving AVCS issue also after repairing rocker arm exodus. When disabled, intake cams are not moving even in the Active Test of Techstream, but exhaust cams moving. Both are not moving in the Tactrix OP2 logs.

But after doing repeated engine braking, finally it works again. Like driving pattern for P000A, P0011, etc.

Attachment 184550

But don't know how long it takes whenever new map is loaded. Just keep doing above driving pattern until cams are moving.

I see that fuel cut when decelerating in region-D is emphasized. Without knowing exactly what does what, it still makes sense. I've noticed that, at no matter what RPM, in fuel cut (mode 4) the VVT angles lock to zero. The intake phasors have a spring-loaded zero lock. The exhaust phasors do not.

Yes sorry, i meant that
i bent that cam and mechanic assumed that from the shock, i needed to change also the 2 chains and other things correlated to them, but not the phasor.. but now i d really preferred to have changed it

I have one phasor that flutters too but I can only see it with tactrix sample rates. Unfortunately no one has the aim angle (input) parameters for tactrix definition files. Tonight I am trying to figure out how to get higher resolution from techstream.

i have techstream, i mean i ll just have to find again a cheap adaptor because for now all I have is ecutek but i'll do.
As Ultramaroon said its user interface is frustrating, can you help us find this thing we are talking about in it?

I read somewhere here in the forum that people needed to change the ecu because it stored wrong initial position values.. doesn t the ecu reset the value after a reset or. flash?

well ecutek is not so bad in refresh rate? i get 12 hz with bluetooth and around 40-50hz with cable and proecu, and i see the flutter real time

It is true. The initial position value table can only be updated when the VVT system is judged to be "OK." The problem is when the root cause for the initial position value drift is corrected, the bad value in the table forces a large enough error between commanded and measured angles to throw the "not OK" flag. It can never re-learn.