IEEE1394

I have an IBot Firewire WebCam. This camera is not detected by the
measurment and automation tool. There it can't by used in labview.
Is there any way to make this camera work in labview?

"Brad" wrote in message
news:101-50650000000500000092140000-980565836000@quiq.com...
> National Instruments is coming out with Firewire drivers soon for
> cameras. You can buy these drivers (by the end of Feburary I believe
> ~$1500), and once these are installed, the camera should appear in
> MAX. This Knowledge Base describes the cameras that will be supported
> by this driver:
>
Driver software is usually shipped with hardware and is useless without it.
This driver software will be used without NI hardware. How will the licence
agreement look like. If we will build the executable that will include this
driver, will there be some inexpensive run-time licence.
Bojan

Similar Messages

[nForce] MSI K7N2 Delta ILSR; bios, neither windows recognize IEEE1394

Hello,
Since 2 years I have used a msi motherboard. Now since I dont have IEEE1394 of an external card anymore (Audigiy), i tried to connect my digital camera with the IEEE1394 to the motherboard. Rebooted my pc, windows doesnt recognize new hardware. i'm going to look in the bios, and see that my bios (bios 7.8) is different from the one explained in the manual (see pic). I tried to downgrade my bios to 7.2, to know if it is the 7.8 version that has the problem. but it was the same, no option for IEEE1394.
Normally have you this:
But I dont see this option for the IEEE1394 in my bios....
Thx in advance for helping me

Quote
He has confirmed the ports are present on the board....
I have seen this in earlier Nf2 Pre Delta boards where it was there but if you had disabled it, and then flashed the BIOS, it would dissapear. The only way to get it back was to flash to an earlier version, make sure it is enabled, then you can flash to the latest.
That is why I always clear the CMOS when starting a new build. You may have a board that may have been fiddled with, believe it or not, it does happen from time to time.
Have you tried the Default BIOS Settings Option in the BIOS? Perhaps you loaded the Performance option and that is why it is hiding?
this worked, thx a lot

How to trigger Camera usinf IEEE1394

Dear Readers,
I am writing a code to trigger the camera externally.
i am using the sony fire wire camera model no: XCD-X710CR. It has two input connectors. one is for the cable from PXI express which we uses IEEE1394, The another one is for Ext trigger.
I wrote a Vi to snap an image through labview. I added Externall trigger.vi immediately after Initiation.vi. In that code, whenever i set the trigger mode in "disabled" condition, i got the snap from camera. When i set the trigger mode as Mode0, Mode1 etc. i got an error message as "Timeout"
I dont know to resolve this...... How to set the capturing time? I need some little more information regarding timing calculation etc....
I connected the cable to ext trigger and checked with Osciloscope. I am getting an output voltage of 4V dc when the camera is not taking pictures(idle mode).
Once i powered ON to take the pictures thro Maesurement and automation explorer am getting the result of oscillating voltage of 0-4V from trigger output poiint.
I need to give the external trigger pulse to capture the image for my application. Whenever i apply the pulse of some varyiing voltage the camera have to capture the image that time. I need to program this concept in labVIEW.....
I came to know whenever we write the vi accordingly, the internal oscillator gets reset and it allows the user to send trigger pulse externally.
How to reset the internal oscilator of the camera?
How to write the code in vi to complete this application?
Moreover i have 100pin Digital I/O board. I need to give the Ext trigger pulse throgh I/O board. How to do that?
i need some quality people's help to solve this problem....
I attacehd the vi which i developed for this application.
Guide me in this regard.
Thanks in advance
Regards,
Deepak
Attachments:
Snap_Ext_trigger.vi ‏46 KB

Hi,
I am attaching a document which has details about acquiring from FireWire cameras, triggering etc. Please read the document. You might find the solution to your problem.
Please revert if you have any further queries.
Krishna Prasad
Attachments:
NI-Tutorial-2977.pdf ‏1061 KB

AVT Marlin IEEE1394 camera not shown in MAX

