08-21-2011 01:42 PM
Hi guys.
I'm creating a small automated inspection project using vision builder 2010 and a daq USB 6008 and I've come across a problem.
First let me give a small overview of the project.
I've built a small conveyor in which the product I will be analyzing will be placed and moved along. At the centre of this conveyor I have a Microsoft HD Lifecam mounted vertically so as it has a full view of the below surface area of the conveyor in order to analyze the product when it is in view. There are three proximity sensors on the conveyor: 1 at the start to detect the presence of the product and start the conveyor, the 2nd at the midpoint of the conveyor to detect the product,stop the conveyor motor and start the vision acquisition process and finally the 3rd sensor to detect that the product has reached the end of the conveyor.
My main problem is this. In order to control the conveyor logic I am using a simple standard state machine in labview. My problem occurs when I come to the vision acquisition state. When the middle sensor detects the product it will move to the vision acquisition state, its at this point that I need the vision builder application to be triggered to start somehow with the USB 6008. Once it has finished the image processing I need it to send one more trigger back to the state machine and transition to the next state.
Is this type of interfacing between labview and Vision Builder possible with a USB 6008???.
Thanks to all who've read and hopefully someone will be able to help me out. 🙂
08-24-2011 09:51 AM
Hi Banjo B,
Are your LabVIEW and Vision Builder programs running on the same computer?
Your trigger source is the middle sensor which is read into your USB-6008. Correct?
Do you want your LabVIEW code or Vision Builder code to communicate to the USB-6008?
Your LabVIEW code and Vision Builder code could communicate using shared variables. You could get LabVIEW to read any triggers from the USB-6008 and then call your Vision Builder code.
You can also port you Vision Builder code straight into LabVIEW once you have developed it and then you can 'talk' to it directly as if it was a VI.
Have I understood you correctly? If so, would my 'solution' be suitable?
Post back.
08-24-2011 06:00 PM