Timing data through OBD2 3.5 2014 f150
#1
Senior Member
Thread Starter
Timing data through OBD2 3.5 2014 f150
Is it possible to get an idea of the timing chain stretch through the obd 2 data ?
If so what should i see at idle normally and how much variation should i see if the chain sprocket aseembly is wearing , and the limit... all i need its 2 months and 5k klm to make it home 🤪 so far only one occurence of the dreaded cold start up noise the truck is an f150 3.5 2014 with 96000 km or 60k miles.
The engine run very smoothly and quietly . No timing chain slapping that i can hear.
Like i've said only one morning within the last 2 weeks. Maybe its just the Fram Tg ADBV that suffers from a hiccup ? Any way i since changed the pp 5w30 and Fram filters to QS euro 5w40 and an fl500s ... im done messing aound with filters. Thanks for your input guys
If so what should i see at idle normally and how much variation should i see if the chain sprocket aseembly is wearing , and the limit... all i need its 2 months and 5k klm to make it home 🤪 so far only one occurence of the dreaded cold start up noise the truck is an f150 3.5 2014 with 96000 km or 60k miles.
The engine run very smoothly and quietly . No timing chain slapping that i can hear.
Like i've said only one morning within the last 2 weeks. Maybe its just the Fram Tg ADBV that suffers from a hiccup ? Any way i since changed the pp 5w30 and Fram filters to QS euro 5w40 and an fl500s ... im done messing aound with filters. Thanks for your input guys
#2
Not thru OBD but thru Forscan (Reading the computer directly). OBD is just what is mandated.
I don't know the exact PID name. It knows what it should be and reports the "Error" between the cam and crank. Should be around Zero ideally.
I suggest Motorcraft Filters with a 3-5K OCI. Nothing more needed.
I don't know the exact PID name. It knows what it should be and reports the "Error" between the cam and crank. Should be around Zero ideally.
I suggest Motorcraft Filters with a 3-5K OCI. Nothing more needed.
The following users liked this post:
homer1959 (01-20-2023)
#3
Senior Member
Thread Starter
Not thru OBD but thru Forscan (Reading the computer directly). OBD is just what is mandated.
I don't know the exact PID name. It knows what it should be and reports the "Error" between the cam and crank. Should be around Zero ideally.
I suggest Motorcraft Filters with a 3-5K OCI. Nothing more needed.
I don't know the exact PID name. It knows what it should be and reports the "Error" between the cam and crank. Should be around Zero ideally.
I suggest Motorcraft Filters with a 3-5K OCI. Nothing more needed.
#4
Yes if you use forscan software. You have access to almost everything the dealer has. You must select PCM, there will about 200 parameters.
https://forscan.org/download.html
https://forscan.org/download.html
The following users liked this post:
homer1959 (01-21-2023)
#5
Senior Member
Thread Starter
Yes if you use forscan software. You have access to almost everything the dealer has. You must select PCM, there will about 200 parameters.
https://forscan.org/download.html
https://forscan.org/download.html
I dont have forscan for now , All i have now is torque light , and I can see TIMING fluctuating very slightly , so with this torque light gizmo what number should I see ?
Forscan will be ordered next week :-)
The following users liked this post:
NYFordTruckMan (01-21-2023)
#6
Forscan can use your OBD dongle. Just download on PC and and connect with your computer.
He is using forscan here:
https://www.f150forum.com/f4/videos-...please-530514/
The following users liked this post:
homer1959 (01-21-2023)
#7
Senior Member
Thread Starter
Bonjour from down the Northway
Forscan can use your OBD dongle. Just download on PC and and connect with your computer.
He is using forscan here:
https://www.f150forum.com/f4/videos-...please-530514/
Forscan can use your OBD dongle. Just download on PC and and connect with your computer.
He is using forscan here:
https://www.f150forum.com/f4/videos-...please-530514/
The following users liked this post:
NYFordTruckMan (01-21-2023)