Thread: Vision Tracking Crashing Crio
View Single Post
  #5   Spotlight this post!  
Unread 19-02-2013, 04:40
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
  
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,752
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Vision Tracking Crashing Crio
To the original poster, the doc you attached is running on the dashboard? And when it sees targets it causes the robot to crash?

I don't even see the 3rd dashboard writing anything to the robot over SmartDashboard. How is it getting the data to the robot, and what is the robot doing with it. Also, what do you mean by crash?

To nickcvet89, I posted in the other thread about how to put stuff on the dashboard. You don't need to move teleop.

The overall structure is that RobotMain calls teleop each time a new joystick command comes in -- about every 20ms. If you don't return from teleop, you miss joystick commands and the robot is not responsive. If you put the code into another function that runs in parallel, such as Periodic Tasks or Vision Processing, then teleop will work as intended.

Greg McKaskle
Reply With Quote