raw-finished management

[crozza]

Hello

I would like to expose you a doubt/problem

I have a roller made up of a metal core and a plastic sleeve:

the sleeve consists of two hubs, a metallic reinforcement and a plastic sleeve/tube

the hubs have a pre-finition (dis. 1.04.60.957/2) and after they are assembled they will be subjected to other processing (s. 1.34.65.602)

How do you manage this situation?
Is there a way to give the same design/code two different "views"? I better explain, that I can choose whether to see it worked or raw, and when I put it on the table I can choose whether to put it raw or worked (as I did in the 2d drafting)

I now create the particular so:
together called a composed of:

soul (not designed in examples) bplastic handle c composed of: worked hubs d + metal reinforcement e + tube fbut the hub will exist also not worked called gBut d e g They will never be bound together.

I hope I explained.

 

[Kaji]

I am sorry, but I understood little, but I still try to give some information on the subject because the management of crude, semi-finished and finished is a situation that happens often.
when I am facing a welded assembly and then worked drawing in 3d the worked, then I cover it at a level, I move all the parts into a container that in turn I put inside the worked axieme.
cancel the shared at a level of all the interested parties from the processing within the container and "cut" the faces that represent the processing, so I get a group that represents the finished axieme within which inside a level there will be all the details and the container that represents the crude and the latter within it will have all the raw details.
then with management parts then choose what to show or not, among other there is also the option to add containers or remove containers just in the management parts.
as regards the code I use the pdm that manages part, document 3d and document 2d; what ends in distinction etc is the part (and therefore part code) that can be very common to the crude and to the hard work that they have different code_document, code_document that does not appear in separate.
among other things is a fairly common procedure in fact the pdm software I use, i.e. pe3, gives me the possibility to save the 3d documents as "variant" of the same part

 

[cacciatorino]

when I am facing a welded assembly and then worked drawing in 3d the worked, then I cover it at a level, I move all the parts into a container that in turn I put inside the worked axieme.

I feel that the workflow to follow is what you indicate.

Have you ever tried to use versions? I have the doubt that maybe they could be suitable for the purpose, but the manual is quite smoky about the purpose of this function.

 

[crozza]

I feel that the workflow to follow is what you indicate.

Have you ever tried to use versions? I have the doubt that maybe they could be suitable for the purpose, but the manual is quite smoky about the purpose of this function.

I honestly don't know how to use them, as I don't know how to use the containers, I'll have to do a "study"

where are the containers used?
and the versions?

 

[crozza]

I honestly don't know how to use them, as I don't know how to use the containers, I'll have to do a "study"

where are the containers used?
and the versions?

Excuse me if I raise the question.

 

[cacciatorino]

Excuse me if I raise the question.

I attach an example of a welded-finished. you will see that the worked contains a container, and inside this container you will find the parts of the welded.

then in the table the system by default shows you the first level axieme, but you can create another view (even on another design if you want) where you only see the container.

p.s. the file is made with modeling 18.1, I hope you can open it.

 

[crozza]

I attach an example of a welded-finished. you will see that the worked contains a container, and inside this container you will find the parts of the welded.

then in the table the system by default shows you the first level axieme, but you can create another view (even on another design if you want) where you only see the container.

p.s. the file is made with modeling 18.1, I hope you can open it.

Thank you!

Now I have made an idea about their use.

while the versions escape my sense, I read a little about the help but nisba.

 

[Kaji]

Thank you!

Now I have made an idea about their use.

while the versions escape my sense, I read a little about the help but nisba.

in fact I use the versions only when I have to deal with two different revisions of the same piece then contemporary load the revision to and the revision b and I see the differences; But this thing manages me the pdm, in fact when I modify a particular or a set that has already been produced, at the time of the rescue I choose "new" revision and he automatically creates a "version" different of the same solid, so that later I can find in the pdm is the revision to that the revision b and upload them together to see its differences

 

[stefanoparducci]

Good morning.
the use of modeling versions is very useful to quickly replace within a project a component with a more updated one.

the mode of use is very simple.

load the group that contains the component to update.
Load the updated component by activating the charge option as vers. part/grp . Obviously it must be the same modified component (to mean the two versions if the load together must be shared)

at that point the component I uploaded as version will have a marroncina icon with a lock.

in the version menu, choose to replace with version and click the original piece and the revised piece.
by pressing ok I will find in the group mounted the revised piece.

for those who have pdm this feature is managed by pdm versions and therefore it is only useful for those who save on files.

greetings, stefano

 

[ansyolitico]

Hi.
I read yours and I have two questions
If I have understood correctly it should be so
Ma
-- --mazza_lavarota
-----|-manico_finito
-----|-ferro_finito
--
-----|-manico_grezzo
-----|-ferro_grezzo

the crude is the copy at 1 level of the finished (in this case you could just make a copy) but when I make the table how do I show only the finished or the crude?
and in the distinct how do I make the pieces appear only once?

ps. are without pdm

 

[Kaji]

The crude is the one-tier copy, but when I make the table, how do I show only the finished or the crude?
and in the distinct how do I make the pieces appear only once?

no, if you make a copy, you actually have two parallel and in fact independent bats instead of one; So I think the possible roads are two:
- create a container where you put all the raw parts that are copies of the finished parts
- or by means of the fine-stock command within each finite part, put its raw part.In this way your bat is unique, it is weighed only once, it appears once when you make the distinction of the parent group to which it belongs and also visually you see only the finite and not even the crude that overlaps and interferes with the adjacent parts.
when you make the drawing of the bat then annotation by default shows you only the finished parts and then you can immediately make the drawing of the worked, then to make the drawing of the crude enough that in managing parts you remove everything and then add containers and see only the raw parts.

As for the distinguished at the upper level it works all well because it is contemplated only the finite bat while the rough bat being inside is not seen, while in regards to the distinct of the bat in itself I can not say anything because I do not know how to handle the codes and distinguishes without pdm, indeed in my specific case when I had pe3 I could brutally give the same code to rough and finished and the pdm even if I generally prefer the first method, perhaps because I use it for years before there was the fine-stock coma and in addition you can automatically manage multiple different finite groups that have the same crude.