I just added another to C and it's still missing the outer most rows and columns.
I just added another to C and it's still missing the outer most rows and columns.
it pasted them right but why are the values say for 400rpms missing?
You don't want the data from the tune... the data will come from a log.
right.. but does it not compare your tune values to what your actually getting and then you multiply that into your table after each log? so if at 400 rpm it says i'm 300% off because it's comparing it to 0 then( my tune may truly already have a value of 3, will it not then set it to double 6 when in reallity it just needed to be a 3?)
Exit the map properties, what does the map say now (you have no log file open)...?
no I don't have a log file open I was trying to set up my log file. map is empty
I'm trying to do my autoVEmap. I just thought Since those values were missing I would get distorted readings. Since when i did this with the 1 bar I don't recall any values being left out...
The data values you see in the cells in the map properties is example data only (look how orderly it looks), and is not related to the data values you're going to see in the map with a log file open.
if its not one thing its another. Now my scanning v7.5 is not working it say it connects but when i press the monitor button or record buttons I get an error message. I did maybe three logs and flashes then it stopped working......?
bug report:
This error is caused by one or more of the following:
1. The interface cable may not be connected to the PC correctly.
Confirm all cable connections.
Inspect connectors for possibility of debris, damaged pins or corrosion.
2. Some other application may be using the interface cable. Windows cannot share the interface cable between multiple software applications.
If you are using the Scan Tool software, make sure the Tuning Tool software is not performing some task that requires the interface cable.
If you are using the Tuning Tool, make sure the Scan Tool software has been disconnected from the interface cable.
3. The FlashScan interface cable may be "black-box" logging. While FlashScan is logging data, the green LOG lamp will be illuminated.
Terminate black-box logging by pressing the "Start/Stop Data Logging" button on the FlashScan interface cable. The green LOG lamp will extinguish when "black-box" logging has terminated.
4. When reconnecting after an abnormal disconnect the cable may have been left in an unknown state.
Try reconnecting EFILive again.
5. When reconnecting after a previous aborted attempt, the interface cable may still be resetting. If a valid OBD II protocol cannot be detected, some cables can take up to 40 seconds to reset.
Try unplugging and reconnecting the interface cable from/to the vehicle.
6. The interface cable is connected to a com port that is not being checked by EFILive.
Make sure the interface cable is connected to a com port that is less than or equal to the "Highest COM port" setting on the Connection tab page of the Properties window.
7. The vehicle's OBD II connector is not supplying power and/or ground to the interface cable.
Check the fuse that supplies power to the vehicle's OBD II connector.
Pin 16 must always supply 12 volts even when the ignition is switched off.
Pin 4 must be chassis ground.
Pin 5 must be signal ground.
8. A USB to serial converter is being used which may not be operating correctly.
Try unplugging your USB to serial converter from your PC and reconnecting it. Wait 15 seconds before trying again.
Try updating/reinstalling the drivers for your USB to serial converter.
Try a different USB to serial converter.
Try connecting using a computer that has a real RS232 serial port.
Unplug the PC from V2, unplug V2 from the PCM;
then close V8 S&T, close V8 EE, close V7 tunetool, V7 scantool...
then connect PC to V2 to PCM, and start the tunetool...
(and click the Connect button, select pids, and click the Record button).
Did you read/check each of the 8 items...?
Posting Permissions
Reply With Quote