The listed ECU files are map files only and do not include the software sections. They are 96k files and the map data is located between 0x0001:0000 and 0x0001:7FFF.
Enginuity Definition FileHere is the latest Enginuity Definition File for 16 bit ECUs.Busa1999-2001.zipVersion1.00 - Dec, 1 2007 Basic maps for -24FD0 (needs a lot of work) 1.01 - Jan,25 2008 Added -24F21 ECU rev limiters only, updated -24FD0 limiters1.02 RR 01-26-08 relabeled misidentified RPM limit. Was labeled IGN but is really a fuel limit
Excellent -thank you.The earlier definition in 32bit was based on kawi info: x/256*90-12.5 so there may be 2.5degree diffrence now to earlier definitons. Anyway the earlier formula gave nice -0 degrees on smaller cells which would now be raised to 2.5 degrees.I think that one of the variables contains something that resembles remarkable the ignition advance values in degrees. Also have Innovate DL-32 to check the ignition advance. Recall having a few degrees difference from earlier testing - but never get to confirm this as that has not been a priority. Maybe now its time to get back to this issue.
When asking a question, you can also consider posting it to facebook:http://www.facebook.com/ecueditorcom
RidgeRacer wrote: The conversion is based on the manual listing the advance as 4 degrees at 1150 rpm. The formula I'm using is Degrees = [(map value / 256) * 90] -10
The conversion is based on the manual listing the advance as 4 degrees at 1150 rpm. The formula I'm using is Degrees = [(map value / 256) * 90] -10
ign_div = 256
ign_mul = 66
Just wanted to let you know that we're now able to read and reflash the 16bit Busa ECUs via an OBD interface without notching the ECU. The K-Line OBD interface is identical to the one used by the 16bit GSX-R 600/750/1000s and is very inexpensive to make. You can read more about in this thread:
Here's a pictures of the software GUI:
You can also find additional information on my site here:
Has anyone had issues using these defs with RomRaider? I'm using version 0.5.8 RC1 and the program seems to wipe the first 40 bytes when you save...
For anyone using RomRaider, there is an issue with defining the "storagetype" and "endian" for "static" X or Y tables that will corrupt your binary, so the above definitions files must be cleaned-up before using them with RomRaider. You can also run the "GSXR Sum" utility found here to confirm your binary hasn't been corrupted:
For anyone using a recent version of RomRaider, I created the "RRcheck" utility to check for (and correct) "Static" declaration incompatibilities in XML files that cause the ECU binary file to become corrupted. You can find a copy here:
And here's a pic: