Timeline for How to handle polling method in micro controllers.?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 26, 2015 at 14:50 | comment | added | tcrosley | @Lundin Agree, that's why I brought up the issue of the UART speed, input rate etc. At 115.2K baud, one message should not take more than about a ms. Obviously an interrupt driven system is a better way to go. This was meant to be a quick refactoring of the original code. I assumed the chances of all the chances of all inputs firing at once are low. | |
| Nov 26, 2015 at 13:33 | comment | added | Lundin | This code creates a tight coupling between the UART transmission time and the delays, where they depend on each other. Suppose there is not enough TX buffers to store the whole message, so that the transmission routine has to wait for the message to get sent; the delays would be arbitrary and real-time non-existent. | |
| Nov 26, 2015 at 11:28 | vote | accept | user46573544 | ||
| Nov 26, 2015 at 11:24 | comment | added | user46573544 |
thanks I have done the same thing. I have made a function inputs for all inputs and calling input after every led. So its working but now I have managed to write a code for TX RX interrupts. Here is my new question: electronics.stackexchange.com/questions/202873/…
|
|
| Nov 26, 2015 at 10:51 | history | answered | tcrosley | CC BY-SA 3.0 |