gemellocattivo.com

Well done!

So you have the crank/cam simulator pins jumpered to the the crank/cam input pins or have some other crank/cam simulated input? You won't get fuel or spark without a good rpm sync.

Then, and I'm reach back into the memory vault there are a couple other things that can disable fuel. For 1 there is a fuel enable setting, make sure that is a 1. then there is a rev limiter fuel cut.....make sure the rev limiter is disabled or the rpm set very high.

We never actually ran an engine. mine wasn't ready and the people with engine didn't have the skills, the people with the skills didn't have engines....so it waited....then I discovered enginelab and moved on, its everything I ever hoped o5e could be . That said everything in o5e has been bench tested and should work....I think the logic I created for my enginelab setup is better than what what I did for o5e, but it should work.

Another place you might be interested in looking is rusEFI, they have many engines running and quite a few features working....there is a question in my mind about the accuracy and robustness of the fuel/spark outputs but they have many engines running so I might be paranoid.

hmmmm google code went away and we moved to github

did you get the code from here:
https://github.com/o5e

I think that is the latest but I could check on my usb drive to see what I have

Fuel pump also has an enable...I suspect you haven't found those 2 yet

ok.

The eTPU pins on the 5634 board behave like any i/o channel....they ground when active

Do you have numbers in all the fuel tables? So should there be a fuel output is the new question? Did you load the TS example file where I set everything up to work with numbers in all the tables?

also are you in run or test mode?

very strange then.

And spark is working?

fuel and spark are basically the same so that's what surprises me....and it shouldn't be on like that, I know there is a setting to invert the spark output and thing there is also one for fuel...I know its down in the eTPU code but don't recall is we put a switch in TS but with the fuel pump acting odd as well I'm confused a bit.

For sure you don't need a pullup...which has me questioning what I told you...."ON" could be 5V, I just don't remember.

Are the fake cam and crank signals working? We always used those for all the basic testing by jumping them to the inputs....I would try that and set TS for a 36-1. I did also do testing with a real crank wheel, also a 36-1.....what crank/cam signal are you feeding it?

the eTPU can be programmed to read any crank/cam signal...if you have an eTPU compiler which is like $5k. The free code that we used does missing tooth(s) at a single location so 36-1 or 60-2, stuff like that.....but I think there is a newer version that will do multiple missing locations but that was after we stopped so I don't know it well.

The MPC5xxx family can do push-pull or open drain on all output pads. Unless you specifically configured open drain, they should be push-pull (driven high and driven low). You would of course need to set the SIU.PCRx.OBE bit to enable the output at all.

"On" is either 5v or 3.3v depending on the voltage fed to the pad bank. The chip runs internally at 1.25v, so there are different voltage sources for the IO buffers and you can configure them. I believe the TRK-MPC5634M has all of the IO banks at 5v.

_________________
"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack

"Any sufficiently advanced technology is indistinguishable from magic" ~Arthur C. Clarke

remembering back...5V is on I think so you have no fuel ouputs. The pump is completely separate code, so if both the pump and injectors are off its likely a common setting....like fuel enable, that's the only one I recall and would need to dig a bit beyond that. I'm happy to spent some time this evening.

Sound like I let a bug into the fuel code then, sorry. I'm sure its minor as it was all working. I also just use a blinking led to tell me I have a legitimate value at each step......its got to be something with enable as that is the only thing I believe links the fuel pump and injectors and I think is the last item and controls the output.

There is no drive by wire. I do have that working well in my enginelab project, you could take that and translate it to C pretty easily....its got start position, pedal-throttle translation table, idle control, stall saver, traction control but only that basics are tested as my engine had some issues I'm now correcting. Rusefi has dbw codes too, but fewer features I think.

With the brink you can step through the code logic and find where it goes wrong.....a debugging tool is much faster but I don't know how to use that.

Enginelab.net uses a pretty simple function library to let the use create control logic without any need to know anything about low level C code stuff. I just love it.

You can download the software, which has a simulator so you can "test" everything on the pc without touching hw....pretty nice. My model (program), which run an engine, is here

http://gemellocattivo.com/forum/viewtopic.php?f=19&t=153

To me, it was worth every penny, no compiling, see/log every internal calculation for bug hunting, just nice.

This it the AEM infinity series ecu....they license from enginelab and I suspect it's that arrangement that means only the highest end, infinity 7, is available directly from enginelab. Its basically a motec M150 at a fraction the price.

Way back we had talked about something a bit similar for o5e....but never acted on it. Everyrhing a library function you call. We tried to keep the code a user would mess with simple and that would have been a next step...but we never got there.

There was another option, an adaptronic 1280 but I thing they dropped it. It used an interface like labview, but didn't quite have everything I needed so ibreplaced my M150 with enginelab once I fully realized the $4k I paid for the motec was just a deposit and I'd be out at least 10k, probably 15 before it did everything I wanted....engine lab does it all for 2k so a bargin to me.

Anyway, all my latest control logic is written in enginelab, i wrote a user manual to explain everything and you're welcome to use anything that helps.