how to work in multi-user environment on the same project

[The_Matrix]

Okay, a little dangerous, no?!? .
if the aid is managed by a few people ok, but with large assemblies managed by various competence center... help

I didn't understand your reasoning. . .
What is dangerous with wave among the things I wrote to you?

 

[stef_design]

I didn't understand your reasoning. . .
What is dangerous with wave among the things I wrote to you?

in general it is dangerous to lean on another geometry for the construction of a part. If I need references from another geometry, I will cover them and then I will scold them from the reference part, requoting them in the new one.
If I didn't understand the wave module badly, it's for me to create an association between parts or geometries in general.

 

[cacciatorino]

in general it is dangerous to lean on another geometry for the construction of a part. If I need references from another geometry, I will cover them and then I will scold them from the reference part, requoting them in the new one.
If I didn't understand the wave module badly, it's for me to create an association between parts or geometries in general.

I imagine there will be a "project" that has the keys to lock/unlock the father part, I don't think that the fiat to say the first designer who gets up in the morning can change the shape of the fanalino if not after twelve meetings and 14 transoceanic teleconferences.

 

[ceschi1959]

in general it is dangerous to lean on another geometry for the construction of a part.

recovering the_matrix: why dangerous?
if you know the operation of the process there are no particular problems.
It is evident that it is necessary to establish a priori (it is not necessary but useful) the flow of information, not to create, for example, cyclical occasions.
Suppose you work in excel. What are you doing? do you copy the result of a box (and then undelete) to make other calculations or associates? philosophy is similar.

If I need references from another geometry, I will cover them and then I will scold them from the reference part, requoting them in the new one. .

How do you do with a surface associated with a set of sketch curves and more?

If I didn't understand the wave module badly, it's for me to create an association between parts or geometries in general.

Yes and you can also quite well!:finger:

 

[stef_design]

I imagine there will be a "project" that has the keys to lock/unlock the father part, I don't think that the fiat to say the first designer who gets up in the morning can change the shape of the fanalino if not after twelve meetings and 14 transoceanic teleconferences.

I wouldn't put my hand on fire... I assure you that the only keys that the project manager has are those of his car. I assure you:

 

[stef_design]

recovering the_matrix: why dangerous?
if you know the operation of the process there are no particular problems.
It is evident that it is necessary to establish a priori (it is not necessary but useful) the flow of information, not to create, for example, cyclical occasions.
Suppose you work in excel. What are you doing? do you copy the result of a box (and then undelete) to make other calculations or associates? philosophy is similar.

It seems to me that in another discussion you had posted images of a recessed electrodomestic all parameterized like: If I change a comma, everything updates.
Here, that system in a medium-big company is the fastest way to get you fired!
until you work in two or three ok, but in + people creates a total mess.
We put that one day your project is entrusted to another, this must lose a week to understand how the hell you parameterized it.
I repeat, I do not know the wave method, but if it is a simple 'copy entity from other parts' it works well if you work in small competence center.
Hi.

 

[axa]

I repeat, I do not know the wave method, but if it is a simple 'copy entity from other parts' it works well if you work in small competence center.
Hi.

to make it short, wave is a feature that allows you to connect geometry (points, edge, sketch, curves, faces, regions of faces, solids, planes etc.) between different files, both in an associative and non-associative manner.
therefore lies at the "feel" of those who use it to decide if and how messing up.
a beautiful thing is that you can link the edges of a face or surface to make an extrusion (or whatever else comes to mind) and then tell him to convert these edges connected to an independent sketch that can then be modified for his own facts (all quoted:biggrin.
then you can do other games x connect "numbers" between different files, for example use the "interpart expressions", or say something like:
thickness="pincopalla.prt": :spessore
or you can copy-paste between different file features and tell them if they need to be connected or not.
in general you can do everything and the opposite of everything, the problem at the end is, as you pointed out, understand whether it is beneficial according to the type of product you plan and the environment you work in.
the "wave control" speech that mentioned matrix instead is a module contained in the more expensive bundles and allows you to manage all the links in a more controlled way, I didn't have to use it more than so, a nice thing is the "interpart link browser" that graphically allows you to see the cases that you created at the level of geometry links and expressions without having to do a research work model sherlock holmes.

 

[stef_design]

to make it short, wave is a feature that allows you to connect geometry (points, edge, sketch, curves, faces, regions of faces, solids, planes etc.) between different files, both in an associative and non-associative manner.
therefore lies at the "feel" of those who use it to decide if and how messing up.
a beautiful thing is that you can link the edges of a face or surface to make an extrusion (or whatever else comes to mind) and then tell him to convert these edges connected to an independent sketch that can then be modified for his own facts (all quoted:biggrin.
then you can do other games x connect "numbers" between different files, for example use the "interpart expressions", or say something like:
thickness="pincopalla.prt": :spessore
or you can copy-paste between different file features and tell them if they need to be connected or not.
in general you can do everything and the opposite of everything, the problem at the end is, as you pointed out, understand whether it is beneficial according to the type of product you plan and the environment you work in.
the "wave control" speech that mentioned matrix instead is a module contained in the more expensive bundles and allows you to manage all the links in a more controlled way, I didn't have to use it more than so, a nice thing is the "interpart link browser" that graphically allows you to see the cases that you created at the level of geometry links and expressions without having to do a research work model sherlock holmes.

thanks axa, you were very kind:finger:

 

[axa]

thanks axa, you were very kind:finger:

de nada!
otherwise what would the forum serve?:finger:

Incidentally, I am a wave potato, only that when I used it to "work" and not to fuck as I normally did in other areas, I managed to create some cases at the level of circular references that forced me more than once to brekkare the links in order to move forward. This obviously because I didn't have the time to plan the work but I had to grind pieces, so what you pointed out is correct not only in the multihead field but also single-headed.

Fortunately, then there was "san synchronous", at the time known "san direct modeling" (although he was a minor saint) who always pulled me out of the mess in acceptable times, along with many other beautiful nx features.

the beauty of explicit! ! ! !

 

[lostico]

de nada!
otherwise what would the forum serve?:finger:

Incidentally, I am a wave potato, only that when I used it to "work" and not to fuck as I normally did in other areas, I managed to create some cases at the level of circular references that forced me more than once to brekkare the links in order to move forward. This obviously because I didn't have the time to plan the work but I had to grind pieces, so what you pointed out is correct not only in the multihead field but also single-headed.

Fortunately, then there was "san synchronous", at the time known "san direct modeling" (although he was a minor saint) who always pulled me out of the mess in acceptable times, along with many other beautiful nx features.

the beauty of explicit! ! ! !

Straquoto!
we work like this:
the project in its embryonic phase was born parametric, and above all linked with the wave. In this way you can control the variables that for example determine the bulk ingots.
then once you approve, and start with the publication in tc (spec, etc.) and then the production, then remove the various links.
this to ensure the possible reuse of components also on other future projects.
in our case we maintain only a couple of connected expressions (the so-called interpart variables), because we have components that can only vary in length (special profiles) and we keep open the possibilities of carrying out checks and controls.

 

[Dade73]

to make it short, wave is a feature that allows you to connect geometry (points, edge, sketch, curves, faces, regions of faces, solids, planes etc.) between different files, both in an associative and non-associative manner.
therefore lies at the "feel" of those who use it to decide if and how messing up.
a beautiful thing is that you can link the edges of a face or surface to make an extrusion (or whatever else comes to mind) and then tell him to convert these edges connected to an independent sketch that can then be modified for his own facts (all quoted:biggrin.
then you can do other games x connect "numbers" between different files, for example use the "interpart expressions", or say something like:
thickness="pincopalla.prt": :spessore
or you can copy-paste between different file features and tell them if they need to be connected or not.
in general you can do everything and the opposite of everything, the problem at the end is, as you pointed out, understand whether it is beneficial according to the type of product you plan and the environment you work in.
the "wave control" speech that mentioned matrix instead is a module contained in the more expensive bundles and allows you to manage all the links in a more controlled way, I didn't have to use it more than so, a nice thing is the "interpart link browser" that graphically allows you to see the cases that you created at the level of geometry links and expressions without having to do a research work model sherlock holmes.

I understand the wave at last, thank you very much. but I read that there is also the interpart link, what difference is between the two?

 

[ceschi1959]

It seems to me that in another discussion you had posted images of a recessed electrodomestic all parameterized like: If I change a comma, everything updates.
Here, that system in a medium-big company is the fastest way to get you fired!

As you have seen in the lostic post, you work so in the design phase produced (and I don't think that in your company they have ever fired anyone for this). Then, if you want, you untie everything.

until you work in two or three ok, but in + people creates a total mess.
We put that one day your project is entrusted to another, this must lose a week to understand how the hell you parameterized it.
I repeat, I do not know the wave method, but if it is a simple 'copy entity from other parts' it works well if you work in small competence center.
Hi.

is not a simple copy entity, I had made you the example of excel (cells connected to others), if I take in hand a worksheet made by another I have to lose a week to understand how links are made? according to your reasoning it would be better that I found a sheet with simple numbers and not formulas.


One thing though I would like to ask who uses other cads: how do you do it? When the wave was introduced in ug (version 14, prehistory) I was told that it was for years.