....
....
Last edited by LRT; 05-24-2021 at 10:45 PM.
....
Last edited by LRT; 05-24-2021 at 10:46 PM.
Thank You!
Last edited by windsma; 01-17-2019 at 02:29 AM.
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.
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:
Last edited by antus; 01-17-2019 at 03:49 AM.
....
Last edited by LRT; 05-24-2021 at 11:05 PM.
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.
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.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.
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.
Can you please update you zip with the plugin I posted above and remove the stolen copies?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;
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....
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-17-2019 at 02:57 AM.
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.Originally Posted by brandonwh64
....
Last edited by LRT; 05-24-2021 at 11:05 PM.
Thank you LRT! Also would your XDF work with my 09354896 ECU? I have downloaded my bin file and when I open it in tuner pro, the values are not right. I used the 512 checksum and the 12202088 XDF.
Hi guys - I`m cross posting from the corvette forum here.
I ordered the AllPro USB ELM327 adaptor and have been able to read my BIN file successfully, 01Z06 with mods and a tune. Great! I think, going via the other thread that I can also write the cal changes I want, even better.
However the final piece needed is data logging. Can anyone help? I found a few LS1 tagged ADX files but none of them get anything in TunerPro from my car.
I set tunerpro to use plug-in, set plug-in to ELM327OBDII interface.
1 of the ADX files lets me connect ok but rate is ~1Hz and i'm not getting any channels coming back. 2 of the ADX files let me connect but with rolling errors and no data. The other files don't even get me connected....
The built in plugin, as far as i can tell doesnt do anything. I use scalxl pro at this stage as ive had a license for it for years. But I do have a working elm327 adx, but a quick test this morning shows it needs some fixes to work on the allpro. If you want to help and understand the elm protocol and adx authorship i'll send it, else give me a few days and i'll see if i can get it going and release it.
Did you ever get an XDF file to work with your 09354896 ECU?
No, i updated my pcm to an OS with an available xdf file and now all is working fine
Posting Permissions
Reply With Quote
Bookmarks