|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Motor Controller Temporal Resolution
I believe all the speed controllers update at 5ms except for the legacy Victor, which was at 10ms. If you look at the diagram of the various motor control Open nodes, you'll see them us 1x, 2x, or 4x as their period multiplier. This is in 5ms increments.
Greg McKaskle |
|
#2
|
||||||
|
||||||
|
Re: Motor Controller Temporal Resolution
For anyone confused at home, adciv gave the update rate for CAN on the roboRIO, (ie how often the roboRIO will send a new command) and Greg gave the update rate for PWM on the roboRIO. On the cRIO, by default, only the jaguar used 5ms for PWM.
Michael, what kind of sensor did you use for the catapult position? Correct me if I'm wrong, but if you could get the catapult to stop at the right position, it wouldn't matter what the temporal resolution is, right? |
|
#3
|
||||
|
||||
|
Re: Motor Controller Temporal Resolution
Quote:
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|