IEEE 1394 problem on 845PEMAX2

I tried to use the IEEE 1394 connection tonight to download digital video from a Panasonic palmcorder. After plugging in the device and getting no response, I looked at the device manager and found a problem showing up. Windows XP Home Edition says 'This device cannot start(Code 10)'. I tried uninstalling and reinstalling the device, updating the drivers from the website and then uninstalling and reinstalling with no change. The device had not shown up as having a problem in the device manager in the past but I had not tried to use it until tonight.
I have an 845PE Max2 MB.
Anyone have a suggestion that might help??

I do not recall seeing the problem (indication in hardware manager that the device has a problem) show up before I connected the palmcorder but I also had not paid any attention. When I opened the computer case following the attemp to download from the camcorder, I found that one of the connections to the front IEEE 1394 connector had come off of the MB. I put this back in but it had no effect. I also tried connecting the camcorder to other 1394 inputs that have socket connections to the MB with no luck.
Since I found the problem, I have tried (at least 4 times) to uninstall the device and then reinstall it. With nothing connected up, I get the same error message showing up - it cannot start the device (I assume that it means controller but it is not clear!). I do not know if this is a remnant of the camcorder being plugged in to the front panel with a missing connection or not. If it is, it is somehow buried in the Windows XP registry. If it is not, then it is most likely a hardware problem.
Any other suggestions would be greatly appreciated!!

Similar Messages

K8N Neo2 Plat - WinXP SP2 IEEE 1394 Problem???

I use the k8n Neo2 Platinum with a Athlon 64 3500+ cpu
I installed WinXP with SP1 an everything was and worked ok (there was a VIA OHCI IEEE 1394 Compilant Controller and a IEEE 1394 net adapter)
When I upgraded to WinXP SP2 there was no IEEE 1394 net adapter any more, but the controller in the Device Manager was ok. Sometimes thought if i uninstall the controller an do a check for new hardware changes the controller appears with a Code 10 error, but when WinXP starts no problem appears in the Device Manager...????
Please help i need the Firewire connection to plug my VideoCamera.
If there is any driver for the IEEE 1394 please email or PM me the url.
thanx Nick
PS. If i arrange the devices by connection type no IRQ conflict seems to exists.
Sorry for the "english" but i'm from greece.
Please help....

I manage to make the IEEE 1394 Net adapter appear.
I changed every file that is about ieee1394 of SP2 with the SP1 files but before i restart i renamed sp2.cab (into hidden folder) file because if any change happens it restores the original files on restart. Now both IEEE1394 Controller and Net Adapter appear into the Device Manager but when i connect any device into firewire port is not recognized. I tried my camcoder to another pc with WinXP SP2 and when i connect it a ballon appears and sain that a Digital Device is connected. To my PC nothing happens.

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

Having problems with IEEE 1394 connection with MSI K8N Neo4 Platinum

Hi...
I am encountering problems connecting devices (portable hd etc) via firewire to my PC. My PC does detect the devices.
I am using the MSI K8N Neo4 Platinum board.
Check with Device Manager show that the VIA OHCI Compliant IEEE 1394 Host Controller is working properly.
IEEE 1394 controller has been enabled in Bios.
Need help to rectify this problem.
Thanks for the assistance...
Regards

Try this patch.

HDX 18/dv8t IEEE 1394/Fire Wire performance problem in Win 7

The IEEE1394 interface lives on the PCI express bus at IRQ 16, which is shared by several other devices. Audio interfaces, such as the M-Audio Pro Fire and Fire Wire series do not work reliably with the shared IRQ. In Vista, by comparison, the IEEE 1394 interface has its own IRQ, and seems to run more reliably.
Any ideas on how to fix this?

Well, I found a workaround for my issue. It's described in this article:
[url="iPod not recognized correctly on Toshiba laptop"]http://docs.info.apple.com/article.html?artnum=300836[/url]
By disabling the "Sandard Enhanced PCI to USB Host Controller" in device manager, my iPod was correctly recognized and I was able to sync with iTunes. That's the good news.
The bad news is that: a) Windows warns me that my "device can operate faster if connected to a USB 2.0 port" - and the sync with iTunes runs slowly; b) if I reanable that USB device (as suggested in the Apple article, my iPod is no longer recognized.
For now, I'll just disable this device when I need to sync, then reenable it when done. But this is going to be a pain. I really don't consider this a fix. It's really annoying that the iPod is the only USB device that requires this kind of nonsense.
Looking forward to a "real" fix for this some time soon.

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

P30: External HD isn't detected when using IEEE 1394 cable

My P30 won't/ can't detect my newly aquired Western Digitak Extreme Lighted Drive 320GB when I connect it via the firewire port. I use a 6 pin to 4 pin cable (which cost a fortune, by the way) that is supposed to be a way to connect this drive to a pc.
My ieee 1394 driver seems to be called "VIA OHCI Compliant IEEE 1394 host controller".
Can anyone tell me what to do? I really need to connect this drive by firewire because I need the USBs for other devices.
Thank you!

This may sound like an obvious problem, but is the drive:
1. Set to Master on the jumpers?
2. Formatted?
If the drive is not set to master, the computer will not recognise it using 1394. And if it is set to master, but it has not yet been formatted, the computer will register that something using 1394 is connected, but will not know what to do. To format you right click on My Computer, and select manage.
Mike

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

"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

Why is the IEEE 1394 Standard for digital cameras difficult to synchronize/trigger with other devices?

In the knowlege base, it generally says under "analog and digital cameras: advantages and disadvantags" that the IEEE 1394 is difficult to synchronize and trigger. Why is that exactly so and how can you solve that problem in DIAdem 8.0 when you would like to trigger your measurement inputs (accelerometers etc) together with a camera.

I would guess it is difficult to synchronize because it provides a software trigger. Latencies in the communication would make it difficult to perfectly synchronize two separate events.
Many firewire cameras also have a hardware trigger. If you were to use this with your other hardware, you would probably be able to get much better synchronization.
Bruce
Bruce Ammons
Ammons Engineering

NI_IMAQ IEEE-1394 bug?

I am starting to familiarize myself with the new v2.0 IEEE-1394 firewwire camera driver VI's and have been working with the property nodes that have replaced the IMAQ1394 Attribute & Attribute Inquiry VIs. I have managed to build a VI that will quite repeatably crash LabVIEW.
It requires:
1) a query of a camera attribute property that is recognized by the property node but not by the camera.
2) a subsequent query of another camera attribute property.
Has anyone else seen this?
An example (for LV 7.0, IEEE-1394 v2.0.0) is attached.
Attachments:
Crash LabVIEW.zip ‏27 KB

