Gmoccapy - A new screen for linuxcnc

Your code looks very strange, but I doubt that is the problem.

Can you answer the question about whether the DRO changes during the un-programmed move? That would help to work out where the problem might be.

Is this a stepper machine, or servos?

The machine is set with Bosch ac servo. Tacho to the drive encoder to linux. mesa 5i20 7i33 7i37

Yes the DRO is showing the moove, and the plot have record the moove.

Here some picture, the pencil show the move. The result is on the white melamine sheet.






My Gcode is strange i know.
I cut it in parts with a lot of underscore in case i need to start again at a tool change position.
And recently i have mix G61.1 with G64P to win some time during positioning move where i dont need any acuracy.

This is the G code file i was running when it happen.

OK, that's a big, serious machine and runaways there have scope to be very bad.

What are your following-error limits? Do you trigger a following-error fault during these moves?
I am trying to work out if these are commanded moves being accurately followed, or something hardware / control-loop related.

(As an example, a wiring fault on a tachometer would send the drive running full-speed in a random move, but LinuxCNC would spot that the axis wasn't where it should be and shut-down when the F_ERROR limit was hit.)

Actually, that's another thing, do you get a following-error?

Can you take the tool out, move the Z to a safe height, and repeat with Halscope running?

I am not in front of the computer but this kind of move are bigger than what i have set! The gantry id quite heavy....

I am have use the machine a complete year under Axis with 2.5 and never get any problem.

The strange thing is Pusch PAUSE then STOP and here she jump.
Tow day ago it was worst, she completely Erase g54 XY offset on the middle of a cut and went out of 350mm
Hopefully i am not using any fixture

I tell you Halloween is coming and she want to kill me.

One idea will be to try with 2.6.3 and Axis Display if it happen again.

Next month i will start retrofiting a bigger one with 3.5m/s/s acceleration and 75m/mn XY speed...... I hope we found what going wrong around

Any way i dont think Ferror will save me because when i look at the Gcode on right screen the line where she jump was highlight. ( i have not sitch on Start frome here ) wihout stable MDI mode it is yo hazardous to Start on the middle of a moove without any G43 or M code.

Last thing, the crazy moove was perfectly executed, cordinated XY g61.1 then plunge g64 and cut.
A mechanical error could not be so perfect.......

It's a ghost !!!!!

papaours wrote: One idea will be to try with 2.6.3 and Axis Display if it happen again.

That's an easy test. Gmoccapy is pretty new.

You could try Touchy, but that absolutely requires some physical controls. (The designer didn't trust a touch-screen for actual machine moves, a viewpoint I have some sympathy with)

Axis is very, very well tested by now. I think that switching to that might help isolate the problem.