Roland@pcmtec

Play with these Commanded lambda at crank auF0180 auF0181 multiplier to cranking lambda. This is per PIP. A pip is an individual cylinder fire. Eg column 18 is after 18 cylinders have been fired from cranking. This effectively decays the commanded lambda from very rich to the actual commanded value. Cranking spark advance auF0209 I've never tried modifying this one, but it makes sense to modify it as the flame burns slower with e85 beware of going too high as you can get detonation whilst cranking due to the very low rpm. Not the end of the world but best to avoid. Then the base fuel table when the engine is cold auF0173. Make sure the bottom row is the same as the bottom row in your base fuel table. The numbers in the example above work ok as a base, but definitely need further tweaking. I have it starting first crank at 8°C in SA however at ~16°C it takes 2 goes, unsure if it needs more or less fuel as its been too warm to properly test. I will optimise it this winter and possibly do a proper write up then.

275/45/19 is a huge tyre, definitely not 35 profile? Got a picture? I'm quite curious how it even fits! I have never seen that code before so I'm not sure however it seems plausible it is the cause. I would try putting other wheels on as a test if you have another vehicle handy. u1900 is meant to be CAN message missing, so either the ABS is going into fault and stopping comms due to the wheel size error, or it some vibration at high speed causing a connection to come loose. I would be betting on either of those.

I would like to add individual USB/Serial support later however initially we will simply support the IO8 cable. So in that case you will need to run an analog wire to it along with a ground. Analog inputs are prone to ground offsets, so the serial direct from the AEM X Series will give you more accurate data, but only once we support it. This support will depend on how many workshops use them and request it so 0-5v input will be what you need to wire up.

Does it happen exactly at 100kph? Do you have different sized front and rear tyres?

We now have 2:1 printable banners and all of our logos available for download. We are looking at organising our own printing however you are free to print and display the logos below if you own the workshop software. Printable Banners: pcmtec-banner.2by1.pdf pcmtec-banner.2by1withbleed.pdf We also have SVG which you can use for T-Shirt logos and can be blown up as big as you want. Standard logo: pcmtec-logo.vector.svg Square logo: pcmtec-vert-logo.vector.svg There is also PNG which is to be used on websites and for small print. pcmtec-logo.1200px-gradient-transparent.png pcmtec-logo.1200px-gradient-dark.png pcmtec-vert-logo.800px-gradient-transparent.png pcmtec-vert-logo.800px-gradient-black.png Here is a preview. Please do not print this version and instead download the PDFs and zip file. pcmtec-banner.2by1withbleed.pdf pcmtec-banner.2by1.pdf pcmtec.logos-package-2017.zip pcmtec-banner.2by1.pdf pcmtec-banner.2by1withbleed.pdf pcmtec.logos-package-2017.zip

You don't have to license it to use it to merge from in the merge wizard. You have to license the file you are merging to.

It is just for cranking the engine. So probably no need to ever change them.

What do you mean "what are you doing with 250rpm column" ? As in what are the stock numbers?

Can you give some more information? What specifically do you mean?

For anyone who is reading the problem Puffwagon found was that our NGEN (native image installer) executed after the intaller finished and took quite some time which could appear as if the installer had crashed. It now runs asyncronously after the installer has exited so you may see 20-50 instances of ngen.exe in task manager for serveral minutes after doing a fresh install.