Hi everybody,
i have an existing PXI system running with WinXP, a IEEE1394 camera and IMAQ for IEEE1394 and NI-Vision software. That runs fine. Now i am forced to update to Win7 and i try to get it run again...
I have a AVT Marlin IEEE1394 camera connected via a ExpressCard-FireWire adapter to my PXI system. The adapter is shown in Windows device manager under tree item "IEEE1394 Bus Hostcontroller" as "OHCI-compliant Texas Instruments1394 hostcontroller", the connected camera appears under tree item "NI IMAQ interfaces" as "NI-IMAQdx IIDC digital camera". But when i open NI-MAX the camera is not shown there. Under tree item "Devices and Interfaces" there are only the PXI chassis, 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 AVT driver the camera even does not appear in windows device manager. However is has to work with IMAQ.
Please help!!!
PXI-8105
Windows 7 SP1 (32 Bit)
Delock ExpressCard-to-FireWire adapter
AVT Marlin F-033C
MAX 5.5
NI Vision Aquisition 2013.09 Evaluation
IMAQdx 4.3
Solved!
Go to Solution.

I had the same issue about 2 years ago and solved it by switching to the "OHCI Compliant IEEE 1394 Host Controller (legacy)". Details are given here.

Dead MS6330 after PCI IEEE1394 Controller install

Hello,
Yesterday I installed a PCI IEEE1394 Controller on a MS-6330 with 1300Mhz Athlon. After installing the necessary software and restarting my WinXP couldn't load. I tried removing and adding the newly installed card, the LAN and video cards. Now as I start the computer the power supply looks fine, all the coolers start etc. but no signal (even BIOS) appears on the monitor, neither does the 'No input signal' message that appears when video signal is absent. Could you offer some solution to the problem?
10x in avdnce

Did you try clearing the CMOS ? ( Clear CMOS Guide)

Ieee1394 and dv camera

Hi, i have some problems with firewire in archlinux, all i know is that kino does not find my camera and dmesg giving me error... and i have not installed more then kino and dvgrab and all dependencies.
dvgrab
Error: no camera exists
dmesg
ohci1394 0000:02:0d.0: PCI INT A -> GSI 21 (level, low) -> IRQ 21
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[21] MMIO=[dc000000-dc0007ff] Max Packet=[2048] IR/IT contexts=[4/4]
ohci1394: fw-host0: Get PHY Reg timeout [0x02e20000/0x00000000/100]
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x00012669] (count: 0)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f96e6baa>] ? ohci_transmit+0x7a/0xe0 [ohci1394]
[<f825bb35>] ? hpsb_send_packet_and_wait+0x45/0x60 [ieee1394]
[<f825c972>] ? hpsb_read+0xa2/0x110 [ieee1394]
[<f8261ec5>] ? nodemgr_host_thread+0x425/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
[<f8261aa0>] ? nodemgr_host_thread+0x0/0xb90 [ieee1394]
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: received packet during reset; ignoring
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x00043573] (count: 1)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: received packet during reset; ignoring
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x00063679] (count: 2)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: received packet during reset; ignoring
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x0009a172] (count: 3)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ieee1394: raw1394: /dev/raw1394 device initialized
video1394: Installed video1394 module
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: received packet during reset; ignoring
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x000a137f] (count: 4)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: received packet during reset; ignoring
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x000e052d] (count: 5)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ieee1394: Stopping reset loop for IRM sanity
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x0010060e] (count: 6)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
ohci1394: fw-host0: AT dma reset ctx=0, aborting transmission
ohci1394: fw-host0: AT dma reset ctx=1, aborting transmission
ieee1394: received packet during reset; ignoring
ieee1394: Current remote IRM is not 1394a-2000 compliant, resetting...
ohci1394: fw-host0: Error in reception of SelfID packets [0x00000000/0x0010060e] (count: 7)
ohci1394: fw-host0: SelfID received outside of bus reset sequence
modprobe raw1394 ... etc
WARNING: All config files need .conf: /etc/modprobe.d/sound, it will be ignored in a future release.
Anyone able to help me with this information ?
Last edited by eviltoaster (2009-10-10 20:18:48)

