Burst of a Burst, the return

dbauguion · March 4, 2015, 1:37pm

Hello

I have a problem with the explosion:

I made the exploded of a subassembly, friends when it was time to reuse it in the final assembly, Solidworks refuses to take the exploded of the subassembly into account: "None of the selected subassemblies has an exploded view to reuse."

Thank you in advance for your answers

pl · March 4, 2015, 1:43pm

Hello, is it the active configuration that has the exploded view? The configuration of the subassembly in the parent assembly must have an exploded view, it does not work if the exploded one is for another configuration.

dbauguion · March 4, 2015, 1:44pm

Yes, absolutely.

pl · March 4, 2015, 1:46pm

Is the subset well resolved? Isn't it a complex assembly or hose problem?

dbauguion · March 4, 2015, 1:48pm

Yes, everything is good at this level too

gt22 · March 4, 2015, 1:55pm

Using the exploded view of a subassembly

If a subassembly already includes an exploded view, you can reuse that view in a top-level assembly.

To use the exploded view of a subassembly in an assembly :

Select a subassembly for which you have already defined an exploded view.
In the PropertyManager, click Reuse Subassembly Explode.
The subassembly is exploded in the graphics area, and the steps in the corresponding exploded view are listed underExplode Steps.

@+

dbauguion · March 4, 2015, 1:57pm

I know where you got this answer but the help of solidworks doesn't help solve my problem (yes I looked before asking the question ^^")

gt22 · March 4, 2015, 2:00pm

what version of SW are you under

@+

dbauguion · March 4, 2015, 2:01pm

Premium 2013 x64 SP0.0

gt22 · March 4, 2015, 2:03pm

Your subset (exploded view) has its proper name?

and registered as such?

@+

dbauguion · March 4, 2015, 2:04pm

It is aptly named as Éclaté

gt22 · March 4, 2015, 2:04pm

There are a lot of bugs on all SP0s

To be avoided as soon as possible, pass mini sp 1

@+ ;-)

dbauguion · March 4, 2015, 2:06pm

erf, I have to see this with my computer scientist =/

Is there no other solution?

opiep27 · March 4, 2015, 2:30pm

And by testing on a new assembly just to see if the sub-assembly breaks up well this time?

dbauguion · March 4, 2015, 2:42pm

Well I just tested it does the same, so the error is either software or human.

pl · March 4, 2015, 2:50pm

To find out if the problem is with the workstation configuration, see this tutorial to reset SolidWorks:

http://www.lynkoa.com/tutos/3d/reinitialiser-les-parametres-solidworks

opiep27 · March 4, 2015, 2:51pm

And when you test with another subassembly, there is no pb?

Otherwise we come back to pl's answer to check the confs and the bursts...

Or restart everything.

Or throw everything out the window to make a nice burst!!

gt22 · March 4, 2015, 2:58pm

your sub-assembly which is in fact an assembly

that you have registered (assembled)) with his proper name

and that you have recorded (exploded) with a diff name

If you close your assembly (bursts) and reopen it, what happens?

@+

dbauguion · March 4, 2015, 3:04pm

absolutely nothing, I see with the reset of the software

gt22 · March 4, 2015, 3:16pm

do you see it burst or not