Ford Fusion V6 Sport Forum banner

IPC Control of Adaptive Steering and Continuously Controlled Damping (CCD) Suspension

69170 Views 240 Replies 51 Participants Last post by  Downforce137
2

This mod requires FORScan (PC Version) and an OBDLink MX (or similar OBD Device that supports MS-CAN):

For 2017+ Fusion Sport Only:

IPC (Instrument Cluster Panel) Changes (Module 720):

Continuously Controlled Damping (CCD) Suspension Control:
720-01-01 xxxx xxxX xxxx
Enabled: Add 8 to value at X... (example if it is a 4 make it a C (12))

Adaptive Steering Control:

720-04-01 xxxx xxxX xxxx
Enabled: Add 1 to value at X

Thanks @DaMiFo for testing this modification out... and taking these photos:





Reference Thread: HOW TO: FORScan - Modify Module As-Built Data (Detailed)


See less See more
  • Like
Reactions: 5
201 - 220 of 241 Posts
I still want to know what signal controls the shocks. Appears to be a stepper motor on shock itself.
"someday", I still want to create a signal that sets firm over a certain lateral g-force
(or maybe only fronts firm during hard braking or even auto firm over a certain speed).
  • Like
Reactions: 1
I still want to know what signal controls the shocks. Appears to be a stepper motor on shock itself.
"someday", I still want to create a signal that sets firm over a certain lateral g-force
(or maybe only fronts firm during hard braking or even auto firm over a certain speed).
I'm not sure myself. I was originally thinking they'd be listening on the HS-CAN bus, but the damper connectors look like 18-gauge 2-conductor, so I think it's probably analog, if I had to guess. Which I do, because I just don't know. ;)
VDM itself is on HS-CAN 2, with the strut solenoids being powered / controlled directly from the VDM. Height sensors are also directly connected to the VDM.

Firmware between the MKZ and Fusion Sport (at least on MY17 vehicles) is the same. There are some variables that are tweaked tho - the usual "vehicle details" like engine, drivetrain, chassis ; but there Are also tweaked stepdown amperage variables, bump volt limits, and height sensor ranges.

Sent from my SM-G986U using Tapatalk
  • Like
Reactions: 2
VDM itself is on HS-CAN 2, with the strut solenoids being powered / controlled directly from the VDM. Height sensors are also directly connected to the VDM.

Firmware between the MKZ and Fusion Sport (at least on MY17 vehicles) is the same. There are some variables that are tweaked tho - the usual "vehicle details" like engine, drivetrain, chassis ; but there Are also tweaked stepdown amperage variables, bump volt limits, and height sensor ranges.

Sent from my SM-G986U using Tapatalk
So if I had to guess, someone who wanted to integrate a G-force sensor, for instance, would be best off integrating that with an embedded controller and communicating with the VDM via HS-CAN 2. So it wouldn't matter so much what the signaling out to the shocks is I guess, because you wouldn't be at that layer.
Hey @DaMiFo while we're talking about the VDM, I've been sort of tossing around what might be involved in a VDM swap with an MKZ part, to enable further separation of the Lincoln Drive Control settings, similar to what the MKZ has. What do you think about that? I'm wondering a few things:

1. I'm not sure where the VDM actually is. From what I've found in the Service Manual, it looks like it's somewhere in the trunk area maybe? How easy is this to access?
2. Is the logic that ties the functionality together in certain ways on the FFS, vs the MKZ, in the VDM (I think the answer here is "yes" but not 100% sure, just probably 95%)?
3. If the logic is in the VDM, what about just flashing MKZ firmware onto the VDM? I think the module part number is the same between the two cars, isn't it?

Thanks for any info you can offer. :)
Yup VDM is in the trunk - DSP on the passenger side, VDM on the driver side. I looked into it a few years ago, no difference between MKZ and Fusion VDM, unfortunately. I wish it were that easy!

I'm 80% sure the CCD limitations are coming from the PCM. I started message logging a few years ago but got sidetracked and just never put aside more time for this to be honest. I did look into configs on the PCM but there wasn't much there, it's probably baked into the firmware (which definitely run different strategies between Lincoln vs Ford, engine differences aside).

Sent from my SM-G986U using Tapatalk
  • Like
