Thread: Motor Drivers
View Single Post
  #12   Spotlight this post!  
Unread 19-02-2013, 00:09
Jaxom Jaxom is offline
Registered User
AKA: Michael Hartwig
FRC #1986 (Team Titanium)
Team Role: Mentor
 
Join Date: Apr 2010
Rookie Year: 2008
Location: Lee's Summit, MO
Posts: 379
Jaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant future
Re: Motor Drivers

Quote:
Originally Posted by team1165wins View Post
I am pretty sure that vxWorks (on the cRIO) uses a lot of the processing power itself, just like how a slow netbook might have a 50% processor usage, running nothing but the operating system.
If your OS uses 50% of your CPU you need a new OS. vxWorks isn't that bad. Heck, even Windows isn't that bad.

But to reiterate the answer others have given to your original question: that kind of coprocessing is not legal for FRC; the cRIO has to control your motors. If you're experiencing lag you should spend the time to learn more about your current environment & find out *why* you have lag. It's pretty easy to introduce unwanted lag via programming.
__________________


Mentor http://www.teamtitanium.org/