"Emergency Stopped" message won't go away

[Lakedaimon]

Soryy if this is covered somewhere else, I searched and could not find anything on this.
We have been through multiple installation process on the driver station, we finally see the compass, everything is green, we are reading battery voltage - so I think we are getting close. However, the driver station says "Emergency Stopped" and we cannot enable anything. What are we doing wrong?

[Brandon_L]

If someone hit the button: Turn off robot and turn back on.

If not: I have no idea, check your code? I dont know if the watchdog does that as I have never been shut down by it. Try running the default code.

Not sure what it says if the button isnt plugged in, but make sure its in also.

[Lakedaimon]

Yep, that worked. It was still E-stopped through the driver station update and multiple PC reboots, but it's fine now.

I still can't get the camera working though. Went through the setup process multiple times, and I'm updating the Driver Station for the third time now, but I can't see it on the Driver Station.

[Brandon_L]

have the code running for the robot and it should work, did for us.

[basicxman]

For reference once the E-Stop button is pressed, you'll need to hard reboot your robot no matter what. For more details read the control systems manuals.

[Tom Line]

Originally Posted by Lakedaimon

Yep, that worked. It was still E-stopped through the driver station update and multiple PC reboots, but it's fine now.

I still can't get the camera working though. Went through the setup process multiple times, and I'm updating the Driver Station for the third time now, but I can't see it on the Driver Station.

You must either run code from a developer computer or permanently deploy code to the CRIO for a picture to be visible on the driver station.

[Lakedaimon]

To verify I understand what you mean - we have loaded the Java version of the bench test code from the Driver Station to the cRio and are using that to test with. I sounds like you are saying that the camera image will not display on the Driver Station with this configuration.
It sounds like now we need to load another project (TrackerDemo?) to get the camera to display on the Driver Station. Is that correct?
Thanks for the help!

[Tom Line]

I'm sorry - I can't comment on the Java configuration. I know in Labview for the camera picture to be visible, you have to "run" the code from a developer computer, or permanently deploy it to the CRIO. The vision components come as a standard piece of the default framework that everyone uses.

Sorry I can't help more - hopefully one of the Java programming teams sees the post.

[Mark McLeod]

Can you browser to the camera if you hook it directly to the Classmate?
I assume you setup the camera with an FRC/FRC account/password?

[Lakedaimon]

We loaded the CircleTrackerDemo code into the cRIO and the camera feed showed up on the DS, so we are on our way (at least for now.)
Thanks for all the great input!

[marley4070]

We were getting that same problem regarding the emergency stopped message on our driver console. I saw that everyone was mentioning things about problems with the code? I was wondering if anyone could help me diagnose what kind of problem that would be. Like, what would be the problem with the code that would produce that problem?

Help would be much appreciated!

Thanks!!!

[Mark McLeod]

Once your robot is E-Stopped it can only be cleared by turning the robot off.
E-Stop is designed that way.

The Driver Station space bar E-Stops the robot now, so avoid using it.
It's easier to Disable your robot using the Enter key.

[rg_09]

If you have issues after successfully setting up the camera and then doing a power cycle, it is because you are using the wrong version of the Camera Setup utility. Get and install the update from the NI site and it will correct this problem. The original version of the setup utility released around 2012 kickoff caused this behavior.

[Gigakaiser]

If you're using the actual E-stop button on your driverstation:

I was stuck on this issue for hours one day during build season. (we switched laptops, powercycled multiple times, etc) This may sound idiotic but the corner of our driverstation was slightly pressing the e-stop button the entire time.

[Tom Line]

HA!

We tried to use our E-stop button about a year ago (the old style). We discovered that I had been a little over-zealous hot-gluing it down. Evidently, we had gone to multiple competitions with an E-stop button that was about as useful as a paperweight.

ON another note (to National Instruments), PLEASE PLEASE get the e-top button off the spacebar. Trying to type on the drive station and constantly having it e-stop the robot is beyond annoying. Move it to the escape key. It's rarely hit during normal use.