Hello Warren,
Thank you for using our discussion forums. I have taken a look at your VI and seen similar behavior as you described. I noticed that if you remove the bundle by name from the case structure the problem seems to disappear, let me know if you see a similar behavior. Otherwise, I am trying to investigate the problem and will get back with you as soon as I have any updates. Thank you for your patience and have a great day!
Regards,
Nipun M
Applications Engineer
National Instruments

Windows 7 hangs at desktop when installing IEEE 1394 Controller driver

Hi Guys,
This is a repetitive problem for me, my win7 always hangs at the desktop whenever it tries to install the driver for the IEEE 1394 Controller. Does anyone have a solution for me?
Thanks.

Hi and welcome to Discussions,
maybe the solution in here http://social.technet.microsoft.com/Forums/en/w7itprohardware/thread/65cb7a25-2a 84-4875-aa27-b084537e8da1 can help you.
Regards
Stefan

SP A10: XP SP2 and Maxtor IEEE 1394: Need MS Hotfix?

I have a Satellite Pro A10 hooked up to a external Maxtor 80Gb disk on a Firewire/IEEE 1394 link.
The IEEE 1394 is attached to a PCMCIA card (from Belkin) which uses the NEC 1394 chipset.
There is a Hotfix available from Microsoft (see http://support.microsoft.com/default.aspx?scid=kb;en-us;885464) but MS Support say this can only be sourced through Toshiba Support.
Can you help me obtain the Hotfix?
Without it I can rarely access the drive.
It works fine on my Tecra M2 which accesses the same drive through it's built-in 1394 interface. The problem only occurs with 1394 chipsets from NEC.

Hi
Well, did you contact the Belkin support?
In my opinion you should ask the PCMCIA card manufacturers for the upgrade or this hotfix. Furthermore you can check the Toshiba drivers download page for this hotfix. The Microsoft hotfixes are called QFE. Maybe you will find the right one. But unfortunately, if you are not able to find this one, you have to wait for the next Windows XP service pack that contains this hotfix. :(
Bye

No IEEE 1394 Host Controller found.

While attempting to update my iPod..actually, just while saying "Do Not Disconnect" my iTunes has been shutting down.
I ran diagnostics on my iPod and the subject showed up -- "No IEEE 1394 Host Controller found." Any idea what this could mean?

I think I am having the same problem, my iTunes is hanging and not responding. I am not very technically minding, and have now been trying to update my Ipod, and my husbands Ipod, for 3 days. In the same time I have, I think, downloaded Ipod version 7.0.1. I therefore do not know if it is my husbands Ipod which is at fault, or the new software. I ran the diagnostics tool and got the following outcome, which leads me to believe that there is a problem with the host controller, however.. i dont appear to be able to do "anything" with iTunes without it hanging, e.g., i cant burn a backup of the library. I have restarted, restored, downloaded the latest version of itunes, all to no avail. Is there an "idiots" guide to this somewhere? I am totally lost and cognitively challenged. Here is the diagnostics print out
Microsoft Windows XP Home Edition Service Pack 2 (Build 2600)
Acer Aspire 3610
iTunes 7.0.1.8
iPodService 7.0.1.8 is currently running.
iTunesHelper 7.0.1.8 is currently running.
Current user is an administrator.
Connected Storage Devices:
IDE\DiskWDCWD600UE-22HCT1_____________________09.07D09, Bus Type ATA, Bus Address [0,0]
USBSTOR\DiskApple__iPod___________1.62, Bus Type USB
Universal Serial Bus Controllers:
Intel(R) 82801FB/FBM USB Universal Host Controller - 2658, PCI bus 0, device 29, function 0. Device is working properly.
Intel(R) 82801FB/FBM USB Universal Host Controller - 2659, PCI bus 0, device 29, function 1. Device is working properly.
Intel(R) 82801FB/FBM USB Universal Host Controller - 265A, PCI bus 0, device 29, function 2. Device is working properly.
Intel(R) 82801FB/FBM USB Universal Host Controller - 265B, PCI bus 0, device 29, function 3. Device is working properly.
Intel(R) 82801FB/FBM USB2 Enhanced Host Controller - 265C, PCI bus 0, device 29, function 7. Device is working properly.
No IEEE 1394 Host Controller found.
Connected Device Information
PAUL FORD'S (F:\), iPod with Click Wheel running firmware version 3.1.1
Serial Number: 4J451VHQPS9
Bus Speed: 61440
The last connected iPod serial number: 4J451VHQPS9.

IEEE 1394 problem on 845PEMAX2

Similar Messages

Maybe you are looking for