Assy Bubbles Incorrect on Multi Page Drawings

[DrGonzo]

Hello,

I have searched a bit and am stumped on this one, as well as my co-workers.

We are running SW2004 SP1, Office XP, Win2000 Pro.
P4 2.4 1gig Quadro4 550

Files are opened up over the network, can't do much about this one without a PDM solution. Suggestions welcome, but we share many parts between assys being used by different users simultaneously.

Now the problem:
The BOM is on the first page and bubbles on this page correspond to their item numbers correctly. Views on other pages don't correspond to the BOM on the first page, pulling numbers from thin air.

To fix this we currently insert a BOM on each page we use bubbles, and then hide it or move it off the page.

This seems unreasonable to me, but I have tried everything I can.

Any help is appreciated.

Thanks,
Dr. Gonzo

 

[DrGonzo]

Quick note:

I see that I can set my bubbles to link to a specific file.
Not happening for large amounts of bubbles.

I also see a setting when RMBing the view with incorrect bubble number that allows me to link it to a specific BOM. This option is however grayed out, on the second page. Not on the first page. I can select a view that wasn't used to create the BOM and change the setting as long as it is on the same page.

Thought this might help.

 

[drawoh]

DrGonzo,

My experience with SolidWoris 2003 SP5.0 is that the presence of a BOM affects the item numbering on a drawing view. Consider the following sequence.

1. I insert a view directly from the model.

2. I insert a BOM into the new view.

3. I insert another view directly from the model.

4. I apply item balloons all over the place.

The item balloon numbering will not necessarily be consistent between the two views. Projections from the first view seem to item number consistently. When you placed view on two separate sheets, you probably did what I show above.

The solution is to place a BOM on the second view. You can drop the BOM somewhere off the drawing if you only want to see this once. Check the BOM properties and make sure the settings under the Control tab are the same. The section labeled "Row numbers" affects the row numbering, not surprisingly.

JHG

 

[automationbabe]

Verify that the views you are adding bubbles to are the same configuration as the view that created the BOM. I'm running same SP and have no problems with this.

Good Luck

 

[DrGonzo]

Thank you for replies so far. I am running into trouble when:

page 1. I create a bom from a simple ISO view.

page 2. I create views from derived configurations in the
original view on page one. These views are
derived and in my mind should therefore be
children of the same BOM.

So following the thought of making sure all views show the same configuration... How do you go about showing various exploded/detailed views and bubbling them without them showing the same configuration? I don't know of any other way to show exploded views, or views with hidden part; without creating configurations for each view I want, relatively speaking. If you do it this way then you will undoubtedly have the views looking at different configurations, which goes back to the derived and original configs sharing the same BOM. If this is the case you would only need one BOM not one for each view as I do now.

I just don't see anyone writing software that would force you to insert a BOM for each view. If you want to maintain consistent numbering you would have to ensure that each BOM was created exactly the same, no sorting and reordering on one and not on another, etc.

Sorry I am tired. This boggles my mind...

 

[CorBlimeyLimey]

I'm running SW04-SP1 & have just tried to duplicate your problem.....without success. My item numbers on second page match item numbers on first page, without making BoM on second page!! First page has Front & Right Views, second page has Rear & Top Views.
Only thing I can suggest is to RMB your BoM>Properties>Control & make sure "Row numbers follow assembly order" is checked.
Do you have the same problem on other machines?


CorBlimeyLimey
Barrie, Ontario
faq559-863

 

[DrGonzo]

Hmm. That is not what I wanted to hear corblimeylimey

I have tried the setting you are talking about as well, but good thing to point out.

I would be happy to try out your files if you could send me something that works correctly. I could in turn send you similar if you don't mind. I can create a stripped down version so it is smaller and duplicate the problem in it.

This problem is happening on all machines in my department, this leads me to believe it could be a template issue. Grasping for straws on this one. Any pointers/pitfalls for templates would be great. I did not create ours, a coworker did prior to me starting, but I need to fix this problem. It is spawning all kinds of downstream errors outside of engineering.

Thanks for the help.

 

[automationbabe]

It sounds like you have different configs displaying the drawing as you want. If the BOM was created from one config, that is the config you want to use throughout.

We have our models set up where BOM is the config we use to drive the BOM. Exploded views are a derivative of this config as well and maintain the BOM bubbles numbering order.

If we have a view that we need parts hidden in, we hide the components in the drawing, not in the assy model.

There are a few times when we show reference geometry that we don't want on the BOM, and we give this a name like "Drawing Config". The BOM config still drives the BOM in the drawing though.

There are a number of "little" things that we do to ensure that our drawing BOM, assy BOM and MRP BOM are identical at all times since our system is set up around the BOM config being accurate. All other configs are gravy. I can elaborate further if you like. Let me know.

 

[drawoh]

DrGonzo,

I have been successful almost all the time at making multiple configurations each show the same item numbering. If any parts are suppressed, you have to be absolutely methodical about making each configuration identical in this respect.

Each time I create a view from a configuration, I insert a BOM. This imposes a control on the item numbering. Any BOM inserted outside the title block will not be printed.

JHG

 

[CorBlimeyLimey]

DrGonzo
I do not have a suitable non-proprietary assy that I can release at the moment. If I have time, I will make something up tonight & send it....if you let me know to where.
You can use the email account in my profile. I use it only for these forums.


CorBlimeyLimey, Barrie, Ontario.
Don't Take It Personal, Have Fun While You Learn
faq559-863

 

[DrGonzo]

Thanks to all for all the suggestions, unfortunately my time is being consumed at a faster and faster rate. For now I will continue to insert boms for each view and try and work through this when I get a bit more time.

However this may be come a mute point if my company decides to move to SolidEdge. Cring, I have been demoing it off and on for the last few months and am not looking forward to that possibility.

 

[MElam]

If you have views that are different configs, you can "Lock view focus" on the view the BOM was created from, then balloon the view of the different config. These balloons should match the BOM. Does not always work across sheets, but you should not need a bom for every view.

 

[CorBlimeyLimey]

DrGonzo
Why would your company even consider that? I can understand going from ProE, Ideas, etc (because of cost, ease of use & learning curve) to SolidEdge .... but to go from SW to SE makes absolutely no sense. Cost, ease of use & learning curve are all about the same & SE has just as many problems as SW. What on earth do they expect to gain from such a "plan"?


CorBlimeyLimey, Barrie, Ontario.
I intend to live forever - so far, so good
faq559-863

 

[DrGonzo]

CBL,

I too feel the same way. I am not against using new things and always look for ways to expand my knowledge, but I feel SE is a regression. VARs can always tell you everything is great great great, but I see nothing so great. I do see they were first midrange with sheetmetal, but after they did that they play catch-up. Spend more time with insight and the like making a pdm/web project managment tool. Rather than making a modeling tool first.

Too say the least I am frustrated. Currently cleaning house in a design group. Building up libraries of baseline designs. Configs are wonderful for this The nice thing is we are using SW built in utilities, where as we would be developing personalized scripting to do most things in SE. These aren't too bad until it comes time to upgrade, and possible issues arise.

Biggest thing is they are a metal working company. We do wood. They are bigger, we are smaller. They buy things first, think second. They have 5 extra seats of SE sitting around. They originally bought for the department, same department size now, why are 5 seats sitting unused? hmmm