Best Ls1 Tuning Software

. Moderator. please sticky this thread so that people may more readily find itOver two years ago, I posted a couple of XDF files for use with TunerPro editing software, specific to the LS1 type PCM. Below is a link to my original thread:I am not going to revisit the comments made in the original thread, nor the number of times that “free” LS1 flashing software has failed to materialize. I am cautiously optimistic that this may finally be on the horizon.

WinTEC Engine Tuning Software 3.5. Electromotive Inc. The new WinTEC3 Software is Electromotive's most powerful engine tuning software ever! With newly added features, expansion of existing features, simplification of terms, and a sophistication level that tuning experts will appreciate, WinTEC3 is the tuning environment for the new millennium.

Please read the thread linked below:A hard working group of enthusiasts is attempting to bring a no cost LS1 Flash Tool into existence. Given this development, I went back to creating more XDF files for LS1 type PCMs. These XDFs are based on the original work of Dimented24x7, and the disassembly that he shared freely.This disassembly allowed me to create a template for basic tuning (enough functions for an enthusiast to tune their own PCM). Each subsequent XDF was based on this template and disassembly - the same way that commercial tuning software companies would have developed their product.The attached instructions (PDF) below have been updated from the 2016 version.A new feature is the “Operating System” button, near the bottom of the Parameter Tree.

This will show you the Operating System of the LS1 type PCM BIN file that you have opened. No matter which of the accompanying LS1 XDFs that you have currently selected for use with TunerPro, the Operating System will ALWAYS be correctly displayed - for all 512Kb and 1Mb LS1 type PCMs.This feature will help ensure that you select the correct XDF for editing your BIN file. This is how commercial tuning software works. It determines the Operating System in use, and then automatically loads the corresponding editing file.

You must load the corresponding XDF manually - but the concept is the same.Please read the attached instructions. Then download both of the Checksum Plugins (512Kb and 1Mb), and place them into the TunerPro folder on your computer, as described in the instructions.After this has been done, download the XDF files from the posts below. Note: I will update posts #2, #3, and #4 below with new XDFs as these are developed.

Nice work on the XDFs but it'd be nice if you had contacted me before you included versions of my checksum plugins, and provided creditation for my work. Also, you should NOT load both checksums. The 1 Mbyte should be an update to the 512kb, and carries the same internal GUID as the earlier version which needs to be unique. In fact, I think tunerpro will detect this and ignore the older one and use the 1 Mbyte plugin for all. Also grrr at whoever patched out my email address from the DLLs!:( Im not saying its you but it definately has happened.

ZIP IOMEGA 100 DRIVERS FOR MAC DOWNLOAD. June 22, 2018adminBluetooth DevicesNo Comments. I saw some community message suggesting an old Windows version might work with Zip drive. The PC actually acknowledges the plug in of a Printer probably the parallel cable. A few Zip disks could back up most hard drives in; one Zip disk could hold a bootable system plus diagnostics. Iomega zip drive software download. Every Mac-formatted ZIP disk has a copy of the 'on-disk driver' on it. When you boot with the option key held down, this instructs the Mac to 'scan all connected drives' to look for bootable copies of the OS. Even though the ZIP disk doesn't have a copy of the OS on it, the Mac should scan the USB bus, and load the on-disk driver. Zip disks not mounting could be a bad Zip drive (as I had) not the driver's fault. Try this when upgrading your Mac OSX versions: 1) after upgrading the Mac OS version, use the Iomegaware 4.0.2. Iomega driver free download - Iomega NAS, Iomega QuikSync, Digidesign CoreAudio Driver, and many more programs. Update Mac OS 8.5 or 8.5.1 to OS 8.6 for improved system performance. Save On IOMEGA ZIP Drives Online At Office Depot Free Delivery On Orders $25+Iomega Zip 100 USB External Zip Drive PC / Mac $44.99. Iomega zip 100 external portable drive. Good preowned condition. Does not include the Quiksync software, will.Find great deals on eBay for iomega zip 100 and iomega zip 100 usb.

I'd like to clean that up.For the checksum plugins to work you'll need the VC2010 redist package installed on your PC else it'll fail to load, and then it wont update the checksums which will cause problems flashing. Also note that you only need the plugin for the OS Segments, and unless you have code patches (I dont think anyone has developed any yet) you can and should use the built in tunerpro checksum calculations instead as that will remove the external dependency on the checksum plugin and in turn the VC2010 plugins so that it will always work.I'll attach my build of the 512kbyte and 1mbyte plugin.

If you want to talk plugin development send me a PM.Here is an example of checksum without a plugin for the engine calibration segment, the same applies for all segments except the OS segment. Also would it be possible to get these XDFs complied into a ZIP file?.Edit. Would these XDFs work with a 4896 ECU?

