![]() ![]() ![]() I click on "create job", select the cube from dropdown menu and get path job. so i click part workbench, create cube and go back to path workbench. I know has been looking into crashes related to the simulator. Is this something you'd be interested in working on?Īlso, in some cases the simulator currently crashes for me - actually, FreeCAD segfaults. We can leave the 'example_pre' bare-bones importer untouched and create a new one that does more. The nice thing is that these can live side-by-side. Import is done with a 'pre-processor' script which is very similar to the post processors. Fortunately, Path as designed to accommodate this. The bottom line is that we need a much more sophisticated importer. What do we do if there's a tool changes to tool numbers that don't exist in the tool table? What if there are tool changes in the imported gcode? Do we create multiple 'customs' and Tool Controllers? As you noted, it doesn't have a tool controller and it needs one. The 'Custom' object was only meant to insert a few commands into a job. I think imported code should become a 'custom' operation in the tree. ![]() To work at all, imported code has to get into a Job and have a tool controller. There are several things that need to happen to make this work even a little bit and to make it work well gets tricky fast.Īs you found, importing a gcode file creates a Path object in the tree but does not add it to any job. It's funny you mention this as I started looking into it last week. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |