Recently I used an encoder for both velocity and position on a specialist application (not using LinuxCNC) and it worked very well. Velocity is calculated by measuring the time between successive encoder counts. This application uses a very coarse encoder (144 counts/rev) and it only runs at low speed (<200RPM). I'm not sure how well that would translate into a LinuxCNC application. For higher resolution encoders at higher speeds you need a very fast timer.
Les On 26/03/2015 02:59, Leonardo Marsaglia wrote: > Hello Jon and thanks for the link I didn't remember about it. I guess > my approach of using the same encoder mounted on the shaft of the > motor isn't the best solution for speed and position feedback right?. > As I told gene I was planning on using the same encoder for velocity > and then position feedback but I don't know if this is a good option. ------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/ _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
