Select by session IMAQdx (GigE Camera) program

Similar Questions

• Camera not selectable in "Session".

  Hello

  I have the following configuration:

  A 'ELIIXA + 8 k/4 k' camera, connected to an SMU-1435 module in the SMU-1082.

  My goal is by program aquire images in LabView (14.0.1 / 32-bit)

  In MAX, I can take pictures very well.

  I wrote a simple program to run on the PXI system, but I can't select the camera like "cam0" (or something) at the Session 'en' - selector.

  (Yes, I deploy the VI for PXI)

  This is a screenshot of MAX (German version)

  

  Why the camera appears as a "Channel 0", as opposed to "cam0?

  Can I change this?

  How can I use a camera that presents itself as "Channel 0" in LabView?

  This is my test VI, it displays the error code "-1074360311 IMAQdx Open Camera", as is expected, when the camera is not correctly selected.

  

  There seems to be something fundamental, that I am completely missing.

  Thank you for your help.

  Hi SeWi,

  Since you have a camera link you can yous the driver not the IMAQdx IMAQ.

  What is the difference between NOR-IMAQ, NOR-IMAQdx and NOR-IMAQ i/o? -National Instruments
  http://digital.NI.com/public.nsf/allkb/0564022DAFF513D2862579490057D42E?OpenDocument

