Encoder and E-series DAQ Board

Hello!
I am connecting a Quadrature Encoder to a PCI-MIO-16E-4 DAQ board. The board is now called a PCI-6040E. I am wondering how exactly to connect the Encoder to the DAQ board. Direction is not necessarily that important, but it would be cool if the DAQ board could tell when the direction changed. On the board are an out, gate and clock. I don't know what to put where??? Please help me???
Thank you,
Tiffany Bierly

CTR0 :
A --> CTR0 SRC (pin 37)
B --> P0.6 (pin 16)
CTR1 :
A --> CTR1 SRC (pin 42)
B --> P0.7 (pin 48)
See chapter 4 of this document for more details about using quadrature encoders with series E DAQ boards.

Similar Messages

Quadrature encoder with PCI-6259 DAQ board (driver for QNX)

where can I find any example for connecting Quadrature Encoders with M Series DAQ Boards ?
The only more or less suitable example I found in nimseries DDK, is
"Count pulses from an external source using an external signal to control
the count direction" (nimseries\Examples\gpctex2.cpp).
But this example is not working correctly with Quadrature Encoders
(encoders with two shifted on 90 degrees phases A&B).
i.e. in case of using this example code I get some extra count while encoder is on vibrant motor
what means enums
typedef enum {
       kG0_Up_DownHardware          = 2,
       kG0_Up_DownHardware_Gate     = 3,
} tG0_Up_Down;
and
typedef enum {
       kG0_Encoder_Counting_ModeId          = 1,
} tId;
in (nimseries\ChipObjects\tTIO.h) ?
What initalization procedure I need to work with Quadrature Encoders?
I have PCI-6259 DAQ device
and I'm writing programm under QNX6 operating system

Hello alexey_3269,
If you want to read a quadrature encoder start with gpctex1.cpp and follow the thread.
I give you my code:
BEGIN CODE
==========
boardGpct->G0_Mode.writeG0_Load_Source_Select(tTIO::tG0_Mode::kG0_Load_Source_SelectLoad_A);
boardGpct->G0_Load_A.writeRegister(InitialCount);
boardGpct->G0_Command.writeG0_Load(1);
boardGpct->G0_Load_B.writeRegister(0);
boardGpct->G0_Load_A.writeRegister(0);
boardGpct->G0_Input_Select.setG0_Source_Select(9); //see above for choices, PFI8=9, 100 kHZ=18
boardGpct->G0_Input_Select.setG0_Source_Polarity(1); //0=CCW, 1=CW
//If using 80 MHz timebase
boardGpct->G0_MSeries_Counting_Mode.writeG0_MSeries_Alternate_Synchronization(1);
boardGpct->G0_MSeries_Counting_Mode.setG0_MSeries_Encoder_Counting_Mode(3); //3 for X4 encoder counting
boardGpct->G0_MSeries_Counting_Mode.flush();
//Enable Input Pins
boardGpct->G0_MSeries_ABZ.setG0_A_Select(9); //PFI8=9,
boardGpct->G0_MSeries_ABZ.setG0_B_Select(21); //PFI10=21
boardGpct->G0_MSeries_ABZ.setG0_Z_Select(10); //PFI9=10
boardGpct->G0_MSeries_ABZ.flush();
boardGpct->G0_Mode.setG0_Gate_Polarity(1); //invert=1
boardGpct->G0_Mode.setG0_Output_Mode(tTIO::tG0_Mode::kG0_Output_ModePulse);
boardGpct->G0_Mode.setG0_Loading_On_Gate(tTIO::tG0_Mode::kG0_Loading_On_GateNo_Reload);
boardGpct->G0_Mode.setG0_Loading_On_TC(tTIO::tG0_Mode::kG0_Loading_On_TCRollover_On_TC);
boardGpct->G0_Mode.setG0_Gating_Mode(tTIO::tG0_Mode::kG0_Gating_ModeLevel_Gating); //kG0_Gating_ModeGating_Disabled
boardGpct->G0_Mode.setG0_Gate_On_Both_Edges(tTIO::tG0_Mode::kG0_Gate_On_Both_EdgesBoth_Edges_Disabled);
boardGpct->G0_Mode.setG0_Trigger_Mode_For_Edge_Gate(tTIO::tG0_Mode::kG0_Trigger_Mode_For_Edge_GateGate_Starts_TC_Stops);
boardGpct->G0_Mode.setG0_Stop_Mode(tTIO::tG0_Mode::kG0_Stop_ModeStop_On_Gate);
boardGpct->G0_Mode.setG0_Counting_Once(tTIO::tG0_Mode::kG0_Counting_OnceNo_HW_Disarm);
boardGpct->G0_Mode.setG0_Reload_Source_Switching(tTIO::tG0_Mode::kG0_Reload_Source_SwitchingAlternate);
boardGpct->G0_Mode.flush();
boardGpct->G0_Command.setG0_Up_Down(tTIO::tG0_Command::kG0_Up_DownHardware); //kG0_Up_DownSoftware_Down
boardGpct->G0_Command.setG0_Bank_Switch_Enable(tTIO::tG0_Command::kG0_Bank_Switch_EnableBank_X);
boardGpct->G0_Command.setG0_Bank_Switch_Mode(tTIO::tG0_Command::kG0_Bank_Switch_ModeGate);
boardGpct->G0_Command.flush();
boardGpct->Interrupt_G0_Enable.setG0_TC_Interrupt_Enable(0);
boardGpct->Interrupt_G0_Enable.setG0_Gate_Interrupt_Enable(0);
boardGpct->Interrupt_G0_Enable.flush();
END CODE
========
I hope this code is appropriate to you.
FV1234

