The term real time is subjective in this context anyhow. There is always going to be latency, it is just a matter of how much you can put up with. After all we're not talking about some medical device, or Automobile control system. UAV ?
But looking at this from an automobile perspective, you have a main computer system with many MCU's Performing sometimes critical tasks, and communicating back and forth with this main system via CANBus. The OP really needs to define "Robot" more clearly. I mean we're not talking about an AT-AT walker model with stepper motors, while also having the ability to walk around are we ? . . . On Wed, Jul 2, 2014 at 5:30 PM, Robert Nelson <[email protected]> wrote: > On Wed, Jul 2, 2014 at 7:28 PM, Jerry Davis <[email protected]> wrote: > > I have used BBB, RPi, and arduino. > > > > arduino is closer to real-time if you need that. However, it does only > what > > is programmed in C in a loop fashion. There is a setup() function and > loop() > > function. > > just about everything is done in the loop. If you need tight integration > > (real-time) with some piece of hardware, then arduino is the way to go. > > Unless you use the "pru" on the bbb.. ;) > > Regards, > > -- > Robert Nelson > http://www.rcn-ee.com/ > > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to the Google Groups > "BeagleBoard" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- For more options, visit http://beagleboard.org/discuss --- You received this message because you are subscribed to the Google Groups "BeagleBoard" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
