On 25 July 2018 at 05:07, Valerio Bellizzomi <vale...@selnet.org> wrote:
> Well then, PyCAM has rough and fine operations. I am not 100% sure that that is the same thing. For example previous finish operations with a different cutter might leave large lumps of finished surface above the height of the current operation. Conventional algorithms for an operation that works on _different_ surfaces would either retract to a safe height or crash through these. (the former is obviously to be preferred). Proper rest-machining can weave a path between these on point-to-point moves. This is much easier to do when the CAM is integrated to the CAD. in effect the previous operations become "Cut" operations in CAD and the resulting remnant is a true representation of the remaining stock. Unless the CAM system also becomes a 3D CAD system which can operate on solid bodies as well as interpret them this is hard to do properly. -- 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 ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Emc-users mailing list Emc-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-users
