Dynomotion Forum

There are about 8 other ops in the program. The one right before this calls the tool/offset/spindle speed (it's the same op, just patterned to a different instance of the part, it also doesn't error out weirdly). I can re-post with just that op, make sure it still fails and upload that if it does. Y...

This is what it shows

I commented out everything but WaitForNextTimeSlice(); in the forever loop. I get the same error in the same place. I *think* I might be using the trajectory planner from this link but I can not remember for sure:

http://dynomotion.com/Software/Patch/Im ... preter.dll

Yes, repeats every time in that spot. I'll give it a shot and see what happens. Travels are 40x20x20" (XYZ).

Trajectory error.txt is the g-code program that causes the error; the line it stops at is marked (error)

Main c program is defaultStart.c

The other two are the spindle programs, there is nothing else running.

Sorry for the delay, I had to go out of town suddenly. I'll dry run it tomorrow and copy/paste the code where it errors out (it's a long program). I am using 4.35f

update to add: the particular code has quite a few feedrate changes fairly rapidly, from 15 IPM to 60 IPM (cut at 15 ipm then reposition, repeat over a small area)

Weird random error today while running a small adaptive clearing toolpath with a 1/16th end mill. Happened in the exact same spot twice in the code, just a normal x-y move after an arc. No console output directly after the error but after clearing the error msgbox and trying to jog the Z up with my ...

The only other program that should be running is the main loop (attached). Yes I see the forever loop sends FRO and SSO commands to KMotionCNC. Also potentially very frequently as these settings: #define CHANGE_TOL 0.02 // only update if change is more than this #define CHANGE_TIME 0.05 // don't up...

I discovered PC_COMM_HALT_NEXT_LINE. Will see if that does the trick.