Roland@pcmtec

Yes you can invert all of the boost settings. Eg switch the overboost to be 1 and underboost to be 0. Then invert/flip all the other tables. Alternatively you could invert the valve as well so it operates in reverse. This might mean it is no longer fail safe however.

It is hardcoded as inHG (inches of mercury). This will be fixed in the next update (2.00) In the mean time you can log MAP pressure which can be changed to PSI. This will be referencing 0 not atmospheric however. So 14.7psi will be 0 psi and 29.4 will be 14.7 psi etc. Alternatively you can use the unit converter or google "30inHG in psi" for a quick answer.

Only what is listed is possible if you must use an external switch. Highly recommend using the multune as the options in this thread are fairly redundant and obsolete now, use a CANBarra module with the cruise control buttons wired up.

Could the cam timing have skipped a tooth? That is great news that you have the inferred load that close, almost no one bothers to do that. In that case it will probably do what you need. The fact this engine is not turbo and has no VCT really helps as well. The approach you are taking would not work on a VCT turbo 6 as the load can change drastically at the same throttle position whilst the turbo spools up, the NA v8 will have almost no transient change in VE for a static throttle position.

Alpha N means throttle vs rpm. Eg very old school tuning method. It is not load on the y axis so it absolutely does not line up with the load from the logger. It is inferred load calculated from the failed maf table which has throttle position vs rpm to generic a fake inferred load. Regarding bank2 being out it is probably a blocked rail/injectors. Seen old engines sitting around for months rusting up and then partially blocking injectors before. I would pull it all off and flow bench/clean the injectors/rail as these cars are getting on now.

Problem: You need to change the serial within a Custom OS file due to a failed PCM. As the Serial and VIN are embedded within the Custom OS the firmware they cannot be changed using the normal methods and the Custom OS file must be be recreated. Solution: We create a new stock file and re-run the Custom OS Wizard via the following steps: The guide assumes your previous Custom OS file has been named as "Previous Custom OS.tec" This guide will require that you fully relicense the new file as part of the steps. If this is a Multi Tune it will require 10 more credits. We can refund these credits AFTER the process has been completed by contacting support. If the previous Custom OS license is refunded/deleted prior to completing this process the procedure will not work. Firstly we must read the new PCM and save it as "New PCM.tec" DO NOT LICENSE THE FILE. Close the file. Press Calibration Tools -> Create Stock File/Calibration Merge Select "Create Stock File From Existing File" then load your previous custom OS tec file. Press "Save/Open File" and save the file as "New Stock File with old serial.tec" Press "Compare/History" -> "Load Compare File" and load the previous Custom OS file that you are recreating ("Previous Custom OS.tec") Click anywhere within the compare tree view then select all items via Ctrl + A then pressing space. Once selected press "Apply" to copy the values over to the stock file. Now we must change the serial to that of the new PCM. Save the file as "Stock OS with values copied and old serial.tec" Close the file. Ensure you have a read of the new PCM saved as "New PCM.tec" DO NOT LICENSE the new PCM yet. Close any open files. Open Calibration Tools -> "Create Stock File/Calibration Merge" Select "Manually Merge VID/Serial" Press "Load File 1" and select "Stock OS with values copied and old serial.tec" Press "Load File 2" and select "New PCM.tec" Press "Import PCM Serial from File 2" Press "Save File 1" and save as "Old PCM with new PCM Serial.tec" Open "Old PCM with new PCM Serial.tec" License the file. Step 2: Create the Custom OS Select "Calibration Tools" -> "Custom OS Configuration Wizard" Press "Load All Defaults From Existing File" from the bottom left hand corner and select the original Custom OS file that you are recreating "Previous Custom OS.tec" The wizard will now replicate your previous file. Review these settings to make sure they are what you expect. Press Next and review the next page (depending on what type of custom OS you created you may not see all of these page or options). If you are recreating a Flex/Multi Tune you will now see the table selection page. The tune and table setup should match the previous Custom OS. Review the table/scalar setup to ensure it matches what you had previously. Press "Check License and Proceed" and save the new file as "Custom OS re-created with stock values.tec" Press Next and exit the Custom OS Wizard. Now press Compare/History -> Load Compare File and load the previous Custom OS File. "Previous Custom OS.tec" This is the same process and steps as you did earlier in the guide and will copy over the flex/multi tune tables. Once again click anywhere within the compare tree view, press Ctrl + A then space to select all of the previous Custom OS tables/scalars. Finally press Apply to copy them over. You will now have a freshly created Custom OS with a different VIN number. Press File - Save As and save the file as "New Custom OS with new VIN and all values.tec" Flash the file into the vehicle. Please contact support via https://www.pcmtec.com/contactus and we will manually refund the credits required to relicense the replacement PCM, please include the VIN, vehicle type and what failed on the PCM. Please note that for new customers we may ask for proof of the PCM replacement as this process could be abused. Finally follow step 7 from the generic PCM replacement guide:

