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

Similar Messages

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."

Two Simultaneous USB Camera Image Acquisition and Saving

Hello everyone,
Recently my friends and I have begun a project which requires the simultaneous acquisition of images from two independent USB cameras. Throughout our project research we have encountered many difficulties. The major problem appears to be how to successfully interface two USB cameras and properly save the image to a median for further processing down the road.
Our first attempted at this was with the USB IMAQ drivers. Unfortunately, to our surprise, it does not support two independent and simultaneous camera acquisitions. To combat this problem we implemented a crude loop of closing a camera reference, then opening the other, acquiring an image, then closing, etc... This did provide us with functionality but was very inefficient, resulting insufficient acquisition speeds.
Afterwards we began looking at other ways of capturing and writing the image, which are listed below.
Various Acquisition Interfaces / Strategies
USB IMAQ Driver - USB interfacing kit available for public download, (not officially supported by NI) zone.ni.com/devzone/cda/epd/p/id/5030
Status - Abandoned because of the lack of dual web camera support
Avicap32.dll - Windows 32 DLL responsible for all web camera communication, and other media devices.
Status - Currently acquired two streams of video on the front panel but with no way of saving the images
Directx - The core Windows technology that drives high-speed multimedia on a PC.
Status - Currently researching.
.NET - Microsoft .NET framework, possibly a valid interface to a video stream.
Status - No development until further progress.
We are still currently developing the Avicap32.dll code but the major bottleneck is the learning curve on the property nodes, library calling nodes, .NET and other references. So far it’s been a tedious effort of trying to understand example code and piece them together. As a former programmer of C I know this is not the proper way of writing code web I can’t seem to grasp how these functions work. (Property nodes, library calling nodes, .NET and other references). Learning this may allow us the knowledge to code a proper system. Does anyone know any good tutorials or learning material for such functions? So far my research has come up empty handed.
We are currently working with these interfaces and other reference examples on the NI site. Unfortunately we cannot seem to properly integrate the code for our system. Does anyone know if this setup is even possible? Also, if anyone has any experience with similar systems and can offer advice, code snippets, or any other assistance it would be greatly appreciated.
Our current projects will be posted below if you have any suggestions. (More will be added when I get to my desktop tomorrow)
Two Camera Avicap32.dll - Currently stuck on how to save the image, various tweaks have gotten us stuck at this point ( will have another Avicap32.dll implementation posted tomorrow)
USB Capture Example - This USB capture VI was an example that immediate had problems. We used it as a baseline for crude open-close camera image grabbing system. (Will also be posted tomorrow)
Thanks for any help, it's much appreciated.
Taylor S. Amarel
Thanks,
Taylor S. Amarel
Learning is living.
Co-Founder and CEO of http://3dprintingmodel.com/
"If we did all the things we are capable of, we would literally astound ourselves."
-Thomas Edison
Attachments:
Two Camera Avicap32.dll.zip ‏84 KB
USB Capture Example.zip ‏17 KB

Thanks for the information but that's not exactly what I'm looking for. I've been to that URL and read the information before. I don't mean to disparage you help but I'm looking for ways that I can successfully implement a functional system, not information on an unfunctional method. Maybe I was unclear before, I'm looking for any advice, knowledge or help on how to make this system properly work.
Thanks, have a great day.
Taylor S. Amarel
Learning is living.
Co-Founder and CEO of http://3dprintingmodel.com/
"If we did all the things we are capable of, we would literally astound ourselves."
-Thomas Edison

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

I am using PCI-6033E IO card and i would like to send 5 volts (high logic ) to the trigger box. the trigger box will trigger the frame grabber card, that i am using for image acquisition.

i am using PCI-6033E IO card and i would like to send 5 volts (high logic ) to the trigger box. the trigger box will trigger the frame grabber card, that i am using for image acquisition.

Hello;
The first thing you need to figure out is the shape of the trigger pulse needed.
In case you just need a logic high TTL pulse, you can use one of the digital lines of your DAQ device.
In case you need a pulse train (multiple trigger pulses), you will need to configure one of the general purpose counters to accomplish that task.
You can find examples in both Labview and NI-DAQ showing how to program your DAQ board to accomplish both approaches.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

Do I need LabVIEW RT for a simple 10objects/sec image acquisition/processing?

