PLX2 corrupt?

[purrvert]

My V1 stopped logging PLX2, just shows open voltage of 3.6v. Using Windows 7 in Bootcamp V7.5.7 build 283. I have an older version on my computer V7.2.7 build 236, When I review the identical log file in both versions build 236 AD2 shows correct voltage but changes PLX2 to LM1. Also both versions add two un-selected PIDS, Ext.AD1 and Ext.Temp1 Thermocouple. I load 21 pids and record 23. Attach far left build 236 center build 283 right pid selection in V1. Anyone seen this before?
One more item. when loading pids to V1 bottom frame of build 283 scan shows generic, vin and operating system 2030003, I select controller and it shows GM-VIN-2030003 but when I connect to V1 it reverts to generic-vin-2030003.


18652

[joecar]

Try V7 build 286 from here: July-08-2015-EFILive-Public-Pre-Release (https://forum.efilive.com/showthread.php?25758-July-08-2015-EFILive-Public-Pre-Release)

[purrvert]

Iinstalled build 286, exactly the same corruption. I can select PLX2 pids in build 236 after loading log and they read OK.

[joecar]

Ok, something broke after V7 build 236.

[joecar]

I'll pm Paul.

[purrvert]

Thank you. I probably need to remove all EFI files and start with a fresh install. Lately when I close Tune Windows reports missing handles.

[joecar]

...
Lately when I close Tune Windows reports missing handles.Post a screenshot.

[purrvert]

Won't do it now. "Invalid Handles" roughly six different dialog boxes.

[purrvert]

I've uninstalled both versions of scan and tune. Reinstalled build 286. It's getting worse. Six dialog boxes for 'invalid handles' appear when I close tune, all code 1400. Tune authorization set to demo but scan is not connected and tune Help register has been filled in for commercial. I'm lost.



1866918670

[joecar]

My V1 stopped logging PLX2, just shows open voltage of 3.6v. Using Windows 7 in Bootcamp V7.5.7 build 283. I have an older version on my computer V7.2.7 build 236, When I review the identical log file in both versions build 236 AD2 shows correct voltage but changes PLX2 to LM1. Also both versions add two un-selected PIDS, Ext.AD1 and Ext.Temp1 Thermocouple. I load 21 pids and record 23. Attach far left build 236 center build 283 right pid selection in V1. Anyone seen this before?
One more item. when loading pids to V1 bottom frame of build 283 scan shows generic, vin and operating system 2030003, I select controller and it shows GM-VIN-2030003 but when I connect to V1 it reverts to generic-vin-2030003.


18652The EXT.AD1 and EXT.TEMP1 are along for a free ride, they do not occupy any pid channels.

[Blacky]

I've uninstalled both versions of scan and tune. Reinstalled build 286. It's getting worse. Six dialog boxes for 'invalid handles' appear when I close tune, all code 1400. Tune authorization set to demo but scan is not connected and tune Help register has been filled in for commercial. I'm lost.

Those registration details are not correct. They do not match what we have on file for that FlashScan V1.2 device.
Please send your FlashScan authorization code to me at paul@efilive.com and I'll re-issue you with the correct registration details.
You can generate the authorization code using the V7 menu option: Help->FlashScan V1 PCM licensing... Then select the [Authenticate] tab page and click the [Copy] button to copy the "Auth code" then paste it into the email.

Regards
Paul

[joecar]

Post your log file here, I'll take a closer look at it with latest software.

[purrvert]

Joecar,
here's a run to the grocery store.
1867118672

[joecar]

Joecar,
here's a run to the grocery store.
1867118672Which file is ok in V7 build 236...?

Which file is corrupt in V7 build 286 (BB-Log_87.rfi...?)...?

[purrvert]

Neither log is OK in either build. 0087 reads AD2 correctly after about a minute but changes PLX2 to LM1, 155 mph sustained speed? I believe 0087 was saved with 236. 0050 shows open voltage for AD2. The same pid selection shown in my original post was used for both logs.

[joecar]

Ok, I'll point that out to Paul.

[purrvert]

Update. Read a non related post by Blacky "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." I don't remember how I got started after hard-drive failure besides loading build 236 from originally supplied disk and then upgrading to build 283 and the non read of AD2 showed up. After reading post I found build 256 and installed and tested OK. Installed 281, 282, 286 and all is well.
Only the Electronic Throttle doesn't show red directories unless V1 is plugged in. I understand that is a 'KEY' problem.

link to the post
https://forum.efilive.com/showthread.php?25502-Known-issues-with-May-01-2015-Public-Release&highlight=282

[Blacky]

Update. Read a non related post by Blacky "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." I don't remember how I got started after hard-drive failure besides loading build 236 from originally supplied disk and then upgrading to build 283 and the non read of AD2 showed up. After reading post I found build 256 and installed and tested OK. Installed 281, 282, 286 and all is well.
Only the Electronic Throttle doesn't show red directories unless V1 is plugged in. I understand that is a 'KEY' problem.

link to the post
https://forum.efilive.com/showthread.php?25502-Known-issues-with-May-01-2015-Public-Release&highlight=282

For future reference, each installation executable file is 100% self contained. You don't ever need to install an older release before installing the latest release (or pre-release). It doesn't matter if you do, it's just not necessary.

Regards
Paul

[Blacky]

Only the Electronic Throttle doesn't show red directories unless V1 is plugged in. I understand that is a 'KEY' problem.

That is how it is designed to work. The throttle tables are only available to customers who have a FlashScan device and that FlashScan device is connected when the software is started. The throttle tables will not show up based on software registration details alone.

Regards
Paul