Target System (Console Out)

[KRibordy]

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!

[mikets]

Are you connecting via null modem serial cable? Or are you using NetConsole? If via serial cable, make sure it is a null modem cable, the console out switch is enabled and the communication protocol on the PC side is set to 9600,n,8,1.

[Thomas DeSilva]

You should be able to open the console that your printfs display to with nothing but WindRiver and the correctly configured connection. To open the console window, you just need to right-click on your cRIO connection in WindRiver (the one you're running code on, you don't need a new one), then navigate to Target Tools > Target Console. This should display your printfs while your code is running. Is this what you've been trying? If this isn't working, is it giving errors?

[KRibordy]

Last year we had a connection to the cRIO which we used to download code, view the console, and reset the robot. This year, with a new installation of WindRiver, it's apparently possible to download code without using a "connection." I haven't looked too hard for the documentation on how to make a new connection to the cRIO yet.

We're wirelessly connection to the D-Link adapter in access point mode. We managed to get the robot driving (it was a combination of bad PWMs and Victors, among other things), but it would still be nice for debugging purposes to have a console.

[CodeMonkeyMatt]

You downloaded your code without setting up a connection to the cRIO in Windriver? I didn't think that was possible.

[auk]

I can confirm that it is possible to download code without creating a vxWorks Target Connection in Windriver. We have been doing this routinely ever since we discovered it this year.

[CodeMonkeyMatt]

Huh, that would have been nice to know. I guess it doesn't really matter, just a neat tip. Thanks.

To actually contribute to the thread, check out the C++ Getting Started Guide here: http://firstforge.wpi.edu/sf/docman/..._documentation

Hope it helps.