QTPYVCP+VISMACH+LINUXCNC ROLLED INTO ONE?

no retro fits on these i was just saying the memory for program storage is what ever the base model came with at the time. sadly the people i work for don't spend the extra money to upgrade that part of the machine when they buy them.

they guys were old school who have retired or moved on and they hand coded everything in the past so bloated cam programs were never an issue before because of this. the one mori is nothing fancy at all but when i first came out of trade school back in 1991 they had that machine at it's still there so it's 35 years old plus

 

i'm not even close to being done but got the viewer hooked into a custom .ui file. i think i am on the downhill side of things now but this seems to be the hard way to do it but since i have so much time in teaching myself this i will finish what i started. but basically, it's done in OpenGL.

This is amazing and exactly what I was looking for. (Thank You!) I'm struggling with how to fix the scale of my stl file. I'm also having trouble finding any documentation for this. Does anybody have a link to documentation or other examples?

how is your project coming along?

   


As per your instructions I have made vismach file for my small cnc.But CNC movement if GUI is correct. But Tool movement in Y direction is wrong.My yaml file.
 

its not wrong, which direction is the "TOOL" moving through the work?

The problem is that the backplot needs to move with the table.

How can I resolve this?

See GIF file I have uploaded. The tool marker from view port is moving in opposite direction. I want it should be below spindle tooltip. As it moves while jogging in X or Z direction. But Y jogging time, table is moving correctly. But tool marker is moving in opposite direction.

The tool path needs to be plotted relative to the work piece. (tool -> world -> work)

The problem is that your tool position is plotted in World coordinates (tool -> world) which works if only the tool moves because the Work coordinate system remains identical to the World coordinates.
However on a machine like yours where the tool AND the work move in space the plotter needs to track both the tool tip as well as the work piece.
This is why the 'vismach' tool needs the capture() function for the tooltip as well as for work.

Not sure but maybe the backplot in ProbeBasic only plots tool position in world coordinates instead of plotting tool position in Work coordinates?