Ticket #3834 - Loss of coordinate systems during .stp (AP214) import/export
Forum rules
and Helpful information
and Helpful information
IMPORTANT: Please click here and read this first, before asking for help
Also, be nice to others! Read the FreeCAD code of conduct!
Also, be nice to others! Read the FreeCAD code of conduct!
Re: Loss of coordinate systems during .stp (AP214) import/export
The LCS should be then moved inside a Part
It would be nice to have it in an Import/Export STEP code ...Re: Loss of coordinate systems during .stp (AP214) import/export
Great, i really appreciate your work.
I know this is not make a wish, but if the implementation is possible,
these Features wouldt be awesome too.
Add, move, orient, copy, name/rename and of course export these datum planes to a Step AP214.
For re/orientation i tried this -> plm.Placement.Rotation=App.Rotation(0,90,0,0)
and it worked so far.
Again, thank you!
I know this is not make a wish, but if the implementation is possible,
these Features wouldt be awesome too.
Add, move, orient, copy, name/rename and of course export these datum planes to a Step AP214.
For re/orientation i tried this -> plm.Placement.Rotation=App.Rotation(0,90,0,0)
and it worked so far.
Again, thank you!
Re: Loss of coordinate systems during .stp (AP214) import/export
Hello,
any News on this issue ?
any News on this issue ?
Re: Loss of coordinate systems during .stp (AP214) import/export
Hii wmayer,
would it be possible to switch from "App::Placement" to "PartDesign::CoordinateSystem"?
That would allow to work with assembly 4 approach, which is using "PartDesign::CoordinateSystem" to make assemblies...
Code: Select all
plm=App.ActiveDocument.addObject("PartDesign::CoordinateSystem","CSW")
plm.Placement.Base=App.Vector(31.8244952147467,33.7921260930763,-162.824495214746)
plm=App.ActiveDocument.addObject("PartDesign::CoordinateSystem","MCS")
plm.Placement.Base=App.Vector(15.925,31.8500000000002,-82.48178698)
plm=App.ActiveDocument.addObject("PartDesign::CoordinateSystem","PCS")
plm.Placement.Base=App.Vector(7.105427357601E-15,1.04449782156735E-12,1.4210854715202E-13)
Moreover would it be possible to consider both import and export this LCS within STP?
Thx in advance
Maurice -
Re: Loss of coordinate systems during .stp (AP214) import/export
Some months ago someone with a commercial CAD system already asked for this feature. It's listed in the bug tracker.Moreover would it be possible to consider both import and export this LCS within STP?
Re: Loss of coordinate systems during .stp (AP214) import/export
Hi, any Updates on this issue?
Kind regards
Kind regards
-
- Veteran
- Posts: 2189
- Joined: Tue Jan 03, 2017 10:55 am
Re: Loss of coordinate systems during .stp (AP214) import/export
I browsed through the OCC source code about this. I think it is quite doable. I'll add that feature once I got time.
Re: Ticket #3834 - Loss of coordinate systems during .stp (AP214) import/export
Added ticket # to thread title and assigned ticket to @realthunder
Alone you go faster. Together we go farther
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
Please mark thread [Solved]
Want to contribute back to FC? Checkout:
'good first issues' | Open TODOs and FIXMEs | How to Help FreeCAD | How to report Bugs
-
- Veteran
- Posts: 2189
- Joined: Tue Jan 03, 2017 10:55 am
Re: Ticket #3834 - Loss of coordinate systems during .stp (AP214) import/export
Copy my response from the other thread.
The STEP Axis information is part of the GD&T section. I did some research on how various other CAD handles this. I think FC is almost a blank in this area at the moment. Someone did a GD&T workbench some while ago based on Draft dimension, but was abandoned. And based on the look of the code, I decided not to continue the work. Instead, I plan to add basic GD&T support directly in Part workbench, maybe based on the existing Part measurement, to make them editable object and so on. But that is likely going to wait till the next release.
BTW, in case any one think its high priority and want to step in, you can checkout OCC source file XDEDRAW_GDTs.cxx, function DumpGDTs() to see how to extract various datum information from a XCAFDoc, which is what OCC imports STEP into.
The STEP Axis information is part of the GD&T section. I did some research on how various other CAD handles this. I think FC is almost a blank in this area at the moment. Someone did a GD&T workbench some while ago based on Draft dimension, but was abandoned. And based on the look of the code, I decided not to continue the work. Instead, I plan to add basic GD&T support directly in Part workbench, maybe based on the existing Part measurement, to make them editable object and so on. But that is likely going to wait till the next release.
BTW, in case any one think its high priority and want to step in, you can checkout OCC source file XDEDRAW_GDTs.cxx, function DumpGDTs() to see how to extract various datum information from a XCAFDoc, which is what OCC imports STEP into.