PCI-DIO-96 on Windows 7 64 bit

I was running Labview 8.5.1 with a PCI DIO-96 card on a PC using Windows XP Professional. The PCI DIO-96 driver was a Traditional DAQ Legacy 7.4.4. The PC died and was replaced with a PC using Windows 7 64 bit. I loaded Labview ok, the PCI GPIB card seems communicates ok. I tried loading TDAQ750 but it appears it only supports Windows 7 32 bit. I also tried NIDAQ951F2 with no luck. Any suggestions to getting the PCI DIO-96 going before i ask our IT to load Windows 7 32 bit? At this point i don't know if Windows 7 32 bit will work.

Try using the DAQmx drivers instead of the Traditional DAQ.  It is a much better API anyways.  If DAQmx doesn't support that card, go with the PCI-6509.  It is a very good card and I'm pretty sure it can be a drop-in replacement.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Similar Messages

  • PCI DIO 32HS (6533) Suddenly giving "The device is not responding to the first IRQ level" error, and no longer functioning.

    Greetings NI folks,
      I'm an oceanographer, and have an sidescan sonar data aquasition computer running Windows XP SP2, and NiDAQ 7.0 (Legacy). For several years, this machine has worked flawlessly, but today, I booted it up to test the system for an upcoming job, and I got some strange errors in our sonar program. I tranced the problem to our NI-6533 PCI-DIO-32HS card. I launched NI Automation Explorer to test that the card was responsive, and when I click the "test panel", I get an error: "The device is not responding to the first IRQ level." Continue (yes/no). If I click yes, I can test the digital i/o's, but nothing happens, and all the tests fail (nonresponsive). I tried moving the card to another PCI slot, tried forcing it to have a specific IRQ that was unused by anything else, and finally tried moving it to another computer that had never been used with the DIO card. I'm still getting the error, and the card is nonresponsive. I'm at the limit of my abilities, and would like to know if there's anything else I can do, or should we send the card back to NI for repair/diagnosis.
    Thanks.

    Duplicate Post
    Best Regards
    Hani R.
    Applications Engineer
    National Instruments

  • PCI-DIO-32HS (PCI-6533) setup problem

    Hello
    I am in the process of setting up a Windows XP-based Labview 7.1 system and I am encountering a frustrating problem. Just to make sure I provide enough details, I'll describe what I've done so far, step-by-step (sorry if this gets tedious):
    First, I installed Labview and the NI-DAQ 7.3 drivers. I powered down the system and installed two PCI cards: a PCI-6031E and a PCI-DIO-32HS (PCI-6533) in PCI slots 1 and 2, respectively. I powered the system back up, went into MAX and configured the cards as follows:
    PCI-6031E: Device 1; AI: Polarity/Range=-10.0V - +10.0V, Referenced Single Ended; AO: Polarity=Bipolar; Accessory=SCB-100
    PCI-DIO-32HS: Device 2; Accessory=SCB-68
    I then started up Labview and ran my VI. This VI has been in use for 2 years now on the same NI hardware, so it's been well-tested and works great on other systems. However, when I run it on this system, the PCI-DIO-32HS spits out an error, with "Digital Buffer Write" as the source, and with a code of -10843 (buffer underflow).
    What's interesting is that I had this exact same problem when I was setting this system up in Mac OS 9. That time, I realized that the problem could have been due to the fact that I installed the hardware before I installed the software, so there may have been problems communicating with the device. By uninstalling everything and then re-installing it in the proper order, I solved the problem and was able to run the VI flawlessly. I'm assuming that these two problems are related in their nature, but this time around I was very careful to make sure that I did all of the setting up properly (I did it twice just to make sure. It did not work either time), so I'm not sure what could be the exact source of this one.
    Please let me know if you have any ideas as to what the source of this problem might be. Like I said before, I think there's probably a resource problem that's causing a communication failure which results in no data being sent to the DIO card (hence the buffer underflow error), but I can't figure out where to look for such a problem or how to fix it. Obviously, I'm rather new to Labview and everything about it, so the help is greatly appreciated.
    Thanks!

    Hi,
    Thanks for the reply. I have run the test panels, and I have not generated any errors in them. I've verified that I can definitely do output, because LEDs on my equipment turn on when turn on output on certain channels.
    So, I agree that the problem lies in the VI. I was not the author of the VI, however, so I'm not sure where to look. The author was also kind enough to have not provided any documentation. What would be a good example VI to run? I've never looked at any of them.
    As for how the program works, I don't believe there's any actual input coming back into the DIO-32HS. The system is used for electrophysiology. The DIO sends a signal to flash LEDs at given intervals. Electrodes then pick up an electrical signal from the retina of a mouse, which is sent to the DAQ card and written to a file. I have run complete tests, and proper data files were generated and contained expected voltage values. The only part that's not working right now is that the LEDs aren't flashing due to this error.
    I did some digging around in the program, but I couldn't come up with much. I verified that the program expects the DIO card to be Device 2, so there's no problem there. Aside from that, I couldn't find anything that seemed like it would apply.
    Thanks for your help! I have no experience with Labview, yet I've found myself placed in the "Labview expert" position over here, so I've kind of been forced into a sink-or-swim type crash course where I learn as I go.

  • How do I create an interrupt on the PCI-DIO-96 from an external signal connected to the lines PC0 or PC3 of a port?

    Hi everybody,
    we are currently using the PCI-DIO-96 for data acquisition from an old AT-DIO-32F card. All PPIs and ports work in mode 0 (standard input/output). The manual mentions the possibility to create an interrupt from an external signal connected to the lines PC0 and PC3 of port C from a PPI. To get the interrupt I have connected my interrupt service routine to the PCI-DIO-96, enabled the master interrupt enable bit in the interrupt configuration register 2 and enabled interrupt enable bits of every PPI chip in the interrupt configuration register 1. The interrupt should be generated if a signal low-to-high transition occurs on th
    e lines PC0 or PC3 of a PPI. We've simulated the signal low-to-high transition with an external voltage source connected to the line PC0. We actually saw in the memory that the line toggled from state low to state high, but no interrupt was generated. I don't have a guess what I am doing wrong. Perhaps anybody knows the solution of this problems.
    Thanks and best regards.
    Sven Jungnickel

    You may want to try disabling your USB or IEEE-1394 host controller. It's possible that one of these devices could be on the same interrupt as you DIO-96 and causing the interrupt to not be serviced.
    Regards,
    Erin

  • Basic questions about PCI-DIO-96

    Hi
    I am trying to write code to control a digital I/O board for the first time.
    I have a legacy board, PCI-DIO-96, as the code implies, it is a PCI digital I/O boiard with 96 I/O channels
    My first question is, what would be the drivers and development platform I should download for this board?
    I am planning to write my code in C++.
    The second question is, I am trying to write a very simple application to drive 96 solenoid valves through the board.
    Basically I need to use the board in output mode only.  No data gathering here.
    The application basically needs to open and close these valves  for a specified number of milliseconds.  So basically,
    I would be sending either 0 or 1 through the output channels, that's
    it.    If I send a "1" signal through the board, does
    that
    "toggle" the channel, meaning the channel will keep sending "1" through the ouput until I send another signal, or do I need
    to send the "1" signal every few milliseconds to simulate a constant "1" signal?
    Does anyone have code samples or know where I can find code samples illustrating this simple case?
    It would be greatly appreciated.
    I realize these are very basic questions, but I am new to hardware programming and I am on a deadline.
    Thank  you
    Kiko

    Hi Kiko,
    Great to see that you are asking questions here first, you definitely came to the right place.
    Since you are starting with a clean slate as far as knowing how to use this board we can start off on the right foot. 
    Download the latest version of the drivers for your board.  You can find the drivers here: NI-DAQmx Version 7.5 for Windows 2000/NT/XP
    After you have downloaded the drivers, power down the computer,
    insert your board, and power it back up.  The board should now be
    recognized and the drivers will install similarly to any new hardware
    would in Windows.
    Now it's just a matter of learning how to use the commands that you need to get started.
    I would recommend starting in the example files.  You can find
    some excellent examples that should do almost exactly what you are
    trying to do by looking in this path:
    C:\Program Files\National Instruments\NI-DAQ\Examples\DAQmx ANSI C\Digital\Generate Values
    Look for the example that best represents what it is you are trying to
    do.  You will notice that all of the examples have a general flow
    to how they call the board.
    Create a Task and Define what that task is meant to do
    Set the configuration for how exactly that task will operate
    Read/Write various values until a condition is met
    Close the Task
    Error Check all operations to assure that everything is working properly
    It's really not all that difficult and should you run into any problems or errors don't forget to search ni.com or the forums to see if others have run into similar issues to what you are facing.
    Regarding how the states for digital lines work.  The short answer
    is that if you set a digital line to high it will stay high until you
    set it back to low and vice versa.  For more details on everything
    digital check out our Digital Fundamentals page.
    Best of luck!
    Otis
    Training and Certification
    Product Support Engineer
    National Instruments

  • Digital Handshaking with two PCI-DIO-32HS Cards

    Hardware: two PCI-DIO-32HS Cards
    Software: LabVIEW 5.1, NI DAQ 6.6
    Problem:
    I'd like to do burst digital handshaking with two PCI-DIO-32HS cards.
    One being used for sending bit stream while the other receive.
    Suppose I want to use burst handshake mode.
    How should I wire the connections?
    Where should I wire the REQ, and ACK line from the sending card?
    Should I wire REQ from card one to REQ of the other card?
    Also, how do I configure labVIEW VI to do burst handshaking mode.
    Can anyone send me a VI that can do this.
    Thanks a lot.

    Matt,
    I would recomend using the DIdoubleBufPatternGen.C examples that ships with NI-DAQ. You can find it in your \NI-DAQ\Examples\VisualC\Di folder. If you don't have this example on your machine, you can get it by running NI-DAQ Setup and selecting support for C/C++.
    This example does double buffering to allow you to continuously acquire data from your card. Data is transfered only when a full 1/2 buffer is ready. You can set how long to acquire data by setting the number of half buffers to read, or by modifying the read loop conditional parameters to fit you needs. See the NI-DAQ help on how to set you REQ pulse rate to 100kS/s.
    Nick W.
    www.ni.com/ask

  • Who has had a PCI-DIO-32HS card fail, ever?

    I've looked through the forum somewhat and I've found little concerning the card itself failing.  For instance, I found something about the card failing due to driving it with a TTL high before it was powered, but that was about it as far as actual death of the card.  Hence, I'm wondering if others besides myself, and therefore my design using the PCI-DIO-32HS, have killed or had the death of a PCI-DIO-32HS DAQ card and what was determined to be the root cause in your case(s).
    Also, by chance, did your card's death also take down the PC such that it wouldn't POST (Power On Self Test) until the card was removed?
    Thank you all.

    First, the issue has not been resolved yet. I still have boards dying. At $1500 a pop, this issue needs to be resolved.
    I was mistaken about two things said earlier: 1) The G card has now failed; therefore, the recovery was a fluke, and 2) I thought 8.x was installed in the design's PC, but as it turns out it has been 9.x. (The version numbers are tough to remember. Sorry. I think it's 9.1.7.) Is there a known issue with that one also?
    What I really want to know is why the original board I returned to NI failed. I want to know specifically what slot contacts are holding up the PC, keeping it from performing its POST? I don't want to hear any more suggestions for installing version x.y.z. without also having a specific reason for why it should work. These cards are too expensive. There's something very wrong with this design such that I can't keep the DAQ card alive using Traditional DAQ software that has run for years. The system works until (it seems) you think the problem's been resolved, and then whammo! An esoteric error number in a window is thrown up. (It's not just one error. The error can change as you try in vain to avoid cycling power as the only way out of the now dead software.) You can't run the software past a button click due to the error window, but yet the PC itself works fine...unless you cycle the power: NO POST.
    What on earth in this design could be killing these cards? The PCI slot was tested via substitution with a video card and there was no issue found. I just can't keep the DAQ card alive. Help! Trying version x.y.z of the driver is not a good enough solution. Running software should not just out of the blue blow up a DAQ card and cripple the PC only at power-up. Rather, there should be an error, some incompatibility indication before the card is dead. Frying a $1.5K card...eventually...is not how you find the source of an incompatibility issue. Like I said, HELP!
    I'm suspecting the software is creating a bus contention somehow which doesn't end in an error but, rather, an internally shorted IC, where I'm guessing it's the large NI ASIC just above the card edge due to the considerably noticeable heat generated while the PC tries to POST, a short that is undetectable except that the software stops working, but nevertheless a short that won't let the PC continue its POST if power is removed and then reapplied to the PC. It's like the software has had a "sacrifice(PCI-DIO-32HS, legacy_sw);" function embedded into it that only gets called under certain circumstances, circumstances that involve the power-up sequence of a PC. Help!

  • PCがリブートする(PCI-DIO-96,PCI-MIO-16EX-10)

    PCI-DIO-96とPCI-MIO-16EX-10を使用しているソフトがあり、今回、若干の変更を行いました。
    変更前から使用しているPCで動作させたところ、まれにPCのリブートが発生してしまいます。
    ソフト変更部分には特に問題は無さそうです。
    リブート発生時に以下のようなイベントログが記録されているようです。
    対処方法をご教示頂きたく、宜しくお願い申し上げます。
    <Event Log>
    Type Information Event ID: 1001
    The computer has rebooted from a bugcheck. The bugcheck was:
    0x000000d1(0x00000000,0x00000002,0x00000000,0xbff286fe).
    Microsoft Windows 2000[v15.2195]. A dump wa saved in: C:\WINNT\MEMORY.DMP.
    動作環境は以下の通りです。
    <PC>
    DELL Optiplex GX60 BIOS:A08
    <OS>
    Windows2000 SP4 5.00.2195
    <Measurement & Automation Explorer System Information>
    NI-DAQ    6.9.2f8
    NI-PAL Sowftware 1.5.6f0
    CVI Run-Time  6.0.4.105
    IVI Engine   1.83
    NI Spy    1.4
    NI-VISA    2.5.2
    以上

    Intoさん
    　参考になるか分かりませんが、過去にプログラムを若干変更した後にランダムに再起動する症状の
    報告があります。
    　NIPALK message（NI Discussion Forums>MultifunctionDAQ)
    　解決策としては、NI-DAQのアップデートで直ったようです。もし今お使いのドライバのバージョンに
    こだわりがなければ、最新版をインストールされてはいかがでしょうか。
    　NI-DAQmx 8.8 - Windows 2000/Vista x64/Vista x86/XP
    　Intoさんは以前にも同様のご質問をされていたかと思いますが、そちらは改善されたのでしょうか。
    ひょっとしたらWindows 2000にすることで解決されたのでしょうか。もしよろしければ教えてください。
    このメッセージは　 10-25-2008 07:51 AM
    に Hisasis TAKASU が編集しています。

  • I was trying to find out if the PCI-DIO-32​HS will take thermocoup​le readings?

    I have a PCI-DIO-32HS and a SCB-68 connector block. I am trying to figure out if the card will receive the input coming from a thermocouple.

    Dennis is right.
    however, if you feel like not spending more money on a analog input board, and have hands for a little electronics, here what you can do:
    1) use a 16bit D/A converter (eg DAC7744), connected to the card.
    2) connect the output to a comparator (LM311),  to compare with your own analog input. you might want to isolate the 2 inputs via INA105.
    3) connect the output via a pull up resistor directly to pin 1 of your parallel port.
    4) create a small Labview program for making a 16 (or 8 or 4) bit comparison process:
           - create an analog value of 0V (via 16 bit digital card)
           - check if response is true or false (higher or lower than your  analog in) from the parallel port
           - if true, send new analog value of -5V
    ....check again, 16 times.
    you got your analog value. of course this is a relatively slow process, as you have to read the parallel before each time you send the new analog value. yet, it is going to be much faster than a NI-USB 6008 for example. i expect a rate around the KHz at least.
    ... And here's where I keep assorted lengths of wires...

  • Installing PCI DIO 32HS 6533 card

    I'm back to using DAQ after 5 years on other things...
    I can't find the CD that came with my PCI DIO 32HS 6533 card (my desk is a
    meter high mess of paper, disks, broken cards...)
    I installed NI-DAQ from the CVI 5.5 CD but upon reboot I still get the
    "Windows found some new hardware" without being able to point it to the
    correct driver, and in addition I get a "Missing NICFQ32.DLL" error.
    Any help ?
    Guillaume Dargaud
    CNR/IFA
    http://sung3.ifsi.rm.cnr.it/~dargaud/
    http://sung3.ifsi.rm.cnr.it/~domec/
    http://sodarserver.ifa.rm.cnr.it/
    "Q: How many software engineers does it take to change a lightbulb ?
    A: It can't be done; it's a hardware problem."

    Go to www.ni.com choose download software then drivers and updates then NI-DAQ
    then 6.8.1 for Windows (if you have windows)
    "Guillaume Dargaud" wrote:
    >I'm back to using DAQ after 5 years on other things...>>I can't find the
    CD that came with my PCI DIO 32HS 6533 card (my desk is a>meter high mess
    of paper, disks, broken cards...)>I installed NI-DAQ from the CVI 5.5 CD
    but upon reboot I still get the>"Windows found some new hardware" without
    being able to point it to the>correct driver, and in addition I get a "Missing
    NICFQ32.DLL" error.>>Any help ?>----------------->Guillaume Dargaud>CNR/IFA>http://sung3.ifsi.rm.cnr.it/~dargaud/>http://sung3.ifsi.rm.cnr.it/~domec/>http://sodarserver.ifa.rm.cnr.it/>"Q:
    How many software engineers does it ta
    ke to change a lightbulb ?>A: It can't
    be done; it's a hardware problem.">

  • Why ACK should be deasserted sometimes during the data acquisition with PCI-DIO-32HS burst mode handshaking?

    My peripheral device sends 32-bit data to the DIO board serially with PCLK 6MHz, about 300,000 times totally. The phenomenan like I mentioned in the summary above happens, and it causes some data missings.
    Though I know ACK is not always asserted as somewhere in the NI database says, I want to know why it happens. if I can. I wonder if it is just inevitable or not.
    Do I only have to add some buffer memories to my device and make it watch on the ACK changing? Or, is there any other good way to avoid this problem?

    Hi,
    Burst mode handshaking protocol needs to conditions to be meet before data can be transfered. The PCI-DIO-32HS need to be ready to transfer data and the external device needs to be ready to transfer data.
    The ACK line tells the external device when the PCI-DIO-32HS is ready and the REQ line tells the PCI-DIO-32HS when the external device is ready. When both are ready data should be transfered. This is the nature of Handshaking, guarenteed data transfer (when both devices are ready), but not at a guarenteed rate. Handshaking means that the two devices communicate with each other to determine when to transfer data.
    The PCI-DIO-32HS ACK line is toggling low because the PCI-DIO-32HS is busy catching up with the given transfer and is not ready to receive m
    ore data at this time. The ACK line is not something you can control, it is controlled by the PCI-DIO-32HS.
    Your application may be better suited for use with Pattern I/O if you are not using the handshaking lines, ACK and REQ, to control the flow of data. Pattern I/O does not use handshaking lines and clocks data in on every rising edge of the clock. You may receive an error if your system can not keep up with the transfer rate.

  • Drivers for PCI-DIO-96

    Can someone in NI tell me how to download NI DAQ software for the PCI-DIO-96 that will work with windows vista

    Hi
    That depends on what LabVIEW version you are using and if you are after DAQmx or Tradition DAQ. The device is still supported in DAQmx 9.1.1 (as per the readme). That version is avaliable for Vista, but you'll have to check if it's compatible with your LabVIEW version. If you want Traditional DAQ the latest version is 7.4.4, but is only officially avaliable for XP/2000. That said I currently have it installed on Windows 7. I've nver actually used them since I reinstalled but they did insall and I have seen them installed on Vista machines as well. Give it a try and see.
    Best Regads
    David
    NISW

  • Pci resource pci-dio-96

    I have inserted a PCI-DIO-96 in three different PCs riunning Windows XP.  In all cases the Device Manager does not show resources allocated automatically to the card.  It is recognised as being a "PCI card" but no further progress is possible - there is no data posted in the "properties" sections of the DM.  Does this suggest that the card is faulty?
    Do I understand the installation procedure correctly - resource address allocation should be automatic?

    There should have been a disc that was shipped with the DIO card that has DAQmx.  If you do not have that, the latest version can be found here: NI-DAQmx 14.5.1
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Can Group1 and Group2 of the PCI-DIO-32HS 6533 card be configured at the same time?

    Can the PClk1 and PClk2 run simultaneously when both groups 1 and 2 are configured?

    Tmax,
    Yes, both Group 1 and Group 2 of the PCI-DIO-32HS can be configured at the same time. Furthermore, both PCLK1 and PCLK2 can run simultaneously.
    Good luck with your application.
    Spencer S.

  • How to use the PCI-DIO-32HS counter

    I have to create a SPI, I'd like to use counter, but the card doesn't answer, so Labview bug. Do you if there is programmable/configurable counter on this Card?

    Hello,
    The PCI-DIO-32HS does have a counter onboard. However the counter is only used for generating an internal clock in order to do pattern generation. You cannot program this counter in LabVIEW. If you need a counter, I would look at using an M Series Board, or a 660X board.
    Best regards,
    Justin T.

Maybe you are looking for