FORScan 6DCT450 Clutch Learn - a few notes

[AlCan]

Subject vehicle: 2013 MC TDCi Wagon 134,000km, with various issues including inappropriate early changedown from 3rd to 1st.
System: FORScan V2.3.64 release on Windows 10 Laptop.
OBDII Connection: vLinker FD - Bluetooth.

From a bit of prior reading on the subject, knew that part of the Clutch Learn procedure was to "Floor" the accelerator pedal.

This caused me much dread and trepidation, as the RPM dashed Red Line starts at 4,500 and goes solid at 5,000. I didn't fancy revving my engine until it was bouncing off the rev limiter at 5,000 RPM, as is the way things are with mechanical diesel engine governors.

Obviously, I'm way behind the game with CR Diesels, so was very pleasantly surprised when, as I apprehensively pushed my accelerator pedal to the floor, the engine revs went to 3,000 exactly, and stayed there. Obviously, when in Park with the brakes on, that's all the ECU [PCM] allows you. They never went over 3,000 throughout the process. I've never tried this before and don't know what other conditions limit the engine RPM, but maybe I'll experiment more.

Anyway, 3,000 RPM is perfectly acceptable, and I proceeded with the Clutch Learn. There's a progress bar along the bottom of the FORScan window, and mine went to 9% and stopped there, seemingly for ages. I was thinking Hell, if this is only 9%, how long is this going to take?

It's interesting when whatever is in charge then dropped the RPM to 1,500 then to 800 as the test progressed. You could hear the system testing things, with obvious, small changes to load and RPM as clutches started to engage, etc.

Then at some point, don't remember exactly when, the Progress Bar suddenly zoomed to 100% and the process was complete.

It took 4 minutes.

To conclude, from my experience with this transmission, there's nothing to be scared of in performing a Clutch Learn.

BUT: I'd recommend being confident with your OBDII dongle before you do it, especially if it's a Bluetooth one.

Others here have reported connectivity issues with Bluetooth models, but mine has so far been flawless in that respect. (It's supposed to go to Standby / Low Power when Engine Off etc for a while, but mine seemingly doesn't do that part, judging by the heat.)

I have a vLinker FD (Bluetooth). [This model does not connect to Apple devices, only Windows & Android.]

I was very impressed with the process, which was not scary at all. The transmission now operates much more smoothly, and no longer tends to roll downhill at low throttle when trying to back uphill.

Not sure I'd be happy running Clutch Learn on the 2011 though, as it has obvious clutch shudder issues. Anyone else tried similar?




P.S. The OBD Connector is behind the long small door above the Driver's right knee. The design is, I'm sure, intended to dissuade you from driving the car with an OBD connector plugged in, as the door won't shut when the connector is in place.


The workaround for this: the OBD connector is held in place in the moulded door and frame piece by a single, heavy duty clip behind the OBD connector, on the bottom side. I haven't managed to release this clip with the door assembly in place, but it may be possible. Otherwise, just undo the four Torx head screws holding the frame in place and gently turn it around to release the clip and push the connector backwards out of the moulding. Then, as there's just enough length to the wires, you can put the door back in place.


Then, you can plug it in and dangle your dongle into the well in the bottom of the door, and shut it. The plastic door doesn't affect the Bluetooth signal, and I suspect this is what Ford intended, for Service Agents at least.

[AlCan]

Originally Posted by AlCan

Obviously, when in Park with the brakes on, that's all the ECU [PCM] allows you.

CORRECTION: It's not 'obvious'.

I checked this out later...

Being in Park with the brakes on is NOT what does it. The engine still revs beyond 3,000 RPM.

Evidently, when initiating Clutch Learn, it's something triggered by FORScan. Whether it's set by FORScan or it's a routine built into the TCM that FORScan activates, I can't say.

I just followed the on-screen instructions, and pressed the pedals (Brake & Accel) as instructed by FORScan.

What I can say is that if you get to this stage in the Clutch Learn process, and the engine revs go over 3,000, I would question the reliability of your OBD connection. It may be unstable, and this would be the worst time to have that.

I'd say Stop and don't proceed further until you have verified that your connection is reliable. Bluetooth connections are known to be troublesome, especially with cheaper dongles. To test it, run it on Read-only tasks for a while. Download lots of Live Scan data, check that it looks correct.

[goz007]

Nice write -up of your experience..... yeah I'd say it's all Forscan controlling the cars out put after you follow Forscans desired inputs.....well done on the write-up & completing the relearn.

[AlanM]

Something I've found is that a clutch learn produces a better result if it's done when the transmission oil temperature is close to the upper limit Forscan allows.

In use the oil temperature tends go go quite a bit higher so the warmer the oil the more "realistic" the conditions when the clutch parameters are set.

[AlCan]

Thanks AlanM. I'd agree 100%. As per my other thread, I got my Trans Fluid up to 92°C yesterday, without much effort. Just sitting at idle for the last few degrees.

On another topic, can I ask, when you pull a TCM out, do you replace those two long metal gaskets each time?

[AlanM]

Originally Posted by AlCan

Thanks AlanM. I'd agree 100%. As per my other thread, I got my Trans Fluid up to 92°C yesterday, without much effort. Just sitting at idle for the last few degrees.

On another topic, can I ask, when you pull a TCM out, do you replace those two long metal gaskets each time?

No, those gaskets are fine to re use as long as you haven't bent or damaged them.