Which type of ADC is used in M Series, S Series and C Series DAQ Cards?

Hi
I want to know which type of Analog to digital converters(ADC) are used in M Series and S Series DAQ Cards. I know that DSA Cards and some C series are using Delta Sigma ADC. What about the ADC used in non delta sigma C Series modules. Why Delta sigma ADC is not used in M series and S series DAQ cards.
Regards
Samuel J

Hi Samuel.
The ADC type used is Succesive Approximation ADC. You can refer to the following links for your reference.
http://digital.ni.com/public.nsf/websearch/32FD9AA817D0EBE68625708C005E1B26?OpenDocument
Hope this helps.
Thank You.

Do I need extra logic circuit for quadrature encoder using M-series DAQ PCI-6221?

Hi,
I understand that extra logic circuit, say quadrature clock converter LS7083/7084, is needed to enchance the reliability or integrity of the data for E-series board DAQ in accordance to application note: AN084.
This is due to the vibration/jitter of the motor during running.
Currently, I'm using M-series PCI-6221.
Is it this new model itself can eliminate to construct this extra circuit?
Coz I observed error is accumulating after motor rotating certain period of time. It defintely affect the control performance.
Other than using hardware, can we use software to eliminate/mitigate the error?
Please enlighten me. Thanks.
Best regards,
IANES

Hello,
The ap note you are referring to discusses circuitry that conditions the quadrature encoder signals before they get to the DAQ device to eliminate 'false' signals being sent to the DAQ device. The same system would apply to an M Series Device. I am not aware of any way to achieve this functionality in software. FYI, there is some good documentation for counters and counter applications for M Series. Take a look at the attached M Series help file. Hope this helps some.
-Alan A.
Attachments:
M_Series_Help.zip ‏1145 KB

Encoder and S series

Do S series counters support quadrature encoders? If so, how to do connection between board and encoders?
My encoder is US digital HB6M with A,B channels, index, ground and +5VDC power.
Solved!
Go to Solution.

I am using S series NI 6123
I tried the sample code for measure an encoder. code fragment:
DAQmxErrChk (DAQmxCreateTask("",&taskHandle)); DAQmxErrChk (DAQmxCreateCIAngEncoderChan(taskHandle,"Dev1/ctr0","",DAQmx_Val_X4,0,0.0,DAQmx_Val_AHighBHigh,DAQmx_Val_Degrees,24,0.0,""));
DAQmxErrChk (DAQmxCfgSampClkTiming(taskHandle,"/Dev1/PFI9",1000.0,DAQmx_Val_Rising,DAQmx_Val_ContSamps,1000));
But the error message is: Measurements: Selected physical channel does not support the measurement type.
Does this mean that NI 6123 doesn't support encoder meansurement?
Thank you in advance.