Reactions: 2
I don't have an MKZ or Fusion, but on other Ford's I drove with CCD (MKS, MKC, Expedition), the easiest way to feel the difference between "Comfort" & "Normal" modes is on a speed bump. The type of speed bump that is high and short and would cause the vehicle's suspension to compress considerably after the bump. In "comfort" mode, the suspension (especially rear) clearly compresses more and then bounces a bit, maybe one or two rebounds. In "Normal" (and sport) modes, you can feel the suspension actively "stopping" the compression & bouncing.
  • Like
Reactions: 2
This is an older thread I know but this seems the most relevant to my new issue.

I have had the MKZ IPC installed for about 1 year in my 2017 Sport. Set to comfort for the entirety of that (besides in sport mode of course). But now I am getting "Drive Control Malfunction, Service Required" every time I start the car. This has been going on for about 3 weeks. (have been lazy and trying to find the right course of action). I do not have any experience with FORScan but I would be willing to start into it if I thought it was a simpler fix for my issue.

@Engineer I know you have had your MKZ Cluster for a few years now.. Have you had this issue or seen it? Of course most MKZ owners would just take it in but I am afraid the dealership would just be totally confused about the situation plus my local dealership is notorious for over charging and "fixing" the issue only to have it return as soon as I take possession of the car back.

Speedometer Motor vehicle Gauge Odometer Automotive design
See less See more
Hi @LHawk270 ! I'm sorry to hear that's happening. That's a bummer.

I haven't seen that error ever but what I would do first is pull the DTCs with a code reader and see what comes back. Something should come back because the IPC wouldn't kick that out unless there was a DTC. Then you can look up the DTC and see what's going on with it.
  • Like
Reactions: 3
I agree with Engineer, check for DTCs before going down the research rabbit hole or doing any changes. It could be completely unrelated to the IPC.
  • Like
Reactions: 2
on the ford raptors anyways, you lose all your drive modes if there's a wheel speed sensor not reporting. i know of several getting pinched or hit by flying debris, and this is usually the cause of loss of drive modes.. A bunch of functions go into the VDM..

i was assuming the solenoid on the shock is also similar to the raptor's live valve, in which its basically a magnetic needle valve in the shock being controlled by the electromagnetic coil that the wires go into.. theres height sensors at every corner so the car determines how much valving is needed in the moment..
  • Like
Reactions: 4
Thanks Guys for the Quick Responses. The car seems to drive normally so I haven't stressed over it yet and I had a busy Easter weekend. (Happy Easter BTW) I will check for DTCs tonight after work.
  • Like
Reactions: 1
Unfortunately I am not getting any fault codes. Considering disconnecting the battery to reset the system. Thoughts?
Unfortunately I am not getting any fault codes. Considering disconnecting the battery to reset the system. Thoughts?
I don't see how that could hurt. I'm really surprised you're not getting DTCs thrown though. I mean if it's popping a message on the IPC I would expect there to be some kind of signal on the CAN bus that's causing that. That just seems weird to me. But yeah I'd try resetting it.
Another thought, how's your voltage looking?
Unfortunately I am not getting any fault codes. Considering disconnecting the battery to reset the system. Thoughts?
What are you using for a scanner? If you have that error but no codes, my guess is whatever you're using can't read that part of the car's network. Pulling the battery wouldn't hurt - worst thing it would do is change nothing.
  • Like
Reactions: 2
What are you using for a scanner? If you have that error but no codes, my guess is whatever you're using can't read that part of the car's network. Pulling the battery wouldn't hurt - worst thing it would do is change nothing.
Agree. Try FORSCAN if you don't have a higher end scanner that will read live data.
And even if you do, will it read the CAN BUS data and would it be usable unless you were a programmer.
At least with FORSCAN, you can get codes from each module, not just the main ECM.
  • Like
Reactions: 1
Voltage reading 12.7V when "off", 15V when running.
It is a cheaper scanner (MP69035), it was reading live data but not any DTCs.
I think I will swing by AutoZone on the way home and see if they can pick up anything with theirs.
Then do the battery disconnect tonight if they don't find anything.

FORSCAN is my last resort, just because I have never used it before.
Autozones scanner will most likely not pick up the vdm either.. forscan is the easiest way my guy
You were correct autozone got nothing.
Plan will continue as stated. Disconnect battery tonight, see what happens.
In meantime get Forscan setup, need to get the hardware and download it. Do you guys prefer using a laptop or your phones? (Windows or Lite versions)
201 - 220 of 241 Posts
Top