GRBL new post processor with drill cycles G81..G83

[Gauthier]

Hi all,

Because of GRBL limits (https://github.com/gnea/grbl/wiki#limitations-by-design), and that not all GCode sender program do the translation, I added the translation code between G81, G82 & G83 to the G0, G1 & G4 corresponding moves & pause.

Added 2 new options to the grbl_post.py :
--translate_drill : translate drill cycles G81, G82 & G83 in G0/G1 movements (default)
--no-translate_drill : don't translate drill cycles G81, G82 & G83 in G0/G1 movements

This new GRBL post-processor is attached here, any test and comments are welcomes

@++;
Gauthier.

[crc1021]

I don't have much to say other than it was exactly what I was looking for and it worked great. Thanks.

Eric

[georgevt]

Thanks for the fix. Are there any plans to add this to the master branch? I noticed that the latest grbl_post.py has a different precision value (3 vs 4). And there might be other changes. It would be nice if your fix was merged into master branch so that other changes get automatically picked up.

[Gauthier]

Thanks for the feedback,

In fact, only a few small changes have been made since my version:
- Update of the default value of the precision from 3 to 4 digits, the operations remains the same. You can use the "--precision" option to define what you want from FreeCAD.
- The others modifications concern the necessary corrections for the transition to Python version 3. Tey don't change the current functionalities with Python 2.x.

I will integrate these updates ASAP and then, I will propose a Pull Request.

For the moment, I'm working on a new version of GRBL working up to 5 axes on Mega 2560 with RAPMS 1.4, and a new interface for managing those 5 axes, so I do not have much time ... But I'm going to try anyway not to be too long on the post-processor.

@ ++;
Gauthier.

[herbk]

For the moment, I'm working on a new version of GRBL working up to 5 axes on Mega 2560 with RAPMS 1.4, and a new interface for managing those 5 axes, so I do not have much time ... But I'm going to try anyway not to be too long on the post-processor.

That sounds very interessting, please keep us informed about it.

[polemidis]

Can I have a hint plz on how to use the new post processor? Sorry I have no idea about python. Should I run it somehow, or can I replace the default grbl that freecad 0.17 has??

[Gauthier]

Hi,

You need to place this file (grbl_post.py) in <FreeCAD_program_path>/Mod/Path/PathScripts/post, replacing the old one or rename it.

@++;
Gauthier

Can I have a hint plz on how to use the new post processor? Sorry I have no idea about python. Should I run it somehow, or can I replace the default grbl that freecad 0.17 has??

[chrisb]

You need to place this file (grbl_post.py) in <FreeCAD_program_path>/Mod/Path/PathScripts/post, replacing the old one or rename it.

Or you put it with the same name in the user's Macro Directory.

I am a bit unhappy with this architecture, because the individual modifications prevent updates on that very post processor. I will make a proposal for 0.18 how to change this, which should take into account that the PPs are very similar.

[GeneFC]

I am a bit unhappy with this architecture, because the individual modifications prevent updates on that very post processor.

I am not disagreeing, but I cannot understand the point you are trying to make. How are updates prevented?

Gene

[chrisb]

I am a bit unhappy with this architecture, because the individual modifications prevent updates on that very post processor.

I am not disagreeing, but I cannot understand the point you are trying to make. How are updates prevented?

Rereading my post I have to confess that the statement given was very unclear . I give an example for what I actually meant: When a user wants to have a special tool change GCode in his linux_cnc he copies it and makes the changes. He either gives a new name to his personal post prcessor or he puts it in his local macro directory.
When sliptonic adds an improvement to linux_cnc it is well updated in the FreeCAD Path subdirectory, but the changes will not affect the locally modified copy.