IEEE 1394 for IMAQ Deployment Issue

I have IMAQ Vision 6.0 and the IMAQ Vision Deployment Engine for Vision 6.0 , which installs the Vision 6 Runtime Engine on my target , but i also use IEEE 1394 for IMAQ in my application and the IMAQ Visiion Deployment engine doesn't seem to install/support that. Do I have to manually install IEEE 1394 for IMAQ onto my target in order to have my Application not be broken ? Also , what are the licensing requirements for Deploying Applications which contain IEEE 1394 for IMAQ vi's. I am using the Labview 6.1 Professional Development system. Thanks.

You do need to install IMAQ for IEEE 1394 separately. I believe you need to purchase a license for each computer you will be using it on. You should call NI or your local sales rep to get the details.
Bruce
Bruce Ammons
Ammons Engineering

Similar Messages

IEEE 1394 bus host controller issue.

Each time I boot my system (Tecra A9 S9021V) the IEEE 1394 Bus host controller device driver displays that it is disabled with an error code 22 (this taken from device manager).
From within device manager I manually disable the device, then re-enable the device. The device then displays that is operating correctly. The device driver is displayed as "Texas Instruments OHCI Compliant IEEE 1394 Host Controller". There are 2 files associated with the driver - (1) 1394bus.sys (Microsoft Corporation; version 6.0.6001.18000 longhorn_rtm 080118-1840), and (2) ohci1394.sys (Microsoft Corporation; version 6.0.6000.16386 vista_rtm 061101-2205).
I'm running Vista Business SP1 with all updates/patches.
Is there something I can do to get this device to start up correctly?
Thank you!

Tecra A9-S9021V
Each time I boot my system...the IEEE 1394 Bus host controller device driver displays that it is disabled with an error code 22 (this taken from device manager).
What is the exact message that appears when you boot? No paraphrasing.
What did you change about the time this started?
Can you do a System Restore to before the trouble began?
What is System Restore?
-Jerry

NI-IMAQ for IEEE 1394 hardware compatibilities

Need to check if the following camera can work with NI-IMAQ for IEEE 1394?
http://www.ptgrey.com/products/dragonfly/index.html
thank you
Attachments:
dragonfly.pdf ‏1052 KB

If you look at How Can I Tell If My IEEE 1394 (Firewire) Camera Is Supported by the NI-IMAQ for 1394 you will find the dragonfly listed there.
You will also find a reference to Digital camera specification: 1.3 in the camera data sheet which confirms this.
Hope this helps!
Amaury
NI Applications Engineer

"Insufficient resources for this video mode" error in IMAQ for IEEE-1394 1.1

I'm using 3 Sony DFW-X700 cameras (1024x768 YUV 4:2:2) and 1 Sony XCD-X700 (1024x768 8-bit mono) connected to 2 IEEE-1394 adapter cards (3 ports each). I'm running LV 6.1 on WinXP Pro PT.
I've tried several acquisition modes, and the only one that works fine is 'continuous acquisition', using 1 buffer per camera. The problem is that I can only setup 2 color cameras and 1 mono camera. If I try to setup 3 color cameras, I get an 'insufficient resources for this video mode' error. I would like to know if it's possible to configure more memory for the acquisition buffers under IEEE-1394 so that I can avoid this error.

Habil,
You might want to try to lower the frame rate of the cameras. This error is caused because the driver is able to allocate only part of the firewire bandwidth for your image acquisition, and a three camera color acquisition requires a huge amount of bandwidth. This is currently an issue that our R&D department worked this period and is going to be resolved in the next release of the driver. This release should be ready in one month. Good luck!
Nestor.
Nestor
National Instruments

NI-IMAQ for IEEE 1394 camera

Is it possible use a Sony DCR-TRV33 Digital camcorder (new product) with Labview and IMAQ driver?
link: http://www.sonystyle.com/is-bin/INTERSHOP.enfinity/eCS/Store/en/-/USD/SY_DisplayProductInformation-Start;sid=O4wBNalZKM0BQZc08S8LPuZXzYU9CfK8bpk=?ProductID=eXAKC0%2eNUwAAAADzQ65E%2eteI

