IMAQ IEEE 1394

Hi,
When am running my application in one of my client place am getting an error pop up saying (ERROR - 1074364412) occurred at IMAQ 1394 Grap.vi and possible reasons are NI-IMAQ IEEE-1394 : (Hex 0xBFF68004) Internal error. I attached the error screen also.Please help me in this
Attachments:
Tacho.JPG ‏142 KB

Similar Messages

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

Ni IMaq IEEE-1394 v2.0 plug/unplug/enumeration

The IMaq IEEE-1394 v2.0 Driver contains some new missed function's espec. the Camera plug/unplug and enumeration.
I can't find any example, how to use this functions correctly. The Cam. plug/unplug functions are impl. by the IMAQ1394 Occurence Config. This Vi needs a valid Session ID, but is there none camera attached or the valid Cam. are detached, this Vi fails.
In the future of my project, there are up to 15 Camera's attached, based on two PXI-8252 1394 Host adapters run's under Lv7.1-RT
regards
M.Funke
Applications Engineer

Dear Mr. Funke,
as starting point you can use the programming model of the imaq example ll occurence vi's, that ship with LabVIEW. Implement the imaq 1394 vi's in a similar order. Place a loop, in which you wait on the occurence.
Information how the imaq 1394 camera driver assigns interface numbers:
camX (where X is an integer, and the first one is 0) is the interface name and is specific to a single camera.
On Windows, the camera file is created when imaq1394CameraOpen is called (either through MAX or programmatically), and the imaq1394.ini file is updated. The imaq1394.ini file is created when the first camera is initialized. You can call imaq1394 Init with the interface name.
The camera order (cam0 vs. cam1) is determined by uuid (unique universal identifier) of camera. The lowest uuids are first. So if you plug in a camera, it will be cam0. If you plug in another one, it could be cam0 or cam1 depending on its uuid. If you have two cameras plugged in and you unplug cam0, cam1 will become cam0.
Regards,
Philippe Goetz
Applications Engineer, National Instruments

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

IMAQ IEEE 1394 Occurrence

Hi,
I am trying to get �IMAQ1394 Occurrence Config� to work for some time, and I don�t seem to have any success.
I am using a triggered acquisition, and although the �Frame Done� event has definitively happened (I can get and display the image using �get image�), my �wait on occurrence� does nothing but timing out.
I am using the 1.5 driver.
Has anyone managed to get this working on 1394? If so, could anyone be so kind to please post some sort of simple description or some simple example on this?
I have spent already too much time on trying to get this to work, and it is getting frustrating by now . I am starting to feel that I should have bought a camera with hardware �frame done� signal instead on trusting software to do-it...
Thanks a lot,
Sorin

Hi Phil,
Thanks a lot for your help. Your example does work, however I am still a bit confused over the occurrence functionality. I�ll explain first what I am trying to achieve:
My application involves Motion synchronised with Vision. Every time a sample is positioned in the right place, a trigger signal is received, which triggers the lighting and the firewire camera. I have a 10 ms exposure time, and after that it is safe to move again. One of the requirements for the application is guaranteed no missed frames; therefore I need to chain the imaging part with the motion part, instead of having a free run motion that just sends triggering signals.
Therefore what I wanted to do is:
1.Move
2.Wait on Frame done
3 On frame done get from a queue where to go next and start motion again
4 Get image and repeat.
The point of using occurrence for this was so that motion does not wait for the frame to be transferred in the PC memory, only waits for the exposure time, which is short (around 10 ms), where the total time is 133 ms / frame. Combining this with the chained motion/vision would imply that, in the case that the CPU is free and can process images faster that the motion, than everything would run at the maximum speed, while as soon as the processing part slows down for whatever reason, the whole system slows down. Just using buffers would not help in my case, because the system is being used on a factory floor and, no matter the buffer size, it will eventually get full.
However, if I am timing the time to �get image�, as I have shown in the attached example (your example with the timing code in it) I am getting values of 1 to 3 ms, which looks to me like the time to make an image copy in the memory, and nothing like the time to transfer an image over the firewire bus. If this is the case, it looks like using firewire cameras with the NI 1394 driver would lead to an unnecessary delay of 120 ms/part, and if you consider using this on the factory floor, and making many of these parts, it will soon ad up to a lot�
Please let me know if my understanding of the 1394 occurrence functionality is right or I am missing something. Also any suggestions on how this application could be optimised are very much welcomed.
Thanks a lot.
Best regards,
Sorin
Attachments:
IMAQ1394RingWithTiming.vi ‏99 KB

Synchro camera video ieee 1394

Hello,
I'm trying to synchronize 2 video camera Sony in fireWire using the imaq ieee 1394 library. I've seen it's possible to do with an external trigger but when I try there is a delay beetween the 2 pictures. Somebody can explain me why it does not work?
Thank you.

Hello Fredazerty,
Please see the documents below:
1 - Using an External Trigger for IEEE-1394 Camera Image Acquisition from Vision Builder for Automated Inspection
http://digital.ni.com/public.nsf/websearch/E6462CB483A403B686256D4A004CE313?OpenDocument
2 - Acquiring from Firewire Cameras using National Instruments NI-IMAQ for IEEE 1394
http://zone.ni.com/devzone/conceptd.nsf/webmain/a533e1e5a109cbce86256d8e00768814
3 - How to trigger a camera with 1394 drivers
http://forums.ni.com/ni/board/message?board.id=200&message.id=6729&requireLogin=False
Regards,
Sanaa T
National Instruments
Sanaa T.
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> http://www.nidays.fr/images/081110_ban_nidays09_468X60.gif

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

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

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

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

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

"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

IEEE 1394 Camera Not Visible in MAX

Problem Description :
I'm using the following hardware:
1. Texas Instrument OHCI Compliant IEEE 1394 Card ( Ratoc PCIFU2)
2. Basler 601f Camera ( NI certified)
(DCAM v.1.20 compliant)
Sofware :
1. LabView 7.0
2. Max 3.0
3. NI IMAQ for IEEE -1394 Ver 1.5
4. Vision Development MOdule 7.0
I am able to use the camera via Vision Assitant (7.0), but unable to see
the
camera listed in MAX. I have tried all the steps listed in FAQs.The driver
for
the camera is 1394imaq (i.e. all this has been checked).
I can run the 1394-Imaq vis & acquire images as well, but like i said no
camera listed in max ....
NI Software : LabVIEW version 7.0
NI Hardware : Other device
Driver Version :
OS : Windows 2000
Customer Info
rmation :
MK
[email protected]

Hello,
It looks like the MAX provider for NI-IMAQ 1394 may have been corrupted. This can usually be fixed by running a repair on the installer. You can do this by running the installer from Add/Remove Programs.
Hope this helps!
Best Regards,
Yusuf C.
Applications Engineering
National Instruments

How to grab two IEEE 1394 cameras simultaneously?

Is it possible to grab two or more firewire cameras simultaneously? I have two Sony XCD-X710 cameras and they are both connected in same card in PC. Grabbing works fine with only one camera, but when trying to grab two cameras simultaneously, the computer will crash. Sometimes it crash immediately and sometimes it takes few seconds to crash.
Used frame rate is quite low (about 3.75 fps).

It is definitely possible to acquire from two or more firewire cameras simultaneously, as long as you are not exceeding the bandwidth of the firewire bus (which you should not be at a frame rate of 3.75 fps).
What version of the NI-IMAQ for IEEE 1394 driver do you have? There were some issues with version 1.1 of the driver with certain cameras and simultaneous acquisition, and these were resolved in version 1.5 of the driver. If you have not yet upgraded to version 1.5, contact NI Sales at (888) 280-7645 for a free upgrade.
If you already have NI-IMAQ for IEEE 1394 version 1.5, please let me know and I would be happy to assist you further.
Best regards,
Dawna P.
Applications Engineer
National Instruments

IMAQ IEEE 1394

Similar Messages

Maybe you are looking for