Engine Management

Back again...

After a bit of time away seeking enlightenment (and a steady paycheck), I am ready to get back to work on my project. I have continued to play around with the code and a number of components. First, I wanted to have a more interesting development workstation, so I thought it would be fun to use a Raspberry Pi. After installing the latest version of Raspbian and getting all the updates, I loaded the AVR tool set, then Eclipse and the C/C++ components. Then adding the AVR plugin and whoopee I had a workstation.

I also really wanted to use the Nano for a platform but had problems with adding controls for 8 cylinder coil on plug and still be able to have outputs for solenoids and idiot lights (shift, MIL, etc). Then I thought of using 4 of the port lines to control a 74LS138 and using a bunch of 74LS75s and some inverters, route the other 4 port lines available to create a multiplexed switch network. Got it to light LEDs and the scope signals look right too.  The last part of the puzzle for the Nano was since the 328p is limited for timers, I got inventive for some of the timing pieces (fueling is less time critical).

So I created a dual path, with the majority of software files being shared between both platforms, only when hardware forces there to be a difference, the same code runs on both Mega2560 and Nano.  I will attempt to provide all the how-to for the development workstation, the Nano setup and programming, and source code with design theory.

Since much stuff has been refined over the course of time, I will probably be redoing a bunch of stuff and there will probably be a bunch of  repeat.  For anyone interested, it is possible to get a big dose of what is to follow by looking over the early work at Engine Management project

I am now in the throws of developing the UI to provide the calibration in a more comfortable way. Again, trying to stay with using a Raspberry Pi as the UI platform too.

Jack

Hi Jack,

Interesting project for a single software developer. When I worked at Chrysler in the engine controls group they needed over 30 people to code, calibrate and develop hardware for the SBEC controller.

Good luck,

Scott

Hi Scott,

Were you on the second floor over the Dyno Cells?

Jack

Hi Jack,

I started downtown, then moved to Auburn Hills 3rd floor engine and chassis controls for large car platform.  The coolest toy they had was the engine simulator cube.

Scott

Nice, so you knew Fred, Ron, Dale, and Bob, or were you after that (probably yes if you came from HP).

Jack

ps. Trying to keep names and details obscure to protect the innocent.

I'm trying to think of who Fred is...…...I worked for Kissel, then Cwiek.

I remember watching them build the first Dodge Viper in the plastics shop on a dune buggy frame in HP.

Scott

Hi Scott,

Came over from AMC/Jeep (Plymouth Rd). Fred was Meisterfeld. and Dale Koch. Was part of Neon Launch (dare to be different). Then went over to IT to work on DRBIII.

Jack

Hi again,

Back to your first statement, about volume of work for a single programmer.  I guess it might be... but I am an old, retired, programmer. This is a good exercise to see if it really can be done.

My problem is, I do need help with the hardware stuff (circuit design and layout). My stuff is all using breadboard, LEDs, and some Rube Goldberg mechanical devices.  I think I have the software working, but would really appreciate some partnership assistance from time to time

Jack

Hardware is usually vehicle specific, what is your target platform?

Funny you should say that. The truth is the hardware is pretty much portable. The difference for system timing comes down to the cam and crank wheels and the signals they produce. I have software that does the cam decoding for simple pulse or half moon, Mopar 4/6/or 8 cylinder, and GM VVT. The crank signal is based on the call out for how many teeth, and if there are filled or missing teeth. The other parameters are for injector size and the variety of sensors. I had similar code operating a GM LS, a MOPAR SRT, and a Ford Cobra (with multi-strike CD), The input signals might need some conditioning for hall effect, I will need to see about that. My focus is primarily on the coding side of the process.

The primary target for the controller project is actually Porsche and VW 4 cyl, and Corvair 6 cyl. But I have built the code and my breadboard to run up to 8 cylinder COP, with direct sequential injection.

Jack

Funny you should say that. The truth is the hardware is pretty much portable. The difference for system timing comes down to the cam and crank wheels and the signals they produce. I have software that does the cam decoding for simple pulse or half moon, Mopar 4/6/or 8 cylinder, and GM VVT. The crank signal is based on the call out for how many teeth, and if there are filled or missing teeth. The other parameters are for injector size and the variety of sensors. I had similar code operating a GM LS, a MOPAR SRT, and a Ford Cobra (with multi-strike CD), The input signals might need some conditioning for hall effect, I will need to see about that. My focus is primarily on the coding side of the process.

The primary target for the controller project is actually Porsche and VW 4 cyl, and Corvair 6 cyl. But I have built the code and my breadboard to run up to 8 cylinder COP, with direct sequential injection.

Jack