AT-MIO-16E10 - Error 10846

Hi
I am using the above card for acquiring data simultaneously on 4 channels. I have written both labview as well as Visual basic codes for this. I see that the maximum sampling rate given for the card (100 kS/s) is shared between the channels - I get maximum of 25 kS/s. I am acquiring photodiode signals detecting laser pulses with repetition rates ranging from 10 Hz to 100 kHz. I want to acquire 500 scans (points) per each laser shot and this, along with the maximum allowed sampling rate restricts my signal frequency to 50 Hz. I am using software triggering (stop) with Channel 4. I can change the number of pulses to acquire (with 50 Hz or lower)
I have the following problems:
1) Even with 50 Hz or 25 Hz signal repitition rate, the program (Visual Basic) does not acquire all the pulses I select.
2)It often gives Error :-10846 suggesting that I should either increase the buffer size, reduce the rep.rate, reduce the acquisition rate or reduce the tasks that my PC is undertaking. I am using a P-II with 64MB RAM. I know it is old :-) I tried with changing buffer size but it did not work. I cannot reduce the repetition rate or acquision rate for my application.
3) the labview program does not give an error but it also does not acquire all the pulses I select.
4) The problem gets worse when I try to write the data to a file.
I am using the acquisition program (both VB and labview) to simulate an oscilloscope. Is this causing the trouble? I am attaching my codes here. The file-writing part in VB program is commented out.
Thanks for your help
Rajeev
Attachments:
acquision.zip ‏18 KB

Thanks Anuj,
I had solved the problem. I tried clearing the buffer periodically and that solved the problem. Thanks any ways.
The labview code is the code for scope (the one that comes with DAQ examples) with an additional routine to calculate the maximum in each waveform.
-Rajeev

Similar Messages

Quantization Error for NI AT-MIO-16E-2

Hi
I wanted to confirm the value of quantization error for the 12-bit NI AT-MIO-16E-2 DAQ. I can take values between -10 to 10 Volts. So the quanitization error would be:
= +/- 0.5*(20/(2^12)) = +/-2.44e-3
Is this correct? This seems like a high amount of error when voltages are below 0.1V
Also, I want to know if the above DAQ card comes with an anti-aliasing filter, depending on the sampling frequency.
Thank you
Karthik

Hi Karthik,
If you choose your measurement range to be +/-10V, the smallest change that can be detected is 20/2^12 = 4.8mV. So the maximum quantization error would be +/-4.8mV. If you're looking to increase the accuracy, you can change the measurement range to be the smallest possible for your requirements.
There's no anti-aliasing filter built in to the DAQ card, but you can easily implement them on a terminal block (analog) such as the SCB-68 or in software (e.g. Low Pass Filter in LabVIEW).
Analog Input Low Pass Filtering with an SCB-68 Terminal Block:
http://digital.ni.com/public.nsf/websearch/5D82A2990FB1D21386256EEE00018FF0?OpenDocument
Hope this helps!
Thanks,
Lesley Y.
Applications Engineering

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

Pulse Train Generation using PCI-MIO-16E-4

