| ??? 05/13/08 16:41 Modified: 05/13/08 16:41 Read: times |
#154735 - Agreed Responding to: ???'s previous message |
an ISR should "almost always" do nothing except tell main() what to do
True enough. One example that came to mind was driving a stepper motor. That's one of those cases where the timing has to be precise, and the best way to do it is to go ahead and have the ISR wiggle the signals that control the motor. -- Russ |
| Topic | Author | Date |
| Struct member losing value | 01/01/70 00:00 | |
| Please post your code | 01/01/70 00:00 | |
| Posted here (along with file descriptions): | 01/01/70 00:00 | |
| the can of worms | 01/01/70 00:00 | |
| Your program needs to be restructured | 01/01/70 00:00 | |
| Can't mod this one up enough. | 01/01/70 00:00 | |
| Thanks for the tips | 01/01/70 00:00 | |
| You're doing pretty good then. | 01/01/70 00:00 | |
| I think that it can be said in a simple way | 01/01/70 00:00 | |
| Sorry but.. | 01/01/70 00:00 | |
| Agreed | 01/01/70 00:00 | |
| the phrase was | 01/01/70 00:00 | |
| I agree | 01/01/70 00:00 | |
| Don't ignore rules | 01/01/70 00:00 | |
| What is "short" in an ISR...? | 01/01/70 00:00 | |
| Two Program | 01/01/70 00:00 | |
breaking switch/case | 01/01/70 00:00 | |
| Do you understand why? | 01/01/70 00:00 | |
| make it a FAQ, please... | 01/01/70 00:00 |