Thread: Motion Outputs disabled after cRIO reboot via DS
View Single Post
  #5   Spotlight this post!  
Unread 18-03-2013, 05:34
Travis Hoffman's Avatar Unsung FIRST Hero
Travis Hoffman Travis Hoffman is offline
O-H
FRC #0048 (Delphi E.L.I.T.E.)
Team Role: Engineer
  
Join Date: Sep 2001
Rookie Year: 2001
Location: Warren, Ohio USA
Posts: 4,047
Travis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond reputeTravis Hoffman has a reputation beyond repute
Re: Motion Outputs disabled after cRIO reboot via DS
Quote:
Originally Posted by Kevin Sevcik View Post
Forgot to mention that you should probably run a practice match after booting. Or atleast enable teleop mode. That starts several functions that could throw relevant exceptions. We had the silly problem of not testing for a null pointer and killing the robot if we enabled in teleop without running auto first. Exception came right up in Netconsole and made the problem pretty obvious.
Will do.
__________________

Travis Hoffman, Enginerd, FRC Team 48 Delphi E.L.I.T.E.
Encouraging Learning in Technology and Engineering - www.delphielite.com
NEOFRA - Northeast Ohio FIRST Robotics Alliance - www.neofra.com
NEOFRA / Delphi E.L.I.T.E. FLL Regional Partner
Reply With Quote