Storm
Registered User
I'm watching a log on a truck that's not pulling over 20lbs of boost at WOT..
idle - VGTDC .662
3000rpm - VGTDC .362
What's the ranges on VGTDC ?
idle - VGTDC .662
3000rpm - VGTDC .362
What's the ranges on VGTDC ?
Aye.. What the hell is SCT doing than with software.. I don't get why their VGTDC is misreading.. I assume its pulling the VGTDC from the same area ya'll are..
Hmmm
I have that.. It's for a buddy who's about 200 miles from me.. He's trying to keep from going to Ford b/c he isn't comfortable with their service..
He asked me to look over this log, and I can see a problem.. He's a truck driver and sometimes the truck sits for weeks.. I'm thinking stuck vanes because it's not being ran..
Exactly... The problem is, It appears the Duty Cycle isn't getting to the right place for the boost build.. It's like it stalls, however looking at it in current, its hard to decode it into actual Duty Cycle.. I may have to call SCT on this one and find out why the VGTDC PID is showing voltage.. I know its the same PID ya'll use, maybe ya'll software readjusts the signal into a different format..
See I don't know what 85% is tho because what I see on VGTDC PID is decimal.. Unless we have a way to compare 85% to the decimal.. I could easily say .662 is 66.2%
LOL but than that doesn't make sure.. More boost you build the high the Duty Cycle goes right? or the lower?
Hey new to the board and was just reading along. Even with whatever readout of the signal that is being sent to position the VGT it is just that. You still have to parse out the actual position of the VGT as it may be stuck correct? As far as I gather there is no feedback signal to the computer that gives actual VGT position.
JR