1394 MAX

Similar Questions

• How can I get a list of all IEEE 1394 defined in MAX cameras?

  I can use the DAQmx_System:Global_Channels property node to get all global DAQ channels defined in MAX, but is it possible to do something similar to get all the names of camera?  I am after all especially the IEEE-1394 cameras, but would be happy with a list of all the cameras to begin with.  Is there a property node that I'm over looking?

  Hi, Christopfer,

  You can use IMAQdx list Cameras.vi for a list of all the cameras. (of course, here I assumed that IMAQdx used to connect to the IEEE-1394 camera).

  Another way is utility CameraValidator.exe with key/enum - this will also list the available cameras.

  Best regards

  Andrey.

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

  
  

• 1394 camera does not appear in MAX

  Hi, I have a new AVT Pike 1394 camera that deserves to be supported by LabView. It works fine with the software of the seller. However, it does not appear in the action and even if Automation is expected to be taken in charge.

  I'm under LabView 8.6 with NOR-IMAQ 4.1 and NOR-IMAQdx 3.2

  Any suggestion how to fix this annoying problem?

  Hello

  Please make sure that the Microsoft 1394 adapter driver is installed and not the driver fix (is installed from the FirePackage) no more.
  You can use the 'install or remove the 1394 driver' tool from the FirePackag directory or manually in the Device Manager.

  When the camera makes its appearance in the device as a device of imaging Manager, it will also be available in MAX.

• My integrated Webcam is recognized by MAX but not as the IMAQ device

  Hello

  I use with 2014 LabVIEW IMAQ 14 and IMAQdx14.

  I am able to use my webcame MAX both in the Vision Assistant, but when I am trying to generate vi, in the wizard, IEEE1394 Imaging is grayed out.

  When I am using triggered image acquisition and select cam0 as the name of the interface (name of my camera to the MAX), I get the error code:-1074397163 (NOR-IMAQ: the session or the interface passed is not valid.)

  In MAX, I can see and use my camera, but it appears directly in the devices and Interfaces (and not under devices NOR-IMAQ)

  I can't find out if it is compatible live show... Is this to say that my camera is not supported by IMAQ? Is there a way to check whether LabVIEW?

  Thank you

  Karol

  Hi Karol,

  Since you are able to use the camera in MAX, it is DirectShow compatible. The reason why you get this error, it is that your device is not compatible with the IMAQ driver. Instead, you should be using the driver IMAQdx and corresponding IMAQdx live. Once you use those, you should be able to control in LabVIEW. It isn't an IEEE 1394 device either, so I think that it is expected that all options for this would be grayed out. Hopefully that should get you going in the right direction, but please post again if you have problems with the generation of VI you.

  Thank you

  Katie

