apoc

This is from HAEDDEZ - FG N/A tune as far as I know. I think this is an auto tune but my BF manual one is pretty similar.

From what I can see in the professional version, you can change the expected gear ratios in the tune, it may be your solution.

I'm quite impressed at the amount of spark these PCMs can pull with knock, datalogged my Patrol and it was pulling >8 degrees at WOT in some spots, with no pinging whatsoever. Have fixed it now. Noticed that the 'Auto Octane' tables pull 4 degrees when it sees -4.55* of knock consistently, would a good way to tune for this tune for ~4.5 degrees of knock retard on 91 and turn auto octane on for when you run 95/98? It's a bit crude I know. I have knock ears and it doesn't seem to be pinging at all Is there a rule of thumb for the Falcon 4L and amount of timing advance possible between 91 and 98?

Noticed that his list doesnt have the HACCK strategies either (unless I'm blind)

I've made a spreadsheet with all the info Matt has got, let me know if it's not kosher and I'll take it down. BA-FG_PCMCodes.xlsx

Awesome. Am looking forward to getting rid of my SCT handheld!

Hmm, just checked the deadtimes, I have an FG manifold on a BA lpg motor, with BF cams and BF pcm. Looks like the BF deadtimes are still in there, am using the FG injectors. Will swap to the FG ones. I didn't make this tune, it was done by a shop via SCT and I'm trying to make it more consistent, and run better. Only had the fuelling and idle cleaned up, and 2* of timing across the board from 0.5 load upwards (in the borderline knock table). The dash still reads 4-5L/100km when in full decel mode, will see if the deadtimes change anything. Haven't got my wideband on at the moment as fuel trims were good to begin with, may have to add it in though. How long until your logging / scanning functions are available? Regarding the RPM, it doesn't have to be low, can be >2000rpm if need be. What I meant is it would be in low range gear, going down a steep hill. I appreciate the fast responses too. Cheers!

That's what I would have thought too, but there seems to be a 'internet opinion' that the injectors still are pulsed a tiny amount. I'll have a play with the cam timing, to see what helps it a bit! Still working on the dashpot adjustment, which table should I be adjusting for it? Increase the maximum on auF0034 and auF16506 at >2000rpm? My end goal is to maximize engine braking in low gear, as I drive it in 4wd high country vic. It runs on a bit more than I would have expected, I assume because of the lighter rotating assembly than the old motor, but also the tuned-in manners for a lighter street car. It would save my brakes a fair amount when going down kilometers of steep hills!

Hi, Looking to increase engine braking as much as possible (or reasonable) on my BF engine in my Patrol. From a look at the tune and a datalog, it seems to be commanding around 18-25* of timing while in decel fuel cut. From some reading, more advance seems to generally help with engine braking performance while in dfco. auF16630 (MBT timing) is around the 40* range, auF16593 (Bldn Timing) is 50, and auF0228 (Decel spark angle) is set to 63. Is the ignition retard coming from the CFC torque on rate (auF0149) and Torque spark retard (auF0263)? So if I increase the former to around 0.8 to test, it should pull less timing?

Tested the VCX Nano with my BF Patrol last night, got it working. Had to set up the device as a passthrough, set the open the console, set the programming voltage to 18000mV, close the connection and leave the DLL registered, then it worked. Will test with my GT as well, but pretty confident it'll work. Managed to pull the current tune, stock tune, and re-write the tune back in with some modifications. Had some issues with PATS but got it going in the end. Thanks!

Thanks, will do and report back tonight.

Thanks, I'll get an Tactrix Openport eventually, just wanted to have a play with this one if possible first. Yep, set up the J2534 driver as a pass-through using VXManager, didn't seem to help. Possible that I have a bad device, or that I need to set the programming voltage to 18v as above (or I'm just a derp and not setting it up properly, wouldn't be the first time!) Whats the process you went through to get it working? Did you have to install the Ford IDS software? Win10 or 7?

Hi Darryl, Probably not worth a new topic, was there anything special you had to do to get the VCX Nano working with PCMTec? (I know its officially unsupported, but you seem to have it working). I've been trying to read my 2014 FG GT, and it seems to get a security error. Assumedly I don't have a setting/driver or application working properly. Will also try another USB cable as you found above. I'll try it on my Barra Patrol (BF PCM) tonight too if I get time, to confirm it's not just the car. Thanks!

I've upgraded to the professional version and it's now working very nicely. Appreciate the help Roland!

In the case of an engine conversion (no door sticker, BF PCM), is there anything special I need to do to change over? Or just read the tune, return the car to stock using the controller, license the *tuned.tec* file and it'll flash as per normal? Understandably the tune will need be checked over before re-flashing it back in to check for errors / mismatches etc. Car is currently SCT X4 tuned.

Sounds good. Thanks for the prompt reply!

Hi, I purchased the Enthusiast version of the editor, and don't have access to the car for a week or so. Does the enthusiast license have access to the stock file database? I can't seem to find any tunes (bar the demo ones), stock files folder is empty etc. The calibration merge button is greyed out. I've also tried on 2x different computers. Is this a >=Professional feature only? Thanks,