Hi John,
It looks like it affects LinuxCNC too, I created an issue to track it here:
https://github.com/LinuxCNC/linuxcnc/issues/550
The root cause seems to be that canon and TP have different ideas of what a
"small" displacement is. Due to architectural decisions made before my
time, the TP has
ajectory
> planner and what normally prevents that from happening?
>
> Yours and Schooner's insights have been helpful so far. Maybe we can work
> together to figure out what is going on.
>
> -John
>
> On Saturday, February 25, 2017 at 1:16:32 PM UTC-7, Robert Elle
It's a bit hard to follow at first, but there are two functions that
actually queue a move in the trajectory planner (both in tp.c):
- tpAddLine
- tpAddCircle
These are called from command.c int the "emcmotCommandHandler" function,
when the EMCMOT_SET_LINE and EMCMOT_SET_CIRCLE commands are
What I thought was the fix had already been merged in at least a year ago,
so it will take more testing to isolate the cause. Is there a short G code
program that can reliably reproduce the issue?
On Mon, May 8, 2017, 3:06 AM icecube45 wrote:
> @Robert
> I was wondering if you had found a time t
Hi All,
My guess is that this is a mismatch between canon and the TP in how a zero
length segment is defined. I recall running into a similar issue with
LinuxCNC. If we're lucky, it's been fixed already in another branch and
it's a matter of porting the fix over to Machinekit. I'll take a look thi
