Skip to main content
15-Moonstone
January 8, 2020
Question

:att_cmp only works with parts?

  • January 8, 2020
  • 1 reply
  • 2813 views

So I have a drawing with many simplified rep views. Can't do a normal BOM since I can't show balloons in different simpreps. I look around and there's this tip that you can get around this by using component parameters instead. I try it and it works. I still need to have one BOM for every simprep, though, which means my drawing now has five BOMs. I can hide them, but it's quite clumsy.

 

I realize, though, that I should be able to do it with balloon notes and the text &FINDNUMBER:att_cmp. I try it out and it works! I realize quickly that it doesn't work with sybols, which is a shame, but still, it's pretty convenient.

 

But now I try it on some more components and it dawns on me that the :att_cmp tag only works for parts; not for assemlies. It's terribly annoying and rather makes the whole :att_cmp useless, it seems to me. I'm guessing it's just how it is and nobody is going to do anything about it, but I wanted to make a post just in case anyone has a workaround. Or just to have something searchable that people can find if they happen upon the same issue as me.

 

So: anyone have a workaround? Is is possible to call out the component parameters in balloon notes? I guess I could do it with Session IDs, but that would be a LOT of work and not nearly as robust (if you change the attachment, for example).

1 reply

23-Emerald III
January 8, 2020

I don't know how to fix the actual question of the component attachment.

 

There is a "bug" you can use to get balloons across simplified reps.

https://community.ptc.com/t5/Creo-Parametric-Ideas/Allow-BOM-Ballons-from-Master-Rep-Repeat-Region-to-be-displayed/idc-p/466857/highlight/true#M5732

 

If you haven't, vote on the idea in the link also

 

 

15-Moonstone
January 9, 2020

Thanks, yeah, I found that one, too, but it doesn't seem to work on this installation. And with some 50 balloons, it sounds like it would take a lot of time.

 

I voted on the idea, and it seems it's already been acknowledged. If I'm not too lazy, I might write up an idea to fix the :att_cmp issue as well, though I doubt it affects enough people to gain any traction. It's really useless to have this half-working possibility as it is now.

24-Ruby III
January 9, 2020

@Pettersson wrote:

Thanks, yeah, I found that one, too, but it doesn't seem to work on this installation. And with some 50 balloons, it sounds like it would take a lot of time.

 

I voted on the idea, and it seems it's already been acknowledged. If I'm not too lazy, I might write up an idea to fix the :att_cmp issue as well, though I doubt it affects enough people to gain any traction. It's really useless to have this half-working possibility as it is now.


Hi,

I tested following scenario ...

top_asm.asm

... some parts

... subassembly.asm

    ... some parts

---

In top_asm.asm I defined component parameter mypar for subassembly.asm

In subassembly.asm I created datum point representing note attachment point.

I created drawing of top_asm.asm and placed iso view of assembly.

In drawing

  • I created note with leader attached to entity
  • I selected above mentioned datum point
  • I entered &my_par:att_cmp
  • finished ... my_par value defined for subassembly.asm component was displayed

Maybe it helps ...