Email: Password: Remember Me | Create Account (Free)

Back to Subject List

Old thread has been locked -- no new posts accepted in this thread
Daniel Jenkins
02/22/13 23:46
Read: 1877 times
United States

#189447 - Looking for direction - racing application
I am a mechanical engineer who races opend road Time-Speed-Distance events. I have enough beckground in electronics to know what is possible, but not enough to do it. I have a Cygnal 8051 F124 kit that I am trying to use as a foundation for a timing system.

A little background:

A time speed distance race is about completeing a certain distance at a perfect moving average. I have an electronic speedometer that receives 5V pulses from a sender hooked to my driveshaft. Since the distance is known (90.000 miles), the number of pulses per mile is known (16124), and the target speed is known (180 mph, for example), I know I need to get 90 x 16124 pulses in 1800 seconds in order to cross the finish line on my perfect moving average. Since I start form a stand still, I will instantly be behind the closck as soon as the timer starts, requiring me to "catch up." The physical sender will start emitting pulses as I start to move, and at a rate equal to a factor of my actual speed.

What I want:

I want a continuously (~10Hz) updated display showing how far ahead or behind I am of the ideal count. In my mind, I would have one output that simply counted my ideal pace at a rate of 48384 cycles per minute (806.4Hz), a second counter that totaled the actual number of pulses actuall=y received from the sender, and a display that read the output of ideal - actual. I could than raise my speed past the ideal average to chip away at the deficit until I caught up to zero on my display.

Am I on the right track with this controller or am I totally missing the boat? I have NO programming experience, but I am wanting to learn.

List of 19 messages in thread
Looking for direction - racing application      Daniel Jenkins      02/22/13 23:46      
   step by step      Erik Malund      02/23/13 06:29      
      First step...      Daniel Jenkins      02/23/13 11:20      
         well, you are new      Erik Malund      02/23/13 13:08      
         First, check number sizes and precisions       Jim Granville      02/23/13 15:51      
            Good catch on the clock accuracy.      Daniel Jenkins      02/24/13 01:10      
               Judging      J. Guy      02/25/13 11:17      
                  Judging      Daniel Jenkins      02/26/13 12:25      
                     Rethink your solution      J. Guy      02/27/13 11:04      
                        Not sure we're seeing eye to eye...      Daniel Jenkins      02/27/13 20:16      
                     think precision       Jim Granville      02/27/13 13:44      
                        Increasing accuarcy      Daniel Jenkins      02/27/13 20:28      
                           Precision still matters.      Jim Granville      02/28/13 02:17      
            Precision distance!      Oliver Sedlacek      02/28/13 05:09      
               Rulebook on timing      Daniel Jenkins      02/28/13 11:37      
                  They have a serious system      Jim Granville      02/28/13 13:09      
   very imprecise      Erik Malund      02/28/13 13:37      
      re:      Jacob Boyce      02/28/13 14:52      
         re: speed      Daniel Jenkins      02/28/13 16:45      

Back to Subject List