Encoder measurement

I found this paper that shows how to take the encoder measurment,,, now there is VI front panel shown at the bottom of this paper.... Now Iam using an NI Elvis board to take measurement and I need to know the code for this front panel..
http://zone.ni.com/devzone/cda/tut/p/id/7109#toc4
Thanks

SK0480,
Here is a link that explains how to use the quadrature encoder with NI Elvis. If you follow the link at the bottom of the article, you will also find an example that illustrates how to implement this in LabVIEW.
Good luck with your project!
Thanks,
Trey C.
Links:
http://zone.ni.com/devzone/cda/tut/p/id/4623
http://sine.ni.com/devzone/cda/epd/p/id/2177

Similar Messages

Quadrature Encoder measurements with PXI-6143 S-Series DAQ

Has anyone used a S-series PXI-6143 DAQ to take encoder position measurements? I believe there are 2 counters available, if you have any examples of how to access and read from these counters it would be greatly appreciated.

Hi Bentup,
Measuring a quadrature encoder on your device is actually going to be a bit different than on an M series device. The STC-2 chip, which is used in the M series, allows for A and B inputs specifically for encoder signals (used in the Angular Encoder task). The original STC-1 chip which is used in E series and most S series boards (including your 6143) does not have these same inputs. Instead, you may must a Count Digital Events task (taking advantage of the up/down line of the counter). The Angular Encoder task is not supported on STC-1 devices.
The article that lab_boy linked earlier actually mentions how to use an encoder with an E series device once you scroll down a bit (here's the link again). This same procedure should apply to your S series--connect the A output of your encoder to the source of the Counter (this is the signal that you are counting). Connect B to the up/down line of the counter (P0.6 and P0.7 for counter 0 and 1 respectively).
The downside with this method is that it is more susceptible to vibrations or noise on the encoder lines. If this is a problem for you, you can look into an external encoder conditioner like the one mentioned in the article. I hope this helps!
Best Regards,
John
John Passiak

Ni9402 CompactDaq Encoder measurement? DIO-ctr-PFI?

Hello,
I need to read two encoders. Actually, by now if I can read one I will be happy enough.
I've been trying with a ni9402 module and a 4-slot CompactDaq chassis. However, I haven't been able.
First tries were using DAQAssistant, but, can't understand how to perform the cabling. I get to choose with counter to use (CTRO/CTR1), afterwards I'm ask to cable A and B into PFI0 and PFI2, but my inpunts are named DIO0-3. So I've found in the help documents a correlation between PFI and CTRs... but still don't know how to cable.
Can somebody help me?

Hi pd1234,
You are probably picking up glitches on the transitions (encoders tend to be pretty noisy signal sources). These glitches would register as very short pulses, which would in turn be calculated to represent very large frequencies. To fix the problem, you should enable digital filtering (see M Series User Manual):
The above will pass through any pulses larger than 6.425 us, but will ignore the small glitches that you are likely seeing.
Best Regards,
John Passiak

Troulbe in measurement quadrature encoder with 6601.

Hi,
We are trying to measure position with 6601. The frequency of quadrature encoder is from 100Hz to 8MHz. Now, we connet the A,B and Z channel directly to counter . Using the example in CVI, we change the filter to 100ns and use x4 mode. It works perfect at low frequency.
The problem is when the frequency of encoder is higher than 2MHz, the accuracy decreases greatly. I'd like to know about following:
1.Can 6601 do the previous task enough? Or I must change to use 6602.
2.If 6601 is available, is there any way to increase measurement accuracy ?(in software or wire connection )

Jimmy,
You would need to specify what type of accuracy you are looking for, which is pretty much dependant on the type of operation you are performing. You could be looking to timestamp your encoder positions or you could also be looking to perform position/angle tracking over time. You could also be performing single point vs. multiple point (buffered) operations. You could mention which one of the CVI examples you are using and that could give an idea of the type of operation you are performing.
The NI-6601 is able to perform quadrature encoder measurements and the only limitations you can have in regards of frequency are the filtering parameters (if you use filtering) and the actual maximum timebase of the board (20 MHz).
Please keep in mind that by ena
bling filtering at 100 ns you are only guaranteeing that pulses with widths of 100 ns or longer are not being filtered out. This limits your encoder phase frequency to around 5 MHz. (Each encoder period has a 50% duty cycle, therefore the pulse duration is half the encoder period). You can refer to the board�s manual for more information on filtering.
We would have to know the following in order to provide further help:
a) Type of operation being performed
b) Specific example you were using
c) Type of accuracy you were looking for
d) Range of accuracy you needed on your measurement
Regards
Alejandro Asenjo
Applications Engineer
National Instruments

