IMAQ 1408 + DAQ cards crashing when loop iteration 1

I have a problem trying to run some code which outputs a synchronised analog and digital pattern using the PCI-DIO-32HS and PCI-6713 DAQ cards which triggers an external analog camera. The images from the camera are then read via the IMAQ 1408 frame grabbing card.
When I run the code once, it executes successfully every time. If, however, I select 'run continuously', or alternatively place a FOR-loop around the pattern output and image collection, the computer executes the pattern once, then completely freezes the computer, requiring a hard reboot of the computer.
I have attempted to add wait times at various points through the code, however even if I place 10s delays in the loop (the pattern takes around 1s) the computer hangs and crashes. Running the code by repeatedly clicking 'run' however works every time, with no error or crashes.
Is there any way to extract or trace the error causing this behaviour - the issue must be with the IMAQ drivers, however I cannot see what is different between running the VI manually 10 times in a row, and running it continuously with a wait to prevent it running at full speed. Any advice for debugging this error would be much appreciated. I have attached the code with subVIs necessary to reproduce the error.
Attachments:
JAI_Testing.zip ‏841 KB

Hi Fan Wu,
You're right that you only have two counters on your USB DAQ device. If we limit the problem to only one channel, then I would recommend using the counter because it sounds like you're creating a pulse train of known parameters. Since the counters use a fast timebase (if you're using Mseries you're using an 80MHz clock), you'll get very predictable performance at 1ms of interest.
The other way to do this (since you'll need more channels) is to use a counter to setup a timing engine. A simple pulse train with 50% duty cycle and whatever frequency you're interested in (sounds like 1kHz) can be used as your DI/O timing clock. You can then create a digital waveform with the characteristics you are interested in and write that to your buffer. With your Digital task correlated to your counter output, you can output this waveform at the rate of your counter output.
While this is NOT the end application you are looking to write, this example has some great parallels to what you are trying to do. It illustrates creating a clock with the counter and then writing a digital waveform to correlate to that clock.
http://zone.ni.com/devzone/cda/epd/p/id/3687
PBear
NI RF

Similar Messages

  • (bootcamp) graphics card crash when playing games

    Firstly apologies if I've put this in the wrong section of the forum... this is the most applicable I could find.
    Having tried to enquire at the good folks of AMD, they told me I needed to see apple. Finding a support email is nigh on impossile - so either that or advice on this issue would be greatly appreciated!
    I have a boot camp partition on a mid 2011 macbook pro - my graphics card is Radeon HD 6750M.
    I have recently been experiencing graphics card crashes when playing games.
    There is no boot camp update available, so I am forced to update the driver manually. Trying to use the automated detection/installation tool on the ATI site resulted in the error "your computer doesn't have a proper graphics adapter"
    When I located and downloaded the mac bootcamp drivers from the ATI site site, and I tried to install these it was unable to detect my existing microsoft C++ distributable or install its own - so the installation failed.
    All advice welcome!

    yeah - it *might* have fixed my issue - or at least it hasn't crashed yet... jynxed it now ofcourse ;p I have acouple of questions though...
    Why did this just start happening - I've played other games and this game before without these crashing issues?
    I'm worried about configuring this fan thing correctly - lots of 'if your hardware gets damages it's not my problem' warnings on the software site. I know there's only 4 options - how do I ensure I select the right one? ie I thought I had a unibody macbook pro but it can't find the second GPU?

  • Multiple DAQ Cards, Multiple While Loops

    I'm writing a code to support 3 small test stands that each have the same outputs and inputs as the others. I'm running them all off of an 8-slot DAQ. Each test stand has its own dedicated RTD Card and Analog Out card, but they all share a 32-channel Analog Input card.
    I'd like to decouple the 3 test stands as much as possible - if I have to take out an RTD card or Analog Output card, I don't want the entire LabVIEW program to stop running. I want to be able to keep running and logging data on the other two test stands if I were working on the other test stand. Is there a way to do this with only 1 cDAQ? Is it simply a matter of creating separate, independent while loops for each test stand? If so, would LabVIEW have issues with each while loop writing its own measurement file in parallel with the others?
    Thank You.

    Is it safe to assume you've been running the three tests?  Some of your post makes it sound like you've run them coupled while other parts make it sound like you haven't successfully had all three tests running simultaneously.
    If you aren't running them, are you using hardware timing (counters) for your tasks?  If you're looking to use counters, you're only using one per task, correct?  The cDAQ will only have four counters total to be shared between your loops.
    I can't remember off the top of my head if it is the task or the computer that reserves a cDAQ chassis.  I want to say it's the computer so you can run multiple tasks from the same cDAQ.  But, you'd still need to choose ctr0, ctr1, ctr2, etc in each task so that you don't share these resources between tasks.
    Are you looking to pull the shared module out frequently?  If not, are you gaining enough functionality to justify buying two redundant modules to gain decoupling?

  • Graphics Card Crashes When I Open Final Cut X

    Never happend before, i started a project for a timelapse video and loaded about 3000 photos into final cut, loaded them to the timeline and 10 seconds later my whole computer restarted. I tryed opening again, right when my project opens, my computer restarts again.
    I have the imac 27" mid 2011, everything updated, i have 16gb ram with about 600gb free harddrive space.
    I know its my graphics card causing the problem for sure knowing by using Pro Maintenance tools. Im using Final Cut X (10.0.6).
    What do i do, im stressting out!!!!!

    If you're certain it is the graphic card then you're only recourse is to have it repaired by Apple or an Authorized shop.
    If you're near an Apple Store then that wil be the quickest solution.

  • K8MM-V will crash when using any Radeon Graphics Card (ok with NVIDIA)

    Can anybody help!!!
    Hi, OS MCE 2005 (Fully Patched) I have tested my system with 3 fully working ATI Radeon Cards (9800Pro, 5550 & 9200SE) all cards crash when entering Media Centre GUI or using any 3D app (e.g 3DMark 2003). I have fitted an NVIDIA 5900XP and the system runs 100% stable. I have a fresh install of OS, .NET ,Motherboard & latest ATI Drivers (V5.10) drivers. I have even fitted a replaced the motherboard (MSI K8MM-V. Is there a fix or are ATI cards incompatible with this motherboard/chipset. Any advice greatly received.
    MSI K8MM-V MB
    512MB DDR 400 (Crucial)
    160GB SATA HD
    Athlon 64 3000+
    NEC DVD/RW
    Hauppauge WinTV-PVR 150
    Gigabyte GN-WPKG Wireless PCI Card
    Sound Blaster Live 5.1
    ATI Radeon - 9550 256MB or 9200 128MB or 9800Pro 128MB
    Media Centre Edition 2005 - Patched
    ALL CARDS AND DRIVERS NOT INSTALLED EXCEPT ATI for testing.

    I flashed to 9.20 and my video went in the crapper and the computer became unstable, unusable really .  I had crashing with my 9800 Pro and installed a 9200 and it worked fine.  I read on another topic to change some BIOS setting, for me it was turning off the spread spectrum under the cell settings that changed everything .  Once that happened, about 5 minutes ago, I booted for the first time in a week and the 9800 Pro appears to be working fine. 
    Look at this link...https://forum-en.msi.com/index.php?topic=89456.0
    Props to Tiresmoke for the fix
    If it works, let the forum know so other can figure this out as well. 

  • Problems acquiring images with IMAQ-1408

    I have a IMAQ-1408 acquisition card that I recently transplanted from an old computer to a new P4. Initially, it did record a few images (both in one of my programs and using the test panels in the Measurement and Automation Explorer. Now it doesn't acquire. I have tried several things like switching PCI slots, adjusting some of the settings like the sync voltage levels and such, but I'm not getting any images. All 6 diagnositc tests past (from 'FPGA register' to 'Basic interrupt'). Also, the card is still detecting something - when I connect to a video source, I get the error ... when I have it disconnected from the video, it gives an IMG-ERR-VLCK. So it must be detecting some of the V-synch pulses. Anyway, at what poi
    nt do I decide that my card is non-functional? Are there any more setting adjustments I should try. (BTW, I'm using an NTSC source).
    thanks

    This issue is sounding more like a hardware problem if the diagnostics fail repeatedly. Before considering repair or purchasing a new board, I still recommend testing the card in another machine just to be thorough.
    The board most likely can be repaired (I'm not sure about the cost, since it is most likely out of warranty). Otherwise, the PCI-1409 board is similar to the 1408, but has several advantages. Please see this KnowledgeBase for more information on the differences. If you are interested in the repair/replacement options, please generate a service request to speak directly with an engineer. You can generate a request online at "http://www.ni.com/ask">www.ni.com/ask. This will allow us to set up an RMA if need be.
    Regards,
    Jesse D.
    Applications Engineer
    National Instruments

  • FP11 - Graphics Card Crashes

    Hi Adobe,
    I'm experiencing regular graphics card crashes when viewing Molehill demos using the latest FP release 11.0.1.3d.
    For instance, these demos cause my entire screen to go black for 5 seconds and crash my whole browser:
    http://www.ringo.nl/projects/away3d/broomstick/LoaderOBJTest.html
    http://blam3d.com/demos/f16uvtest.html
    Any also, I can't watch any videos on Vimeo and half the time, youTube videos won't play for me.
    I've lodged bugs for these issues in Jira:
    https://bugs.adobe.com/jira/browse/FP-7191
    https://bugs.adobe.com/jira/browse/FP-7192
    But I'd like to know from Adobe, will these crashes go away when FP11 is released? There are so many different PC/Graphics Card combinations, will Adobe be able to ensure that Molehill applications won't cause crashes?
    My team has invested a lot of time in a big app that uses Molehill, but we are getting very nervous seeing so many crashes - please re-assure me and my team that FP11 Molehill will be rock solid at the time of release!

    obviously its NOT fine, and stability in a handful of other applications means jack.
    different applications apply different load in different manners to the hardware.
    There is an evident history of improperly configured hardware or actual hardware combinations causing problems in D3D but not in OpenGL, or in OpenGL but not in D3D.
    such is the case with a VIA KT600 and an nvidia GFX card at AGP 8x causing graphical corruption and crashes in D3D that never occured in opengl, or an overclocked i7 that absolutely only ever hung in opengl apps but not in direct3d apps(voltage insufficient).
    The sooner people stop blinding themselves to the realities of just how much a precise configuration matters, the sooner they'll fix their own problems.
    Seriously, if i can deploy flash across a wide assortment of hardware configurations and not get crashes or blackscreens, then its definitely saying about the  configurations of the denialists who claim their system is fine.

  • Mac G4 crashes using continuous generation with PCI-1200 DAQ card

    I've been trying to use a PCI-1200 DAQ card with a Mac G4 to create a continuous analog output signal. The problem is that the computer locks up after a while (a few minutes). I have been using the Generate Continuous Sine Wave vi, but the problem remains.
    I've tried slow signals (10Hz) and fast signals (2kHz) but the computer still seems to crash. I have no clue what is going on!

    bissdp,
    The first thing I would recommend is making sure you have the latest version of the driver:
    www.ni.com > Support > Drivers and Updates > Current Versions > Multifunction DAQ
    Another you could try is to determine what component is causing the computer to lock up. Use a process explorer utility to try to see what processes are locked up. A search in google might turn up utilities like this one: (http://www.clarkwoodsoftware.com/peekaboo/)
    Keep in mind heat or speed issues. It may sound funny, but you may want to try opening the computer case and making sure the board has enough air flow to keep it cool.
    These are just some ideas for now, I hope they help.
    Alejandro Asenjo
    Applications Engineer
    National Instruments

  • Error 10401 when switching to a new DAQ Card

    Hello,
    I am running LabVIEW 7.1. Initially the computer had a PCI-6024E DAQ card installed with Traditional NI-DAQ 7.2 and NI-DAQmx 7.2. The card worked fine.
    Recently I replaced the 6024E with a PCI-6225 DAQ card and it was not recognized by MAX. I then downloaded a newer version of DAQmx, 8.6.1 (I chose this because it is compatible both with the new 6225 and also the old version of LabVIEW, 7.1). Once I installed this, MAX recognized the 6225 and it passed all of the MAX tests, so I think the hardware is fine. However, when I run I get an error 10401. I then removed the 6225 and replaced it with the 6024E again, and the old card still works fine.
    With the 6225, the error 10401 occurs in 2 different subVI’s. I've attached a screenshot of the error and the subVI "DIO Port Config" where it occurs. The other subVI where there is the same error is "AI Group Config".
    I have a guess for why the error 10401 is occurring. I read on this forum that these two subVIs are Traditional DAQ subVIs, which can't be used if the board (6225) is setup to use DAQmx. Is this true?
    In addition to the error screen shot, I've attached a screen shot of MAX with the old card and a screen shot with the new card. You can see that the 6024 is setup to use the Traditional DAQ, but the 6225 uses the DAQmx. If the code is written using Traditional DAQ functions therefore it makes sense that there would be errors with the new card. When installing DAQmx 8.6.1 I was told that "a newer version of Traditional DAQ was suggested". MAX shows that my Traditional NI-DAQ is version 7.2. Recall this was also the version of DAQmx I had prior to installation of 8.6.1.
    Could installing an updated version of the Traditional NI-DAQ and then setting up the 6225 to use this instead of the DAQmx remove these errors? If this is a solution, does the 6225 support Traditional DAQ?
    I appreciate any help,
    Stefan
    Attachments:
    Error.GIF ‏153 KB
    MAX_new_card.GIF ‏48 KB
    MAX_old_card.GIF ‏70 KB

    It takes a little getting used to if you have never done anything but Traditional. I find that it is easier after using it for a few years now. It may be a bit of work depending on how complicated your code is. If you need help we can point you in the right direction. Look at the examples and work from there.
    Tim
    Johnson Controls
    Holland Michigan

  • .DMP crash when opening a the UDF bar on a customer equipment card CEC

    Anybody every heard of a client crash when opening the UDF bar for a customer equipment card?
    Specifically when using the golden arrows from a service call then opening the CEC UDF bar, it immediately causes a .DMP crash.
    Furthermore, it is only for one user, not for the manager user.
    Corrupted UDF?  Corrupted client?  (I am reinstalling the client right now)
    TIA,
    M

    Hi,
    Check this note:[1284009|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0001284009|B1 shuts down when trying to update/remove UDF] whether it relates to your issue.
    If in any case dmp file is created you must contact sap support,according to note:[1009615|https://websmp130.sap-ag.de/sap(bD1lbiZjPTAwMQ==)/bc/bsp/spn/smb_searchnotes/display.htm?note_langu=E&note_numm=0001009615|SAP Business One application shuts down unexpectedly]
    Hope this is helpful!

  • I am using a 6024E DAQ Card. Software is done in VB5. When closing the applicatio​n is there anything that I have to do to close the card or just simply exiting is OK ? I am just using the AIRead_Sca​n and DigInPort functions.

    When using the 6024E DAQ card, with VB5, is there anything that one has to do to close / shutdown the card before exiting the application. The application only uses AIRead_Scan and DigIn_Port functions.
    Raghunathan
    LV2012 to Automate Hydraulic Test rigs.

    Hello,
    You won't need any other functions after AI_Read_Scan or after DIG_In_Prt since both functions are for none buffered acquisitions.
    For more information, I recommend that you take a look at the shipping examples that get installed under the folder C:\National Instruments\NI-DAQ\Examples
    Good luck with your application!

  • Designer crashes when checking for contexts or loops

    Designer crashes when testing one of our universes for contexts or loops.  I implemented the solution suggested in #1377869, but it made no difference.  Checking loops/contexts in other similar universes (similar in complexity, connection, number and types of tables) does not crash Designer.  This happens to all Designer users, not just me, and from any computer, including the server.
    We use BOXI R2; Fixpack 2.6. 
    The universe uses DB2.

    Hi Ingo,
    thank you for your help. My next step is to open a customer case. But what's about the logging? Is there a way to enable additional logging/trace for the BO Designer?
    Best Regards
    Matthias

  • Sound Card Problem, or Driver Problem? Games crash, when they didn't befo

    Not sure what the problem is, but seems to be a sound problem of some sort. I have just re-installed Vista 64. And now when I try to play BF242, the game crashes before I even see any kind of gameplay. It also instantly crashes when I click on the audio options tab. I have installed the latest drivers from the site. I have even uninstalled them, and launched the game without any drivers, and the game runs perfectly fine, but only without sound.
    But I've been able to play BF242 before, but it would evenutally crash after a while, but at least I was able to get into the game. So knowing that Ive been able to play before, and it played without any drivers, I dug up some drivers that I know I had working at one point when the game was playing. And it still crashes before it gets into the game.
    So this makes me wonder, is this really a driver problem or a soundcard problem?
    All sounds are perfectly fine elsware, music, movies, OS tones, web, etc. Crysis runs perfectly fine. Company of Heros Crashes, Quake Wars crashed about 0 mins into a game. Team Fortress 2 runs perfectly fine. Battlefield 2 instantly crashes.
    Here's my specs:
    Vista 64 Ultimate
    Asus P5W DH Deluxe
    Asus nVidia 8800 GTX
    4gig Corsair XMS2 240-Pin DDR2 SDRAM DDR2 800 (PC2 6400) Dual Channel
    Powersupply Antec True Power Trio TP3-550 550W ATX2V Power Supply with Three 2V Rails
    Sound Blaster x-fi fatality (whatever the one that comes with the front computer interface)
    Any help would be great. I'd hate to go buy a new sound card just to try it, unless I had a pretty good idea that it was the issue.

    I think I found the problem. It was the physical card itself. I pulled my old Audialogy card out of my old machine, and swapped it. Now BF242 runs.
    And mine never went to a black screen, and had to hard reset. It just dumped right to the desktop with a message "bf242.exe has stopped working."

  • System crash when DAQmx call to USB DAQ device is powered off

    My PC crashes when I attempt communication with a NI DAQPad 6015 USB device which is in the powered off state. I am attempting to add error handling to my LabView application to cover the above condition, however, instead of receiving a error message, my PC crashes. When the device is powered on, my LabView routine works properly. I created the vi using the DAQmx DAQ assistant for a simple analog read from the device. I want to add the potential error handling condition to cover the case in which a user may attempt to run the software without turning on the device. When I attempted to run my vi twice with the device powered off, my PC crashed both times. The 2nd time, during reboot, I discovered that MAX was corrupted and had to repair using the installation CD.
    I am using LabView 7.1 with DAQ 7.4 on Windows 2000.
    Is there a known fix or workaround to this issue? Or is there a way to detect the presence of the device first before trying a DAQ read?
    Thanks,
    Joel

    Thanks very much for both your responses. I tried it again, but as you suggested, I used one of the example vi's. I chose the following:
    Acq&GraphVoltage-IntClk.vi found within: Hardware Input and Output >> DAQmx >> Analog Measurements >> Voltage
    I first tested the example vi with my DAQPad-6015 powered on. The vi successfully ran without error. I then turned the DAQPAd power off and ran the vi again. My system immediately crashed leaving me with a blank screen (with streaky lines) and forcing me to reboot. After reboot, I discovered that I can no longer open any of the DAQmx examples that are compatible with the DAQPad-6015. All are corrupted. Curiously, MAX was not corrupted again. I will have to re-install all examples and possibly LabView itself.
    Based on your feedback, I am guessing you will tell me that repeating the above on your system will simply produce an error message, as expected. It appears that I may have a fundamental incompatibility between my specific system hardware and DAQmx/LabView.
    Regards,
    Joel

  • Why is it that I can't do a continuous streaming to disk with a 5102 scope card (PCI) when I can do it with a DAQ Card of much lower specs (my requirement is for small sampling rates only)?

    I am told that the 5102 Card (PCI) does not support continuous streaming of data to the hard disk. My application requires only very low sampling rates. If I can do it with a low spec DAQ Card using LabView why can't I do it with this card?

    Hello,
    The PCI-5102 is a high-speed digitizer card that has a slightly different architecture than the DAQ cards and was not built with the ability to stream data to the PC. However if you are sampling at low rates you can still acquire up to 16 million samples, which is done by using dma to tranfer data from the onboard memory on the 5102 to the PC memory. However, you will not be able to save the data to disk until the acquisition is complete.
    Another option would be to purchase either a DAQ card or a PCI-5112. Both boards can continuously stream data to the host PC and you should not run into any PCI bus limitations if you are stream to disk at relativiely slower rates.

Maybe you are looking for