Re: We are going to Want a GRIP fourm
 

Yes to both questions. If you look at SampleRobot.java (the base class your code is using), you'll see there's a number of different functions you can override. robotInit() is one. robotMain() is another (as is operatorControl(), disabled(), autonomous(), etc). The startCompetition() function shows the sequence in which these functions are called. robotInit() is called first, and should contain only initialization code -- code you want to run before the match. Only after robotInit() returns does startCompetition() call the FRCNetworkCommunicationsLibrary to let the driver station know robot code is ready to run (which is what makes "No Robot Code" disappear). Note it's somewhat risky to override robotMain() instead of the individual operatorControl(), disabled(), etc. functions, as you will need to handle the state transitions between these modes yourself (versus having startCompetition() handle it for you).

While SampleRobot is okay for small test programs like this one, for your actual competition robot code, if you don't want to do command-based programming, I recommend you use a different template such as IterativeRobot and override only robotInit and the various autonomous/operatorControl functions. The IterativeRobot class startCompetition() function will take care of calling these functions in the right order and putting in appropriate delays to not swamp the CPU.

Re: We are going to Want a GRIP fourm
 

Hello. New to vision processing.

I'm trying to deploy GRIP to my roborio but no luck. It doesn't tell me that it failed, it simply spins and there is no run button or console activity. I've tried deploying to roborio-58-frc.local and other ip addresses.

As a side note I also cannot get Network table data from the outline viewer. thanks.

Re: We are going to Want a GRIP fourm
 

^^^^^^
Same :-/

Re: We are going to Want a GRIP fourm
 

I honestly can't help much with deploying, maybe try checking the issues page for similar problems.

If you go to the chat you can also talk to @JLLeitschuh, who wrote the deploy code.

Re: We are going to Want a GRIP fourm
 

When the robot is on Communication to the drivers station with the smartdashboard working and displaying data from robot code run GRIP on the PC. Set the GRIP project NetworkTable address to 10.TE.AM.20 (Is you TEAM 0058?) if not your roborio-58-frc.local is wrong and should be roborio-TEAM-frc.local were TEAM = your number 1234. Now create a pipeline in GRIP to write data to the Network table. Online Viewer.jar should show your smart dashboard data and Grip Data. You must also enter 10.TE.AM.20 in the Online Viewer and select client. Or Test GRIP not using the Roborio by tring to follow a suggestion I made on the GRIP issues pages. https://github.com/WPIRoboticsProjects/GRIP/issues/349

Re: We are going to Want a GRIP fourm
 

new page to the wiki

Tutorial:-Deploy-to-the-Robot

Re: We are going to Want a GRIP fourm
 

This may sound really stupid, but for the life of me, I can't figure out how to get the results from the "Publish ContoursReport". I don't want to deploy it onto the robot yet, but I want to be able to see what the X and Y coordinates it finds in the sample images so I can try and write a program that would make decisions on it.

Re: We are going to Want a GRIP fourm
 

I did share a way with the developers and they marked it as a Wiki item. I just started poking through their code and with their blessing my help and write this to the Wiki. For the mean time check this out.

https://github.com/WPIRoboticsProjects/GRIP/issues/349

Re: We are going to Want a GRIP fourm
 

Is there a way to just get the Outline Viewer? We use Python so I would rather not have to install Eclipse and Java in order to just use the one program.

Re: We are going to Want a GRIP fourm
 

I wonder if you could extract it from the off line Java tools install method mentioned at the end of the "Installing Eclipse (C++/Java)" set up pages.

Re: We are going to Want a GRIP fourm
 

To everyone having deployment problems, you can also try to deploy it manually:

1. Set your publish address in GRIP's settings to your RoboRIO's address (roborio-<teamnumber>.local)
2. SCP (using PuTTY pscp on Windows) app/core-1.0.0-all.jar from GRIP's install location (typically C:\Users\<username>\AppData\Local\GRIP) to your RoboRIO:

3. SCP your grip profile:

4. Login over ssh/PuTTY to the lvuser account
5. Start GRIP:

Re: We are going to Want a GRIP fourm
 

FYI GRIP v1.1.x is out now. This show hopefully fix all of your deploying problems and more.