Re: We are going to Want a GRIP fourm
 

Maybe to fix the problem of Grip vs Streaming the Grip app should generate a Java / C++ / your language script similar to RobotBuilder to insert directly into the code. Then They can share the same capture frames.

Re: We are going to Want a GRIP fourm
 

1. While developing the script the camera is connected to the pc running GRIP.. after the script is done, i move the camera to the USB port on the rio and then deploy the script to the rio.

2. Im lucky that even with the on board camera built into my laptop the usb camera we are using get identified as camera0 consistently when used on the RIO and on my laptop.

3. the process for getting the camera on the smartDashboard is entirely separate from using GRIP and thus they actually will conflict with one another.
The strategy when using grip is to do the analysis of the image on the RIO and then only transmit the raw numerical data back to dash to assist the driver via indicators.

4. roborio-4525-frc.local


let me clarify this. GRIP is a separate program from your Robot. Within the GRIP development UI there is the ability to deploy.. and after a brief wait a play button will appear to launch the GRIP script on the RIO.

A GRIP script should include as its last step one of the RIO publish tasks. These push data to the networkTables mechanism that your Robot code can access.

There are thus separate applications that talk via the networkTables.

Re: We are going to Want a GRIP fourm
 

agreed.. i would like to embedded grip vs having to call to runtime to start yet another java application.. from my java application. :P

Re: We are going to Want a GRIP fourm
 

Scary.. I have had limited success deploying and running grip on the Rio. If the NetworkTable has old data it will not clear. How I see it if Grip does't launch you maybe acting on OLD DATA.

Re: We are going to Want a GRIP fourm
 

for the data to be good to the driver or autonomous system is needs to be constantly updating.. .if you see static numbers.. youll know somethings up.

Re: We are going to Want a GRIP fourm
 

If it's a USB webcam, probably not. I don't think multiple applications can access a USB webcam on linux at the same time.

One planned feature for the next minor version of GRIP is a "publish image" operation. That should let you look at any image in your pipeline using SmartDashboard.

Re: We are going to Want a GRIP fourm
 

I see the option for deploying a GRIP pipeline to the roboRIO. However, I'd like to try running my pipeline on a Raspberry Pi.

Is there an easy way to simply generate the pipeline's grip.jar file onto my local filesystem?

Re: We are going to Want a GRIP fourm
 

Seen that in the issues tab of the project #355. Would help heaps. Also is there talk about adding blocks to get data from the SmartDashboard to get values to plug into the slider controls to dynamically control the filters from the Robot or Smartdashboard?

Re: We are going to Want a GRIP fourm
 

I love the discussion going on. I've challenged our programming team with GRIP. I've asked them to give a short presentation to the team leaders and mentors about GRIP. What is it, what can it do, what are the pain points, and how can it make our bot better.

My first thought is to run it on a Raspberry Pi too. But we'll see. With all the talk in here, I think they'll get a good feel of what to expect. It might be interesting to spin up an IRC chat room in the evenings for help/advice, if there is interest in it. Being an alpha version, we're all experiencing growing pains.

Brian

Re: We are going to Want a GRIP fourm
 

Help me out please... What is GRIP?

Can you point me to documentation/description?

Re: We are going to Want a GRIP fourm
 

GRIPis GRaphical Iage Processing. It allows easy creation of 'pipelines' that will allow you to identify objects. It's not apart of your robot code, but is a separate program. After getting things setup, you then have to connect the data from GRIP to your robot software.


Jojoguy10 posted a link for more information: http://wpilib.screenstepslive.com/s/4485/m/50711

Re: We are going to Want a GRIP fourm
 

Re: We are going to Want a GRIP fourm
 

Is "filename" a variable in your code, or am I supossed to write something specific? If I only write filename, eclipse is showing me an error

Re: We are going to Want a GRIP fourm
 

Thomas

if you have insight into the inner working of GRIP..
can you provide a build of the existing version where by i can programmatically start (<here is my .grip file) and stop() grip.
suggesting we call out to an external process to run it means we have no control over grips lifecyle in relation to our robot.

Re: We are going to Want a GRIP fourm
 

I'm Quoting from https://github.com/WPIRoboticsProjec...va-FRC-program

In my code I created a variable to String filename = "myGripProgram.grip"; There is no documentation on how or why to do this I just assumed. It hasn't work for me yet.