Need to use quadrature encoder to trigger (RTSI) single point DAQ on 2 channels of E-Series DAQ, using 6602 NI-TIO for counting encoder pulses.

This is for LV6i, W2000, all PCI equipment.
Using a quadrature-measure position-VI, I get 7200 edges/rev from the encoder of my physical system. This equates to 0.05 degrees of angular displacement. This amounts to an angle stamp as opposed to a time stamp.
I need each of these 7200 edges (source: 6602 NI-TIO) to trigger (using RTSI) the acquisition of a single sample from each of 2 channels on an E-Series DAQ board (maybe more channels later). I only need/want one rev (7200 samples per channel) of data for each run of the test. As I write this I think I want pre-triggering and a little more than a rev of data. So the
re is a buffering step. Anyway, you can get the idea.
I need this angle stamp and the DAQ samples to be placed in an array and on the hard drive for graphing and other mathematical treatment, analysis, etc.
I think there must be a way to use the quadrature output of the counter/timer as a scan clock for the DAQ board, but I haven't seen an example to guide me.
It seems like all of the RTSI or other triggering examples I have seen trigger once to start a continuous scan, not a series of discrete samples repeated quickly. I am not sure how to fill an array with this data. Again, examples are for continuous sampling, not a series of discrete readings.
Any hints on any part of this task will greatly appreciated. This is my first LV project.

