|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: Periodic Task Input
You can put your robot into test mode using the driver station. That allows you to watch sensors that you've opened while the robot is safely disabled, and it allows you to drive actuators that you've opened when enabled. Note that periodic code will continue to run, even in test mode.
It also allows you to run test VIs that you write to calibrate or verify controlled mechanisms. Greg McKaskle |
|
#2
|
|||
|
|||
|
Re: Periodic Task Input
Quote:
|
|
#3
|
|||
|
|||
|
Re: Periodic Task Input
We've seen this before on our robots. What does the dashboard report as your CPU utilization? If we're running at 100%, we see this on occasion. Do you have any unthrottled loops?
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|