rusefi.com

Hey guys. Just heard about your project when OSHPark tweeted about it today. Looks excellent. Very good choice of Microcontroller, I'd have picked that one too. I've got extensive experience with homebrew fuel injection, having used MegaSquirt in the past. I've become a bit disillusioned with MS's greedy licensing, so I've been looking for alternatives. I've installed MS efi in probably 10 different vehicles, so I have a lot of experience on the install and initial tuning side of things. I've also got some electronics experience, having designed a few PCB's for work and my own projects.
I have an STM32F4 discovery board already, it looks like you've designed your ECU to connect right up to it, so I guess my first step is to order up a PCB and get tinkering with it. Maybe start with loading the firmware onto the board and interfacing with the computer?

Welcome on board, we can surely use your experience! Any chance you would be interested to invest time & play with all this? We are definitely looking for people with time & passion for all this.

Yes Frankenstein http://rusefi.com/forum/viewtopic.php?f=4&t=359 is designed as an stm32f4discovery shield. I am expecting to try our own chip board hopefully later this week, but Frankenstein would stay as a more DIY-friendly option anyway. Jared @ did a great job putting the essential info on the www.rusefi.com wiki and feel free to ask any questions

Wellcome along and by all means feel free to ask questions. If you plan a project let us know we would likely be happy to help and get involved.

Cool, I setup an account on the Wiki, was going to add a source for automotive grade wire that I've had bookmarked for years. Can I get write permission on the Wiki?
Definitely planning to play around with this thing. What kind of trigger inputs does it support? 36-1 wheels? The Neon engine that's running on this - is it using the Neon crank trigger? I have a PT Cruiser that uses that same crank trigger, I''d be happy to mess around with running that on this.
Awesome that you have this working with TunerStudio, as I already have a registered copy of it. I assume this means MegaLogViewer works with it too?

Just granted Write permission to the wiki.

Currently it supports any skipped tooth configuration (X/Y, say 36/1 or 24/2 or 60/2), neon, aspire and miata. You can see how decoders are defined in trigger_* source code files if you are curious or I can just add any configuration you would need. See http://rusefi.com/wiki/index.php?title=Manual:Engine_Type

TunerStudio free edition would work too, but a license does not hurt. As for MLV, we kind of have logging support but I am not sure if it's already compatible with MLV or not.

I think that so long as TunerStudio wrote the log file, MLV can read it.
Is the schematic for Frankenstein posted somewhere? I found the gerbers, but haven't seen the board and schematic files. But I haven't checked the google code repo, maybe it's there?
Thanks.

Check the links @ http://rusefi.com/forum/viewtopic.php?f=4&t=359 - the ones under the video.

daecu google svn has some stuff, but it usually ends up @ https://svn.code.sf.net/p/rusefi/code/trunk/ (see hardware/) which is the central point currently.

If you have a crank wheel that is not currently supported you can sniff it with a logic analyzer (LA) and then Russian can make a decoder. I seen to recall we have sniffing capabilities but a LA is cheap and offers extra resolution. LA's often capture at around 5nS while our sniffer is around 5uS. Both are good enough but a LA offer's more resolution which doesn't hurt. Some day we will probably get around to making this sniffer faster but for now it works for most applications. So we'll concentrate on developing other features.