Occasionally you may read a vehicle only to be greeted with a checksum warning. The warning says you may have a permanent DTC or the car may not be drivable. In 90% of scenarios checksum errors are harmless. Some of the possible causes of a checksum error are listed below: Harmless causes: You have an early BA with a blank VID block from the factory Someone used Ford IDS improperly and wiped the VID block You have a vehicle which was tuned with an early CAPA flash box or other third party software which has no ability to update checksums You used recovery mode on a third party hand controller PCMTEC Editor was closed improperly or crashed. In these cases you can simply save the file and re-open it, PCMTEC Editor will recalculate and update the checksums. You can then flash the file in and the car will run and function exactly as it did previously. If the file does not open utilise a backup from the documents/PCMTEC/1.xx/Backups folder or re-read the vehicle. Causes you should worry about: The vehicle was tuned with a hand held flash tuner which had incorrectly mapped tables. You had a corrupted read due to low voltage or a faulty J2534 dongle. Your PCM flash memory is corrupted. Your PC has bad RAM which has corrupted the file in memory. In the case of a flash tuner causing the error you will see errors in the log such as "non sequential table" or "binary validation error". If you click on these errors and the table has strange numbers/dimensions this usually is due to an incorrectly mapped table in another product. In these cases you will need to make a new stock file and copy the changes over. In the cases above you can try reading the file from the PCM again and seeing if the checksum error persists. If the checksum error persists and the car does not start, you most likely have a faulty PCM or a faulty J2534 cable. If the vehicle does start and run then you most likely have a faulty J2534 cable. In this case do not attempt to flash the vehicle until you have a second cable to test with.

You have set up the axis incorrectly and missed cell no 13. The axis only has 13 values so you will have to skip one and interpolate it which is why Ford did this from the factory. Some of the axis that Ford have done are quite strange, I believe it is hangover from the days where they had memory restrictions. Because of this you often have skip cells and let it interpolate them automatically for you. Eg if you do the following rpm cell 1000 1 5000 5 This would interpolate into the following automatically and save you 4 rows (16 bytes) which adds up. 1000 1 2000 2 3000 3 4000 4 5000 5 Knowing this you should be able to get any values you want, you just have to be creative about it.

Get the stock file, use the calibration wizard to merge your VID, serial and VIN into it. Flip the oil pressure sensor scalar. Then license it and flash it in. You'll need to compare everything as depending on your car/cal it may not be completely compatible. There are no guarantees that swapping operating system will be completely compatible or work however I know of about 5 cases where it has worked without issue.

You don't need to, it will always use the PCM overrides in a mk2

If you have the VID block enabled and a car other than FG Mk2 the VID block will override some of these values afaik.

digikey will do free shipping over $60 so maybe do a group purchase, I bought 4 and got them 2-3 days later. https://www.digikey.com.au/product-detail/en/DLP-IO8-G/813-1010-ND/1894342/?itemSeq=286026595

Definitely check this out. Cat and exhaust protection will richen the motor up.

What anti virus do you have? If you can export your Windows event logs from event viewer and send them to me I can see if there is a good explanation.

1.11 can be downloaded now, ensure you are logged into the website to download https://www.pcmtec.com/downloads 0.75 will continue to work side by side 1.11 until the QA process is finished. edit: 1.11 is officially out of QA and has been released. 0.75 should no longer be used as there may be incompatibilities with the newer files.

Change the OSID and Strategy back to standard and you will be able to log everything again. Eg change PCMTY back to HACCK and change PCMTYGA back to HACCKGA This won't affect the Custom OS/Flex tune.

Made some additions to the OP

