The need for a default assembly workbench
Forum rules
Be nice to others! Read the FreeCAD code of conduct!
Be nice to others! Read the FreeCAD code of conduct!
- wandererfan
- Veteran
- Posts: 6326
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: The need for a default assembly workbench
Using it as a guideline will not be a good thing?wandererfan wrote: ↑Sun Mar 26, 2023 2:10 pm Everything you ever wanted to know about a data model for assemblies.
Maybe adopting a similar terminology too?
NIST has a decent reputation to be trusted for some insight.
Regards
Carlo D.
GitHub page: https://github.com/onekk/freecad-doc.
- In deep articles on FreeCAD.
- Learning how to model with scripting.
- Various other stuffs.
Blog: https://okkmkblog.wordpress.com/
- In deep articles on FreeCAD.
- Learning how to model with scripting.
- Various other stuffs.
Blog: https://okkmkblog.wordpress.com/
- wandererfan
- Veteran
- Posts: 6326
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: The need for a default assembly workbench
I'm still working my way through the document, but we might translate a subset of OAM terminology into FreeCAD terminology as:
OAM Artifact = FC Document(?) (Here Artifact is representing Product)
OAM Assembly = FC App::Part
OAM Part = FC PartDesign::Body and Part::Feature(?)
OAM Assembly Feature = FC Constraint(?) and FC LCS(?)
OAM Artifact is a bit of a catch-all. Product, Assembly and Part are all Artifacts. We might call this a base class.
"An Assembly is decomposed into sub-assemblies and parts. A Part is the lowest level component which cannot be further decomposed. The diagram shows that an assembly or a subassembly is made up of at least two parts."
"Assembly feature is defined as an element to specify the relationships between a pair of assembled components. For example, a hole and a cylinder are typical assembly features, which represent the physical connections between a bearing part and a shaft part. The assembly feature association representation is an aggregation of parametric assembly constraints, a kinematic pair, and/or a relative motion between assembly features as shown in Figure 9."
Re: The need for a default assembly workbench
Thanks and yes, this was for a long time my argument and critique on the different assembly wb developments, one has to first establish a clear assembly/part tree structure before doing anything else. Nobody is denying the usefulness or the need of constraints and solvers (more on this in a different post later), I am sure Zolko would also be more then happy to add them to his Asm4, but they by themselves don't give you an assembly. Here is the structure done with just the existing Part containers (so not even using any geometry or LCS or even no Asm4). And all the arguing on solvers, licenses, types of constraints, even comparing of the different Asm WB's are basically meaningless if we don't first understand and agree on this.wandererfan wrote: ↑Sun Mar 26, 2023 2:10 pm Everything you ever wanted to know about a data model for assemblies.
Last edited by saso on Tue Mar 28, 2023 11:27 am, edited 6 times in total.
- wandererfan
- Veteran
- Posts: 6326
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: The need for a default assembly workbench
Any default assembly workbench should produce an "output" that is suitable for use in subsequent operations.
Based on limited exposure, Asm4 satisfies this requirement, A2+ may not. I can't speak to Asm3.
Based on limited exposure, Asm4 satisfies this requirement, A2+ may not. I can't speak to Asm3.
- wandererfan
- Veteran
- Posts: 6326
- Joined: Tue Nov 06, 2012 5:42 pm
- Contact:
Re: The need for a default assembly workbench
That diagram is actually from "the Japanese National Committee (JNC) proposal for a STEP assembly model of products", not the OAM per se, but your point is still absolutely valid.
Re: The need for a default assembly workbench
And the important thing to understand here is that this structure by itself should actually be quite simple and in a way rigid, because it is then very easy to build BOMs from it and do proper STEP imports/exports of assemblies.wandererfan wrote: ↑Sun Mar 26, 2023 3:14 pm That diagram is actually from "the Japanese National Committee (JNC) proposal for a STEP assembly model of products", not the OAM per se, but your point is still absolutely valid.
Last edited by saso on Tue Mar 28, 2023 11:30 am, edited 2 times in total.
Re: The need for a default assembly workbench
Much has been said about this already in the past, and I would not want to start this debate again in this topic, but basically the implementation of Bodies in FC is just wrong (at least that is my view). They act as both a body and a part at the same time and this is just wrong and bad.adrianinsaval wrote: ↑Sat Mar 25, 2023 5:04 pm If I'm not mistaken this isn't necessary for bodies as they will have the same structure as a Part when exported, right?
- adrianinsaval
- Veteran
- Posts: 5553
- Joined: Thu Apr 05, 2018 5:15 pm
Re: The need for a default assembly workbench
DISCLAIMER: I have not read the document, my opinions are based solely on what has been said in this thread and my previous knowledge of other CAD systems.
I'm not sure fi this is correct, from what I understood earlier I think it's not desired to have standalone Part::Feature objects directly under the assembly container, so instead this would be App:Part too.
I think it means much more than that, in other CAD systems you do some operations in the assembly, like mirroring, pocketing and can't remember what else. I think this has been mentioned before here too.OAM Assembly Feature = FC Constraint(?) and FC LCS(?)
Re: The need for a default assembly workbench
ASM3 can handle assemblies and subassemblies as well, but uses its own Assembly container instead of the FC App::Part.wandererfan wrote: ↑Sun Mar 26, 2023 3:07 pm Based on limited exposure, Asm4 satisfies this requirement, A2+ may not. I can't speak to Asm3.
It works well with App::Links and PD bodies at least.