AT-MIO-16E-10 Read encoders problem (a possible driver problem ?)

Hi there! I have AT-MIO-16E-10 board and i have a problem with reading the "values" from an incremental encoder.Here it's the description of the problem : I have the encoder conected via a mechanism formed by a belt and a pulley (the pulley it is connected directly to the encoder shaft) and this mechanism it is moved by a dc motor which it's also conected to the belt by an identical pulley mounted on the dc motor shaft.The motor drives a cart (by this mechanism formed by pulley-belt) on a track which has 1200 mm length.Now here comes the problem : The resolution of the encoder i use to measure the position it's 10000 ppr. The diameter of the puley it's 30.56 mm. Now the pulses given by the encoder during the full track (the total counts measured within the total length of the track i.e 1200mm) are measured with an universal counter (a hardware device) and with an aplication program (which it is attached bellow).The number of pulses for the total lenght of the track it's around 125000 (plus minus maxium 10 pulses) for the universal counter device (the hardware device) and around 128000 for the aplication program (plus minus 100 pulses).Now if we do a simple mathematical calculation we shall observe the following : if the puley has the diameter of 30.56 mm that gives us a linear length (the length of the circle) of PI*diameter i.e around 96.00424 mm (3.1415*30.56).If the total length of the track it's 1200mm that means the puley makes 1200/96.00424 rotations i.e. around 12.499 rotations and if the encoder give us 10000 ppr that means 124990 pulses for the total length of the track (for 1200mm) which it's extremely closed to the value of 125000 pulses provided by the universal counter (the hardware device) and quite far from 128000 pulses provided by the aplications program attached bellow.If we supose that the corect number of pulses it's 128000 that means the pulley should turn 12.8 times comparing with 12.5 times on the total length of the track which it's not true! (i could see with my own eyes that the pulley rotates under 12.5 rotations during the total length of the track). So after my opinion there is something wrong with the software (the program it is downloaded from zone.ni.com).I'm using AT-MIO-16E-10 hardware device,with LV6.1 (and real-time version),NI-DAQ 6.9.3 driver on XP1600+ processor,with Windows XP operating system.If any of NI aplication engineers see this please reply as quick as possible.Thank you very much for reading this and i'll be waiting for your answers as quick as possible.Best regards,Michael.
Attachments:
Quad._Encoder_with_E-series_(STC).VI ‏50 KB

>by Michael Antonios
The number of pulses for the total lenght of the track it's around 125000 (plus minus maxium 10 pulses) for the universal counter device (the hardware device) and around 128000 for the aplication program (plus minus 100 pulses).
>mross
IF the signal from the encoder is correct (proper voltages High and Low, and noise free), THEN the count will be correct.
This is gauranteed.
You probably have a noise problem ( I speak from experience). The counter is expecting TTL logic. In my experience, if the low of the encoder signal has noise exceeding 0.8V, the counter will falsely count the noise.
The simplest solution could be to trigger on the falling edges of the encoder signal. There is more "headroom" coming dow
n with TTL. If your high signal is running 5V, the undefined range starts at 2.4V (which is pretty much when the counter will start counting). This gives you the ability to reject 2.6V of noise. On the rising edge, you may have a 0.3V low and only 0.5V of noise rejection.
The other option is to clean up the noise. Get an osilloscope and start looking. Fix any bad grounding and wiring practices. Turn off any noisy equipment. There are ways to buffer the counter input so that the encoder signal is a differential signal. Optocouplers and schmitt triggers can clean up the encoder signals. Sometimes the encoder needs to drive some current to be less noisy. A fast Line Receiver can clean up rounded off encoder pulses (see US Digital - $16).
Good luck,
mike

Similar Messages

Possible Driver Problem in ODPNET9202102

Hi,
got following problem with above ODP Driver:
In out Application we open a connection to the Oracle database, read data into a ado.net dataset, close connection. Before storing data back, again connection is open, data saved an connection again closed.
We get the following strange behaviour:
Reading the dataset and adding a new datarow to the table (dataset conatins only one table). Storing the dataset. reading it back again in the application and changing an exiting record. The next save (actually the Update of the Dataadapter on the modified Row in the dataset) comes up with the following (I translated the message from german to english) message:
Generation of dynamic SQL not successful. No Information on Keys found.
After that, ending the application results in NullReferenceException.
Same code works on other driver (for example OLEDB on Access).
What wrong?
Thanks for your help.

The reason I asked for a test case was to verify the fix in 9204000. Since you have verified the fix yourself, you don't need to send the test case.