steve___ wrote:
After you do
$ modprobe raw1394
Do you see it in the out of
$ lsmod |grep raw1394
I remember I got an error when I dumped some video from my camera but I do not remember the specific error. The solution was to specify the format.
$ dvgrab -f hdv FILENAME
[eviltoaster@Arch ~]$ lsmod | grep raw1394
raw1394 25724 0
ieee1394 85324 3 video1394,raw1394,ohci1394
i have never used dvgrab only kino .. but kino does not show my camera so i installed dvgrab.
[eviltoaster@Arch Desktop]$ dvgrab -f hdv tape1
Error: no camera exists

Mount USB vfat and IEEE1394 vfat hdd"s on separate pci

Trying to mount /dev/sda1 as USB HDD vfat system and /dev/sda2 as IEEE1394 vfat hdd simultaneously using PCI interfaces for each.
I haven't been able to establish sda2 in cdrecord -scanbus but the sda1 hdd on USB 2.0 is recognized in -scanbus and can be mounted.
Modprobe -v ohci1394 and modprobe sbp2 have both been entered. When using only the IEEE1394 HDD (no USB2.0 HDD connected) I can mount the IEEE1394 HDD as sda1.
Do I need to change the identification in fstab to sdb1?
Fstab:
/dev/sda1 /mnt/fat1 vfat defaults 0 0
/dev/sda2 /mnt/fat2 vfat defaults 0 0

: D Xentac;
Sdb1 indeed! That was the solution, now both are available simultaneously.
Thanks for the response.

Ieee1394: sbp2: Number of active logins: 357913941

I have been tortured by my new WesternDigital 320GB external hard drive.
I use Dell PowerEdge 350 and 750 with Red Hat Linux 2.6.9-22.EL kernel.
The ohci1394 driver is downloaded from oracle site, oracle-firewire-modules-2.6.9-22.EL-1286-1.i686.rpm.
After I modprobe ohci1394 I get
ieee1394: sbp2: Number of active logins: 357913941
Here is the output from lspci:
00:0e.0 FireWire (IEEE 1394): VIA Technologies, Inc. IEEE 1394 Host Controller (rev 46) (prog-if 10 [OHCI])
Subsystem: VIA Technologies, Inc. IEEE 1394 Host Controller
Control: I/O+ Mem+ BusMaster+ SpecCycle- MemWINV+ VGASnoop- ParErr- Stepping- SERR+ FastB2B-
Status: Cap+ 66Mhz- UDF- FastB2B- ParErr- DEVSEL=medium >TAbort- <TAbort- <MAbort- >SERR- <PERR-
Latency: 64 (8000ns max), Cache Line Size 08
Interrupt: pin A routed to IRQ 7
Region 0: Memory at febfe800 (32-bit, non-prefetchable) [size=2K]
Region 1: I/O ports at ec00 [size=128]
Capabilities: [50] Power Management version 2
Flags: PMEClk- DSI- D1- D2+ AuxCurrent=0mA PME(D0-,D1-,D2+,D3hot+,D3cold+)
Status: D0 PME-Enable- DSel=0 DScale=0 PME-
And here is dmesg after modprobe ohci1394
ohci1394: $Rev: 1285 $ Ben Collins <[email protected]>
ACPI: PCI interrupt 0000:03:03.0[A] -> GSI 11 (level, low) -> IRQ 11
ohci1394: fw-host0: OHCI-1394 1.1 (PCI): IRQ=[11] MMIO=[fdedf800-fdedffff] Max Packet=[2048]
ieee1394: Host added: ID:BUS[0-00:1023] GUID[1394041021000ed3]
ieee1394: Node added: ID:BUS[0-01:1023] GUID[0090a950000ab88f]
ieee1394: The root node is not cycle master capable; selecting a new root node and resetting...
ieee1394: Node changed: 0-01:1023 -> 0-00:1023
ieee1394: Node changed: 0-00:1023 -> 0-01:1023
sbp2: $Rev: 1265 $ Ben Collins <[email protected]>
scsi1 : SCSI emulation for IEEE-1394 SBP-2 Devices
ieee1394: sbp2: Node 0-00:1023: Using 36byte inquiry workaround
ieee1394: sbp2: Maximum concurrent logins supported: 0
ieee1394: sbp2: Number of active logins: 357913941
ieee1394: sbp2: Device does not support any more concurrent logins
sbp2: probe of 0090a950000ab88f-0 failed with error -16

