drbitboy
Lifetime Supporting Member
catching both rising and falling edges to increase resolution works best if the prox duty cycle is 50%.
...or is it an infinitely variable pitch drive
they had them like 30 years ago everybody changed them to a VFD a long time ago ....
As long as you can reliably sense the rising and falling edges, the duty cycle doesnt have to be symmetrical.catching both rising and falling edges to increase resolution works best if the prox duty cycle is 50%.
As long as you can reliably sense the rising and falling edges, the duty cycle doesnt have to be symmetrical.
Count the rising edges over time to calculate the rate.
Count the falling edges over time to calculate the rate.
Sum the two values and divide by two and you have doubled the resolution.
Then JesperMP's idea will work. Adding more proximity detectors that count the rising and falling edges will help.Typical prox response time is .3ms. Need to see the actual wiring.
DrbItbOy is right, really?
Does a ML1400 have floating point? Is it implemented in software or does the microcontroller have floating point instructions?How does one implement alpha-beta-gamma filter with Mlgx 1400?
Am I missing something here - you have a HSC - get a cheap $100 encoder. Voila!
In searching for a high resolution motor tachometers.... I did notice... for slower rpm readings...they were using photo eyes and not prox switches.
You are right. For example I use servo motors, with nominal speed 3000RPM, and resolution 2^22 pulses per turn.I think every encoder I have seen or checked out online was an optical encoder, even those rated for high speeds