IMac disk drive problem, iMac disk drive problem

Hi. Don't have original software disks. Anything I need to do before I bring in my iMac to the Genius Bar?   I haven't been able to backup via time machine since I've purchased this iMac a few years ago.   Any helpful insights or suggestions?

You will need an external disk drive that's freshly erased.
Clone Lion/Mountain Lion using Restore Option of Disk Utility
Boot to the Recovery HD:
Restart the computer and after the chime press and hold down the COMMAND and R keys until the menu screen appears. Alternatively, restart the computer and after the chime press and hold down the OPTION key until the boot manager screen appears. Select the Recovery HD and click on the downward pointing arrow button.
     1. Select Disk Utility from the main menu then press the Continue
         button.
     2. Select the destination volume from the left side list.
     3. Click on the Restore tab in the DU main window.
     4. Check the box labeled Erase destination.
     5. Select the destination volume from the left side list and drag it
         to the Destination entry field.
     6. Select the source volume from the left side list and drag it to
         the Source entry field.
     7. Double-check you got it right, then click on the Restore button.
Destination means the external backup drive. Source means the internal startup drive.
Shutdown and reboot hangs usually are caused by applications or other processes that have crashed and are interfering with the shutdown process. Open Console in the Utilities folder to see if there are messages indicating what specifically is causing the problem.
Open Activity Monitor in the Utilities folder. Select All Processes from the Processes dropdown menu. Click twice on the CPU% column header to display in descending order. See if any running process is listed in red or is otherwise shown as not responding.
Before you do a shutdown you could instead try quitting every open program you have run. If one or more refuse to quit then you know which is causing the problem.

X3100 problem with spectraview (driver problem?)

Hello,
I have a macbook 3.1 late 2007 4 gb ram with an x3100 intel and snow leopard 1.6.3
I wanted to know if this video card support ddc/ci and if it's possible to see on my mac if this service works. I bought a nec monitor with spectraview and this software cannot recognize the nec monitor probably due to ddc/ci issue. Are there intel driver to overcome this problem? thank you!

Well I spotted this on that website BucksCountyBob linked to:
"The following models of NEC display monitors are not compatible with SpectraView when using an Apple MacBook Air or MacBook 13" with Intel GMA X3100 graphics processor. This issue is due to a hardware incompatibility with the Intel GMA X3100 graphics processor and can not be fixed by a future software update. Note that these monitors will otherwise function normally on these models of Apple Macs."

Ati driver problem linked with HP on Dutch win7 Pro

Hello,
There are 2 notifications that show up about having display adapter problem and Ati driver problem .
Is there a solutions ?

Please upload a copy of your system information file. Click "start" , type "msinfo32" , Click "file" at the top of the page, select "export" and give the file a name and click "save" .
Navigate to where the file was saved to, and upload the generated text file to a public folder on your OneDrive account and post the link here.

How to reduce reading and recording data time/ Visual C++, PCI 6024E and PCI-MIO-16E?

Right now I am working on a data communication programme. The time of reading digital signal and recording data is more than I expected, which is about 100 microsecond. I need to reduce the time. The software I am using is Visual C++ 6.0. I use two DAQ boards, which are PCI-6024E and PCI-MIO-16E. I have set the priority of Visual C++ to be realtime by task manager. The operating systme is Windows XP.
I am wondering how to set the interrupt of reading or writing data to be the highest and stop any other kind of interrupt.
Thanks in advance!

The primary limitation you will encounter when trying to do high speed
digital I/O using your E-Series hardware is that the digital lines are
all software timed. This means that for each and every digital
read it is necessary for your software to issue a command to your
hardware, read a single point, then receive the response from the
board. This prevents you from performing digital operations at
very high speed. In general, I would say that 100 microseconds is
a very good response using software-timed digital I/O on a Windows
computer.
It is difficult to make a good recommendation without more detail about
what you are trying to do. You may need to consider switching to
a Real-Time operating system, or upgrading your DAQ hardware to a board
that will allow you to time your digital acquisitions on the board
itself. These devices, such as the m-Series DAQ or the PCI-653x
series, would allow you to use hardware triggers for your digital
acquisitions, change detection, and buffered data acquisitions to
reduce the software overhead involved in a rapid acquisition.

Upgrade win98/LV4 to win2000/LV6: Speed problems with AT-MIO-16E