• FireWire 1394 camera problem

  Community salvation OR,.

  I want to use my guppy (FireWire 1394 connection) of Allied vision camera, but I came across a connection problem. I use this card FireWire (http://www.belkin.com/IWCatProductPage.process?Product_Id=428618), but according to the installation, check, this card is properly installed.

  When I plugged the camera Vision Builder AI 2010 and it wouldn't recognize my camera so I went for the problem that I found at my material properties. When I go to the properties of the camera, he said: "this device does not start. (Code 10).

  I've been looking for a solution, but I'm not a genius when it comes to this. So is there maybe someone who can help me with this problem.

  Concerning

  Ruts

  Here's an update after a whole day looking for a solution.

  I currently see the my card PCI IEEE 1394 (old map 2001) who has a complaint OHCI driver (I guess that's the default windows driver). I also see the camera under my hardware, but it shows with a small sign of error that says "device will not start (Code 10)". I also installed the driver NOR can I see in my MAX of NOR, but non-material to my PCI IEEE 1394 card.

  I also discovered that when I had a unibrain driver installed (in collaboration with the complaint OHCI driver) my camera simply don't appear in my hardware.

  That maybe I need to connect the driver OR with my IEEE 1394 card (I tried to do, but I could not)?

  In the attachments you will find a photo that shows my material.

  EDIT:

  Don't bother the problem is resolved. I think she had need of some time after uninstalling the driver unibrain to see the cam OR max. For those who have the same problem: just install the default windows driver (OHCI complaint) and install the NOR-IMAQ for IEEE 1394 driver (think my problem was the additional Unibrain driver).

  Concerning

  Ruts

• FireWire camera works to the MAX, but not in LabView

  Hello

  I use a 1394b (grey Grasshopper Point 14S5M-C) camera connected to a 1394 bus controller. In MAX, the camera works fine, but it will not work with all files of 1394-example LabView. These allways throw the error "NOR-IMAQ IEEE-1394: (Hex 0xBFF6800F) attribute not supported by the camera" even if some of these example like "grab.vi" files no attributes are defined at all. On the same computer, another device (Point Grey Scorpion 20SOM, 1394 (a) works without any problem.

  Can anyone help?

  Hi Christian,

  Thanks for this tip, this is the reason. I was unintentionally using the IMAQ instead of example IMAQdx files. With IMAQdx it works now.

  Best regards

  Karl

• Problem of lack of resources for IEEE 1394

  We currently have a CVS-1454 with two cameras inspections.  Due to circumstances with the inspection and machine, we try to move the inspections to the computer that communicates with the RESUME.  We get the error "the IEEE 1394 camera could not be initialized because of the lack of resources on the IEEE-1394 bus".  This error occurs only in Vision Builder.  This is not the case in MAX.

  The specific features of the system are: the PC is under XP SP3 with a card PCI-8252.  There are two cameras from Basler scA1390-17fm of the inspection.  The cameras are using the 7 Format, Mode 0, 1392 x 1040.  The PCI card is new out of the box, the cameras are a couple of years.  VBAI version 3.5, LabView 8.6, MAX is version 4.6.2.

  I found the articles on NI.com addressing this issue, but the recommendations have had no effect.

  1. Package size & framerate: in MAX speed can be set on a 100Mbs.  Reduce the size of the package has no effect.  It has been set to the default value to 1024, but we lowered it to 200 without effect.
  2. We installed the driver of Bus AVT Package, but when we went to the driver of the TRA, the bus went to the MAX and then Windows through the new hardware wizard found and we couldn't get the cameras is displayed correctly in the Windows Device Manager, nor did they ever appear in MAX.  All of the documentation I've seen looks that we should not need to install additional drivers for the Basler cameras.
  3. The machine does not have hotfix 885222 installed, but I contemplated trying to run this update anyway: http://support.microsoft.com/kb/955408
  4. Alternate video modes: we have tried to put the cameras to any other video mode.  We can put a camera in an incredibly small resolution, but then the camera still does not work regardless of the video mode.

  I hope that I put all the details there.  Any thoughts?  Should we need to install anything else after the passage in the AVT bus driver?  I was full of hope that would solve the problem.

  Thank you

  Paul

  I agree with Brad, your question is probably the famous issue of Microsoft that XP SP2 and SP3 downgraded a potential to S100 speed, requiring to be restore the driver 1394 SP1 of Microsoft, or switch to Win7 where they finally solved the problem.

  Or by using a substitute 1394 Microsoft compatible spare driver, such as the one offered by AVT.

  But I differ respectfully with Brad that re. If the driver AVT 'worked right' or not... as it was only designed to work with AVT cameras - and will not work with Basler cameras.  This is a deliberate design feature.  Or constraint,'s point of view.  ;-)

  Scott

• AVT Marlin IEEE1394 camera not presented to the MAX

  Hello world

  I have an existing PXI system running with Windows XP, a camera IEEE1394 and IMAQ for IEEE 1394 and NOR-Vision software. Which works very well. Now, I am forced to upgrade to Win7 and I try to run again...

  I have an AVT Marlin IEEE 1394 camera connected via an ExpressCard-FireWire adapter to my PXI system. The adapter is displayed in the Windows Device Manager under the element in the tree 'IEEE1394 Bus Hostcontroller' as 'Compatible OHCI Instruments1394 hostcontroller Texas', the connected camera appears under the element in the tree 'NOR IMAQ interfaces' as "Digital of NI - IMAQdx IIDC camera". But when I opened NOR-MAX, the camera is not shown here. Under the item of the tree 'Devices and Interfaces' there are only the chassis PXI, COM, LPT, PCI-CommunicationController and NetworkDevices, but no camera. I installed the AVT driver package and got access to the camera with their demo tool, but with driver AVT camera even does not appear in the windows Device Manager. Is however must work with IMAQ.

  Help, please!

  ---

  PXI-8105

  Windows 7 SP1 (32-bit)

  DeLOCK adapter ExpressCard-to-FireWire

  AVT Marlin F-033_C

  MAX 5.5

  NEITHER Vision acquisition 2013.09 assessment

  4.3 IMAQdx

  I wonder if this could be a manifestation of a recent problem that arose. Can you try to rename "niu3v.dll" in C:\Windows\SysWow64 and then closing/re-open MAX?

  Eric

• Interface not found error when using Snap example for Firewire (IEEE 1394)

  Recently, I installed a SONY XCD-SX910 in interface with Labview 8.2.  When you choose the driver, only the Legacy driver would work for the installation of Firewire (R) (or IEEE 1394).  After installing the driver, I have images of the inteface to MAX.  However, when you attempt to trace through the example of Snap 1394 legacy since the document installation IEEE 1394, I get the error "Interface not found".  I tried a few iterations to try to name the camera as "cam0' (the name given to the camera to the MAX) and" cam0: SONY XCD-SX910.  However, the error continues.

  What should I name my camera so he could find the interface?  Will there be another underlying problem that is not obvious?

  Control of IO is not something that will be filled when you use the Legacy 1394 driver. If you use IMAQdx as your driver, it will fill. Thus, when you use the Legacy 1394 driver, you have control of the chain on your façade. When you use control of the chain, you must set the name of the camera as "cam0" as you did before. As long as this corresponds to what is able & Automation Explorer, you should be good as long as MAX uses the same driver that you are trying to use.

• Rate question frame IEEE 1394

  Dear all,
  Currently, I have a problem with NI MAX and my software that uses niimaqdx for camera firewire 1394.
  I use HAMAMATSU C10600 (ORCA R2).
  When I use the software HCImage that origin of the HAMAMATSU Corporation, I can get good pace which they spoke.
  But in MAX, it does not work properly. For example, rate of rebar binning 2 x 2 is 15.6 Hz. But in MAX, it's only of 10 Hz. I tested binning settings. In Max, it can no more than 10 Hz.
  And I tested all firewire cameras. It has the same problem.
  But camera PCI card does not have this problem.
  Please let me know the solution for this.

  Sincerely,
  Taiyoon Lee

  Hi Taiyoon,

  First of all I suggest you check the camera settings in MAX to ensure that there is no maximum set of frame rates. In addition, you should check to ensure that the duration of exposure and shutter speeds are set so that the highest frame rate is possible. I recommend you take a look at this article in the knowledge base , which covers some troubleshooting operations when the camera acquisition rate is lower than expected.

  Article:

  "High refresh rate may not be achieved because the camera sends all executives. To achieve the maximum frame specified for these cameras, the shutter speed must be increased so that each image can be completed on time. It is an attribute that can be adjusted in Measurement & Automation Explorer (MAX). In addition, make sure that the camera is in the correct video mode. Several times for a camera reach its specified maximum frequency, it must be in Format 7 mode. »

  I hope this helps!

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

• How to assign the original number of camera to the MAX for the replaced firewire camera

  I have 8 cameras 1394 a (cam0 to cam7) on a machine and cam3 went wrong.  I cut and pasted the cam3.id and cam3 configuration file into a temporary directory.  I plugged the replacement unit and MAX assigned cam8.  How can I change cam8 to cam3?   In the meantime, I opened cam3 configuration file and copied/pasted content in the cam8 config file.  I then changed references in my software VB6 cam3 to cam8 database.

  Hi Dan delphi,.

  You right-click on the camera of MAX and select "Rename." Then select cam3 or whatever ID want you.

• E3000 Max Throughput for internet and USB NAS

  I ran some tests to see what I can do to speed to the interenet and disk NAS.

  I have a NIC card (1394) and the max connection I get East of 400 MB/s. The card is supposed to be the card 10/100/1000 and E3000 is the same thing... so why can't connect me to 1000?

  Transfer of Max that I get to my NAS is 64-80 Mbit / s is there a way I can get this to be faster? I have a 1 TB western digital disk attached.

  If I went with a NAS like Synology BYOD system could get faster transfer speeds if the NETWORK card on the system was a 10/100/1000?

  Thank you

  Scott

  Make sure that the Ethernet cable is connected to the router to the computer is a Cat6 cable, then you will get 1000 Mbps data transfer speed.

• MacBook Pro (15 inch, end 2013) with MacOS Sierra 10.12: kernel_task maxing out CPU with external display

  I have a maxed out end 2013 the MacBook Pro Core i7 to 2.6 GHz, 16 GB of DDR3 RAM, 1 TB SSD, NVIDIA GeForce GT 750 M 2048 MB, Intel Iris Pro 1536 MB.

  Also, I have a DELL P2415Q Display 24 inches (3840 x 2160) using Thunderbolt, are involved through the headphone jack and use a USB for lightning to recharge my iPhone.

  I upgraded to macOS Sierra the day he is released and had no problems until this morning. I unplugged my external screen and speakers and used my laptop for about 15 minutes, the battery, and then returned to my office and plugged my Thunderbolt, rear speakers display in and my CPU shot at 100% and never came back down. My Mac is essentially useless because kernel_task is eating all my CPU and to prevent another asks to enter the CPU.

  I have since audited equipment - everything was fine, reset the NVRAM and I tried to erase IOPlatformPluginFamily.kext .plist files but I couldn't on my Mac (trying to follow this guide, started in Safe Mode and everything then went to try and find the file and my Mac just does not have it). When my external screen is plugged if I'm doing anything CPU intensive (videophone, opening of Chrome, etc.) then my kernel_task gets mad again, and the only way to move is to unplug my screen. Connect my iPhone to charge the tips also my kernel_task as well. I followed my internal temperatures, and nothing was out of the ordinary, to cold currently at about 140 °.

  At this point, it seems that any time that puts something on the charging system and increase the temperature internal internal components of my Mac kernel_task maxes my CPU, which brings my Mac to its knees.

  Any ideas how to fix? Is this just a major bug in 10.12?

  Hi, Trent L.

  Try this - problems with macOS Sierra? This fix can help you.

  He got rid of all my macOS strangeness of the Sierra.

  Hope this helps,

  -BrainSel