Subject: this may be what we are looking for
From: Rotary Engine
Date: 11/17/2009, 9:16 AM
To: AAA Put this in the To box



http://www.sae.org/mags/AEI/6906

  http://www.freescale.com/support

  C. Smith

  I'll second that. In the true spirit of the 555 one computer per
  injector.
  If we can get this to work it will be off the shelf ignition and
EFI  at very low cost indeed.  Modular and redundant for safety.

  For a two rotor, four FreeScale demo PC boards would be required
  aseach one has an injector driver. Two triggers are no problem
  for usas each rotor fires once per rev. Just like a one cylinder
  two cyclepiston engine.

  Hopefully there is a one cylinder 2 cycle piston engine FreeScale
  software example that we can use to get a fast start.

  I downloaded a bunch of stuff and got this version of the code
  warrier up and running. Do we have any C programmers on here?

  FreeScale makes you jump through a lot of hoops as far as
  registering and activation which is a real pain in the ass. I
called  them and tried to explain I don't run windows on the
Internet for  virus reasons so on-line activation does not work for me.

  Thanks Craig for letting me know about this.

  -----------------------------------------------------------------------
----------------

  OK I found the section in the user manual that talks about the
50cc one  cylinder sample program which should work for us as is.
All we need do is  modify it if we get lucky.

  Quote:
  " Once you have installed the CodeWarrior application and become
familiar
  with its operation through the virtual lab, the software
development  environment can be validated. Software Development Environment
Validation
  Exercise

  1. Create a new project in CodeWarrior for the MC9S12P128 MCU
using the  Project Wizard that appears when CodeWarrior is launched.
Create the project  using default settings but be sure to include
the USB BDM tool [USB  connector see attached file] included with
your kit as the target  connection.

  2. Once you have the project created, verify the integrity of the empty
  software project by doing a build.

  3. Once successful, connect the ECU to your 12V power source using
your  simulated load harness.

  4. Next, connect the PC to the USB BDM tool. Installation will be
required
  if this is the first connection to the PC, follow on screen menu
and install  driver automatically.

  5. Connect the BDM ribbon cable to the BDM header on the ECU, note
the  location of Pin 1 as the red wire on the cable and number 1
near the header.

  6. Press the debug control in CodeWarrior to download the empty
software
  project to the ECU. Follow the on  screen menus to connect and program
the
  ECU, as performed in the Virtual Lab for the S12XE.

  7. Press the ?GO? arrow and allow execution for a few seconds
before  pressing ?HALT?. The source window should show the processor
stuck in an  infinite FOR loop. This verifies that the ECU is
working and the software  environment has been created allowing
programming and development. As a  final piece towards a complete
development environment, a build of the  example software will
verify if all of the tools discussed this far are  working on your
system. System Setup Validation Exercise

  1. Save the example application software by copying the folder ?Example
  Scooter Application? from the DVD. This is a CodeWarrior project that
  contains a working application that runs a 50cc scooter engine

  2. Open ?My _Engine_Project.mcp? in the saved folder through
CodeWarrior.

  3. Build the project. [means compile or assemble]

  4. Program the ECU by providing power and clicking debugger per
previous
  exercise.

  5. Run the application using the green ?GO? button.

  6. Stimulate the application by running the engine position simulation
and
  using the Engine Stop Switch. Operation should be identical to
simulated
  engine environment test performed above." End of Quote!

  Does anybody have one of these demo boards yet?

  Paul Lamar

Paul, I noticed on a previous post that you mentioned having ambient
pressure data. Is the intent to write a function block in the
program to adjust for the percentage of oxygen in the atmosphere
lost due to altitude. This could be an automatic leaning type of
thing for reduced fuel consumption. Also with two injection nozzles
and two spark plugs are we looking at two boards per rotor, set to
different crank angle tooth counts, programmed like single cylinder
two strokes.

george grimes

Correct.

IMHO auto altitude compensation is not worth the additional code.
People lean the engine beyond that. We need a way of manual leaning.

BTW there is a lot of extraneous crap in Code Warrior. That makes it
difficult to sort through all that stuff for just a simple application.

I still have not found that one cyl 50 cc example source. Have you?

Paul Lamar

Paul I haven't loaded code warrior yet. I am trying out meshcam to
get cam files for my aluminum end housings on the four rotor. One
thing at a time.

  I was not looking to eliminate manual leaning, just thinking
about saving some climb fuel on long climbs to altitude. There is
some merrit to running over rich for cooling from latent heat of
evaporation
of
the fuel, however with no valves to damage and my parallel cooling
and material choices I don't think waiting for cruise to lean is of much
benefit. If I get round to writing an EFI program I would nest the
functions
with the inner functions controlling fuel flow timing  and spark
timings.

  There would be a counting variable to run all the extraneous calculations
only every 10 scans. Checking air temperature, engine
temperature,ambient
air pressure among others  to adjust variables in the core function
block
just adds unnecessary scan time, they would just maintain their last
calculated value if not updated on the current scan.Also keeping to a
minimal core block if one or more external sensors fails to produce data
in
the check range of the external function block, having the core isolated
is
less likely to result in engine stoppage.

  IMHO there is not a problem with
complicating the program code provided some attention is given to
isolating
the important minimum output. Nearly all the computer failures I have
suffered have been  related to power supplies and input data
failures. If the processor overheats and fails it is usually
catastropic in nature like turning off a light switch, it is working
then it isn't. The amount of code it scans is irrelevant to the failure.

  george grimes

  More code more bugs. Bugs are proportional to the square of the
code. If you want to  make it reliable keep it simple.

  Paul Lamar

If we want manual leaning than what is wrong with using a voltage divider
with a MAF?  I know it is non-linear but if we are going to be manually
leaning with a pot couldn't we just  adjust it based on an O2 sensor?
Please help me understand.  I have a MAF built into the airframe and
now we are going in a different direction.  Not that ther is
anything wrong with that.  Thanks

Joe Berki

The problem with the MAF sensor puts out 5 volts so a pot will
reduce that.

You have to divide by 2 and then use an amplifier or do it in software.

Paul Lamar

 Auto EFI sensors 1 to 5 volts. More volts, more fuel. Except the O2. It
works on 0 to 1 volt. You could lean on the MAP, MAF or temp sensor signals
with a pot. They should have 0 ohms in one spot. Select total pot resistance
for how much lean you want. Coolant temp is a good one to use for this
trimming. Some tuners use it to richen the mixture. Depends which wire you
put the resistor in.

Dale Davies


The bad news on the single cylinder board from Free Scale is they are not shipping until January. I have one on back order from Mouser. The other bad news is it is $220 so we are going to need a PC board if we are using one per spark plug. I am going back to the super 555 system for now as that will prove to be a much cheaper system.

Paul Lamar



-- 
The Rotary Engine NewsLetter. Powered by Linux.
ACRE NL web site. http://www.rotaryeng.net
Youtube key word UTUBPLEASE
Copyright 1998-2009 All world wide rights reserved.