MAX 2.2 refuses to see PCI-DIO-96

I am trying to install and configure PCI DIO-96. MAX 2.2 refuses to see it. I have uninstalled NI-DAQ (ver 6.9.2) with several times, both with and without the board in the computer. The device manager can see it and reports that it seems to be functioning normally. I
have also tried reinstalling MAX. Is MAX broken? Does NI-DAQ continue to stay around inspite of being removed (de-installed)? is there any other way to configure and test the DIO-96?

I have finally convinced MAX that there is a DIO-96 board in my system. However it is not by what I would call "normal" means. In MAX, I went to Tools>>NI-VISA>>VISA Options... and selected "Show all PXI/PCI devices accessable to VISA"
Now after refreshing MAX, I can see the board but only through a VISA or PXI as an intermediary.
PXI System
PXI Bus 0
PXI0::16::INSTR (PCI-DIO-96)
I would rather NOT operate the board through this rather complicated looking VISA style interface
if I can avoid it.
Have I done something wrong by installing something I don't need (like VISA)? Can I get rid of it? How?

Similar Messages

  • Pci-Dio-96 and Max

    I'm using a PCI-DIO-96 and am aware that the default power up state is high and can't be changed. When I open up NI-Max, the application sets all ports to high,
    even after I have set them low in my own app. Is there a way to prevent Max from doing this?
    Curt

    Hello;
    Please refer to Chapter 3 of your hardware's product manual in the section titled "Digital I/O State Selection" for any jumper locations and configurations.
    PC-DIO-96 -- Inputs (high-Z) pulled up through 100k
    Hope this helps.
    Filipe A.
    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.

  • 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

  • Measuremen​t of CMOS signals using PCI-DIO-96

    I am trying to measure a CMOS signal level with current limiter resistor (25k) on the output. But the CMOS device is not capable of sinking the input of the PCI-DIO-96 because of the 100k pull-up resistors on the board. Will the PCI-DIO96 work as an input if I remove the 100k resistor or use e.g. 500k instead?

    Hello;
    When a digital board has a pull up resistor, that means the output line is a open collector type, so, a "external" connection needs to be made to the Vcc supply. Then, when a current is applied at the base of the transistor, the transistor switches and the ground (low state) is connected to the output lead. If no current is applied to the base of the transistor, then the Vcc level is being output at the output lead, meaning a high digital state.
    The value of the resistor is chosen depending on the specifications of the transistor used as the gate. As my understanding, as long as you increase the values of that resistor you shouldn't have any problem as far as high current flowing trough the transistor when it switches. I've never tested that myself, but I
    don't see why that couldn't be done.
    But always keep in mind the warranty will void if you make such changes.
    Hope this helps.
    Filipe

  • PCI DIO 32HS

        Hi,
        I have a legacy VI that I am troubleshooting. It involves configuring input & output digital ports on our PCI-DIO-32HS.
    Two ports (Port B & C) are configured as outputs. I have a suspicion that Port C is not operating correctly (or at least some of the lines on Port C are not operational).
    Is there a way of verifying the output operation of Port C ? (I have checked out the Test Panels in MAX - maybe there is a more direct test ?)
    Earlier, our computer crashed when I tried to reboot. Immediately before that the VI & NI488.2 Communicator were running at the same time - perhaps there was a hardware conflict that caused the crash ? Besides this incident, the program has been running fine for several years...
    Finally, is the PCI-DIO-32HS available for sale ? If not, what is the closest substitute ?
      Any help would be greatly appreciated !
        Regards,
             ak

    Hello ak,
    What is it about port C that you believe is not working anymore? You could try generating on those lines, and then test the correct pins with a multimeter or scope.
    Please also do a device Reset from MAX and verify that the device passes a Self-Test.
    We no longer sell the PCI-DIO-32HS, but we do have a wealth of other cards that are HSDIO. I don't know what kind of specs you want, but this is a great starting spot: http://www.ni.com/highspeeddigitalio/
    Any card that starts with 65xx is a HSDIO card. I believe the PCIe-5635 will be the closest replacement spec-wise, but you will need DAQmx or NI HSDIO for the programming, I do not believe you can use Traditional DAQ.
    Thanks,
    Joel C
    National Instruments

  • Pci dio 32hs burst mode

    We would like to use simultaneous input output data acquisition using the
    burst mode protocol.
    The problem is that we notice that the operations are not simultaneous: first
    a group and after the second.
    We have try all tipe of pclk (internal and external) and we connect req1 and
    req2 to an external manual trigger to have the same handshaking signal to
    both the groups. We also try to differ the active high or low of both the
    groups parameters.
    In the vi attachment, you find the simple 2 groups acquisition chains and
    it's easy to see that if you use an external clock of 1 Khz with 3000 input-
    output samples, the total acquisition time would be 6 second instead of 3.
    For our application it's necessary to use this protocol
    (not the pattern
    generation that we have tested in continuos and it worked) so we would like
    to have a solution to this problem.
    Since the pci DIO 32HS's manual asserts that it's possible to have 2
    handshaking operation simultaneous we didn't aspect so many problems.
    Thank you for your time
    Pier

    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.

  • PCI DIO 96

    Hi all,
    I have a tap test interface that operates the solenoid in a TEC.
    The computer communicates with the tap test interface with a PCI DIO 96.
     Since the program in the computer was written with older version of labview (supposed to be LabVIEW 5.x) and the block diagram is not available,
    to install the program in a newer version of OS, I downloaded the new driver for PCI DIO 96 for XP.
    But the old program in not running with the new driver (XP) in a XP installed machine.
    Is there any way to make the same program work in a XP system as there is no code available or any document for the tap test interface available to write a new program similar to the old one.
    Thank you ,
    VJ  

    Thank you ppl for your valuable inputs..
    Thank you John and Matthew for the suggestion.
    John, I downloaded the DAQ and replaced the one which I had earlier..
    the error that I got was
    Error - 10240 occured at DIO port config.
    Possible reasons
    NI-DAQ LV: The driver interface could not locate or open the driver.
    I have attached files which are snapshots of the error, the version of the labview used by the program, and the MAX screen which shows my device 
    I completly uninstalled the newer version of DAQ and installed the one you suggested.
    The device got listed in MAX and I was also able to test the device.
    But I got the above error. Can you please help me regarding this?
    Thanks for your suppport..  
    Attachments:
    max.JPG ‏98 KB
    driver error.JPG ‏69 KB
    about.JPG ‏102 KB

  • 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-DIO-96 Port to hardware pinout

    I'm configuring a PCI-DIO-96 (PN: 777387-01) using the DAQmx Assistant. The DAQ assistant allows me to program by port, ports 0 through 11. Could someone point me to link that shows DIO hardware connector pin numbers with respect to port numbers programmed?

    Jim77215 wrote:
    Why the ridicule? Yes I did search out the manuals and saw nothing with respect to Ports0-11 as they are programmed in the
    DAQmx assistant.
    It wasn't ridicule. There's a fine line between sarcasm and ridicule. 99% of the time when we see questions such as yours it's from people who simply don't bother opening the manual or performing a simple search. For those of us who have provided more than a few thousand posts this can get quite grating. Dennis has seen his fair share, I suspect. 
    Your initial question did not provide any information that you actually (a) had the manual, and (b) looked in it, which is way more than a lot of people who post questions on this board bother doing. So, kudos to you for actually doing that. In the future, though, please mention what you've done to prevent misunderstandings and/or people jumping to incorrect conclusions. It is, after all, a 2-way street. Thanks.

  • 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

  • Leopard refuses to "see" iPhoto, even when it's running.

    I'm having an iPhoto problem with Leopard that is different than the ones I was able to find so far. I did an upgrade install from OS 10.4 and had iPhoto 6.0.6 installed. After upgrading, iPhoto is still there, it still runs and my photos are all fine.
    BUT, the features in Leopard that are supposed to use iPhoto refuse to see my library!
    - In Mail.app, when I try to open the Photo Browser while composing a message and select iPhoto, it gives me a message saying "Open iPhoto 5 or later to see photos from your iPhoto library in this list."
    - In Preferences > Screen saver, when I choose Pictures Folder and Mosaic, the preview window says "You must have an iPhoto library to run the mosaic screen saver."
    - In iTunes, when I tell it to sync photos from my iPhoto library to my 5g iPod, I get an error upon syncing that says "The iPod 'Icarus' cannot be synced. An unknown error occurred (-50)", but it syncs fine if I tell it to sync pictures from a folder instead.
    - In iChat, the "Share iPhoto with iChat Theater" option is always greyed out, but I can share photos from folders.
    These problems occur regardless of if iPhoto is open or closed. I have about 270 photos in my library. The files are located in Home/Pictures/iPhoto Library. The only iPhoto plugin I have installed is the Picasa Web Albums uploader.
    Any ideas?

    I decided to install iLife '08 and updated iPhoto to 7.0. After doing that, it resolved all of those problems, but the error messages I previously had indicate that iPhoto versions below that should work.

  • 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

  • ITunes refuses to 'see' external drive

    All my tunes are on an external LaCie 120GB mobile HDD as they have been for a couple of years and all has worked well. Now for some reason iTunes refuses to 'see' the iTunes Folder on this drive it doesn't even seem to see the drive at all. The drive is fine as I can double click a tune from it from the finder and it plays it in iTunes ok.
    iTunes also recognises an interacts properly with my wife's iPod.
    I have checked and rechecked that the iTunes/Prefs/advanced/iTunes music folder location is set to the HDD folder.
    Is this a problem with the latest iTunes version?

    I have stopped, started, uninstalled, reinstalled, used msconfig to stop all other processes, changed drive letter, shut down, reboot, restart with IPot connected, restart with IPot disconnected... nothing on the Apple page has been of any help. Could it be something to do with low power USB v/s high power USB? All thought I don't buy that either. My wife has an IBM T42 and it works no problems, mine IBM T43, does not work. Other USB devises do work on my T43??? Hense the point of this thread.

Maybe you are looking for

  • No sound during slides

    my boss is putting on a class tonight, and is using keynote. the problem is that he is not getting any sound from the embedded movies. any help would most likely save my bacon, so to speak. if it matters, he is using a macbook pro, released right bef

  • Cannot find intf mapping in interface determination

    Hi all, I have these bpm steps 1. Trasnformation followed by send sync. i am trying to do a receiver JDBC sync call to oracle db. 1. in my transformation i have my: 1. Request message : messageA mapped to 2.Response message JDBC request and in my syn

  • Apple Application Support - What and why does this exists?

    So I welcomed iTunes 9 on my computer and iOS4 on my music player (latter to a great commonly known regret). Now here is my question: What is the "Apple Application Support" and why iTunes 9 must have it to run? (Note: Normally many software products

  • Unable to Redeem purchased product

    I am unable to redeem a pre-paid card for Elements 12 and Premiere 12 package. I enter the card redemption code but nothing happens when I click on Redeem button. I have latest version of Flash on XP. Tried multiple times. I should make clear that th

  • Can you frce a date range

    I am trying to force a user to only enter a date between the range of 01/01/2009 to 12/31/2010. Is there a way to do this in a standard <cfinput>? I attempted to use the range attribute, but it does not like the format.