Bruce Ammons wrote in message news:<[email protected]>...
> The Sony video cameras will not work with the IMAQ for IEEE-1394
> drivers. The format that the video camera sends is compressed and is
> not compatible.
>
> You might have luck with some other methods, though. I think Irene
> He's IVision toolkit provides a method for video input from devices
> such as internet cams or video cameras using VFW. There are one or
> two other methods out there, also. I haven't needed to use a Sony
> camera, so I haven't tested any of these.
>
> Bruce
I just got it working with DV camcorder today. But I haven't update my
website. I need to do a final test over this weekend. On next Monday I
will post an update in m
y website. So far I've tested on Cannon ZR45MC
DV camcorder and it worked fine. I can capture the live video or tape
from the camcorder through firewire and sample the image data out of
it. And was able to remote control the recording action.
Irene
www.geocities.com/irene_he

NI-IMAQ for IEEE 1394 cameras under LabVIEW 6.1

I just purchased this driver for Firewire cameras and got the latest version 2.0 that seems to only work for LV 7 and higher. Which version works for LV 6.1 and where can I get it? (Older versions of these drivers don't seem to be available under the driver pages at ni.com in the usual place.) I suppose i need to "downgrade" now. Any insights?

Hello bernhardschnurr,
Thank you for using our discussion forums. You will have to use NI-IMAQ for IEEE 1394 cameras ver 1.5.3 or earlier for support for LabVIEW 6.1. These drivers are not available for download on our website. I would recommend contacting your local NI support and they can help you get these drivers. Please visit http://www.ni.com/support/ and choose to phone NI.
Regards,
Nipun M
Applications Engineer
National Instruments

Missing camera attributes with the NI IMAQ for IEEE-1394 driver

I'm using an ORCA-AG and the IEEE-1394 driver. When i look at the camera attributes (either with MAX or the attribtue inquiry vi.) i can see just some of them (brightness, shutter,...). I have tried the ORCA-ER, which has the same attributes, but uses the PCI-1424 framegrabber. Using this camera i can see and modify more attributes (light mode,...). How can i modify them with the IEEE 1394 driver?
I also have another problem. When i use 1x1 binning the image must be 8bits, if is use 16bits, max cannot aquire the image (timeout error). Does anyone have the same problem?
Thank you very much.

Some non-standard attributes can be modified by directly reading and writing to the memory of the camera. Your camera manual probably has memory locations listed for the different attributes. You can get to these using the low level firewire routines. I have done it once or twice.
Bruce
Bruce Ammons
Ammons Engineering

Attempting to control Sony DFW-VL500 via IMAQ IEEE-1394 and LabView 7.0

I'm attempting to get images from a sony DFW-VL500 camera. I defined it as a device in MAX 3.0: the grab and snap functions seem to work. However, I cannot save video (only still images work).
This is a non-issue since what I would like to program in Labview 7.0 is to preview a continuous image and then snap individual frames. However, I keep incurring a -1074364408 error. Has anyone been able to get a functional VI that grabs images with this camera? Furthermore, is there a way for me to control the Zoom and Focus via LabVIEW? Any help will be appreciated.

The error you are receiving is a "Function not supported error" - which function does this error occur at? Make sure that your camera supports this feature and that you are calling it correctly.
I do know that this camera is supported by the NI-IMAQ for IEEE-1394 driver, version 1.5. If you don't have this latest version, you'll want to update that - although since it is not a free download, you'll have to call in to NI to get it.
In order to program what you are discussing, take a look at the following linked example program.
http://sine.ni.com/apps/we/niepd_web_display.display_epd4?p_guid=B45EACE3E1DB56A4E034080020E74861&p_node=DZ52490&p_source=External
You'll have to replace the regular IMAQ functions with 1394 functions, but other than that it should be th
e same.
Hope this helps -
Julie

Labview 7.0 and NI-IMAQ IEEE-1394 1.1

I upgraded to Labview 7.0 and have NI-IMAQ IEEE-1394 1.1
Is there a compatibility issue between these two? The data type for IMAQ Image Create in 7.0 is different than in 6.0 and also different from IMAQ1394 Get Image.
Is there a solution to this?

Hello.
There is a possibility that you are having some issues due to driver incompatibility problems. The current version of the NI-IMAQ for 1394 driver is 1.5.3. The following download page will take you to the update to 1.5.3, but you must have 1.5 or higher to run this updater.
In your case, you should probably call in to your local inside sales representative and request your free upgrade to 1.5.3 on CD, or you could go to http://www.ni.com/advisor/ to go through the upgrade advisor for your software.
I believe that with a fresh installation of the latest driver, your issues should
go away.
Regards,
Colin C.
Applications Engineering
Colin Christofferson
Community Web Marketing
Blog

IEEE 1394 insufficient resources issue

We currently have a CVS-1454 with two cameras performing inspections. Due to circumstances with the inspection and machine, we are trying to move the inspections to the computer that is currently communicating with the CVS. We are getting the error "The selected IEEE 1394 camera could not be initialized because of insufficient resources on the IEEE-1394 bus". This error is only happening in Vision Builder. It is not happening in MAX.
The system specifics are: the PC is running XP SP3 with a PCI-8252 card. There are two Basler scA1390-17fm cameras performing the inspection. The cameras are using Format 7, Mode 0, 1392x1040. The PCI card is new out of the box, the cameras are a couple of years old. VBAI version 3.5, LabView 8.6, MAX is version 4.6.2.
I found the various articles on NI.com addressing this issue, but the recommendations have not had an effect.
Framerate & Packet size: In MAX the frame rate can only be set to 100Mbs. Reducing the packet size has no effect. It was set at the default to 1024, but we lowered it to 200 with no effect.
We installed the AVT Bus Driver Package, but when we switched to the AVT bus driver, the bus went away in MAX and then Windows went through the found new hardware wizard and we were unable to get the cameras to show up correctly in Windows Device Manager, nor did they ever show up in MAX. All the documentation I've seen looks like we should not need to install additional drivers for the Basler cameras.
The machine does not appear to have Hotfix 885222 installed, but I was contemplating trying to run this update anyway: http://support.microsoft.com/kb/955408
Alternate video modes: We tried to set the cameras to any other video mode. We can put one camera at some insanely small resolution, but then the other camera still doesn't work regardless of the video mode.
I hope I've put all the details out there. Any thoughts? Should we need to install anything else after switching to the AVT bus driver? I was hopeful that would solve the problem.
Thanks,
Paul
Solved!
Go to Solution.

I concur with Brad that your issue is surely the famous Microsoft issue whereby XP SP2 and SP3 downgraded potential throughput to S100, requiring either rollback to the SP1 1394 driver from Microsoft, or upgrade to Win7 where they finally fixed the problem.
Or using a substitute Microsoft compatible replacement 1394 driver, such as that offered by AVT.
But I'd respectfully differ with Brad that re. whether the AVT driver "worked right" or not... as it was only designed to work with AVT cameras - and will not work with Basler cameras. That was an intentional design feature. Or constraint, depending on one's perspective. ;-)
Scott

IMAQ AND IEEE 1394 problem

When I use IMAQ vi's to acquire and process an image from a 1409 board and a standard ntsc camera ,my IMAQ vi's for IMAQ Clamp Horizontal MAX and IMAQ Find Vertical Edge work fine and display the overlay information properly using IMAQ WindDraw. When i run the same application using the setup and acquire vi's for IEEE 1394 and a firewire camera , when i show overlay information from the Edge detection tools ,the overlays are never refreshed , meaning the IMAQ WindDraw output window Image contains every overlay , it never overwrites the others with the current overlay. The screen becomes filled with the overlay information and cannot be cleared out. Why is this ? How to work around this ? The show search line can also be turned on and shown in
the window ,but when you turn them off ,they also stay onscreen. This behavior is not that way when I use the framegrabber/ analog camera configuration.

It sounds like IMAQ for IEEE 1394 does not clear the overlay information when you reuse a buffer.
The simplest solution would be to use IMAQ Clear Overlay immediately after the image acquisition. This will remove any existing overlays that were left over from the previous image.
Bruce
Bruce Ammons
Ammons Engineering

Resource Allocation for IEEE 1394 (Firewire) Cameras in Triggered Mode

In this article:
Resource Allocation for IEEE 1394 (Firewire) Cameras in Triggered Mode
http://digital.ni.com/public.nsf/allkb/ED092614FCCC900D86256D8D004A3B0C
it says "The Bytes Per Packet value represents the number of bytes that are transmitted at consistent 125us intervals on the FireWire bus during image acquisition" and the reciprocal of the 125us value would seem to be the source of a value of 8000 in a subsequent formula used to calculate the frames per second.
Is this 125us value independent from the firewire bus speed or a function of it?
If it is a function of bus speed, how does it vary with speed?
(Is the 125us value for 400Mbps and 250us for 200Mbps?)
Thanks!

Hello Warren
Thank you very much for getting in touch with us. Although the Firewire standard itself is not technically supported by National Instruments, I will do my best to assist you. I am currently referencing the IEEE 1394 documentation. From what I'm reading, I do not believe the 125 microsecond value changes. I have copied and pasted the paragraph of interest under Bus Arbitration from a document that I referenced:
The arbitration mechanism gets more complicated when isochronous devices are connected on the bus, because those devices have already been guaranteed bandwidth. Each arbitration round is approximately 125μs long, so bandwidth is allocated as a portion of the 125μs interval. The root node broadcasts (sends a message to node 63, the broadcast address) a cycle start packet, which begins the arbitration round. All interested nodes send an arbitration request as before, and the winning node is still the node closest to the root. After .04μs of bus idle time, the remaining nodes arbitrate for control of the bus. Once each isochronous node has completed its transaction the time remaining in the 125μs interval is used for asynchronous transactions. Up to 80% of the bus bandwidth may be allocated to isochronous transactions and the remaining 20% is left available for asynchronous transactions.
The original document can be found here:
The FireWire Serial Bus and its Implementation
I, unfortunately, cannot claim to be an expert on the IEEE 1394 standard but from what I've researched, the 125 microsecond time allocation is standard and bandwidth is then allocated accordingly. I may recommend consulting IEEE 1394 Trade Association (http://www.1394ta.org/about/Contact.html) for more in depth information. Please let me know if this is sufficient or if I can be of further assistance. I will do everything I can to ensure that your issues is resolved.
Have a great day!
Sincerely,
Greg S.

Firewire to Thunderbolt adaptor. 6-pin IEEE 1394 firewire for video transfer

Will the Apple Thunderbolt to firewire adaptor work with a IEEE 1394 6-pin firewire for video transfers?

You'll need a Firewire 800 (9-pin) to Firewire 400 (6-pin) adapter or cable, but yes, it should then work.
Regards.

W520 Replace DVD with another Hard Drive and IEEE 1394 spec for music recording

To increase the performance, I am taking the 160 GB SSD instead of the mechanical drive. Obviouslt, I need more space than this. I don't care about the DVD rom. It can't play blu ray anyway. Is it possible to replace the dvd drive with a hard drive? Where can I get a replaceable drive for this? What do I do with the DVD? Can I sell it back?
I need to do music recording with this. I was wondering about the IEEE 1394 spec; the latency etc. If I remember correctly the W510 IEEE1394 was very good, probably was manufactured by Texas Instruments. I could not find anything about it anywhere. Not even here: http://www.lenovo.com/psref/pdf/tabook.pdf
Also, a bit worried about the sound card. How good is it? Did anyone use this laptop for music recording?

hey udvranto,
with regard to this, i would suggest contacting tech support via the number listed in the link below to check if it is possible to replace the dvd with your harddrive.
http://www.lenovo.com/contact/us/en/
on the part of the soundcard, I believe it is good for music recording. Though this really depends on the software that you're going to use to record.
WW Social Media
Important Note: If you need help, post your question in the forum, and include your system type, model number and OS. Do not post your serial number.
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"!
Follow @LenovoForums on Twitter!
Have you checked out the Community Knowledgebase yet?!
How to send a private message? --> Check out this article.

Dummy DV (IEEE 1394) grabber for Mac OS?

Is there some "stupid" utility for Mac OS, which would allow to grab video from DV camera via IEEE 1394 port without touching camers's controls?
I'm trying to use AV->DV dup function on my Canon Elura camera, when the analog signal is just translated to DV out. But iMovie is a control freak: it won't start importing without starting the cassete...
I'm thinking about something similar to dvgrab for Linux...

Utility...which would allow to grab video from DV camera
via IEEE 1394 port without touching camers's controls?...
iMovie is a control freak: it won't start importing without
starting the cassete...
I think there is some clarity missing here.
How one can get any signal, digital or otherwise, from a tape without actually playing the tape?
Or do you mean play the tape to get the DV out signal, but without capturing a MOV file on your HD?
In iMovie, clicking the play button will roll tape so you can view it onscreen, but it will not import when you do that.
Using the play button on the camera will also display within the imovie screen.
So my warped logic is telling me:
Presuming hitting the AV>DV button on your camera rolls tape and sends the digital stream out...it will beginn to display in iMovie, at which time clicking the import button should capture the digital stream the camera is outputting, which is the goal you are trying to achieve, right?

IEEE 1394 for IMAQ Deployment Issue

Similar Messages

Maybe you are looking for