Thread: Debugging on the cRIO
View Single Post
  #3   Spotlight this post!  
Unread 27-01-2011, 10:34
whytheheckme's Avatar
whytheheckme whytheheckme is offline
Registered User
AKA: Jacob Komar
no team
  
Join Date: Feb 2006
Rookie Year: 2005
Location: Providence, RI
Posts: 1,320
whytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond reputewhytheheckme has a reputation beyond repute
Send a message via ICQ to whytheheckme Send a message via AIM to whytheheckme Send a message via MSN to whytheheckme Send a message via Yahoo to whytheheckme
Re: Debugging on the cRIO
Quote:
Originally Posted by kwojcik View Post
I figured out how to do this 2 years ago but I highly recommend you do not try to do this. Reason being: one time we deleted the tasks and the robot started driving full speed... very dangerous.
Really? I don't think this can happen due to the interface between the PPC and the FPGA - if the kernel crashes, the FPGA should disable the outputs.
Reply With Quote