Search the Community

Problem: Running more than 2.5 bar of boost requires upgrading the boost and TMAP sensor which is expensive and can often cause drivability issues due to the decreased resolution of the new TMAP sensor. Solution: Utilise our custom operating system and the "TMAP Configuration" feature which allows you to use a 4 bar boost sensor (or larger) with the standard 2.5 bar TMAP sensor. This adds logic to switch the speed density calculation over from using the TMAP sensor to the Boost sensor for it's calculation above a voltage set point. At high boost levels the air velocity is high enough there is no perceivable signal lag between the two sensors. This means you can retain the standard TMAP (cheaper and simpler) with it's factory resolution but still have full closed loop boost control at high boost levels with the standard fuelling model. To enable this feature you require the workshop edition and a 5 credit "Standard Custom OS". This is an extra 2 credits on top of a standard license. First open the custom operating system wizard, select "Standard Custom OS" and press Next. You will then see a "Custom OS Options" page, leave these values as the standard values. Press "Check License and Proceed" which will then ask you to license the file, this will charge you an extra 2 credits (totally 5 for the vehicle). This will only be charged once. You will now see a second set of Custom OS options (these can be changed as many times as you like). Select "TMAP switch to Boost sensor after TMAP_Volts" from the "TMAP Configuration" drop down menu. Press Next then "Finish" and the file will automatically save and re-open. Now navigate to "Custom Operating System Configuration" within the navigator and locate "Voltage to switch from using the TMAP sensor to the boost sensor". Now enter a value of 2.5v into auF100000. 2.1v is roughly 150kpa or 4psi of boost. If you leave the standard value of 15v this will effectively disable the switchover logic. This means the sensor used in the speed density calculation will switch over at 4psi. You MUST have your boost sensor slope/offset set up correctly for the transition to be smooth. If you are unsure if this is case log both boost pressure and MAP pressure and ensure the values are equal at this boost pressure. If they are not either rescale your boost sensor or increase the voltage to where the two sensors become equal. Ensure you have adjusted your TMAP max volts to above 5.0 V (TMAP sensor will peg at about 250 KPa but Bosch sensors are rated to work in an environment up to at least 5 bar). Change these settings (Speed Density -> Scalars): We also changed the "Boost Sensor Volts Max Value" to stop it causing a failure mode on overboost. You could set it to the voltage reading to a point slightly above the maximum boost you want to run to put in a safety margin in case of a hardware failure (like a wastegate jammed shut). If you purchase a 4 bar boost sensor from Independent Motorsport they can provide you with a PCMTEC parameter file with the slope and offset required. https://www.independentmotorsports.com.au/bosch-map-sensor-4.0-bar-0-261-230-046-ford-xr6-bo

Update: This guide is obsolete. Please read the guides here. With the release of 0.75 PCMTec allows Workshop customers to create a Custom OS from an existing licensed tune. The first release for the Custom OS to Customers will configure by Default: Dual MAPS Resized Spark Tables TMAP Change over to boost sensor Automatic Gear Change Fix for WOT gear changes Basic Flex Blend ramps Conversion table from %Alcohol to Stoich After this is configured you will then have some options to alter the configuration to: Disable/Enable TMAP switch logic Change Boost table to use Gear, Vehicle Speed or default Intake Air Temperature Step 1: Configure Basic Custom OS and License the Custom OS. Open your existing licensed calibration and in the Navigator go to "Custom Edit" -> "Enable Custom Operating System" The following message will appear: This message informs you the Custom OS has been configured and you will need to save this file in order for it to be licensed and activated. Press OK and then use the Save As to save the file. DO NOT OVERWRITE your existing tune. Keep this tune as the basis for making different versions of the custom OS or as your last tune before you went to a Custom OS. In this example I saved the Custom OS as MyCustomOS_HACH3CA_Version1.tec . Close and now Open the file you saved away. Finish preparation by licensing the file. Step 1 Complete, you are now ready to configure your Custom OS. Step 2. Configuring your new Custom OS. After you Reopen your Custom OS created in Step 1 navigate to the Custom Edit tree entry and browse the new entries that can be configured: The tables you see in the above screen shots have been "Dual" mapped. These are the ones that will be activated or blended to depending on your configuration. They are copy of the primary tables used by Ford. If you have the flex fuel kit from Danny then you can load the parameter file and start tuning. If not then then you must change these two calibration entries. Under System Switches -> Scalars Change auF0010 to 1 and auF0011 to 0: Step 3. Getting the car started. Configuring the Custom OS to use one map or the other. In order to select a single MAP for tuning your vehicle you only need to edit the "Voltage to % Ethanol Conversion" table. Make the % Ethanol 1 for tuning the High MAP (E85 on Flex Fuel cars) and make it 0 to select Low MAP (98 on Flex cars). This configuration shows the car setup to use the High MAP: This works in conjunction with the Stoich Table which should be setup like this: The default config has 100% ethanol as being stoich 9.078. As can be seen if you make the Voltage conversion table always return 0 then the stoich value would be 14.64. In this case ensure you car has E85 in it and then you can start tuning in the HIGH MAPS (Custom Edit tables). Merging existing tunes. If you have a 98 tune and an e85 tune for the car already then you can quickly merger the two tunes. Open each tune and convert them to a custom OS. This allows for the Spark table resize so you can compare them later. Say the 98 tune is converted to 98_CustomOS.tec and the e85 is converted to E85_CustomOS.tec. By starting with the converted E85 tune as a base you have populated the HIGH MAP tables with the correct values. Close all tunes. Open E85_CustomOS.tec Click Compare History Load Compare File and select 98_CustomOS.tec Now tick and apply the LOW MAP tables from the compare/history view to the tune. Save the tune away as a new tune.iframe widget