Subject:
|
timing
|
Newsgroups:
|
lugnet.robotics.handyboard
|
Date:
|
Thu, 27 Feb 1997 16:59:57 GMT
|
Original-From:
|
Mike Degon <degon@cadetmail#IHateSpam#.uscga.edu>
|
Viewed:
|
1492 times
|
| |
|
|
Hi-
I'm attempting to write an assembly routine to control a pulse width, but I
can't seem to get the timing down. For example, I can output a 3.33ms
pulse width, but if I run the routine again, it sometimes jumps to 3.5ms,
and then jumps back down to 3.33ms the next time. Why is this? Does it
have something to do with interupts wedging themselves into my code? Can I
turn off all interupts? How about that heart beat? Can I turn it off? Or
turn off the whole LCD display, for that matter, because I'm not using it?
Sorry about all the questions, but I'm in desperate need of some answers.
Thanks,
Mike Degon
U.S. Coast Guard Academy
|
|
Message has 1 Reply:
 | | Re: timing
|
| (...) Mike, Not enough info to determine your problem. Are you using the Output Compare functions, or are you trying to emulate that functionality some way? The OC lines are hardware-set, so they go off whenever the free-running counter matches some (...) (28 years ago, 27-Feb-97, to lugnet.robotics.handyboard)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
