DIO 6533 Question

I have a pci DIO-32HS card, which I have wired (using a SCB-68) such that there is a binary number coming in as the input lines for port A, and I also have a strobe signal as an input. I have two questions:
1. What pin should the strobe signal be wired to, so that every time strobe goes high I have the card read the input on port A and convert it to a number. I only want the data read on the rising edge of the strobe signal, and not again until the next rising edge.
2. How would I implement this using labview? What vi's and settings should I use?
Thanks in advance for all the help.

I have been trying to get this to work and still cannot. Is it possible for you to help me with the specific settings that I need to have in the vi? I obviously need to use an external clock, and the clock is asynchronus. I also set it up for the correct device and port numbers, and I know the card works because I have tested/configured it in MAX. However whenever I run the vi, and then apply power to the strobe line (connected to REQ1 because I am trying to read port 0/A) nothing happens the vi still sits there. Any help?
Thanks again.

Similar Messages

Accessing counter value on STARTTRIG/ACQ line for Dio-6533

Hello,
Using LabVIEW 6.1 for MacOS (on a laptop), NI-DAQ 6.9.
I was wondering if there's any way to access the counter value assosicated with each control group for the dio-6533. Basically, I want to use triggered i/o; however, I don't want it to generate/acquire on each trigger, but wait for a set number of triggers. DIO boards don't seem to have a feature like certain E-series boards where you can specify that the board wait for a certain number of trigger pulses; I thought to circumvent this by accessing the counter and arming the trigger just before the pulse that I want it triggered off of.
Thanks for any insight you can offer.
Regards,
jdk

Hello;
The only way to accomplish that is to use another board together with the 6533. You can even get a low cost E-series board, and use the available general purpose counters to create the necessary delay, and then enable the external pulse train to start clocking data in/out on the 6533.
Hope this helps.
Filipe A.
Applications Engineer
National Instruments

DAQ 6533 question

HI, all:
I have a question on DAQ Card 6533.
My peripheral device need a 'ACK' signal to start the transferring of data
into the 6533, but from the NI Website, I know that the 6533 can't generate
the 'ACK' signal at the beginning, so we have to use another DIO Line to
provide this pulse. My question is that how we can connect two outputs of
the 6533 together, both connect to the 'ACK' pin of the peripheral device,
will it cause some problem?
Thanks,
Guohua

Guohua
The 6533 has the "Wired-Or" ability. You can find more info about this in the 6533 user manual in chapter two.
Here is a brief description about wired-or and how to program it.
http://digital.ni.com/public.nsf/3efedde4322fef19862567740067f3cc/8072d2b1f4687276862564d1006ad789?OpenDocument
Brian

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

How can I write a bit to DIO-96 card?

I´ve got a diagram-program which works with the card dio-6533. With this I can write and read a bit to the card. Now I´ve to change the card to DIO-96 and the programm doesn´t work. First it writes a signal to the one cable connector (with 50 pins)than to the ohter cable connector (with 50 pins). What can I do to make the programm correct?

Hi,
I don't know what it is (maybe I'm stupid ??) but I find NI's digital
functions a monumental pain in the t*ts to work with for several reasons;
1) for simple devices such as the pci-6503 you can configure individual
channels to READ individual bits with no problem (assuming you set the
'read' VI's port width to 1)- try and configure individual channels to WRITE
individual bits and you have a problem (basically all of the other bits on
that port get set to 'zero' when you write the bit - even when you write a
value other than zero to the iteration terminal, and even with the port
width set to 1!!) in other words 'read' seems to work fine on a bit-by-bit
basis but 'write' only seems to work on a port basis
2) several of NI's card do not give you the optio
n to set the startup
condition of the digital lines - they deafult to 'high' meaning you have to
switch a 0V input to them and then invert the value to get a high reading
(when a switch makes normally you expect a 'high' signal ??)
3) you can only have bits and ports configured as read or write - even such
'low end' board such as Arcom's PCIB-40 allows you to set a bit value and
then read it back!!!
Errrmm ... starting to run out or complaints here (well it is nearly 1:00 AM
on Saturday morning :-)
If anyone can point out something that I'm doing very wrong here then I'd
love to hear, otherwise I think NI should give some consideration to the
basic functionality of their low-end digital stuff.
All the best
Andy

Problemes de formats des data!

