Known issues with May 01, 2015 Public Release

[Blacky]

Currently known issues and possible workarounds for the May 01, 2015 Public Release of the EFILive Software and Firmware

Download the public release software here: http://www.efilive.com/latest/cat/download-efilive



Software: V7.5.7.282
Software: V8.2.2.276
FlashScan/AutoCal firmware: V2.07.82


Issue 1:
If you are Black Box Logging PIDs from an ECM and TCM simultaneously and you have selected a PID from the transmission controller (TCM) that has an identically named PID in the engine controller (ECM), then when the log file is loaded back into the V8 software for viewing, that TCM PID will be displayed as if it originated from the ECM. The PID's data will have correctly been logged from the TCM, only its name will appear to indicate that it was logged from the ECM.
Workaround:
None.
It is a restriction of the *.efi (V7.5 log file format). That restriction will be removed and the TCM PIDs will display their true origin once the V8 scan tool software is available.
Issue 2:
EFILive V7 pass-thru data logging does not record external PIDs correctly (i.e. PIDs used by wideband, dyno and third party data loggers).
Workaround:
Update your V7 software (to V7.5.7.283) using the option: Start->All Programs->EFILive->V7.5->Check For Updates.
Issue 3:
After successfully performing the "Check For Updates" option to update the installed software. Running the "Check For Updates" option again continues to report that "There is a newer version..." even though the software is up to date.
Workaround:
Resolved. Perform one more "Check For Update" to update the version numbers correctly.
Issue 4:
After stopping playback in the V8 scan tool the software incorrectly attempts to connect to the vehicle via FlashScan or AutoCal - even when FlashScan or AutoCal is not connected.
Workaround:
None. Will be fixed in the next update, scheduled for June 03, 2015.
Issue 5:
After a failed LML flash, recovery may not be successful and may fail with $0322 error.
Workaround:
Download the attached E86.zip file. Unzip the contents into the folder: \Program Files (x86)\EFILive\V8\Config. Overwrite the existing files. Retry the flash recovery.
Issue 6:
After a full-flash of an LS1B or E54 (LB7) controller, subsequent flashes may fail with the $0333 "Security Access Denied" error. The Seed and Key have incorreectly been set to $0000 and $0000 by the EFILive full-flash procedure.
Workaround:
An update to correct the fault will be made available ASAP (hopefully in the next 24-48 hours)
Until then, when using the V8 pass-thru software to read or flash a controller, check both the "Try Alt Keys" and "Assume Lock May be Faulty" checkboxes.

[wesam]

I have a very big problem
The 7.5 sxan tool can not see the external serial wide band data
I make sure every thing is connected well
I can log the wide band data in the V2 sceen but the scan tool always show the external wide band data as 10 AFR even if its disconected

Looking forward to hear from you

[Blacky]

I have a very big problem
The 7.5 sxan tool can not see the external serial wide band data
I make sure every thing is connected well
I can log the wide band data in the V2 sceen but the scan tool always show the external wide band data as 10 AFR even if its disconected

Looking forward to hear from you

The problem has been reproduced here at EFILive. A fix will be available asap.

Regards
Paul

[Blacky]

The 7.5 sxan tool can not see the external serial wide band data

A patch has been issued and is now available using the option: Start->All Programs->EFILive->V7.5->Check For Updates.

Regards
Paul

[wesam]

Thanks a lot Paul
I will test it and will let you know

[wesam]

Paul still has the same problem after installing the patch
Also i noticed if i go to Start->All Programs->EFILive->V7.5->Check For Updates again it will show that there is a new update available
Also i noticed if i save log file then open it again the WB readings will go from constant 10 AFR to 369 AFR !!!!
Attached Log file

[Blacky]

It is possible that the patch is not getting applied correctly on your setup. Try downloading the full install and installing it that way.
http://www.efilive.com/latest/cat/download-efilive

Regards
Paul

[wesam]

Even after i installed the full version from the link when i try the auto update it will show that there is a new version to be installed
Is this normal ?

[Blacky]

Even after i installed the full version from the link when i try the auto update it will show that there is a new version to be installed
Is this normal ?

Previously I said try downloading the full-install. My mistake, there is no full-install for build 283. Build 283 can only be installed by installing build 282 (the current public release) and then doing a "Check For Updates" option.

Plus as you've discovered there is an issue with the installed version number not updating correctly during a patch update. That leads to the "Check For Updates" option always reporting that a new version exists, even when you have the most up to date software installed. The installed version number is stored in the file \Program Files (x86)\EFILive\V7.5\AutoUpdate.ini. That file should get updated to 283 during the previous "Check For Updates" but it is being left at 282 which makes the AutoUpdate option always show that an update exists.

Meanwhile, when you run the EFILive V7 Scan Tool software, check the build number using the menu option: Help->About. If it shows 283 then you have the latest version installed (as of May 04 2015).

Regards
Paul

[Blacky]

Paul still has the same problem after installing the patch

The "Check For Updates" patch should update your system correctly now.

If the patch still does not work correctly, you can download the full V7 build 283 install here:
http://download.efilive.com/Software/V7.5/EFILiveV7.5.7.283_Setup.exe

Regards
Paul

[wesam]

Thanks Paul every thin is fine now

[bobo]

