firewire acquisition

Similar Questions

• CQI IMAQdx continues FireWire DVCAM

  Hello everyone,

  I have a (old) Hamamatsu analog interline CCD camera C5985 where images are digitized by a sony DVCAM DSR11. The digital video output is connect on PCI Firewire on the PC and a TV card

  With the acquisition of visoin Wizard, I continually get these images and get this kind of frame interlaced instead to get a homogeneous place

  

  It seems to show that a part of the image, no?

  How can I do to avoid this intertwining?

  Thank you very much!

  Hello AndGar,

  Thanks a lot for your attention and your response,.

  I install that update Vision CQI and all seem to be ok. I now have a seamless task as you can see:

  

  There are no interlacement now!

  There is also an analog video output (coaxial connector) on the camera C5985, whitch can coupled directly on a TV screen and the DSR11 with a Coaxial base / RCA adapter.

  Thanks again,

  Best regards

  KALAKUTA

• Sampling frequency for the output of an acquisition of data USB-6211 card?

  Hello-

  I use a CGI CMOS FireWire camera to read an interference figure, then using a transformed of Fourier transform spectral interferometery (FTSI) phase recovery simple algorithm to detect the relative phase between the successive shots.  My camera has a linear 28 kHz scan rate, and I programmed my phase retrieval algorithm take ms ~0.7 (of a trigger of camera at the exit of the phase). I use the live signal to control a piezoelectric stack, by sending a voltage single sample to the analog output of a data USB-6211 acquisition card.

  Send this output voltage increases the time of my loop 4 m, I would really like to achieve a 1 kHz or better sampling rate. Is the problem with my DAQ card or with the processor in my computer? The DAQ cards of NOR can support these speeds?

  Thank you

  -Mike Chini

  Hey Mike,

  With USB, your loop rate will be around or under 1 kHz, even on the best of the systems. USB has a higher latency and less determism PCI and PCIe. You can get rates AO one much better sample on a PCI card, potentially a PCI-6221. We have a few HAVE points of reference for targets of RT for PCI, / AO in a loop, you should be able to get similar performance in Windows, but if you do a lot other treatments may suffer from your local loop rates.

  Hope this helps,

  Andrew S

• DAQmx constantly firewire PCI card

  Hi all

  I have a map of acquisition data NI PCI-6221 here and use DAQmx and LabVIEW 8.6 to start some counter and tasks of the AO. Everything works very well. The problem is on the same PC, we use a firewire PCI to control the Aerotech motion stands. When the DAQmx tasks start Aerotech motion steps disabled! I guess there is a monitoring function on the update of the firewire card controllers and somehow NI DAQ travel that guard dog. We need to do some research more but thought I'd post today to see if someone has solved similar problems.

  TIA

  -Martin

  Just an update-

  Never really gone at the end of this problem of driver but worked around it by replacing the PCI DAQ card with a USB version.

  Now all the work as expected with zero code changes.

  -Martin

