Instead of commanding 0, try commanding 3-5* and never 0 anywhere.
I would be confident the phaser DC doesn't get pegged at 0% doing that. If this is an eco boost their feed forward tables are around 40% for the hold position.
37-39% seems to be where your phaser is able to hold the cams position, and it does that fine until you command less than 3-5* and that error is there for a few seconds not being corrected. It is still there even on decel.
If this is a coyote and its holding position at 37-39%, and not near 50, thats an indication of an issue.
as you stab the throttle:
Shooting up into the 50's it moves it oneway
Slightly after the pull starts:
Shooting down into the 30's it moves it the other.
The lag between desired and actual, thats all normal.
making the FF tables more aggressive tightens this lag up.
Why can't you command 0 and achieve that position ever? idk some physical problem with the phaser or position sensor. Maybe the exhaust timing is off a tooth.
Phaser duty cycle and error.jpg
When you start this car up, is the exhaust cam at 0*? When the engine is off does it show 0*?
You have other logs, different cars, that show exhaust cams reaching 0. not logged was desired, duty cycle, or error, so I cant show those and what they should be doing. What you do see is its not exactly pegged at 0, its holding it there with small variations just like other positions.
exhaust angle at 0.jpg