I have a pretty simple application. A photoelectric sensor detects an object and triggers the image acquisition. The image of this object is then processed (a few morphological functions and particle analysis) and results are displayed in a table before a new image is acquired. The application also includes indicators for high/low limit, statistical calculations and a report generation. 7 to 10 particles per second are analyzed. Being still in the design phase, I use LabVIEW 7 Express. Do you think the LabVIEW Real-Time Module is necessary for my application?
Thank you very much for your help.
Bernd

Hello Bernd,
LabVIEW Real-Time is used to acquire robust and deterministic operation. It's basically a stripped down operating system that runs your application, and that's it. There's no additional software running in your background that can clog up the processing queue and lose the exact execution that your application requires.
Yes, you could use Real-Time for your application, but I don't think it would be necessary. If anything, you may be limited by the hardware that you use and whether or not it will be able to acquire as many images as you would like in that short period of time.
National Instruments does have a real-time Compact Vision System which you may not to inquiry further about. I would strongly suggest posting a very simi
lar question to the Vision discussion forum to see what developers in that area think about your application. The numbers that you mention alone may light up a few light bulbs as to which LabVIEW target is generally used to reach the goal you desire.
Hope this helps.
Jared

I w'd like to know if LabVIEW 6.0 Application Builder includes the daqdrv (for data acquisition) and serpdrv (for serial communication) support files by default.

Building an application to communicate to a device by serial port

Hi velou
The LabVIEW 6i Application Builder no longer requires daqdrv. Regardless of your Application Builder and LabVIEW version, you must always install the appropriate driver files on the target machine. For example, if your application communicates with a DAQ board and a GPIB board, then you must install NI-DAQ and NI-488.2 on your target machine. If you are using the VISA VI's for serial communication, than you have to install NI-VISA . If you are using the "old" serial VI's, than you have to include serpdrv separately.
Luca P.
Regards,
Luca

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.

Missing ID file for 1049 image card and JAI-M10bx camera?

IMAQ examples have code for JAI-M10 camera.
i got a JAI-M10/bx model.
ni-1409 image card.
However my PC/win200 with Labview-7& Imaq don't offer
an *.ICD file to setup that camera.
i am trying to setup a dual camera system with two
1409 cards.
where/how can i get the ICD file?
thanks
larryb

larryb,
I noticed in your post that you mention you have an analog image acquisition board (PCI-1409) and that you are looking for an .ICD file for your camera. ICD files are used only for digital cameras, there are equivalent files called .IID files for analog cameras that work in much the same way. There is however one big difference between analog and digital cameras. Digital cameras are usually custom designed, and as a result require a custom configuration file (.ICD file). Analog cameras generally adhere to a standard (NTSC, PAL, RS170, CCIR) and as a result there is no need to create a custom file for each camera, instead, you can just use one of the generic .IID files that come preinstalled with the NI-IMAQ driver.
I took a look at JAI's website, an
d it appears that the model of camera that you are using (JAI-M10BX) comes in two formats, CCIR and RS170 (also called EIA). Your documentation should clarify which format you are using. To set your camera to the appropriate format, open Measurement and Automation Explorer (MAX) and click on the channel of your 1409 board that your camera is hooked to. Right-click on this channel and select Camera » CCIR or Camera » rs170 depending on which format your camera uses. This should get your camera working properly.
Regards,
Jed R.
Applications Engineer
National Instruments

Differences in CIN management between Labview 5.0 and Labview 7.1 ?

Hi,
I'm using a VI on a two photon microscope. It steers the laser beam in the sample (quite the same way as a TV scan, scanning a fast line on the X axis, then moving the line down) controlling two mirrors by the PCI-MIO-16E-4 Multifunctions card on traditional DAQ and at the same time it serves as the acquitision through a non-NI DSP Multifunction-board with on-board buffers and hight data throughput (70 Mb/s).
It is this part of the program which gives us strong headaches since we have upgraded to a new PC.
On the old machine we used Win2k and Labview 5.0; on the new machine we planned to use WinXP Pro and Labview 7.1.
The acquisition part of the VI uses 2 CINs. One is used to configure the FPGA on the Multifunctions board at initialization.
The second CIN reads he buffers received from the board and puts them into the shape of an image.
Now since we tried in WinXP Pro and Labview 7.1, we get some kind of weird bugs. Either there is a big problem concerning the synchronization of the mirros with the acquisition or with the image reconstruction. We have already tried :
1. Putting everything back into the old machine to verify there has not been any damage to the boards. OK
2. Using the boards in the new machine but with Win2000 and Labiew 5.0, just to be sure that there are no conflicting elements in the hardware. OK
As we wanted to check everything slowly but surely we then installed LV 7.1 on the new machine but still with Win2k. And here the problem appears !
First we thought the drivers for the Multifunctions board (ATEME Adr128C6x) were not compatible with WinXP Pro, so at this point we were quite surprised to notice the problem seems to be caused by the upgrade from LV 5.0 to 7.1 !
Now, finally my question is : Are there any major changes in how Labview handles CINs between LV5.0 and 7.1 ?
Can the problem be caused by the