I found that in Windows 2000 with Labview 6 the readout rate of our AT-MIO-16E board drops to approx. 2.5 kHz max. (before approx. 11.5 kHz in Windows 98 with Labview 4 ) using the 'AI single scan' VI (see attached scheme for the readout routine). I don't know if this is due to Win2000 or due to the new NI-DAQ drivers, but for our timing-critical application this is unacceptable.
Are there any suggestions about how to accellerate the readout of the AT-MIO-16E board?
With best thanks,
Thomas Schultz
Attachments:
AT-MIO-16E_DAQ_example.bmp ‏161 KB

Hi Thomas,
Here is another idea I can give but will be of limited use in chasing it down.
Make sure the board is using DMA.
DMA is alot faster than CPU based data transfers.
Maybe durring the softeware conversion, the board got installed without DMA enabled.
Just an idea.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Data acquisition and generation with PCI-MIO-16E-4 card help!!!!

Hello,
I'm using a PCI-MIO-16E-4 card with labview7 (in using DAQmx)and I
would like to draw a frequency response.
My problem is: my program can run correctly in low frequency but, it
can't work correctly in high frequency (after 2KHz the signal is
false).
For verifying my program: I only try to generate and acquire a sweep
sine. I constate after 2KHz the sine I read dosn't resemble to a sine
I wrote.
Can you say me where is the problem?
Thank you.
Le Trong Thao.

"Dr. Imad" wrote in message news:<[email protected]>...
> my understanding is that you are generating a sine wave (on one of the
> anlogoutput channels) and you are trying to read the signal.
> Since you can verify the signal at low frequency, but not at high
> frequency, it looks like you should increase the scan rate of the data
> acquistion (if you can, set it to 10 times the signal frequency)
> You can also use an oscilloscope to verify the signal is what you
> really generated.
Thank you for your response.
I've tried to do it, and I've tried several other possibilities but it
doesn't work correctly.
In fact, I think the problem is in my program. Do you have a program
that works correctly? I f
ound examples in the help but they don't run
correctly.
Le Trong Thao.

AT-MIO-16E-10 Gate signal,how can i configure it as in input or as an output ?

Hi there ! I have AT-MIO-16E-10 board and i want to control a counter (the GPCTR0 counter of the bord) to count up depending on the gate signal.Now i have the following missunderstanding.I've read in the AT-MIO-16E-10 manual that the gate signal can be treated eather as an input or as an output.So i want to control my counter (to count up) until a signal that comes on my gate counter's entry changes his states from 1 to 0 (to reset the counter) and then when it changes his states back to 1 form 0 i.e a transition from 0 to 1 to start counting again from zero.Now here i have 2 questions : 1. How can i config the gate signal as an input signal (in the AT-MIO-16E-10 manual it sais that the signa
l can be treated as an input or output and it's known if i configure the port as an output and if i came with an external signal to the gate i can damage the board if the signal it's set to zero ) 2. What it's the default state of the gate signal ?
Any vi files would be very usefully,Thank you very much for reading this and i'll be waiting for your answers as quick as possible.

Antonios,
The shipping example VI Count Edges does what you describe.
>Quoted from VI Description
Count Edges (DAQ-STC).vi
DESCRIPTION:
This VI counts rising edges, using an STC based device (e.g.: E-series). The counter increments its event count everytime a pulse comes into its source input. A gate signal can be added such that if a low signal occurs on the gate, then the counter will pause (scroll the front panel left to access the gate settings). The current value of the counter is read continuously in the while loop, until the Stop button is clicked or an error occurs.
I/O CONNECTIONS:
Connect the gating signal, if any, to the gate input of the selected counter.
If you selected the Source Selection to be "PFI line", connect your event count base signal to the PFI line indicated by "Source PFI line number used". (If you selected "Internal Timebase", no source connection is necessary.)
NOTE: For actual I/O pin numbers, please refer to your hardware user manual.
INSTRUCTIONS:
1. Enter the device and counter you want use.
2. Make your Source selections, as desired.
3. Optional controls are located on the left side of the front panel. You will have to use your scroll bar to reach these.
4. Connect your signals as described below in I/O CONNECTIONS.
5. Run the VI.
>End quote
If you look inside the Diagram of the Count Edges VI you will see a subVI, Group Config CTR, that has a constant set to "simple event counting." This configures the gate in the correct manner. You have 17 or so options to choose from (right-click to see the other choices). Each choice configures the counters as needed. No special effort is needed on your part.
If you really must know more details double-click on the Group Config CTR icon. On the Diagram of that VI is a Call Library function. Right-Click that and see more ugly details that you don't need to know. The functions of the counters are fully implemented by the options already available, so you don't need to know how the details, but it is intersting.
Hints:
Keep in mind that the counters require TTL level signals. 0V to 5V. Limit the current to the level the DAQ board can handle. You will false trip the counter if your low is higher than 0.8V. I have had problems with this when using noisy signals.
Also make sure you debounce any switches you wire to the counters. It is instructive to hook up an unbounced switch to the counter inputs and see just how many false trips they can generate!
Mike

