EFI332 Software Development / News: Recent posts

Its been two years in development, and a pretty stable and robust code base has emerged. While there are some differences between the archive tips and what I am running now, its close. I used to think that attaining OEM driveability was a dream with a diy system but I've been proven wrong by the performance of this system.
Software development activities now focus on a port to the MPC555 which will host my next generation ECU. I'm back down to a developer team of one so initial versions of that port won't be complete until sometime in the first half of '03. Until then, things will be pretty quiet here so email me directly if you have questions or need help with downloads.

Note that there are two versions of the v1.7 release - one for Labview 5.1, the other for v5.0. The 5.0 version has _50 appended to the filename prefix. In either case try7.vi is the executive that you want to run. Also included in both releases is a .log file that you can play back via the File I/O pane.

With change traffic slowing, I have placed two software packages out for release. One contains the embedded software, listings, map files, and S-record file for the 68332 processor. The other contains the Labview VI suite for the console display application.

After about a year of my own efi332 development and about six more months of completing the mechanical restoration of my target vehicle, I'm happy, no ecstatic, to report the successful firing of the engine under control of the efi332 board. With the help of Bruce Bowling and Bill Wrobel, we successfully fired the engine and ran it for a total of about 15 minutes today. We were able to observe data in real-time using the LabView interface and make tuning adjustments while the engine was running. In between runs, we played back the data through the same interface to fully digest what happened during the run.
Despite alot of personal effort, I would not be in the position of reporting this without the hard work and generosity of Bruce Bowling and Al Grippo. Thanks for a great design guys.
jc

Using a derivative of the baseline CVS archives, developer Peter Siebold has successfully fired and run an aircraft engine using spark control only. The code is a modified version hosted on a 555 processor which has very similar architecture to the 68332. For more details see the list archives.

I've uploaded a web page that I did about a month ago but for various reasons have been holding back publishing it. It still needs fleshing out but its a start. Contributions most welcome !

I've created a new mailing list for developers and onlookers to use to communicate with. This should make it a little easier to use than the forums.

A CVS repository containing the TPU microcode used in the baseline version has been created. This code is a modification of the code on the diy-efi/efi332 site to remove the PSP35 angle - angle function and condense the remaining code down to make enough room for the minimum functions needed. Credit goes to Ian Murphy for this modification.

Welcome Tony Williamitis and Steve Oxley !

The CVS repository now has an initial code revision. This version is aimed at a V8 - 4 TPU channels for waste fire spark, 4 channels for bank fired injectors. Its functional but there is lots of work to do, see the task list - serious efi332 developers wanted !