MPVI2, 2+, AND 3 STANDALONE DATA LOGGING
REQUIREMENTS
| ￭ | MPVI2/2+ with Pro Feature set or MPVI3. |
| ￭ | VCM Scanner 4.9.238 or higher. |
| ￭ | MPVI2 must have firmware v3.1.2 or higher. |
SETUP
| 2. | Connect your MPVI2, 2+, or 3 to your computer with the USB cable. |
| 3. | In the menu bar, select Help > Resync Interface. The firmware will update automatically. |
NOTE: If you are using an MPVI2, standalone data logging is only available if the device's firmware is v3.1.2 or higher.
| 4. | In the menu bar, select Vehicle > MPVI2 Data Logging. |
| 5. | Click the Resync Interface Resources button. It will take 10-15 seconds to update your interface device. |
| 6. | If you want to send your current channel configuration to the device, click Write Channels Config. Otherwise, leave it set to Vehicle Defaults. |
CONFIGURING START TRIGGERS (OPTIONAL)
By default, a short press of the BT button on the device will trigger the start of logging. If desired, you can set up triggers to start logging automatically based on the vehicle's acceleration).
| 1. | In the menu bar, select Vehicle > MPVI2 Data Logging. |
| 2. | Select the Start/Stop Triggers tab. |
| 3. | If desired, select either the Street Car button or the Race Car button near the top of the window. This will fill in some suggested values for the Sustained Acceleration fields. |
| 4. | Configure the fields in the Start Trigger group as desired. You can enter a single condition (trigger) or multiple conditions. When using multiple conditions, data logging will begin when ANY of the conditions are met. |
| ￭ | Short Button Press. If this box is checked, a short press of the BT button on the device will trigger the start of logging. If this box is not checked, a short button press will not trigger logging start. |
| ￭ | Instantaneous Acceleration. If this field is populated, logging will start when the vehicle reaches the specified acceleration. |
| ￭ | Sustained Acceleration. If both of these fields are populated, logging will start when the vehicle sustains the specified acceleration for the specified number of seconds (for example, 0.05 G for 1 second). |
NOTE: If you are using an OBD extension cable, we recommend not using the accelerometer G-forcestart triggers. The interface device is only secure when it is plugged directly into the vehicle’s OBD port. If the device is connected via a cable, it might move independently of the vehicle’s acceleration. As a result, the accelerometer readings might be inaccurate and could result in a false trigger.
| 5. | When finished, click the Set Triggers button near the bottom of the window. |
CONFIGURING STOP TRIGGERS (OPTIONAL)
By default, a short press of the BT button on the device will trigger the stop of logging. If desired, you can set up triggers to start logging automatically based on the sustained acceleration and RPM.
NOTE: Additionally, data logging will stop if there is no movement and zero RPM for 1 minute.
| 1. | In the menu bar, select Vehicle > MPVI2 Data Logging. |
| 2. | Select the Start/Stop Triggers tab. |
| 3. | If desired, select either the Street Car button or the Race Car button near the top of the window. This will fill in some suggested values for the RPM fields in the OR trigger group. |
| 4. | Fill out the fields in the OR Trigger Group and/or the AND Trigger Group as desired. The OR Trigger Group allows you to set numerous conditions. Data logging will stop if ANY of these conditions are met. The AND Trigger Group allows you to set multiple conditions that must ALL be true in order for the data logging to stop. |
| ￭ | Short Button Press. If this box is checked, a short press of the BT button on the device will trigger the stop of logging. If this box is not checked, a short button press will not stop logging. |
| ￭ | Sustained Acceleration. If both of these fields are populated, logging will stop when the vehicle drops below the specified acceleration for the specified number of seconds (for example, 0.05 G for 1 second). |
| ￭ | RPM. If both of these fields are populated, logging will stop when the vehicle drops to the specified RPM or below for the specified number of seconds. |
| 5. | When finished, click the Set Triggers button near the bottom of the window. |
GENERATING A LOG
| 1. | Disconnect the interface device from your computer. Also ensure that the device is not connected to any application (TDN, TrackAddict, etc.) via Bluetooth®. |
| 2. | It can take up to two minutes after you disconnect for the device to be ready for standalone data logging. If you need to start a log sooner, you can force it to reset by unplugging it from the vehicle's OBD-II port. |
| 3. | Plug the device into the OBD-II port of the vehicle you wish to log. |
| 4. | Start the engine or place the vehicle on the ON/RUN state without starting the engine. This will provide power to the device. |
| 5. | Data logging should start automatically about five to ten seconds after the configured trigger conditions are met. Once data logging is fully active, the amber OBD light will flash. |
NOTE: The first time you log a particular vehicle, allow an additional five seconds for the system to initiate. If it takes longer than twenty seconds to start, please submit a support ticket and attach a copy of the Infolog.
| 6. | Data logging will stop automatically when the configured stop triggers are met. Alternately, pressing the BT button will perform a quick stop and discontinue logging data (some devices may require a firmer button press than others). |
CAUTION: Do not unplug your interface device without properly stopping the data logging. Doing so will result in some loss of data.
NOTES
| ￭ | Do not connect to VCM Suite, TDN, or TrackAddict while Standalone Data Logging is running. If you do so, the data logging software will turn off and stop recording. Data collected up to that point will be saved. |
| ￭ | If the data logging fails during startup (for example, if the vehicle’s ignition is turned off), logging will abort and the device will wait for another start trigger. |
| ￭ | During startup, the OBD and Host lights will flash and may occasionally pause. This is normal. |
RETRIEVING LOG FILES
| 2. | Connect your HP Tuners interface device to your computer with the USB cable. |
| 3. | In the menu bar, select Vehicle > MPVI2 Data Logging. |
| 4. | Select the Log Files tab. |
The newest log files will appear at the top of the list. The name will contain the sequence number and the VIN.
NOTE: The MPVI2 does not have a persistent clock, so dates will display the year 1980 unless you connected to VCM Suite, TDN, or TrackAddict during the same power cycle.
| 5. | Select the log file you want and then click Read Selected. |
| 6. | Choose a destination folder in which to save the file. |
TROUBLESHOOTING
If you encounter problems, make sure you are using the latest version of the VCM Scanner software. We're constantly trying to make the software better.
You can also try the following:
STANDALONE DATA LOGGING IS NOT STARTING (NO LOG FILE CREATED)
| 1. | If you are using an MPVI2, verify that the firmware has been updated to v3.1.2 or higher. |
| 2. | Click the Resync Interface Resources button in the MPVI2 Data Logging window. |
| 3. | Under Start Triggers, verify that the Short Button Press option is checked and enabled. Then, use the BT button to initiate logging manually |
| 4. | Ensure that the vehicle’s ignition is ON or the engine is running the entire time. |
| 5. | Remove the channels from the channel configuration and try again. Click Erase Channels Configbutton in the MPVI2 Data Logging window to reset it to Vehicle Defaults. |
STANDALONE DATA LOGGING IS NOT STOPPING
| 1. | Under Start Triggers, verify that the Short Button Press option is checked and enabled. Use the BT button to initiate logging manually. |
| 2. | Remove the channels from the channel configuration and try again. Click Erase Channels Configuration in the MPVI2 Data Logging window to reset it to Vehicle Defaults. |
A DATA LOG IS CREATED, BUT CHANNEL VALUES ARE BLANK, OR AN ERROR WINDOW POPS-UP WHEN OPENING THE FILE
| 1. | Ensure that the vehicle’s ignition is on or the engine is running the entire time. |
| 2. | In VCM Scanner, right-click on the channel, navigate to Polling Interval, and ensure that it is set to a reasonable frequency. |
| 3. | Remove the channels from the channel configuration and try again. Click Erase Channels Configuration in the MPVI2 Data Logging window to reset it to Vehicle Defaults. |