Skip to main content
G
gkarthikyn1-Visitor
1-Visitor
January 20, 2020
Question

CREO Drawing Balloons with Different REP

  • January 20, 2020
  • 3 replies
  • 8872 views

Hai, 

 

I am Creating assembly Drawing. Usually we create REP to for View clarity for views other than main view . But Now i am unable to use parametric balloons on views with different REP. any way to fix this. BOM balloons is from Master REP.

3 replies

S
23-Emerald III
StephenW23-Emerald III
23-Emerald III
January 20, 2020

Unfortunately it is not currently possible. There is a product enhancement idea to add this functionality.

https://community.ptc.com/t5/Creo-Parametric-Ideas/Allow-BOM-Ballons-from-Master-Rep-Repeat-Region-to-be-displayed/idi-p/466852

 

Within that product idea, there are a couple of work-arounds and I used to use one of them that let you do a "same ref" attachment but I can no longer make that work (i'm on Creo 4, M090).  Not sure if it's just me or if that work-around has been "corrected" (for lack of a more crude word).

 

    P
    Pettersson15-Moonstone
    15-Moonstone
    January 22, 2020

    This is a functionality that needs to come soon. While we are waiting, there are a few workarounds:

     

    1. Create several BOM tables (one for Master Rep and one for each Simp Rep) and sync their item numbers. Then hide all tables except the Master Rep one. Downside: Updates risk introducing non-synced items that the designer doesn't notice.
    2. Rather than using Simp Reps, create a layer that contains the items you want to hide and then hide that layer on the drawing view. This is often the easiest solution.
    3. Use Component Display in the drawing to hide the components you want to hide. I wouldn't recommend this, as it will be harder for people to find how you hid the components, and it's less reuseable (if you want to repeat it on a second view, for example).
    4. Use component parameters to set item numbers for all your components, then use these in your BOM instead of rpt.index. (Remember to also change the contents of the BOM balloons to show this instead of rpt.index.) Then, as in the first solution, create several tables and hide all except the master rep one. This will automatically sync all your tables, but you run the risk of others opening your drawing not knowing how it was made.

    If you go by option 2, you could sync your layer with a simp rep by creating a simp rep driven by a rule to exclude everything on the layer you created. Unfortunately, as far as I know, you cannot create a rule in a layer to include everything excluded in a simp rep (which is weird, because when you create a rule-driven simp rep you can create a rule based on what is excluded in another simp rep).

      G
      gkarthikyn1-VisitorAuthor
      1-Visitor
      January 22, 2020

      Hai Pettersson, i like the Layer Proposal. we can work out and see how easy it will be for us.

        R
        rustys1-Visitor
        1-Visitor
        February 7, 2020

        this may help you

         

         

        G
        gkarthikyn1-VisitorAuthor
        1-Visitor
        February 7, 2020

        Video is not helping. Since issue is how to show same Balloon number in different REP. 

        S
        sacquarone21-Topaz I
        21-Topaz I
        March 18, 2022

        Hello @gkarthikyn 

         

        Consider that for this kind of business need, the suggestion from @JS_9824412 is the one we propose as well, as documented in article 31065 (confirming as a current limitation that usage of a single unique repeat region cannot be the starting point of BOM balloon values being produced and mantianed in different views for multiple simplified representations in assembly drawings)

         

        In other words, create BOM Balloons for all components (starting from Master Rep), and then use Search Tool for a quick and easy access to Blank Components in Views.

         

        Just trying to help a bit further here. Not an ideal approach, I agree, but I do not see any better way to do this, due to the current limitation officially documented in above article.

         

        Regards,

         

        Serge

        Terms & ConditionsCookie settingsAccessibility statement