Page 1 of 1
Open source ECU :)
Posted: Thu Feb 10, 2005 7:20 am
by Sabre
Go figure the name would be
OpenECU!!!! Check it out though, seems to be very preliminary. Everyone know's that we're all about the hacking, but when it's on what gets me to work.... I don't know how I feel. The problem that I really see is if they are trying to use a off the shelf computer, how they are going to keep up with the timing required. If you move to some specialty boards, you can get the resolution that you need, but that's the same price as buying a UTEC then!
I'm still thinking of doing an interface for the Hydra for monitoring

Posted: Thu Feb 10, 2005 8:31 am
by ElZorro
I don't think a standard pc would have any problems. The biggest issue is the sampling rate, for analog signals you use a sound card which is capable of > 20khz (audio, plus nyquist for those of us that remember it). For digital signals you use a couple serial ports or the parallel port, couldn't imagine we're talking more than 4Mbps of throughput.
Re: Open source ECU :)
Posted: Fri Feb 11, 2005 2:33 pm
by AJ711
Sabre wrote:Go figure the name would be
OpenECU!!!! Check it out though, seems to be very preliminary...
And once again, the MY98 is left out to dry. Dag-gone DOHC, MAF based ECU with small production numbers.
Thankfully, the Hydra presented itself as a perfect standalone ECU. I'm impressed by what it can do just with minimal add-ons, and I've read that the self tune feature brought a test car to within 5HP of a professional dyno session. All from just driving around town for a while.
Now, if I could only figure out how to use a standalone unit and still have OBD-II capabilities to pass the stupid testing and crap. Then I'll be rich... I mean, set.
AJ
Re: Open source ECU :)
Posted: Fri Feb 11, 2005 3:22 pm
by Sabre
AJ711 wrote:Sabre wrote:Go figure the name would be
OpenECU!!!! Check it out though, seems to be very preliminary...
Now, if I could only figure out how to use a standalone unit and still have OBD-II capabilities to pass the stupid testing and crap. Then I'll be rich... I mean, set.
AJ
Hey AJ,
The Hydra is a great peice of magic
I know what you mean about ODB-II connections... we need to talk... and decifer the ODB-II communications proticol.
Re: Open source ECU :)
Posted: Fri Feb 11, 2005 4:08 pm
by AJ711
Sabre wrote:
Hey AJ,
The Hydra is a great peice of magic
I know what you mean about ODB-II connections... we need to talk... and decifer the ODB-II communications proticol.
Yes it is.
And yes we do. I'm no code/computing genius, but I can solder and navigate via wire diagrams with the best of them.
AJ
Posted: Sun Feb 13, 2005 10:43 am
by ElZorro
IANAL, but that may start getting strange. ODBII is a standard required by federal law, to provide "false" output could be a no-no.
But, that being said, it shouldn't be hard.

Posted: Sun Feb 13, 2005 5:57 pm
by AJ711
All I want to do is be able to run a stand-alone ECU to properly tune my engine, but at the same time, have them plug in their stuipd OBD-II tool come inspection time and be happy. Is that too much to ask?
Oh yeah, and lean out my mixture at idle so I pass those emissions. Or better yet, have a separate map that is called "Fool the emissions people" that passes at idle and whatever other RPM they test at.
Now, to just get a smog reader.
AJ
Posted: Mon Feb 14, 2005 10:25 pm
by zaxrex
If you overcome your OBD II issues but still need to pass the sniffer test, I have had good results with running 3/4 - 1/4 volume mixture of regular unledded and methanol.
Of course water injection puts a lot of water vapor in the exhaust which takes some of the no_no gasses and puts them into suspension so the sniffer can't sniff them.
Posted: Tue Feb 15, 2005 6:58 am
by ElZorro
And the sniffer test, for an AWD, is standing still with engine revs at like idle and 2.5K?
Posted: Thu Feb 17, 2005 5:11 pm
by AJ711
What are they looking for on the OBD-II test as well? Error codes? That the ECU is actually hooked up and running (aka engine parameters)?
If it is just error codes, all you need to do is create some little module that will spit back "No Errors" or whatever to their reader, badda bing, done. Then, just mount your ECU where the stock one once was. If they peel the carpet back and ask if that is your engine control unit, you can't lie, "Yup, sure is."
Remove the sticker, heck, even rip the stock ECU apart and put the exterior sheet metal over it to make it appear stock. The only people who would probably know the difference would be a dealership, and if you're dumb enough to go there for the test with all that stuff on there, well... :slaps forehead:
Otherwise, the rest is tuning and trial and error.
"What, I didn't pass? Okay."
<drive out, find parking lot, change parameters, drive back.>
"Try it now."
<test>
"I passed? Cool, where's my sticker?"

<wierd look from techs>
Posted: Fri Feb 18, 2005 9:12 am
by ElZorro
I agree, it wouldn't be hard.

The OBDII interface is a little strange, lots of pins, but it's a published standard.