Roland@pcmtec

I sent you a reply. I haven't been able to reproduce this with 1.11 or 1.21 beta so far. If anyone else has this issue can you please contact us as well.

To disable the seat belt chime in an FG the procedure is turn key to ignition, wait for airbag light to go out, then plug in drivers seat belt 10 times. Thanks to Matt at Dark Horse for this info.

Can you send us an email demonstrating this behaviour? It should not occur so it is likely a bug, if you can include the files that cause the problem that would be great. In the mean time you can reset those settings to factory by going to Documents/PCMTec/1.11/Settings and deleting (or backing up) the file called PCMTec.Editor.Settings.dat This file contains the logged in user, recent file history, units, selected theme and any other options you've enabled. You will need to log back in after doing this.

The hardware differences between auto and manual should not be an issue, just make sure you get a PCM of the same type, eg if its a turbo you must get a turbo, if its a 6cyl you must get a 6cyl etc. Then flashing in the manual version of that strategy and you should be 90% of the way there. Someone on here took a manual F6 strategy, compared it to an auto 4 speed strategy, copied over all the various auto tables and it worked fine so you could also convert the auto strategy to a manual via that method as well, however you'd need the workshop package to make sure you dont miss any parameters. I wouldn't even bother looking at the DTC codes until you put the right strategy in, removing the auto box will cause a huge number of them, and it may mask others as well.

I'm not sure off the top of my head. Those kind of questions are easier to answer by experimenting, just put some silly numbers in there and see what happens. Something to be aware of, the load is not actual measured load, but inferred load based on throttle opening. So the load numbers you see on tuning correction are not going to match your load on the spark map.

Not really following what the question is.

If you want exactly 1 then you need to run open loop at all times. You can do this in a BA/BF if you follow the guide, FG you may need to unplug the sensor to achieve this.

1.0 * 1 -1.133 = 0.867 You have 13% short term fuel trims so it makes sense to me. This is normal as the narrowband is trying to induce a rich lean lambda oscillation to keep the catalytic converter in the efficiency region. Can you log your o2 volts against it? It is probably reading lean hence the short term trim commanding a rich afr to attempt to get it to swing. Short term trims are not very useful to log as they will always oscillate. Just look at the long term trims and your actual wideband reading. The fact you have -0.8% LTFT means you've got it dialed in well imo.

The beta does not, but the full release may. The staff member working on it was in hospital for a week so there will be some delays there however he will be back into it soon. BA/Single rate logging (eg > 15 parameters are once) and ZF logging all require very similar code to be written so they should all come in short succession of each other.

Everyone with the workshop version will get emailed the new link. I will reply to everyone to PMd me separately if you are using pro. Release hasn't gone out yet.

First see this thread to setup your Multi Flash Tune (MFT) Custom Operating System. This launch control system is activated whilst he cruise control paddle is held in. As you can see it goes from 2psi without launch control to 9psi. This is on a large frame GTX42 style turbo. The launch control maps are activated by holding down the cruise control paddle. The goal here is to build as much boost as possible and reduce torque to stop the vehicle braking through the torque converter or revving too hard. WARNING This system can destroy turbines, valves and anything not heat shielded that is near the turbo if you do this for an extended period of time. It is recommended to be used for a few seconds at a time at the drag strip. If you have a cracked exhaust manifold, housing or snapped exhaust studs this will amplify the problem in a very short period of time. If you have weak valve springs this may also cause the lifters to pump up and cause a lumpy idle immediately after using the launch mode. If you use this system then immediately turn the vehicle off you may cause the turbo bearing shaft to droop (due to it being so hot it bends) this will then destroy the turbo next startup. Ensure you cool the turbo and engine down for at least 5 minutes after use. This can also melt catalytic converters possibly blocking your muffler, ensure it is only used with an aftermarket exhaust. This system should only be set up for customers vehicles who have been explained the risks and know when to use it, similar to using a 2-step or transbrake. First ensure your TPS threshold is setup such that the vehicle will go into open loop when in launch control Next we can start modifying the launch control spark maps. For an aggressive spark map that causes the maximum boost to be generated you could use the following. Note you would need to change the minimum spark clip to -20 to actually see these spark values. auF16593_LaunchTune_Fuel1 Now if you want to ensure the vehicle cannot stay in this region for an extended period of time you could just add a spark hole instead. In this example once a certain amount of boost has been made it will either break through the converter, or if in a manual vehicle it will just rev to redline. auF16593_LaunchTune_Fuel1 For an automatic it is recommended to set the -20 column just before the converter slip limit is reached, this way the car will reach the converter slip limit at 2500 (for example) rpm, hit -20 degrees, lose torque and drop rpm, when the rpm drops the timing will increase bringing it back up. This will cause the car to bounce between say 2400 and 2500 rpm like a limiter. If you set the timing negative too early, the car will not get high enough on the converter and will not build boost. For the launch fuel map you can go fairly rich, I found the engine will misfire much below 0.74 lambda, when cold even 0.78 will cause a misfire at times. For late model FGs you will also likely need to set up the following to remove the factory torque limits when launching the car. Beware doing so may result in broken driveshafts and axles if they have not been upgraded. auF0172_LaunchTune_Fuel1 Regarding cam timing we can use a fairly aggressive overlap of 30-35 degrees. Ensure you set both Max Overlap tables auF16492_LaunchTune_Fuel1 auF16503_LaunchTune_Fuel1 For the wastegate duty cycle we recommend zeroing the duty cycle at high revs to ensure you do not overboost. Note on a stock gt3582 even with 0 duty cycle you can still overboost. This must be checked on the dyno to ensure it is safe. We highly recommend you DO NOT disable the factory overboost protection (eg boost sensor and tmap max volts). If you disable these settings and overboost pegging the map sensor you will lean the engine out and eventually melt a piston. auF0307_LaunchTune_Fuel1