I have a new computer and I installed the new software on it. It seems to delay on start up of the scan tool by ~30 seconds. I did the patch to Build 283. Build 282 was the same. Does anyone else have a noticeable delay when they open v7.5 scan tool? I did do a fair amount of changes in the settings to try and improve the start up speed, but it did not change.


Here are the timer results to get the scan tool ready from the Console F6 tab:
TEST 1:
15:46:26.106: EFILive V7.5 Version V7.5.7 (Build 283)
15:46:54.602: Ready.


TEST 2:

15:50:07.993: EFILive V7.5 Version V7.5.7 (Build 283)
15:50:34.679: Ready.



TEST3:

15:54:05.702: EFILive V7.5 Version V7.5.7 (Build 283)
15:54:31.988: Ready.

[Blacky]

I have a new computer and I installed the new software on it. It seems to delay on start up of the scan tool by ~30 seconds.

Right-click the V7 Tune desktop shortcut and select Properties.
Add the three characters: <space><forward slash><Lowercase L> to the end of the Target field, like this:


......V7.5\EFILive_Tune.exe" /l

Then click OK and re-run V7.

It will create a log file called StartupLog.txt in the same folder as the EFILive_Tune.exe file.
Important, you must have write permission to the \Program Files (x86)\EFILive\V7.5 folder. That means you may need to turn off UAC temporarily while you do that. Or take ownership* of the \Program Files (x86)\EFILive\V7.5 folder.

The log file will show you the steps that the software goes through when starting up along with timestamps that show how long each part of the process takes.

* Take ownership of a folder: https://technet.microsoft.com/en-nz/library/cc753659.aspx

Regards
Paul

[bobo]