Hi user490493, have you got your problem fixed? I have the same HD and got the same problem. I will be very appreciated it If you could let me know the status.
Thanks.
Zhaohua

Error -1074364412 (NI-IMAQ,IEEE1394)

I don't know what happen to this error display.
I use the IEEE-1394 camera(AVT Marlin F-033B) with NI-Imaq for IEEE1394
The grab method is "triggered async grab"
In the inspection mode,
I push the inpect start button, then Code is called that example and grab the image.
and I push the stop button then the example is stopped. then that error is appeared.
I wonder that error is appeared what happen.

Thank you for your advice.
As much as possible, I write about more information what you understand.
First of all I use the LabVIEW V7, Imaq Vision Ver 7, IEEE1394 Driver for LabVIEW V1.5.1, and three cameras at a same time.
Second, I tested in the MAX, but I didn't found that error comment.
Third, as I programmed the application that I refered to the examples of IEEE1394 acqusition part.
I attach the program of aqusition part.
I handle the three cameras by the parallel.
When you press the start button repeatedly,
you may find the error message occasionally
Please, you check my VIs, and give me the error information.
I look forward to hearing from you soon
Thank you.
Sincerely yours
Hyuk Jun, Yang
Manager
DISSE
M
Alliance member in South Korea
Attachments:
Test.zip ‏146 KB
test_main.vi ‏426 KB
triggered_grap_initial.vi ‏62 KB

Need help with Premiere 6.5 using IEEE1394 firewire and Canopus ADVC110

I have been using Premiere 6.5 for over 10 years now and had to replace the Pinnacle DV 500 card with a Canopus ADVC 110 and firewire when Windows XP had its Service Pack 2 downloaded. Recently for no apparent reason the Premiere Capture Window is showing Unable to connect to capture driver. I have checked the firewire cable, the ADVC device and the OHCI DV (IEEE1394) device and all appear to be working. Can anyone point me in the right direction for a solution?
Alan

Alan,
The Grass Valley/Canopus ADV-110 should come with a copy of the Edius capture software. That is what I would use for the Captures. Just set it to DV-AVI Type II w/ 48KHz 16-bit PCM/WAV Audio. Then, Import these into Pr 6.5 for editing. The ADV-110 should allow you to capture from any source hooked to it, whether analog, like VHS, or digital, like DVD from a connected set-top player. I use a similar device in this manner.
The only slight drawback is that one has no direct Device Control, as they would from a FW connected miniDV camera. I cue up the source player (VHS or DVD), start Edius, after the settings are done, and hit Record, then click my remote for the device deck to Play. Works perfectly.
Good luck, and hope that this helps. For direct FW Capture in Pr 6.5 you would do that from a miniDV camera. Do not know if Pr 6.5 had full Device Control, or not. PrPro 2.0 was the first Pr version that I used.
Let us know if this works.
Hunt

Satellite Pro M30 error in IEEE1394

Hello...
I think i have a problem whit the driver of IEEE1394
I can't find the drive at any part, and the cd of the drivers don't have that driver i don't no how resolve it, and the re-installation of the S.O. don't solve me the problem...
Anu trick?
Tank's a lot