How can I wire two PWM outputs of Accelerometer into PCI-MIO-16E boad with SC-2043-SG?

I have been using counter/timer pin since the accelerometer (ADXL202AE, Analog Device) provides about 550Hz PWM signal. The purpose of the project is:
- To acquire PWM signals with Full cycle(ms) and Posity duty cycle(ms) generated in Accelerometer.
- To convert the cycles into acceleration value.
By using counte/timer(GPCTR0_Source) and Trigger(Trig1) on SC-2043-SG board, the signal was obtained.
However, after converting the PWM signal to acceleration value and plotting with labview on-line, the sampling rate was pretty low (26-28samples/sec).
Then, I began to doubt that there is a wrong wire connection. Even though I am using one counter/timer pin, the sampling rate
was low. The purpose of using the acceleration was to obtain two output using two counter/timer pins.
Could anyone help me wire pins and solve the problem?
GINO.

Gino,
You should definitely be getting many more values in your buffer. You should actually be getting 500,000 values every second because a measurement is being taken for every pulse. I found a couple knowledgebases that describe error -10920 and how to remedy it. One is pasted below and the other can be found through the link.
But I'm not sure if you're going to be able to fix this problem because you're measuring pulses at a very high rate. What is happening is every time a pulse width measurement is taken it is put into an onboard (DAQ board) FIFO buffer that is 9 samples long. The computer then reads these samples out of the FIFO and into an a buffer that you can see in LabVIEW. I think the FIFO is filling up too fast and the computer is not able to read the data out fast enough. Therefore you are losing samples because they are being overwritten. This is all dependent on your system.
Here are some benchmarks for pulse measurements:
The following numbers were derived from a Gateway with 128 MB-RAM and an Athlon 700 for ONE counter of the PCI-6602. The number of counters you are using will affect these numbers.
Finite Buffer
Buff Period - 7.25 MHz
Buff Pulse Width - 7.25 MHz
Buff Semi-Period - 3.35 MHz
Continuous Buffer
Buff Period - 250 kHz
Buff Pulse Width - 250 kHz
Buff Semi-Period - 140 kHz
You should still be getting many more samples than 26 though. Try using this example with a very slow frequency pulse to make sure it operates correctly. Then start speeding up the pulse and determine when you get error -10920.
Here is an internal knowledgebase that may help you:
Title:
After Long Periods of Acquisition with AI and Counters, a -10920 Error Occurs
Problem:
A customer has a PCI-MIO-16E-4 and his application is acquiring analog input signals and performing event counting with the buffered event counting mode. The problem is that the buffered event counting is at some arbitrary amount of time (e.g., after 2 days) getting an error with the number -10920. The questions are:
1. Why is he getting this error?
2. Do you know how big the FIFO is for this buffered event counting?
3. When he shares a DMA channel with the floppy controller, how can we make sure they use separate DMA channels?
Solution :
Here are the answers to the above questions:
1. There is probably just some noise on the signal line coming in at some point. The STC is VERY sensitive, so if there is any fast glitching, it will attempt to transfer all of these. This can also happen if the signal does not ramp up fast enough, resulting in double-triggering in the middle region. Use a filter, or a Schmidt trigger*, to clean up the signals. Another suggestion is to use the PCI-6602 with filtering.
2. There is no FIFO used for the counters. The mMite has its own FIFO, but it is only about 9 samples long.
3. PCI does not "share" DMA channels. It may technically be the same DMA channel number, but this is just for reference. PCI cards use Bus Mastering. With Bus Mastering, the operating system gives up control of the PCI bus so that the hardware (in this case, our DAQ board) can handle its own data streaming, eliminating the extra step of having the OS monitor the transfers. The DMA channel numbers are just the "channels" that are supported by the mMite chip. You can have 3 PCI cards in the PC, each with DMA 1, 2, 3, and none of them will actually be sharing any resources.
And another knowledgebase about error -10920
http://digital.ni.com/public.nsf/websearch/8FB9091CB9BB452B8525642000554799?OpenDocument
Hopefully this all helps,
Erick D.
NI Applications Engineer

