Quote:
Originally Posted by vScourge
Where are you testing for the output from the RPi? In the robot code running on the roboRIO?
How is your RPi connected to the roboRIO? Are they both connected to the radio with ethernet cables, for instance?
If so, have you verified the RPi is connected to the roboRIO over the local network? You should be able to SSH into either device and ping the other successfully.
If that's not working then the NetworkTables client on the RPi will not be able to connect to the server on the roboRIO.
|
We are running the NetworkTables successfully. We have the rpi connected to a router that the roboRio is also connected to. We have input a test line into the NetworkTables and it showed up in our drivers station. The problem lies with the grip code. We can ping the roboRio from the pi and we can ping the pi from the roboRio. We just recently changed the values in our hsl filter and generated the code and it no longer works. We then changed the values manually in the working grip file and it worked. So the code in the GRIP program works fine but when it is generated and transferred to the pi, it does not produce any contours. If we edit the code on the pi and change the hsl filter to something with a much wider range, it works fine and outputs a bunch of contours in networktables. So something between GRIP on our computer and GRIP/OpenCV on the pi is inconsistent. We aren't sure what is going on.