Grecode

Thanks for the reply.
I didnt compile it. I will try to do it, not sure how. Copy/paste the crecode folder in to linuxcnc config folder and run -make- ? I guess...

Can't make it to work... Not sure how to do it. Any help?
Maybe the problem is that I am using gmoccapy.
I did manage to run the ge.py with m138 but nothing happened when I choose xflip nor other options.

Aciera wrote: [edit]
Using two different switchable kinematics might also get you a functioning machine but the toolpath preview on screen would not show the gcode as mirrored since it's the kinematic that changes and not the gcode. Also I would think it's quite a bit more effort then if you can get grecode working for you.

No luck with grecode so I am thinking about switchable kinematics. I am a little unsure how it's going to work. My machine has ATC and it is set in G54 coordinates. What will happen with ATC when I run the program in G55 (RH corner) with switched kinematics (X opposite). It will make tool change but, I wonder if it will come back to switched kinematics

I did manage to run the ge.py with m138 but nothing happened when I choose xflip nor other options.

Did you reload the gcode? Also I'm not sure on how to set up Grecode but I presume you needed to define file paths and things. Maybe something is not quite right there.

thinking about switchable kinematics. I am a little unsure how it's going to work.

I've made a quick sim config using dgarr/switchkins-v2. So after homing the machine is set to regular kinematic (LH), you set your G54 Offset location on the LH side of your table and load your GCODE containing G54. to switch to the RH you issue M429 and the G54 offset location is automatically mirrored to the right hand side of your table and you can run the gcode file. Then you can issue M428
and the G54 offset is mirrored back over to the LH side and you can run the gcode there. ATC should not be affected, I think.

user-images.githubusercontent.com/460672...d8d-7d55946dcb26.mp4

If you want to try it you will have to build the switchkins branch:
forum.linuxcnc.org/38-general-linuxcnc-q...atics?start=0#210809

Here is the sim config folder if you want to browse:

I did manage to flip g-code using Ge.py but in axis gui and still didn't make it to do the work automatically.

Your idea sounds easier for me. Not sure how will manage complex g-codes.
Found one post that goes like this: "...there may be arcs in the code that include movement along the Z axis, and then, if there is one along the mirroring axis, everything turns into a mess. As an output, then you should apply mirroring along another axis and then in the code rotate the axes by 180 degrees + shift the coordinates. "

With switchable kinematics the gcode is not changed at all. In your case its just the direction of the x axis that is (mathematically) flipped. It's the most trivial change between two kinematic models since it just inserts a minus into an equation.
Your regular default kinematic that you use now is a righthanded cartesian system for the flipped second kinematic it's changed into a lefthanded cartesian system (ie x axis inverted in your case).

So I don't think you should run into problems using any gcode that runs on your regular setup. In fact I would be more skeptical using an external application like grecode that changes the actual gcode back and forth a number of times.

Note that switching kinematics _will_ change a righthanded helical tool plunge into a lefthanded one. Thus it will change a conventional circle milling operation into a climbing milling operation.

If you're uncertain as to what could happen to particular GCODEs I would encourage you to install the switch kins branch from above and copy my sim folder into the /configs/sim/axis/vismach folder. The simulation can then be chosen from the startup window of linux cnc and you can then load any GCODE you like.