So, no answer,...
Anyhow, we found the problem on our own. For anyone else experiencing this kind of behaviour :
The problem did not have anything to do with our CINs, nor with XP.
In fact, we have noticed that the Analog Ground the Digital Ground had to be connected. For some kind of reason in LabView 5.0 this did not introduce the problem. But in Labview 7.1 the sync, because of a somewhat unstable Ground, it caused complete disfunctionment. We don't know why but, hey, the problem is gone.

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

Differences in CIN management between Labview 5.0 and Labview 7.1 ?

Hi,
I'm using a VI on a two photon microscope. It steers the laser beam in the sample (quite the same way as a TV scan, scanning a fast line on the X axis, then moving the line down) controlling two mirrors by the PCI-MIO-16E-4 Multifunctions card on traditional DAQ and at the same time it serves as the acquitision through a non-NI DSP Multifunction-board with on-board buffers and hight data throughput (70 Mb/s).
It is this part of the program which gives us strong headaches since we have upgraded to a new PC.
On the old machine we used Win2k and Labview 5.0; on the new machine we planned to use WinXP Pro and Labview 7.1.
The acquisition part of the VI uses 2 CINs. One is used to configure the FPGA on the Multifunctions board at initialization.
The second CIN reads he buffers received from the board and puts them into the shape of an image.
Now since we tried in WinXP Pro and Labview 7.1, we get some kind of weird bugs. Either there is a big problem concerning the synchronization of the mirros with the acquisition or with the image reconstruction. We have already tried :
1. Putting everything back into the old machine to verify there has not been any damage to the boards. OK
2. Using the boards in the new machine but with Win2000 and Labiew 5.0, just to be sure that there are no conflicting elements in the hardware. OK
As we wanted to check everything slowly but surely we then installed LV 7.1 on the new machine but still with Win2k. And here the problem appears !
First we thought the drivers for the Multifunctions board (ATEME Adr128C6x) were not compatible with WinXP Pro, so at this point we were quite surprised to notice the problem seems to be caused by the upgrade from LV 5.0 to 7.1 !
Now, finally my question is : Are there any major changes in how Labview handles CINs between LV5.0 and 7.1 ?
Can the problem be caused by the traditional DAQ

So, no answer,...
Anyhow, we found the problem on our own. For anyone else experiencing this kind of behaviour :
The problem did not have anything to do with our CINs, nor with XP.
In fact, we have noticed that the Analog Ground the Digital Ground had to be connected. For some kind of reason in LabView 5.0 this did not introduce the problem. But in Labview 7.1 the sync, because of a somewhat unstable Ground, it caused complete disfunctionment. We don't know why but, hey, the problem is gone.

Image Processing and machine vision don't appear in Function Palette

Hi,
I have problem and I can't solve it
Image Processing and machine vision don't appear in Function Palette, Although I set up NI imaq and NI Vision Acquisition Why??
Anyone can help me?
Solved!
Go to Solution.

If the image is already a Grayscale U8 image you would just have to save it to a bitmap file using the IMAQ WriteFile VI. If not, use the IMAQ Cast Image VI to convert it to a Grayscale U8 and then save it.
Also, it would probably be better to create a new thread for questions like these.
Cameron T
Applications Engineer
National Instruments

Google Earth Plugin and LabVIEW: High CPU usage when adding placemarks

