Thread: Target System (Console Out)
View Single Post
  #1   Spotlight this post!  
Unread 18-02-2011, 15:19
KRibordy KRibordy is offline
Registered User
FRC #1000 (Cybearcats)
Team Role: Mentor
  
Join Date: Mar 2008
Rookie Year: 2006
Location: Valparaiso, IN
Posts: 36
KRibordy is an unknown quantity at this point
Target System (Console Out)
Hey guys,

We're trying to figure out why our robot won't drive. I realize that this could stem from a number of issues, but mainly I want to make sure the software isn't the issue.

Last year, we could connect to the cRIO via WindRiver and get a console output using printf and such. It seems that they changed a few things this year and I cannot figure out how to achieve the same result. I tried creating a new connection to the cRIO's IP, but WindRiver refuses to connect. Are there any parameters that I should be using?

To clarify, WindRiver downloads the code without any problems, the driver station can communicate with the robot and go into tele-op/autonomous mode, but that's as far as we get. No signs of life on the robot. We just imaged the cRIO to v28 and I just installed the latest WindRiver updates, so I'm pretty sure this is a minor thing that I'm overlooking.

Thanks in advance for any help!
Reply With Quote