Reboot robot every download?

[lostkhaos]

No no no, I know how to make it deploy-able. My issue is when I deploy code that isn't "installed". The first time it works fine, but if I stop the program and change something, then RE-upload it, it fails to do anything at all. If I reboot the robot, however, I can then upload code which executes beautifully.

[Greg McKaskle]

The typical workflow is to press the run button on your VI, stop edit, press run, ... , until your code is perfect.

Once you are happy, you then build, deploy, and set to run as startup. When you do that, your code runs on startup, stopping it means you need to reboot the controller or use a command line tool to start it. LV doesn't expect startup apps to stop and be restarted.

Greg McKaskle

[lostkhaos]

Let me be as clear as I possibly can. I do not have the code set to run at startup. The code is supposed to be loaded to RAM. The code is not installed. I know my process is correct because it used to work. It no longer does.

[airnate]

lostkhaos,

Sorry, we clearly don't understand the work flow that you use. Can you describe for us the procedure that you are actually undertaking and the resulting behavior vs what you intend it to do?

e.g.

1. I open the Basic Robot Main project
2. I expand the Build Specifcations
3. I right click on the FRC Basic Robot Deployment and select Deploy
4. The cRIO reboots and executes the code, but...

[lostkhaos]

1. I turn on the robot
2. I turn on the DS
3. I open my project
4. I open Basic Robot Main.vi
5. I click "Run"
6. The robot code executes normally
7. I click "Abort Execution"
8. I click "Run"
9. The robot code does not execute

[Greg McKaskle]

When the robot doesn't execute, what does it do? Do you get an error? Does the Robot Main VI look like it is running?

Early template code didn't do a good job of killing camera and compressor tasks, so that on a restart some stuff would give errors or behave a little funny. Those issues weren't that serious and would normally work, and they have been fixed since update 1 or 2. Please describe better what the run button does and we can figure out what is going on.

Greg McKaskle

[lostkhaos]

Ok, I'm using version 3. When I say it does not execute, I mean that there is no error returned, yet Main.vi insists that it is running. And if I turn off the robot, LabVIEW notices and waits for it to come back.

[Alan Anderson]

Originally Posted by lostkhaos

When I say it does not execute, I mean that there is no error returned, yet Main.vi insists that it is running.

That sounds like it is running. What makes you think it isn't?

[lostkhaos]

None of my code ends up being executed. For example, my drive train? Nothing. My camera search pattern? Nada. Joystick triggers? Nihil. However, if I reboot the robot and change none of my code, it works like a charm.

[Alan Anderson]

Originally Posted by lostkhaos

None of my code ends up being executed. For example, my drive train? Nothing. My camera search pattern? Nada. Joystick triggers? Nihil. However, if I reboot the robot and change none of my code, it works like a charm.

None of your code? So far, your description just indicates that the outputs are not working, but you haven't said anything to help determine where the problem lies.

Have you tried probing the joystick axes? The camera servos? The inputs to the motor drive? Find out how far things do work, and then we can try to figure out why they stop working at that point.

[lostkhaos]

Ok, after further investigation the motors were the ones that did not respond without a reboot. I have lately flashed the v11 code to the robot, and it is now working flawlessly. Issue closed?

[TimeOut]

One note, use the large 'Finish' button in the Robot Main.vi If you press that button it calls the finish.vi and closes all the references. If you press the 'Abort Exectution' button, you could possibly still have stuff open and running on the cRIO. There is quite a bit of code that is running behind the scenes that may not shutdown properly without calling the finish.vi

Sean

[lostkhaos]

Large 'Finish' button? I don't have one, how would I add one?

[TimeOut]

I'm sorry, the 'Finish' button is in the Advanced Framework and it sounds like you are running the Basic Framework. That goes along with there not being a finish.vi. (Edit: Meaning, that this is probably not the problem)

When you hit the run button the second time, open the block diagram for Robot Main.vi and press the 'light bulb' on the tool bar. Do you see it highlighting the execution through your TeleOp Execute?

You may also want to try to put a probe on one of the joystick axis just to see if it's reading the joysticks.

Sean