MIO-16E-1 Output sample rate limited?

I have a program that I have used successfully on some old Pentium 2 computers. I recently purchased a new PCI-MIO-16E-1 board, and placed it into an AthlonXP 3000+ (2.1 GHz) computer (HP a700n). It seems that I have to limit my output sample rate to be less than 5kHz, where on the old systems the rate could be up to 1MHz. I am wondering if anyone has ran into the problem before or not?
I have tried the older MIO cards in this newer computer, and came with the same problematic result (no output).
I have also tried changing the output between IRQ and DMA modes (making sure the input channel is opposite).

Can you give some additional details of the behavior you are experiencing on the AMD computer? It sounds like if you increase the update rate beyond a certain rate, then your program executes but you don't see a signal on your AO channels. Is this correct?
Yes, Jeremy, this is correct. It seems that if we go above a 400kHz output sample rate, the signal either doesn't make it to the output buffer, or simply never gets placed on the AO of the board.
Are you checking for errors in your program? If so, do you get any errors? Are you using NI-DAQmx or Traditional NI-DAQ to communicate with your hardware?
Yes, we are checking for errors, and we get none. Using Traditional NI-DAQ, all responses are (0) as expected.
It also sounds like you are performing AO and AI in the same application. Have you tried to run a simple AO example that ships with NI-DAQ?
I was searching for an example to try when I though about trying a Pentium PC to see if the same thing happened. As far as I know, anytime our software has worked on any computer, I need not go back to trying samples, as they are typically more complex than what we end up with. We simply make a voltage array, and shoot the array to the board (After setting output rate).

My AT-MIO-16E-2

My AT-MIO-16E-2 is acting up lately. I am reading input of ~-6V in all
channels even when the cable to BNC 2090 is disconnected. The V
starts out from 60 and slowly drifts up to -6 V. I ran the diagnostic
online where the device failed the. Could this be the root cause of my
errorneous voltage reading? Is there a solution to this problem?
Digital Lines -- Read/Write Verification
This test verifies the operation of the digital I/O circuitry by
performing line input and output. A Boolean value is written to each
digital line and then read back internally. Both True and False values
are tested. To pass, each value read must matc
h the value written.
Testing Port 0, Line 0: PASS
Testing Port 0, Line 1: Please Wait. . .
FAILURE: Incorrect digital value read internally from Port 0, Line 1,
Expected False, Read True.
Testing Port 0, Line 1: FAIL
Testing Port 0, Line 2: FAIL
Testing Port 0, Line 3: FAIL
Testing Port 0, Line 4: FAIL
Testing Port 0, Line 5: FAIL
Testing Port 0, Line 6: FAIL
Testing Port 0, Line 7: FAIL
FAIL: Device 1 has failed the Read/Write Verification Test
Digital Ports -- Read/Write Verification
This test verifies the operation of the digital I/O circuitry by
performing port input and output. A binary pattern is written to each
digital port and then read back internally. All possible binary
patterns are tested. To pass, each pattern read must match the pattern
written.
Testing Port 0: Please Wait. . .
FAILURE: Incorrect digital value read internally from P
ort 0, Expected
0, Read 2.
FAILURE: Incorrect digital value read internally from Port 0, Expected
1, Read 3.
FAILURE: Incorrect digital value read internally from Port 0, Expected
4, Read 6.

I am not sure why your digital lines are failing, but they should not affect your analog input lines. You need to make sure that the cable is disconnected from the AT-MIO-16E-2 when you run the test. Also, have you run the Resource Test in MAX, because it can help diagnosis resource problems.
Now for the floating lines. This is actually very common. When nothing is connected to the pins the voltage will charge up on the leads. Sense the pins are not connected to anything and the voltage has no were to go the lines will normally completely saturate the capacitors on the board.
This is not a bad thing and it should not affect your measurements, if you do not scan the channels that are not connected. If you are worried about the unused floating signals, you
can wire the unused inputs to ground.
If you are performing measurements and notice that the inputs are floating you should check your grounding methods. In general use RSE for floating sources, NRSE and DIFF for grounded signal sources. If you want to use NRSE or DIFF on a floating signal you will need to add a 10-100kOhm bias resistor from the negative lead to AIGND to reference the signal. Refer to this KB for more help.
http://digital.ni.com/public.nsf/websearch/DF70FCE03D397BFE86256A3700780FFA?OpenDocument
I hope this helps,
Joshua

