LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

R64 Camera Link

Hi,
I have a R64 Camera Link image acquisition board from Bitflow and a camera  Dalsa 1M30 Pantera. I have the labview drivers and the example .vi programs from Bitflow website. When i am trying to acquire images in the trigger mode i get the following error
"R64 board does not support triggered acquisition"
Which is not true since this camera supports external trigger mode and works with other programs than labview.
Do you know why i get this problem?
Thanks,
Christos


0 Kudos
Message 1 of 10
(4,580 Views)
This error most likely originated in the driver you are using (supplied by Bitflow) to interface with LabVIEW.  It may be a limitation of their driver interface with LabVIEW, but I am not certain about the limitations of the Bitflow LabVIEW driver for their cards.  Where you are using a 3rd party driver, it may be a good idea to also contact Bitflow.  Did the error have a number along with the text?
S. Arves S.
National Instruments
Applications Engineer
0 Kudos
Message 2 of 10
(4,554 Views)
Hi,
Thank for your response,
Bitflow made a new SDK version, 4.5 and the error i had before does not appear anymore. However, after following their instructrions of installing the new 3rd party drivers in
labview 7.1/vi.lib/addons/..... and trying to use their examples i get an error from labview (5001, Error Opening Board) Even when i make my own simplest vi and just include in it the subvi open board, it tells me the same think. I am sure there is no hardware problem since the board and camera are working with bitflow interface called "Ciview.exe"
Thank you,
Christos


0 Kudos
Message 3 of 10
(4,549 Views)
Christos,

It sounds like there is a problem with the linking between LabVIEW and Bitflow's driver if the card is working properly with their test software and not with LabVIEW.  This MIGHT be resolved by the following procedure:

1. Uninstall their driver
2. Shutdown the computer and physically remove the frame grabber
3. Re install their driver
4. Shutdown the computer and physically install the frame grabber.

Unfortunately we do not have access to the software or hardware from 3rd parties, so you might be best off contacting Bitflow for troubleshooting the installation problems with their driver.

-Arves
S. Arves S.
National Instruments
Applications Engineer
0 Kudos
Message 4 of 10
(4,545 Views)
Hi,
I followed your advice and it worked, Thanks!!!
I have a question about camera control from labview. As mentioned before i am using the R64 Camera Link bitflow board and the 1M30 Pantera camera by Dalsa.
The control of the camera is basically done through the camera link board via a virtual port. When i am using a program that is made by bitflow and looks like the window hyperterminal program the camera receives the commands. I am trying to do the same with labview but the problem since the camera is not connected on an actual port of the computer but through the framegrabber, i don't know which is the correct port to send the commands. Does labview can write to a virtual port?
Thanks,
Christos

0 Kudos
Message 5 of 10
(4,531 Views)
Hi Christos,

I'm glad to hear that it worked!

If you are able to send and recieve commands to the card using Windows Hyperterminal then you should be able to communicate with the card from LabVIEW using VISA.  But if you cannot communicate through Windows Hyperterminal it is probably safe to say that you will be unable to communicate with the camera directly from LabVIEW.  Also, Bitflow may provide some way of interfacing with the camera settings through LabVIEW though through their driver.

-Arves
S. Arves S.
National Instruments
Applications Engineer
0 Kudos
Message 6 of 10
(4,526 Views)
Hi,
I am trying to use labview to acquire images, as i ve mentioned before i am using a Dalsa 1M30 Pantera camera and Bitflow R64 camera link board. I have all the drivers installed and is working ok. The problem is that when using a timed loop for acquisition i can't go more than 12-15 fps (frames per second). The camera is supposed to acquire images at 30 fps and it does when using other softwares like image warp or the one that bitflow made for testing purposes, it acquires and displays live 30fps.
I am attaching u a picture that includes the timed loop with the acquisition part. Do u suggest any way to increase the speed and make labview able to go 30fps?
Than you,
Christos
 
0 Kudos
Message 7 of 10
(4,477 Views)
Christos,

Generally with a software timed loop, such as the one you are using in the example code you sent, you are limited by the amount of time it takes to process the loop.  For acquisitions above 15 fps, we recommend using a grab acquisition, which sets up a buffer for the camera to write to in a hardware timed loop.  As frames are written to the buffer, the software requests frames as quickly as possible.  While the hardware can supply frames at speeds of 30 frames per second and beyond, it may not be possible for your software to acquire at that rate and some frames will be lost.  Therefore, grabs are useful for high speed acquisitions where processing on each image is not necessary.  In the case when processing is necessary on every image, we recommend using a ring acquisition which sets up multiple buffers for the hardware to write to and read from.  Rings can be configured so continuous acquisition and processing of every image is possible.

There are shipping examples for both of these types of acquisition that come with the NI-IMAQ driver.  I would assume that Bitflow would provide similar examples of how to use their driver, but if not, it will be necessary to contact them for help with creating these types of acquisitions.

As for your code, I can see a few ways to improve performance.

1.  Creating images can be time intensive and may not be necessary in your case.  If it is, I would recommend creating them outside of the loop
2.  Same thing for copying them.
3.  A timed loop is not necessary because you are trying to go as quickly as possible.  I would recommend using a standard while loop.  While loops will run as quickly as possible while still performing every function within the loop.
5.  In general it is best to perform all processor intensive operations outside of a time critical loop.

S. Arves S.
National Instruments
Applications Engineer
0 Kudos
Message 8 of 10
(4,460 Views)

Christos... did you ever find a way to make your LabVIEW application talk to your CameraLink camera using the BitFlow device you mentioned?  I'm currently looking to see if anyone has developed a CameraLink LabVIEW driver base to be able to use 3rd party framegrabbers within LabVIEW to talk to CameraLink cameras using the CL serial port.  Please advise.  Thanks.

-J.C..

-----
Juan Carlos Flores
ArchonWest Technologies, Inc.
http://www.archonwest.com
0 Kudos
Message 9 of 10
(4,207 Views)
Hi, i managed to use Labview to fully control the camera through the Ni1429 framegrabber.
Thanks,
Christos
0 Kudos
Message 10 of 10
(4,198 Views)