Bill

There are some links in the AudiWorld forum thread to other forums with some more info

Some interesting reading in the AudiWorld forum for interpreting ZF6HP19 adaptation values. @hjtrbo @Puffwagon while you're testing, it would be good to find out if the items in the table below are some of the TID's of interest that @Kirby@PCMTec posted previously Interpreting tiptronic adaptation values - what is your gearbox telling you? - Page 3 - AudiWorld Forums

@hjtrbo Ford TCM Calibration files say 19.04.0

Erased TCM Flash & failed to write. It successfully wrote back the original BF file & reads ok but there are no changes to adaptation values

@Mick if you're not in a rush & can hold off until I get the file back from Roland, I'll test flashing it on the TCM I have here. If something goes wrong on the bench, it won't be as big an issue

@Roland@pcmtec the previous file is unlicenced but is the FG one we want to change the part number on & try. Here's a licenced BF file with serial 5R29-7J105-DG.tec

8R29-7J105-DF_TCM_Test.tec

I'm unable to edit the TCM part number in 2.11 & 3.0. Trying yes as per below just results in an error. I'm happy to bench test using the TCM I have here if you want to provide a "Test Version" that allows editing the part number. The BF TCM I'm using for testing has a broken pin & has been flashed a heap of times. Lost communication & recovered so I'm not too concerned. This would tell us if changing to a FG calibration will reset adaptations. I have tried setting ZF03182 to 0 in using a Territory 7R29 calibration & flashing over a BF 5R29 calibration with no change to adaptations. They use the same TCM part number

You'd need something like PCMFlash to change the TCM OS. I tried this with PCMTEC a long time ago & again this morning. I don't have a licenced FG TCM so it first prompts to licence the TCM as expected. It then determines the TCM part numbers don't match Program Error. Please contact support@pcmtec.com. Detailed information: Exception Message: ZF Part number of vehicle (DAI26832) does not match the part number of the file (DAC26840) Merging the serial number would brick the vehicle. You must only flash in a matching TCM OSID to the TCM. Source: Pcmtec.Editor Exception Format: _u3HBrE0jX7mWSGMMYVRpFPzKgdw StackTrace: at _ONL59ErIAD4BWw6Qc2htQIbeooB._jwPA5dLVOyy8KYw7u3QQntWjsYH.MoveNext() --- End of stack trace from previous location where exception was thrown --- at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task) at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task) at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task) at _ONL59ErIAD4BWw6Qc2htQIbeooB._MaJ2GsSOsVTLmRQPDrc2TSFLJ9A.MoveNext()

Yeah, I didn't know if you'd done it or whether it would make a difference but thought I'd check, it's written as part of the procedure

Did you start the car & put it in gear after changing it to 0 & then turn it off before flashing it back to 1?

Great write up Graham. Time to enjoy!!

Low fan set at 68°C would see it come on well below the thermostat opening temp & high speed fan at 78°C may also see it coming on before thermostat opening temp, depending on the rating of the one you've fitted. Sounds like it won't be a real problem with the fans you've used in hotter weather with but make sure that in cold weather you don't end up it having it run too cold or have the thermostat constantly opening & closing

That's correct, it has an inbuilt resistor

Yeah, that's my understanding of it

Single fan was used on some from 01/05 & still available through Ford. P/N BR2Z8C607AA The factory 2 fan units use 3 relays to control them where the single fan uses 2 BF fan wiring diagrams....if needed

If your strategy is a na one, have a look at a BF turbo strategy eg HACCHB5 & compare as it was factory dual fans. I believe most na were single fan HEDF is High Electro Drive Fan

Have you checked if the P2110 code is present with a stock tune or with altered throttle parameters reset to stock?

P2110 - has any throttle body wiring been altered/extended/damaged? Has the original, working throttle body been used? Has the throttle pedal been unplugged for some reason? Check wiring, log pedal position & TPS P0701 - check the wiring connector & pins at the gearbox. Also look for damaged/broken TCM pins. Make sure there's no damaged wiring between the TCM & PCM

FORScan can't program PATS on FGII. They only support up to FG1 & haven't cracked the algorithm for FGII

Using the merge function may have copied a value that's causing the ABS/DSC fault depending on exactly what the fault code is??? C1991 or something else? @jakka351 has invested a lot of time finding a solution for this issue

Have you had a read through

Hi @Roland@pcmtec are the MID's listed under CustomOS available to Enthusiast & Professional customers? I've created a CruiseControl.tlo for @Plumbs & attached it to a previous post. I've also & added some comments in a logging screenshot explaining what should be expected but couldn't test the "Clutch In" to confirm it's the correct MID. Are you able to confirm if it's the correct one?

@Plumbs here's the logging layout I was using CruiseControl.tlo

@Plumbs I've setup some channels & run a test. The below MID's are what I've setup & used, renaming the Display name. Some MID's are sitting under "Cusom OS" so hopefully they're available for you. There are some notes in the screen snip explaining what you should see.