| View previous topic :: View next topic |
| Author |
Message |
placa
Joined: 06 Aug 2008 Posts: 6 Location: NV
|
Posted: Wed Aug 06, 2008 11:05 am Post subject: Using labview 8.5 to acquire sequence of high speed images |
|
|
I am trying to use Labview 8.5 with the latest version of Vision and Bitflow Labview vi's (sdk 5.0 drivers) to capture and save image sequence (video) at 200 fps. We are using a roadrunner r3, CL board with a Pulnix tm-6740cl camera (200fps full frame). The computer is a newer Dell Optiplex running Windows XP.
I can get the example code to work but that only captures 1 image. I have tried to run a loop on the example vi like get frame and save each individual frame to an image, but the frame rate is too low.
It is not clear to me how to program a Labview vi to get 200 fps. I know that somehow the images need to be stored in a buffer on the system memory but I am not exactly sure how to do that and access them after the acquisition.
Any help would be greatly appreciated. Thanks. |
|
| Back to top |
|
 |
BFSupport
Joined: 09 Feb 2004 Posts: 300
|
Posted: Fri Aug 08, 2008 4:29 pm Post subject: |
|
|
| The LabView frame grabber interface is somewhat inefficient and probably can't support image acquisition at this frame rate. However, we have added a new VI to our LabView support which acquires images into a set of buffers behind the scenes automatically. Then from LabView you can access each image asynchronously. Download the multi-buffer example VIs, which are part of the LabView driver download available from our web site. These examples are brand new and we just uploaded them to our web site. |
|
| Back to top |
|
 |
placa
Joined: 06 Aug 2008 Posts: 6 Location: NV
|
Posted: Fri Aug 08, 2008 5:51 pm Post subject: |
|
|
Thank you for the updates. I have installed the new Labview drivers. I tried running the multi-buffer grab vi and it returns an error (5020) at the Bitflow wait for frame vi. I tried increasing the timeout time from 5 seconds (default) to 10 seconds and I still get the same error. I have stepped through the vi while running and it returns this error on the second iteration of the loop.
I know the camera and the board are working because I can run the fast get frame vi and get an image from the camera.
Is there any suggestions on why it is doing this?
Thank you again for the help. |
|
| Back to top |
|
 |
BFSupport
Joined: 09 Feb 2004 Posts: 300
|
Posted: Wed Aug 20, 2008 11:36 am Post subject: |
|
|
| We are not sure what is causing this problem. We have been able to duplicate this problem here and and working on a solution. We will post here when we have a fix. Also, if you would like to receive an email when we have a fix, send email to support @ bitflow.com referring to this thread. |
|
| Back to top |
|
 |
BFSupport
Joined: 09 Feb 2004 Posts: 300
|
Posted: Wed Aug 20, 2008 3:37 pm Post subject: |
|
|
| We think we have figured out what is causing this problem and we have a fix for you to try. Please send email to support @ bitflow.com, reference this thread, and we will send you a new LabView driver to test. |
|
| Back to top |
|
 |
placa
Joined: 06 Aug 2008 Posts: 6 Location: NV
|
Posted: Wed Feb 04, 2009 2:49 pm Post subject: |
|
|
| I have installed the new Labview driver that you sent me and I still get the same error (5020) at the wait for frame vi. Is there anything else that I can try to get the Multi-Buffer Grab vi to work? |
|
| Back to top |
|
 |
BFSupport
Joined: 09 Feb 2004 Posts: 300
|
Posted: Thu Feb 05, 2009 11:00 am Post subject: |
|
|
Do you have the full SDK install on your PC, or just the drivers? The way to tell is how you install the SDK. If you installed it with a serial number, then you have the full SDK. If you installed it with the serial number 0, then you have just installed the driver.
The reason I am asking is that we are interested in finding out if our BiFlow application works with your camera. BiFlow is only installed if you have the full version of the SDK. This is also a sequence capture program. If BiFlow does not work, then the problem is most likely related to the camera configuration file. If BiFlow works fine, the the problem is more related to the LabView drivers.
If you have only installed the drivers only version, let us know and we will figure out another solution. |
|
| Back to top |
|
 |
placa
Joined: 06 Aug 2008 Posts: 6 Location: NV
|
Posted: Thu Feb 05, 2009 12:03 pm Post subject: |
|
|
| I do not have the full version of SDK installed. Just the drivers are installed and the camera (Pulnix TM6740CL) works fine as seen in CiView. The Camera config file I am using is "Pulnix-TM-6740-E2-OE-FreeRun.rcl" |
|
| Back to top |
|
 |
BFSupport
Joined: 09 Feb 2004 Posts: 300
|
Posted: Thu Feb 05, 2009 6:52 pm Post subject: |
|
|
| We have just sent you an email with something to try. |
|
| Back to top |
|
 |
placa
Joined: 06 Aug 2008 Posts: 6 Location: NV
|
Posted: Fri Feb 06, 2009 1:32 pm Post subject: |
|
|
| I ran the application that you sent me and it acquires sequences of images without getting any errors. |
|
| Back to top |
|
 |
BFSupport
Joined: 09 Feb 2004 Posts: 300
|
Posted: Wed Feb 11, 2009 11:21 am Post subject: |
|
|
We assuming that you are still using the "Multi-Buffer Grab.vi" example for testing, is this correct?
Are you still getting the first frame, with a time-out on the second frame, as you were previously? Or are you seeing a different behavior with this latest version?
Here is another thing to try. Run the registry editor, navigate to the following key:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\BitFlow\RoadRunner
Under this key, create a new "String Value" give it the name "OldQTabMode" and give it data "1". Try your LabView test again. |
|
| Back to top |
|
 |
placa
Joined: 06 Aug 2008 Posts: 6 Location: NV
|
Posted: Fri Feb 13, 2009 1:08 pm Post subject: |
|
|
I am still using "Multi-Buffer Grab.vi" for example testing.
I created the registry key that you suggested to try and I still get the same time out as previously mentioned.
I haven't been able to get any frames. |
|
| Back to top |
|
 |
devil
Joined: 20 May 2010 Posts: 2
|
Posted: Fri Jun 18, 2010 10:26 pm Post subject: |
|
|
I also have the same problem,using LabView 8.6 and Bitflow sdk 5.0,when I use the Muti-Buffer Grab.vi ,The same error (error5020)occurs.Then I delete the "BF Wait4Frame",then the "Muti-Buffer Grab.vi" can run.But when I try to acquire the image , the flat Imager acquire the image ,but the Bitflow didn't get it.I could only see a black image.
I want to know if the problem have been solved or not.
My friends who use VC could get the image,but I could not(we use the same computer),I doubt the error occurs in the LabView. |
|
| Back to top |
|
 |
|