Roland@pcmtec

Hi Brendan. We don't currently have any plans for Mustangs this early. We are currently working on 2015-2020+ Mustang support which is currently in alpha status.

I've confirmed it uses a hard coded constant of 2 seconds for the timer. You would need to user a timer relay with a TOFF delay to extend the prime timer. The other values are used for plant priming when the odo is < 100km or you demand a fuel pump test from IDS.

I've been told you can simply swap them. Though I've never done the swap and have never compared the two, so the information I was given might be wrong.

Have you tried logging the items above?

For those of your who are trying to run this on Windows 7/8 whilst we don't officially support those operating systems you can in most cases make the software work by installing the Microsoft Universal C++ Redistributables package below. https://support.microsoft.com/en-us/help/2999226/update-for-universal-c-runtime-in-windows

Also, we won't stop adding and improving until people genuinely tell us it is better than any of the competitors products.

Road map for the datalogger is as follows: Mustang logging support. Alarm banners Digital/analog guages Histograms/Scatterplots (that auto populate the axis from tables) Map tracing Time estimates are basically impossible for us to give as there are just so many unknowns with software development. I'm hoping towards the end of the year we would have the above complete but that's a guess at best, it could be sooner or later.

Yes it can. You can still use a spark hole or a rev limiter (for a manual). Obviously there is no turbo to spool so the system will be a lot simpler. In the case of the 5.0 supercharged you probably actually want it to reduce power so that you don't turn the tyres. All comes down to the use case and the goal as to what the tuner will do.

For those of you who want to test this out at work here are some test files. Example of 5 minutes driving.teclog

Video demonstration

Video demonstration

I've been told that auF1716 (engine capacity) setting this to 80 will also disable traction control as it puts it into an error mode. That scalar is only sent via canbus and not used internally in the PCM. Make sure that ABS still works after doing this by testing the brakes somewhere safe like a gravel carpark. Try that if the suggestions by Darryl do not work as the Mk2 and Mk1 FG are quite different in terms of how they communicate via canbus.

Your FUEL_PW uses different units that are seconds. Either change your log to ms, or change the scaling to suit. edit: Just looking at that scatter plot its immediately obvious that your injector offset and high slope need major changes of ~15%

I don't have a vehicle with a ZF to test with but there are several scalars in the ZF that look promising. Connect to the TCM and browse through the various shift map related scalars. Here are some ones that look interesting. TID000568 - Actual Number of used shiftmap TID002575- Current active shift (code) TID000357- ID of used shift pattern TID000351 - Actually used shift pattern

New documentation on the datalogger is available here.

Change your axis scaling so you can see the actual values.

You can use the manual ABS module and set the speed input to be ABS via CAN. Otherwise a speed input on the back of the output shaft will do.

It should do in almost all cases. Eg it will cut all boost on detection of overboost, it will also have knock control kick in to pull timing if it detected knock. It is very hard to kill these motors with a stock tune.

Version 1.22 is now out of beta and has been released. Download here for registered users. https://www.pcmtec.com/downloads Version 1.22 brings the following new features. Custom Operating System Chime fix. The custom operating system no longer shows the "low oil pressure" and "charge fault" warnings during the dash sweep. To enable this new function please open your existing file, open the custom operating system, press next all the way to the end re-creating the file (this updates the firmware) and the new file will automatically have this update applied. Datalogging: The datalogging package has had a huge number of improvements and bug fixes over the past few months. If you used the earlier beta please download this update. Some of these features include the following: ZF Datalogging (templates are in alpha status with almost 4k parameters available to log) Configurable units Configurable scales Exportable layout files Auto range improvements Auto connection of vehicle and auto re-connect on key cycle/flashing etc. Poll rate of single rate DMRs massively improved (poll rate can be see via right clicking, column chooser, selecting rate) Fixes for auto range, zooming, changing units, auto connect, enumerated display Unlimited number of channels can be logged (update rate slows the more you add) DLP 8 Channel Analog Digital (DLP-IO8-G) added with voltage lookup table and configurable units Ability to sort scalar list entries, adjust number of decimals Right click assign chart positions for each channel Added playback mode Ability to press/hold cursor keys or mouse to move through log when paused or on playback modes Fix for logs over 1 hour long Ability to auto pause logging, and resume between doing PCM flashes automatically allowing seamless logging, flashing, logging, etc A huge number of bug fixes and performance related improvements. The datalogging package is still under going many new features with Mustang datalogging coming soon, histograms, map tracing, gauges, alarms and warning banners. There are many new shortcut keys documented here: Editor Changes The editor has had a round of performance and memory usage updates. This will improve the performance on older laptops, especially with the Custom OS Wizard. Colour Changes Scalars/Tables that are different to stock are now shown with a red icon in the navigator, this makes it easy to quickly identify which parts of the tune have been modified. Delta Colour Mode A new delta colour mode has been added. This mode shows stock values in green, values that are less than stock in blue and values that are larger than stock in red. The colour range changes depending on how far away from stock the value is. The original colour mode can be switched back on via right clicking and unchecking "Use Delta Colour Style" The Delta colour style can also be modified here if needed. User Information User information is now stored inside TEC files. Detailed information allows full rich text editing including photos, images etc. In this example we have stored a dyno print out in the TEC file. Coming in future versions: Datalogger Updates Histograms Scatter plots Map Tracing Gauges Alarms and Alarm Banners Mustang Support. We currently have alpha support for 2015-2020 5.0 Mustangs with full read/write support including partial write on the 2018+ models. For example we have almost 32,000 scalars and tables mapped in the 2018 10 speed auto 5.0 which we will be automating to map to a similar level across all strategies. This will allow for OEM level tuning access to this platform. Templates are still in alpha status and we are making progress weekly on these. We will be contacting workshops once these are in beta status and ready for use. The alpha support for this is available in 1.22 for those with the Workshop package who wish to view their existing tunes. We also have a new employee who is working on a custom operating system for the Mustang platform. This will ultimately bring similar features as the Falcon to the Mustang platform. Including live multi tune selection (MFT), proper flex fuel support (eg ethanol sensor) and many other features. We are hoping to have this available in some form by early 2021.

Apparently Forscan can change the ABS as built data in some cases. Best option will be to just get a manual ABS module though.

It isn't as simple as just turning off a code, you have to tell all the other modules that the vehicle is now a manual which is not trivial as the problem has nothing to do with the PCM, the dash and ABS modules will need reprogramming at a minimum. Have a chat to Whiteford, he can sort you out for this and is in VIC. https://www.facebook.com/WhitefordTech

From what I can tell its basically a time limit on when the stock flapper blows open (and hence boost drops). So the longer you can make the boost wait the higher in the rpm it will be (and hence more peak power). Eg If you have a load cell and hold it at 5k it won't matter what you do, boost will eventually drop. Definitely do what @CalFlyheight says for a nicer torque curve and better figure though. Will help reduce wheel spin as well.

New datalogger beta is available on the website. Shortcut keys are documented here

So far I've tried all the items you mentioned on there own and they work on our test BF. I don't see how the LTFT master switch would not work. Can you send me a log with the LTFT master turned off? Also can you try setting the min/max learning limits to 1.0, 0.0

I never even knew that existed. I've gone through the logic and auF0164 should indeed turn everything off from the code I can see, it will hard code ltft o 1.0 for both banks (The current LTFT).