32920-41G00 112100-2600 12V NEP0G3 I have also done a preliminary Enginuity definition. I will update this file as I update the definition and post rev notes in this thread.
Ver 1.00 4-30-08 Untested prototype with limiters, crude ignition, fuel maps identified, full map table listings. Ver 1.10 5-14-08 Modified so definition will work with either US or Euro version. Ver 1.11 5-17-08 Updated Ignition and Alpha-N definitions. Ver 1.13 11-17-08 Added Fan on/off Temperature table Ver 1.14 02-24-09 Updated Speed Density Maps
MAKE SURE YOU ACTUALLY CHECK THE NUMBER ON YOUR ECU. THERE ARE TWO VERSIONS OF ECU FOR THE 2005/2006 MODEL
I've updated the post above to include the Euro version of the GSXR-1000 K5/K6. (Thanks to Hans in Germany)
In comparing the two versions I found the software code section of the images exactly the same with some minor, less than 1%, differences in the map sections.
For that reason I have rewritten the Enginuity / RomRaider definition above to use either version.
BTW I think this commonality between the two images speaks to the validty of both.
As far as I know the EU bikes have immobilizer but the US versions don't. Do you know how this works if the ECU SW is the same? Is it configured in the EEPROM if the ECU looks for the immobilizer or not?
That would be the logical assumption, that there is simply a map 'switch' byte that enables/disables the immobilizer test routines.
BTW if you wish to discuss this subject further please start another thread. I'd like to keep this one strictly for listing map and definition version information.
Finally had time to look at the Gixxer definitions file. Looks very similar to Busa ECU.
A couple of questions: - Will ya check the serial protocol if its alike to busa... if that is compatible enough I can fairly easily convert ECUeditor for gixxer K6/K6 too so that we can have a dyno tuning tool and start to put this info into real world tuning experience. (Having read the gixxer K7 manual it surely looks the same, but there may be differences) - Additionally would need idle map addresses MS0/MS1 - when tuning we just copy the tuned map information into idle maps but tuning a bike without ability to tweak the idle maps is not really yielding good results as the transition points at around 2400rpm becomes too big. - Also the TPS<->IAP (alphaN-speed density) switching point, e.g. TPS10% is important information from tuning perspective. We need to know which map we are tuning at any certain point of time. - If you can find injector size constants that would be additional benefit, but not utterly important. - Last important item is regarding the serial protocol. Would need variable pointers for: RPM, TPS, IAP, Ambient, CLT and pulswidth high byte. There should be a long table of RAM variables before ROM area.
Interesting to see if we can accomplish the same with Gixxer as with Busa tuningwise ?
__________________
When asking a question, you can also consider posting it to facebook:
From what I've seen of the code the different bikes are very much the same. GSXR 1000, 750, Busa all have the long look up table at the end of the code. I'm sure they all have the same serial telemetry capability.
One thing that could help me find them faster is if you could give the busa addresses of the things your interested in.
On a general note it is finally summer weather here and school is out so I plan to spend more time with the family and actually riding motorcycles rather than dissecting them.
On a general note it is finally summer weather here and school is out so I plan to spend more time with the family and actually riding motorcycles rather than dissecting them.
I know the feeling... now my bike is waiting for a gearbox repair to start so time to think this kind of projects for a couple of days. Hopefully can start some time next week...
I will write a separate thread about the more specific details on this matter when have more time on this.
__________________
When asking a question, you can also consider posting it to facebook:
Petrik, i am trying to get the right theory going here so I can do some testing on my 1000. What were you able to accomplish so far with the busa that you may be possible with the 1000? Busa before and after comparison? Secondly, if i was to send you a map with some ignition changes, would you be able to look at it and tell me if something was "beyond safety" by looking at the timing numbers?
The remaining 12 maps are 3 groups of 4 individual cylinder maps.
The group used is selected by gear as defined in the Ign Map Gear Select table.
The stock settings are:
Gear 1,2 Group 1 Gear 3,4 Group 2 Gear 5,6 Group 3
Just to make sure I understand the function of this table, if the values in the Ign Map Gear Select table are all changed to 3, will the Group 3 ignition maps be used for all gears, or is the Ign Map Gear Select table just informational?
Will closing the clutch switch cause the ECU to use the Neutral limits and ignition/fuel maps? If so, any idea which table will allow this to be disabled or changed?
I looked at the code and there is no map switch that disables the clutch in same as neutral.
That doesn't mean it can't be done. We can change program instructions the same way we change map values. The problem is there are a lot (20+) places in the code where clutch is tested with neutral. I don't know what half of them do.
The easy thing of course would be to disable the value at its source. Mask out that bit so the bike never sees clutch in but that could have unknown effects like messing up the safety lock out and the bike wouldn't start.
What exactly is your application or reason for wanting the clutch in disabled?
Several reasons. Just convenience on a full roadrace bike mostly. The bike is usually on stands, and I'm usually holding a laptop in one hand, so using both hands to start the bike kinda bites. It's also an easier starting procedure for the rider to use, especially while under duress. Finally, should the gear position or clutch position switch sensor fail or become inoperable during a race, the bike can still be restarted and run at full power, rather than use the neutral limits and maps.
I think the safety lockout can be bypassed by installing a jumper in the sidestand switch and supplying a fixed ground to the starter solenoid (rather than using the clutch switch as a ground). Surprisingly, I've found that removing the clutch pin from the ECU will cause the ECU to report a clutch-in state, even though the schematic shows that circuit should be normally-open to ground.
In looking at the code the first thing the ECU does after reading the i/o port register is invert some of the bits, including the clutch. It would be a very easy thing modify the byte that flips the bits so the clutch bit is not included.
In other words I can make clutch in look like clutch out and vise versa. So if you disconnect the clutch wire from the ECU it would look like clutch out.
BTW neutral is a separate issue. With the above mod if your gear position sensor fails or goes out of range the ECU will still use the neutral maps.
So would changing the neutral maps and limits to match the 5th gear maps and limits, along with disconnecting the clutch wire from the ECU and jumpering the clutch switch get me where I need to be without modifying the clutch position byte in the ECU?
You can use the 32920-41G10, it is a 2005 GSX-R 1000 US and works with your ECU. Don´t use the 32920-41G00, it is a EU bin with immobilizer and your engine won´t run with it.
Blackgixxer should be able to answer this question. I believe he successfully flashed US code into his EU ecu and it worked but I don't remember the details.
I think I can help you. But what makes you think that your bike´s ECU isn´t ok? If you put an US ECU in a EU bike instead of the EU ECU the bike won´t run. You can contact me over the "Send Email" option in my profile.
I did a little bi tof research on the difference between the two bins. I found differences in some known and unknown maps. But there are some differences, which do not lie in the scope of the maps of the definition file, also.
Are some maps missing? I thought, I have read that the maps are extracted automatically from some source file.
Is a map file of the 32920-41G60 ecu available for download, somewhere?
I have it but haven't posted it because you can't use the RomRaider Definition for the -41G10/00 and I haven't had time to write one for the -41G60 yet.
I did the reflashing on my 06 1k.... with all this information it was really easy to do... Thanks guys for all the information and time... The results: I changed timming maps rev limiter, and some of the timming: ....wow...my own bike try to kill me ...it was so much fun again, I was getting bored with the power delivery and i was going to buy a new bike....first ride she try to kill me 3 times, now I'm going to play with some more timming... Quick question, is a way to fix speedo missreading thru the ECU? I don't want to use another box (speedo healer) if it can be fixed
Keep up the great job maybe you guys to hear it often but we do appreciate the help
I show the X axis Manifold Absolute Pressure in volts. This seems to be the unit that people are actually logging in and therefore the easiest to translate to a map column.
When you first start your run power up the ecu for a couple of seconds to measure the IAP value. When the engine is off IAP = SAP. Then to find which map cell corresponds to a Speed Density value take your baseline engine off IAP Voltage and subtract the log IAP Voltage. The resulting voltage can then be used to find your place in the X axis of the Speed Density maps.
Does anyone have a flash for a 05 with full exuast, bmc, short stacks, pair mod, that I can try as a base and tune from thier. Im not real familar with this yet and want to give it a try. Thanks for all your help!!
It is still early days with the 1000s. We of course hope that as more people start flashing their 1000 they will share their maps and we can build up a library of base maps.
Also, I could not find a place for "memo" or "notes" to save with the bin in RomRaider so that it would be easy to remember details about the bin edits.
Sometimes, I just use the filename to describe what the map contains (e.g. 41G-Mod-TopSpd-IGN5+100Red.bin). That works fine for binary and 2D tables like limiters and redlines, but not so well for 3D map changes. Then again, powercommanders, EMPros, Tekas and Z-Fi boxes allow very little room for verbosity in the comments fields, where they exist.
If you need more than 255 characters to describe the bin file, just name the map file with the venue, date and revision, then create a text file in the same directory with the same name (different extension) and document away in that file. At the start of a race weekend, I will start with a -- revision level, then use -A, -B, etc., so I can keep a record of my changes not only during the weekend, but throughout the season. For example, in two weeks, I will use 20090320_Fontana_--.bin and a 20090320_Fontana_--.txt. Putting the date first and in that format allows for better sorting.
Can anyone tell me about the accuracy of the limiter numbers in the map files? . The K5 I've been fiddling with hits the standard limiter at 13000 according to both the logger and a dynojet dyno.
So far they have proved very accurate. The limit calculation is not unique to your bike but used on all the 7052 equipped Denso ECUs I've come across so far in Suzuki, Kawasaki, and even Arctic Cat snow mobiles.
Besides consider that the difference between 13 000 and 13 200 is what, 1.5%? And truthfully both your logger and dyno show exactly 13 000? Not something like 13 047 on one and 13 068 on the other?
Any chance your bike thinks it is in Neutral? Do you have any kind of aftermarket clutch lever setup that might make the ECU think the Clutch is pulled in? The neutral limit is 12 875
I'm having problems updating my definition file. I'm sure its something simple but i need some help. WHen I click on the link above and save, it tells me its gonna overwrite the existing file and I save it. The problem is when I open up romraider, where can I find my .bin file to open and edit? The only .bin files I can open are the ones that are already in my computer which still have the version 1.13 definition.
The posted definition works with K5 and early K6 41G00(EU) and 41G10(US) only.
The K6 41G50(EU) and 41G60(US) are only slightly different but different enough that all the maps have different locations. If they move by even 1 byte you have to rewrite the whole definition.
It is on my list to do I just haven't gotten around to it yet. Same with the K3/K4.
The FI light on the PAIR valve should be an easy mod for the software. The fuel level indicator on the other hand is an instrument cluster issue. The ECU has no control over it.
It's been a while, but I believe the PAIR light can be disabled by placing a jumper across the PAIR solenoid electrical connector. The fuel level light can be disabled by placing a 22 ohm resistor between the sensor wire and ground.