[help needed] Dual Suzuki GSXR750 K8 driven autocross car

[soberpei]

Hello there,

I am Stefan from Austria.
We are using two Suzuki GSXR750 K8 engines for driving our autocross buggy.

The engine is a 4 cylinder, 4 stroke with hall sensor on crank, camshaft sensor, two fuel injectors per cylinder and one spark plug with a coil for every cylinder. Air mass is not measured, sensors for athmospheric and manifold pressure and intake air temperature are present. Original the engine is equiped with a secondary throttle plate. We removed this one and therefore only the mechanical actuated throttle plate is used (throttle position sensor is available). Max RPM of the engine is about 15000, idle RPM is 1300.

Are there any complaints? Should be possible to use rusEFI?

I read rusEFI can be used with tunerStudio. Whats possible to configure for the CAN bus? Is there a broadcast option?
Are there ideas for traction control ore launch control?
Stefan

[AndreyB]

Hi! Only one engine has _maybe_ exceeded 10K rpm - see http://rusefi.com/forum/viewtopic.php?f=3&t=396&start=90 - so too little information.
CAN functionality is really limited due to shortage of software developers. Why do you need custom EFI and why are you considering rusEFI?

[soberpei]

I am generally interested in engine electronics and I have some ideas concerning autotune algorithms. Standard ECUs (amd racing ECUs too) are not open for such modifications.

I found rusEFI while searching for open source EFI systems. Do you think it is not applicable? Its seems clear to me that thats more than just changing the ECU.

[AndreyB]

rusEfi is definitely a great option for you, I believe that it is more suited for expansion then the three other open source ECUs I am aware of. As long as you understand that rusEfi is not an off-the-shelf ECU ready for prime time you are good

http://rusefi.com/wiki/index.php?title=Manual:Current_Status

[kb1gtt]

Hello and welcome along.

I agree it sounds like your engine has fairly standard hardware, and could very likely use rusEFI. Do you know your crank wheel pattern? There are currently several crank wheel patterns supported and I'm not aware of any patterns that can't be supported. It's a matter of developing the decoder. The rusEFI design allows for these decoders to be made fairly quickly. As well russian has a setup which includes two different boards that's part of the development system. He first sets one board to simulate an engine, then he sets another board to decode the engine. He makes the first board generate set RPM and such parameters, then validates the other board is operating as expected. This allows for reasonably good levels of validated on engine setups he doesn't have. I forget how high of an RPM he has tested with this setup.

Some standard disclaimers, this is a DIY beta kind of project, it has only been run on something like 18 different engines at this point, and real world data is minimal. It's generally not plug and play, and requires a bunch of work on your end. We want to try and make sure you know that using it is a large project, such that you have reasonably expectations. We have seen far more people who have gotten the assembled kits and turn them into running engines, so we suggest the assembled kits. The SMT PCB assembly is very extensive, with some fine pitch components. If you get an assembled PCB, it avoids the complicated SMT assembly. As well the assembled kits come with a certain level of validation, so we know that things like the voltage regulator is creating 5V, fuel injectors are blinking lights, things like that which validate basic functionality of the board.

Again welcome along, and feel free to ask questions.