Bringing TBI and Multi Port Fuel Injection to a New Level.     EFI Conversions and Tuning! Seattle to Portland! E-mail Tuning Consultant!
Page 1 of 3 123 LastLast
Results 1 to 15 of 37

Thread: Free LS1 Tuning Software (all you need is TunerPro)

  1. #1
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168

    Free LS1 Tuning Software (all you need is TunerPro)

    *** Moderator *** - please sticky this thread so that people may more readily find it

    Over 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:

    http://www.gearhead-efi.com/Fuel-Inj...with-Checksums

    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. Please read the thread linked below:

    http://www.gearhead-efi.com/Fuel-Inj...han-You-Think)

    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. ***
    Attached Files Attached Files
    Last edited by LRT; 01-15-2019 at 07:29 AM.

  2. #2
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168
    XDF - 512Kb LS1 PCM

    The XDF files attached below are for use with 512Kb PCMs (Service Numbers 09354896 and 12200411). These PCMs were generally used from 1999 to 2002. Corvettes in 2003 still used this PCM, as did some Holden models until 2004.
    Last edited by LRT; 01-15-2019 at 07:24 AM.

  3. #3
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168
    XDF - 1Mb LS1 PCM

    The XDF files attached below are for use with 1Mb PCMs (with various Service Numbers). These PCMs were generally used from 2003 to 2006. Some models continued to use this PCM in 2007.
    Attached Files Attached Files
    Last edited by LRT; 01-14-2019 at 08:50 AM.

  4. #4
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168
    XDF - Custom Operating System (COS)

    COS have a variety of additional functionality. Generally a COS1 is the same as the original GM Operating System, with the exception of being able to operate in Speed Density mode (i.e. no MAF) while maintaining the use of High Octane Spark function.

    Generally a COS3 has all the features of a COS1, plus the additional feature of supporting Forced Induction (i.e. boost) up to 3 BAR.
    Last edited by LRT; 01-14-2019 at 05:15 PM.

  5. #5
    Carb and Points!
    Join Date
    Jan 2019
    Age
    38
    Posts
    1
    Thank You!
    Last edited by windsma; 01-16-2019 at 04:29 PM.

  6. #6
    Carb and Points!
    Join Date
    Dec 2018
    Age
    35
    Posts
    2
    Thank you!!! 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 0411
    Last edited by brandonwh64; 01-16-2019 at 04:57 PM.

  7. #7
    Fuel Injected!
    Join Date
    Dec 2015
    Age
    38
    Posts
    63
    Thank you for all the work you've put into these, I know how much time they take to create.

    I can't wait to see where this leads us now that open source flashing is now possible.

  8. #8
    Fuel Injected!
    Join Date
    Dec 2015
    Age
    38
    Posts
    63
    Quote Originally Posted by brandonwh64 View Post
    Thank you!!! 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 0411
    The 512K Xdf's are OS dependent. If you have a supported OS on an 0896 there is no reason it won't work. It is a 0411 for all purposes.

  9. #9
    Fuel Injected!
    Join Date
    Jul 2013
    Location
    Australia
    Posts
    51
    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. Thats nasty. 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:
    Attached Images Attached Images
    Attached Files Attached Files
    Last edited by antus; 01-16-2019 at 05:49 PM.

  10. #10
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168
    Quote Originally Posted by brandonwh64 View Post
    Thank you!!! 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 0411
    Hello 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 09354896
    0411 = Service Number 12200411

    Regarding 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.

  11. #11
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168
    Quote Originally Posted by antus View Post
    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. Thats nasty. 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.

  12. #12
    Fuel Injected!
    Join Date
    Jul 2013
    Location
    Australia
    Posts
    51
    No, this is the first public release of the 1mbyte version, though its just a minor update. I can see that the 1mbyte dll you posted is someone elses hack of my dll as there is an extra space where someone typed over the 512kbit string.

    Code:
    This plug-in provides a way to calculate checksums for LS1 512k bin files.
    This plug-in provides a way to calculate checksums for LS1  1Mb bin files.
    The source code for the guts of it is published here but I cant post in full because of the restrictive license on the tunerpro SDK.
    https://pcmhacking.net/forums/viewto...&t=3845#p85328

    The offical 1Mbyte support is added by duplicating the if which sets os_hack=1 and updating the end address for the extra bin range.

    Code:
                // if we detect its the LS1 OS range, then enable a hack to skip parts that are not included
                if (pCalcInfo->dwRegionStartAddress==0 && pCalcInfo->dwRegionEndAddress==0x7FFFD) os_hack=1;
                if (pCalcInfo->dwRegionStartAddress==0 && pCalcInfo->dwRegionEndAddress==0xFFFFD) os_hack=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....

  13. #13
    Fuel Injected!
    Join Date
    Jul 2013
    Location
    Australia
    Posts
    51
    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.

    plugin hack.jpg
    Last edited by antus; 01-17-2019 at 07:07 PM.

  14. #14
    Fuel Injected! roughneck427's Avatar
    Join Date
    May 2012
    Location
    Fresno CA
    Age
    43
    Posts
    266
    Wow i can see this is going to be ugly in some areas. Not sure why someone would want jack with the checksum and repost it. I know i had messaged Antus awhile back pcmhacking about a 1mb checksum and he offered to to make one. And furthermore anyone thats been involved with this project its common knowledge who made them. People are going to mess up a good thing.I can see xdfs going the same way.

  15. #15
    Fuel Injected!
    Join Date
    Jun 2014
    Posts
    168
    Quote Originally Posted by roughneck427 View Post
    Wow i can see this is going to be ugly in some areas. Not sure why someone would want jack with the checksum and repost it. I know i had messaged Antus awhile back pcmhacking about a 1mb checksum and he offered to to make one. And furthermore anyone thats been involved with this project its common knowledge who made them. People are going to mess up a good thing.I can see xdfs going the same way.

    Only if people choose to be part of the problem, rather than part of the solution.

Similar Threads

  1. Opinions on OBDII auto tuning software
    By scuzz in forum OBDII Tuning
    Replies: 9
    Last Post: 07-16-2016, 08:23 PM
  2. Learning a new ECU and tuning software
    By Xnke in forum Introductions
    Replies: 0
    Last Post: 06-24-2015, 12:02 PM
  3. sale on tgo for laptop and tuning software.
    By one92rs in forum Buy - Sell - Trade - Wanted
    Replies: 1
    Last Post: 04-25-2013, 08:28 AM
  4. Long Starting with EBL Flash and TunerPro software
    By beast94 in forum GM EFI Systems
    Replies: 18
    Last Post: 06-02-2012, 05:28 PM
  5. Nissan Tuning software and Hardware.
    By Six_Shooter in forum Other EFI systems and related topics
    Replies: 0
    Last Post: 10-24-2011, 09:22 PM

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •