How is it coming Kevin?


 Paul Lamar
 --

 Hi Paul...There must be another Kevin working on the EFI, since I
 know nothing about them.

 I do, however, see that the check I sent you to help w/ the turbo
 compound costs hasn't cleared my credit union. Did you receive it?

 Kevin Richey
 Portland, Oregon

 That was Kevin Alderman.

 Yes. Just cached it this morning Kevin. Been in Vashon the last few
 days.
 Thanks very much. It is a big help.


 Fortunately I just found some BIG 5 dia. inch 90 degree bends I was
 sweating on Ebay :)
 That is one big exhaust pipe. Even for a truck.  It is for the exhaust
 out of the turbine.
 Low exhaust back pressure is real important.

 Boesch Built


 Paul Lamar




 Kevin,
 I am new to the group but been interested in rotary engines for a long
 time, just have not done anything about it yet. I live out in Estacada
 and would love to talk to you, since I am in your area, and learn what I
 can. I am getting ready to start building a Bearhawk Patrol.
 Thanks
 Doug




OK, first the EFI:

Many of you know I have been talking with a race car builder/ computer
programmer that decided to write his own EFI. After many conversations
and emails with him (Fred) I have what I need to complete the system (I
think. The adage "you don't know what you don't know bites me
regularly). The main board is, currently, the Technological Arts board
with XGate. XGate is important because it takes many of the basic
interrupt driven calculations off of the main processor. Such as reading
the input from a sensor and converting that to a useable digital input
for the main program. I have almost completed the hardware portion, and
have written a couple of header files to define parameters specific to
the rotary. The only really important thing I have to do to the program
now is to add an input for the pot for manual mixture control.

I think if I can isolate the XGate part and re-introduce this section
back into the main code or at least a header file, I can get the system
to run on an Arduino Mega. Plenty of speed, plenty of IO and ADC ports.

While I am building and coding, the interior goodies in both planes are
going to be controlled by an Arduino Mega- LED lights, strobes, climate
control, etc. That is fodder for another thread though :)

http://technologicalarts.ca/shop/


Second, Doug feel free to call, email or drop by. I am building 2
Wheeler Express planes. One is at my house in Tavernier just below Key
Largo, and the other is at the Homestead General Aviation airport- X51.
The one at my house is being built with a Mazda 13b P port that will be
an EFI turbo intercooled plane. The other I bought partially built with
a Lyc IO360. I went from building one plane to building 2 at one time.
Unfortunately I like the challenge.


Kevin Alderman

==============================================================
The MC9S12XDP512 introduces the XGATE processor into the S12 line. XGATE is a Reduced Instruction Set Computer (RISC) processor that is designed specifically to handle certain types of Input/Output (I/O) requirements that an application might have.  It is not just another CPU made for running programs.

Most user applications can use the standard S12X CPU by itself to handle their I/O needs.  It is for that reason that many development environments concentrate on the S12X, without providing XGATE support. The only time one has to start thinking about the XGATE processor is if there is a need for it.

For example, if an application has a requirement to handle an interrupt source that occurs very often, then this could be a situation that requires the use of the XGATE processor.  Otherwise the S12X processor ends up using most of its processing power handling just this one interrupt.  Of course, if using XGATE still isn't fast enough, one may end up having to resort to a hardware solution, such as GAL, FPGA, or ASIC circuitry.  XGATE bridges that gap.

So if you have the need for speed with one or two I/O types, then XGATE is for you.  Don't use XGATE for a lot of different I/O requirements though.  It's not designed with that in mind.  The reason for this is because of the way it works.  Most of the time the XGATE processor actually just sits there doing nothing.  It only starts running when an interrupt destined for it gets triggered.  At that point, XGATE will begin execution of the routine to process that interrupt.