Roland@pcmtec

We do not have a ZF custom os. There are a few companies working on a hardware solution. All of them will require box out and either an external controller or modifications to the tcm.

We have the multi tune (MFT) where you can effectively load up to 8 tunes into the PCM and switch tunes using the cruise control buttons. We don't support any proprietary flashing devices.

We don't supply tunes however there are various companies that can do it for you. We do supply technical howto guides however. If you have no plans to tune the vehicle yourself then I would recommend a mail order tune or visiting a workshop. https://www.pcmtec.com/workshops

Bill we might have to employ you soon, you are doing a better job than us at replying to these!

Yep fg is very different and it would be quite painful Ba and bf are quite similar though. They are also simpler cars.

Converting the PCM to a BF might be an option also.

Post your file and a datalog showing torque source. Alternatively try someone like custom machine works for a mail order solution. They do lots of conversion vehicles.

Renaming is supported in the beta. Press f2 or right click with show display name and you can rename the short name (what you've highlighted) Renaming the description will be available next beta update. If you have worked out what the horrid German acronyms are and found them useful submit a ticket with the IDs and names and we can get them permanently added. The ZF scalars definitely need some love. Units can be changed in bulk under the menu system. Math parameters are in the schedule, we have a math subsystem we use for the units currently which will be expanded for user input. The most time consuming part for that is building the parser that takes the 50 different ways people might type things and convert it to RPL in a manner that is performant and user friendly. I've seen some good and some terrible math user input so I want to make sure it's done right when we get to it.

The logic is a bit complicated as there is max overlap vs max exhaust cam and also max intake cam. You might have to adjust the intake cam position as well at light load high rpm to get it to do what you want. I believe there are some closed throttle scalars as well with load and tps that decide when it's in closed throttle mode.

It likely affects the VE in a small way which would likely be linear to rpm/load if you plotted it. You could most likely fudge this error in a variety of ways, tuning correction, injector slopes etc. The correct way would be to rescale the speed density offset/slope tables to suit, but that is an extremely time consuming process which requires you lock the cams at each position and datalog each cam/rpm cell in steady state on a dyno. Realistically no one would do this. What is more likely a problem is unbalanced flow across the cylinders, the stock manifold is the best and if you've used a front facing plenum you likely will need individual cylinder air mass trims, the only way to determine this is with individual EGT and lambda probes. edit: Do you mean the new plenum the intake is in the centre? If so its likely its reasonably balanced, but you never know.

The axis is shared across all of those tables. The tables do not reference each other. I'm not sure what you mean by the B series being superior? Can you explain your thought process in some more detail?

I don't believe its possible to cause valve piston interference even if you tried due to the hard stop. I am not an engine builder though so maybe someone else can comment.

The main issue i am seeing is when closed loop boost control is enabled my AFR gauge swings between 13.5:1 and 15/16:1 and will do a full swing once every second or two. You mean closed loop O2 control right? The O2 circuit purposely oscillates rich/lean to keep the cat converter working correctly. If you can show a datalog of the narrowband voltages and wideband overlaid on top this would be interesting to see. Your plot looks pretty good to me, if you don't look at the datalog and the car drives smooth with no stalling I would call it a day. If you ever get a stock car do the same logging and you may be surprised how good yours is. I suspect there are hardly any cell counts at the 0.95 region?

For anyone interested this is the charting library we use. So anything shown on this page could technically be done at some point. They have an interactive demo you can download as well. https://www.arction.com/gallery/

I think we actually started out like this and decided the split was cleaner. But its probably reasonably easy to enable something to let you select Kirby made this in paint, is that what you mean? Or the axis as well? or just the axis?

Support for all 2.3T, 3.7 NA, 3.5T, 5.2NA, 5.0NA and 5.0 Supercharged 2015-2021+ F150 and Mustangs with other Fords coming after release. Approximately 2500 strategies and 350 operating systems across 5 different CPUs we have mapped so far (Falcon was only 165 operating systems over 2 different CPUs). We then plan to offer the Falcon style multi tune on with full mapping support (eg 30k parameters). To do this we have had to spend the last 2 years with 3 new staff writing various tools to automate mapping and naming about 80,000 different parameters. It is incredibly time consuming doing this whilst supporting the existing business but we are almost complete with quite a few shops beta testing it now. The other major project has been the new datalogger and 2.1 Falcon template renaming (new naming, units and descriptions for about 5000 parameters in the datalogger and editor).

Just an FYI if you do this, the equation for NA offset is inverted vs the turbo equation. So if you copy the turbo values to the NA values, you need to invert the offset. Eg as follows. Why Ford did this I have no idea as it makes no sense, it looks like a programmer changed the sign for some reason by mistake.

We won't be doing any further discounts for the full workshop product. We would like to release a single use workshop edition next year (time pending) where you get workshop access to a single vehicle for a discounted price, however we have several other projects on which are consuming all of our time at the moment so we don't have a timeline for this.

This is from a recent support ticket and we thought it might be interesting information for some people. In the Mk2 and later models of Falcon Ford have changed the smart alternator settings to improve fuel economy. Here is a screenshot showing some of the changes they make. As you can see its a fairly drastic drop in commanded voltage and what is considered low voltage. If your injector deadtimes are not correct at these lower voltage this can cause issues with cranking. Also if you have large fans that kick in before the alternator has kicked in you may have stalling issues. These problems can come about if you are changing to a newer strategy or operating system.

Enables wastegate control, enables the boost input sensor, closed loop boost control and turns all the associated over/under boost logic and fault codes on. If you have a boost sensor and boost controller it's a must for it to operate properly. If your pcm is not a turbo pcm and lacks the boost output it's cheaper to replace the pcm than to buy an eboost and tach adapter.

Have a look at the release notes. There have been some big updates to the datalogger performance. Check your version against the release notes listed.

Are you using the latest version here? Use help about and check your version. www.pcmtec.com/alpha-release Also if you can list your system specifications.

The poor man pays twice! Good luck with the project.

We are aiming for public access to the beta when our next sprint finishes (we are doing fortnightly alpha releases). I would like to say the end of October pending any unknown major issues that we don't yet know about. This will only be for the workshop edition initially until we port all our new naming and parameters over to professional/enthusiast levels which should come soon after. If you have the workshop edition and would like to trial the alpha please get in contact with us. The requirement is that you actively participate in the beta program by sending in high quality bug reports with regular use of the software (at least once a week).