We are having a problem with the vision tracking code. After following the LabView rectangle tracking example’s directions for saving the VI into a new project, we have tried to run the project to see the camera image and debug the code. We are running the cRIO-II plugged into the DAP bridge, with all IP’s configured correctly. We can see the unprocessed image on the dashboard, but on the LabView screen we cannot see the images. Any help would be appreciated.
I’d check that to see if there are errors on the DS diagnostic tab. I’d check to see that it is enabled on the Robot Main panel, or otherwise the global is set somewhere in the code. If looking at a binary mask, be sure to set the palette to binary.
Greg McKaskle
Sorry, I can’t be of help. But we are needing an example, where did you find the LabView rectangle tracking example. Thanks!
I believe Help >> Find Examples will work pretty well, and the FRC/Vision folders are probably the right place to look.
Greg McKaskle
I have the same problem, and the built dashboard executable works properly processing images on my coding computer. However, when I move the built executable with the image processing to the Driverstation, there is only the live feed, and no image processing. I am wondering if this could be a problem with Labview not being installed on the other computer? I just have the driverstation installed on the driverstation computer.
I would check the Begin vi. There is a boolean that decides what IP to use to find your camera.
http://img3.imageshack.us/img3/9273/cameraipselect.jpg](http://imageshack.us/photo/my-images/3/cameraipselect.jpg/)
This very important based on the type of crio and setup!
Other than that. I would check the camera Ip to insure that it is set up correctly.
For simplicity’s sake, I just deleted all that boolean nonsense and entered our two camera’s IP’s manually. That might work for you if there’s an IP error.
The Ip addresses are correct, as the driverstation is still recieving all of the image data, along with being able to process it on our other computer. Our Dashboard has all of the image rectangle finding code in it, and works well on the coding computer. The issue appears to lie in the .dll’s of the NIvision, specifically, the calls to GetColorPlane and other functions like that. I already tried moving all the files I could manually, but I will later try to reinstall some of the vision software on that computer.
Ha, it was actually an extremely simple problem to fix. Unbeknownst to me, the Labview installer had an “install Driverstation Support” feature, which after installing on the Driverstation, made everything work.