Dificulties developing software

[Daniel_H]

I helped our team program during 2009 and we were continuously sending provisory software to cRIO and monitoring things on the code's front panel, a very quick and helpful process btw. I couldn't participate actively last year, I know a lot has changed, but frustratingly I couldn't do the same thing this year so far.

I first tried to monitor a sensor, so I put the necessary code inside the teleop VI and observed the chart in the front panel. Nothing happened. Later I realized that the competition status was stuck on "Autonomous disabled" and there was no way to get it out of there. The teleop vi was never being called. How do we select the competition status outside the competition in order to test our codes?
I'm not talking about using the driver station, remember that I am developing code and continuously changing and uploading it to monitor sensors and other variables on the front panel.
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.
If you programmed in 2009, you probably know what I'm talking about.. is there a way to use the cRIO like it was done back then?

btw, all I did was with a tethered connection. If I want to do this wirelessly, again, not using the driver station, all I need to do is connect manually to the router while in AP mode?

Thanks.

[Kevin Sevcik]

You need to have the driver station software up and running with the STOP button connected or overridden. There is no other way for you to run your code and have it enter into teleop mode.*

Luckily, this doesn't preclude you from the active debugging and running code that you want to do. You can still just hit the run button on the appropriate startup VI, and the code will download to memory and start running. Having the DriverStation software up and running shouldn't impact this a bit. The only way I could see it causing a problem is if you have a LOT of data going back to your driverstation.


*That is, no way without HEAVILY modifying the base framework. To the extent that I wouldn't really trust any code you've developed on it afterwards.

[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.