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

Similar Messages

  • "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

  • Resource Allocation for IEEE 1394 (Firewire) Cameras in Triggered Mode

    In this article:
    Resource Allocation for IEEE 1394 (Firewire) Cameras in Triggered Mode
    http://digital.ni.com/public.nsf/allkb/ED092614FCCC900D86256D8D004A3B0C
     it says "The Bytes Per Packet value represents the number of bytes that are transmitted at consistent 125us intervals on the FireWire bus during image acquisition" and the reciprocal of the 125us value would seem to be the source of a value of 8000 in a subsequent formula used to calculate the frames per second.
    Is this 125us value independent from the firewire bus speed or a function of it?
    If it is a function of bus speed, how does it vary with speed?
    (Is the 125us value for 400Mbps and 250us for 200Mbps?)
    Thanks!

    Hello Warren
    Thank you very much for getting in touch with us.  Although the Firewire standard itself is not technically supported by National Instruments, I will do my best to assist you.  I am currently referencing the IEEE 1394 documentation.  From what I'm reading, I do not believe the 125 microsecond value changes.  I have copied and pasted the paragraph of interest under Bus Arbitration from a document that I referenced:
    The arbitration mechanism gets more complicated when isochronous devices are connected on the bus, because those devices have already been guaranteed bandwidth.  Each arbitration round is approximately 125μs long, so bandwidth is allocated as a portion of the 125μs interval.  The root node broadcasts (sends a message to node 63, the broadcast address) a cycle start packet, which begins the arbitration round.    All interested nodes send an arbitration request as before, and the winning node is still the node closest to the root.  After .04μs of bus idle time, the remaining nodes arbitrate for control of the bus.  Once each isochronous node has completed its transaction the time remaining in the 125μs interval is used for asynchronous transactions.  Up to 80% of the bus bandwidth may be allocated to isochronous transactions and the remaining 20% is left available for asynchronous transactions.
    The original document can be found here:
    The FireWire Serial Bus and its Implementation
    I, unfortunately, cannot claim to be an expert on the IEEE 1394 standard but from what I've researched, the 125 microsecond time allocation is standard and bandwidth is then allocated accordingly.  I may recommend consulting IEEE 1394 Trade Association (http://www.1394ta.org/about/Contact.html) for more in depth information.  Please let me know if this is sufficient or if I can be of further assistance.  I will do everything I can to ensure that your issues is resolved.
    Have a great day!
    Sincerely,
    Greg S.

  • IEEE 1394 bus host controller issue.

    Each time I boot my system (Tecra A9 S9021V) the IEEE 1394 Bus host controller device driver displays that it is disabled with an error code 22 (this taken from device manager).
    From within device manager I manually disable the device, then re-enable the device.  The device then displays that is operating correctly.  The device driver is displayed as "Texas Instruments OHCI Compliant IEEE 1394 Host Controller".  There are 2 files associated with the driver - (1) 1394bus.sys (Microsoft Corporation; version 6.0.6001.18000 longhorn_rtm 080118-1840), and (2) ohci1394.sys (Microsoft Corporation; version 6.0.6000.16386 vista_rtm 061101-2205).
    I'm running Vista Business SP1 with all updates/patches.
    Is there something I can do to get this device to start up correctly?
    Thank you!

    Tecra A9-S9021V 
    Each time I boot my system...the IEEE 1394 Bus host controller device driver displays that it is disabled with an error code 22 (this taken from device manager).
    What is the exact message that appears when you boot? No paraphrasing.
    What did you change about the time this started?
    Can you do a System Restore to before the trouble began?
       What is System Restore?
    -Jerry

  • 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

  • From USB to IEEE-1394: question about HD capture, editing, sharing.

    I’m new to editing video but have a question about capturing video into Premiere Elements 7. I have been using a Canon HF11 which shoots only in HD and only has USB output to copy video to my desktop. I don’t have a Blu-ray burner yet but I have burned a few projects to DVD, shared video on YouTube, and saved files in .avi and .mpeg to view on computer screens. But obviously I’m missing out on sharing HD on disk at this time. I just bought a Canon XH A1s which shoots both HD and SD on miniDV tapes. And uses IEEE-1394 cable for capturing (to Pre7). I did a 3 minute test project in SD and burned it on a DVD disk. I was very pleased at the results and the ease of editing. I don’t have any HD tapes yet, but when I do what differences will I experience from shooting in HD and then capturing, editing, then to sharing? My current HD processes with the HF11 is slow, occasional low-resources warnings, and less then pleasing results on DVD disks. Thanks for any and all comments and/or suggestions.

    Your HF11 is AVCHD format and the Canon XH A1 is HDV MPEG2. AVCHD takes a lot more computer horespower to edit compared to HDV MPEG2... main reason being that AVCHD is more highly compressed giving small file sizes. This is also why you get the low resource and memory alarms while editing.
    To shoot HD you do not need HD miniDV tapes you can use the standard miniDV tapes. However the HD tapes are supposed to give fewer drop-outs than the standard tapes but are considerable more expensive. With DV-AVI a drop out would be hardly noticed, but as HDV MPEG2 is a compressed format and the picture relies on information in a number of frames any drop-outs can give a second or so of bad video. That said I have had very few issues with drop-outs. If you are doing a wedding or something important that you do not want to risk then probably better to use a HD miniDV tape.
    In the past the advise has been to capture in high definition to get the best quality and then downconvert in the camcorder and capture in DV-AVI... the reason being that older versions of Premiere Elements did not do a good job of the down conversion. Reports on PE7 indicate it is better and that you could use a HDV workflow and burn to DVD as a last stage. This also allows you to export a high definition version of your video to view on a monitor where you can appreciate the higher resolution. Or in the future when you have a Blu-ray burner and player you can burn the file to disc... save doing all the editing all over.

  • 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.

  • 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

  • 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

  • Info urgently needed - Need IEEE 1394 (Firewire) connection

    I need a IEEE 1394 connection for my T60 (1951 A47) for transfering digital video from our new HD video camera. How can I upgrade my laptop to receive such a signal?
    Not solved but replaced by -> http://forums.lenovo.com/lnv/board/message?board.i​d=T_Series_Thinkpads&message.id=19376 
    Kind regards
    Per Buch Larsen
    IBM Denmark, Communications
    Message Edited by pbl_ibm on 10-10-2008 04:38 AM
    Message Edited by pbl_ibm on 10-10-2008 04:40 AM
    Solved!
    Go to Solution.

    I have searched for other issues in this forum regarding the mentioned PCMCIA IEEE 1394 adapter. It seems that people do experience troubles using it. Is there one adapter that is better than another? Should I change something in the setup of my T60? Simply, will it chrash? 
    Thans in advance
    Kind regards
    Per Buch Larsen
    IBM Denmark, Communications

  • 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

  • Insufficient resources error - Speedgrade - Premiere Pro dynamic link

    Morning all,
    I'm getting an error as follow:
    Insufficient Resources - GPU-enabled rendering disabled due to insufficient GPU recources. Relaunch SpeedGrade to re-enable GPU rendering.
    I've tried rebooting and I get the same problem. It means that this workflow between PP and SG are no longer viable. Is my system struggling with the volume of data?
    Media is from a Sony FS700 (AVCHD files) and 5dmk3 (h.264). I work using the dynamic link between PP and SG. I used SG to colour my rough edits from PP. Have used this technique for a long time and not had an issue. The only difference about this project is the volume of media is very high. I've shot around 250gb of data. This is broken up in the project into short timelines, edits etc and I'd assumed that the volume of media in the PP project wouldn't influence the dynamic link to SG connection but this is the only thing I can think of that's different about this project. Not knowing how the system processes that connection via dynamic link leads me to thing that SG is struggling to read such a big PP project but I might be wrong here. 
    Anyone got any ideas what causes this error and if there is anything I can do to rectify it?
    Ta,
    Alan
    My system is as follows:
    Windows i7 3770 3.4Ghz
    16GB RAM
    Nvidia GTX 680 Graphics card
    Editing from a Lacie RAID via usb 3 connection
    Latest version of Adobe creative cloud for PP and SG
    The error I'm getting...

    As dummergold notes, this has been an irritating problem for some, and a complete show-stopper for a select few lucky folks. I "caught" this on the initial release, and for a month, I couldn't work Direct Link at all. I could work Sg in a native mode (creating an Sg project) ... but then of course, you either have to get Sg to accept an EDL from PrPro (which can be tricky at times, smooth as silk others) or grade the footage then render/export to work in PrPro, or export a completed file from PrPro in a codec Sg takes, use the clip-detection feature in Sg, and grade then export. It's how "we" did it before, of course, but it's a PAIN now.
    So ... hopefully, in a couple days at most, after starting & stopping the thing a few times, maybe trying the alt/shift hold-down while starting thing to void the preferences file. A couple people had it stop on signing out & back into their CC account. Or maybe even using the Adobe CC Cleaner tool to uninstall both PrPro & Sg, then download & re-install. There's always the possibility of going back to 2014.1 BUT ... you have to do that with both PrPro & Sg, and if you use say Ae or Audition, them also ... and any project started in 2014.2 won't work in 2014.1.
    They showed off the new release at NAB, which is an amazing new tool ... literally ... and they think they've got this nailed down in that release so it will finally STOP happening. However, the date it goes public is anybody's guess. They demo'd last year at NAB, and it was sometime in June that 2014 "launched" publicly. Wish I could be more help, but yes ... do look back through that post above. Your machine is very much like mine except for the video card, and I would note ... even a hard-drive RAID via a USB3 connection isn't giving a great sustained throughput. eSATA would be near to double the sustained in/out, and Thunderbolt rather a bunch more than USB3. I'd suggest going to the Tweaker's Page and finding the stuff on disk in/out & types of connections tested and such.  Note, unlike the Theory of disk in/out & connection performance (manufacturers and MANY "knowledgeable" types), their data is from thousands of tests on real machines running specially designed sequences with logging programs "on" that check out what doth happen in reality.
    Tweaker's Page ...
    http://ppbm7.com/index.php/tweakers-page
    Neil

  • IEEE 1394/Firewire port not seeing DV

    Hey All,
    New to this forum, but looking for some help.
    I have read just about EVERY previous topic regarding the 1394 issues and cannot find a solution to my problem.
    I CAN see the 1394 setting in CMOS, and it is set to "AUTO".  Also, in the Device Manager, I can see "IEEE 1394 Controller" with no IRQ conflicts.  I have updated all of my MSI drivers as well as CMOS up to current.  I have installed the DV drivers that came on my Camcorder's CD as well as programs that are designed to utilize the DV out on the camcorder.  Also, I have reconnected my two 1394 ports on the motherboard in every configuration to check if it was a connection problem.  Tomorrow, I'm gonna go get another cable, but doubt that's it; it's brand new.
    I plug in my Digital Camcorder (Canon ZR85) and there is nothing.  Windows makes no notice of it, and when I run the program designed to utilize it, it says that it is not connected.  I have followed the owner's manual to a 'T' for setting it up.
    Here's my info:
    Athlon XP2400
    512 MB RAM
    120Gig drive (SATA)
    Windows XP Pro (SP1a)
    Canon ZR85 MiniDV
    4 pin to 4 pin IEEE 1394 Firewire cable
    (This MiniDV Camcorder will only connect DV via 1394, not USB 2.0)
    Any help would be greatly appreciated!
    Saint

    So... seeing that no one responded to my initial request for information to solve this problem and I was not able to find any other helpful forums out there, I decided to do the prudent thing and buy a new motherboard/cpu, etc.
    I bought what was supposed to be a top-line mboard, the K8N Neo Platinum with an AMD 3000+ chip, 512 PC3200 Crucial memory, 200 gig SATA HD, and 3dForce 6800.  What I have come to figure out is that my brand new MSI mboard has the EXACT DAMN PROBLEM!!!!!!!!!!!!!!!!
    I vowed years ago not to buy another MSI because of previous failures, but I was convinced that they were really producing quality boards now.  Yet again, however, I guess I was fooled.
    IF anyone has ANY help they could provide for this problem, I would be incredibly grateful.  Otherwise, I'll have to take this mboard back, and I will NOT EVER buy another MSI product, and will be sure to tell everyone else the same thing.
    Desperately,
    Saint Raj

  • Please Help.... IEEE 1394

    Just brought an IPOD nano ma4777zt/a (don't understand 2nd generation / click wheel ?)
    and my PC runs Windows XP home Edition
    loaded itunes onto my computer by clicking download on web site Itunes 7
    Once complete connected ipod via cable and I've got the message
    "No IEEE 1394 Host controller found"
    Searched for 8 hours & nothing seems to have worked
    Please help !!!!

    Carefully check the bottom dock connector for any bent over pins or something in there shorting pins together. A magnifying glass would be a help.
    The Firewire data pins on the dock connector are right next to some power pins and if you get a short between them, it can fool the iPod into thinking there is data coming in on the Firewire pins and it will give you Firewire related error messages.
    For that matter, be sure to carefully check the Dock end of the USB cable for the same sort of problems. It would be help if you can find, beg, borrow, another USB cable, even if you just go to a local electronics store that sells iPods and see if you can test your iPod with one of their cables. Obviously if it doesn't give you the message on a different cable, then your cable is the issue. If you still get the message, then likely it is your iPod itself.
    Patrick

  • IEEE-1394 MoBo connector

    Hi,
    The Neo Platinum board has 2 IEEE-1394 connectors on it, according to the handbook.
    However, these connectors are the same "9 out of 10-pin" connectors used for USB connections.  While this may be fine for the MSI specific adaptor, my computer case has an internal wire with a normal IEEE-1394 6-pin connector on the end.
    Anyone know where I could get an adaptor (in the UK)?  I've looked on PC direct seller sites (dabs, etc) and on RS Components but I cannot find one.
    Cheers,
    David

    Found this answer at microsofts website,  looks like a winner for a lot of people.
    http://social.technet.microsoft.com/Forums/en-US/w​7itprohardware/thread/65cb7a25-2a84-4875-aa27-b084​...
    I hope this can help you. 
    The 1394 bus driver that is included with Windows 7 replaces the 1394 bus drivers that were included with earlier versions of Windows. See this site for details 
    http://www.microsoft.com/whdc/connect/1394_Windows​7.mspx
    You can try the following steps to fix our issue, [sic] This solved my initial problems with a Maxtor III OneTouch drive.  
    1- Click the Start Button, type devmgmt.msc in the “Start Search” box and press Enter.
    2- Expand the "IEEE 1394 Bus Host Controllers" node in the device tree on the right hand pane
    3- Right click the host controller node select "Update driver software ..."
    4- Select "Browse my computer for driver software"
    5- Select "let me pick from a list of device driver on my computer ..." and Check the box before “Show compatible hardware”.
    6. Choose the second option---1394 OHCI Compliant Host Controller (Legacy), and click next to update the driver.  

Maybe you are looking for