Okay, thank you! I did that for the Tune tool like you said(I'm not seeing a delay in tune tool start up, only scan tool start up).....and here is what I got:


17:18:54.275|4696|FormCreate (fMainTune)
17:18:54.285|4696|LoadFormState (fMainTune)
17:18:54.289|4696|LoadFormState (fMainTune) done
17:18:54.293|4696|Creating (TConfig)
17:18:54.315|4696|Creating (TConfig) done
17:18:54.319|4696|LoadListView (lvFav)
17:18:54.324|4696|LoadListView (lvFav) done
17:18:54.385|4696|LoadFormState (fUnitsSys)
17:18:54.389|4696|LoadFormState (fUnitsSys) done
17:18:54.393|4696|LoadListView (lvCals)
17:18:54.398|4696|LoadListView (lvCals) done
17:18:54.458|4696|FormCreate (fDownload)
17:18:54.464|4696|LoadFormState (fDownload)
17:18:54.468|4696|LoadFormState (fDownload) done
17:18:54.473|4696|FormCreate (fDownload) done
17:18:54.521|4696|FormCreate (fV2Upgrade)
17:18:54.525|4696|FormCreate (fV2Upgrade) done
17:18:54.548|4696|FormCreate (fUpload)
17:18:54.560|4696|LoadFormState (fUpload)
17:18:54.577|4696|LoadFormState (fUpload) done
17:18:54.624|4696|FormCreate (fUpload) done
17:18:54.680|4696|FormCreate (fRoadRunner)
17:18:54.702|4696|LoadFormState (fRoadRunner)
17:18:54.707|4696|LoadFormState (fRoadRunner) done
17:18:54.797|4696|FormCreate (fRoadRunner) done
17:18:55.000|4696|LoadFormState (fSpeedoAdjust)
17:18:55.010|4696|LoadFormState (fSpeedoAdjust) done
17:18:55.029|4696|LoadFormState (fCreateScript)
17:18:55.043|4696|LoadFormState (fCreateScript) done
17:18:55.047|4696|LoadListView (lvScript)
17:18:55.052|4696|LoadListView (lvScript) done
17:18:55.056|4696|LoadListView (lvCopy)
17:18:55.061|4696|LoadListView (lvCopy) done
17:18:55.099|4696|FormCreate (fLocking)
17:18:55.112|4696|LoadFormState (fLocking)
17:18:55.131|4696|LoadFormState (fLocking) done
17:18:55.176|4696|FormCreate (fLocking) done
17:18:55.279|4696|LoadFormState (fProperties)
17:18:55.284|4696|LoadFormState (fProperties) done
17:18:55.410|4696|FormCreate (fPcmInfo)
17:18:55.432|4696|LoadFormState (fPcmInfo)
17:18:55.437|4696|LoadFormState (fPcmInfo) done
17:18:55.441|4696|LoadListView (lvPcmSeg)
17:18:55.446|4696|LoadListView (lvPcmSeg) done
17:18:55.451|4696|LoadListView (lvPcmVin)
17:18:55.466|4696|LoadListView (lvPcmVin) done
17:18:55.535|4696|FormCreate (fPcmInfo) done
17:18:55.566|4696|FormCreate (fLicMgr)
17:18:55.574|4696|LoadFormState (fLicMgr)
17:18:55.580|4696|LoadFormState (fLicMgr) done
17:18:55.584|4696|FormCreate (fLicMgr) done
17:18:55.639|4696|FormCreate (fV1License)
17:18:55.644|4696|LoadListView (lvPcm)
17:18:55.649|4696|LoadListView (lvPcm) done
17:18:55.654|4696|FormCreate (fV1License) done
17:18:55.687|4696|FormCreate (fV2License)
17:18:55.692|4696|LoadListView (lvPcm)
17:18:55.697|4696|LoadListView (lvPcm) done
17:18:55.701|4696|LoadListView (lvStream)
17:18:55.706|4696|LoadListView (lvStream) done
17:18:55.731|4696|FormCreate (fV2License) done
17:18:55.867|4696|LoadFormState (fCumminsTimingCalculator)
17:18:55.873|4696|LoadFormState (fCumminsTimingCalculator) done
17:18:55.878|4696|LoadPanel (pnlInfo)
17:18:55.883|4696|LoadPanel (pnlInfo) done
17:18:55.960|4696|LoadFormState (fMainTune)
17:18:55.966|4696|LoadFormState (fMainTune) done
17:18:55.971|4696|obdiiInit
17:18:55.987|4696|LoadConfig file: C:\Program Files (x86)\EFILive\V7.5\Configuration\sae_generic.txt
17:18:55.993|4696|ClearConfig
17:18:56.688|4696|Calc PIDs filename: C:\Users\Diesel\Documents\EFILive\V7.5\User Configuration\calc_pids.txt
17:18:56.693|4696|LoadFile (sae_generic.txt) Section (FILE)
17:18:56.697|4696|LoadFile (calc_pids.txt) Section (FILE)
17:18:56.708|4696|LoadFile (sae_generic.txt) Section (ENHANCED)
17:18:56.723|4696|Enhanced file: C:\Program Files (x86)\EFILive\V7.5\Configuration\gm_enhanced.prn
17:18:57.056|4696|LoadFile (sae_generic.txt) Section (UNITS)
17:18:57.061|4696|LoadFile (gm_enhanced.prn) Section (UNITS)
17:18:57.073|4696|LoadFile (calc_pids.txt) Section (UNITS)
17:18:57.078|4696|Checking for duplicate units
17:18:57.083|4696|No duplicate units found
17:18:57.100|4696|LoadFile (sae_generic.txt) Section (PROTOCOLS)
17:18:57.106|4696|LoadFile (sae_generic.txt) Section (DTC)
17:18:57.114|4696|LoadFile (gm_enhanced.prn) Section (DTC)
17:18:57.167|4696|LoadFile (sae_generic.txt) Section (MODULES)
17:18:57.172|4696|LoadFile (gm_enhanced.prn) Section (MODULES_ENH)
17:18:57.177|4696|LoadFile (gm_enhanced.prn) Section (PCM_HARDWARE)
17:18:57.182|4696|LoadFile (gm_enhanced.prn) Section (PCM_LOCKING)
17:18:57.193|4696|LoadFile (sae_generic.txt) Section (MODES)
17:18:57.198|4696|LoadFile (sae_generic.txt) Section (RESPONSES)
17:18:57.203|4696|LoadFile (sae_generic.txt) Section (V5V6)
17:18:57.209|4696|LoadFile (sae_generic.txt) Section (BBLV7)
17:18:57.214|4696|LoadFile (gm_enhanced.prn) Section (BOOTBLOCKS)
17:18:57.221|4696|LoadFile (sae_generic.txt) Section (O2RESULTS)
17:18:57.226|4696|LoadFile (gm_enhanced.prn) Section (SMSRESULTS)
17:18:57.233|4696|LoadFile (sae_generic.txt) Section (SLOTS)
17:18:57.244|4696|LoadFile (gm_enhanced.prn) Section (SLOTS)
17:18:57.262|4696|LoadFile (calc_pids.txt) Section (SLOTS)
17:18:57.282|4696|LoadFile (sae_generic.txt) Section (PRN)
17:18:57.298|4696|LoadFile (gm_enhanced.prn) Section (PRN)
17:18:57.333|4696|LoadFile (calc_pids.txt) Section (PRN)
17:18:57.339|4696|LoadFile (gm_enhanced.prn) Section (PIDGROUP)
17:18:57.351|4696|LoadFile (calc_pids.txt) Section (TABLES)
17:18:57.355|4696|Sorting PRNs
17:18:57.361|4696|Sorting PRNs done
17:18:57.366|4696|LoadFile (gm_enhanced.prn) Section (V7SCANID)
17:18:57.378|4696|LoadFile (gm_enhanced.prn) Section (CUST_OS)
17:18:57.385|4696|LoadFile (gm_enhanced.prn) Section (OS_COMPATIBILITY)
17:18:57.392|4696|LoadFile (gm_enhanced.prn) Section (DMA)
17:18:57.400|4696|LoadFile (gm_enhanced.prn) Section (P05)
17:18:57.407|4696|LoadFile (gm_enhanced.prn) Section (ALT_CAL)
17:18:57.414|4696|LoadFile (gm_enhanced.prn) Section (ALI_TAP)
17:18:57.422|4696|Sorting PRNs
17:18:57.428|4696|Sorting PRNs done
17:18:57.433|4696|Checking for duplicate PRN names
17:18:57.438|4696|No duplicate PRN names found
17:18:57.443|4696|Resolve multi packet PRNs
17:18:57.451|4696|Resolve multi packet PRNs done
17:18:57.460|4696|LoadConfig Done
17:18:57.466|4696|Apply config...
17:18:57.476|4696|Apply config done!
17:18:57.481|4696|Create FlashScan Object...
17:18:57.506|4696|Unload bin...
17:18:57.619|4696|Unload bin done.
17:18:57.640|4696|Unload bin...
17:18:57.753|4696|Unload bin done.
17:18:57.758|4696|Create FlashScan Object done!
17:18:57.765|4696|Load bin file "C:\Users\Diesel\Desktop\Tune\Customer Folders\.ctz"...
17:18:57.770|4696|Close all calibrations...
17:18:57.775|4696|Close all calibrations done.
17:18:57.780|4696|Clear all calibrations.
17:18:57.785|4696|Unload bin...
17:18:57.902|4696|Unload bin done.
17:18:57.907|4696|Unload bin...
17:18:58.020|4696|Unload bin done.
17:18:58.025|4696|Clear all calibrations done.
17:18:58.031|4696|Populating Navigator...
17:18:58.079|4696|Populate segments...
17:18:58.087|4696|Populate segments done.
17:18:58.132|4696|Unload bin...
17:18:58.249|4696|Unload bin done.
17:18:58.255|4696|Unload bin...
17:18:58.369|4696|Unload bin done.
17:18:58.375|4696|Open bin as "C:\Users\Diesel\Desktop\Tune\Customer Folders\.ctz"
17:18:58.396|4696|Populating Navigator...
17:18:58.406|4696|Populate segments...
17:18:58.414|4696|Populate segments done.
17:18:58.457|4696|Bin file "C:\Users\Diesel\Desktop\Tune\Customer Folders\.ctz" loaded.
17:18:58.463|4696|fMainTune, initialized OK.
17:18:58.470|4696|Refresh display...
17:18:59.997|4696|Refresh display done!
17:19:00.005|4696|fMainTune, activated.
17:19:04.392|4696|Close all calibrations...
17:19:04.399|4696|Close all calibrations done.

[bobo]

Here is where the scan tool is waiting:


17:47:10.649|620|LoadListView (lvGrpSel) done
17:47:23.444|620|FrameInit (frPID) Done
17:47:31.913|620|Validate connection...
17:47:31.920|620|Load customer details...
17:47:31.998|620|Load MRU PID selection...
17:47:32.004|620|OpenPid C:\Users\

[bobo]

I did the same log on another machine with older software and there is very little delay between "LoadListView (lvlGrpsel) done" and "FrameInit (frPID) done". The new computer is waiting there for ~13 seconds and ~8 seconds to move to the "Validate Connection" task.

[joecar]

( ( hmmm, interesting.... how much memory do each of those two computers have...? ) )

[bobo]

( ( hmmm, interesting.... how much memory do each of those two computers have...? ) )

Everything works fine except the scan tool. The tune tool opens just like normal. Its a cheap computer, but everything works good except the scan tool.


Intel® Celeron® Processor N2840
Windows 8.1
4GB DDR3L 1600MHz

One of my other laptops is an Intel(R) CORE i5-337U@1.8 GHz and 4GB RAM.....it works fine....on a different version of EFILIVE.....and I don't want to update anything else because I have known stable versions that don't muck things up on the other computers.

[Yellow05C6]

Sorry about the length, I’ve tried to be concise. We are having trouble with LS1B ECMs and their O2s. We’ve built wiring harnesses for both 1M and 0.5M LS1Bs w/o issue. Suddenly the last two harnesses (both for 0.5M LS1Bs) result in the ECM not being able to “see” HO2S11 & HO2S21 sensors (i.e. O2 voltage remains a steady 450mV after the O2 heats up). I cannot say if the ECM would respond with LTFT/STFT because I have no scan data for an engine running in closed loop. We checked pin-to-pin in both harnesses and found no errors and they are duplicates of past good harnesses. First we attached a 1M LS1B to a “bad” harness. The 1M LS1B did “see” the O2 sensors (i.e. O2 voltage drops to small mV range with the sensor in air). We reinstalled the 0.5M LS1B into the “bad” harness and re-verified that the ECM could not “see” the O2. We tried several 0.5M LS1Bs all with the same 450 mV result. Then we back probed one of the O2s and found sensor voltage to actually be 90mV and descending even though the scan still indicates 450 mV. Stated plainly, the 0.5M LS1B is acting like the O2 sensor is not connected. In all cases we are directly applying 12 volts and ground to the O2 sensor heater (as we have done in the past), and O2 sensor temp hovers around 200F. Also the engine is not running but the O2s are in air or in a cold exhaust pipe. All other sensors are installed and read correctly. We’ve even injected simulated CKP & CMP signals to fool the ECM into thinking the engine is running. A Snap-On Scanner also displays a continuous O2 reading of 450 mV. This problem appears to have started after V7.5.7 Build 283 and V8.2.2 Build 276 were installed. Harnesses & ECMs built / programmed before the May release do not exhibit this problem. I’m not sure what the previous versions were; but it had probably been more than a year since the previous update. 1.0M, 0.5M LS1B tune and scan files as well as the ECM pin-outs we use are available if they would be of interest.

[ProperTuningOG]

We build harnesses as well and have not seen this issue. We are running the newest release......

[68skylark455]

Not sure if this is the spot to put this but I used my EFILive Saturday, already did the new update and while trying to start a 2001 stock dmax I was watching the pid "actual fuel pressure" and a few others while cranking with no issues. Last night I tried with both of my laptops, one windows xp and the other windows 8.1 and when I selected the yellow start monitoring button I get this message in the pic. It was fine Saturday and Wednesday night it did this on both pc's and on two different dmaxs.
18347

[ScarabEpic22]

Hate to tell you, that "Celeron" processor is based on the Atom architecture and not the Core architecture (Note the "N" prefix on the model #, i.e. super low power and not powerful). It might work ok in the Tune tool, but you might have framerate issues as simply the processor cannot keep up with the Scan tool. Ive only seen the V7.5 Scan tool utilize 1 thread/core (havent checked in a while) and I imagine it will overwhelm that Atom core in a heartbeat.

[Blacky]

Not sure if this is the spot to put this but I used my EFILive Saturday, already did the new update and while trying to start a 2001 stock dmax I was watching the pid "actual fuel pressure" and a few others while cranking with no issues. Last night I tried with both of my laptops, one windows xp and the other windows 8.1 and when I selected the yellow start monitoring button I get this message in the pic. It was fine Saturday and Wednesday night it did this on both pc's and on two different dmaxs.


The scan tool will autimatically "drop down" to generic scan mode if you select only about 1-3 PIDs. It is faster to log 1-3 PIDs in generic mode than in dynamic mode. However, the dmax can't log DMA PIDs in genreic mode. So try selecting anough PIDs to bump the channel count to more than 6. The channel count is shown at the bottom of the [PIDs (F8)] tab page.


Regards
Paul

[Blacky]

Here is where the scan tool is waiting:


17:47:10.649|620|LoadListView (lvGrpSel) done
17:47:23.444|620|FrameInit (frPID) Done
17:47:31.913|620|Validate connection...
17:47:31.920|620|Load customer details...
17:47:31.998|620|Load MRU PID selection...
17:47:32.004|620|OpenPid C:\Users\

The 8 second delay between these two entries:
17:47:23.444|620|FrameInit (frPID) Done
17:47:31.913|620|Validate connection...

is the point where PIDs get validated. Normally PIDs are only validated when connecting to a vehicle. However, if you have your system set up to "auto connect" at startup, then when starting the software a connection is attempted and all the palava that goes along with attempting to establish and validate the connection is performed.

Check to see if you have "auto-connection" active. View->Properties->[Startup]->"Try to establish an OBDII connection to a vehicle".
If it is active, try switching it off and see if that speeds up the software startup.

I still can't explain the 13 second delay between these two entries:
17:47:10.649|620|LoadListView (lvGrpSel) done
17:47:23.444|620|FrameInit (frPID) Done

Anyway, let me know if switching off the auto-connect option (assuming it is switched on) helps with one or both of those delays.

Regards
Paul

[Blacky]

Hate to tell you, that "Celeron" processor is based on the Atom architecture and not the Core architecture (Note the "N" prefix on the model #, i.e. super low power and not powerful). It might work ok in the Tune tool, but you might have framerate issues as simply the processor cannot keep up with the Scan tool. Ive only seen the V7.5 Scan tool utilize 1 thread/core (havent checked in a while) and I imagine it will overwhelm that Atom core in a heartbeat.

Yes, unfortunately the V7 scan tool only uses single thread architecture which inefficient when doing blocking I/O (i.e. while the thread is waiting for the USB data to arrive from FlashScan it can't be updating the charts/gauges). But back when it was designed it only had to handle 10 frames per second from LS1 style controllers. Now some of the Cummins controllers (when using EFILive's EDA) can send back 40 frames per second with 40-50 PIDs in each frame.

The V8 scan tool uses multi thread (well two threads), one to wait for data from USB and one to handle the charting/gauge updates. The V8 scan tool runs much better than V7 on even the slowest, modern CPUs.

Regards
Paul

[joecar]

Sorry about the length, I’ve tried to be concise. We are having trouble with LS1B ECMs and their O2s. We’ve built wiring harnesses for both 1M and 0.5M LS1Bs w/o issue. Suddenly the last two harnesses (both for 0.5M LS1Bs) result in the ECM not being able to “see” HO2S11 & HO2S21 sensors (i.e. O2 voltage remains a steady 450mV after the O2 heats up). I cannot say if the ECM would respond with LTFT/STFT because I have no scan data for an engine running in closed loop. We checked pin-to-pin in both harnesses and found no errors and they are duplicates of past good harnesses. First we attached a 1M LS1B to a “bad” harness. The 1M LS1B did “see” the O2 sensors (i.e. O2 voltage drops to small mV range with the sensor in air). We reinstalled the 0.5M LS1B into the “bad” harness and re-verified that the ECM could not “see” the O2. We tried several 0.5M LS1Bs all with the same 450 mV result. Then we back probed one of the O2s and found sensor voltage to actually be 90mV and descending even though the scan still indicates 450 mV. Stated plainly, the 0.5M LS1B is acting like the O2 sensor is not connected. In all cases we are directly applying 12 volts and ground to the O2 sensor heater (as we have done in the past), and O2 sensor temp hovers around 200F. Also the engine is not running but the O2s are in air or in a cold exhaust pipe. All other sensors are installed and read correctly. We’ve even injected simulated CKP & CMP signals to fool the ECM into thinking the engine is running. A Snap-On Scanner also displays a continuous O2 reading of 450 mV. This problem appears to have started after V7.5.7 Build 283 and V8.2.2 Build 276 were installed. Harnesses & ECMs built / programmed before the May release do not exhibit this problem. I’m not sure what the previous versions were; but it had probably been more than a year since the previous update. 1.0M, 0.5M LS1B tune and scan files as well as the ECM pin-outs we use are available if they would be of interest.Sounds like a harness wiring problem (loose crimp, excess voltage drop across a crimp/connection, loose pin contact)... did you check continuity to the NBO2 pinouts...?

[68skylark455]

When we were using it on Saturday I had all 8 cyl balance rates up plus the actual fuel pressure and desired pressure as well. I saved that selection two months ago. We didn't change anything at all. Wednesday I made a plug for the fuel rail and was going to see if the actual pressure came up and if it started we could see the balance rates. When I hit the start in real time yellow button that message appeared. I tried general, dynamic, stream slow and fast and tried it on two different trucks an 01 and 04. The only thing I found yesterday was it shows the v2.5 hooked up through a HAPI connection instead of the USB. Haven't tried to change that yet just found it yesterday.

[Blacky]

When we were using it on Saturday I had all 8 cyl balance rates up plus the actual fuel pressure and desired pressure as well. I saved that selection two months ago. We didn't change anything at all. Wednesday I made a plug for the fuel rail and was going to see if the actual pressure came up and if it started we could see the balance rates. When I hit the start in real time yellow button that message appeared. I tried general, dynamic, stream slow and fast and tried it on two different trucks an 01 and 04. The only thing I found yesterday was it shows the v2.5 hooked up through a HAPI connection instead of the USB. Haven't tried to change that yet just found it yesterday.

The error message indicates that the software is conencted to a Duramax diesel ECM. If you are physically connected to an LS1 gas ECM but selected a Durmax ECM to connect to then that won't work.

Ignore this post, I mixed up two different posts in this thread (68skylark455's and Yellow05C6's posts)

Regards
Paul

[Blacky]

When we were using it on Saturday I had all 8 cyl balance rates up plus the actual fuel pressure and desired pressure as well. I saved that selection two months ago. We didn't change anything at all. Wednesday I made a plug for the fuel rail and was going to see if the actual pressure came up and if it started we could see the balance rates. When I hit the start in real time yellow button that message appeared. I tried general, dynamic, stream slow and fast and tried it on two different trucks an 01 and 04. The only thing I found yesterday was it shows the v2.5 hooked up through a HAPI connection instead of the USB. Haven't tried to change that yet just found it yesterday.

What list of PIDs are selected when you try to log data?
Note: even if you specifically set the scan mode to Dynamic, Stream-slow or Stream-fast, it will always drop back to generic if only a few PIDs are selected. And DMA PIDs are not supported in generic mode.

Regards
Paul

[Yellow05C6]

Sounds like a harness wiring problem (loose crimp, excess voltage drop across a crimp/connection, loose pin contact)... did you check continuity to the NBO2 pinouts...?
Thanks for your helpful response. Yes, I've verified continuity and even soldered the wires to the pins. Also by soldering a fine wire onto C1 pins 26, 29, 66, & 69 and reinserting the pin into C1, I have measured voltage at the ECM pin. Attached photos are with O2 sensors dead cold (scan=451mV, DVM=393mV) and about 30 seconds after powering up the vehicle up (scan=447 mV, DVM = 79mV). Same performance with three 0.5M LS1Bs (OS12212156) and two harnesses. Removing the O2 sensors from the connector, I find pins A & B of the O2 sensor connector all at about 5 volts with respect to engine ground. Pins A & B show the same voltage with respect to each other as seen at pins 26 & 66 (about 400 mV). Placing a 1kohm resistor across pins A & B drives the voltage at pins 26 & 66 and A & B down to very near zero volts. Yet the scan display still reads 450 mV. More on the harness that is in a car: My previously reported info was wrong, the car had been driven quite a bit and it never went into closed loop. The issue was only noted when the owner attempted to get the car tuned. As I said before, it is as if the O2s are not even connected. The harness is based on a 2002 Express Van w/ unnecessary stuff removed. The tune file and scan files are attached also.

[joecar]

What voltage do you see between NBO2 pins C and D...?

Is the PCM setting any DTC's...?

[joecar]

Is the idle 2 minute capture log file from a running engine...?

various pids (MAP, MAF, IAT, ECT, SPARKADV, RPM) are perfectly flat (this engine is not running).

I see IAC and IACDES stepping from 73 down to zero in as many frames.

I see 239V on EXT.AD1... do you have anything connected to V2's AD1 analog input...?

[joecar]

Looks like either your PCM(s) and/or V2 is faulty.

[Yellow05C6]

Pins C & D are 13.5 volts. O2 tips get to about 220F in about a minute. I enabled the AD1 hoping to capture voltage @ the O2 pins but it killed signal. I forgot to turn AD1 off. There were no DTCs except crank relearn which went away after learning. Very good catch on the PIDs...no it is not a running engine. I have an electronic CKP/CMP simulator (this file is for the simpler low resolution crank). That is why RPM is flat. I also simulate MAT, ECT, etc with potentiometers and can vary RPM with another pot. IAC was trying to lower RPM to desired. I have a '91 TPI Vette running this same OS & settings. When I place this ECM into that car it runs fine and the ECM "sees" the O2 voltage (using this same V2) with or without the engine running. It is highly likely I mistakenly placed this thread. As my investigation develops I'm very doubtful the problem is related to the May build and am open to your suggestion re placement.

[joecar]

Pins C & D are 13.5 volts. O2 tips get to about 220F in about a minute. I enabled the AD1 hoping to capture voltage @ the O2 pins but it killed signal. I forgot to turn AD1 off. There were no DTCs except crank relearn which went away after learning. Very good catch on the PIDs...no it is not a running engine. I have an electronic CKP/CMP simulator (this file is for the simpler low resolution crank). That is why RPM is flat. I also simulate MAT, ECT, etc with potentiometers and can vary RPM with another pot. IAC was trying to lower RPM to desired. I have a '91 TPI Vette running this same OS & settings. When I place this ECM into that car it runs fine and the ECM "sees" the O2 voltage (using this same V2) with or without the engine running. It is highly likely I mistakenly placed this thread. As my investigation develops I'm very doubtful the problem is related to the May build and am open to your suggestion re placement.This makes me think that your newer harness has a problem (or maybe even a missing ground/power)...

V2 is a like a "display terminal" for what the PCM emits on the OBD2/ALDL serial link... I don't think the problem is with V2 any more.

[Yellow05C6]

I'm leaning to the harness(s) also. Just hard to believe all three have an issue.

[68skylark455]

Well I changed the setting from V 2.5 HAPI To V2 USB and so far everything is working again. Not sure how it got changed unless it was within the update but all is well now thank you very much for your help!!

[ProperTuningOG]

I'm leaning to the harness(s) also. Just hard to believe all three have an issue.

Who is the terminal manufacturer you guys are using for the harness parts? We have had issues in the past with terminal, pins, not making proper contact in the ECM. These were new terminals.........

[SmokeAintPower]

Okay...I'm stuck.... Flashed an A50 TCM yesterday....then updated EFILive last night.... No I can't communicate with the A40 or A50 TCMs... I've tried multiple TCMs with no luck.... It always says "No Data Received"

[cindy@efilive]

Okay...I'm stuck.... Flashed an A50 TCM yesterday....then updated EFILive last night.... No I can't communicate with the A40 or A50 TCMs... I've tried multiple TCMs with no luck.... It always says "No Data Received"

What software and firmware are you running? How are you attempting to flash?

The latest software is May 01, 2015 and the builds are:

V8 Software: V8.2.2, Build 276
FlashScan/AutoCal Firmware: V2.07.82 (Apr 10, 2015)
FlashScan/AutoCal Boot Block: V2.07.07 (Feb 07, 2014)
V7.5 Software: V7.5.7, Build 282

To access this release, you must download and install the software from our website, then after installing V8 and/or V7.5 software, customers will need to run Auto-Update in both V8 and V7 software to ensure all available patch updates are installed.

FWIW, yesterday in the office we flashed an A50 using what is to be the next scheduled public pre-release software (build 277) using V8 pass-through without an issue. And I can confirm that there were no changes made to any GM transmission platforms between the 2 software versions.

Cheers
Cindy

[Yellow05C6]

Who is the terminal manufacturer you guys are using for the harness parts? We have had issues in the past with terminal, pins, not making proper contact in the ECM. These were new terminals.........

We were using new pins, but all three harnesses had the exact same problem; so we thought it was not likely a pin problem. In the end the problem was related to the O2 sensors we were using. We found information regarding isolated ground O2 sensors vs case grounded O2 sensors @ http://www.lt1swap.com/vortec_o2_sensors.htm that helped correct the problem. Just like some LS1B ECMs do not support electronic throttle, LS1B ECMs are designed for use with one or the other sensor. It appears in either case the ECM will see the O2 sensors if the O2 low reference pins on C1 are tied to engine ground. Right now all is happiness......:doh2:

[THEFERMANATOR]

I just upgraded to this release, and was scanning an 04 LLY tonight. When I went into DVT's and tried to control the turbo, I found that it didn't control it correctly. When I commanded 0% it went to 0, but when I commanded 100% it only went to 39.9. When I went to 50% it went to 19.9%. It would only command the mto 40% of what I commanded them to with the DVT controls. Also when I set the idle speed, it owuld only stay where I put it for about 45 seconds, then default back to base idle.

[GMPX]

That is really odd, because I can assure you we have not touched the DVT controls in the scantool for many years, I don't know why it would have changed on your truck.

[CR500]

I just downloaded / installed the updates (V8.2.2.276)

I seem to be having two issues:

- When playing back any of my logged data files (LS1B), if I hit the stop button the following error message appears:

No device connected.

Please connect a FlashScan or AutoCal USB device.

If a device is connected, ensure it is not being used by another application such as the EFILive V7.5 Scan or Tune Software.

Happens in Data, Charts, or Gauges.

- Second is with EOPS. This is the thread where you found there was an issue and had me changed GM.EOPS in the data file to XX.EOPS (https://forum.efilive.com/showthread.php?24500-Eops). I had not updated the software since then as that fix worked. Now that I've updated, GM.EOPS seems to be working but for some reason my calc pid to convert that voltage to a pressure stopped working.

To diagnose I tried a calc pid to just read EOPS: return pid("EOPS"); and even that just returns zero.

Thanks

Rob

[bobo]

I've gotta failed calibration flash here in a lml. I can't recover the Ecm. I did email support@efilive.com and sent a bunch of trace files.

[GMPX]

Bob, there is nothing more that you can do other than pull ECM power for 20 seconds or so and retry. Looking at your trace files the ECM is still alive and kicking so should be recoverable.
Can you try a pass through flash instead?

[bobo]

Here is what I'm getting. $0322

[bobo]

I'm doing pass through with v8

[GMPX]

I'm doing pass through with v8
Did you do the battery thing?

[bobo]

Pulled power and it does the same thing.

[bobo]

Did you do the battery thing?
Yes, pulled both negatives off the two batteries.

[GMPX]

Ok, I see Paul has sent you some stuff to try.

[bobo]

I got a new set of files from Paul for v8 that allowed the v8 program to wait long enough to recover the ECM. Thank you!

[CR500]

Guess I'll see if I can go back to the old version that was working for me.



I just downloaded / installed the updates (V8.2.2.276)

I seem to be having two issues:

- When playing back any of my logged data files (LS1B), if I hit the stop button the following error message appears:

No device connected.

Please connect a FlashScan or AutoCal USB device.

If a device is connected, ensure it is not being used by another application such as the EFILive V7.5 Scan or Tune Software.

Happens in Data, Charts, or Gauges.

- Second is with EOPS. This is the thread where you found there was an issue and had me changed GM.EOPS in the data file to XX.EOPS (https://forum.efilive.com/showthread.php?24500-Eops). I had not updated the software since then as that fix worked. Now that I've updated, GM.EOPS seems to be working but for some reason my calc pid to convert that voltage to a pressure stopped working.

To diagnose I tried a calc pid to just read EOPS: return pid("EOPS"); and even that just returns zero.

Thanks

Rob

[Blacky]

Hi Rob,

Sorry for the lack of reply, for some reason I had not noticed your post.



I seem to be having two issues:
- When playing back any of my logged data files (LS1B), if I hit the stop button the following error message appears:
No device connected.
Please connect a FlashScan or AutoCal USB device.
If a device is connected, ensure it is not being used by another application such as the EFILive V7.5 Scan or Tune Software.

Happens in Data, Charts, or Gauges.

That is a confirmed bug. The software is incorrectly attempting to stop data logging on the vehicle even when no vehicle is connected. An update is planned for mid next week.


- Second is with EOPS. This is the thread where you found there was an issue and had me changed GM.EOPS in the data file to XX.EOPS (https://forum.efilive.com/showthread.php?24500-Eops). I had not updated the software since then as that fix worked. Now that I've updated, GM.EOPS seems to be working but for some reason my calc pid to convert that voltage to a pressure stopped working.
To diagnose I tried a calc pid to just read EOPS: return pid("EOPS"); and even that just returns zero.
Thanks
Rob
Can you please send a log file that contains the EOP PID so that I can try and replicate the same issue here.

Regards
Paul

[CR500]

Here's a log file: 18442

I played with it some more.

- open log file
- added my calc pid to selected list
- go to data view and start playback
= calc pid sits at 0 even though EOPS has varying voltage

- edit calc pid
- don't make any changes
- click ok
= calc pid now works

If I open the same log file, add the same calc pid, it doesn't work again and I need to do the same open / save of the calc pid.

I don't know where the calc pids are stored but if you let me know I'll attach it as well.

Thanks!

Rob

[Blacky]

Here's a log file: 18442

I played with it some more.

- open log file
- added my calc pid to selected list
- go to data view and start playback
= calc pid sits at 0 even though EOPS has varying voltage

- edit calc pid
- don't make any changes
- click ok
= calc pid now works

If I open the same log file, add the same calc pid, it doesn't work again and I need to do the same open / save of the calc pid.

I don't know where the calc pids are stored but if you let me know I'll attach it as well.

Thanks!

Rob
In V8 user defined calculated PIDs are stored here:
\My Documents\EFILive\V8\UserCalculatedPids.ini

In V7 user defined calculated PIDs are stored here:
\My Documents\EFILive\V7.5\User Configuration\calc_pids.txt

If you can send me the appropriate calculated PIDs file and athe log file that you are using I'll see if I can see why its not working.
Send to paul@efilive.com

Regards
Paul

[CR500]

More info:

It looks like the issue happens to whichever of my calc pids is added last to the Selected Pids. So its not one specific pid.

I found user calc pids in slightly different location: My Documents\EFILive\V8\Config\UserCalculatedPids.ini

I don't seem to be able to attach the calc pid file with the .ini extension so I changed it to .txt.

[CR500]

18451

[Blacky]

I found user calc pids in slightly different location: My Documents\EFILive\V8\Config\UserCalculatedPids.ini
Sorry, my mistake :)
Paul

[CR500]

No worries, you got me close enough! When's a Mac version coming out ;-)

[Blacky]

When's a Mac version coming out ;-)

:nixweiss::funnypost:

[GMPX]

No worries, you got me close enough! When's a Mac version coming out ;-)
Right after the Linux and PCBSD versions.

[Chuck CoW]

I see that the E92 Commanded fuel pid has been added to the scan tool, but when attempting to log it does not work.

Will you be adding a calculated ben factor pid or do we need to make one ourselves?

Chuck CoW

[GMPX]

I see that the E92 Commanded fuel pid has been added to the scan tool, but when attempting to log it does not work.

In what way? Different value than expected, software crashes, ECM responds not supported?