Bonjour,
je m'appelle Andreas et je traveil avec la carte d'acquisition DIO 6533.
Mon application est la suivante:
J'ai un data x qui est connecte sur le SCB68 line 0/port 0!
En plus j'utilise l'exemple " Buffered Pattern Input.vi"! L'application marche tres bien, mais j'ai un problem
pour enregister mes data dans un file .bin!
C'est a dire: Je prends mes data qui viennent du "port data" du "DIO READ.vi" (c'est un tableau 1D)
est voila je dois les enregistrer byte par byte.
Pour instant je recoupere que des bits (a chaque trigger sur la carte je recois un bit au port data).
Mais je dois enregistres des bytes!
1.problem: comment peut -t- on creer un stream de bytes a partir des bits?
2. reellement il faut enr
egistrer des bytes dans un format HEX: C'est a dire--> exemple:
0011I1100 0000I1111 0101I1100 ......(byte stream sans des tabs, et des EOLs)
C I 3 0 I F A I 3 ......(hex byte stream sans tabs et des EOLs)ce data stream est le but pour
l'enregistrement dans un fichier bin.
Aurriez - vous des exemples pour la programation ou aurriez -vous des vi's necessaire pour resoudre mon problem!
Je vous merci beaucoup pour votre reponse!
Andreas
Attachments:
bufpatternloesung2.vi ‏130 KB

National Instruments Corporate n'a malheureusement pas les ressources nécessaires pour répondre aux questions posées en français. Cependant, ces questions seront redirigées vers le bureau français, National Instruments France.
S'il vous plait contacter National Instruments France á
Support Technique

My callback function under MFC is never called back!

I am developming a MFC application using NIDAQ 6.7 driver and PCI-DIO-6533
for a new
data adquisition system at the Jicamarca Radio Observatory. It is my first
project with the
PCI card. I am having problems with the CALLBACK functions. Following are
relevant portions
of the source code that illustrates my problem:
void CallbackNidaq()
int j;
j=1234;
TRACE("I have entered the callback function \n");
void CCAMUView:nCallbackNidaq()
HWND my_hwnd = m_hWnd ;
u32 direcion=0 ;
puntero = (unsigned char *)piBuffer;
puntero[4*NSAMPLES-1]=0;
puntero[4*NSAMPLES-2]=0;
puntero[4*NSAMPLES-3]=0;
puntero[4*NSAMPLES-4]=0;
iStatus = Config_DAQ_Event_Message(iDevice,(i16)1,//add message
"DIGRP0" , // string description
(i16)0 , // DAQEvent 0-> Adquire N scans
(i32)NSAMPLES , /*DAQTrigVal0*/
(i32)0 , //DAQTrigVal1
(u32)0 , //trigSkipCount
(u32)0 , //preTrigScans
(u32)0 , //postTrigScans
0 , // hwnd
0 , // to post WM_NIDAQ_MSG
(u32)CallbackNidaq) ; // function address
TRACE("I have already configured : status = %d\n",iStatus);
int iStatus2;
iStatus2 = DIG_Block_In(iDevice, iGroup, piBuffer, ulCount);
TRACE("I have started asinc Status2 = %d",iStatus2);
Sleep(1000);
TRACE("Buffer= %d %d %d %d \n",puntero[4*NSAMPLES-1],puntero[4*NSAMPLES-2],puntero[4*NSAMPLES-3],puntero[4*NSAMPLES-4]);
What I expect to happen is as follows:
After I configure the device I should get the first TRACE messages I do. I get
"I have already configured : status = 0" ,
"I have started asinc Status2 = 0"
To make sure the device has actually read a buffer full of data, I print out the contents of the last
four bytes which have been previously set to cero. They do show new values.
My problem is that the callback
function is never triggered.I never get the ""I have entered the callback
function"
message.
For your information, in case it helps. I have used the compiler debug to
find out the address of CallbackNidaq()
but it does not aggree with the address I get for the (u32)CallbackNidaq
address assign to the last argument of
the Config_DAQ_Event_Message function.
I would appreciate very much if you tell me What I am doing wrong.
Wishes.
Gabriel

Hello Gabriel,
the propotype of your callback function is wrong; must be (without CALLBACK keyword):
void CallbackNidaq(HWND handle, UINT message, WPARAM wParam, LPARAM lParam)
See the Config_DAQ_Event_Message in NI-DAQ Help at the bottom.
Hope this will help you.
Grettings,
Alain

Speeding up the drawing of spectrum

Dear expert,
I am using DIO 6533 board (PCI-32-HS) connected with my Optical Spectrum Analyzer to do data acquisition. Now I can get data out from the Spectrum Analyzer�s memory and drew the spectrum chart using the Labview application software. But the main problem I met is that the speed is very slow, the more data points took out, the slow the spectrum drew. It seems that the period of data abstraction time is slow. Because I have several control lines in port D, such as /Reset, /CE, /WE, etc. Which will send DIO strobe
signals in specific amount of nina second to my Optical Spectrum Analyzer. For example, I need to send an at most 40ns. digital "0" signal on the /CE line from my PC to the Optical Spectrum
Analyzer, how I can do that to satisfy the time requirement of my control lines. I know using the Labview application software can�t provide the nina seconds. Is there easier way to support this restriction? Please give me any suggestions and details on this case. Thanks a lot!

