IMAQdx Enumerate cameras - bus type codes

Similar Questions

• -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?

  
  

• 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

• HP Elite X 3: HP Elite X 3 video camera works no-Code error (0x8007045D) 0xA00F427F

  Someone at - it problems with the help of the video camera?

  It does not work for me and I get the following error:

  "Something went wrong".
  Sorry, we weren't able to record video.
  "If you need it, here is the error code: 0xA00F425E (0xC00DABE4).

  As well, the normal camera crashes when I use HDR.

  OS version: 10.0.14393.189
  Revision number of the firmware: 0002.0000.0007.0088

  Edit: seems the changes both error codes: 0xA00F427F (0x8007045D)

  WDRT is Windows device recovery tool.

  This should always be the last step of wiping a Microsoft phone powered :-)

  Thanks for your reply.

  Will try if that helps out.

  Concerning

  JoeTec

• Camera not found, error 1074360311 occurred at IMAQdx Open Camera.vi, USB cameras labview 2013 64 (bitts)

  I use USB cameras with labview 2013, and I can acquire images in the MAX and in the Acquisition of mink (express) settings, but when I run the VI, always appear the same error as shown in the Image below.

  -J' checked the correct versions of my software, IMAQ, IMAQdx, VDM 2013 IMAQ of e/s

  -J' I also make sure I had all the updated device drivers.

  -I'm using IMAQdx LKD schema and examples, getting the same error uu

  Help, please!

  Any suggestions would be very helpful.

  

  If it works in the pop up app Express VI and inside MAX (the two 32-bit applications), then I guess it will work in 32-bit LabVIEW. We wonder why it does not work in 64-bit LabVIEW, but these are the drivers of the device and other pieces of infrastructure/DirectShow Windows.

• Select by session IMAQdx (GigE Camera) program

  Hello

  I have a system with multiple cameras. Is there a way to select the camera for a session of IMAQdx programmatically, based on the number of the unit picture, IP address or something similar that can be read from an input text file?

  Thank you

  Soheyl

  Yes, you can use the enumeration Cameras.vi IMAQdx to get all kinds of information on cameras. This will get the serial number of the cameras (in 2 segments called Hi and Lo), and you can search for a match with the serial number you enter.

• Several acquisitions of IMAQdx USB camera simultaneously

  Hello

  I am trying to acquire 2 or more focused on the USB webcams at the same time, but one of the cameras always error. I replaced IMAQdx ENTER with IMAQdx SNAP and that seems to work to capture frames. But I would really like live food to webcams both (or several) if possible. The idea is to consult the live wire of two cameras and make necessary adjustments in the rest of the material to my system and then begin to capture images every 10 seconds approximately (from two or several webcams).

  Attached, multicamera_op_v1 = VI to get two webcams live food.

  multicamera_op_v2 = VI to get direct feed from two webcams and then captures frames from two cameras.

  I would like suggestions.

  Thank you

  
  

• Unibrain Fire-i with IMAQdx color camera

  Hi all

  I'm considering buying a color of Unibrain Fire-i 785 camera. It is possible to purchase this camera uses OR-IMAQdx (I don't have any NOR-VISION). The sales rep told me to a quite expensive third-party SDK. But all I want to do is wink images to a file, so this seems like an exaggeration...

  Can someone advise?

  Thank you very much

  David

  Just to take pictures, you need the IMAQdx (Image Acquisition pilots), which is a few hundred dollars.  This should be all you need if you're not processes images.  If it is not available without NI Vision to save the Image, you can convert the image into a table, and then save it using the tools of image control.  It takes more than a few steps and probably a little more time, but the price is right.

  Bruce

• HP Pavilion dv6-6185tx: could you tell me the bus type of the hard drive (HDD) of HP Pavilion dv6-6185tx

  Hi, I would like to Exchange SSD for my PC, HP Pavilion dv6-6185tx. However, I couldn't find the but type (for example, SATA, SAS, SCSI, or IDE ect...) of this model on the Web site.

  If anyone knew that, please tell me, thank you very much!

  SATA, 9.5 mm or thinner SATA SSD will fit.

• Change a Bus Type of controller SCSI VMs of BusLogic at LSI Logic

  I'm creating a new virtual machine with "New - VM", but the scsi controller that is created by default is a BusLogic, I need a controller LSI Logic.

  What is the best way to achieve this?

  Kind regards

  Roman

  Take a look at the Configuration Type of SCSI controller.

  This filter must be able to do the trick.

  ____________

  Blog: LucD notes

  Twitter: lucd22

