GRIP needs to be reloaded each time the robot is restarted

[SupremeSteak1]

So we *finally* have a GRIP program that does everything we need to and works well. While testing however, we found that whenever the robot is turned off and turned back on, GRIP is no longer loaded. We were wondering if anyone else has had this problem and found a solution to it. Thanks!
- Team 1100 Software Subteam

[1024Programming]

We ran into this problem last night and were about ready to make a post about it. Don't know if running grip on a coprocessor will fix this problem.

[Poseidon5817]

So we *finally* have a GRIP program that does everything we need to and works well. While testing however, we found that whenever the robot is turned off and turned back on, GRIP is no longer loaded. We were wondering if anyone else has had this problem and found a solution to it. Thanks!
- Team 1100 Software Subteam

Same issue, but we have to redeploy GRIP every time we deploy code. This makes testing slower and obviously won't work during competition. Was about to make a thread about it too.

[techhelpbb]

So a few of those I mentor have been playing with GRIP.
It seems it runs a Java JAR file on the RoboRIO to talk to OpenCV.
The description of GRIP under 'How was GRIP made' (https://github.com/WPIRoboticsProjects/GRIP/wiki)

Have you listed out the processes when it is working via PuTTY and SSH?

ps aux | grep java

The aux means:
a = show processes for all users
u = display the process's user/owner
x = also show processes not attached to a terminal

The grep will search for any line in the output that contains the work 'java'.

You should see your GRIP project name on one of the running JAVA processes something like this:

java FindRed.jar

Then check to see if this still appears if it failed to start?
I would expect that to automatically start somewhere it must call Java to run that JAR file at restart.

[robert1356]

I am only at the experimentation stage, but hoping to do something closer to production tonight. Once the GRIP jar file is deployed (using the GRIP app), is it supposed to start automatically when the robot is rebooted or do we need to create our own startup script? Anyone know? Also, what we will actually need to do is:

Let the robot code launch
- robot code will set the exposure and brightness from preferences
- robot code will disconnect from the camera
Need to launch the GRIP jar file

The above is needed because, based on my initial testing, if you adjust the exposure and brightness, they reset to some default value on power cycle and GRIP has no option to set the values

[fsilberberg]

You need to start up GRIP on your own, it does not restart with your robot code. The GRIP guys have a tutorial on their GitHub that you can look at here: https://github.com/WPIRoboticsProjects/GRIP/wiki/Tutorial:-Run-GRIP-from-a-CPP-or-Java-FRC-program

[Poseidon5817]

You need to start up GRIP on your own, it does not restart with your robot code. The GRIP guys have a tutorial on their GitHub that you can look at here: https://github.com/WPIRoboticsProjects/GRIP/wiki/Tutorial:-Run-GRIP-from-a-CPP-or-Java-FRC-program

This looks perfect. Thanks!

[1024Programming]

You need to start up GRIP on your own, it does not restart with your robot code. The GRIP guys have a tutorial on their GitHub that you can look at here: https://github.com/WPIRoboticsProjects/GRIP/wiki/Tutorial:-Run-GRIP-from-a-CPP-or-Java-FRC-program
AHAH! They changed it! looking at this; now it should work.

[SupremeSteak1]

You need to start up GRIP on your own, it does not restart with your robot code. The GRIP guys have a tutorial on their GitHub that you can look at here: https://github.com/WPIRoboticsProjects/GRIP/wiki/Tutorial:-Run-GRIP-from-a-CPP-or-Java-FRC-program

Thanks! This is exactly what we were looking for!
- Team 1100 Software Subteam