Get the SoR Robotics Android App on Android Market for FREE. See this forum post for details.
0 Members and 1 Guest are viewing this topic.
But the reading of sensors isn't why you'd want a faster controller, but the processing of huge amounts of data - ie computer vision for example. But if you go to fast, the mcu could become unstable and on rare occasion write a 0 when it should be a 1. The clock could also become unstable, interrupts might fail to trigger, the UART might be mis-matched, etc.
I often run PICs at 4MHz as the internal clock divides by 4, giving me a nice simple 1000 instructions per second
Hi,When I run PIC's at 4MHz, I get the full one million, so you really have to complain to Microchip (Or your math teacher )
Anyway, I was reading atmel's document about noise in electrical circuits and I read something interesting. It said that to reduce overall system noise, run your MCU at the lowest speed possible for your application. So I guess that's a reason not to crank it up.