Problem: You need to change the VIN within a Custom OS file. As the Serial and VIN are embedded within the Custom OS the firmware they cannot be changed using the normal methods and the Custom OS file must be be recreated. Solution: We create a new stock file and re-run the Custom OS Wizard via the following steps: The guide assumes your previous Custom OS file has been named as "Previous Custom OS.tec" Press Calibration Tools -> Create Stock File/Calibration Merge Select "Create Stock File From Existing File" then load your previous custom OS tec file with the old/wrong VIN. Press "Save/Open File" and save the file as "New Stock File.tec" Press "Compare/History" -> "Load Compare File" and load the previous Custom OS file that you are recreating ("Previous Custom OS.tec") Click anywhere within the compare tree view then select all items via Ctrl + A then pressing space. Once selected press "Apply" to copy the values over to the stock file. If you wish to change the VIN you must do it now via locating Navigator -> Strategy -> Vehicle Identification Number and entering the new VIN. Save the file as "Stock OS with values copied and new VIN.tec" Step 2: Create the Custom OS Select "Calibration Tools" -> "Custom OS Configuration Wizard" Press "Load All Defaults From Existing File" from the bottom left hand corner and select the original Custom OS file that you are recreating "Previous Custom OS.tec" The wizard will now replicate your previous file. Review these settings to make sure they are what you expect. Press Next and review the next page (depending on what type of custom OS you created you may not see all of these page or options). If you are recreating a Flex/Multi Tune you will now see the table selection page. The tune and table setup should match the previous Custom OS. Review the table/scalar setup to ensure it matches what you had previously. Press "Check License and Proceed" and save the new file as "Custom OS re-created with stock values.tec" Press Next and exit the Custom OS Wizard. Now press Compare/History -> Load Compare File and load the previous Custom OS File. "Previous Custom OS.tec" This is the same process and steps as you did earlier in the guide and will copy over the flex/multi tune tables. Once again click anywhere within the compare tree view, press Ctrl + A then space to select all of the previous Custom OS tables/scalars. Finally press Apply to copy them over. You will now have a freshly created Custom OS with a different VIN number. Press File - Save As and save the file as "New Custom OS with new VIN and all values.tec" Flash the file into the vehicle.

1. No engine braking. When down shifting I get no engine braking. (The revs increase but road speed stays about the same). Having read this forum I understand that L/100 should read 0.0 when on deceleration but I get around 4-5L/100 depending on RPM. Sounds like DFCO (decel fuel cut) is either disabled or more likely it is not working due to excessive load (air leak is the most common cause). If the car is tuned I would advise returning the tune to stock and see if it goes away. If it is not tuned then you have a mechanical issue and I would smoke test the inlet. Not all tuners have a smoke pressure test machine so ask this question. 2. This is related to the above. 3. Is there an ability to have the standard Launch Assist for take off WITH added Flat Shifting capability? Yes. See a video here of it in action. 4. Valet - Low boost setting via switch (I understand this is possible and cheaper than multiple tune options via cruise control buttons) How does the switch wire in so I can save the tuner time doing it myself. It is not really cheaper. You are talking $350 vs $500 in credits but then the labour to wire up a switch etc. Most tuners do not have time for this and if you do it there is a chance they will have to diagnose any issues you've created. I highly recommend against this. The only real reason to use the switch is you don't have the original ford dash (eg a conversion car) or it needs to be an electrical trigger due to nitrous or a mechanical transbrake switch. 5. I would like to purchase PCMtec to play with launch and traction control settings. Will Enthusiast or Professional be able to access these settings and will a tuner be willing to leave their tune unlocked so I can adjust non air/fuel related parameters? Most of the basic stuff (DFCO) etc can be accessed however you would need workshop for any of the custom OS features. Most tuners will lock the tune if they think you will be playing with it after. Either pick a tuner you trust, or go all out doing it yourself. Note is is not cheap to do yourself as you require a lot of equipment to do it properly. Send us a support ticket with what state you are in and we can recommend a tuner which will give you the level of care you are after. If you want to be part of the tuning process etc with the tune left unlocked they will likely charge more as it will take more of their time and more risk on their part (as you will likely need to test drive it a few times to confirm it is exactly how you want), but it sounds like this is what you want and you will likely end up paying twice otherwise so I would recommend you spend a bit more to get the result you want the first time around.