• Is there a way to determine if a camera IMAQdx session is still valid or not?

  If it is valid, IMAQdx Open Camera.vi will return an error.

  If it is not valid, IMAQdx Close Camera.vi will return an error.  And IMAQdx close Camera.vi is very slow during the in camera session is invalid.

  I mean IMAQdx Camera.vi open have not yet been called, or IMAQdx Camera.vi Close has been called.

  Although there is no node property for this purpose, other properties, such as the name of provider of camera, are acceptable workaround solutions.

• FireWire Camera disappeared to MAX when you select the driver NOR-IMAQdx

  Hi, as the title suggests, I'm having a problem getting my camera firewire (a PixeLINK PL-A742) appears in MAX so I can use it in my application. First of all, a bit of history.

  It was all works fine on an old computer (Windows XP SP3, LabVIEW 8.6.1, NOR-IMAQdx 3.2).

  We just received two new computers. They have Windows 7 Professional 64 - bit installed on them, then we are stuck using that (I was going to install labview in XP Mode, but there is no support for firewire, which no longer works). After finally getting installed labview (to run the setup.exe from Distributions\LabVIEW-ENG\LabVIEW861\, rather than make the autorun) we cannot get this camera to work. It works very well with the PixeLINK pilot (and Capture OEM program that accompanies it).

  So here is what I tried, and what happens when I do.

  (1) install cost of LabVIEW (including IMAQdx 3.2) and PixeLINK drivers.

  (2) at this stage, the camera works very well in the PixeLINK application

  (3) start MAX. It detects the camera and shows under devices NOR-IMAQdx. When you click on the camera, it informs me that the selected device is not currently associated with legacy OR-IMAQ driver IEEE or the driver OR-IMAQdx. This is perfect, it is supposed to do.

  4) click camera > driver > choose NOR-IMAQdx IIDC camera digital

  (5) he then disappears from MAX (no record OR-peripheral IMAQdx more). If I goto windows Device Manager, it comes under National Instruments IMAQ Interfaces as NOR-IMAQdx IIDC camera, says the pilot did get properly, it just does not appear in MAX more...

  (6) at this point, there is nothing I can do to get it back to the MAX (except in Device Manager to switch the driver on the PixeLINK one, then he pops up and we return to step 3)

  So, any ideas? This could be a problem with firewire interface and not the camera? I use the FireWire on my computer. It presents itself as Texas Instruments 1394 OHCI compatible host controller in Device Manager.

  Here are a few screenshots to help illustrate my problems.

  It is the initial configuration using the PixeLINK driver.

  

  It's MAX with the PixeLINK driver

  

  As soon as I click on the NOR-IMAQdx IIDC camera, it disappears

  

  And here's what it looks like in Device Manager after you have selected the NOR-IMAQdx driver

  

  Anyone have any ideas? I'm open to anything. At this point, I'm completely at a loss to know what to do.

  Thanks in advance,

  Devin

  Mechanical engineering intern

  University of Victoria

  Well, you can just ignore this message now. I solved my problem. I installed Vision Acquisition software 2009 and it seems to have solved my problem.

