Deployed code not responding

[Matt2081]

We set up our control system on a board just like it says in chapter 2 of the control system manual. We set up our classmate, and logged into the driver account. After turning on the board, the "communication" light on the classmate lit up, but the battery voltage area went from having several dashes to nothing at all. Since the "robot code" light was red, I thought we had to load some code in it first for the battery voltage to show up.

I logged into the developer and started a project. I downloaded the default project, but the joysticks did not respond. Confused, I created a new VI: a very basic one that simply opens a joystick, reads it in a loop and displays it with an indicator, and then closes the joystick after the loop (it also includes a start communications VI and a stop communications VI in the appropriate places). I deployed that, and none of the joysticks would read in any USB port.

I have been working with this for several days now, switching cables, re-imaging the cRIO, changing ports, etc. trying to get it to work. Does anyone know what I might be doing wrong? Has anyone else had this problem?

[Greg McKaskle]

You don't mention enabling the robot on the driver station.

Once you have code running, you should run the driver station either on the development computer or on the classmate. If on the same computer, launch it from the Start menu. If using multiple computers, plug everything into the same switch.

Greg McKaskle

[2544HCRC]

Full disclamer: I am brand new to this and so am sharing my experiences. Take all of this with a grain of salt.

Make sure you have the code set to "run on startup" I know this was selected once before, but you seem to need to do this each time you load a program. Second, the classmate seems to need to be connected and you need to log in under drivers station in order to get things to work. I'm very new to this whole thing and am not sure what bit of magic is performed, but I do know the driver station is critical.

We found this out yesterday when trying to get the joystick input example to work. We had the whole thing working and then it wasn't again. Nothing would work until we plugged in the driver station. Then we could get everything to work. Make sure the driver station is set to the .5 address and the (seperate) developer station is .6

Good luck!