nat
-
Posts
27 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Posts posted by nat
-
-
10 minutes ago, ECPT said:
i put the wrong one down 😅😅 i cant fine auF16503
Oh okay - for that one the FG has changed the ID of it: you're looking for auF0097 (VCT Exhaust Cam Overlap Angle)
-
7 hours ago, ECPT said:
i can not find auF0115 for my FG MK1 ? using pro, please help 😂
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!
-
4 hours ago, Tragilgas said:
Thanks for the info, can I ask what the source is? Nothing personal but a lot of incorrect info gets around on forums.
Seems a strange decision for Ford to increase compression and reduce rod strength in the same engine, especially seeing as historically they've used higher strength ones in the gas engines.
Cheers
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!
-
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?
-
1
-
-
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? -
On 5/12/2019 at 12:16 PM, Roland@pcmtec said:
Great work Nat. If you have the workshop version of the software in the strategy list we have pulled out common auF parameters and put them in there, we could add this to the list if you want as we can automate extracting a specific param from all calibrations into a csv.
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!
-
1
-
-
7 minutes ago, Carl said:
Ok the manual I have for fg said it was b4 for some unknowin reason.
The pcm was originally an auto one.
What would be the best way to change the strategy and what to.
Fg Cruise control, various sensors, turbo comp.pdf 155.64 kB · 2 downloads
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!
-
4 hours ago, Carl said:
Ok I have tried every thing I can think of.
Putting b5 to earth putting it to battery volts putting pullup resister in putting pull down resisters in toggling clutch switches on/off. launch control switch on/off. Cruise control switches on/off.
I have even tried pin b4 as this is the clutch pedal switch for a fg.
I am out of iders.
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)
-
3 hours ago, Roland@pcmtec said:
I haven't heard of this being a problem before.
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
-
8 minutes ago, Carl said:
Running a manual ba f6 calibration
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?
-
4 hours ago, Carl said:
I am starting to think I need to set it up with a pullup resister in between. But not 100% sure.
Are you running the auto or manual calibration? I would expect if it's using the auto calibration the actual state of the CES is ignored. If there was a switch to enable / disable the switch, I'd be looking under System Switches, but I cannot see anything in the FG/FG2 calibration (but it might be different on the BA calibration)
-
Disabling PATS won’t change the cluster so you’re all good there; just the ICC will not function (I believe it will just say security code error)
-
Awesome that you're able to reproduce the issue; good to know it'll all be fixed!! Sounds good about the disabling colouring too - Thanks again!
-
1
-
-
I'm only getting the black cells when the program means to draw the pink changes (literally just opening the file and half the tables have black); but cannot explain why some of the pink cells work and the others do not. I've attached my current tec file I've been working on as it theoretically should allow you to see straight away (It's the file I was talking to Darryl about moving the N/A stuff over to the turbo map therefore there are a lot of changes in a lot of tables! - It's also unlicensed etc so far since my PCM is still not able to be flashed yet). I did try saving the file but it continuously stays with the pink which is quite annoying! (Highlighting the cells redraws fine but with pink on all the stuff; the current workaround I have to get the normal colours back is on each table to hit the undo and then redo button...)
-
Just curious if it's possible to have an option in the settings to turn off the colour highlighting for cells changed? When looking at a few tables now after I used compare view to change some tables I now end up with my tables looking like this with colour missing and or being largely pink!
Thanks!
-
Had a crack at porting all the N/A stuff over to the HAEE4 calibration (from HAEE3) and it looks like I should be all set for when this is all to go together now (got access to IDS so that's all going to be a breeze!) - thanks again for your assistance on this one!
8 hours ago, Darryl@pcmtec said:We are working on this for the next release of the editor with literally 1000s of these being updated, stay tuned
Now this is some great news!! You guys never stop delivering - great work as usual!
-
Thanks for your reply Darryl!
Interesting that the PCM I have may have the inputs connected internally for boosted applications - one day I'll find out as the plan is to sort out setting up the whole turbo kit on this engine.
That makes sense now about why the different OSIDs I've tried all are varying differences! Bit easier to grasp now.
When it comes to all the OSIDs I'm aware of for the FG MK1 these are all I've found; (I had been using the old Ford IDS calibration CD list from 2012); however all I know of for HAEE4 and HAEE5 are of PCM type APS-234 (which means they are all turbo logic by default etc) - since I don't have a specific N/A strategy code for either of these two would you just recommend choosing any of the strategies (i.e. HAEE4A3 or HAEE5C4) and then changing parameters to disable turbo logic (and move over the maps for timing and fuel etc)?
Another question I've got - with some of the descriptions of system switches etc are cut off; I guess the whole description just does not exist?
Thanks again!!
-
So I'm about to put a FG Mk1 N/A motor into my car - and was trying to determine which catchcode / OSID to end up using as the PCM I got with the motor is an APS-232 variant from a 5sp automatic FG (annoyingly there's no catchcode to determine the OSID on it and I'm still to finish the wiring so I can flash the ECU; but from what I can gather being an 8R29 code on the sticker it'll likely run HAEDJ or HAEDH); and since I'll be running a manual transmission instead of the automatic (which runs an APS-231 ecu) I've gotten a relatively decent selection of calibrations (and I'm aware it isn't even all of them! It was hard enough making this list already!)
The strangest thing I find however; when I try different calibrations in PCMTec I end up getting for some calibrations more features/variables; whereas for others I find I get less!
For example, on the left below is what's I see in the coasting cut offs on HAEDHC3; whereas on the right is what I can see on HAEE3F3 - a lot less in this section for example. Other sections do have a few differences as well - I'm curious if this is something that either:
Is there functionality missing from the different calibrations (Note I have fiddled with both turning on and off viewing workshop/professional features and it stays the same, as I'm running Professional) / e.g. would I be best off flashing the calibration that looks like it has more options? (Or am I completely bound per the OSID that will be on this ECU that I currently have? I'm not too sure how different OSIDs particularly work!)
Or is there possibly some way to compare what different calibrations have different settings? As the compare mode of course only compares differences in maps that are common to both.
-
Appears I was too slow to edit my post; I missed the part stating I am not certain on which one the sprint uses; from other posts before it would seem as they kept the same injectors from the turbo models, and not the F6 injectors.
-
On 5/31/2018 at 9:39 PM, Whiteford said:
Hey Nat, Where did you come across this information?
Hi Whiteford,
I originally heard they used the XR6 turbo internals from an interview with Justin Capicchiano (Sprint project manager); I can't specifically find which one it was but here's a link which slightly touches on the subject of the changes: https://www.motoring.com.au/is-fords-falcon-xr-sprint-australias-quickest-car-101758/ (note they have for some reason rounded the comp ratio up for both FPV & XR6T).
Also on which injectors the sprint uses - it's should use the same as all FG F6's (8R29-9F593-CA) whereas all FG/FG-X turbos use BG-9F593-B.
HOWTO: Ghost Cam and VCT simplification
in Falcon HOWTO Guides
Posted · Edited by 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