Sounds like a fairly ambitious first project!
I assume your 7200 edges/rev come from an encoder with 2 channels in quadrature which each provide 1800 cycles/rev. You can clock in analog data at 1800 scans/rev with either of the two encoder channels, but will probably need an external quadrature decoder circuit to produce 7200 scans/rev. Either method can be done with screwdriver and wire or else by using another counter from the 6602 and the RTSI bus. Here are two approaches in detail, but you could mix-and-match as needed.
Note also that if you can be sure that your reference encoder will be uni-directional, you wouldn't need to measure position -- position could be determined by the array index of the analog scan data. This would simplify things greatly.
1800 scans/rev, screwdriver & wire
Wire both encoder channels to your 6602 breakout box and configure your counter for the 4x quadrature option. Send a wire from one of the encoder channel connections at your 6602 breakout box to a PFI pin at your E-series board breakout box. Config the analog acquisition to use an external scan clock and specify the correct PFI pin -- there are built-in examples that will guide you. Now one edge of one encoder channel acts as a scan clock for your analog acquisition. Inside the 6602 breakout box, route the same signal to one of the default gate pins and configure your encoder counter gate to use that pin as its gate signal. Note that there will be a race condition governing whether the encoder value updates from the encoder inputs before or after the value is latched by the gate.
7200 scans/rev, extra counter & RTSI
Make sure you have a RTSI connector between your two acquisition boards inside your PC. Build a quadrature decoder circuit that will convert your two encoder channels into a clock and direction output. (Consider the LSI 7084 decoder chip or similar). Setup your "encoder" counter for buffered position measurement. Use "Counter Set Attribute" to define "up down" as "digital" (don't use it to define "encoder type"). The clock output goes to the counter SOURCE and the direction output goes to the counter UP_DOWN pin.
Use "Adjacent Counters.vi" to identify the counter considered adjacent to your encoder counter. Configure it for "retriggerable pulse generation". Use "Counter Gate (NI-TIO).vi" to specify "other counter source" as the gating signal. Configure the output pulse specs to be short duration (make sure total of delay + pulse width is less than the minimum period of the incoming encoder clock signals). Use "Route Signal.vi" to send this counter's output onto the RTSI bus, say RTSI 0.
Now configure the analog acq. to use RTSI 0 as its external scan clock. Also configure the encoder counter to use RTSI 0 as its gate signal. Voila! Now your quadrature decoder clock output acts as a scan clock for analog acquisition and a "gate" to buffer your encoder measurement. The short delay helps ensure that the clock updates the position measurement before the gate fires to latch the value.
Respond if you need clearer explanation. There's a fair amount of decent info "out there" if you scour the online help and this website. Good luck!

Not receiving any signal input with LabVIEW SE, USB DAQ board

Hello all, good afternoon.
I am having a little trouble with my DAQ device, I hope that someone will be able to help me.
I'm plugging a BNC pH sensor to a NI USB 6251 M-series board, to try and obtain the electrical response of that particular sensor, measuring the voltage output for each buffer solution (pH 4 and 7). Have 9.2.3 mx (lastest) drivers.
The pH sensor (floating) is plugged through a female BNC plug to the circuit board, signal is going through a signal conditioning circuit (composed by a voltage follower on each of the wires to lower the output impedance of the sensor, and 2 bias resistors from AI+ and AI- connected to AI GND with the board case wired to the power supply ground, as seen in http://zone.ni.com/devzone/cda/tut/p/id/4494)
I'm measuring in differential mode, as I said both wires of the sensor are going through a voltage follower each, and into the DAQ board. The Op-amps are being powered by +-15v as seen, again, in http://zone.ni.com/devzone/cda/tut/p/id/4494
I did take the time to read the manuals and tutorials I found, did quite a bit of investigation over the last few days, and wired the system carefully.
In labview signal express, I choose to take an analog voltage read, and select input range from -500mv to 500mv, because the sensor should output at most -400mv to 400 mv
Now, much to my dismay labview registers in that channel absolutely nothing, only a little noise (~1 mV). I unplug the sensor and realise that whether the sensor is connected or not, it doesn't make a difference in the presented output - it's as if it the sensor wasn't there at all. And yes, I am measuring the correct channel. I tried connecting the wires to different AI channel pairs as well, could be a faulty one, but no success either.
If I plug a voltimeter to the wires that are going into the analog inputs (after conditioning), it measures about 50 mV, which is a lot more than the 1 mV the board is measuring, but a lot less than the ~180 mV I should be measuring with a pH 4 buffer solution.
I know for a fact the problem is not the sensor, and the DAQ board seems to be fully operational.
I think it might have to do with the signal conditioning I'm doing, or some sort of configuration with the hardware of the DAQ board.
So, any idea what I might be missing?
I'm a week behind schedule because of this, hopefully I will find my answer here.
Thank you very much in advance!

Good afternoon.
Yes I have tried all of that. The board responds very well when a flat 5V DC voltage is fed into a channel.
However after much investigation I believe to have found the problem yesterday, it probably has to do with the operational amplifiers I was using. The input bias current was in the magnitude of nanoAmps, while for pH measurements an IBC of picoAmps or less is necessary due to the high impedance of the sensor. This was causing a drift of over 100 mV on my output which is about 2 pH and thus unnacceptable (even though I had the Bias resistors at the input to ground, like suggested in the NI tutorials, but apparently they were not enough to compensate for the high IBC).
In the lab all available op-amps suffer from this, even Instrumentation op-amps like AMP04 from Analog Devices. I still haven't had a chance to acquire new op-amps with the necessary IBC but hopefully it will do the trick. Makes sense since I checked the datasheets for every op-amp in the lab, and they all had IBC around 400 nanoAmps (and none of them worked), while every single op-amp for every pH meter circuit I found have IBC's of pico/femtoAmps.
The sensor I'm using is from AquaMedic, I'm not sure what the model is, but it's a cheap plastic sensor that comes bundled with their pH Computers.
Thank you very much for your input.

Using FPGA and Labview without RIO board.

Dear Sir
I am a student. I want to connect my own FPGA and make a program on labview and then transfer to FPGA.I do not want to buy RIO.Is it possible to work
like that without purchasing RIO.
Thanks a Regards

Hooovahh wrote:
Yes NI supports programming FPGAs using LabVIEW without RIO boards I've been doing it for years and it works great. Here are a few non-RIO products I've used LabVIEW FPGA with.
PCI-E Version
PXI Version
USB Version
The PCIe and PXI cards you mentioned are specifically RIO.
But you managed to program a USB-6225 with LV FPGA? I'm not even sure there is an FPGA on there to program. It is an M series DAQ board.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

How to output sample and convert clocks to PFI lines of E-Series DAQ (DAQPad-6015)

Hi,
Can someone tell me how to output sample and convert clocks to PFI lines of E-Series DAQ (DAQPad-6015)?
Thank you very much.
Jack

John --
Windows is not an option for me. I like your idea of using a counter output -- it may be helpful as I am getting ramped up, but my application will eventually require both timer outputs.
I have a legacy C application written for Macintosh, and I am in the process of moving it onto OS X. So my options are to use DAQmx Base, or write an in-kernel driver. I actually have already done the latter for 6024/6025 E-series boards (for another company); for this client I was hoping to use the DAQmx Base to allow an easy transition to M-series boards, without the cost of writing and supporting a low-level driver.
The specific task I am doing is relatively straightforward. I record 2 channels of AI for a short period (usually about 250 ms.) and during this time I drive 2 external digital signals. Right now, I use the 2 timer outputs, which allows precise synchronization with the output and AI sampling.
I appreciate your comments, and thanks in advance for any additional suggestions you can lob my way.
--spg
Scott Gillespie
Applied Brain, Inc.
scott gillespie
applied brain, inc.

Synchronisation of frame grabber and DAQ board

I want to aquire images and analog voltage signals at the same time, and synchronised, using a NI PCI-1428 Camera Link frame grabber and a NI PCI-6014 DAQ board. Can this be done using the RTSI trigger functions? I know that the frame grabber supports this, but what about the DAQ board?
How about synchronising a NI-board with a non-NI frame grabber?
Thanks a lot!
Peter

Hi, Peter,
No, the PCI-6014 DAQ board does not support RTSI. However, most of the low-cost E-series NI data acquisition cards do support RTSI, such as the PCI-6024E or PCI-6036E, so you might consider using one of those boards instead.
If you decide to go that route, there is a useful tutorial that describes the signals that can be routed over RTSI for NI DAQ and IMAQ boards:
Developer Zone Tutorial: Synchronizing Motion, Vision, and Data Acquisition
as well as several example programs:
Developer Zone Example: Integra
ting IMAQ and DAQ with Single Display
Developer Zone Example: Low-level Triggered Ring (with DAQ-supplied triggers)
As for a non-NI frame grabber, that would really depend on what support the frame grabber has for timing and synchronization. You could route a trigger signal or scan clock out over the PFI pins on the PCI-6014, but you would need to see if the frame grabber is designed to receive these types of signals.
I hope that helps!
Best regards,
Dawna P.
Applications Engineer
National Instruments

Current loop measurement and DAQ board

Hi.
I want to acquire some values coming from sensors outputting a 4-20 mA signal.
I designed a solution with SCXI-1125 and E series card.
In other side, somebody -from NI- gave me a price offer with just E-Series DAQ card and a connecting board with resistors (and thus measuring Voltage). I can understand this solution (when the range are compatible).
So, can you explain me what are the benefits if I choose the most expensive solution (SCXI + E-series)compare to the cheapest one (E-series + resistor)
Thanks a lot.
SB.

Basically, the SCXI solution would provide a known level of accurracy and reconfiguration is much easier.
If you used a resistor network to convert the currents into voltages, you would be able to measure these voltages with your E-Series DAQ card with no problem. However, in order to convert these voltages back into the original currents you would have to apply scaling within MAX. This would require that you know each of the resistance values. Since many resistors have a slight tolerance, each resistor would likely have a slightly different value and need to be measured individually. The resistors could possibly change value over time or depending on the environmental temperature.
The signal conditioning solution, on the other hand, can provide you with a
known level of accurracy based on the specifications of the modules used. Additionally, if you ever required a change in your design you would only have to modify the configuration in MAX and no hardware changes would be needed since newer SCXI modules are software configurable.

I want to run my program with continuous aquisition and write data to file when a button is pressed and get the most recent samples from the DAQ board.

This is an update to a question I asked earlier. I am still trying to solve the problem. I have included a zip file with a library file. The file to open in pj_pushbutton.vi. I have placed comments explaining the issues and problems in this vi and the subvi's.
When I push my button to write the data to file I think it is writing the data that has already been stored in the buffer and writing to file all at once. I want the data that is taken from the DAQ board from the time that I press the Write File button. How do I do this?
Attachments:
pj_pushbutton.zip ‏692 KB

Hi,
1. In AI read, you need to set the Read/Search option to "Relative to End of Data".
2. Next you should not start AI Read VI until you press the Write to File. I am attaching an example VI below. Please see if it helps.
Regards,
Sastry V
applications Engineer
National Instruments
Attachments:
MostRecentAcquiredData.vi ‏97 KB

Measurement Computing DAQ Boards and LV

I have been using LV and NI DAQ boards for several years with
excellent results. Goodby C++ forever (well...).
My boss sent me a flyer for Measurement Computing DAQ Boards and the
prices are great. They even offer a card I can't get from NI.
My question is: how well do these boards work with LV? Can I use all
the NI supplied VI's or must I use only the ones provided with the
Measurement Computing card?
Does anyone sell a card that clones a NI card so all the NI VI's work?
Thanks,
Linuz

Here's an opinion from somebody who doesn't work for NI also...
The measurement computing boards are technically very good, and also very
inexpensive. However the last one (a multifunction DAQ card, I forget the
model number) definately suffered from the SW differences you describe.
I already have enough difficulty getting the NI cards to work properly; for
a complicated project I wouldn't want to add a 3rd party card to the mix!
Usually it's worth a couple hundred bucks to have the full NI-DAQ driver,
support with NI-MAX, standard NI vis, and technical support if (when) the
whole system doesn't work as documented. I have had enough trouble using
RTSI synchronization between genuine boxed NI products. For an ambitious
project I would rarely consider a 3rd party DAQ solution.
On the other hand, if your application is straightforward and you like the
cost savings then go for it. When I tried the computerboards card, the SW
was lackluster but functional. The HW was very solid and around 1/3 of the
price. Given that Labview PDS is so freaking expensive, I would definately
consider a 3rd party board for routine tasks. I had a fine experience with
the computerboards card and the approx $500 savings (at the time) made the
project affordable.
-joey
"Greg McKaskle" wrote in message
news:[email protected]...
> > I have been using LV and NI DAQ boards for several years with
> > excellent results. Goodby C++ forever (well...).
> >
> > My boss sent me a flyer for Measurement Computing DAQ Boards and the
> > prices are great. They even offer a card I can't get from NI.
> >
> > My question is: how well do these boards work with LV? Can I use all
> > the NI supplied VI's or must I use only the ones provided with the
> > Measurement Computing card?
> >
> > Does anyone sell a card that clones a NI card so all the NI VI's work?
>
> Any board can work with LV provided it has a driver to control it or you
> are ready to do peeking and poking to the board. Ideally it will also
> have the DLL calls into the driver wrapped into some VIs for easier use
> by LV users.
>
> Measurement Computing does have drivers, and you can purchase LV VIs for
> their cards.
>
> Before I go on, remember that I work for NI, so feel free to get another
> opinion or look into it yourself, but you will see a BIG difference in
> the SW support for boards from various manufacturers. NI provides lots
> of SW tools, VIs, and tech support, and that is reflected in the price
> of the boards. If a company sells the same board for less, they may be
> providing less in the SW and support side. You and your manager will
> have to determine the overall price of the project based upon your time
> spent installing, troubleshooting, writing VIs, and the price of the HW.
>
> As for a company making a clone of our HW so they can redistribute our
> driver? That has happened in the past, but to my knowledge no boards on
> the market currently do that.
>
> Greg McKaskle
>

Selection of daq board to find angular position of 6 motors using encoder

can you suggest me best daq board to use 6 motors positions as outputs using encoders attached to the motors. i will be using single counter for each motor. Or can i use a single counter for all the motors encoders??
Solved!
Go to Solution.

Hello Prabhakar7117,
You would need a counter for each encoder. Since you will be using 6 encoders, you should get a DAQ device with 6 or more counters. Take a look at the PCI-6624 or PCI-6602. Another option would be a CompactDAQ chassis with modules that are able to access the counters. Take a look at them.
PCI-6624
PCI-6602
KB Which cDAQ Modules can be Used to Access the On-board Counters?
Best Regards,
Alina M

I want use c++ for NI DAQ board and remote data access(RDA)

how can i control NI DAQ board with c++(bolandc) through network?

This is a forum for Measurement Studio development tools for Visual C++. You should post questions like this to the Measurements->Multifunction IO section of Developer's Exchange.
Best Regards,
Chris Matthews
National Instruments

Encoder and E-series DAQ Board

Similar Messages

Maybe you are looking for