Roland@pcmtec

Do what they do in the US and you spend months doing a tune for specific sets of parts, then you sell that tune 100s of times. That is the only real way to do tuning on modern vehicles due to the time required. Unfortunately as the cars get older the results become less and less repeatable.

Most tuners turn it off for a coupled of reasons. Firstly they don't have time to tune the closed loop PID to stop it occurring, another reason is most guys are maxing out the internal gates and they can boost spike fairly easily putting the car into a limp mode. You can't really tune this out of the car without modifying the turbo which may be out of the price range for the customer. Setting it quite high but not out of range is what I would suggest if you are time limited (eg most shops). edit: Another reason (which I completely disagree with) is some tuners peg the map sensor (once again budget reasons) and tune the car like this, this makes for a very poor driving experience due to low boost/midrange being very rich, obviously if you are pegging the sensor though you have to turn off overboost. If you don't have time or the parts this may be the only way to make the power desired.

To mask Dtc codes. It's the same as putting sticky tape over the lamp in the dash.

Enter the tear tag into the create stock file wizard and it will automatically download the correct tcm strategy if we have it mapped. If it's not available post the strategy here and we can look up if anyone else has licensed this strategy previously and if there was a corrosponding tcm licensed at the same time. Not a 100% guarantee it's the right one but it probably is.

That PCM should be good to use. Datalog your boost pressure input IBP and all of the various IBP fault codes. You can also datalog the raw voltage.

You can always purchase the enthusiast version then pay the difference to upgrade to professional later. This is an instant upgrade available via the webstore. Professional has the VID block editor and ZF access which you will be unlikely to use. You may want to access the boost control PID parameters and more advanced parameters in professional later on down the track.

The workshop edition may be able to achieve this. Can you give a bit more information, eg an OSID, what the starter check specifically is as it is not something I've had much to do with.

This forum is for general community support. We do visit and read the forum from time to time, however for any tech support requests specifically regarding the PCMTEC Editor and Datalogger package please raise a support ticket and we will get back to you ASAP. https://www.pcmtec.com/contactus Please use the urgency field if a ticket truly is urgent and include as much information as possible. Eg what you have tried, what you expected, what actually occured. Include tec and teclog files if relevant. Also please use the Help -> 'Upload Files To Support' -> 'Send Editor Log Files to Support' function in the editor. If the tech support request is regarding the datalogger please also use the "Send Datalogging Logs to Support" and this will include all of your layout files so we can reproduce your issue. Cheers!

I'm not 100% they have the boost drivers. Do you have the part number? I think some of the LPG ones did but not all.

That's why you often see 6 copies of the same variable, depends how many departments wrote blocks of code that need the same thing. Some of the code in the modern mustangs is shared all the way back to the 90s and uses the same struct definitions and even table values. Then you have 5 different tables types, Bosch tables (knock and low level stuff), old 90s ford float tables, modern ford uint16 tables with built in equation coefficients to turn them back into low effectively half word floats to save memory. Then you also have code and tables that are clearly simulink generated and absolutely impossible to follow the asm due to the incredibly inefficient code that it outputs.

You could read as high as you like. It's a simple floating point number based off speed density and the map sensor. As long as you can read 60psi on your map it will work just fine. Technically you could have 20000psi and it would work.

Is your cam timing oscillating? Show us a datalog of it happening and post the file up. It might be hitting the anti stall or the cam might be oscillating more than you want due to your load kicking it out of the overlap then back into it. If the cam is oscillating all you need to do is datalog what load and rpm it occurs at and adjust the cam timing there. If you find the rpm is dropping too low hitting the anti stall I would reduce the overlap and put -30 at say 600rpm as your own anti stall to stop it going that low. Anti stall kicks in at about 350rpm from memory.

Yes I believe you would have some weird issues due to not copying everything over. We are releasing a new product which you might be interested in however.

Contact support and we can sort it out for you.

We are all for it. We don't have them for sale retail yet but I think @Kirby@pcmtecis looking into it. Most of the workshops should have been sent some already if you are friends with any of them. Also feel free to print any of the artwork here personally

Put a completely stock tune back in the car and then change only the items in the guide.

Data log torque source, throttle source, spark source, knock, commanded lambda, LTFT, and plug in your wideband. Also do a dtc read with forscan

Disabling the torque module switch will definitely cause lots of issues and its highly unrecommended.

Post your file and a datalog up in a seperate thread.

Yeah in the custom os we have literally replaced the code references to the original stoich value so it does nothing at all. We were thinking about hiding it from the template as it's been a point of confusion before.

Have a read of this https://forum.pcmtec.com/topic/264-cold-start-e85/ Due to the poor atomisation at cold temps you need up to 400% fuel enrichment on cold start in the first few pips In the f150 at e100 -30 deg they command 1400% more fuel on cold start.

auf100014 replaces auF0117 in the custom os. The correct stoich for e85 is 9.765 not 9.81

The 5.0 supercharged V8 uses a different knock strategy for tip in spark knock control. It's not something you should change.

If you can find something now definitely order it as this may be due to a chip shortage that is out of everyone's control. Dont hold off as I have no idea if we or anyone else can order these in any quantity. Alternatively we are investigating an analog canbus solution such as the following so we don't have to worry about ground offsets etc. This could realistically be months away however. https://www.aemelectronics.com/products/cd-digital-dash-displays-adapter-harnesses/aemnet-can-bus-expansion-modules/6-channel-can-sensor-module

That is news to us! I'll see if we can arrange a bulk order. They used to be available in regular stock.