I need to generate pulse trains of changing pulse widths using PCI-MIO-16E-4 daq card using Igor Pro.
I have tried to use the CTR functions (but always keep getting errors and it doesn't work). I also used the general purpose counters (GPCTR functions) but cannot visualise them on a CRO. If someone can help in regards to the programming aspect, it will be greatly appreciated.
Thanks
Vakul

Hi Vakul,
Some questions that might help me to get you a solution.
Are you using Traditional DAQ, or DAQmx and which versions are you using?
What operating system are you running?
When you say you can't visualize them on CRO, I assume that you are hooking the counter out to a cathode ray oscilloscope and can't see the pulse train?
Are you going to need more than two different pulse widths for your pulse train?
There are several online knowledge bases describing how to change the frequency of a pulse train on the fly.
This link explains how to use software to create a new pulse width.
http://digital.ni.com/public.nsf/websearch/7B1B0427C39FE33086256CEE00752133?OpenDocument
This link discusses using frequency shift keying, which will only allow you to have 2 different pulse widths.
http://digital.ni.com/public.nsf/websearch/EC1F089252F33B248625696E006FB6FC?OpenDocument
I assume that you are writing this program to compile in Igor Pro using C. I can help you with the C code development, but don't know anything about the Igor Pro API.
Please get back to me about those questions and let me know if you need further help.
Michael Denton

Does the academic version of Labview 8.5 allow running AT MIO 16e-1 DAQ board?

I just bought the academic version of Labview 8.5. I have an AT MIO 16E-1 DAQ board. I have installed the Labview software. Then I installed the Legacy NiDAQ 7.4. I put in the board and MAX recognizes it. Windows detects the board twice. The first time is installs automatically. The second time there is an error.
I can't find the instrument driver/VIs in the Labview functions pallette for the AT MIO board.
Thanks.

Hello Test11111,
In order to use Traditional NI-DAQ devices in LabVIEW you need to know the device number as given in the Measurement and Automation Explorer. Unlike the IMAQ or NI-DAQmx devices, Traditional NI-DAQ devices do not auto-populate in the channel controls or constants. The good news is that if the device shows up in MAX and the test panel works there then your device is working properly.
There are some Traditional NI-DAQ example VIs available through the NI Example Finder. To access these examples open LabVIEW and go to Help» Find Examples... Then in the top left select Directory Structure; the "daq" folder contains all of the Traditional NI-DAQ examples organized by device and function (analog, digital or counter I/O).
I hope this helps, and please post back if you're still having trouble.
Cheers,
Brooks

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

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.

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

Question about setup_MITE in the PCI-MIO-16E-1

I have a quick question about setup_MITE in the PCI-MIO-16E-1. In one of the manuals, it states that if you're using Dell Optiplex GX series for our hardware configuration, is it true we need to re-write the MITE functions to correlate with the hardware? Please if you can clarify what this means, I would really appreciate it. Thank you in advance.

National Instruments is starting a new newsgroup to provide a forum for customers to discuss register level programming issues and ask questions. This newsgroup is not a direct support channel for register level programming, but may be monitored by National Instruments engineers. Please post you question with additional detail in:
natinst.public.daq.driver-development.general
Christian
Christian Loew, CLA
Principal Systems Engineer, National Instruments
Please tip your answer providers with kudos.
Any attached Code is provided As Is. It has not been tested or validated as a product, for use in a deployed application or system,
or for use in hazardous environments. You assume all risks for use of the Code and use of the Code is subject
to the Sample Code License Terms which can be found at: http://ni.com/samplecodelicense

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

Error 10846 occurs only if DMA mode for transfer ist selected

Hello,
my problem is if I use the DMA mode to for transferring data to the PCs memory always the error 10846 occurs.
I perform the buffered semiperiod measurement with a continuous buffer (circular buffer).
I tried to use Interrupts. The error does not occured.
Is this a known problem?
I read another thread in this forum. But there are no useful answers up to now.
I'm thankful for any hints.
Regards Peter

Hi Peter,
The NI-DAQ Help Manual gives this description for the error:
"Your application was unable to retrieve data from the background acquisition buffer fast enough so the unretrieved data was overwritten with new data. To prevent this error, you might increase the size of the background acquisition buffer, increase the amount of data you read from it per call to the read function/VI, slow down your acquisition rate, or reduce the number of tasks your computer is performing."
This is all valid info because I believe that your acquisition rate is on the verge of being too fast for your buffer size and the number of data points you are reading into your application each time. Therefore, DMA, which is a faster transfer mechanism to get data from your c
ard to the PC memory is probably loading the PC memory with many samples until it catches up with the data acquisition card where as Interrupts will gradually transfer the data to the PC memory. This means DMA is bursting data to a PC memory buffer that is slightly too small while Interrupts are transferring at the same rate you are reading (unless you change your acquisition rate depending on the transfer protocol).
I think the only change you need is to increase the size of your buffer (PC memory). If that doesn't work, also increase the number of points you read from the buffer each time by your application program. There will be a balance between these two numbers that will allow smooth operation with DMA. Hope that helps.
Ron

AT-MIO-16E-10 : Data Acquision

Hi
I am using the above card for acquiring data simultaneously on 4 channels. I have written both labview as well as Visual basic codes for this. I see that the maximum sampling rate given for the card (100 kS/s) is shared between the channels - I get maximum of 25 kS/s. I am acquiring photodiode signals detecting laser pulses with repetition rates ranging from 10 Hz to 100 kHz. I want to acquire 500 scans (points) per each laser shot and this, along with the maximum allowed sampling rate restricts my signal frequency to 50 Hz. I am using software triggering (stop) with Channel 4. I can change the number of pulses to acquire (with 50 Hz or lower)
I have the following problems:
1) Even with 50 Hz or 25 Hz signal repitition rate, the program (Visual Basic) does not acquire all the pulses I select.
2)It often gives Error :-10846 suggesting that I should either increase the buffer size, reduce the rep.rate, reduce the acquisition rate or reduce the tasks that my PC is undertaking. I am using a P-II with 64MB RAM. I know it is old :-) I tried with changing buffer size but it did not work. I cannot reduce the repetition rate or acquision rate for my application.
3) the labview program does not give an error but it also does not acquire all the pulses I select.
4) The problem gets worse when I try to write the data to a file.
I am using the acquisition program (both VB and labview) to simulate an oscilloscope. Is this causing the trouble? I am attaching my codes here. The file-writing part in VB program is commented out.
Thanks for your help
Rajeev
Attachments:
acquision.zip ‏18 KB

One possible way of getting around the File I/O problem in LabVIEW could be by having two loops running in parallel: one will do the data acquisition and write to a Queue structure, and the other loop will get information from the queue and write to the file. That way the dataflow in the acquisition loop will not be dependent on the file I/O functions. This is the recommended method in LabVIEW RT for doing data acquisition with file I/O, to enhance determinism, so I feel it can be a good programming tip in this case.
I hope that helps!
GValdes

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

AT-MIO-16E​10 - Error 10846

Similar Messages

Maybe you are looking for

AT-MIO-16E10 - Error 10846