Hi,
do you have the Toshiba OEM OS runing (Toshiba Recovery CD) or did you setup a own OS (Full XP version)?
Also it would nice to know if the IEEE1394 port worked in the past or as the case may be directly after bought the notebook?
Did you checked the the IEEE1394 entry at the Device Manager? Try to reinstall the driver (I think it's a windows standard driver)!
Bye sammy

Communicate with FireWire ieee1394 port

Hi all
Let me briefly explain my current situation. I'm trying to use an Audio Interface as a Micrphone arrays. In my case, Audio interface is a device which has 8 microphones input on it and is connected to the computer by FireWire port (ieee1394 6pin). So by connecting 8 microphone to it, it works as an A to D and the signals of these 8 microphones will be transmitted to my computer via firewire. Now the problem is how to read from firewire port by means of a java program to record these signals?
The more I searched the less I found in this topic.
PS1: I work in linux.
Thanks in advance for all your helps :D

You may want to ask t his in the JNI forum: I'm pretty sure you're going to have to do some C/C++ programming.

Windows 7 not find IEEE1394 Driver for my MAC Mini

Hi, i try to install windows 7 ultimate on my MacMini Core 2 duo.
All ok... I use bootcamp 3.1 for install driver in windows... and all OK but.... not Controller IEEE1394
I can't find and instal driver for it...
someone have a solution?
Thanks a lot....

Hi Kristo,
"Microsoft Windows operating systems include a bus driver and various class drivers to support the IEEE1394 high performance serial bus. However, current driver support is limited to controllers and devices that are compliant to the 1394a standard.The features introduced with the 1394b standard cannot be used in Windows based applications and device drivers."
What do you need to achieve?

Cannot find Basler A101f IEEE1394 camera info file to download

The basler IEEE1394 A101F camera info file used to be on the NI site. Can someone find this and email it to me?

You shouldn't need it. Camera info files for all firewire cameras are created automatically when you configure the camera.
Bruce
Bruce Ammons
Ammons Engineering

Why Can't Get Color Images from My ADS Pyro IEEE1394 Camera

This is a list of our equipment :
Windows98SE
LV6.0i
NI-IMAQ for IEEE1394
Advanced IMAQ Library for LV
Pyro IEEE1394 Webcam from ADS
Unfortunately, we do not see any colors in the RGB Modus.
We have visited your perfect support web sites and found a similar description.
Document ID: 2DGHH1SN (09/17/2001)
We used your support tip (change 1394IMAQ.sys and clean-up MAX) and anyway we do not
see colors even though the PYRO IEEE1304 Webcam support color mode.
We think the hardware of both IEEE1394 webcams (Pyro and IBOT) are the same.
Did you received any feedback from the customer whos has the problem with the Orange
Micro IBOT IEEE1394 webcam ?
It is highly interested for us.
We appreciate y
our help and many thanks for reading and thinking about this manner

Dear Keyle,
Thanks for your response. Now, we have a running XP Home Edition Notebook machine.
We have installed first LabVIEW6.0i then ADVANCED IMAQ VISON > IEEE1394 for IMAQ beta2 + MAX2.2 and finally
VISION BUILDER 6.0
We have observe the VISION BUILDER support during the custom installation process of NI-IMAQ 1394 b2 and unfortunately we running in the same problem and could not use the great VISION BUILDER together with our
IEEE1394 camera. We see a big opportunity to develop our apllications faster and improve the time to market.
It is possible to enclose the difficult situation ?
Up to now, we are very happy to see colors in MAX and
LV.
Yes, we notice that we use a beta driver and we could
not expect that it works perfect. But you wrote, that you have a running VISION BUILDER support with a XP machine and we are in a good mood to read this.
We appreciate your help in this manner and thanks again
Stephan

P45 Platinum IEEE1394 drivers for Win7 x64

I just reinstalled my PC with P45 Platinum mainboard and everything installs fine with the drivers from the MSI website, however there is no driver for IEEE1394 controller there.
I installed Win7 x64 now, before I installed WinXP and at the time of that installation it installed fine.
I am not using the IEEE1394 controller at the moment but there is a exclamation point in the device manager I want to get rid of.
Can anyone point me to the driver, thnx.

In windows 7 there's no Firewire driver needed it should automatically install it as already integrated. Is it already installed and exclamation mark on it like it isn't working correctly or unknown device?

IEEE1394

Similar Messages

Maybe you are looking for