2016 FORD FUSION (AMERICAS) ECU

[x] Cancel search: ECU

Page 310 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual WARNINGS
Never get underneath a vehicle that
is supported only by a jack. If your
vehicle slips off the jack, you or
someone else could be seriously injured. Do not attempt to change a tire on
the sid

Page 311 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual 9. The vehicle jacking points are shown
here, and can be identified by the
triangle markings on the molding. The
triangle marking may be located on the
side or the underside of the molding.
The jackin

Page 312 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual 3. Block both the front and rear of the
wheel diagonally opposite the flat tire.
For example, if the left front tire is flat,
block the right rear wheel.
4. Remove the carpeted wheel cover.
5. Remove

Page 313 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual 10. Place the jack at the jacking point
next to the tire you are changing. Turn
the jack handle clockwise until the
wheel is completely off the ground.
11. Remove the lug nuts with the lug wrench.
12.

Page 314 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual TECHNICAL SPECIFICATIONS
Wheel Lug Nut Torque Specifications
WARNING
When a wheel is installed, always remove any corrosion, dirt or foreign materials
present on the mounting surfaces of the wheel or

Page 361 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual Action and Description
Message
Press the OK button and scroll to select. Press the OK button
to confirm.
Access the Auto Version number as well as the FDN number.
System info
Press the 
OK button to s

Page 381 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual Phone issues
Possible solution(s)
Possible cause(s)
Issue
Depending upon your phone,
you may have to grant SYNC
permission to access your
phonebook contacts. Make
sure to confirm when
prompted by your

Page 382 of 518

FORD FUSION (AMERICAS) 2016 2.G Owners Manual USB and media issues
Possible solution(s)
Possible cause(s)
Issue
Try turning off the device,
resetting the device,
removing the devices
battery, then trying again.
This may be a possible
device malf
Page:   < prev 1-10 ... 9-16 17-24 25-32 33-40 41-48 49-56 next >