Search the Community
Showing results for tags 'Export'.
The search index is currently processing. Current results may not be complete.
Found 7 results
dxf export (or other 2d export)
Mr. Daniel Floden posted a topic in Software ConnectionsHi, What is the most straight forward way of exporting lines (in xy-plane) to AutoCad? Regards Daniel
The attached project shows the export feature I presented at this year's User's Meeting. Its purpose is to show how to use Features to export and import custom file formats using Features. Additionally, it shows how to connect such an export to a SoftwareConnector. [update 4.0]: Please read the second post in this topic to see the improvements regarding connecting your export feature with the Software connector. The geometry is based on the "Basic Hull Model" sample. There are two FStructPanelMeshes (main and stem) that are grouped in a FPanelMeshGroup and transformed using the combination of FImagePanelMeshGroup and FScaling. Running the Feature "exporter" will export the scaled PanelMeshes to a file (see the console output for the full path). The Feature "importer" will import files of the correct format (e.g. one that was exported using the "exporter") to structured panel meshes. The "success" value that is calculated in the export Feature is added to the configuration of a SoftwareConnector, so that it is ran prior to running the external computation. [update]: In 4.0 this is no longer necessary (see next post). Notes: The export feature is written to be used within a SoftwareConnector. In order to make sure that the feature is triggered before running the computation, it takes the file path as an argument with the value set to "getInputDir()". That command yields the input directory of the currently running computation. By setting that command as an argument value, the feature becomes dependent (i.e. a "client") of the so-called PathManager. This ensures, that the export will be triggered before running a computation. If you execute the feature outside of the computation-run the exported file will not be in the correct location for your external program. [update]: In 4.0 this is no longer necessary (see next post). Using "getInputDir()" instead of "getResultsDir()" (which gets the actual working directory of the external process) will export the file to the "input" sub-directory of the computation's results directory. This is done in order to allow the feature to be used in conjunction with remote executions of computations using the SshResourceManager. [update]: In 4.0 this is no longer necessary, files referenced with a relative path are automatically written into the input directory (see next post). featureExport.fdb
Hi, for some of the everyday problems of a CAE-Modeler CAESES® / FRIENDSHIP-Framework provides many useful feature definitions. You can find all feature definitions which are shipped with CAESES® / FRIENDSHIP-Framework in the "Features" tab. You can find those of the features which are related to CAD objects like points, curves, surfaces etc. in the "CAD" tab, too. A general overview of the features can be found in the Documentation Browser in the "Features" tab. Just as an example: You want to close the end of a pipe with a lid. Instead of spending your time with modeling a lid surface by your own you can use the feature "Lid for closed surface edge" (Features > Surfaces > Misc > Lid for closed surface edge). Of course it is possible to edit a feature definition to extend the functionality to your needs. After changing the feature definition you can export it to your user directory to have it accessible in other projects as well. To get access to it: "Features > In User Directory". Cheers Matthias
Parasolid export add-on
Mr. Simone Bigalli posted a topic in Software ConnectionsHi, I have read on the forum that there is the possibility to integrate the Parasolid export option in CAESES as an additional component. How can I add it to my current version of the software? Thank you very much. Cheers. Simone
NUMECA GeomTurbo Export
Jörg posted a topic in Feature ProgrammingHi, Please find attached a feature definition that you can use for exporting blades into the geomturbo file format. Note that this export will be included in one of the next CAESES releases (menu > feature definitions > tools). If you need it right now: Just put the definition into the feature user directory (e.g. C:\Users\name\AppData\Roaming\friendship\features) to directly access it through the menu in CAESES. Cheers Joerg PS: Check also this related post for importing geomturbo files, as well as our company blog post about this topic. GeomTurboExport.fdf
IGES/IGS export settings
Mr. Harry Linskens posted a topic in Post-ProcessingHi everyone, I have a hull form in CAESES as a Brep object, which I would like to export as an IGES file. However, the program I need the IGES for has a very specific set of requirements regarding the included IGES entity types and spatial tolerance settings. Is there any way that I can modify these settings for the IGES Export in CAESES? Cheers!
Exporting sections to an ASCII file
Ms. Filipa Sanches posted a topic in Feature ProgrammingHi, I need to create a feature to export some sections of the hull form with a certain number of points. The ideal would be to import the GroupSection created outside the Feature and then process the sections and create the points that i need. I try to do this but i am not able to import the groupSection to the feature and then export to an ASCII file. Is there any way to do it? The other possibility that i tough was to generate the sections inside the feature by intersection of surfaces and then dealing with the creation of the points. The problem is that the hull form is a group of different sections and i am not able to import them to the feature and to intersect them. Is there any way to do it? Thank you soo much for the help Filipa Sanches