LInuxCNC 2.6.3 encoder.N.min-velocity-estimate
10 Oct 2014 00:41 #51924
by ye11
LInuxCNC 2.6.3 encoder.N.min-velocity-estimate was created by ye11
Hi
Docs for LInuxCNC 2.6 contain such parameter for encoder as min-velocity-estimate. But in fact there is no that parameter. There is old min-speed-estimate.
And it does not work. I dont see encoder.N.velocity became zero, when it less min-speed-estimate.
Docs for LInuxCNC 2.6 contain such parameter for encoder as min-velocity-estimate. But in fact there is no that parameter. There is old min-speed-estimate.
And it does not work. I dont see encoder.N.velocity became zero, when it less min-speed-estimate.
Please Log in or Create an account to join the conversation.
10 Oct 2014 18:23 #51940
by andypugh
You seem to be right: git.linuxcnc.org/gitweb?p=linuxcnc.git;a...=refs/heads/2.6#l590
The value is used around line 473. I am not clear if it is rpm or rps based. It also appears that if you have encoder count dither it won't activate. I can see that dither in an axis might keep the encoder dithering so that the two elements keep each other "awake". I am not sure what you are trying to do with the pin, but it may be that PID deadband would be a better thing to try.
Replied by andypugh on topic LInuxCNC 2.6.3 encoder.N.min-velocity-estimate
Hi
Docs for LInuxCNC 2.6 contain such parameter for encoder as min-velocity-estimate. But in fact there is no that parameter. There is old min-speed-estimate.
And it does not work. I dont see encoder.N.velocity became zero, when it less min-speed-estimate.
You seem to be right: git.linuxcnc.org/gitweb?p=linuxcnc.git;a...=refs/heads/2.6#l590
The value is used around line 473. I am not clear if it is rpm or rps based. It also appears that if you have encoder count dither it won't activate. I can see that dither in an axis might keep the encoder dithering so that the two elements keep each other "awake". I am not sure what you are trying to do with the pin, but it may be that PID deadband would be a better thing to try.
Please Log in or Create an account to join the conversation.
10 Oct 2014 18:58 - 10 Oct 2014 19:00 #51942
by ye11
Replied by ye11 on topic LInuxCNC 2.6.3 encoder.N.min-velocity-estimate
Documention says 'The units of min-velocity-estimate are the same as the units of velocity', so it rps based in my case.
I'm using encoder component simply for sensing spindle speed and nothing more.
When spindle have stoped, velocity isn't zero. So I thought, this parameter was made exactly for this.
I'm using encoder component simply for sensing spindle speed and nothing more.
When spindle have stoped, velocity isn't zero. So I thought, this parameter was made exactly for this.
Last edit: 10 Oct 2014 19:00 by ye11.
Please Log in or Create an account to join the conversation.
12 Oct 2014 16:19 - 12 Oct 2014 16:22 #51975
by ye11
Replied by ye11 on topic LInuxCNC 2.6.3 encoder.N.min-velocity-estimate
After debugging i've selected the value of min-speed-estimate.
I have 100 holes encoder and set position-scale 200. So when my spindle rotates 100 rpm, i have velocity about 1.7 (it's rps, as you see).
Before i've tried to set min-speed-velocity in values like 0.01. And it didn't work.
Now when i set min-speed-estimate 500, all works corectly.
So the units of min-speed-estimate aren't the same as the units of velocity!
I have 100 holes encoder and set position-scale 200. So when my spindle rotates 100 rpm, i have velocity about 1.7 (it's rps, as you see).
Before i've tried to set min-speed-velocity in values like 0.01. And it didn't work.
Now when i set min-speed-estimate 500, all works corectly.
So the units of min-speed-estimate aren't the same as the units of velocity!
Last edit: 12 Oct 2014 16:22 by ye11.
Please Log in or Create an account to join the conversation.
12 Oct 2014 16:59 #51977
by cncbasher
Replied by cncbasher on topic LInuxCNC 2.6.3 encoder.N.min-velocity-estimate
what exactly is your problem , as you dont mention it , rather than what your are trying
Please Log in or Create an account to join the conversation.
Time to create page: 0.276 seconds