We are happy to announce the multi flash tune (MFT) functionality using the cruise control paddles is now available. The MFT system is only available to users with the Workshop package. First we recommend you watch the demonstration of the MFT functionality here if you have not already. This demonstrates how to change the tunes using the cruise control buttons with a brief overview of what the system can be used for. Tune Layout There are 10 tunes which are switched or interpolated between depending on the setup. Base Tune (tune 1) The base tune contains all the major maps that will be toggled when you switch fuel. There is one for E85 and one for 98 Then there is tune 2. When tune 2 is selected the following maps will be switched out of the tune 1 to make a resulting tune that is a combination of tune 1 (base) and tune 2. Tune 3 and tune 2 have identical maps 2 by default. These can be used for multiple boost levels, different cam timing or different fueling. You can add other tables to these tunes if required using the wizard. Then there is the launch tune which is selected by holding the cruise control paddle down. The launch map has the following tables by default. Typically you would run low timing (-15 to -20 degrees), rich fueling of ~0.75 lambda, 30-35 degrees camshaft overlap and a modified duty cycle to ensure no overboosting. No Flex Fuel In the example of a vehicle with no flex fuel sensor you will first select the fuel via the kph on the dash when in edit mode (85kph for E85 and 0kph for 98). This selects the base tune. Then you select the minor tune (1,2,3,4) via the RPM, this selects the boost level etc. From this combination you can create E85 valet, E85 low boost , E85 high boost and E85 ghost cam, 98 valet, 98, low boost, 98 high boost, 98 ghost cam. Finally the launch control tune which could be used for normal launch control or an overboost scramble function. Flex Fuel In the example where you have a flex fuel kit installed the only difference is you cannot select the base tune from the kph edit function. Instead the kph will simply reflect the ethanol % from the sensor. The operating system will then interpolate between E85 base tune and 98 base tune based on the blend curve defined (same as the legacy flex fuel kit). Instructions for E85 valet, E85 low boost, E85 high boost, E85 ghost cam, 98 valet, 98 low boost, 98 high boost, 98 ghost cam. Create a stock file. First you need to create a stock operating system, this includes if the vehicle is already running a custom OS, you must make a fresh stock file. The following standard operating systems are supported. BA, BF, FG Mk2, FGX. If you have an FG Mk1 you will need to convert your operating system to HAEE3/4. This is due to memory limitations with the Mk1 which contains the 5R55 5 speed auto code which is PCM controlled. HAEE3/4 does not support the 5R55 hence it has plenty of free memory. To convert to HAEE3/4 follow the instructions found here. This will cost 2 extra credits which will automatically be deducted off the cost of the multi tune. Create the Custom Operating System Now to create the custom operating system you will need version 1.21 beta or newer. Once you have licensed and created your stock file go to "Custom OS Configuration Wizard" Please select "Multi Tune" then click next. If you are running a flex fuel kit please change "Multi Tune Type" to "Flex Fuel Sensor". If you are running a single fuel please change it to "Fixed Fuel". Then press next Now you can select the extra custom OS options such as "Resize spark tables" to use larger spark tables along with any other pre-options. Then press Next. Depending on whether you selected Flex Fuel or Cruise Control for the fuel type. You will see one of the two tables below. This is where you can add tables and scalars to the base tune. This is the tune that is toggled when you change the fuel type, if you have a flex fuel sensor these are this is the base maps which will be interpolated between based on ethanol content. You can add any extra tables or scalars here. Once you have added all the tables you required to the base fuel tune click next. This screen then lets you choose which tables and scalars you would like in the multi tunes. These tables and scalars are switched out with their corrosponding base tune scalar/table based based on the tune number that is selected from the cruise control buttons. Typically these are only small changes such as boost for tune 2/3/4. By default the required tables for ghost cam are added to tune 4 and extra tables are added to the launch tune. Once you are happy with these tables click "Check License and Proceed" A discount will then be calculated based on prior licenses for this vehicle. The total cost will be 10 credits. The resulting file will then be opened. See the pricing below for the full credit costs. Once the file is licensed you then need to set up the maps. This assumes you already have a 98 base tune and E85 base tune for the vehicle. First you will need to compare against you known working tune and copy the E85 tune into the E85 base map and the 98 tune into the 98 base tune. Live Tune Switching First step is to open "Cluster Configuration parameters for Custom Operating System" Next set auF100033 to 1. This will allow you to change the minor tune (2/3/4) whilst the engine is running. If you would like to also change the base fuel tune whilst the engine is running for a limited period of time you can also enable this by setting auF100034 to a setting higher than 3 seconds. This could be used if you are running dual fuels and need to idle the engine for several seconds at the petrol station to purge fuel (not recommended for most use cases). You can also change the dash sweep kph and rpm. FG is x100 so 26000 = 260 kph. BA/BF 260 = 260 kph. Here is a video demonstrating how to use the live tune switching Launch Tune Setup See the launch tune setup thread here: Tune 1 Valet Set the boost duty cycle table to 0 in both 98 and e85 tunes Modify your spark timing to suit 91 fuel in both tunes. Tune 2 low boost Modify your boost duty cycle to suit low boost in both tunes Tune 3 high boost Modify your boost duty cycle to suit high boost in both tunes. Tune 4 ghost cam Modify the VCT enable/disable scalars to -1000 (see the ghost cam thread for details) Modify the VCT overlap and VCT max overlap tables to command 25-30 degrees overlap Fixed Fuel Guide and explanation coming soon. Pricing The total cost for the multi tune system is 10 credits ($500 ex). If you have previously licensed the file you will be only charged the difference (plus the workshops labour). The preliminary pricing of the various custom operating systems is as follows: Standard Custom Operating System or Legacy Flex Fuel OS: 5 credits ($250) Boost by gear/speed. TMAP switch over logic (to allow for a 4-5 bar boost sensor and a standard TMAP sensor). Speed density map vs rpm (for vehicles with a locked camshaft to create a traditional VE style tuning map). Flat shifting TPS enable setpoint (allows manual flat shifting with injector cut out) IMRC output runner control (for nitrous or staged fuel pumps which will turn on at a specific rpm and load. Flex Fuel OS or dual maps via external input: 7 Credits ($350) Includes all features above. Dual maps (base e85 and base 98) which are interpolated via a flex sensor or switched by an external voltage input. Multi Flash Tune via the Cruise Control Buttons (MFT) Includes all features above. Launch tune via cruise control paddle 4 selectable tunes via the cruise control buttons Caveats As part of the MFT system the vehicle performs a dash sweep when the ignition is turned on. The RPM and KPH sweep causes the BCM (body control module) to believe the car is moving, this then activates the low oil pressure alarm and the seatbelt chime. We are working on masking the low oil pressure and charge fault alarms. The seatbelt warning chime can be disabled via Ford IDS, we are investigating to see if we can disable this via the editor, otherwise anyone with Ford IDS can do it for you. These alarms will only occur if you turn the ignition on and do not start the car. IMPORTANT: You must disable "Drive away locking" if you use the MFT in an FG/FGX. This is due to the fact the dash sweep will make the BCM believe the car is moving and lock the doors. This could result in you being locked out of the vehicle. For those of you who don't have a factory dash and want to use the MFT there are a few options discussed in the guide below.

Yes!

1.21 beta is almost ready. I will send you guys a link to that instead as the datalogging beta will get switched off at the same time.

We will send out an email later on when it's ready.

Think about it. 2 programmers for 1 year is maybe 250k How many F150s are sold each year? 1.1 million. How many other Fords that use this software? Maybe 4 million? How long does an O2 sensor last without the downstream sensor aging it? Lets say 2 years, how long does it last with the aging software? Maybe 5 years? $100 x 4 million = $400 million in replacement O2 sensors. Return on investment? Absolute no brainer. It isn't even a question of you can spend the money on something else, with that kind of ROI you could just borrow the money for the programmers up front and pay interest on it and still come out in front. It is cumulative as well, the FAOSC software was written in the early 2000s and still used to day, its probably saved them over a billion dollars since inception. They don't just do this with O2 sensors they do it with everything. They have a complicated airflow model that models the cooling affect of the fans on the engine in modern vehicles, this might take someone 6 months to model in tensorflow, then a programmer a few months to program it. But if the result is the fan turns on 10% less often, this means they can change the service interval for replacing the fan by maybe 10%, how much does this save them? Even if its a $5 part it is very easy to see the economics in it. This might also help explain why the software in a modern Ford is so damn complicated. There is usually a good reason behind everything you see, and that "good" reason is more dollars for the bean counters.

tuning slopes.xlsx Here you go, have a look at this and it might be of use. I did this back in 2016 so I honestly can't tell you if its completely correct however I did get my trims within 3% across the board at that time using this and lots of datalogging (several weeks of it). There is a description in the spreadsheet of how to use it. The max duty cycle (ms) is where you want fueling to be preserved, eg make this your peak torque value and it will ensure that you don't affect WOT fueling when adjusting the low slope. This is useful if you've got your WOT dyno run done but your cruise is off and you don't want to re-do the WOT fueling. edit: The main use of this calculator was to hone in on the dogleg of the injector slope, eg the breakpoint. This is if your trims are great on decel, great on medium load but off on light load (eg holding in neutral or light cruise). You probably already know this but idle is actually higher load (more duty cycle) than cruise due the fact the rpm are lower. So if you see a kink in your fuel trims when going from cruise to decel to idle the breakpoint being incorrect is usually the problem, this calc can help you shift the breakpoint in 2 dimensions to hone it in.

Great. I did a spreadsheet a long time ago that allowed me to enter in a +-% adjustment to the breakpoint and preserve the WOT fueling. Basically it would shift the low slope by the amount needed then adjust the high slope to ensure it intercepted at the same fuel mass point as it did previously for a given load. I will see if I can dig it up.

If you are curious have a read of the various patents Ford have filed over the years regarding downstream O2 sensors. They go into quite a bit of detail. https://patents.google.com/patent/US6879906 As Darryl said above the main use of the rear o2 sensor is to "age" the front sensor and measure the voltage shift over time which can then be used to correct for an old sensor which would otherwise need to be replaced. This system completely falls apart when you change the catalytic converter efficiency (eg high flow cat or huge exhaust) so you will not be going backwards by disabling it if you are no longer running the factory exhaust and cat. Chances are your NOx and CO are completely out the window from the factory specs once you do any modifications.

make a small adjustment to the cells in the aircharge VE multipler and see how you go with that. You could rescale it to fit your data as well.

When you say 5-8c are you talking about when the engine is cold or up to temperature? If the engine is still cold use the lost fuel tables, these are used when the valves and head are still cold/cool and not atomising the fuel as well. If the issue is when the car is warmed up and you experience a constant fuel trim error at all loads then you could adjust the aircharge VE temperature scalar. Beware this is a global scalar and will affect all loads including WOT.

How good have you gotten the fuel trims? Also even if you are getting transient lean/rich readings on the wideband, how does it drive? I found I was trying to perfect these conditions too much and providing they were within 10% on transient conditions the car actually drove as good as factory, so that is something to keep in mind as well. I've never actually had the oppurtunity to log a completely stock Ford vehicle, I would be curious to see how good they are from factory on transient conditions, I know at a steady state their trims will be within 2-3% which is why this is what I recommend people aim for to achieve stock drivability.

If the stock OSID is different to the one you licensed then yes it will ask you to license it again. Eg if the tuned file was HACCK** and the stock file was HACE** Send us an email with the two files and we can tell you. Otherwise you should be able to tell on the hand controller.

Just depends how you simplify the equation. I just used wolfram alpha to do it as I'm lazy. https://www.wolframalpha.com/widgets/view.jsp?id=4be4308d0f9d17d1da68eea39de9b2ce

You actually have 5, if you have no flex kit you technically have 10 tunes you can select from. E85 tune 1, 2, 3, 4, launch tune 98 tune 1, 2, 3, 4, launch tune If you have a flex fuel kit installed and you select tune 2, it will interpolate between e85 tune 2 and 98 tune 2 based on the ethanol content.