1. Porting of most of the features available in the GEN2 Hayabusa to other platforms (This is currently the plan for future efforts, although some features will be limited due to research / identification of the values and address locations in the various platforms)
2. Adjustable high and low limits for 2-step ignition cut (Clutch in rev limiter)
3. Intake Air Temperature compensation maps (or at least the ability to lock at a set value)
4. Engine Coolant Temperature compensation maps (or at least the ability to lock at a set value)
5. Intake Ait Temperature sensor calibration maps (ability to program different sensors for use, similar to IAP sensor in GEN2 extended boost code)
6. Engine Coolant Temperature sensor calibration maps (ability to program different sensors for use, similar to IAP sensor in GEN2 extended boost code)
7. All functions with independent ability to turn on or off without dependancy on other selections (Boost fuel cut, dragtools options, etc)
8. All functions with pull down menus give the ability to enter a value manually as well (perhaps as an advanced option)
9. Preserve ability to manually edit .bin as with the hidden option in EE (perhaps as an advanced option)
10. Preserve "A" / "B" map capability and allow map copying between maps to allow switch on the fly testing (GEN2 style ECU)
11. Logging of injector duty cycle (individually for platforms with 2 sets of injectors)
12. Alternate boost contol strategies
13. Addition of anti-lag controls for turbo applications (Ability to add fuel and remove timing when the clutch is in.)
14. Shift kill strategies, i.e independant ignition/fuel kill duration, ignition timing modification, timing ramping, delays/offset between ignition. fuel, timing, etc.
15. Real-time tuning of fuel and ignition maps while connected to a PC (example: Use COV inputs to modify maps, store on PC, then flash once a "good" map is developed)
16. Internal plotting and manipulation of logged data from a .wrl file in 2d format (variable vs. time)
17. Map interpolation / smoothing features built into the individual tables

 

-- Edited by sportbikeryder on Monday 12th of November 2012 04:52:23 PM

-- Edited by sportbikeryder on Tuesday 27th of November 2012 01:58:52 PM

Request 1.

Looking to be able to adjust the high and low rpm gap when setting a 2 step. When I use rom raider I can Make my 2 step go between 10000-10050 by with Ecu editor I can't control the gap. So I'd like to be able to set each high and low rpm separately for the 2 step.

Request 2.

On the gen 2 Busa, you can lock the IAT temp. I would like that functionality carried over to 07-08 1000.

A useful feature could be a single command to duplicate A to B (all features, settings and maps) and another command  to copy  B to A.

This would allow a sort of backup/restore and immediate  comparision while riding between a new map (loaded in to A)

with the previous map (loaded into B).

This result can currently be achieved manually, but it is a long process and prone to errors.

 

 

 

 

B -king has 2 map modes selectable by the tank switch: A and B.

Hayabusa has A, B, C.

The command should copy all maps (fuel, ignition, stp, injector balance) from one map mode to another map mode.

Example:

> Select source: B

> Select destination: C

> Confirm copy all maps from B to C (Y/N)?

 

 

 

 

How about apply map button for the 1st gen busa's?

Yes, referring to the import map.

I actually went and tried something the other day since I have a Gen1 busa that a PC3 is acting up on.

Had to go threw some small hoops but I converted a PC3 map to a PCV map with the PCV software and then I opened a Gen1 fuel map in EE and copied the entire map.... than opened a Gen 2 map and pasted my Gen1 fuel map to the Gen 2 map... applied PCV map... copied and pasted back to a Gen 1 map lol....

I know this is probably not the best way of cutting a corner but I went threw the RPM's and checked out how much fuel it adjusted and it seemed like it adjusted it sort of accordingly.


Correct me if I'm wrong but the numbers on a fuel map in EE are injector pulse duration? When I adjust fuel in EE if I want to add say 5% fuel to one area I have to add 5% of that particular pulse duration so if the number is 160 in a cell I would have to add 5% of 160 which is 8 numbers so bring it up to 168. Does that make sense or am I WAY off base?

I have not tested to see what the fuel map will do on the busa I was messing with but will be shortly. But I'm sure someone could figure out a way to apply a PCV or PC3 map to a fuel table.... well hopefully lol.

P.S. Thanks for everything you guys do with all of this stuff!!!

Maj750 wrote:

---

How about logging duty cycle of each injector bank ?

---

 Added to the list....I'm not sure that the ecu directly calculates this though, it may only "know" the injector pulsewidth. Certainly could be calculated form injector pulsewidth and RPM though. I'm not sure how the fault codes are generated when injector duty cycle is exceeded, wether it is from actual duty cycle or indirectly from exceeding a certain pulsewidth at various rpm.

Small things..
-if we are using long path for file name then i cannt see it.

sportbikeryder wrote:

---

BUZKA wrote:

---

Small things..
-if we are using long path for file name then i cannt see it.

---

 BUZKA, is this with the WRT software as well? This is more of a bug than a request. Perhaps we should have a bug reporting area somewhere as well.

---

 Yes this is for WRT.Sorry for the mess in this topic.Maybe should be somewhere sticky topic for small bugs

I think a ramp up rate for where the 100% value was.
PID loop for maintaining boost levels.
Ramp down rate for where the overboost 0% value.

Turboy750 wrote:

---

I think a ramp up rate for where the 100% value was.
PID loop for maintaining boost levels.
Ramp down rate for where the overboost 0% value.

---

I have started a new post to discuss different boost control algorithms. This is something that can certainly use some attention, but it is not trivial to get a basic logic flow and determing what I/O to use.

 

http://ecuhacking.activeboard.com/t51456465/alternate-boost-control-strategies/

 

garth285 wrote:

---

Anything new goin on with this?

---

 The 2 step limiter that you noted may be functional. If you have the ability to flash an ECU, I can send you a .bin or you can use Woolich Racing Tuned software and flash with a 2 step limiter on a GEN1by setting the neutral limiter under the limiters selection.

User
arhur39 has noted that the neutral limiter is functional in Woolich Racing Tuned for a GEN1. Certainly wouldn't hurt to have some more confirmation.

If you look at other platforms in WRT, you will see that the user interface is very similar across platforms. This is especially true when looking at a GEN2 ECU and say a 2007 GSXR 1000 as they are very similar ECU's (The neural limiter is active in the GSXR's as well). The intent of WRT will be to be usable on a wide variety of platforms with a very similar user interface.

garth285 wrote:

---

That makes perfect sense! Maybe I can find that line of code for the neutral limiter and add it to my bin im currently using.

Man I wish I could combine things from both ECU editor and Woolich racing.

I love how woolich can still keep individual gear timing maps which will be important to me for the big motor I'm building and keeping power to the ground with pulling a little timing in lower gears.

The things I like about the ECU editor is the quick shifter function, the shift light from the IAC, and the "big block" cranking which I have not tested with this new motor I'm building but I'm sure it would help on larger motors if it does what its supposed to do!

I know I can put together a map using some things here and there, would just be time consuming

---

 Open teh EE map in WRT and change the things you want, then flash.