Below are a few points we want to mention right up front.
To use V3's storage to persistent flash, you must have a working MFI relay controlled by the ECU. By far, most cars do, but some purpose-built track cars may not.
There are a significant number of keyboard navigation controls you can use while working with a datalog. Try to familiarize yourself with these.
Try to work with the datalog using the new zooming features. This makes navigation through a log extremely efficient. Refer to the datalog help section for more details.
Direct Access can be intimidating. Don't let it be. You can always revert back to stock if you find the changes you've made aren't working out.
You can make changes to ECU settings in one tab while a datalog is being captured in another. However, the ECU settings that will be recorded with the datalog will be limited to those in place at the time the datalog was started.
There are a few points we wanted to mention specifically for those upgrading from V2 (or V1) to V3.
Generally try not to assume things work the same as V2 or else you may miss many new V3 features. An example would be the auto-filenaming function. In V2, this was much more restrictive and hardcoded. In V3, you have a lot more control over this in the application preferences. There are several other examples too. The point being, try to approach this application as a completely new product (because it really is).
Unit display preferences are configured in one place (Edit->Preferences) rather than being scattered out among the different display items on a graph.
Input pins assignments are done entirely differently in V3. Refer to the ECU Inputs tab in the ECU Config area.
The MAFComp table is (and always has been) indexed by MAFRaw. When you connect a GM MAF directly to the ECU input, MAFRaw is a LOT different from what you�re used to with a Mitsubishi MAF (you will be idling in the 500hz area, for example!). You need to view MAFRaw to note its value in the areas where you�d liked like make adjustments.
It's probably a good idea to leave the old V2 application installed after receiving the V3 upgrade package because the V3 application does not (at least currently) read V2 datalogs or .ecu files. That means to transfer settings into the new V3 setup, you will need to run the old V2 application and load your datalogs or .ecu files into it and manually copy over the settings you see in that application over to the new ECMLink application.
© 2002 - 2023 ECMTuning, Inc. All rights reserved.