Model engine CDI Autoadvance


Results 1 to 23 of 23

Threaded View

  1. #21
    Join Date
    Feb 2006
    Location
    Gilroy, CA
    Posts
    1,530


    Did you find this post helpful? Yes | No

    Default Re: Model engine CDI Autoadvance

    Yes, you could just use a lookup table, if you want to. I suppose there are advantages and disadvantages to each.

    Calculating with line equation:
    Code:
    variable = 85 * RPM
    delayangle = (div32 1000) - 60
    And for dwell:
    Code:
    variable = 4000 * 32
    dwell = div32 RPM
    Calculating with a lookup table:
    Code:
     
                              lookUp ldwell,[0,0,0,0,0,1,2,3,4,5,6,7,8,9,10,11,12,14,15,16,17,18,19,20,21,22,23,24,25,26,27,28,29,30,_
                                             32,33,34,35,37,38,39,41,42,43,45,46,48,49,51,52,54,56,57,59,61,63,65,67,69,71,73,75,77,79,_
                                             81,84,86,89,91,94,97,99,102,105,108,111,114,118,121,125,128,132,136,140,144,148,153,157,162,_
                                             165,169,172,176,179,183,187,191,196,200,205,210,215,221,227,233,239,246,254],delayangle
    A lookup table has at least one advantage:
    Code is quicker

    Math equation:
    Code is smaller (usually)
    Quicker to enter new equation than entering a large table (example you want to try a new timing curve)
    Results can be more precise.
    Can change curve on the fly with only two variables.

    I always try to do a math equation. If the math is too dificult, then I default to a table. But that's just my opinion. And there are many, many different ways to solve for "x".
    Last edited by ScaleRobotics; - 13th June 2012 at 05:29.
    http://www.scalerobotics.com

Members who have read this thread : 0

You do not have permission to view the list of names.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts