![]() Moreover, they are much more precise (certainly depending on clock frequency accuracy) than other software timers using millis() or micros(). These hardware timers, using interrupt, still work even if other functions are blocking. The correct choice is to use a Hardware Timer with Interrupt to call your function. You'd prefer to have your function called, no matter what happening with other functions (busy loop, bug, etc.). So your function might not be executed, and the result would be disastrous. But what if another function is blocking the loop() or setup(). You normally use a software timer to poll, or even place the function in loop(). Imagine you have a system with a mission-critical function, measuring water level and control the sump pump or doing something much more important. Why do we need this STM32_TimerInterrupt Library This important feature is absolutely necessary for mission-critical tasks. Therefore, their executions are not blocked by bad-behaving functions or tasks. The most important feature is they're ISR-based timers. Timers' interval is very long (ulong millisecs). It now enables you to use up to 16 different ISR-based timers, while actually consuming only 1 Hardware Timer. This library enables you to use Interrupt from Hardware Timers on an STM32-based board. ![]() How To Install Using Arduino Library Manager ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |