Re: We are going to Want a GRIP fourm
 

I haven't tried running GRIP on a raspberry pi, but it might work. On Windows, the headless jar is likely at C:\Users\YourName\AppData\GRIP\app\core-1.0.0.jar. On Linux it's /opt/GRIP/app/core-1.0.0.jar (this jar is renamed to grip.jar and uploaded to the roboRIO when you deploy).

I don't think JavaFX has been ported to arm linux, so you probably can only run in headless mode on a Pi. Let us know if it works.

That definitely sounds like a cool idea. If you open an issue on GitHub, I can make sure you get notified when we implement this

Re: We are going to Want a GRIP fourm
 

If you're using java, I think you could also use the GRIP jar as a library in your robot project. That would let you manipulate the pipeline however you want. I'll play around with this idea and write up a tutorial if I can get it to work

We also might want to just let people start and stop the pipeline by setting a boolean in NetworkTables. Thoughts?

Re: We are going to Want a GRIP fourm
 

I was going to test running it on a Pi2 soon. However, NetworkTables will most likely not work without a specific NetworkTables build for Pi2, and OpenCV probably will run into the same issue. I know 100% it won't work on a Pi 1, however I haven't tested on a Pi 2. I know I tried RoboRIO binaries on a BeagleBoneBlack, and they did not work. And a Pi2 and BBB should be able to run the same binaries.

Re: We are going to Want a GRIP fourm
 

Has anyone been able to successfully deploy grip to their roboRio? Every time we try to deploy it we get a message saying that it failed. Has anyone encountered this error before? The firewall on our laptop is also turned completely off as well.

Re: We are going to Want a GRIP fourm
 

Pardon my ignorance but I can't seem to find the example files for the 2016 game.. the GitHub has the last 3 games (in addition to 3 fotos of a goat) but no 2016 game samples.

Re: We are going to Want a GRIP fourm
 

Re: We are going to Want a GRIP fourm
 

Yeah, I was afraid that might be true. The roboRIO and Raspbery Pi are both Linux/ARM, but they probably have different libc and kernel versions that make native binaries incompatible. I don't have a Raspberry Pi, but I'll see if I can get my hands on one and build and test the necessary binaries.

For updates, you can subscribe to this issue: https://github.com/WPIRoboticsProjects/GRIP/issues/366

Re: We are going to Want a GRIP fourm
 

Yes a few have. I have a few times too. Seems you may want to try in the settings both roborio-####-frc:local or 10.##.##.20 then when you go to deploy select the FRC advance. You will find the Deploy button is disabled. Edit the box but return it to what it was. (ie delete the .20 and retype .20) The button will enable.

#### - your roborio team number

For me roborio-####-frc:local did not fail but it did not transfer the files as well. When I used 10.##.##.20 it deployed and I got a Play/stop button above the counsel window.

I'm still working on launching the Grip.jar from the robot code. Grip has a wiki to do this but its not working for me.

Re: We are going to Want a GRIP fourm
 

We have tried using the advanced tab and retyping in the roboRio's address and have tried it using the mDNS and the IP address wirelessly and also directly connected to the roboRio through the USB 2.0 type B cable and none of these way seems to be able to deploy to the roboRio from GRIP. Though running GRIP from our pc we are still able to have it work and successfully use the Network tables, we are just unable to have the program deploy to the roboRio so that we don't require the laptop.

Re: We are going to Want a GRIP fourm
 

Did you set the deploy address in the settings tab where you set the network table address and team number. Did you try both mDNS and ip from there first before going to the deploy gui? I have not nailed down how I got it to work yet. Was earlier today and have not gotten back.

Re: We are going to Want a GRIP fourm
 

Yes, we have tried all available addresses to connect to the roboRio with. I was starting to think it may be a configuration issue though be we are not sure. Have you setup any sort of password or user account in the NI Web Dashboard that would allow GRIP to push the needed files onto the roboRio or are you guys just using the default admin account with no password?

Re: We are going to Want a GRIP fourm
 

I did download and install filezila per the wpilib.setupscreens pages to connect and browse the roboRio via sftp. I wanted to see the deploied files. They were not the. The next day when testing again I got a successful deploy. This could of punched a hole in somewhere? It did confirm that files could be transferred or maybe when it logged in it opened the password.

I have had chats with the developers because I wished to directly copy the files. Coping the grip.1.0.0.jar as grip.jar and myGripPipe.grip to the usr/ivuser and sound like it might work. I have to confirm the file locations as I'm not near my pc now. Look at the wiki java/cpp page it exposes the rio folder location "deploy " use. This would be OK for me if I can get the robot code to launch grip.jar. as per the same java/cpp page.

Re: We are going to Want a GRIP fourm
 

I have tried copying the files over manually however they did not work. When you were able to successfully deploy, were you doing it over ethernet?

Re: We are going to Want a GRIP fourm
 

I was wire ethernet. I was also using last year's hub. We have not dug into the new bag of tricks other than to inventory.

Re: We are going to Want a GRIP fourm
 

By robotMain() do you mean outside the robotInit() but inside the Robot() class? Also, by operational part of my code do you mean where I publish the data?