Quote:
Can you clear up a few steps leading up to this.
1. When developing the Grip script where is the camera connected? PC/Rio USB/IP Web cam
2. On the PC what is the Camera Name? Cam0.1.2....
3. If USB what is the USB camera name when viewing the WebDashboard?
4. What is the Deploy address you are useing?
|
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
Quote:
|
I have never waited for the PC deploy and didn't know I would have an option to start the script on the Robot from the PC. I'll check that out.
|
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.