Jens, By default, pythonOCC exports STEP files using the AP214 schema. After you export the step file with Abaqus, the schema used is not the AP214 anymore but the AP203 : when dealing with standard files import/export issues, the problems may arise from the exporter and/or the importer, and it's not obvious to find out the responsible of the issue. Using the same STEP schema for import/export ensures the semantics consistency of the exchange process. Is there any option, in Abaqus, to use the AP214 instead of the AP203?
If you use the latest pythonOCC release (0.4), you can't change the default behavior (AP214) of the STEP exporter. However, the latest revision of the svn trunk makes it possible (see this discussion: http://www.mail-archive.com/pythonocc-users@gna.org/msg01462.html). At last, I'm not sure whether or not the exchanges based upon the IGES standard are still a good way to proceed. I would say 'no', since the STEP scope is much wider than the IGES one (which is only intended to geometry) and, as a consequence, more suitable for industrial processes. Regards, Thomas 2010/10/11 Jens Cornelis <jens.corne...@iwm.fraunhofer.de> > Hi Jelle, hi Thomas, > > btw: exporting the same shape to a IGES file and imorting in Abaqus > works fine. Abaqus imports it as a solid, just as expected. The issue is > only when exporting to STEP (the preferred file format.) > > Maybe this information is somehow interesting for you? > > Cheers > > JC > > _______________________________________________ > Pythonocc-users mailing list > Pythonocc-users@gna.org > https://mail.gna.org/listinfo/pythonocc-users >
_______________________________________________ Pythonocc-users mailing list Pythonocc-users@gna.org https://mail.gna.org/listinfo/pythonocc-users