Encoder and Teslameter measurement....

HI all!!
I am using Encoder (A,B,Z) and Teslameter (measuring magnetic field).. Encoder has got 10000 pulses per revolution... I have connected the teslameter to AI 0... I tried programming to get the encoder reading and teslameter reading at the same time (i mean, for each pulse from the encoder, i should able to attain a value from teslameter)... i am getting failure as shown in the attachment.. i am attching my program as well...
I am using LabVIEW 2012, PCIe 6341..
Thanx in advance..
Every Expert was once a Beginner!!
Attachments:
Test_Drehmomentmessung2.vi ‏41 KB
error.PNG ‏8 KB

Hi Ed,
The DAQ-STC counter/timer chip on your PCI-6035E card is not your most accurate counter/timer chip to perform encoder measurements. You are better off using a PCI-6601 card which is much more accurate and has real encoder capabilities.
PCI-6601 (w/ NI-TIO Counter/Timer Chip)
http://sine.ni.com/apps/we/nioc.vp?cid=3589〈=US
The reason the NI-TIO chip is better suited for encoder measurements than the DAQ-STC is because of the following (which might also explain some of the difficulties):
1) DAQ-STC can't reset the count after an encoder revolution (NI-TIO can w/ Z-Index line)
2) DAQ-STC only has one encoder measurement mode and that is the 2-pulse encoder measurement mode. The NI-TIO has the X1, X2, X4, 2-pulse
This essentially me
ans that your DAQ-STC will count up when channel A leads B and count down if channel B leads A. There is no reference point, no ability to reset and no filters on the lines to prevent glitches.
What is probably happening in your case is that you are measuring 9,000 pulses in one revolution and you are also measuring glitches on the line which is why you are getting the extra 5,000 counts. The DAQ-STC shipping example programs will give you some insight into programming your E Series counter to make encoder measurements but your errors are more likely caused by the fact that it is just a simple 2-pulse encoder (up/down encoder).
Hope that helps. Have a good day.
Ron

Quadrature encoder counter with 8 channels

Hi,
I need to acquire the signals (A and B) of four quadrature encoders. The signals have a maximum frequency of about 5kHz and should be read out with about 100 Hz. Is there a device that fulfils these requirements? It seems that a frequency of 5kHz is no problem since e.g. the USB-6008 has a counter for frequencies up to 1 MHz. However, I can't find a simple low-cost device that provides several counters. Does anyone know such a device with 4 or 8 counters?
No other analog or digital channels are necessary, but a USB connection and Matlab support would be ideal.
Thanks in advance.

Depending on your definition of low-cost, the 9171+9401 might suit your needs:
4 counters capable of quadrature encoder measurements (the single counter on the 6008 only does simple edge counting).
USB connection.
MATLAB support via the Data Acquisition Toolbox (according to their website).
I don't believe NI currently has any other option that meets these requirements at a lower cost. If USB isn't mandatory, you could also consider the PCIe-6612 which provides 8 counters.
Best Regards,
John Passiak

Tuning an optical encoder with a linear actuator

Hello everyone!
I am trying to get an optical encoder (5 lead single ended, incorperated into an Ultramotion D2 series linear actuator) to read the position of the linear actuator's position to 4 decimal figures precision (0.0001), and the DAQ I am using is NI cDAQ 9121 with 2 channels. I decided to use the 65 mV configuration. The encoder has ground, channels A and B, index and 5V leads, of which I have omitted using the index and channel B. Channel A is connected to the AI+. The linear actuator has a scaling of 20,000 steps per revolution and a movement of 4mm per revolution (point to point configuration of the stepper motor drive ST5-S, by Applied Motion).
I am not sure if the above configuration is suitable, but I am limited to the current equipment. I have coded the program using LabVIEW 2014 and, while it seems to give a good estimation of the displacement to the nearest 1 mm, it is not recording the fractions and counts anything that is 1mm or less as simply 1.
My question is actually threefolds:
1) How can I tune the encoder to read the exact measurement to the nearest 0.0001 accuracy?
2) Am I using an appropriate configuration for the leads?
3) If the problem is not one of the above, could it be something concerning the DAQ software settings and/or the code itself?
Thanks for your advice in advance!

Hey kmhijazi,
Here I share the most general documentation about using encoders with DAQ devices:
Using Quadrature Encoders with E Series DAQ Boards
http://www.ni.com/tutorial/4623/en/
Then, here’s a second resource where you can find more details that you can adjust to improve the measurement (i.e the Decoding type, which will however depend on your encoder specifically):
Encoder Measurements: How-To Guide
http://www.ni.com/tutorial/7109/en/
And, here you will find how to create a test task in NI MAX to try changing these parameters and test if these improve your accuracy.
Connecting Quadrature Encoders to a DAQ Device
http://www.ni.com/getting-started/set-up-hardware/data-acquisition/quadrature-encoders
I hope this can help.
Regards,
>>Daniel C.

Problem Counting A and B Encoder Signals on Two Counters.

Hi All,
I have an existing LabVIEW program that uses three counters to measure A, B and Z signals of the encoder. I can read these signals separately if I hook only one of them to the PCI 6602. If I hook up A and B, I will get intermitten correct reading for signal A. I will always get the correct reading for signal B. Is there a problem of trying to measure these signals using separate counters? This program basically tries to measure the time between the different edges. There isn't any documentation, so I am not even sure which board this application was written for. Although, there is an analog input section of this code. I even tried the counter for the 6502E board. I get the same problem. I am not sure if the physical channels constants in the program is correct. Has anyone run into this problem before?
Thank you for your input.
Attachments:
Main Encoder Tester.vi ‏883 KB

Hello Van626,
After looking over your code for measuring a encoder, I would suggest performing this acquistion in a different way. The reason why is that it is not advisable to create and clear or start and stop in a while loop. In order to get around this, here are some ideas I had:
1.) Use the Counter Input Angular Encoder Task. This task will allow you to record the encoder measurements so that you don't have to program this yourself. I would suggest starting with Measure Angular Position.vi example in LabVIEW. In order to specify the PFI lines for the A, B, Z terminals, there is a channel property node under Counter Input » Encoder for A, B, and Z terminals.
2.) If you want to record each signal, you have enough counters to do this. There is a VI called DAQmx Connect Terminals that will connect PFI lines together. In doing this, you can connect your three signals to three PFI lines but have them go to multiple counters. I have current tested this with an Angular Encoder task with a Two edge Separation and it works perfectly
Note: You will need to look at the Device Routes for the PCI-6602 to ensure that you are sending the signal to the correct place. Another caveat about connecting PFI lines together you will have to disconnect them when you are done. If you don't they will always be connected. This can be done by reseting the device using the DAQmx Reset Device.vi or the DAQmx Disconnect Terminals.
Jim St
National Instruments
RF Product Support Engineer

Encoder velocity

I am having troubles measuring the velocity of my linear encoder with PCI-6220 card. I have read examples that used dx/dt, but I cannot seem to get that to wok-- when I wire that output to a gauge, I get "0". I have also tried using shift registers to store previous data for position & time stamp to calculate changing position / changing time, but the problem with that is I get a lot of NaN & inf values randomly occuring admidst getting velocity readings that are appropriate.
Thanks!

Hello Paolinooo,
To get an understanding of how to program an encoder task with the NI-DAQmx VIs and your PCI-6220, I would recommend taking a look at the DAQmx shipping examples found within the LabVIEW Example Finder by going to Help > Find Examples. The encoder measurement examples can be found under DAQmx > Counter Measurements > Position. Also, you can search the online example program database, found at www.ni.com/examples.
Travis G.
Applications Engineering
National Instruments
www.ni.com/support

Counting edges with dynapar encoder

Hello,
I am very new to Labview. To kick off some experience, I am trying to count edges on a Dynapar encoder, Model E14020000303. Here is the data sheet:
https://ecatalog.dynapar.com/downloads/E14_DS_702489_2_.pdf
I am using LabVIEW 2011, with a NI USB-6210 DAQ. My white wire on the encoder is connected to PFI0. The red and black wires are connected to my 5V voltage source. I am rotating my encoder to count the revolutions. Supposedly my encoder is a 200 PPR, and it is also quadrature.
However, I am not understanding what I am getting when counting edges using DAQ Assistant. I am using the Edge Count on ctr0. I can set the DAQ assistant to run on 1 sample acquisition mode and count the rising edge. When I turn the encoder 100 times, the measured value on the DAQ Assistant is usually around 76500, which would mean 765 edges counted per revolution. I can also change things around and go to continuous acquisition mode. I set up PFI2 as the external clock source with a rising edge and put the green wire in PFI2. I set it to read 1 sample at 1k Hz. This usually results in counting around 820 edges.
I don't understand why I am getting these readings. The DAQ Assistant should only be counting rising edges because that is what it is set at. Why am I getting numbers so high?
Thanks!

Hey guys,
Sorry for the late reply, I have been put on other tasks. You all were right about the ground, that indeed was the problem. With the daq grounded, the encoder measures 200 edges per revolution.
Thanks!

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!

Simultaneous acquisition of accelerometer and an encoder measurements of a rotating machinery.

I want to do a simultaneous acquisition of accelerometer and an encoder measurements of a rotating machinery.
So which National Instruments data acquisition product must be chose to do this capture.
Solved!
Go to Solution.

1st: check the voltage ranges of your encoders and accelerometers
2nd: do your accelerometers need IEPE power?
Ideas: (for accelerometers needing power and encoders with > +/-10V range)
NI USB 4432
NI USB 9232
NI CompactDAQ with 9232
other options in C series include 9234, 9229, 9215, etc.
In PXI, there is the 449x series of PXI express cards.
Do you have analysis and visualization requirements?
Take a look at these manuals:
http://digital.ni.com/manuals.nsf/websearch/5D343672A7367E6286257B9D00527B30
http://zone.ni.com/reference/en-XX/help/372416C-01/
Regards,
Preston Johnson
Principal Sales Engineer
Condition Monitoring Systems
Vibration Analyst III - www.vibinst.org, www.mobiusinstitute.com
National Instruments
[email protected]
www.ni.com/mcm
www.ni.com/soundandvibration
www.ni.com/biganalogdata
512-683-5444

MyRIO Encoder Drift

I'm new with myRIO and just started hooking it up to a laser for linear positioning measurements. My problem is I'm getting drift when the actuator isn't moving. I'm using the myRIO express VI for encoder measurements. (I have tried using the myRIO advanced IO encoder VI's and I get the same drift problem, but I also get repeated and occasional errors. This seems like a complicating case, not an enlightening one, so I'm going to focus on getting the express VI to work unless someone has a good reason not to work with it).
Unfortunately, I don't have a great datasheet for my laser setup, but from what I can see now I'm getting about 30,000 counts for my full range of movement which is about an inch. I know this because I can see a nice waveform from the encoder outputs when moving from end to end. So that's good - it works overall. However, every few seconds or so - and this isn't a periodic thing, I can't figure out that it happens regularly - the encoder counts will rapidly change value and lose a bunch of counts, usually around 50 or 100 at a time. 'Rapidly' meaning within about 50 counts of my loop running at 1k. Then it will hold steady (or track the motor position if I move things around) until a few more seconds and it will drift again. Sometimes a few drift occurrences will happen in a row, so the difference will be larger and a little slower. What I'm calling drift looks like a step change, not a ramp.
As far as I can tell, the drift is always negative. If I switch the A and B terminals, the drift is always positive. There are some slight components in the opposite direction, but nothing nearly as large/consistent.
If I turn the laser off, the reading is steady with no drift.
I'm pretty much at a loss right now for what the problem is/how to fix it. Since I'm able to read the encoder when the system is moving, I figure it's not an issue of processor speed since it can capture the faster encoder responses that happen when the system is moving. I don't know what else would cause the counting to get so messed up. Any thoughts?
For completeness, here's my basic VI:
And here's the front panel: around time 9000, I moved the actuator forward, but from zero until then, all that drifting is from this undesired encoder behavior.

Hey rmyUCLA,
When you first call the Encode Express VI a counter is enabled in the FPGA. That counter increments or decrements each time an incoming pulse is read on the encoder channels. Subsequent calls to the Encoder EVI simply read the count register on the FPGA. The FPGA runs independent of your RT timed loop so the timed loop speed shouldn't have any effect on the 'drift' you're seeing.
If you're encoder has about 30,000 ticks per inch were talking about 33 micro inches per tick. The drift you're seeing is about 1500 ticks which is about .05 inches. Is it possible the system is actually moving around this much? Have you used this setup with another system reading the encoder values?
When you say the drift doesn't happen when the laser is off, do you mean the motor controlling the Laser or the beam? Is it possible the beam causes vibration in the system? Is the laser systems power tied to the myRIO power? Its possible the laser causes the encoder power to become noise and generate bad pulse?
Let us know and we'll see what we can do to help. Good luck!
-Sam K
LabVIEW Hacker
Join / Follow the LabVIEW Hacker Group on google+

Encoder and LS184 Clock Converter Problems

I am trying to implement position measurements using a 9000 CPR and 1000 CPR encoder and a clock converter chip LS184 but I have trouble obtaining a consistent count with my PCI-6035E DAQ-STC counter. The count does not seem to be correct (9000 counts in one revolution, which is times 4 in X4 mode or 36,000 counts; I am getting around 14,000 and this is not even the same every time), and the count does not return to zero when turning the encoder back to the original position. I had that problem with the direct encoder connection to the counter (A to source, and B to DIO6), and obtained the LS184 clock converter chip to fix the problem. However, it is even worse with the clock converter. I tried different values of the bias r
esistor but the problem was still there. What am I doing wrong?

Hi Ed,
The DAQ-STC counter/timer chip on your PCI-6035E card is not your most accurate counter/timer chip to perform encoder measurements. You are better off using a PCI-6601 card which is much more accurate and has real encoder capabilities.
PCI-6601 (w/ NI-TIO Counter/Timer Chip)
http://sine.ni.com/apps/we/nioc.vp?cid=3589〈=US
The reason the NI-TIO chip is better suited for encoder measurements than the DAQ-STC is because of the following (which might also explain some of the difficulties):
1) DAQ-STC can't reset the count after an encoder revolution (NI-TIO can w/ Z-Index line)
2) DAQ-STC only has one encoder measurement mode and that is the 2-pulse encoder measurement mode. The NI-TIO has the X1, X2, X4, 2-pulse
This essentially me
ans that your DAQ-STC will count up when channel A leads B and count down if channel B leads A. There is no reference point, no ability to reset and no filters on the lines to prevent glitches.
What is probably happening in your case is that you are measuring 9,000 pulses in one revolution and you are also measuring glitches on the line which is why you are getting the extra 5,000 counts. The DAQ-STC shipping example programs will give you some insight into programming your E Series counter to make encoder measurements but your errors are more likely caused by the fact that it is just a simple 2-pulse encoder (up/down encoder).
Hope that helps. Have a good day.
Ron

Stepper motor pulses per step measurement (Step Angle)

Hi everybody,
Recently I have one project to do step angle measurement for a stepper motor. The motor will couple with A,B phase encoder, and PXI-6602 card is used to count the pulse from encoder.
Well, the test will make the motor to rotate 1 revolutuion (360 degree) i.e. 200 steps are required. The software must able to measure and record the pulses per stepper's step i.e. 1.8 degree until 1 revolution is reached. But now the PXI-6602 will only present the accumulative counts per revolution, Any idea can split the accumulative count into small per step count with high speed and accurate method.
Thanks & Best regard.

What is it you need to characterize? For what purpose? Using an external sampling clock can help make the test run much more quickly, but is not absolutely necessary.
One of my first counter-based apps was to characterize a stepper motor with a microstepping drive. 1 counter measured the step and direction signals going from the motor controller to the microstepping drive. 1 counter measured a quadrature encoder. Only the encoder measurement used a sampling clock, and it was internal.
My technique included considerations such as:
1. I did not move in single steps. It may be a little less crucial to you with a 200 step/rev motor & drive. I had something like 3200 step/rev as I recall. Friction alone could have prevented any motion from occurring on single steps.
2. Each motion moved some small-ish prime number of steps so I could move around many many revs and be sure to land on each stopping position an equal # of times. A simpler method would be to move 1 rev + 1 step. In your case, that's 201 steps. The downside is that you extend testing time. With a 200 step/rev motor, this shouldn't be such a burden though.
3. After all step pulses were issued, I started monitoring the encoder data. I looped around evaluating chunks of position data to determine when I had a dataset that looked "settled." The main criteria I used were slope and standard deviation. When the criteria were met, I would store the median value. You could consider using a mean or an RMS as well.
4. Repeat enough times that you land on each stopping position a statistically significant # of times. Rule of thumb seems to be about 30. That would give you 6000 actuations of 201 steps each. Seems feasible that test time might be in the 1-2 hour realm.
-Kevin P.

Encoder measurement

Similar Messages

Maybe you are looking for