Encoder Issues, Help!
- BigJohnT
- Offline
- Administrator
Less
More
- Posts: 7000
- Thank you received: 1172
15 Jan 2016 22:38 #68499
by BigJohnT
You are in the unique position to help the next person that has this problem.
JT
Replied by BigJohnT on topic Encoder Issues, Help!
I at last figured out the problem. It's a bit embarrassing, but the problem was my measurement setup. I was using a dial indicator on a test stand with a magnetic base. I thought that the results were too consistent to be the test setup so I dismissed that as a possibility. With nothing better to do I made a couple shallow cuts 5" apart and measured them. 5.000" exactly, hooray!!
Thanks everyone for the help and sorry for the wasted time on a dumb mistake.
You are in the unique position to help the next person that has this problem.
JT
Please Log in or Create an account to join the conversation.
- HalaszAttila
- Offline
- Premium Member
Less
More
- Posts: 143
- Thank you received: 5
11 Feb 2020 12:43 - 11 Feb 2020 12:43 #157042
by HalaszAttila
Replied by HalaszAttila on topic Encoder Issues, Help!
Hello,
where can i find this pin:
- quadrature-error.enable
this pin tell me, if some problem is with encoder differential input? Or just check the A - B signal difference?
where can i find this pin:
- quadrature-error.enable
this pin tell me, if some problem is with encoder differential input? Or just check the A - B signal difference?
Last edit: 11 Feb 2020 12:43 by HalaszAttila.
Please Log in or Create an account to join the conversation.
- PCW
- Away
- Moderator
Less
More
- Posts: 17992
- Thank you received: 4838
11 Feb 2020 12:49 #157043
by PCW
Replied by PCW on topic Encoder Issues, Help!
It indicates a error in the quadrature protocol (A,B change at the same time)
You may need updated firmware (and LinuxCNC 2.8) for this to work properly
(there was a driver bug and a firmware bug in older firmware so that the error reporting was not reliable)
You may need updated firmware (and LinuxCNC 2.8) for this to work properly
(there was a driver bug and a firmware bug in older firmware so that the error reporting was not reliable)
Please Log in or Create an account to join the conversation.
Time to create page: 0.056 seconds