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

Similar Messages

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

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

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

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

Can I link my two laptops using IEEE 1394 (Firewire)?

Hi,
I have a X31 and a X60 laptop. Both are running on Windows XP Pro and both have IEEE 1394 (firewire) ports.
I seem to read it somewhere that I can do a network link between two laptops via the firewire ports.
However, it does not work for me after linking them with a firewire cable.
Am I missing something?

Am I missing something?
You have to configure the IPs on the both side as with any other network adapters.
Alternatively you can set the internet sharing to the fireware adaper, on one side only so the pc with internet shared will acts as DHCP server and the other will atutomagically configure itself with a correct IP.

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

No "IEEE 1394 Bus host controllers" node in device manager

I have a new computer running Windows 7. It is functioning well, apart from the firewire card not being recognized. I can see that the BIOS does see the firewire card. Pages on the web offering advice on this kind of problems start their solutions with going
to the device manager and expanding the "IEEE 1394 Bus host controllers" node in the device tree. Only I don't have such a node. How can I get the "IEEE 1394 Bus host controllers" node to appear in the device manager?
Windows update reports that Windows is up to date.

This is one of many threads I came across googling roughly 'IEEE 1394 device not showing up in device manager'. After a lot of reading I never found a real solution - until I started piecing some things together. This is what I did and it works, seems very
simple, logical. Thought I should share it, hopefully save someone else the agony of searching and reading for hours.
Basically, what I think is or can be happening -- and I'm no expert at all -- is that there's miscommunication between the OS, the bus, and the device. The OS doesn't install the service for the bus unless the device is plugged in at startup (the external
hard drive, camera, or whatever), and sometimes it doesn't install the service even if the device is plugged in. Perhaps the device is supposed to send a message that starts the service - who knows. Maybe on older devices the driver isn't doing what it's supposed
to do, and perhaps you have no updated driver and can't get one.
In any event, I edited an entry in the registry that tells the 1394 bus host controller to start at OS startup instead of 'on demand'. After a restart, the bus host will load at startup, and when you plug your firewire device in, the bus host will detect
it and run normally... At least it works for me. Here's the instructions:
Go to search, regedit.exe, run program. This opens the registry.
Go to HKEY_LOCAL_MACHINE\SYSTEM\CurentControlSet\Services and find the folder that corresponds to the 1394 bus host you normally use or see in device manager. On my computer it's 1394ohci. You might have to do a little digging here to make sure you've got
the right service. There's actually 2 folders/entries in my registry that look similar. I used this one and it's working for me.
When I click on the 1394ohci folder it brings up a list of settings. For "Start," "REG_DWORD," the 'Data' value is probably going to be 0x00000003. That means 'start on demand'. I changed this to 2, which means 'start at startup'. To
modify value, right click on start, select modify, and type in 2. Here's a link to descriptions of this stuff: http://technet.microsoft.com/en-us/library/cc722564.aspx
That's it. Close the editor, restart, and the IEEE 1394 Bust Host controller\1394 OHCI Compliant Host Controller should show up in device manager. And when you plug-in your device, it should be detected. Depending on what driver you're using for the bus
host controller, you might see an extra entry popup in device manager (if you're using the 'legacy' driver). Otherwise nothing else pops up when you plug in your device. I guess it might depend on the device though. That's the way it is for me with an older
Acom external hard drive...
Hope this helps...

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

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

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

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

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

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.

Labview 7.0 and NI-IMAQ IEEE-1394 1.1

Similar Messages

Maybe you are looking for