Thread: Vision on the cRIO with OpenCV
View Single Post
  #9   Spotlight this post!  
Unread 27-09-2013, 16:58
protoserge's Avatar
protoserge protoserge is offline
CAD, machining, circuits, fun!
AKA: Some call me... Tim?
FRC #0365 (MOE) & former 836 Mentor)
Team Role: Mentor
  
Join Date: Jan 2012
Rookie Year: 2002
Location: Wilmington, DE
Posts: 754
protoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond reputeprotoserge has a reputation beyond repute
Re: Vision on the cRIO with OpenCV
Quote:
Originally Posted by ykarkason View Post
The problem with using the vision library for LabView is that our team is using java!
I understood that there are some C++ functions from that library wrapped for java use, but not all of them, and I wonder if it'd be possible for me to use the NI Vision Assistant and rewrite the code I get from there in java.
You're right. I have been reading so many vision threads lately that I got this one mixed up. I believe the LabVIEW WPI library is a variant of OpenCV, check on this for accuracy. What I was actually referring to was the algorithm for single image vision using the cRIO. The single image is relatively simple for the cRIO to handle, especially if you know what you are comparing the camera image to. If you want to go to a real-time algorithm, you will need to start looking into coprocessors.