We are happy to announce we are finally into version 1.xx and have removed the Beta title! This is thanks to our QA team (Andrei) who has spent the past few months going through the software finding as many bugs and usability issues as possible. Version 1.11 brings the following new features. User Configurable Units After many requests we have now implemented dynamic units which will now let you use metric units instead of imperial! This is thanks to Scott who has spent the past two months implementing this feature. When opening a 2D table you will see the following new options available in the right click context menu. X axis - Units Y axis - Units Z - Units In the case of desired boost we have changed the Z units from inHg to psi Scalars can now be changed via their appropriate dropdown menu items. Here we have changed the injector slopes from their default of lb/s to lb/hr We also now have the ability to bulk change all units. Eg you can change the units of all temperature scalars and tables from °F to °C by utilising the new bulk change units drop down menu. Paste Special We have now added an excel like Paste Special menu to the right click context menu. This allows add, subtract, multiple, multiply by % and Y-Axis inversion (for those of you who can't get away from using other products!). Multiply by % does the following. Lets say you datalog LTFT and end up with the following errors By using the "multiply by %" when you paste, it will multiply the cells by the equivalent percentage. Eg add 1% for the top left cell and subtract 3% for the middle cells. Performance The performance of opening 2D views has been massively improved this release. You should see a 200-300% improvement in loading speed now. Stock File Downloads We have fixed the stock file download blocking opening and licensing of a file until the download has finished. On slow connections this could often block the user for several minutes. Now this is done in the background so that if you have a slow internet connection you can still continue tuning. Datalogging Whilst not available in this release we have made a large amount of progress with the datalogger thanks to our new staff member Matt. He has been busy adding USB analog input support to allow widebands and any other analog input to be datalogged. We have decided to skip the initial release of the datalogger and hold off until we have analog input support hence the delay in releasing the datalogging software. We are using the following USB analog input cable (8 analog inputs) which has been proven in the field with the Nistune (Nissan Tuning) software. The product is approximately $40 delivered (next delay delivery in Australia) which makes it an excellent cost effective analog input module. http://www.dlpdesign.com/usb/io8.php Other Improvements: Improved licensing popup message when a custom OS was enabled. This makes it clear you are paying for the Custom OS only and not being charged to license the entire vehicle again. Removed the VIN from the licensing model. Licensing is now locked to OSID and PCM Serial only now. This allows you to correct invalid or wrong VINs without having to contact support now. Silent save (of change history and partial write information) no longer updates the file date stamp, this means sorting by date now accurately shows when you last changed a file. BA Partial write now works on all flash types (some early BAs use a different internal flash chip). The licensing model has been modified to only use the Serial and Operating System ID. Previously we also used the VIN. This means you are now free to change the VIN of the vehicle without relicensing. Added "Upload currently open file" option to the help menu to allow you to easily upload the currently open tune to support. Any tunes uploaded will only be used for providing support and will remain the IP of the original user. If requested we will delete the tune from our server after providing support. Bug Fixes: Blocked user from "Exporting all changes to parameter file" when there was no stock file to compare with. This sometimes resulted in users producing parameter files with unexpected values due to there being no baseline history to compare to. Editor would crash if you changed the theme whilst a large scalar list was visible under certain conditions. Fixed rare crash when opening and saving files on certain PC configurations. Fixed the editor exiting immediately after open on some rare PC configurations. Strategy search inside of "Strategy List" would hide all filtered results, it now simply highlights them instead. Disabled the ability to perform a partial compare if either file is lacking stock file history to compare against. In the cases where one file was lacking stock history this would show strange compare results. Pasting VIN numbers into the VIN field now works correctly. Enabling custom os on a TEC file that had been previously tuner locked would remove the tuner lock. Tuner lock is now automatically added back. If you attempting to overwrite a tuner locked PCM with a stock file an error occured "You cannot merge the VIN from a tuner locked file". This is now resolved. Fixed a stock file download bug which in rare circumstances would get stuck in a loop downloading files over and over. Fixed an SSL certificate mis match warning which occured due to our hosting provider issuing a new certificate. Fixed several deadlocks that could occur locking the UI from being used. Fixed several unhandled exceptions which could occur.

LOL

I've been thinking about this some more and it seems if Ford put 0 as the standard gain value it implies the TMAP speed density system should be able to correctly fuel in all transient conditions. This suggests if you get a rich/lean tip in/out there are issues with the closed loop O2 system or injector slopes. That said, i would be a very easy way to fudge much better drivability where you cannot improve it otherwise (eg using dekka injectors etc). It seems ford themselves do a lot of "fudge" tuning which can be seeing with the "Tuning Correction" tables etc which effectively are Alpha - N style correction maps.

The upgrade to pro is only $330! If you put an hourly figure on your time it quickly pays for itself. Not to mention all the extra parameters and getting access to the VID block editor. The main reason why we stopped the zip file is we were creating it manually, it was not practical to keep it up to date so we added the automatic stock file wizard which creates fresh updated files as you need them. You can be ensured that these files are always up to date as the editor checks for updates on startup.