• External triggering of GigE camera

  Hi, I'm planning on using the camera triggers the entry to start capturing images but I'm not sure what I need to do in my c# application when a trigger has launched.

  -If the trigger is coming from the PLC, should I also send a trigger signal to the PC and keep the active trigger signal until the PC is the acquisition of the image?

  -Do I still need use the snap or enter functions in imaqdx to get the picture?

  -If the camera is connected directly to the external NETWORK card triggering she still great benefits? The camera in less than 5 meters from the PC.

  Thank you

  Cliff

  Normal 0 false false false fr X-NONE X-NONE / * Style Definitions * / table. MsoNormalTable {mso-style-name : « Table Normal » ; mso-tstyle-rowband-taille : 0 ; mso-tstyle-colband-taille : 0 ; mso-style-noshow:yes ; mso-style-priorité : 99 ; mso-style-qformat:yes ; mso-style-parent : » « ;" mso-rembourrage-alt : 0 à 5.4pt 0 à 5.4pt ; mso-para-marge-top : 0 ; mso-para-marge-droit : 0 ; mso-para-marge-bas : 10.0pt ; mso-para-marge-left : 0 ; ligne-hauteur : 115 % ; mso-pagination : widow-orphelin ; police-taille : 11.0pt ; famille de police : « Calibri », « sans-serif » ; mso-ascii-font-family : Calibri ; mso-ascii-theme-font : minor-latin ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ;}

  Hi riscoh,

  When you work with a GigE camera you are not anything on the computer triggering its self, only the camera.  When it is configured to trigger it will sit and wait for a trigger.  When he received the signal it will take an acquisition and send the information to the computer.  When you set up your support on the computer it is searched for images and brings them into the computer as they become available.  The example I'm pointing you will show you how to set up the camera by a trigger program.  It looks like it may be available only in Visual C.  As far as the documents relate to article after the release with a GigE camera Developer area described briefly.  Acquisition of cameras GigE Vision with Vision Acquisition Software-part II

• How to identify a GigE camera by IP address

  I have a system with 8 Basler Ace GigE cameras, all on static IP addresses on the same subnet.  I would like to be able to exchange any device with a new one that is configured to the same IP and my LabView RT running on an Exchange virtual server program automatically starts using the new camera.  The LabVIEW program already sets the settings in the camera, if I don't want the user to have to use MAX for any configuration of the camera.  I want to just the user to use the Basler IP configuration tool and the tool of Basler to focus the camera, then having my program discover the camera by its IP address.

  However, I have not found an IMAQdx tool that allows me to distinguish the cameras by its IP address.  The discovering Ethernet cameras VI has an address entry, but it is only a mask and cannot me narrowly find just a single camera on an IP address.  I have not found any camera property or an attribute that returns the IP address.

  So, if I have a bunch of cameras and want to identify who is who, by his IP address, how can I do?

  Hi Ken,

  The main identifier imaqdx uses to track/locate cameras is serial number, which is identical to its MAC address for GigE Vision cameras in IMAQdx. Unfortunately us don't really use IP address as any kind of ID to connect with a specific camera, because we assume that the IP address can be dynamic and flexible (makes it spec GigE Vision DHCP and link-local addressing a requirement standard and everything is designed to allow these cases to work well).

  That said, there is an attribute called 'CameraInformation::IPAddress' that you can query to see the IP address of the camera. The only downside is we do not currently provide this information via the Enumerate mechanism - you first need to query this property of the device. Your application might first browse the cameras and do a mapping of serial to IP addresses?

  Hope this helps,

  Eric

• The value FPS using NOR-IMAQ with a GigE camera programmatically?

  Hi all

  I'm (slowly) learning how LabVIEW plays well with the cameras, GigE, that I just bought.

  At this point, I'm trying to understand how to programmatically set the value of fps for the camera.  I have been using the examples NOR-IMAQdx to control the cameras so far, but I am open to trying anything.  Someone at - it a good example of how I can change the frame rate "on the fly?

  My next task will be to find a way to change the size of the image on the screen programmatically, so if anyone has any ideas for me on this path there, I'd be pleased them too well.

  Thank you very much

  FB

  I thought about it:

  1. use the vi IMAQdx open camera to open the camera

  2 use the "List attributes" in the palette of NOR-IMAQdx to see all available attributes

  3 using the step 2, above, I could find the attribute, the attribute "AcquisitionFrameRateAbs".

  4. create a node in the output of the open unit VI property, choose 'Attributes of the camera,' select "Attribute Active."

  5. set the property node "change all to write."

  6. connect a constant string of 'AcquisitionFrameRateAbs' attributeinto the property node value

  7. create another node in property 'Attributes of the camera', this time by selecting 'Value' and affecting the type DBL

  8. change all to write

  9 create a digital control for cadence

  10. connect the digital control to the property node 'ValueDBL '.

  Presto!  You are finished.

• IMAQdx multi-camera systems: shortcuts for composite image sewn

  Imagine a system using for example multiple GigE cameras through IMAQdx interface where we want to be a stitched composite of multiple camera views. The principle of sewing is naïve, simple concatenation, one next to the other.

  The problem is that, when it is trivial to build a composite image, it is difficult to do this very effectively. Image sizes are large, tens of millions of pixels, so that each copy of questions. Configurations material alternative would open many options but say we are stuck using GigE cameras and (at least initially) the IMAQdx interface. What are the tips or even hacks, you guys can imagine facing this challenge?

  I've seen some talk about the IMAQdx capture buffers and it seems to me that one can not manually allocate these buffers or access it directly. The absolute best scenario would obviously be to hack your way around to spread the image data next to each other in memory, sort of as follows in scenario1.png:

  

  The foregoing, however, don't seem to be too easy to achieve. Second scenario would be to acquire in the individual buffers and perform one copy in the composite image. See the illustration below:

  

  Interfaces usually allow this with relative ease. I have not yet tested, but based on the documentation using ring acquisition of buffer and "Extracted IMAQdx Image.vi" this should be possible. Can anyone confirm this? The copy can be carried out by an external code as well. The last scenario, without ring buffer, using ' IMAQdx to Image2.vi ' might look like this:

  

  The second copy is a loss for this scenario should be out of the question.

  I hope this makes some. Want you magicians say about this?

  Unfortunately he has no concept of a "sub-image" where you could have acquired acquire seamlessly in an image that represents a region of a larger image. However, you are right that the acquisition of the ring with the extract is the way to remove a copy. In this mode, the user allocates the internal buffers imaqdx uses by means of standard images, and then they can access those without copying directly. You can simply extract the image of each camera (zero-copy) ring buffer, then use the VI ImageToImage to copy a region in your larger picture (a copy).

  Eric

• Different behaviors in MAX vs LabVIEW when writing the attribute IMAQdx GigE

  Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

  However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

  I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

  I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

  Any help will be appreciated.

  AnthonV wrote:

  Hi, I'm controlling a Dalsa GigE camera in LabVIEW RT using IMAQdx.  Apart from a few quirks with interface we are image acquisition without a lot of problems at the moment.

  However, there are one or two issues that are confusing.  In this case, it is possible to set a MAX attribute (an attribute of command that tells the device to perform the internal calibration), but when you set the attribute in LabVIEW, the error 0xBFF69010 (-1074360304) unable to create the attribute is thrown.  See the attached images.

  I check if the attribute is writable before making an entry.  It is, however, the write failed, and read the iswritable attribute and then returns false.  In MAX, I can write to this attribute with no problems.

  I have to set up/read/write in my LabVIEW code that makes MAX.  MAX writes all the attributes (based on the values in the XML file) when he opens the camera or he reads simply all the values of the camera.  When LabVIEW opens a reference camera does perform the same steps that what MAX - I'm trying to figure out what could be the difference between MAX and LabVIEW, which might be the cause of this behavior.

  Any help will be appreciated.

  Hi AnthonV,

  "Weird" is a good way to describe the Spyder3 when it comes to the GigE Vision/GenICam interface (as opposed to the Dalsa driver that communicates using custom commands via ethernet camera series)...

  The Spyder3 has many questions focused on the calendar. It is possible that the time between the opening of the camera and the setting of this function is different by MAX vs your code in LabVIEW. In addition, there are some cases where MAX will be deletes the error to display. Ignoring the error indicated vs you see the feature to take effect in both cases?

  The base between MAX and LabVIEW behavior is the same. In both cases when you open the unit all parameters are responsible for our camera file that has the registered device settings. This file is created the first time that you open the unit and are updated every time you click on save to MAX or call an API function to save the settings. In any case, I know that the Spyder3 has various questions backup/restore the settings of our camera files.

  I suggest talking with Dalsa on the issues you are experiencing. They might be able to put up with a newer firmware that addresses some of these issues (we have worked with them in the past to identify several of them).

  Eric

• VB6 with GigE cameras?

  I use Vision Devlopment Module 8.5 with VB6.   I wrote a lot of code using activeX controls for cameras, firewire 1394.   Are there for GigE cameras VB6 activeX controls?  If so, can you put link here for examples.  Thank you

  Hi Dan,.

  IMAQdx documentation indicates that it has supported inherited from MSVB6. Your device should work with these examples as long as it meets the standards GigE or correct DCAM to work with IMAQdx, because it's always using our IMAQdx drivers.

  I'm not sure the support ActiveX specifically for GigE cameras, but once that you have connected to your camera with IMAQdx in VB6, I don't see why you shouldn't be able to use the functions you used before. I suggest that you try to change your existing code to connect you with your GigE camera and test the functionality of your ActiveX code.

  Thank you

• Connection to CVS GigE camera via a network switch

  It is a fundamental and very simple question!

  I intend to connect two GigE cameras to NI CVS-1458RT for an application of Imaging. When I tested the configuration in MAX, I realized that I can connect the cameras directly to the PoE ports, or alternatively, connect the cameras directly to the network switch and in both cases, connect the CVS to my network via its ethernet port. I was wondering if there is a benefit by connecting directly the VCA cameras, if I do not anticipate supply their Poe or if my switch has PoE Betacam.

  Thank you

  Usually, you always want your cameras on dedicated lines, or at least only sharing bandwidth with other devices. The mechanism of transport used by GigE Vision isn't really sharing good bandwidth with other devices. If you only share the bandwidth on a link given with other devices, you can throttle each take only a percentage of the total bandwidth. If you have devices without camera on the link, they don't usually have a mechanism to control the gap inter-frame limitation insofar as GigE vision made which would be necessary for properly sharing the bandwidth without remove the packages of bandwidth.

  If you end up sharing one of the ports for the operation and configuration of the CVS on the network, you will be at the risk of losing image data packets whenever the rest of the traffic is sent. Although there are mechanisms in place to return data, these add latency and jitter to your purchase.

  Eric

• -1074360266 error to IMAQdx Open Camera.vi

  Hello

  We have problems with our LabView vision system; the VI is able to "run" with an intact arrow, but there is an error that appears:

  "Error - 1074360266 occurred to IMAQdx Open Camera.vi" with a possible reason of "NEITHER-IMAQdx: (Hex 0xBFF69036) Impossible to reach for the driver in kernel mode.

  For a little history, we had initially scheduled the VI in LV2009 (where it worked fine), but the customer upgraded to LV2010 (where it now comes up with this error), so it would be logical that it has anything to do with the problem.  In addition, we use two cameras Basler A601f via Firewire connections, which both are recognized by the Basler pylon Viewer software, so we're pretty certain that it's only a problem of LabView.

  We have tried to reinstall the drivers of Acquisition of Vision software, but it does not solve the problem, so we gradually loss.

  Any help or pointers are appreciated, and I apologize in advance if I've left out any relevant information.  Thank you.

  --

  Ben

  Ben,

  Are you able to find the camera and get him to the MAX?  Also, what version of IMAQdx you have installed?  Driver versions are MAX on the software tab.  Because all this happened after an upgrade to a new version of LabVIEW, I suggest to re - install device drivers CD, then reinstall the software of Acquisition of Vision.  I would like to know how this happens.

• IMAQdx Open Camera.vi very slow

  Hi all

  I use a firewire IEEE1394, a camera with IMAQdx with labview 2009.

  1. I have configured MAX camera and tested. It works very well.

  2 - I used the "Grab and attributes Setup.vi" Labview examples. With the vi, it takes about 1 second to find the camera and it works fine.

  3 - I copied the Camera.vi of the IMAQdx 'open' this example in my own software. When I run it takes about 20 to 30 seconds to open the camera. He finds it, but it is extremely slow.

  4. to test, I opened at the same time the 'IMAQdx open Camera.vi' 'Grab and Setup.vi attributes' and my request, set the name of the camera on the two clones and run one after the other: I still see the same behavior: the first (from step 2) takes 1 second to open the camera, while the other (from step 3) takes 30 seconds to open without sending an error message.

  I came to the conclusion that there must be a link somewhere to a file of configuration or something that makes the fastest start-up in one case than in the other.

  Has anyone experienced something similar? / Did someone has an idea on how to solve this problem?

  
  

• GigE camera - image grab bars

  Hello world

  I use or acquisition of vision to capture images of a GigE camera.

  I get images just as I trigger the camera - rates so so good.

  All other photos shows a few black bars.

  Anyone have any idea what it could be?

  It is not the hardware, the camera works perfectly with the shape of the manufacturer's software development kit.

  Thanks for any help

  Looks like an incomplete picture, this could be caused by the missing packets.  To prevent missing packets when the acquisition, you can do two main things: the size of the packets configured on the camera may not exceed what the network card can manage and ensure that the bandwidth of the output of the camera image data do not saturate interface band bandwidth.  I would reduce the packet size of camera for 1500 initially to determine if the size of the package is the cause of the problem.  You can throttle how much data that the camera can send by manipulating the interpacket delay, some manufacturers have a very handy feature called StreamBytesPerSecond.  According to what mechanism, you can use, increase interpacket delay or reduce StreamBytesPerSecond.

• Acquire GigE camera data using labview CIN or DLL to call.

  I am tring to acquire data from a basler runner line CCD camera (GigE).

  Because the NI Vision Development Module is not free, and the camera provide a C++ API and C and also some examples, so I plan on using the function CIN or call DLLS in labview to achieve. Is this possible?

  I tried to generate a DLL with the example of the company code of the camera. But encounter difficulties;

  I did that a little background in C++, but not familiar with it. The C++ Code example provides the camera is a C++ (a source Code file) and a .cproj file, it depends on other files, the camera API directory.

  If I build the project directly, it will create an application window, not in a DLL. I don't know how to convert a DLL project, given that other information such as dependence in the .cproj file, other than source code.

  Can someone help me with this?

  Don't forget that for the acquisition of a GigE camera, you must only Module of Acquisition of Vision, not the entire Vision Development Module. Acquisition of vision is much lower price and also delivered free with hardware NI Vision current (for example a card PCIe - 8231 GigE Vision of purchase). You need only Vision Development Module if you then want to use pre-made image processing duties. If you are just display, save images to disk, or image processing using your own code (for example to manipulate the pixels of the image in a table) you can do so with just Vision Acquisition.

  It is certainly possible to call DLL functions if LabVIEW by using a node called library, it would be quite a lot of work unless you are very familiar with C/C++. Since their driver interface is C++, you need to create wrapper functions in C in a DLL that you write. Depending on how much you want to expose functions, this could be a bit of work.

  Eric

• IMAQdx v3.7 gige camera enumeration/connection slow

  I recently upgraded from IMAQdx 3.2 to 3.7 due to a problem, that I got with a camera (JAI CM-040GE with the new firmware did not work with IMAQdx 3.2).  The upgrade has solved the problem, but now camera enumeration and connection to the MAX and my VB.Net code last much longer that they did with IMAQdx 3.2.

  I used a stopwatch to compare the time enumeration and connection on two computers, one with IMAQdx 3.2 (MAX 4.6.2) and the other with 3.7 (MAX 4.7), all other software are the same.  In MAX, I timed it to developing tree 'devices and Interfaces' until the "NOR-IMAQdx peripheral" appeared, which was 20 seconds with v3.7 and 2 seconds with v3.2.  Connection to the camera, timed click on the camera until the information is visible in the lower pane of the info, takes 10 seconds with v3.7 and 2 seconds with v3.2.  I timed the functions "CWIMAQdx.EnumerateCameras" and "CWIMAQdx.OpenCamera" in my application and got similar results.

  The rest of my software NOR is 9.1, VDM 8.6.4 DAQmx and going TO 8.6.0.  I tested IMAQdx 3.7 on a second computer with the same results.  I use the driver gige of high performance on all computers.  I tried three cameras: JAI CM-040GE, Basler sca640 - 70gm and Prosilica GC655M, all with the same results.  Deleting the files from camera CIM and xml in the file data of IMAQdx did not help.  My employer requires McAfee work on all systems, but it does not affect v3.2 and I see nothing in the McAfee logs that would indicate the interference.

  There is an incompatibility between the versions of the software I use? Is this by design? Or is the wrong thing?  I can work around the issue of the enumeration, assuming that "cam0" is present and only list the cameras so this isn't, but 10 seconds to connect is a very long time, especially since my application is restarted frequently in development and testing and in the field, to a lesser extent.

  
  

• How to make a simultaneous wink of GigE cameras?

  I have 2 cameras of 780-54gm Basler Scout (monochrome GigE) I switch to 10 Hz. This pace is modest and the data rate that results is not particularly high. I would like to get images from two cameras of the same trigger pulse. I have an Intel Pro/1000 NIC and I use the driver NEITHER appears so as National Instruments GigE Vision adapter. When I use the Basler pylon Viewer (the software that comes with the camera), I see perfect images from two cameras at the same time at 10 Hz. This tells me that the network, map NETWORK and the drivers can handle the flow of data without problem. I have activated jumbo frames. When I try to acquire images in LabVIEW 8.6 with screws IMAQdx, however, that I meet problems. I can acquire every single camera, but I can't them both at the same time strictly. The images are taken through with horizontal black lines that appear and move erratically. I have attached a vi that shows the problem. I have set up and start the two acquisitions, then enter a while loop that reads images. If I do the sequential acquisition by starting and stop them inside the loop and ensuring that we stop before the other then I get quality images but they are not the same impulses to trigger, and start and stop of the acuisitions overload slows down things so that I can not get pictures of each trigger. My guess is that it is a problem with how LabVIEW is the memory management, resulting in corruption with simultaneous acquisition. Are there settings I can change to fix this problem? I've experimented with everything I knew (buffer numbers, etc.), but without success. Rich P.S. I posted this in the forum LabView a couple of days but got no response. Sorry if you see this twice.

  Richard,

  Looks like you just packet loss. You might associate a property node to request lost packages to confirm. The reason for that happening is that even if the way to two cameras data rate is less than the limit of the NETWORK card, each camera probably goes to the complete 1000Mbit bandwidth when it transfers each picture. When transfers of images overlap, sending you to 2000Mbit/s down a 1000Mbit pipe and lose packets.

  To resolve this issue, an easy way is to adjust the attributes of Acquisition-> Ethernet advanced-> attribute peak bandwidth used for both cameras 500Mbit. This should ensure that each camera never use more than half of the bandwidth. There are also other options such as sprawl of transfer times, but those who require more tuning you change other settings.

  I don't know why the Basler software shows this, although their lack of bandwidth might just be lower at the expense of additional latency to get the images.

  Hope this helps,
  Eric