Since this issue is now under attention, and the G71/G72 will probably live, I have a suggestion to make it improved.
Background: Tool information is already available in the tool table. Tool radius, direction, tool front and back angle. With this information is possible to "know" the points on the toolpath where the tool can ACTUALLY REACH without damaging both the tool and the work part. This would provide a large improvement even over standard industrial controllers. Most CAM packages do this for the user, but using a cycle means that generally it is used for direct gcode input. On the image attached is my understanding of a good G71. Can this be possible to implement with the information that reaches the python remap, or this is unreachable? I understand that a lot of math is involved, and when small line or arc segments are present can represent a real challenge. Filipe Citando Filipe Tomaz <[email protected]>:
Hello, Please see attached files. Test is very simple, 3 linear movements. The G71 on most all machines take the current position (before the cycle) as the "stock". This means that if you start the cycle at X50 it is expected that the material have 50mm where the cycle will work. I believe that this approach is important as it is safe. In your implementation this is not taken in account, and you look for the maximum programmed X value as the stock (if I add a extra movement, for example to X=40 it would be ok). Also, the retract that is implemented to make the pockets are to the Xmax position that you have. I understand that it is for safety, but at the same time is seams unproductive. Image attached also, where a looong retract is shown. I also tested with compensation. I think that the compensation is not taken in account. Am I correct? I think that the G71 can machine incorrectly shapes when the tool radius compensation is needed. I normally use the back tool post, so I hope that I am not saying anything silly. Either way another fine work, thank you Andy. Filipe, EuSurplus Citando andy pugh <[email protected]>: > There are two ongoing work-streams with this:G71 as a G-Code is happening in this branch: https://github.com/LinuxCNC/linuxcnc/tree/BenPotter/G71 At the same time I am experimenting with G71 Type 11 (ie, with pockets) as a Python remap in this branch: https://github.com/LinuxCNC/linuxcnc/tree/andypugh/g71type2remap The point of the Python version is to work out the niggles in the algorithms in a situation where debugging is easier and there is no compile step. Example video: https://www.youtube.com/watch?v=DwV2cibjGmo It is nearly ready for requests to attempt to break it. -- atp "A motorcycle is a bicycle with a pandemonium attachment and is designed for the especial use of mechanical geniuses, daredevils and lunatics." — George Fitch, Atlanta Constitution Newspaper, 1916 ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing [email protected]https://lists.sourceforge.net/lists/listinfo/emc-developers
------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, SlashDot.org! http://sdm.link/slashdot
_______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
