DIY PROMDo It Yourself PROM chip burning help. No PROM begging. No PROMs for sale. No commercial exchange. Not a referral service.
Welcome to ThirdGen.org!
Welcome to ThirdGen.org.
You are currently viewing our forum as a guest, which gives you limited access to view most discussions and access our other features. By joining our community, at no cost, you will have access to post topics, communicate privately with other members (PM), respond to polls, upload content and access many other special features. Registration is free, fast and simple, join the ThirdGen.org community today!
The change was to standardize the addressing of XDF items for use with or without the NVSRAM board. Functionality is the same.
I did sneak in one tidbit. (see item 5)
Revision history and notes: 41026 V4A & B Version: 04-30-2008 1.) Corrected issue with NVSRAM usage where data tables were not located to fit in the available memory space. Checksum would fail and default “chip” program would restore negating any changes on the fly. 2.) Version 4A created for std use. 3.) Version 4B created for use with NVSRAM module. (confirm at Location 800A-800D to verify the version) 4.) DXF changed to allow both bins to operate from the same definition file. File: S_AUJP_V4a.XDF Late Error Change Ext VE table address to "9A0" in XDF file and save.
5.) Added Program ID function. If ALDL location 16 is changed to read $01BA, the value at L800A will be displayed in the datastream. Great for switcher guys to see current program that is being run. Display will be in the NV Ratio item. Figured nobody uses that anyway. No conversion needed. 0-15 Value 6.) Reworked the V4 Document to show changes.
Major Note: When converting from the original V4 to this new version, You can use the “Difference Tool” in TunerPro to copy over your existing values.
DO NOT COPY ANY VALUES FROM ADDRESSES L8998 AND HIGHER. These items were rearranged and will certainly not be what you want. Print screen or Export your data to a text file and manually enter your setup numbers. There is not many and doesn't take long. This would include:
Wide Band setup options 1 & 2
VE Upper Table Extended to 6400 RPM (Z69)
PE , % Change to AFR Vs. RPM Extended Table (Z69)
Launch Mode Retard Vs Speed (Doesn’t work so don’t bother)
Wow you guys have a lot of work into this so first I'd like to thank you for sharing!
But even after an hours worth of reading I can't decide if I should start with the 1024 or 1026?
Tomorrow I will be helping a freind with his 5.7L cammed TPI engine he says was from a Camaro and he got a 1227730 with chip and harness from somewhere? It runs well, no codes, idle needs work, but initail data shows lean overall.
Since there has been so much work done on this I figured it would be a better start. So 1024 or 1026?
__________________ GearHead-EFI.com EFI Conversions and Chip Tuners!
After several more hours research I think your right. The 1026 zip file has 2 bins. One for NVSRAM one for standard. 1024 does not. This was the most confusing part for me as I did not understand if 1026 was just updated or 1024 was just for NVSRAM...
1026 for sure.
The 1024 file works but not for the NVSRAM module.
The correction was made by rearranging the additional features so the XDF file is different for the 1024 to the new 1026.
I'd like to have Moates remove the 1024 just so there are not any problems with people using new definition files with it.
Be sure to go the the "S_AUJP V4 released" thread and do the couple of edits to the definitions so all is current.
Jp
