Machine Vision

cancel
Showing results for 
Search instead for 
Did you mean: 

IEEE 1394 insufficient resources issue

Solved!
Go to solution

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. 

  1. 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.
  2. 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.
  3. 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
  4. 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

0 Kudos
Message 1 of 5
(4,292 Views)

The fact that you can't choose more than 100Mb for the speed indicate your XP still has the issue where Windows doesn't allow access to the full 1394 bandwidth. It sounds like the AVT bus driver you installed didn't work right, but the microsoft link you mentioned should fix your machine so you can have 400 for the speed instead of 100.

 

Hope this helps,

Brad

Message 2 of 5
(4,289 Views)
Solution
Accepted by topic author Paul_Barber

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

Message 3 of 5
(4,285 Views)

Thanks Brad and Scott,

 

I didn't want to install the Microsoft hotfix without asking first.  It worked.  I can now get images from both cameras 😄

 

Paul

0 Kudos
Message 4 of 5
(4,281 Views)

Hi,

 

I'm using EVS1464 Windows 7. I experienced the same problem when I changed the Acquisition Mode from "Continuous - Immediate" into "Snapshot" and the Packet Size as well. Any suggestions?

 

Thanks,

Andrei K.

0 Kudos
Message 5 of 5
(4,270 Views)