Hi,
I posted this question on stackoverflow earlier this week but feel it might be better suited to the LabVIEW community specifically so I'm reposting here:
I'm writing an application which uses the Google Earth Plugin to display events on the globe. Each event is a single point kml placemark with an icon which is a 3kb png file. Placemarks are uploaded to the plugin as they are received by the software. I am experiencing increasing CPU usage with the number of placemarks that are added.
I have tested displaying a new placemark every second and running until the software running the plugin completely froze (graph attached). The GEPlugin (green trace) stopped responding (i.e. the globe did not respond to the mouse) at around 1200 placemarks added and CPU usage was at ~30%. When the software itself (red trace) froze the plugin was using around 50% CPU and ~3700 placemarks had been added). After the freeze, no new placemarks were added which caused the software to respond (but not the plugin) so I could clear all the placemarks. After the placemarks were cleared from the globe, the CPU usage of the plugin returned to around 5% CPU.
So what I've seen is that GEPlugin CPU usage increases linearly with each kml placemark added. Is this the expected behaviour/ a normal limitation of the plugin? If not is there a more efficient way of adding many placemarks to the globe?
I am using GEPlugin version 7.1.1.1580 (API version 1.010) and LabVIEW 12.0f3
Please see the test results attached. Any input greatly appreciated!
Original stackoverflow post:
http://stackoverflow.com/questions/20994323/google-earth-plugin-with-labview-high-cpu-usage-when-add...
Attachments:
Performance Log 020114_095115.png ‏82 KB

Hello,
I have had a look at your graphs and understood what you are trying to do. To me it seems that as the image gets more complex it gets harde to render which wold likely cause increase in CPU usage resulting in the freeze. I would suggest you try running the program on anoher computer to check on the RAM front of things. If this is a limitation of the GE Plugin then unfortunately I can not do much to help, but if you think this is a problem coming from your LabVIEW code then you can post your code here and I can take a look.

Signal Processing and LabVIEW Expert Full Time Position – London, UK

1x Signal Processing and LabVIEW Expert - Full Time Position – London, UK
1.0      Description:
As a Signal Processing/Software Engineer, you'll be part of a team that is responsible for developing applications based on large high speed data analysis for a large green energy project. Your skills must include a knowledge of Waveform analysis and understand the concepts of cross correlation, Fourier Analysis, Spectral analysis and other similar items.
The position ideally requires someone of CLA level of LabVIEW program to act as the project lead on the programming and technical levels of the system.
2.0      Duties and Responsibilities:
The duties and responsibilities of this position include, but are not limited to, interacting directly with customers to program, train, inform, advise and consult in the design of their applications using the best test and measurement hardware and software by:
◦     Programming memory and speed efficient applications using LabVIEW and Object Oriented Programming and Event-based architectures.
◦     Understanding of the data acquisition side of the system and previous experience using National Instruments hardware and DAQmx
◦     Knowledge of Power engineering, Volts, Amps, current, Power Factor etc.
◦     Providing timely, accurate and effective solutions to technical problems.
◦     Providing guidance on the installation and working functionality of both software and hardware, including explanation of configuration settings.
◦     Reproducing and troubleshooting problems and incompatibilities.
◦     Delivering technical presentations and demonstrations to customers, colleagues and partners.
◦     Ability to project manage and understand how to keep on track with a Microsoft project based externally monitored project.
3.0      Qualifications & Requirements:
◦     Minimum second class higher honours degree in engineering or science related field, such as electronic engineering, physics, mechatronics or computer science.
◦     Basic Knowledge of text based programming languages.
◦     Experience in either LabVIEW, minimum of three years full time and at CLA level, or capability to reach there in a short space of time with the relevant training.
◦     Experience in a second language such as JAVA, C and C++ is strongly preferred.
◦     Have a vast experience of signal processing, both digital and analog.
◦     Although not required, but must have skills to pass the Certified LabVIEW Developer exam and CLA within the year.
◦     Ability to learn new skills/languages/applications quickly (MATLAB, JavaScript, STK, etc.).
◦     Knowledge in instrumentation & control, and industrial automation, is strongly preferred.
◦     Must be able to handle multiple tasks and enjoy working with people.
◦     Strong problem solving skills to analyse the problem and think creatively to provide a solution.
◦     Excellent written, oral and presentation skills are key.
◦     Ability to deal effectively with customers to make them successful is essential.
◦     Ability to get along with others and function as a team player as well as work effectively alone.
◦     A proactive/can do attitude is vital and a positive outlook on problem solving.
◦     Legal right to live and work in the UK. Sponsorship is not available.
◦     Must hold a full valid UK driving license.
4.0      Location:
This role is located in London, UK
5.0      Reporting:
Signal Processing Engineers will report to the Technical Director.
6.0      Salary:
Competitive salary based on level of experience.
7.0      Application:
To apply for this position please send a copy of your CV to
[email protected]
Please state the job title of LabVIEW Signal Processing Engineer in the email subject.

Hi,
I am from india.I can able to complete the projects through the internet itself.
Please let me know if any demos required to show my expertation.

Euresys Picolo image acquisition and LabVIEW

Similar Messages

Maybe you are looking for