I'm curious as to the reason why the tune file security is updated all the time.
Better compression/different algo to reduce file sizes?
I'm curious as to the reason why the tune file security is updated all the time.
Better compression/different algo to reduce file sizes?
I tried to read LS1A yesterday it finished successfully but show Access violation error after that
this is with the latest fix
EFILive Tuner
Paul, I am receiving the same error Code 1400 on the last release as well as this new one. I did an Uninstall and reinstalled the latest version from scratch.
Best I can figure if you open a Table and let it sit dormant for 5 minutes. For example Using an LS1B tune and go to B0104 and just let it sit for 5 minutes and make no changes and No Saves. Then just Close out of program.
I will send you some logs.
![]()
Hey Ross and Paul,
Something that is new in this release is getting this error when locking AL5 controllers with a custom key.
Everything was done correctly. Got a read from the TCM and then attempted the lock. As you can see something is happening where it is causing the Serial to read offset. Its the same serial, it just starts from a different location.
We have attempted this on several controllers and the results are consistent.
Is there anything else that you need from me in order to help you track this down?? If so, let me know and I will make the time to get you the data that you need. Its sorta important to us.
The only reason we are using 7.5 is because I need to use a custom key, not a generated one from the v2 serial#.
Josh
'04 GMC LLY - L5P, Motech, 6-Spd Conv. ML Trans.
'05 GMC LLY - 250%, 12mm, 67mm Custom Turbo, 6-Spd Conv. ML Trans
'19 3500 RAM - Tuned Aisin 0_o
I'll test it today Josh and see if we run in to the same issue and fix accordingly.
Thanks,
Ross
I no longer monitor the forum, please either post your question or create a support ticket.
I got the logs, thanks. Unfortunately I still can't reproduce it.
One thing to try is to close all V7 software, edit the Registry (run regedit) and completely remove the V7.5 registry key and all it's sub keys. The restart the V7.5 Scan tool, close it (to regenerate the scan tool registry settings), then restart the V7.5 tune tool and close it (to regenerate the tune tool registry settings).
The registry key to remove is \\HKEY_CURRENT_USER\Software\EFILive\V7.5
Regards
Paul
Before asking for help, please read this.
The V8 software doesn't use the V7.5 registry settings. So the V8 problem is most likely not related to deleting the V7 registry settings.
Try running the V8 installation again and it/should will fix any damaged or missing files from the install.
The error is most likely referring to the USB driver dll file located here:
C:\Program Files (x86)\EFILive\Drivers\EFILive\Win-XP-Vista-7-8\i386\ftd2xx.dll
PS. V8 keeps all it's settings (the equivalent of what V7 keeps in the registry) in multiple *.ini files in the folder: \Documents\EFILive\V8\Config
It ended up being a lot easier to manage *.ini files while Microsoft was transitioning from XP to Vista to Win7, each major Windows update brought changes to the registry security settings. Using the registry turned out to be more trouble than it was worth during those years.
Before asking for help, please read this.