Dificulties developing software

[Alan Anderson]

Originally Posted by Daniel_H

If we are to use the driver station, we have to build and deploy the code, which takes a lot of time, and won't help monitor so freely as the code's front panel does.

That's wrong.

You do not have to build and deploy code in order to use the driver station. You can do exactly what you want to do and simply run the Robot Main vi, then enable the robot to let Teleop execute.

[Daniel_H]

Originally Posted by Alan Anderson

That's wrong.

You do not have to build and deploy code in order to use the driver station. You can do exactly what you want to do and simply run the Robot Main vi, then enable the robot to let Teleop execute.

Once I'm communicating with cRIO through LabVIEW, the Driver Station can't communicate with it, isn't that right?
If that is true, I have to send the code, close LabVIEW (or disconnect) and open the driver station, right?

I much prefer doing my tests and measurements in LabVIEW then at the driver station, but I need the driver station to change the competition status

[Joe Ross]

Originally Posted by Daniel_H

Once I'm communicating with cRIO through LabVIEW, the Driver Station can't communicate with it, isn't that right?
If that is true, I have to send the code, close LabVIEW (or disconnect) and open the driver station, right?\

That is not correct.

[Alan Anderson]

Originally Posted by Daniel_H

Once I'm communicating with cRIO through LabVIEW, the Driver Station can't communicate with it, isn't that right?

No, that is not right. The Driver Station talks to the robot whether you run the Robot Main vi interactively or deploy the compiled program to run at startup.

You do not need to close the Driver Station application before you run LabVIEW. You do not need to close LabVIEW before you run the Driver Station application. The Driver Station program should always be running if you are doing robot software development.