plate development on board does not update with all new processing

[reggio]

Hi, it's an old problem that keeps creating damage

In practice, starting from parts already designed and, adding work, if in the table there is already development (flattened), sometimes the last work remains suspended and not seen in flattened view.

as the lamierist is based only on flattened, cuts and prepares a wrong piece ...

in the example below we wanted a part with holes 1,2,3,4 .. while we got "b" or the previous version.

the problem is that if you do not control one by one the tables and changes, sometimes even very small, you risk getting wrong parts to throw.
Have you ever seen such a thing? would you know how to deal with and solve?

 

[re_solidworks]

hi reggio, development is a configuration and is subject to all pros and cons of these. to be sure not to give wrong developments, when I change a sheet I proceed in 2 ways:

1- if the flat repetition has variations compared to the folded hand control
2- If there are no variants and it only has to flatten, I delete the configuration and make it regenerated through a fake table that I do not save. At this point I am sure that the flat was created from scratch from the updated situation.

I happen to make cloning of also important assemblies and when we make the tables, before opening the table, we open the part and we act on the model as mentioned.

 

[SperX]

bye, do button on b and open in place then check what is suppressed, usually in the views does not save changes if they are successive.

 

[reggio]

Hello and thank you,

the problem at the end is that "we cannot trust" of the cad without checking, and checking each sheet is expensive ... sob

 

[SperX]

Hello and thank you,

the problem at the end is that "we cannot trust" of the cad without checking, and checking each sheet is expensive ... sob

It's not expensive. It's something that needs to be done. At the end the cad does what you say to him. I prefer to recheck everything and not have 400 enclosures to rework or worse to throw. cmq if you make changes or changes to the sheets is like when you use a configuration you have to change everything.

 

[re_solidworks]

Hello and thank you,

the problem at the end is that "we cannot trust" of the cad without checking, and checking each sheet is expensive ... sob

the table will open it to check if all the odds are attached and in place. in that fringent enter the part, cancel the development configuration and make it regenerate costs a few seconds. to work well you have to learn the skills and limits of our tool and work by exploiting the first and radiating the second, that is for each program. I don't see it as a limit or cost, it's part of normal work iter.

 

[reggio]

the table you will have to open it to check if all odds are attached...

You're right.
In this case it would be interesting a macro that, at every table opening, replaces the old development with a new relative to the configuration opened at the moment ... but also so I would lose the external quotas of maximum ... in some way it touches to look at every single table

 

[re_solidworks]

You're right.
In this case it would be interesting a macro that, at every table opening, replaces the old development with a new relative to the configuration opened at the moment ... but also so I would lose the external quotas of maximum ... in some way it touches to look at every single table

when I re-create development I don't do it with the open cloned table. I open the model, eliminate the development, create a new table from the model, insert the development, close the table without saving, except the part, I open the "official" table of the part that finds the development without giving errors. with a little bit of handiness you put 30 seconds.