Lumenera DirectShow camera attributes

Similar Questions

• gigE camera - attribute out of range 0xBFF69012

  
  

  Lightworker,

  Have you tried the version August 2010? There was a combination of elements (updates of the firmware of the Basler) and the third-party component GenICam which could cause incompatibilities that have been addressed in this release. One of the questions likely to be affected of the Scout and pilot series with firmware version 3, 2 - x and 3, 3 x, the newer versions of the firmware form Basler should solve this problem as well, but later IMAQdx also work around the problem.

  Grab the release of August 2010 here:

  http://Joule.NI.com/nidu/CDs/view/p/ID/2137/lang/en

  Eric

• GigE Directshow or bus ethernet type Max camera

  I have the Imaging Source DMK 23G 445 GigE camera.

  MAX I could see it as Directshow camera camera ethernet either in 2 versions.

  It works without any problem as Directshow camera but as soon as I use it as a camera Ethernet, that problems appear I could not put high package size, the highest I have together is 1484bytes. Extended frames are enabled and put only 7K.

  If I try to use the packet size like that I have an image similar to that attached, just the size of the bands depends on the size of the packets.

  If I try to use it as Directshow camera there are different problems in my software. I'm analyzing the particles, by default the camera is monochrome, and it's good for the analysis of the image it must be monochrome.

  This camera is monochrome in reality, but Directshow it shows like BGRA packed 8.

  So, I couldn't run image analysis I need to convert it to mono color.

  Is it possible to do?

  In the past, we used the color camera in a monochrome mode (max value) without too much problem.

  Unfortunately, I use Labview 8.6.1 so maybe it's one of the reasons that my current installation it is not working properly.

  Hi Sergey,

  It is recommended that you create a new location of the image with the correct format, see the image below for the base image-image on.

  

  Please let us know if that helps.

