nat

I don’t know of any way for the ZF to do that, but personally I’ve never worked with those (as I’ve got the TR6060). Roland will have a better idea if anything, or if anyone else in the thread has worked with the FG autos and wishes to share their setup may help you. My car has a bit of a drivability issue itself in the throttle hanging a lot on decel even though I only touched 3 tables (overlap tables) 😂 Might need to datalog load and commanded overlap etc

Oh okay - for that one the FG has changed the ID of it: you're looking for auF0097 (VCT Exhaust Cam Overlap Angle)

I've got a MK1 and using Pro too and can see it; if you click View up the top and under PCM see if Professional is ticked there?

I would think that half of it would be cost savings - but also with the smarter PCM used in the FG knock detection I would expect is much better than back in the days of the BA. The main reason for the change to thicker rods originally was due to backfires bending the rods, and it does appear less likely in the EcoLPI (although I never have worked with LPG myself) Considering the brutal testing Ford put the engines through (48 or 72 continuous hours of interchanging between max power and max torque - can’t remember exact numbers) they certainly weren’t worried about reliability!

BarraDrifter is correct here - I used to work with the parts system used at dealers (Microcat Live) and can confirm that this is the case - you can call any Ford Dealer and they can confirm the rod used. I've attached a file I created to reduce confusion back when I had full time access to the parts system. Hopefully that helps answer that question! Engine differences.xlsx

I don’t believe anyone has posted any tune with that already done. You’d have to use the compare function to change over quite a bit of the tune as there’s a lot different (Almost everything to be honest as new cam profile, injectors, compression, and intake manifold) between the BA and Fg. Plus I don’t know about independent VCT in the BA PCM whether that’ll even work. Probably not?

Well after a day of mucking around with my car I’m certain the auto PCMs do not have the input for the clutch switch internally connected. FG 5sp auto PCM in a manual FG just doesn’t detect the switch at all. Launch control still works (the car will rev to 3650 from memory) and just sit there as long as the car isn’t moving. Not sure Barra.AU what will happen in your case if it is the other way around.. also maybe Roland meant use a relay to invert the signal to the PCM?

Cheers Roland - I personally don’t have the workshop edition so wouldn’t get to use that function - whether or not it’s useful I suppose comes down to how many possible conversions any workshop would be doing to ever use this functionality (and whether or not it truely works!)

Apparently I can't edit the one above again: another thing to note is auF2193 does not exist in the FGmk2 onward or the SZ territory. I went and found a couple of N/A and Turbo Territory IDs and sure enough; there's no reference of a 4WD 0x80 bit. All fall into the bits I've posted above. Quite mysterious!

So I was doing some comparisons of plenty of PCMs (19 different ones in fact!) and ended up with this bit breakdown for those two config words: The only car I couldn't get was a N/A Territory (I'll likely go on carsales/pickles salvage to get an ID) to check if bit 7 of auF2193 was in fact used. (as mentioned with the 0x88? above) I couldn't verify the 4WD vs AWD part of auF2193 either; as there is no true 4WD anyway!

Did some looking at the proper ford wiring diagrams, and indeed the FG mk2 and FGX both use the switch on B04; however the Ba-FG1 are all definitely on B05; so the document you’ve got is correct but should say from 2012 onward, not 2008! As for a strategy to try instead, I gather you are already using HAAT0V6 and have licensed it? (BA F6 manual) - I have another calibration of HAAT3VC (BA manual, pretty certain it’s an F6 as it runs even higher boost levels then HAAT0V6) you can get it using the create stock file wizard. The only issue is for licensing: I’d suggest wait for Roland or Darryl to chime in to let you know as I think it would cost in credit as I believe the calibration OSID is the first 5 digits (HAAT0 vs HAAT3); I wouldn’t suggest going ahead until you’ve got clarification as no point spending a credit if it achieves nothing! Sadly I don’t have a list of any other HAAT0 IDs... my list is old as - around 2012!

FG is actually still pin b5 for the switch, b4 in an FG is the start enable pin which goes to the starter relay in the power distribution box. From the sounds of it; I can only think either: a) the PCM is either faulty or if it was an auto pcm then for some odd reason the pin is not hooked up internally (It is so unlikely though to be that! Doesn’t require a solenoid or anything); or b) the strategy is for some reason always ignoring the clutch switch. whether or not it’s possible to try another manual strategy to cancel anything being software related? (don’t start the car, just flash it and see when ign on if the status changes when logging through your preferred method)

I agree that I’ve never heard of it as a problem either - It would be unlikely that something could have gone wrong in regards to the switch as I’ve even tested my FG one and it’s just straight to ground... it’s just very odd that even with the manual strategy it always puts the PCM in the clutch not depressed state!

Is it possible that if it was originally an auto pcm flashed to manual that the pin isn't connected internally? Someone else with a BA PCM flashed to manual would need to chime in though

I should have read!! No issues there then so: I gather your switch you’ve added is directly off the PCM to ground (i.e not running off another loom) as everyone else mentioned they are a very simple ground switch to activate, nothing can really go wrong there. So when you don’t have the launch control settings in place does the motor rev freely and not cap at the set launch rpm?