Bill
-
Posts
380 -
Joined
-
Days Won
50
Content Type
Profiles
Forums
Events
Posts posted by Bill
-
-
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
On 12/14/2022 at 2:01 PM, Kirby@PCMTec said:TID of interest:
TID002456 - Status value of the base point adaptation (so maybe a status flag of adapted/not adapted)
TID000916 - Flag of the setpoint being applied (I think this might be a flag for "adaption in progress")
TID002212 - Adaption Time Counter (possible relation to the timers above)
TID002481 - counter adaptations (possible number of adaptation cycles performed)TID002482 - counter TCC activations -
On 12/13/2022 at 7:00 PM, hjtrbo said:
Having a read of the adaption procedures. Do we know what software version we are? Stuck on night shift so cant go through the tune.
Software P says 6HP19 which leaves us 19.02 (A), 19.04 (N), 19.11 (T)
@hjtrbo Ford TCM Calibration files say 19.04.0
- 1
- 1
-
2 hours ago, Roland@pcmtec said:
8R29-7J105-DF_TCM_with BF serial.tec 249.17 kB · 1 download
Try this. You'll need to license it as well. Enable recovery mode when flashing and it should stop the warning about mismatched OS etc. Note that I had to do this manually, the editor normally blocks you from merging the serial in (for good reason).
The trans should go into limp mode once that file is in, I'd power cycle everything, then put the correct file back in using recovery mode and then check the adaption values.
Erased TCM Flash & failed to write. It successfully wrote back the original BF file & reads ok but there are no changes to adaptation values
-
5 minutes ago, Mick said:
@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
-
28 minutes ago, Roland@pcmtec said:
@Billthat file you attached is that with the serial of the TCM you are trying to flashing? If not can you send the licensed TCM file you are using currently in the bench PCM and I'll make a file with the wrong calibration in it but the same serial, that is all you really need to do to make it flash.
@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
-
7 minutes ago, Roland@pcmtec said:
Attach your file here and I will give it a go.
-
18 minutes ago, Roland@pcmtec said:
I think there is a bypass for that. It will "brick" the tcm but it will recover just fine. I think we allow editing the part number on 3.00 also (there is no good reason to do this except forehat we are trying here)
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 -
8 hours ago, Roland@pcmtec said:
One that's worth a shot is flashing a BF strategy into an FG or vice versa then putting the original os back. In most modern Fords they reset the KAM when that happens.
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() -
39 minutes ago, Mick said:
I redid it that way, still did not reset
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
-
46 minutes ago, Mick said:
I set ZF03182 to 0, flashed it, tuned on data logger and learned values were still there, I reset ZF03182 to 1 reflashed it again, checked with logger again and still the same values remaimed.
FG Mk2 XR6 T
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!!
- 1
-
7 hours ago, BeerTurbo said:
this setup worked as expected.
low fan on after temp1 and then fan2 started after tmp2 and fan 1 remained on.
my fans are not good enough to cool it down under threshold so i couldn't test if HSF drooped out.
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
-
11 hours ago, BeerTurbo said:
that single fan looks like it has an inbuilt resistor (or whatever is required to drop volts) in the fan itself to allow for low speed in the fan itself.
That's correct, it has an inbuilt resistor
-
5 hours ago, BeerTurbo said:
i thought the config read some similar to this because it turns of the low speed fans then 1-2 degree more turns on the high speed fans (the way im reading it)
Yeah, that's my understanding of it
-
-
5 hours ago, BeerTurbo said:
Hi Guys
can someone clear this up for me. for the Bf pcm - the fan config is it set so the LS fans turn of when the HS fan comes on?
is there a way to make this so the LS fan comes on above a certain temp and the HS fans come on above a different temp , but the ls fan stays on?
just in this conversion the radiator has one 12 and one 14inch fan on it, was hoping to run both indipendantly.
and what is the HEDF?
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?
-
2 hours ago, Jake said:
Having issues now with P2110-40 and P0701-20
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 & TPSP0701 - 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
-
2 hours ago, BeerTurbo said:
I just did a pats reset using Forscan for a Bfmk2. Just needed two keys.
FORScan can't program PATS on FGII. They only support up to FG1 & haven't cracked the algorithm for FGII
- 1
-
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
- 3
-
2 hours ago, cars.shyne@gmail.com said:
Afternoon all, so I’ve recently converted my 2008 fg to na+t and zf6 and created a file using the stock na tune and merge function, while successful in doing so and safe enough to drive to the tuner not far away (afr wise) I have a dsc fault that pops up not long after driving, in one instance I’d just left the drive when it sounded like the abs kicked in for a second on the passenger front and disappeared then the dsc fault appeared. I tried to change the abs calibration with forscan which actually makes the dash light up like a Xmas tree so returned it to stock.
I still have much to learn here so any info much appreciated.
I have been through many posts on this subject but none helpful to me at least that I understand!Have you had a read through
-
21 hours ago, Roland@pcmtec said:
Pcmtec???
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?
- 1
-
@Plumbs here's the logging layout I was using
-
@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.
- 2
Resetting ZF learned adaptions
in Transmission Tuning (AUS)
Posted
There are some links in the AudiWorld forum thread to other forums with some more info