• Lumenera Infinity 2 camera Communication issues

  Hello National Community Instruments,

  I am trying to get a 2 Lumenera Infinity camera to work with LabVIEW.
  I downloaded the http://www.lumenera.com/support/downloads/microscopy-downloads.php sheet

  I also downloaded NI Vision with its pilots IMAQdx and IMAQ according to needs.
  However, whenever I try to load an example, or even to add a block of program it starts asking for NILuAPI.dll
  This file does not exist in the plug in.
  I was wondering if anyone had experienced this or if it was just a case of a file with the incorrect path.

  Solution?
  It was a little confusing that request since they refer to National Instruments when it comes to LabVIEW.
  However, talking to Lumenera was the right path.
  For my particular problem, the NILuAPI.dll file, on what he asked was missing in the standard download.
  You must request this Lumenera and also be sure to ask for the 32-bit or the 64-bit version, according to which matches your version.
  Then move the folder of Lumenara (LuCam) of inst.lib in LabVIEW 2010 (by default it's made)

  and move ot the inst.lib in 2011 (or whichever is yours).

  (this is for the 64-bit version only)
  Finally and above all to move the NILuAPI file in the Windows System32 folder which is located under C:

  Then try opening an example of the LuCam folder.
  Everything should load successfully.

• PCI-1422 and RS 232 control of a camera Hamamatsu ORCA-HR (HR C4742-95-12)

  Hello

  I'll have some incompatible problems when I try to control a camera Orca-HR (Hamamatsu C4742-95-12 HR) via RS232.

  I have a feeling that the problem comes from how the RS232 port emmbedded (emulated?) in the PCI-1422 is used or recognized by the various software that I've tested.

  So first, this port emulated/integrated should appear in the series, Max & list parallel port? I don't think, but he's not here, that's for sure. I have 'only' the projection of card PCI-1422.

  Case where I can access some of the attributes (accessible from limited functionality) camera:

  -By MAX I can change some settings so the snapshots of controller and make.

  -I can access these functions by IMAQ ('IMAQ camera set attributes.vi', etc. see Appendix vi example).

  -J' have a full control of the camera via the Hamamatsu Hipic 8.0 software, but only if I use the internal drivers and a different com port than those incorporated in the card PCI-1422 (Hipic offers not only port com in any case perhaps because there is no by saying?)

  Case where I can't access the camera at all:

  -If I try to use VI to a Hamamatsu (the most recent in sample screws & DLL or older version), it does not work: calls to any function of the 'tmcamcon.dll' return errors, pointing to the fact that there is no camera detected: the first sub_Vi (tm_initialize.vi) will return no error but zero connected camera and other screws return errors saying there is no camera using this handle, or no camera can be activated at using this handle.

  -I have NO camera control via the Hamamatsu Hipic 8.0 software if I use the DCAM API drivers no matter what com port (incorporated in the card PCI-1422 or other).

  Does make any sense to you?

  I just thought that the Hamamatsu screws cannot access the camera via emulation RS-232 of the PCI-1422. Is there a configuration setting, that I could use to those who do work and do not have to restart from scratch with IMAQ and with only limited functionality?

  Thanks in advance for your answers.

  Hello

  In fact, you can have access to the serial port integrated on the PCI-1422 map only with IMAQ functions.

  This explains that you cannot see in the section "Series and parallel" in MAX.

  I have not really well know PCI-1422, but there's probably a way to access the serial port on the card PCI-1422 in MAX.

  Camera attributes, you are able to access with IMAQ, y then the camera assigns the has camera driver.

  If you are able to access more attributes with Hamamatsu driver, it is the manufacturer who decided to restricted access to other drivers.

  But if you are not able to use the screw manufacturer, you should probably call him to find out why it works badly. Perhaps a version control problem or a update of the firmware?

• Where can I find the "Mirror Vertical" property?

  Hello

  I have a connected USB camera that displays the image in the wrong rotation. Under Max there is a setting in"attributes"-> "Mirror Vertical", which can be set to True.

  How can I adjust this setting under LabView? I don't find it in the properties.

  Thanks in advance

  How can I adjust this setting under LabView? I don't find it in the properties.

  In IMAQdx, you generally refers to properties by specifying them with string. See get programmatically and set attributes with IMAQdx
  For a list of the supported your camera attributes, call "IMAQdx enumerate attributes.

• IMAQ USB installation Grab in executable error

  I created an executable file that returns

  Error 1074396024 has occurred to IMAQ USB enter Setup.vi

  IMAQ Vision: Value of minimum coverage should be greater than zero.

  I developed the executable on a 32-bit computer with LabVIEW 2009 and the Vision Development Module 2012 SP1. The target computer has LabVIEW Vision Development Module 2012 and LabVIEW Run-Time Engine 2009 SP1 (32-bit Standard).

  Other people on the forum had this error, and I have tried everything what they suggest. I keep getting the error. I also tried to download IMAQ and acquisition of Vision software, but I get the same message. Some people have had problems with the LabVIEW versions in different languages, but I use only English. This problem is caused by not having does not correct execution engines?

  Any help would be greatly appreciated.

  Thank you!

  So apparently uninstall the Vision Development Module strips the description of your error code error. I think we should focus on the "IMAQ Vision: cover Minimum value must be greater than zero" error. Can you run your application successfully in the development environment? You use the same camera at the time of development and deployment environment? Identical camera attributes are? What troubleshooting steps you tried before to solve the problem? Using NOR-IMAQ or NOR-IMAQdx?

  Kind regards

• Live Show and driver OR IMAX.

  I try two Point Grey camera Firefly-MV acess and receive this response of an engineer.

  There are two ways to access the firewire OR IMAX camera. One is to use our
  DirectShow (with PMP driver) and the other is to use the 1394 host windows
  driver for the card with the driver OR IMAX. When you use the
  interface of DirectShow that the cameras will not be displayed separately and the manner of
  switch between the cameras in IMAX is to bring up the camera selection dialog
  box. When you use driver OR not directshow camera will appear
  separately and you will be able to switch between them by clicking on it
  separately. Both must work and please let me know if your currently
  Configuration (using the driver of OR) is causing problems.

  It's okay?

  Marcus René

  Hi Marcus,

  NOR-IMAQdx work directly with cameras 1394 (firewire) and if you work with LabVIEW, it is the best way, because all the functionality of the driver are supported by OR. The difference between working with NOR-IMAQdx or directshow is the driver, and how, engineer Piont Gray said, using the NI_IMAQdx driver you can access each camera separetelly.

  In summary, your end result will be the same using the driver IMAQdx or directshow if you use only one camera, but will be better with NOR-IMAQdx if you use more than one. And NOR-IMAQdx esiest to use with LabVIEW, once NOR-IMAQdx is native to it.

  Best regards

• Generation of the trigger (or TTL) analog signal

  Hello world

  Well I look at the droplet, riding on the vibrating bath. In this case I have to synchronize the device with the accelerometers.

  Accelerometers are connected to the vibrating plate vibrating sinusoidal with frequency of 80 Hz. I am the acquisition of acceleration using NOR-DAQ USB 6212. A camera (Camera Link Basler, NI PCIe-1433) is used to acquire images of the vibrating plate. The frame rate of the camera is 20 Hz which controlled by external signal (TTL) or camera attributes.

  I would like to generate a trigger of data acquisition (signal HAVE) to the camera at the first minimum acceleration in the attachment. I've also attached the file vi. Could if it you please let me know if is there anyway we can generate the trigger of the analog signal.

  See you soon

  NGO

  Hello, NGO,

  Can you post the update VI?

• How to read data from 16-bit unsigned IMAQdx?

  I was using my firewire camera to take pictures in unsigned 16-bit grayscale and processing of these data in matlab. However, the data becomes incorrect when the integration time of the camera is great. I discovered that the reasons are: 1, IMAQdx decoded data monochrome 16-bit signed 16-bit, which returns a negative value if the amplitude of each pixel is greater than 32768.  2, IMAQdx automatically adds a constant, which is equal to the amplitude of the largest negative value pixel, to all the pixel values, to change the smallest value to zero, but this process ruin the rest of my data and makes them almost irreversible.  I think the only method could solve this problem is to try to do in labview read image form of unsigned data, but I don't know if it's possible, because it is not optional in IMAQdx manual.

  Any suggestion will be appreciated.

  Hi Hosni,

  FireWire (especially earlier on) had some ambiguities on the endianness, signed-ness and depth of the pixel data that is returned. IMAQdx tries to take the best prognosis for 16-bit data using specific registers defined by the IIDC and other information she can deduct on the camera. However, sometimes these assumptions are incorrect. If you go to the acquiring of your camera attributes tab in MAX, you should be able to replace all these parameters correspond to what the camera expects its data should be interpreted.

  Eric

• Error of flow OR MAX and attribute camera out of reach

  I recently bought a camera Point Grey Grasshopper3, it seems to work fine at point software fly Cap Gris provides, but I get an error NI Max when I try to do a simple puncture (see below). This error appears every time I try to catch a time image the first after the opening OR MAX, even if the flow is set to maximum. Then I change the flow under control of the unit to any integer 125000000 max, and the camera works very well for MAX. It will capture images as much as I need. Then I save the camera output MAX, open MAX once again, it shows my saved settings, I'm going to capture images and I get the error again. If I change the range regardless of the number and it works again in the same session in MAX.

  I had a gray point Zebra2 work very well and he used in my program LabVIEW with IMAQdx to acquire images. When I try to use grasshopper3, LabVIEW returns error attribute camera out of reach of the VI camera configuration. I use to test the camera of the VI is the camera just to open, configure acquisition, start acquiring, get the picture, cancel the acquisition and nearby IMAQdx camera configuration. I did twice open MAX, change the flow, save the camera, close MAX without grasping an image and then was able to acquire images in LabVIEW in the first inning. I would run the VI once again and then it returns the error to attribute camera out of reach. I changed the packet size, resolution and the frame rate of the camera with a difference in errors.

  Since I am able to images of the stream from the camera to the gray point fly capture and Max after activating/deactivating the flow layout, it leads me to believe there is some sort of error MAX/LabVIEW that prevent me to capture the images.

  Any ideas? Has anyone else had this problem with MAX and LV?

  Looks like the point Grey cameras showed this error before the firmware on the basis. See this linkfor such a forum. I would monitor the camera (*.icd) file located in the data folder IMAQdx in public Documents to see if the actual value is be replaced after the configuration of the camera has been saved in MAX. There is a chance that the GigE. XML file which is transferred from the camera is overwrite these values in the unacceptable value. See this linkfor a KB about this error, which leads me to believe that this may be the problem.

• Camera USB/DirectShow is no projection in NOR-MAX

  I have a gray Chameleon Point CMLN-13S2M USB 2.0 camera and it does not appear in the NOT-MAX.

  I am well aware of Directshow registration with cameras RMP problems and I can tell the camera is correctly recorded.  It comes without any problem in AMCAP, a simple viewer of Directshow and also in Skype.

  I just uninstalled the drivers PMP and spent some time going through the registry to remove all references that I could, at Point Grey and PMP.  Then I reinstalled the 32-bit version of the newer drivers, v2.5 beta 2.  I've also upgraded the firmware of the device later.

  I am running

  LabVIEW 2012 SP1 f2, 12.0.1

  Vision development 12.1.0 module

  MAX 5.4.0f0

  NOR-IMAQ 4.7.2

  NOR-IMAQdx 4.1.0

  Any ideas?  It is a side project and I worked on it market now for over a year and I've learned to get this camera working.

  Hello

  The way list us the cameras is quite simple using the only mechanism of API Miscrosoft has for him. One thing I noticed, is that we need the "DevicePath" registry key to be filled (in addition to the key "FriendlyName"). Can you check and see if the entrance of advanced camera Grey was who? If this is not the case, try adding a string with a text for her.

  Eric

• Change camera vision Builder link attributes

  I have a Camera Link camera and a NI1427 Council. I need to change the shutter speed by program during an inspection. Is it possible to change the attributes of the Interior VBAI camera?

  I have seen a few examples for Firewire cameras and Camera Link cameras do not use IMAQdx, IMAQ simply. Is it possible to send commands to the camera inside VBAI? Is it possible to call a LabView VI that was to change the camera settings? Thanks for your help!

  Thanks for the input Brad. In fact, I realized another way to change the exposure through VBAI.

  It turns out that my camera camera (Sony XCL-5000) link has a mode in which the shutter speed can be controlled by a trigger pulse width.

  In IMAX, I changed the following attributes of the camera:

  Mode of operation-> pulse width

  Source of relaxation-> Camera Link

  Duration of exposure-> 7ms

  Then I put CC1 to "switch 0.

  In VBAI, I have configured step to acquire images at:

  Triggered-> checked image acquisition

  Trigger-> external 0 line

  -> Rising edge polarity

  I thought I'd be able to use the stage to generate impulses, but the width cannot be changed programmatically. So I use two measures of e/s of read/write with a time delay between the two. The first read/write IO affects 0 ane high external line that second place low. The value of the delay can be changed using a control variable. The pulse width resulting is probably not the most accurate, but it works for my application because I want to just increase the exposure when the picture is too dark and decreases when it is too bright.

• How do I enter attribute vertical mirror for a firewire (imaqdx) camera

  We have a device that looks like a real physical mirror, but the image of the camera, feeding demand must be correctly oriented, as if the camera looking directly at the object. I expect the vertical mirror attribute allows you to set the orientation of the image in the imaqdx driver (this is a fire - I unibrain firewire camera) but I can't find this setting exposed anywhere. Any tips on how to do this? Thanks in advance.

  
  

• Why are some attributes of 1394 camera Max writable yet Enumerate in LabVIEW Vision as unwritable

  I know that this room sees its fair share of issues of setting attribute camera but I hope that it is sufficiently different to justify an exchange of views.

  I'm in the middle of a piece of code that used to use IMAQ Legacy 1394 to IMAQdX since NEITHER decided to drop the single 1394 support portage.  I ran into an interesting problem.  When you work with a DCAM 1.3 complient camera (Prosilica E1360C, firewire) I find that it is possible to manually set the Max gain, but when you list the attributes of the camera in LabVIEW using the enumeration Attributes.vi, CameraAttributes::Gain: Value rises only not available in writing.  How did MAX OR move it?  I tried to write the gain using the gain writing Register register manually by referencing the DCAM 1.3 Spec document and then using the Register.vi to write, but I had no luck.  The same is true when you're just trying to write the CameraAttributes::Gain: Value by using the attribute writing property node.

  Does anyone have a suggestion?