Delphi+At-MIO-16E-10 multithreading, also board identification

Hi Everyone,
I've got two questions to ask....
Has anyone done multithreading using Delphi to control a
nidaq card?
Basically, I want to know if it feasible to
output a function to an analogue output channel using
WFM_op, for example, in one thread, while doing data
acquisition in another thread (using scan_op).
Does anyone know of the limitations here?
Furthermore, since we sometime use multiple cards in the same
computer, if would be useful if we could call a routine to
identify which cards are present (and assigned devicenumbers)
and what board type they are. Note that I don't want to change
the board addresses, just determine which ones are present, and set up
the code depending on
which board the user chooses.
I haven't come across a function that can does these things and I'd
appreciate
any advice.
Regards,
Roland
Dr. Roland I. Keir Phone: +61 8 8302 3252 (Lab) / +61 8 8302
3024 (Office)
School of Physics and Electronic Systems Engineering Fax: +61 8
8302 3389
University of South Australia E-mail:
[email protected]
The Levels Campus, Mawson Lakes, SA 5095
www.laser.unisa.edu.au

Hi Walter,
From your comments it looks like it will be possible.
Many thanks for your advice, you've saved me
a great deal of time.
Cheers,
Roland
"Walter van Iterson" wrote in message
news:[email protected]..
>
> Hi Roland,
>
> >I've got two questions to ask....
> >Has anyone done multithreading using Delphi to control a
> >nidaq card?
>
> Not in Delphi, in Java. No problems running change detection
> together with digital in- and output (on a 6527 card). Ni-Daq has no
> problems with multithreading. I don't know how the AT-MIO-16E board
> behaves.
>
> >Furthermore, since we sometime use multiple cards in the same
> >computer, if would be useful if we could call a routine to
> >identify which cards are present
(and assigned devicenumbers)
> >and what board type they are.
>
> You can poll each device number (1 to 16) using Get_DAQ_Device_Info
> with infoType = ND_DEVICE_TYPE_CODE. It returns an infoValue, which
> is an identifier for the device type. It's ugly, but it works. See the
NI-Daq
> help
> on Get_Daq_Device_Info and Init_DA_Brds.
>
> Hope it helps,
> Walter van Iterson
>

PWM signal from Accelerometer by using DIO of PIC-MIO-16E-4

I am a new beginner to use digital signal acqusition. The accelrometer send the pulse width modualated signal and I need to use DIO line instead of counter. I wonder how I can measure the pulse width, + duty, and -duty.

Hi Gino,
If you plan to use the digital inputs of the PCI-MIO-16E-4 then you will be limited to software timing since the digital inputs are asynchronous and dependent on software calls. This means your fastest rates are roughly 100-1000Hz (computer dependent). Since you also want to sample a period at least 5 to 10 times so that you can get a somewhat accurate representation of the duty cycle and the pulse width, you are further limited to the signal being slower than 10-200Hz.
However, if this is acceptable then you only need to create a loop and sample your digital inputs at the desired loop speed and perform calculations to determine the duty cycle.
How you would determine the pulse width and duty cycle is everytime you take a digital measureme
nt you also use "Count Ticks (ms).vi" in LabView to count the time between each call to this VI. You simply add these times while the reading is high and you have the high dutycycle. Do the same for low and then add the two together.
Hope that helps.
Ron

I am trying to generate a 50kHz sine wave for ten cycles, then aquire this waveform and store it in a file, I am using a PCI-Mio 16E-4 board, has anyone done anything like this?

I am trying to generate a 50kHz sine wave output on the DAQ card and then simultaneously recieve. I am using a PCI-Mio 16E-4 series board to do this. Has anyone done anything similar. I can generate a 50k wave no problem, and recieve one, but I can not get these vis to run together? Any suggestiosn

Jrod, yes you should be able to do this, actually there are quite a few example programs come with LabVIEW that handles simultaneous analog input and output, I check the specs of the board you use, the board should be able to handle the sampling/generation rate, but make sure for 50KHz sine wave, you would sample at least twice as fast, preferably ten times the generation rate, then this puts the sampling of the board to thew limit.
The program you can try is attached here, good luck with the application,
XD Gao
Applications Engineering,
National Instruments
Attachments:
Simul_AIAO_Buffer(E-series).vi ‏104 KB

AT-MIO-16E-10 Read encoders problem (a possible driver problem ?)

Similar Messages

Maybe you are looking for