6533 (DIO-32HS) card performance figures

Hello all,
I have a question about the fast data transfer using PC computer and 6533
(PCI-DIO-32HS) card.
I understand that the DMA is the bottleneck in transfer. The DIO 6533 manual
offers
some figures (10Ms/s for some PC mother boards) about performance when using
pattern generation
mode. Are these figures reliable ?
Is it possible to obtain 10Ms/s performance ? The shortest timeslice in
6533 is 50ns, which is enough but how
about the DMA ?
I'd appreciate overall data throughput figures in function of a certain PC
configuration.
Thanks in advance,
Sami Laitinen

Hi Adikus
I have had the same problem recently - losing data points every time I transfer a half-buffer when acquiring in burst mode. Some application notes I found useful from the development library were:
Measurement Hardware > Digital Input/Output > Handshaking >'Handshaking I/O Issues Using the DIO-32HS/6533 Device'
Measurement Hardware > Digital Input/Output > General >'High-Speed Digital Considerations'
and
Measurement Hardware > Digital Input/Output > General > 'Digital I/O Applications'
The problem you are having is due to the fact that you are not using the REQ and ACQ lines. The ACQ line is controlled by the PCI 6533 card and signals when the card is ready for a transfer. If you have a look at this line during acquisition you should see that
it is set low briefly each time that you transfer a half buffer.
You need to monitor the ACQ line and pause your external card from trying to input when the ACK line is low. I've added a FIFO between my instrument and the PCI 6533 card. I've found that I require this to be capable of holding 16k samples but I arrived at this value through testing alone (I am acquiring 2 bytes at 1MHz). My testing also illustrated how other activity on the PC can affect the acquisition, e.g. saving a large file would cause a pause.
I've posted a couple of questions relating to this recently too which might be useful for you to check out.
Regards,
Cheryl

