rusEFI OpenGDI ECU

Hardware inside and outside of the ECU
Post Reply
User avatar
AndreyB
Site Admin
Posts: 10851
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City

rusEFI OpenGDI ECU

Post by AndreyB »

tbd
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239

User avatar
AndreyB
Site Admin
Posts: 10851
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City

Re: rusEFI OpenGDI ECU

Post by AndreyB »

tbd
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239

User avatar
AndreyB
Site Admin
Posts: 10851
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City

Re: rusEFI OpenGDI ECU

Post by AndreyB »

We need a smarter GDI board - one which would have it's own MCU and a case. Considering low cost of HW and huge cost of hardware maintenance I suggest we make a board which could be both a self-contained ECU and a GDI extension board for microRusEFI or even non-rusEFI ECUs.

Shall we combine
https://github.com/mck1117/proteus for general io
https://github.com/rusefi/rusefi/tree/master/hardware/Common_Rail_MC33816 GDI
https://github.com/rusefi/rusefi/tree/master/hardware/Breakout_154pin_284617-1-Connector 154 pin connector
https://github.com/rusefi/rusefi/tree/master/hardware/brain_board_176-pin 176 package and prototyping are for general spirit of Frankenso?

OpenGDI=Proteus+154+176stm32+GDI

Since there are rumors of Proteus154 maybe probably this should wait for Proteus154 to happen?
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239

mck1117
running engine in first post
running engine in first post
Posts: 620
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: rusEFI OpenGDI ECU

Post by mck1117 »

AndreyB wrote:
Wed Oct 21, 2020 11:04 pm
self-contained ECU and a GDI extension board for microRusEFI or even non-rusEFI ECUs.
"self contained ECU"

Why does it need to be a self contained ECU? The easiest path forward, by far, is to bolt an MCU, power supply, and CAN tranciever on to the existing PT200x board.

It would even fit inside the MRE case.

User avatar
AndreyB
Site Admin
Posts: 10851
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City

Re: rusEFI OpenGDI ECU

Post by AndreyB »

mck1117 wrote:
Wed Oct 21, 2020 11:08 pm
The easiest path forward, by far, is to bolt an MCU, power supply, and CAN tranciever on to the existing PT200x board.

It would even fit inside the MRE case.
Because feature creep?

Very tempting to develop this as a board useable with non-rusEFI standalone ECUs which would probably mean HPFP control including analog inputs. Once we have MCU, power supply, and CAN transceiver and analog inputs and protected digital inputs we are getting soooo close to complete ECU that it's very tempting to make that extra effort.
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239

mck1117
running engine in first post
running engine in first post
Posts: 620
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: rusEFI OpenGDI ECU

Post by mck1117 »

AndreyB wrote:
Wed Oct 21, 2020 11:34 pm
mck1117 wrote:
Wed Oct 21, 2020 11:08 pm
The easiest path forward, by far, is to bolt an MCU, power supply, and CAN tranciever on to the existing PT200x board.

It would even fit inside the MRE case.
Because feature creep?

Very tempting to develop this as a board useable with non-rusEFI standalone ECUs which would probably mean HPFP control including analog inputs. Once we have MCU, power supply, and CAN transceiver and analog inputs and protected digital inputs we are getting soooo close to complete ECU that it's very tempting to make that extra effort.
Another option is to double-decker a GDI add-on board on top of BigProteus when that exists. There will be pleeeeenty of connector pins to dedicate some that only get used if you add the GDI board.

User avatar
kb1gtt
contributor
contributor
Posts: 3684
Joined: Tue Sep 10, 2013 1:42 am
Location: ME of USA

Re: rusEFI OpenGDI ECU

Post by kb1gtt »

Is @AndreyB suggesting a board which accepts low side pulses and generates pulses for GDI injectors? Done up as a stand alone box. Similar to the high Z to Low Z injector modules that can be obtained for people who desire low Z but have high Z ECU.
Welcome to the friendlier side of internet crazy :)

User avatar
AndreyB
Site Admin
Posts: 10851
Joined: Wed Aug 28, 2013 1:28 am
Location: Jersey City

Re: rusEFI OpenGDI ECU

Post by AndreyB »

kb1gtt wrote:
Sun Oct 25, 2020 9:52 am
Is @AndreyB suggesting a board which accepts low side pulses and generates pulses for GDI injectors?
Yes and no. I am interested in the same board also doing HPFP which means analog inputs. Once we have analog inputs this really starts to look like a complete ECU to me - maybe a dual-purpose standalone/pibbyback ECU.
https://rusefi.com/s/howtocontribute
very limited telepathic abilities - please post logs & tunes where appropriate - http://rusefi.com/s/questions
my skype is arro239

mck1117
running engine in first post
running engine in first post
Posts: 620
Joined: Mon Jan 30, 2017 2:05 am
Location: Seattle-ish

Re: rusEFI OpenGDI ECU

Post by mck1117 »

AndreyB wrote:
Sun Oct 25, 2020 1:31 pm
kb1gtt wrote:
Sun Oct 25, 2020 9:52 am
Is @AndreyB suggesting a board which accepts low side pulses and generates pulses for GDI injectors?
Yes and no. I am interested in the same board also doing HPFP which means analog inputs. Once we have analog inputs this really starts to look like a complete ECU to me - maybe a dual-purpose standalone/pibbyback ECU.
The same board could do HPFP hardware control (just like injectors), but not HPFP algorithm control. The HPFP controller needs crank/cam/vvt position info, since the HPFP is usually installed on the far end (ie, back) of one of the cams. No reason the main ECU couldn't do that logic and just tell the GDI controller when to turn on/off the valve solenoid.

Post Reply