GRIP and NetworkTables settings for use with a co-processor

[Jdkmotorhead]

Ok, so I just tried it on my personal laptop, and it is working with the OutlineViewer in server mode, and the host set as localhost on both the server and GRIP. I don't see how this is any different from how I was testing it on the robot, with the addresses both set at roborio-5102-frc.local, and OutlineViewer in client mode...

[Peter Johnson]

Originally Posted by Jdkmotorhead

Yes, it has robot code running, and the robot is connected. I will try the other things next time I have access to the robot. And what GRIP console window? Is that just if you run it from the command prompt? Do I have to run the GRIP program somehow, or does it just work in real time as you edit the filters? Do I need to somehow "deploy" the project to the laptop, or is that just if you are running it on the robot?

Correct, just run it from the command prompt. No need to deploy, you're basically running the same executable you run when you click the GRIP icon when running GRIP normally, just from a command prompt instead.

Originally Posted by Jdkmotorhead

Ok, so I just tried it on my personal laptop, and it is working with the OutlineViewer in server mode, and the host set as localhost on both the server and GRIP. I don't see how this is any different from how I was testing it on the robot, with the addresses both set at roborio-5102-frc.local, and OutlineViewer in client mode...

That's right, it shouldn't be any different. Thus the questions about pinging, running from console window to see error messages, etc.

[Jdkmotorhead]

Ok, I'll try these troubleshooting steps next time I am at robotics, and post the results.

[Jdkmotorhead]

I just tried it, and I'm not able to ping roborio-5102-frc.local from either the DS laptop or my personal laptop. The DS laptop has the firewall disabled, and the IP and DNS both set to auto. I even tried reprogramming the radio, but it still won't work. Bonjour is running in the background too, so it shouldn't be a problem with resolving the address. Are there any other troubleshooting steps that I can try for getting the mDNS to work?

[1024Programming]

Originally Posted by Peter Johnson

Correct, just run it from the command prompt. No need to deploy, you're basically running the same executable you run when you click the GRIP icon when running GRIP normally, just from a command prompt instead.



That's right, it shouldn't be any different. Thus the questions about pinging, running from console window to see error messages, etc.

What command would we run in the command promt to open grip and the project file that we want. Currently, when we set the .grip file to open as grip executable, the save does not open into the grip window and it is like it just opens grip.

[Peter Johnson]

Originally Posted by Jdkmotorhead

I just tried it, and I'm not able to ping roborio-5102-frc.local from either the DS laptop or my personal laptop. The DS laptop has the firewall disabled, and the IP and DNS both set to auto. I even tried reprogramming the radio, but it still won't work. Bonjour is running in the background too, so it shouldn't be a problem with resolving the address. Are there any other troubleshooting steps that I can try for getting the mDNS to work?

The Driver Station (DS) software can see the robot? What team number are you setting in the settings tab of the DS? What versions are shown under "Versions" on the diagnostics tab of the DS? If pinging roborio-5102.local works, you need to update your roboRio image to this year's. Another thing to try would be to ping "roborio-5102-frc.lan" instead.

[Peter Johnson]

Originally Posted by 1024Programming

What command would we run in the command promt to open grip and the project file that we want. Currently, when we set the .grip file to open as grip executable, the save does not open into the grip window and it is like it just opens grip.

See https://github.com/WPIRoboticsProjects/GRIP/issues/492

[ThomasClark]

Originally Posted by 1024Programming

What command would we run in the command promt to open grip and the project file that we want. Currently, when we set the .grip file to open as grip executable, the save does not open into the grip window and it is like it just opens grip.

The latest release of GRIP doesn't support opening a file immediately when the program starts up, but I actually have a pull request right now that will probably make that work.

A consequence of this is that GRIP can be started from a shell script, so you could potentially have the DS computer open GRIP with a certain project as soon as you log in.