rusefi.com

Hello,
I'm from Poland I want to try run my engine on rusEFI, but I've got a problem.
I read Soft U Manual - wiki - I loaded firmware to my STM, but while I try connect to TS I'll receive error:
"pe4 req by spa2 used by fuel pump relay"
I didn't make any changes in configuration, just try to connect after STM programming.

What I do wrong?

You are not doing anything wrong - it's my fault, yesterday I've broken default pin configuration. I'm sorry your experience with rusEfi starts like that.

Thank you for reporting the issue, just fixed it. In this case you would need to reset the configuration in flash - please use 'erase chip' option in ST Link Utility - and then program new version.

I know that beginnings sometimes are hard
Thank for fix, I'll try again later.

I erased the chip and program again with new firmware.
Currently when I try to connect using TunerStudio I've got an error: Should I configure input and output first, then burn config and connect again?

That's good progress Looks like the bug is gone, good!

Now you are just connecting with TunerStudio to 'dev console' port. You need a jumper to switch from default mode as described at http://rusefi.com/wiki/index.php?title=Manual:Software:User/en#Communication_mode

Please also read http://rusefi.com/forum/viewtopic.php?f=5&t=210

Yes,I read it yesterday, but today I forgot about it.
Anyway, I made connection and it works. Thank you.

To be continued, maybe tomorrow. Stay tuned

Anybody can tell me what configuration should I use with EDIS?
OE connection is like that: Currently I don't want to modify my wiring, so I want to use EDIS.
Signals on EDIS are like that: PIP signal is 50% duty square wave. There are three signals per revolution.
ECU generates SAW signal which is used by EDIS to advance ignition.

I want to use it on V6 engine with firing order 1-4-2-5-3-6. Engine has no camshaft position sensor. Fuel injection is semi sequential, two banks - first: cylinders 123, other: cylinders 456.

Is it possible to run this engine on RusEFI?

V6 is supported - you need to specify six cylinders in TS
36-1 trigger is supported - you need to specify trigger type 36/1
batch injection also supported

1-4-2-5-3-6 was not supported 30 minutes ago but I've just added 1-4-2-5-3-6 support so if you update to latest version you would be able to select 1-4-2-5-3-6 firing order in TS

We did not yet start any EDIS engines but I am sure that this would not be a problem. Once you have the hardware side ready we will take care of what could be missing if any. Supporting people with real hardware is my top priority

EDIS 6 cyl would be cool. Let us know if you need any help.

as far as I remember, EDIS is a bit different configuration than what we have used to in ruesefi.
namely, it is EDIS which does VRS decoding (see diagram) and which actually controls ignition. then, it provides decoded signal to another unit which controls fuel injection. (not sure what are the voltage levels there in the interconnect bus).
so I think this would require a different config from rusefi, with a different decoding algorithm and without ignition subsystem. or, which seems more convenient and straightforward, i'd better leave just edis coilpacks.

Yes, as I know rusefi can control coil directly. EEC-IV doesn't control coil directly, but is uses EDIS. EDIS sends PIP signal (12V) to ECU which is information about engine speed. ECU replies for PIP signal and sends SAW signal to EDIS (5V). SAW Pulsewidth control timing advance.

AW Pulsewidth (usec) = 1536 - (25.6 x (desired spark advance in degrees))
Range: 64 - 1792us (57.5° BTDC to 10° ATDC)
Resolution: 4us (5/32nd of a degree)

Example:

You want 29 degrees of advance.

PW = 1536 - (25.6 * 29)

PW = 1536 - (742.4)

PW = 793.6

Without SAW signal timing is 10 degrees BTDC.

EDIT:

russian wrote:V6 is supported - you need to specify six cylinders in TS
36-1 trigger is supported - you need to specify trigger type 36/1
batch injection also supported

1-4-2-5-3-6 was not supported 30 minutes ago but I've just added 1-4-2-5-3-6 support so if you update to latest version you would be able to select 1-4-2-5-3-6 firing order in TS

We did not yet start any EDIS engines but I am sure that this would not be a problem. Once you have the hardware side ready we will take care of what could be missing if any. Supporting people with real hardware is my top priority

Thank you for support 1-4-2-5-3-6.

If you want to make something to support EDIS by RusEFI, you can use simple square wave generator witch 50% duty cycle.
5Hz signal is like 100RPM
50Hz - 1000RPM
315Hz - 6300RPM - rev limit for my engine
^^ it's for 6 cylinder. For 4 cylinders frequency should be multiply by 2/3 - (~3,33Hz - 100 RPM, 33,3Hz - 1000RPM, 210Hz - 6300RPM etc.)
For one PIP signal RusEFI should generate SAW signal, which pulsewidth depends on timing advance. EDIS also generate IDM signal for ECU, which is use for diagnose, so now, we can skip it.

I think that support EDIS is good idea, because RusEFI could be used without wiring modification - EDIS is in engine bay, ECU is under dashboard.

I'm expecting the EDIS to be removed mostly. The coil ignitors can be used, and fuel injectors would go direct to rusEFI. I guess I'm ignorant about if those coil packs have internal ignitors. Do we have a schematic for what is inside the coil pack? It may require a high current and high stand off voltage. We need to verify that we are driving an external ignitor not driving the coil primary directly.

voitec wrote:I think that support EDIS is good idea

I agree. Once there is a person to try we will figure it out

russian wrote:

voitec wrote:I think that support EDIS is good idea

I agree. Once there is a person to try we will figure it out

Like it! Do you want any other information about EDIS?

voitec wrote:Like it! Do you want any other information about EDIS?

EDIS was discussed before - for example in http://rusefi.com/forum/viewtopic.php?f=3&t=469 - so I have enough info to know that we can handle it. Until that's really needed that's probably enough info.