Similar Messages

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

  • 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

  • Programing Data Acquisition Card AT-DIO-32HS in LabView or ANSI C

    Hello,my name is Andreas an I work the first time with LabView. We bought the NI AT-DIO-32HS card. My problem: I have a rnadom-generator application, with two data-outputs , data1 is the random data, data2 is the shifting frequency from the shift register which shifts the random-data out, I must aquire the random data each time when a positive edge of the "shift-frequency" occures. Do you have some programing examples in LabView or in ANSI C to give me a first idea for the programing of these aquisition cards? E_mail: [email protected]

    Hi Andreasz,
    Welcome to LabVIEW!
    Any time I start working with a new device I start by searching the examples that ship with LabVIEW.
    Goto search examples. Take a look at the examples located in
    Hardware Input and Output >>> Solutions >>> 653x Logic Analyzer
    There you will find four example that will get you sarted.
    If you find these lacking, let us know what needs changed and we may be able to help.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Register Level programming of the AT-DIO-32HS

    I am working with a piece of software that was written using the AT-DIO-32F card. The original programmer did NOT use the National Instruments driver with that card, but rather used a software library that allowed him to access and manipulate the registers directly on that board. The name of the library is called NTPORT (http://www.zealsoft.com/ntport/index.html).  He did this because he was not able to meet the timing requirements using the NI driver.
    We have to replace the AT-DIO-32F card with the AT-DIO-32HS card, and I would like to know if I can continue to do register level programming with the 32HS card.  I have found that I also can not meet my timing requirements using the driver that comes along with the 32HS card.
    I checked this web page (http://digital.ni.com/public.nsf/allkb/B08F4125A9325B3F862565CC0073E68F?OpenDocument), and did not find the AT-DIO-32HS listed. Does this mean I can not program its' registers ?
    Any feedback would be appreciated !!
    Thanks !!

    Hi Raminta-
    The Measurement Hardware Driver Development Kit (MHDDK) provides examples and register documentation for the 653x devices (which includes the AT-DIO-32HS).  The DIO-32F and DIO-32HS devices are quite similar, so it is possible that your existing code will work.  The resources on the MHDDK page should help you fill in any differences.
    Thanks-
    Tom W
    National Instruments

  • At-dio-32hs

    I've tried to install my At-DIO-32HS card, on my computer under Win Nt and with labview 6.i and Ni-daq 6.8.1 but I was not able to configure it.
    I tried to refresh MAX or to install another time NI.daq, but AT-dio-32HS didn't appear under devices, and when I'v tried to create a new device from MAX I saw AT-Dio-32F only between the choices.
    What can I do?
    Thank you,
    Paolo5

    Here are a few KnowledgeBase entries I found by searching the ni.com support pages (search= +nt +at-mio +install). Although, the solution could any number of things, these documents point out some unique installation steps on NT machines.
    Installing Plug and Play Support for ISA-bus Boards on Windows NT 4.0 Systems
    AT-GPIB/TNT (PnP) Board Is Not Recognized in Windows NT
    Assigning a Driver to
    an ISA PNP Device under Windows NT
    Hopefully these are helpul. Good luck!
    -Craig
    -scraggs99

  • NI PCI 6533 DIO to NI PCIe 6536 compatiabl​ity

    Hi All,
    I have NI PCI 6533 DIO PCI card which is very old and now NI is not manufacturing the same card , so it is replaced by NI PCIe 6536 DIO . I am using the PCIe to PCI adaptor as I dont have the PCIe slot.
    Now my questions are :-
    1) does the same DLL can be used to NI PCIe 6536 DIO ?
    2) I am using the LabView 5.1 for NI PCI 6533 DIO is that same can be compatiable for NI PCIe 6536 DIO .
    can any one please help me in above questions
    Thanks in advance
    Hussain .

    No and no. The 6536 requires the DAQmx driver and DAQmx is not compatible with version 5.1. So, you finally have a good reason to upgrade LabVIEW.

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

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

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

  • DIO-32HS: All outputs go high (intermittently) after completing a single pattern buffer

    My application uses a PCI-DIO-32HS board in double-buffered pattern generation mode to output a series of 32-bit wide words synchronized to a 1 kHz external REQ pulse (rising edge). The approx. 1 Kword buffers are created about once every two seconds, so throughput speed is not an issue. However, once every few thousand successfully output buffers, all 32 lines are driven high out-of-sync with respect to the REQ rising edge, and remain high until the next pattern buffer is started (for about a second, which causes serious problems for the target hardware). The buffer is always padded with all zeroes at the end to ensure that the outputs stay low between pattern outputs. This even
    t occurs at random (it seems), and is very difficult to trace due to its intermittent nature. The DPULL signal is left open (pulled down internally on the DIO board according to the manual) and in our current system only up to 6 of the 32 lines are ever set to 1's in the pattern buffer, so, in theory, the unused lines should never be going high. The same Visual C++ application is used in other systems with identical CPUs, but the problem does not occur in those cases. Replacing the DIO-32HS board has no effect. NI-DAQ version 6.9.1f28 is being used. Can anyone provide any insight into why the outputs might all go high at once in this fashion? Have there been any design changes (firmware or ASIC) on the PCI-DIO-32HS board over the last several years?

    Hi Doug,
    It is very strange that the program is working fine with the other cards and not this one. If the clock signal to the REQ line is not the same then I would suggest to check the REQ line to see that it is not receiving any ghost pulse.
    Again, it is a good idea to install the latest driver of NIDAQ 6.9.3 and see it.
    Also give a shot for an example program in the c:\program files\national instruments\ni-daq\examples\visualc folder and see if you get the same problem.
    Please do let me know if you have any questions.
    Sincerely,
    Sastry V.
    Applications Engineer
    NI.

  • 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

  • Can I use DIO 32HS in pattern I/O and Unstrobed I/O in the same time?

    I work with a pci dio 32 HS(programming with labview) and i want to know if it is possible to configure 3 ports in unstrobed output mode (24 static digital lines) and 1 port in pattern I/O mode which can read AND(not "or") write data(using internal clock)in the same VI.moreover in pattern I/O mode am i obliged to use these port combinations (16 bits: (port0,Port1) or (port 2, port 3) , 32 bits: (port 0,1,2,3))and not an other one and can i configure one port in output and input at the same time (for example aquiring and generating data at the falling and rising edge of the internal clock)?? please give me all possibilities of lines, ports and groups direction (input output bidirectionnal) with more de
    tails (i'm not sure of what i can do using the 653X user manual). else, I can't observe with my oscilloscope TEK the internal clock signal(squarewaveform TTL) onthe REQ pin as it is said in the user manual, WHY????
    Thank you for your answers.bye

    Hi,
    No, you cannot configure 3 ports together. On the PCI-DIO-32HS, there are two main port groups, each group consisting of two ports: group 1 (ports 0,1) and group 2 (ports 2,3). You can configure two 8-bit ports (0 and 2), two 16-bit ports (0,1 and 2,3) and one 32-bit port (ports 0,1,2,3); you can configure each group independently.
    Regards,
    RamziH.

Maybe you are looking for