This functionality has been available for over 2 years now! FYI your current values may not make sense currently as that table you are modifying is throttle position (inferred load) not actual load which would explain why you are having funny results. Tuning correction is basically an Alpha N correction table. All your other values will remain, you can always copy them back.

It should not even require an ignition cycle on the BF/FG. If it does you can usually do it in 1-2 seconds, but 3 is what is meant to be required by the PCM. I would lean towards shorter rather than longer.

The unit converter is wrong. KPag = kpa - 101.325 The log is correct. I wasn't aware anyone was using the unit converter, it was written a long time ago before we had any QA system so it looks like the equation is back to front.

Can you attach a log showing which values are being logged and what units have been selected.

Could save yourself a lot of time if you use this feature! Sounds like you have it pretty close now anyway. The reason there is hardly any information on tuning cams is because hardly anyone actually knows how to do it properly in these cars. The main reason as you found out is a total of 0% of customers are willing to pay the tuner for the time required to do it properly.

Either providing the cams are locked.

Have you tried following the guide? It is very difficult to do remotely as it needs some trial and error to get it as the owner desires.

Do you have the workshop edition? This requires our custom os which is only available with the workshop edition.

https://forum.pcmtec.com/topic/561-howto-full-independent-vct-cam-control-in-ba-6-cyl/

So stock tmap and a 4 bar boost sensor?

What boost sensor are you using and what boost sensor scaling?

I'm not sure what the issue is here. Both statements make sense. KPag is simiply kPa + barometric (roughly 101.325 kPa)

You can log IBP which is your actual boost pressure instead of logging map. What map sensor and map scaling are you using? Make sure your units are correct as well. Some of them are in inHG and are not currently configurable in 1.25 Also are you using the tmap switch over logic in the custom os?

This is one way to prevent kick down ZF00117 "Minimum throttle value to detect kick down" Set this to 100.4

Go to the rear O2 sensor tree entry and look at the scalars there. When I'm in the office I can look up the ids but it should be easy.

I'll put the reply here as well regarding poll rates. The way the datalogger works is you get 15 rapid packet polls, these update at roughly 50ms. Then every thing else after this is polled as fast as it can, eg if you have 16 items you are logging, the 16th item will still log very fast. If you have 60 items, the 45 items after the first 15 will log quite slowly, roughly once a second. We get a few 'freebies' that are broadcast data and always log fast irrespective of whether they are set to high priority. These are engine rpm, oil temp and a few others. This is something only we do, other companies don't take advantage of these. If you are very curious about how it works you can right click on the name column, select column chooser, scroll down to 'rate' and add this column. This will show a number which is number of updates per second. For a fast dyno pull you need at least 250ms updates for rpm, boost, load, knock for it to be useful, otherwise the values will not line up and you will miss spikes of knock etc. In future versions we will be setting high priority by default on knock, rpm, cam angle etc. Currently it has to be done manually if you have selected over 15 items.

The way the datalogger works is you get 15 rapid packet polls, these update at roughly 50ms. Then every thing else after this is polled as fast as it can, eg if you have 16 items you are logging, the 16th item will still log very fast. If you have 60 items, the 45 items after the first 15 will log quite slowly, roughly once a second. We get a few 'freebies' that are broadcast data and always log fast irrespective of whether they are set to high priority. These are engine rpm, oil temp and a few others. This is something only we do, other companies don't take advantage of these. If you are very curious about how it works you can right click on the name column, select column chooser, scroll down to 'rate' and add this column. This will show a number which is number of updates per second. For a fast dyno pull you need at least 250ms updates for rpm, boost, load, knock for it to be useful, otherwise the values will not line up and you will miss spikes of knock etc. In future versions we will be setting high priority by default on knock, rpm, cam angle etc. Currently it has to be done manually if you have selected over 15 items.