path errors after power down, estop events, long arcs and other weirdness 2.8.4

has anyone seen weird behavior after hitting the machine power down button ? I get some truly strange behavior,it seems like the path blending is doing strange things. I have no idea where to look. 

Pics of error, those 2 arcs appeared and the machine cut that path, after i powered the the machine on off , and it will do it if i let ut sit as well, or if i alter the speed fred spindle speed, it's like the coordinated motion is getting screwed up. I am using constant surface speed

I'd check the G64 value that's active before/after power on/off cycle.  Maybe there's an inappropriate P-number that the machine is defaulting to between on/off and the program you're running doesn't have a G64 Pn to reset.

I'll check that, also that tool path, she's moving fast , it's a small part and I'm sending it

Spammer booted.

G64 p0.001 is set in my startup configuration in my ini, has been for a long time. I've noticed some other issues, weirdness due to power off, estop

smc.collins wrote:

G64 p0.001 is set in my startup configuration in my ini, has been for a long time. I've noticed some other issues, weirdness due to power off, estop

According to the docs, the startup code in INI is only read in when the interp initializes.  So my guess is that while your first cold-start invokes G64 P0.001, after subsequent power-off or estops the P-value may not be what you think it is.

I could be wrong, of course.  But it's worth checking the p-value after powering down and back up and not just relying on the INI value.

Regarding estop resetting G64:
github.com/LinuxCNC/linuxcnc/pull/2742

not sure if this is also an issue for versions pre 2.9.

Solid, I should probably just mosify my post processor to output the g64 commans8 for finishing passes

My lathe is very fast, over 600ipm capable and acceleration to match, I've got 10hp dc brushed servo drives with 75 amp 240v glentek amplifiers.

It's not a acceleration issue as eluded to in that ticket. The default should always be precision over speed however. Novel idea, why not add some custom mcode macro calls into the default install and add matching macro calls to the post processor, when roughing, leave 30 50 thou, a little loose on path following is ok, on finish and tolerance work, no can do