I would like to see something placed at the top level, right under the Help section "FreeCADLink" and then a couple sub groups "Real problems" and "All other". Isn't there some way we can recognize realthunders work and get it on the forum in a major way so we can see how it compares to Std-FreeCAD. I have been here (on the forum) for a couple years and haven't used asm3 mostly because it was moving so fast that I didn't trust it on designs, but it appears that maybe that's changed and it has settled down. To start with could we agree that assembl圓 (asm3) has taken FreeCAD to another level, it appears there are big improvements in file structure, topological error handling, linkstage, multi-object bodies, tree options, and I'm sure more that I haven't seen yet? ![]() I was kind of hoping we could find some middle ground here on the forum. In PartDesign typically you start with a planar sketch that is then used to create a solid object by extrusion PAD), revolution or other operations.I know there are some strong opinions about realthunders fork of FreeCAD but that's not my target, but it is open discussion after all. Part is mostly based on solid primitives (Cube, Sphere, Cone.). The main difference is the kind of design flow. Part and PartDesign have similar names and are both aimed to the creation of solid objects. Sketch WB is also used very much but usually I call it from the PartDesign WB. The most important WBs are PartDesign and Part. There are several tutorials on the net (also on youtube) about FreeCAD usage.įC is composed of several WBs (Work Benches) and you may switch between them with a start menu near the upper left corner. I was able to write this script only thanks to the help of Realthunder which has been very helpful (see ). Unfortunately the python interface is not well documented. Regarding the complexity of FreeCAD I may understand the difficulties but I think it is better to start with the GUI. If you open the "test_file.dxf" with klayout you will find a single line on that layer but it is not written in "test_case_SPLIT_1.dxf". I forgot to say but I have already put this script into the git repository īut I think that only you may tell why the file "test_case_SPLIT_1.dxf" (written for layer 61/0 of file test_file.dxf at line 127 of the script) is void. Sketches associated with other layers which contain polygons (instead of lines) are OK and FC is able to use this kind of thanks for your interest. This file should contain a single line generated by the path but when I open it I can not find anything. At that point the script will have written a file named "test_case_SPLIT_1.dxf". You may continue a few times until you find opi='vsurf'. The script will stop at line 139 where there is pdb.set_trace(). If you have installed the RT branch of FreeCAD ( ) you may check the annexed script and test case by giving the command: layout2fc -stack UMS_PH10.stack test_case.dxf I wanted to make a single face extruded from a line defined by a klayout path with 0 thickness. The last line should produce a vertical surface (instead of a solid object) using the sketch profile stored in layer 61/0. The order is important for the ins (insert) operation which consists of a solid extrusion plus a cut of all previously created solids which intersect the new one. Means that layer 49/0 defines a vertical solid extrusion from h=0 to h=70mu, the last number (before the comment) refers to the ordering of the related CAD operation. The first line with scale is used to convert FreeCAD unit (mm) into micron. The new format is better explained in following lines taken from annexed file UMS_PH10.stack scale: 0.001 ![]() In the previous version I was using datatype to define the insertion order but I think that it is better to have a separate data field. To do that I need to extend also the stack format adding two columns holding (for each layer) the kind of operation and the insertion order. ![]() Hi Matthias, I would like to extend a little bit the capabilities of my script.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |