The problem is that Path changes custom code
Code: Select all
G53 G1 Z0
G53 G0 X0 Y0
Code: Select all
G53
G1 Z0
G0 X0 Y0
I could fix this in linuxcnc_post, but I wanted to ask how other controllers handle the "modality" of G53.
Code: Select all
G53 G1 Z0
G53 G0 X0 Y0
Code: Select all
G53
G1 Z0
G0 X0 Y0
I use it sometimes to move the head out of the way, regardless of current coordinate system/fixture, tool compensation and so on.Konstantin wrote: ↑Mon May 07, 2018 5:40 am G53 is very specific coordinate system. On some controllers you can't even call it in regular program. Can someone tell me, why you use it? How it is used in LinuxCNC?
Hm, it's a very specific use case. It might be specific for every machine, I don't think it's a good idea to add this for everyone. By the way, how would you use it in FreeCAD at all? It has only machining paths, how you will generate your G53 moves (which as you say will move "regardless of current coordinate system/fixture, tool compensation and so on")? Make a special path by hand? You use it instead of G28 or G30? I don't get it. Maybe you are making something very specific, without example I can't understand it. But I think it's a better idea to make your local modification of linuxcnc postprocessor.
As I said, I'm using a "custom" operation to move the head out of the way (for refixturing etc...). This "custom" operation is mangled because FreeCAD Path does not copy the custom G-Code verbatim but interprets it and outputs it's own understanding, and that includes treating G53 as modal. Which is wrong in the case of linuxcnc and possibly other controllers.Konstantin wrote: ↑Wed May 09, 2018 7:08 amHm, it's a very specific use case. It might be specific for every machine, I don't think it's a good idea to add this for everyone. By the way, how would you use it in FreeCAD at all? It has only machining paths, how you will generate your G53 moves (which as you say will move "regardless of current coordinate system/fixture, tool compensation and so on")? Make a special path by hand? You use it instead of G28 or G30? I don't get it. Maybe you are making something very specific, without example I can't understand it. But I think it's a better idea to make your local modification of linuxcnc postprocessor.
I personally don't think something like that is needed. Custom toolchange actions can be integrated into linuxcnc.Konstantin wrote: ↑Wed May 09, 2018 7:08 am For example, add an argument "--use_toolchange_file=/my/precious/hardcoded/toolchange/file", and if it is set, use users file with needed operations.
Fix it for Linuxcnc. If it differs for other posts, it might have to be modified on a case by case basis. Doesn't sound like it's widely used though.