That sounds right, it's a queue buster because of the spindle speed change,
so it acts like exact stop. I'm still not sure why it's capping the speed
at 237RPM.
Your outputs make sense (~19 ipm at ~270RPM actual speed is about 0.07 in /
rev). I'll poke around some more and see what I can find.
oh - what - did you mention you get exact stop when it is trying to
change the spindle speed? Is that why it is happening on this system?
sam
On 12/14/2016 05:56 PM, sam sokolik wrote:
> Here is a plot with motion.spindle-speed-in
>
>
also - am I seeing an exact stop at the pull out?
2.7 doesn't seem to do that. (I am positive we want blending on pull out)
http://electronicsam.com/images/KandT/testing/robthreading/latest/current2.png
sam
On 12/14/2016 05:56 PM, sam sokolik wrote:
> Here is a plot with
Here is a plot with motion.spindle-speed-in
http://electronicsam.com/images/KandT/testing/robthreading/latest/robnewandspindlein.png
sam
On 12/11/2016 03:52 PM, Robert Ellenberg wrote:
> Sam, one last thing, is it possible to put the spindle-speed-in pin on a
> halscope channel? I'd like to
There is no filtering. Here is the complete config
net spindle-vel encoder.0.velocity motion.spindle-speed-in
http://electronicsam.com/images/KandT/testing/robthreading/latest/Emco_HalfFull_Morph.tar.gz
I can scope more pins but it will have to wait a few days.
sam
On 12/11/2016 03:44 PM,
Sam, one last thing, is it possible to put the spindle-speed-in pin on a
halscope channel? I'd like to see what the spindle velocity is when it
transitions out of accel sync.
On Sun, Dec 11, 2016 at 4:44 PM Robert Ellenberg wrote:
> Thanks for giving it a spin!
>
> I am still
Hi Gene,
I don't fully understand your question, but I have reason to think that my
fixes will improve position tracking accuracy and consistency, and may help
in the scenario you describe.
In case you're not familiar with motion's internals, here's what happens at
the start of a position sync
Thanks for giving it a spin!
I am still getting the error about the spindle going too fast.. You can
see the threading is happening at 19.12 ipm and the axis max vel is
30ipm. I tried a similar config and got the same result (could be both
configs have some odd issue we have not figured out.)
Threading air..
The motion seems a lot more consistent - no funny blip the original did.
run after run looked pretty much identical in halscope.
http://electronicsam.com/images/KandT/testing/robthreading/latest/newthreadingfix.png
motion.spindle-tracking-gain set to .5
On Sunday 11 December 2016 09:17:32 Robert Ellenberg wrote:
> Ahh, that would have been smart to include before:
>
>- sim_spindle_encoder's position signal is now quantized based on
>encoder resolution.
>- Use motion.spindle-speed-in as the velocity reference for spindle
>position
Ahh, that would have been smart to include before:
- sim_spindle_encoder's position signal is now quantized based on
encoder resolution.
- Use motion.spindle-speed-in as the velocity reference for spindle
position tracking (falls back to old velocity calculation if this pin is
On 11 December 2016 at 06:30, Robert Ellenberg wrote:
> For anyone interested in testing, my latest branch based on Peter's
> suggestion, and a bunch of other spindle tracking fixes is here:
Can you explain what is changed and improved?
--
atp
"A motorcycle is a bicycle with
On Sunday 11 December 2016 01:30:42 Robert Ellenberg wrote:
> For anyone interested in testing, my latest branch based on Peter's
> suggestion, and a bunch of other spindle tracking fixes is here:
>
> https://github.com/robEllenberg/linuxcnc-mirror/tree/feature/spindle-s
>ync-overhaul-2.7
>
>
For anyone interested in testing, my latest branch based on Peter's
suggestion, and a bunch of other spindle tracking fixes is here:
https://github.com/robEllenberg/linuxcnc-mirror/tree/feature/spindle-sync-overhaul-2.7
I've tweaked a lot of spindle tracking code, so I'd be careful when running
Peter, I like your idea of calculating a velocity if none is provided. I'll
take a look at the PID component.
Andy / Chris, from your feedback, it sounds like cases like Jon's are rare,
but we shouldn't break them. Peter's approach gives a safe if suboptimal
fallback. If the future manual
On 12/08/2016 12:19 PM, andy pugh wrote:
> On 8 December 2016 at 18:10, Robert Ellenberg wrote:
>> Does anyone use a spindle encoder with only position output? In other
>> words, encoder position linked to motion.spindle-revs, but no input to
>> motion.spindle-speed-in?
> I
On Thu, Dec 08, 2016 at 06:10:09PM +, Robert Ellenberg wrote:
> Hi All,
>
> Does anyone use a spindle encoder with only position output? In other
> words, encoder position linked to motion.spindle-revs, but no input to
> motion.spindle-speed-in?
motion.spindle-speed-in IN FLOAT
On 8 December 2016 at 18:10, Robert Ellenberg wrote:
> Does anyone use a spindle encoder with only position output? In other
> words, encoder position linked to motion.spindle-revs, but no input to
> motion.spindle-speed-in?
I would imagine that it might be uncommon, but not
18 matches
Mail list logo