• Cannot create an installer containing IMAQdx in 2014 of LabVIEW

  I have a strange question in the generation of installers with a function IMAQdx in LV Application Builder 2014.

  When I was building an installer for an executable file using IMAQdx in 2013 LV, Application Builder automatically selected additional installers needed and IMAQdx drivers (Vision Acquisition) were one of them. Now I'm trying to build the project even in 2014, but in the additional installers, I see only NOR-IMAQdx DURATION 14.0. When I build the installer in 2014 LV, the size of the file is about 300MB opposed to 900MB of the installer which has been built in 2013 of LV.

  When I run the installation program from 2014 on a 'clean' Windows, install and run any application that uses IMAQdx, I do not see the cameras connected. This problem is fixed after manual installation Vision Acquisition software of DVD drivers for the device OR. After that, I can see all the cameras in the application and in MAX.

  I tried to manually add additional installers in 2014 LV, but nothing helped. It seems to me that there is no way drivers IMAQdx bundle in LV Application Builder.

  I found a post related to this and I wonder if someone can reproduce this behavior before dropping off a CAR. I have attached a simple project with a simple VI and installers of the sample in for testing. The VI allows you to select a camera (e.g. a webcam) and video image.

  Hi martin.zmrhal,

  What you see with only the Vision Acquisition Software runtimes (VAS) available in the list of installers extra is expected with the latest behavior.

  Before Vision Acquisition Software (VAS) August 2014, programs additional installation to after-sales Service, namely OR-IMAQ, e/s NOR-IMAQ and NOR-IMAQdx not only includes the runtime components but also for LabVIEW application development support. GO August 2014 and later, now only allow us the deployment of runtime components. This gives the advantage of a substantially reduced Installer size, but you can include more support development (ADE) LabVIEW applications is in the installation program.

  This change aligns Vision with LabVIEW behavior and most of the other products OR you cannot deploy generally support the complete development of a product, but rather only the runtime components. If you need to install GO with ADE on your deployment machine, you will need to distribute the complete Installer GOING on this machine in addition to LabVIEW (to make use of the SAV ADE support). To do this automatically, you will need to write a batch file to run the installer for LabVIEW, then IMAQdx.

  With respect to the second issue of not being able to see the camera, I think that what you are experiencing is that the drop of the control Session is dimmed and you cannot click on it to see a list of the cameras on the system. It is also the expected behavior for the runtimes are going TO. This does not mean that the driver is not well that discovery of cameras, and you can test this by typing the name of the camera in the Session control (for example "cam0" for the first discovery of camera on the system).

  What we are looking for with this behavior, is for vision applications deployed to abstract the end-users camera selection process. Ideally, your code must list programmatically cameras with IMAQdx list Cameras.VI and then determine what device (based on the type of bus, serial number, model number, etc.) to the target. We are working on an application note paper that clearly explain with some examples, but the idea is similar to this example of community for NI-DAQmx devices: https://decibel.ni.com/content/docs/DOC-10014.

  I'm sorry for the current lack of documentation on these features, but without a doubt, we are working to provide examples useful and other items in the knowledge base at this address. I'll post a link to the content as soon as it is available.

  In addition, Vision Acquisition Software August 2014 f1 went live yesterday: http://www.ni.com/download/ni-vision-acquisition-software-august-2014-f1/4974/en/. The patch is also available through the Update Service, and it is strongly recommended that you upgrade if you still use drivers of August 2014.

  Kind regards

  Joseph

• If USB3 IMAQdX does not support a pixel format is at - it a way to make do, or am I hosed?

  We recently bought a USB3 HDSDI converter of Pleora Technologies (model
  IPORT HDSDI-u3).  This adapter is supposedly USB3 Vision and Genicam Compliant.  When I
  connect to my computer and open MAX it enumerates correctly as an IMAQdX USB3
  camera.  When I try to get the video, I can get video successfully if I use the
  following modes of pixel: mono8, mono10, mono10p.  If I try to use the
  color modes, I get an error 0xBFF69037 "no decoder available for pixel selected."
  format ".  I spoke with the support of Pleora and they said that NEITHER must
  supplor type pixels YCrCB to get this job.  The exact answer
  He has supported:

  "The list of pixel format that you see is the HDSDI XML file reading. Those
  are all the pixel format THAT is supported by HDSDI.
  Apparently MAX is not a decoder for the "YCbCr", that's why you got the
  error.
  You may need to talk OR to see if they support this format or not. »

  Here is the list of the listed indicating by MAX Pixel formats:

  Mono8
  Mono10
  Mono10p
  YCbCr601_422_8_CbYCrY
  YCbCr601_422_10p_CbYCrY
  YCbCr709_422_8_CbYCrY
  YCbCr709_422_10p_CbYCrY

  The first three (mono) selections work.  The last four give the decoder
  error.

  Y at - it any help you guys can give me to do this job?

  Hello

  IMAQdx supports various configurations of the pixelformats of YCbCr color space, but it seems that there no versions of Pixel Format Naming Convention new mode which explicitly list the exact color space (because there are several YCbCr color spaces). Decoders of YCbCr from IMAQdx are all followed the standard ITU - R BT.601 and support for 8-bit (10-bit variants are not supported).

  You can change your local cache of the file XML Pleora (C:\Users\Public\Documents\National-Instruments\NI-IMAQdx\Data\XML) and replace the enumeration name "YCbCr601_422_8_CbYCrY" by "YCbCr422_8_CbYCrY" (the older generic name that existed before the 601 variant). This should allow the pixel format to correspond to one of the known encodings of IMAQdx and be properly decoded.

  I'll file a bug report internal for the 'YCbCr601_422_8_CbYCrY' (and the rest of the formats similar to this question) added as an alias for good for the decoders we have so that "everything works" in the future.

  Eric