VBAI Balser Ace Continuous Image Acquisition

We are running VBAI on a fast PC through an Intel Pro/1000 port and jumbo frame GigE switch to a large number of Basler Ace GigE cameras.
Two of the cameras are inspecting a rotating part. They both have hardware encoder triggers wired to their input lines.
In order to capture a sequence of 9 images, we are using the continuous every image acquisiont mode with buffers set to the max of 10.
We assume that in this continuous mode these cameras will broadcast frames, nonstop, to the PC, consuming network bandwidth even for the gaps between successive inspections.
In order to conserve network bandwidth, should we turn continuous mode off after we have captured 9 frames by putting the camera in shaphot mode with a read/write camera parameters command? Or is there a way that we can use the Number of Frames to have it automatically stop after 9 images?
The Basler users manual describes a number of low level Pylon SDK commands to control starting and stopping acquisition, but those are obviously not available from VBAI.
Thanks,
Nelson

I tried using the camera's attributes for "Acquisition Mode" set to Single Frame and the "Acquisition Frame Count" set to 9, but it looks like the frame count only applies if the camera supports a "MultiFrame Acquisition Mode" and my Ace did not, so I don't think there's a good way to do it using publicly available camera attributes.You could do as you describe and change the cameras attributes so it's no longer continuous once you get the images you need. Another option would be to gate your encoder signal so the camera is only triggered when you want it to be (not sure how easy/feasible this is, but this would be the cleanest in SW side since you know every image is a valid one and you don't need to worry about discarding images). Another option is to throttle the camera bandwidth so it can't send data as quickly and doesn't take as much of the GigE bandwidth, and you can even use the "Frame Transmission Delay" attribute under Transport Layer to offset the two cameras so they aren't sending their images at the same time.
Hope this helps,
Brad

Similar Messages

IMAQ-continuous image acquisition for VB

C:\Program Files\National Instruments\NI-IMAQ\Sample\MSVB.NET\Getting Started
Configure()
CWIMAQ1.Start()
CWIMAQViewer1.Attach(CWIMAQ1.Images.Item(1)) <--------I do not understand
Can teach me
And, how to acquire the single image under the continuous state.

Burki,
Are you trying to save the continuous images as a movie? This is not supported in VBAI, however if you wish to snap continuous frames individually you can try editing your inspection state diagram to repeat your current inspection and transition to the stop step only after your current inspection has been performed a set number of times.
Regards,
Isaac S.
Applications Engineer
National Instruments

Image acquisition not functioning after upgrading computer

Hi all,
I've run into a bit of a snag with our LabVIEW program. This program was written by someone that no longer works at my company and his VI scripts and installer do not exist, at least no where that we can locate. We've migrated the executable as well as the LabVIEW runtime environment over to a new Windows 7 PC (the original computer was running Windows XP). The program loads as it should but when it comes to the image acquisition within the program, the camera image is garbled and basically useless.
Using NI MAX, I am able to detect the camera and I can set it to the settings from the original PC but the image is even scrambled inside NI MAX. The camera in question is an ATV Oscar F810C which is detected as such by NI MAX. I've updated the Vision runtime to the February 2014 build available on NI.com (about a 2GB download). Here are some screenshots of the original PC's settings in NI MAX:
In reality, the image in NI MAX should look like this:
On the new system with the same settings it looks like this:
And when running the program on Windows 7 it looks like this:
If I change the Video Mode to one of the lower res ones, such as the first greyscale 1024 x 768 option, the image stops being scrambled inside NI MAX and I'm able to see the image properly. However, the image acqusition inside the program still does the same thing. Without having any information on the contents of the program or access to the original files, it would appear to be some kind of driver issue since the setup works fine on the old system.
Any ideas on what may be the issue?

billko wrote:
It may be that you have to download a WIn7 driver for the camera. Dll(s) might be incompatible.
Sorry, I did not see that that was one of the first things you did.
Bill
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.

Hardware digital trigger to start stop continuous analog acquisition

Hi I have seen the following example to use digital trigger to start and stop for finite number of samples. The example names is (DigitalStartandStopTrigger.vi)
in this example Reference Digital edge is used to stop acquisition but if I change to continuous then Reference Digital edge stops and show an errir. Could you please let me know how can I use hardware digital trigger to start stop continuous analog acquisition. An example would be really great
many thanks

HI tintin_99,
The way that example works (by modifying the read position of the buffer) essentially performs the same operation that the continuous samples mode does. That is to say, it is already a continuous acquisition.
The article below explains this in more detail, and the reasoning behind specifying buffer size manually and other tricks used. You may have already visited it in order to get the example VI, in which case it may be worth another read over.
http://digital.ni.com/public.nsf/allkb/BA775B0E445BFA79482571FE0032CCEB
Kind Regards,

Why my image acquisition pci 1409 board could not be detected by matlab image acquisition toolbox?

i have a National Instruments PCI-1409 image acquisition board that works very well
with the software provided by National Instruments, whereas it could
not be detected by matlab image acquisition toolbox when the command
"imaqhwinfo" was executed. I don't know why. the system is XP and
DirectX9.
any of your advice will be greatly appreciated.
thanks
yours sincerely
Jing
[email protected]

Is your matlab image acquisition toolbox DirectX based? If so, NI frame grabber will not work for your matlab image acquisition toolbox because it does not provide WDM or VFW drivers.
Irene He
[email protected]
www.hytekautomation.com

Multi channel continuous DAQ acquisition

Complete newbie question here. First time using Labview so I apologize for asking this question: Is it possible to have multi channel contiuous acquisition? If so, does this have to go through a circular buffer to prevent tying up all the computer memory? Can you vary the scan and read rates for each channel? Last question: If it is possible to do all of the above....how do you do it? I've attached a .pdf file with screen shots of my front panel and block diagram....it's extremely crude just trying to get some basic concepts down. Also if anyone can recommend some good books on actually doing the wiring and conditions of the various elements, I'd be extremely grateful. Currently I have "Labview for Everyone".
Attachments:
DAQ.pdf ‏33 KB

Hello,
It is possible to have a multi channel continuous acquisition and it does use a circular buffer. Please check out the Continuous Waveform Acquisition Tutorial for more information about how this is done. With our DAQ devices you can use different sampling frequencies as long as they have a common divisor and the sampling rates remain within the device specifications. There is an example of that called Multi-Rate Continuous Analog Input.
The example finder is always a useful place to look for ideas on how to make a VI. In LabVIEW, go to Help->Find Examples and you will open up a browser that will allow you to look through many examples. You can also check out the LabVIEW Zone Learning Center where you can find a book listing under the fundamentals section.
Hope this helps!
Laura F.

Is vision development module in labview 8.6. sufficient for real-time image acquisition and analysis using a webcam

Hi,
I'm new to labview and trying to develop an eye-tracker using labview 8.6. It has the vision development module and i was wondering if this was sufficient for real-time image acquisition and processing or would i be needing any other software tools.
Solved!
Go to Solution.

Hello, certainly it is possible and sufficient for real-time tracking!
About eye tracking - if you need an example, you can find the code here:
https://decibel.ni.com/content/blogs/kl3m3n/2013/10/08/real-time-face-and-eye-detection-in-labview-u...
The code uses OpenCV functionalities along with the LabView UI (and some other functions like overlay).
Hope this helps a bit.
Best regards,
K
https://decibel.ni.com/content/blogs/kl3m3n
"Kudos: Users may give one another Kudos on the forums for posts that they found particularly helpful or insightful."

Continuous image scroll

I have made a continuous image scroll, but as it it loops it
messes up my spacing between my images. I am trying to scroll about
25 images each of which are are their own movie clip. I have this
code which works well for five images now I want to ad about 20
more.
onClipEvent(enterFrame) { // movie clip enterframe event
_x=_x+2; // change position for each enterframe event
if(_x>=540){ // condition
_x=-360; // if condition true movie clip jumps to starting
postion.
The tutorial I am using states this:
"if(_x>=540)" value depends on the no. of movie clips.,
but I am confused as to where the 540 comes from? is it the length
of all of the movie clips put together?
I am confused as to how to alter this so it works with around
25 images any help would be greatly appreciated!
Thanks so much!
AZ

Assuming that this clip event is attached to the MC
containing the images, you could use the _width value of the clip
to determine the start and ending point of the movement.

VBAI Interface - Get inspection Image -- Image Dest

I have a complete Vision algorithm build in Vision Builder AI and programmed a VI in Labview which started the Algorithm and uses the results to compute. This works fine. Connection between Labview and VBAI is OK and results are nicely updated. Now I'd like to show the image from VBAI into my Labview GUI by using the "VBAI Interface - Get Inspection Image" VI from the Vision Builder AI toolkit. Whatever I try to connect to the "Image Dest" input of the VI I'm not able to let it run and give an image to show. See attached screenshot for details.
- What type of input do I need to link to get this VI working?
- Where can I find more detailed info than in the Context Help about all these VBAI toolkit VI's?
Solved!
Go to Solution.
Attachments:
ImageDest.JPG ‏65 KB

You need to use IMAQ Create to create an image. You can see an example of this in the Vision Builder AI folder under API Examples\LabVIEW Examples\LabVIEW API Example (Local).vi
Hope this helps,
Brad

Real-time PID control and continuous buffered acquisition. Does it work together?

I use the "real-time PID control.vi" that acquires single AI point and generate single AO point in every "while loop" iteration to control a piezo actuator motion. Simultaneously I need to do (in another loop) a continuous buffered acquisition of another two AI channels (in the same rate as first AI channel).
It does not work together.
Does anybody know how to fix it?
Platform: LabVIEW 6.1
Board: PCI-6024E

Hi,
I would try to avoid the idea of using a separate loop since the PID
loop is a continuous acquisition and will require un-interrupted access
to the Analog DAQ system of the board. The last thing it needs is for
you to attempt to start other AI functions at the same time.
Configure your AI in the PID loop to read in multiple channels (Just add
some more channels to the Input Channels Control. Separate the data as
it comes out of the AI single Scan function using Index Array or other
Array functions into that needed for the PID and that needed for your
other data (the example is already doing this to make sure it only gets
1 channel of data into the PID). If you don't need to sample all your
channels of data all the time you can throw some data away as
required.
Obviously your other channels are now arriving one sample at a time so
if you might need to build an array, insert into an array or use Auto
Index on the loop if you are data logging.
Regards,
Dave R.
varmih wrote:
> I use the "real-time PID control.vi" that acquires single AI point and
> generate single AO point in every "while loop" iteration to control a
> piezo actuator motion. Simultaneously I need to do (in another loop) a
> continuous buffered acquisition of another two AI channels (in the
> same rate as first AI channel).
> It does not work together.
> Does anybody know how to fix it?
>
> Platform: LabVIEW 6.1
> Board: PCI-6024E

Keep all overlay information during image acquisition when using the base IMAQ package

I have made an X control from the IMAQ image display control that has the ability to overlay points and lines on an image but when I put my X control into my image acquisition loop the overlay information disappears with every new image I acquire.
How can I keep the overlay in place and just update the control with the new image and not overwrite the overlay data? I have tried the merge overlay function but this does not seem to work.
Thanks.
Solved!
Go to Solution.

Overlays normally are erased when you acquire a new image. You could create the overlays on a separate image, then copy the overlays to each new image before you display it. The other option is to recreate the overlays for each new image.
Bruce
Bruce Ammons
Ammons Engineering

Express vi for image acquisition is missing

I am using labVIEW 2014. I am doing a project which is based on image acquisition and recognition. I installed both VDM and VAS tool kits. But i am still unable to locate the image acquisition express vi. Please help me with the same. I have also attached a screen shot of the same

yes, i have installed the imaqdx drivers. still i am having the same problem

Image acquisition using video capture card

I am developing an application for Single fiber fusion splicer...my application basically has to capture the picture from the splicer using a Video capture card...Is it possible to use IMAQ session to get the picture from the card,store it a file and display the same using labview??or is there any other suitable way instead of IMAQ???

Cyril,
A typical image acquisition system consists of the following
components:
Camera » Framegrabber board » Image Acquisition Software »
Image Processing Software
The software in this application is of course LabVIEW. The ease of integration of it with your
camera and framegrabber board is dependent on a number of variables and I
discuss that further in the rest of this post.
Camera
It looks like you already have a camera picked out, but I could not find
any information on the VHR-1000 on the internet. Who is the manufacturer? Can you provide a link to information
available about it online? NI does
not actually make cameras; we simply connect with third party
cameras. We have a list of the
various cameras that are tested and supported by our hardware available at
http://www.ni.com/cameras
Here are two more documents that will discuss camera options in more
detail:
Choosing A Camera
http://zone.ni.com/devzone/cda/tut/p/id/3087
Image Acquisition
http://zone.ni.com/devzone/cda/tut/p/id/2808
Framegrabber
board
The framegrabber board is what will be responsible for taking the signals
from your camera, either digital or analog, manipulating them
appropriately, and storing them in computer memory.
The framegrabber board you choose will largely depend on the camera you
choose and the interface it uses. (Interfaces are discussed in the Image
Acquistion document mentioned earlier)
It looks like you already have a Domino Maxi framegrabber board, which
LabVIEW may or may not be able to interface with. Could you please provide more
information and possibly a link to some info on this framegrabber board?
Choose NI Vision Hardware
http://www.ni.com/vision/hardware.htm
Image
Acquisition Software
The Image Acquisition software is the software responsible for bringing
images into the computer in conjunction with the framegrabber board or
IEEE-1394 bus. Depending on your
interface, you will need either NI-IMAQ (framegrabber) or NI-IMAQdx
(IEEE-1394).
Image
Processing Software
For image processing in LabVIEW, you will need the Vision Development
Module. It’s product page can be
found here:
Vision Development Module
http://www.ni.com/vision/vdm.htm
This software will enable you to do any type of image processing that your
application may require.
Those are the basic components of an image acquisition
system. Hopefully you will be able to
follow those links and gain a better understanding of what exactly you need to
be able to setup the kind of system you are looking for. This presentation provides a great deal of
general information and may be able to answer some more specific questions you
have:
Imaging Fundamentals
http://www.ni.com/vision/vdm.htm
It also discusses camera and lens selection with respect to
the image size and detail that you need.
Please let us know if you have any further questions related to this.
Regards,
Luke H

5122 and continuous triggered acquisition

I have a PCI-1522 and I want to do a continuous synchronous acquisition and have tried a number of things in NI-SCOPE without success. The signal I want to acquire is triggered (or to be more technically correct is synchronous with a second external signal) at 10 or 20 kHz and I want to sample at about 20 MS/s. Setting up the ext trigger is fairly straightforward if you put the initiate and fetch within a while loop. But then you have to loop on each trigger every 100 us (which the software is not fast enough to do even without the decimated processing I want to do) or acquire a larger chunk of data. This latter approach essentially initiates on one trigger pulse but acquires a large number (2M) of samples at 20 MS/s and therefore is subject to jitter if the samples acquired aren't exactly right. (I adjusted the sample size to correct within one sample and there is still persistent jitter so without triggering the accuracy required is less than one sample.) Bottom line is you aren't synchronous with either approach. With the fetch forever example, you move the initiate outside of the while loop which is great. But you have to use a software trigger in order to get it to work. All of the possible solutions essentially boil down to software triggering. I suffer either from jitter or drift.
I thought about using the video ref triggering schemes but then I have to configure my signal to fit into the pre-defined video formats which may not be possible. I haven't thought too much about a DAQmx solution. Are there any examples or solutions of a hardware-synchronous, continuous acquisition in NI-SCOPE or DAQmx?

Hi Dan,
You might want to take a look at the niScope EX Multi Record Fetch More Than Available Memory.vi shipping example. With this VI you can set up a multirecord acquisition and fetch records as they are being acquired. This allows you to acquire more records than will fit in the onboard memory. Currently, there are limitations in the driver which limit you to fetching about 2,000 to 3,000 records per second, so you will not be able to keep up with your 10 to 20 kHz trigger signal indefinitely. However, we are currently working on fetching optimizations which should bring this number up to the 10 kHz range in the future. We hope to release these optimizations in Q1 of 2007.
I hope this helps.
Regards,
Sean Close

Euresys Picolo image acquisition and LabVIEW

Hi all,
Unfortunately I have bee asked to use a Euresys piccolo image acquisition card in LabVIEW. I my case I only need to display the image on / on top of a LabVIEW front panel. Yes – I know it would have been much better to use an NI card but sometimes other people........
Anyway my question is - has anyone out there managed a reliable interface to the piccolo dll yet? I’ve been looking at the ActiveX interface but it looks like an exceptionally tricky job. I see there are few previous discussions that will be of help should I have to start from a blank VI.
Any advice appreciated,
-Martin
Certified LabVIEW Architect

Hi Martin
I have had a look for you this afternoon to see if I can find an example for you as to how to communicate to you Euresys frame grabber in LabVIEW but an example or driver is not available. It should though be possible to comunicate with your board using the manufacturers dll. You mentioned that you were aware of other forum posts that will be helpful in you starting to develope you code but I thought it might be helpfull to post some links below.
Forum posts:
Is it possible to use Euresys Picolo card with IMAQ vision and LabView?
activex help!!!
calling picolo.dll in Labview
Other Resources
Using External Code in LAbVIEW
Integrating External Code with the Import Shared Library Wizard
I hope this helps

VBAI Balser Ace Continuous Image Acquisition

Similar Messages

Maybe you are looking for