As the title explains, when I enable tele-op, tele-op pauses itself. This hadn’t been a problem before this and no change was made to the code between then and now. Is there an explanation for this and how do I fix it?
What exactly do you mean by pausing? Do the Driver Station Comm and Code LEDs stay green when TeleOp “pauses”? Are you running the code permanently or with the run arrow?
I have comms and code still. I am running the code with the run arrow. By “pause” I mean the built-in LabVIEW pause button is activating itself.
Do you have a breakpoint in your code that you added by accident?
No. I did forget to mention that I had e-stopped the robot sometime around/before then. Could that have an effect?
I did cycle power and restart the code, driver station, etc. after that, though.
Estopping should be fine if you have rebooted everything. Are you getting any errors on the driver station?
Yes - lots. However, all of the ones I’m getting are related to having things in code that don’t physically exist yet, and are the same as before.
I do want to note that I pulled the same version from github and ran that and it worked fine.
Open Robot Main and go to View->*Breakpoint Manager *and see what’s listed there.
There might be two default breaks, but there shouldn’t be any more.
You shouldn’t be running the program by the arrow build it then deploy it and run it from the driver station.
He’s probably just debugging the program, as an actual build/run as startup takes several minutes.
This is not true. LabVIEW is meant to be able to run without a full deploy. If you have a slow laptop or packet loss, that can cause the behavior you are seeing. In addition, any errors showing in the diagnostic window can potentially cause issues.
A slow wifi connection to the programming computer should not cause the robot to do anything out of the ordinary but it may cause indicators on the computer to be delayed. A slow wifi connection to the DS could cause some hiccups, however.
Are you seeing the pause button near the run arrow turn red? If so, what happens when you click the red pause button to un-pause?
Just to pile on, … err … , I mean clarify, LabVIEW debugging involves running the VI interactively by pressing the run button
Each VI’s compiled code is downloaded to memory, connections are established so that you can see panels, probe, breakpoint, change some values on panels, etc.
Once the code is working well, you build an exe and deploy it. There happens to be a way to compile debugging into an exe, but that is not used as often as the interactive case.
Greg McKaskle
Does deploying as startup produce the same pausing behavior?
Yes, the pause button turns red. When I un-pause it, it finishes that iteration of the teleop loop, and pauses on the next iteration.
I was making the (perhaps incorrect) assumption that he was running the code on the driver station. Ever since we got rid of that hideously underpowered classmate 8 years ago, that’s the way we’ve done it.
In the Teleop front panel or block diagram check under Operate on the top menu bar and see if *Suspend When Called *happens to be checked.
It is not checked. I do have a red border around the edges of the vi though.
A red border means you have a Breakpoint set somewhere.
http://digital.ni.com/public.nsf/allkb/113422F9F1F73A8A8625670D00547B7C
Thank you!