• Imaging Source DFG/SV1 acquisition card is not correctly recognized in LabVIEW 2009

  I have an Imaging Source DFG/SV1 frame grabber/capture card (I think that this example uses a Bt878 chip) that I am using with LabVIEW 2009 (Fall edition 2009 academic Site license), including elements of acquisition of vision (NEITHER Vision, NOR-IMAQ (4.3) OR-IMAQdx (3.4), etc.). I have all the latest sources of imagery support drivers and software for the Board of Directors (http://www.theimagingsource.com/en_US/products/grabbers/dfgsv1/ drivers: v6.0.3.0, IC Software v2.1 and IC Imaging Control v3.1) with drivers being compatible DirectShow. The DFG/SV1 is detected in MAX under devices NOR-MAQdx / DFG/SV1 / cam0 and I can grab and preview images, however to 320 x 240 resolution, I have a higher resolution camera and know that the jury is capable of greater resolution using IC software manufacturing and also via TWAIN with ImageJ software drivers. Interesteingly, if I try to acquire an image of the card purchase using the Vision Assistant, the DFG/SV1 card is not recognized as a card acquisition, but listed under IEEE 1394 or GigE peripheral, revealing with it being direct device that I can't understand. Despite this I can acquire images, but I am limited to 320 x 240 format and change the type of image (RGB, UYVY etc) causes an error. Once again, oddly enough, I can use "enter and select mode example VI" which should only be compatible with IEEE 1394 cameras.

  I'm not sure why LabVIEW is not seen this card properly, I contacted Imaging source who were also intrigued by the fact.

  Any information on how this could be resolved would be much appreciated.

  Thanks in advance.

  Hi OCastell,

  With this Council Imaging Source, the only interface supported with drivers of NI Vision Acquisition is through using IMAQdx DirectShow interface. It is possible that their DirectShow driver does not properly support all of the capabilities of their Council. Given that ICR software and TWAIN support can be routed to a different implementation of one of the DirectShow support, you can see the different features available. Unfortunately, you probably go through Imaging Source to determine why their DirectShow driver does not support the full resolution. You can confirm that it isn't IMAQdx this limiting trying other software such as Windows NetMeeting or AMCAP DirectShow and see what capture resolutions are listed.

  Because the DirectShow interface is managed by IMAQdx driver, it will not be detected as a framegrabber IMAQ using the IMAQ driver. This is expected since it fits in the same category as firewire and GigE Vision cameras and is supported with the IMAQdx driver instead.

  The "Grab and select the Mode" example VI isn't really specific FireWire, although he was certainly intended to highlight the various video modes that generally expose FireWire cameras. Since the DirectShow devices are similar and have several selectable video modes, it's why he's probably working. In any case, IMAQdx abstracts usually differences between all supported camera types and in general a single VI can run on all cameras IMAQdx-taking in charge unless you rely on buses or the camera-specific features.

  Regarding Vision Assistant marking the camera as 'IEEE 1394 or GigE', I think it's just an aesthetic issue (which may already be fixed in new versions). When IMAQdx was out, these are the supported types of cameras and so Vision Assistant was trying to say clearly what driver was used for the type of device. Now that IMAQdx supports a multitude of new interfaces (including DirectShow and some IP cameras) that the label is inaccurate.

  Finally, looking at the specs for this capture card, it looks like a standard reference BT878/848 model and then you could try potentially replace your Imaging Source driver with one here:

  http://BTWinCap.sourceforge.NET/

  I used this with a with IMAQdx BT878 capture card and can get it to capture an image full resolution (but of course, your results may vary...). It goes without saying that this solution using DirectShow is much more limited than using an industrial camera on 1394/firewire or a framegrabber IMAQ.

  Hope this helps,

  Eric

• How to detect the camera firewire on labview?

  I set up my camera IEEE 1394 Basler A 601F. It is detectable on MAX and video it is displayed by the wizard of vision. I have labview 8.2.1 installed with the kit of vision and movement. I need to get the stream in labview for furthur video processing. Should I have the Vision Development module for this?

  Furthermore, what is the process to get the video from a firewire camera in labview. It is similar to the video for USB cameras getting?

  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-fareast-font-family : « Times New Roman » ; mso-fareast-theme-font : minor-fareast ; mso-hansi-font-family : Calibri ; mso-hansi-theme-font : minor-latin ; mso-bidi-font-family : « Times New Roman » ; mso-bidi-theme-font : minor-bidi ;}

  Dear Asad,

  There are three different Modules in National Instruments Vision:

  1. Vision Development (VDM) module
  2. Vision Builder for Automated Inspection (VBAI)
  3. Vision acquisition software (SAV)

  You can perform a basic image acquisition, display and record requests with just the drivers included in the Service, but for any transformation or manipulation, you will need VBAI or VDM and more to GO. See this link for these products: what is the difference between software Vision VDM, VBAI and going TO?

  To see your camera in LabVIEW, I recommend using one of the examples to start shopping. In LabVIEW so you navigate to help > find examples > Input and Output material > IMAQ. You will find lots of well documented examples to help you get started. In addition, the 'Vision and Motion' that you have installed are not a Toolbox. It is a collection of functions that move depending on which driver you have installed.

  Thank you and have a nice day.

   

  Esmail Hamdan | Engineering applications. National Instruments

• Error-1074360293 (IMAQdx Timeout) after completing the acquisition for some time

  My vision in LabVIEW application makes several acquisitions and successful treatment but then acquiring (grab) suddenly fails with a timeout error (-1074360293, IMAQdx: timeout). The error does not when acquiring only the images.

  After that the error occurred that no acquisition is possible. Although LabVIEW is closed MAX Returns a time-out error. Only restart helps.

  some details of the material:

  3 controllers FireWire (1394-a)

  3 cameras connected to the first two controllers, one third (total of 7 cameras)

  Mode for all cameras: 1280 x 960 Mono 8 fps 7.50

  The bandwidth for a FireWire controller is sufficient. (Three cameras on a single controller are running without any problem).

  Consume the application memory is short before or after that the error occurs. But I can't find where exactly.

  Until the error occurs a few minutes until one and a half hour pass.

  More details will follow.

  Is there a FireWire or specialist in the vision that can help you?

  Greetings,

  SHB

  Change the driver it seems to fix the problem:

  "Compatible (legacy) 1394 OHCI host controller" (in German: "OHCI - 1394-Hostcontroller (alt) konformer")

  With this pilot test has worked for more than 66 hours without raising an error.

  Some Articles about:

  http://www.RME-audio.de/forum/viewtopic.php?id=9827

  http://www.myvideoproblems.com/ProblemPages/CannotCapture.htm

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