The 6533 has can be clocked to output data at 20MS/s (or 20MHz) using Pattern Generation to output data. 20 MHz will only give you control of 50ns, so 40ns timing cannot be accomplished with the 6533.
The other option would be to use a 5411 which is a function generator, but it has the ability to ouput digital data at a rate of 40MHz which would be 25ns.
You have the option to output digital data at a rate of 40MHz/n; n=integer 1....2^24-1.
The 5411 has 16-bits of digital output.
You can also use RTSI to trigger both cards at the same time if your application requires, but the 6533 will still run at a max rate of 20MHz and the 5411 at a max of 40MHz.

Verification of the data-acquisition process

Hello,
my name is Andreas and I'm a beginner in LabVIEW programming.
My task could be described as follows:
I have on data signal to acquire with the PC-DIO-32 Acquisition Card.
I have also the connection block SCB-68 to connect my application.
What is my application:
"clock one": is a 166kHz clock trigger clock ti= 200ns tp=5.8us
"clock two": is a data stream signal binary signal (patterns of 0 and 1) data stream of a Random Generator
Each time when a positive edge of the clock "one clock" arrives the DIO 6533 has to be store the signal of
the "clock two" data in a binary file.
I chose the " Burst" - mode example in external trigger clock conditions for my application:
and I use the SCB-68 connections:
PCLK1 (connector 5 of the SCB-68) is the connection for my external trigger clock "clock one"
ACK1(STARTTRIG1) (connector 3 of the SCB-68) is connected to 5+ Volt (connector 1 of the SCB-68)
REG1(connector 2 of the SCB-68) is connected to 5+ Volt (connector 1 of the SCB-68)
The port data output of the VI DIO-Read is connected to the data input of the VI Write File!
The program seems to work fine but I can't verify if the acquisition card takes the data of "clock two" really
at that time when the rising slope of "clock one" arrives!
To solve that problem I did the inverse option of the "burst" mode-> Pattern generation using an external clock at PCLK!
So I took my clock "clock one" fed to PCLK1 and I started the program!
Bad, it didn't work! Problem with a buffer configuration ERROR -10022!
So I will send you my program to give you an idea of my design problem!
If the "burst" - mode is not the best way to solve my application problem I would like to know in which mode
I should adjust the card to solve my problem!
Furthermore it would be great to get a programming example in which I can observe if the data is taken by the card
each time a positive slope occurs!!
Thank you very much for your help,
Andreas
P.S:
It is not easy at all to find your answer in your whole database! So if possible send me your answer to
[email protected]
(Sorry for my English!)
Attachments:
burstaziwithfile.vi ‏108 KB

Thank you very much toddd,
is seems to you that I'am a real looser.
But if I use the Pattern Input vi with the DIO 6533 I still not able to verify if the stored or screened data (see the graph vi in my example)is really that one which should be acquired by the card!
Let me explain:
You have NRZ-signal generator which output you can switch on or off.
You may connect your data-stream which you want to store into the DIO card to DIOA0 (connector 10 at SCB-68).
Your NRZ-signal from the generator is fed to REQ1 (connector 2 at SCB-68).
Now you will start your labview program. I set a timing delay at Read vi of 25sec.
I also monitored the data-stream of DIOA0 and the trigger signal at REQ1 using an oscilloscope.
(the trigger of the osci is set
to single mode , leading edge for the osci-channel which is connected to the trigger signal at REQ1)
Now I switch on the output of the NRZ-signal generator to on.
Now you can see at the screen of your scope some trgger pulses an the data-stream.
At each time when the trigger signal positive slope rises the data(0 or 1) at DIOA0 must be stored!
Problem: the detected data on the scope screen are not the same wich I stored in the DIO card!!
Todd, could you tell me what I did wrong?
And again, many thanks for your message!!!!!

NI PCI 6533 DIO to NI PCIe 6536 compatiablity

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.

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.

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

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

MS-6533/G memory question

I have a MS-6533/G motherboard with a Sis650 chipset. It has one 256MB DDR266 (PC2100) DIMM. I want to add another DIMM. Do you know if I can use faster memory DDR333 (PC2700) or DDR400 (PC3200) memory on a motherboard which calls for DDR266?
Thanks!

Idon't recommend mixed of RAMs for MSI mobos, if you want to run DDR333 RAMs, make sure that all are of the same type and not different ones as these are mainly the cause of stability problems or RAMs having memory dump errors.

DIO 6533 Question

Similar Messages

Maybe you are looking for