Weird Crio/Programming problem

[mattiej]

Originally Posted by Cecil

When you say tethered, do you have it tethered to the D-Link or to the cRIO? It almost sounds like the D-Link is losing power/connection for a second. Do you have the DC to DC converter plugged into a normal 12 volt slot on the Power Distribution Board or the dedicated 12 volt port at the top of the board? Your motors could be drawing enough that it could reset your D-Link.

We are directly hooked into the cRIO. We have the D-Link hooked in correctly though.

Originally Posted by Mark McLeod

If the Safety Config is tripping, then you should see an error message on the Diagnostic tab window eventually. You probably have to scroll back through all the messages carefully.
If you suspect it, then you can Disable the Safety Config, but I'd put the robot up on blocks to test it, so that if it tries to run away it won't get anywhere or hurt anyone.
In fact, I'd put the robot up on blocks until you get this figured out.

The robot is already up on blocks. Always test that way after laptop #1 got destroyed by a robot. I didn't see a Safety Config error message, but I will double check.

Originally Posted by Mark McLeod

Lost communication can also be caused by a poor DLINK power connection on the robot. If you have the robot up on blocks try directly connecting an Ethernet cable between the laptop and the cRIO to test run.

We tried the Ethernet cable and still had the same issue.

Originally Posted by Mark McLeod

You can use a Diagram Disable structure (same menu as the programming loops) on the camera code or delete it altogether if you don't plan to use it. Code for the camera is in Begin.vi and Vision Processing.vi and both will need to be disabled.

The FRC Driver Station Log Viewer should show up on your Start -> All Programs menu. It got installed with the Driver Station update.

Thanks!

Originally Posted by katsauga

is there a chance you have a bad joystick?

That's next on the list for testing. But from looking at the Driver Station just now, I did notice that the driver station seems to be returning a ~.07 value on an axis when it isn't even being moved.