• Calculation of frame rates of acquisition image using the 7 Format

  So I finally got my Basler firewire (IEE1394b) camera to capture images at his rate max (120 fps).

  But to do this, I need to use the '7' Format.... which is a bit confusing to me.  When I use the '7' Format, I can't specify the frame (frames per second) rate.  Apparently, you only specify the parameters (length, width, color / mono) of the image and the size of the packets and a few other things.

  So, how can I calculate speed?  I need to know exactly how much time elapses between each image.  And it must be constant.  I can't have a different frame rate.

  NEITHER told I can calculate the frame rate using this equation:

  

  That comes from this article.

  But I am skeptical because the article also says:

  Please note that the time to transfer an image is slightly faster than the time it takes to acquire an image.
  

  People out there can clarify this for me?  Is the frame rate constant?  And then I actually calculate when using size 7?

  The rate will be constant.  It won't change from image to image.  The difficult part is to find what it is.

  Basler camera manual will tell you how to calculate the frame rate.  There are three different calculations, and gives you the slower pace is one you use.  These calculations are accurate enough, I think.

  Another possibility is to measure the frame rate, but that requires several seconds (or minutes) for a measurement precise.  The simplest method is to start a life-long and save a frame in time at the beginning, wait several seconds (or minutes) and save the time of another framework.  Subtract the chassis numbers, subtract the time and divide to get the frame rate.  With a wait of several minutes, it's extremely accurate.  To get the acquisition time, read an image whose value "Next Image", then save the chassis number and read the msec timer immediately after reading.  Using a flat sequence structure is probably the best to ensure that everything happens in the desired order.  If you loop playback, you will see real cadence cadence converge slowly.  Stop it when it is pretty accurate.

  In a program I wrote, I controlled the pace by setting the shutter exposure time.  I used the derived formula of the Basler manual for cadence and reversed to calculate the shutter speed.  This only works if you have another way to adjust the brightness levels (opening, lighting, etc.).

  Bruce

• I have an epson 1640 scanner xl says it is not connected via firewire

  Scanner Epson expression 1640 xl... cannot connect... error not says not connected... but it is, and I changed the firewire ports... error persists...

  Connected to what Mac with what operating system?

• Since macos sierra my isight FireWire doesn´t work with Facetime

  Until El Capitan works my FireWire iSight without problem with Facetime. After the upgrade to sierra, my iSight FireWire doesn´t work with Facetime, only with Photobooth!

  Fact the iSight camera please about this Mac-> System Report-> Firewire? What is the year/model of your Mac?

• I need to transfer my OS to iMac with firewire for Mac mini with love at first sight. Don't know what to do.

  Hello I have a 2010 iMac Core i3 3.2 GHz, 8 GB of memory, and El Capitan mid with a firewire 800 port that goes wrong. I just bought a Mac mini refurbished end of 2014 Apple, Core i5, clocked at 2.6 GHz with 8 GB of memory with thunderbolt 2 ports (but unspecified OS, I guess Yosemite 10.10 if Apple put the original on the renovated units OS) I want to use migration assistant to transfer all of the iMac with firewire for the Mac mini with the crush.  Can I use thunderbolt Apple firewire adapter for it? If this is not the case, what can I do? Any help would be greatly appreciated. Thank you for your time.

  Yes, you can.

  (144741)

• Transferring content via FireWire

  Shortly, I will receive a Macbook Pro. I will be to transfer the contents of my iMac via FireWire to the Migration Wizard help. Put online to get a cable, and that's when I came across a problem. They had all sorts of configuration such as 4-pin to 6-pin. Can someone tell me what configuration FireWire cable to transfer my content from my iMac to my Macbook Pro?

  It depends on the ports; a FireWire 400 on a Mac port is 6-pin, a FireWire 800 port is 9 pins. If a Mac has FireWire, one a Thunderbolt port instead of a port, use a FireWire 800 adapter Thunderbolt.

  (144603)

• Can I use a Thunderbolt Firewire adapter to connect my PowerBook to my MacBook Pro?

  I want to use my PowerBook as a hard drive of my MacBook Pro. Can I use a Thunderbolt Apple Firewire adapter to connect the two?

  Yes, if they have the appropriate ports.

  (144310)

• Compatibility «?» (Mac Pro Tower / Firewire / climax together, etc..)

  I take Logic Pro 9, but after looking at all the improvements for Logic Pro X, I can't wait to get up to speed.

  I like the look of the improvements to the plug-in; logic adding distance (not available for LP9?); Drum Kit Designer, synthesizer, etc.

  When he (LP10) announced that there is a flagrant limitation I had with my current set-up but I don't remember what the hiccup was... perhaps there is none and I could be good-to-go.  Can anyone confirm if and where I'm looking at compatibility problems?

  System: Mac Pro Tower (mid-2010) 2.8 GHz Quad Core Intel Xenon

  OS: 10.10.5 (Yosemite)

  Interface: Climax together - Firewire

  If I remember, the question I met was first introduced with the announcement of Logic Pro X was he needed El Capitan - which did not offer the divers "Core Audio" / support, which means that overall height (Firewire) would be uncertain if even not work at all.  "" Looking at the "tech specs" on Logic Pro X, it supports OS X 10.10.  That looks promising (if it in fact the issue with El Capitan and the lack of support for Core Audio driver still exists).

  Can I run Logic Pro X to Yosemite?

  Can I run overall height (FireWire) in El Capitan without the Core Audio Driver issues / Firewire?

  Thanks in advance!

  I must add, additional hardware, I am running is a UAD PCI card in the tower.