Engine Management

I found out how to attach a zip file... I had to go over to the advanced editor

So here is the zip with the source so far.

I don't know if it has been said but there is an open source project called speeduino. Its been running engines for a while now, actually my daily runs on it. It started on the ATMEGA 2560 but its been ported to the teensy 3.6? ARM32. You could use the well developed hardware for testing purposes with your code.

I don't know if it has been said but there is an open source project called speeduino. Its been running engines for a while now, actually my daily runs on it. It started on the ATMEGA 2560 but its been ported to the teensy 3.6? ARM32. You could use the well developed hardware for testing purposes with your code.

Hi,

No I had not seen that (yet), if you could post the link here, I can chase things down and see if it will give me some help with the hardware aspects of this project. My source is primarily for 328, but I also have a version that runs on 2560 that uses all shared code with the exception of 4 files.

Thank you for the shout out,

Jack

www.speeduino.com that's the homepage. Glad to be of help

Thanks a lot for the link. I looked over the site and kind of gleaned much of the information. The information provided shows they are using the Arduino interface, which might explain the reason for upgrading to the ARM processor version. The Arduino interface takes time away from the operation. I also see they are working on some CAM and Crank problems that I have already resolved and will present here. The fun thing to see is how they have a developed UI stage for updating calibration information. This is where a one man show, can be a little slow. I know what needs to be done, and I have a mental image of the interface and the code to make it work, but I just haven't done the deep dive into writing the code.

My aim is to use off the shelf open source tools, so everything is repeatable by other members. So, I have started building a simplified UI using GCC and have been flip flopping between GTK+ or QT, but I am leaning to GTK because of some licensing questions I have about QT. We shall see.

Thanks again for the link,

Jack

Not a software person myself pretty much at beginner level. The mega is the primary platform for the project and some new additions had to be made to the Arduino software side to speed up things. The injection and ignition channels are limited by the number of timers; (9) I think? The crank and cam triggers are kind of modular ;missing tooth on crank or cam is functioning properly and other patterns have been added. You may get in touch with Josh the developer if you need more info.  A more closer to the hardware approach like yours would probably utilize the available resources more efficiently. When its ready I would love to be a tester

Hi,

Timers can be a little obscure if you don't work with them all the time. There are actually 6 timers on the 2560 numbered  0 through 5. Timers 0 and 2 are 8 bit timers and have 8 bit compare registers. Timers 1, 3, 4 and 5 are 16 bit timers, and have 16 bit compare registers. 3, 4, and 5 also each have 3 compare registers, so that might be where the idea of 9 timers comes in.

I invite you to read the description of how the source works for my project further down, and I am happy to answer questions about technique.  I think I am up to programming methods for doing formulas that are fast and accurate. I already covered linear and planar interpolation. I also covered use of binary radians to provide simplification of the equations. Stuff coming up is when to perform the calculations, what information is necessary, and how to generalize operations so they can become reused processes.

Look forward to hearing more from you,

Jack