Its pretty much the same as a 0411Hello Brandonwh64,Great questions - if you have them others will too - will try to answer clearly.Regarding PCM Service Numbers.Sometimes people use abbreviations for these, rather than the complete service number.4896 = Service Number 11 = Service Number 12200411Regarding zipping all of the XDF files.I purposefully did not put all of the XDFs into a zipped folder - so people could see at a glance what was available, and what was not.Hopefully this makes sense. Nice work on the XDFs but it'd be nice if you had contacted me before you included versions of my checksum plugins, and provided creditation for my work. Also, you should NOT load both checksums. The 1 Mbyte should be an update to the 512kb, and carries the same internal GUID as the earlier version which needs to be unique. In fact, I think tunerpro will detect this and ignore the older one and use the 1 Mbyte plugin for all.

Also grrr at whoever patched out my email address from the DLLs!:( Im not saying its you but it definately has happened. I'd like to clean that up.For the checksum plugins to work you'll need the VC2010 redist package installed on your PC else it'll fail to load, and then it wont update the checksums which will cause problems flashing. Also note that you only need the plugin for the OS Segments, and unless you have code patches (I dont think anyone has developed any yet) you can and should use the built in tunerpro checksum calculations instead as that will remove the external dependency on the checksum plugin and in turn the VC2010 plugins so that it will always work.I'll attach my build of the 512kbyte and 1mbyte plugin. If you want to talk plugin development send me a PM.Here is an example of checksum without a plugin for the engine calibration segment, the same applies for all segments except the OS segment:Hello Antus,I have worked with more people than I can count, or recall, over the years - helping them with their projects, and trying to get the tuning portion of this coming along.The 512Kb Checksum Plugin has been posted on this website since 2016, and on your Github site for nearly a year - with no comment from you (or anyone) with respect to “credit”. If it is yours, then please feel free to take credit for it.I don’t recall you ever posting a 1Mb Checksum Plugin, but if you wish to take credit for that also, please do.I located some old files recently, that had been cast aside the last time a “free” flash tool failed to materialize, which contained the 1Mb Checksum Plugin, and the basis for the Corvette XDFs attached in post #2, and the COS XDFs attached in post #3.If the Corvette XDFs are your work, please take credit for those also.

If the COS XDFs are your work, please take credit for those also.I am not about taking credit for anything. I am about trying to get this done for the average fellow’s benefit. This has meant donating thousands of hours of my free time over the years.I have been quietly sending things to Pete S. For some time now - not wishing any credit, nor was I concerned with how this material would be used by others for a non-commercial product. Everything that I sent to Pete S. Had to be “unlocked”, so that your group could have full access to my work.

This did not concern me, as it was supposed to be an open sourced, non-commercial venture.Some of the material that I sent, was never posted to the Github site - which made we wonder how it was actually being used. When I recently could not get access to upload things to your Github site directly, I elected to post things here.The XDFs and Checksum Plugins both work harmoniously in TunerPro. The Checksums are properly calculated and saved to the bin file. No problem loading both Checksum Plugins concurrently.

Code: // if we detect its the LS1 OS range, then enable a hack to skip parts that are not includedif (pCalcInfo-dwRegionStartAddress0 && pCalcInfo-dwRegionEndAddress0x7FFFD) oshack=1;if (pCalcInfo-dwRegionStartAddress0 && pCalcInfo-dwRegionEndAddress0xFFFFD) oshack=1;Can you please update you zip with the plugin I posted above and remove the stolen copies?If you need more proof see the filesystem string in the dlls from my server where oseplugin is mentioned, which is a completely unrelated plugin for older delco pcms on pcmhacking.net. Thats in all versions. LRT, you have done great work, and I understand the confusion, this hacked version has been passed around and I have just been informed someone is or was selling an ls1 flash tool on ebay, and they removed the credits and included it in the package they are selling. So that is the source of the hacked version. It is deliberately stolen work, but not by anyone here. I am happy for the real version to be passed around and I have shared how it works for the community and I have shared my ls1flash-free source and kernel with NSFW and open sourced a lot of my former work in PCM Hammer but I have a problem with this plugin. I dont think its fair to strike my name out of it.

Please dont distribute the hacked version. Since we are all a community (or a couple of communities) working towards the same goal, you are welcome to distribute the one I posted above.Now I understand whats going on, and I see how the 2 bytes of guid were hacked. The 2 stolen copies can load side by side because of the differing IDs, and they hacked the DLL twice because they couldnt add the one line of code that was needed. So they just changed 7FFFD to FFFFD in the second copy.

To be very clear I am only talking about the checksum dlls, not the rest of LRTs work which is fantastic and a huge needed piece of the free flashing solution.