cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
Showing results for 
Search instead for 
Did you mean: 

Cannot reference pattern a merge feature

Re: Cannot reference pattern a merge feature

Yes, this is a typical case as I mentioned it in my post from Sep 6, 2013 4:40 PM.

It is a variation of my number two of the "most likely reasons for the pattern to fail":

A merge elimiates the second selected quilt, merging its geometry into the first selected quilt.

What is happening is, that your pattern in the original design is becoming the new parent of a referenced surface.

If you change the order to move the pattern after the "unwanted child", then a different feature will become the parent (the previous owner of the referenced surface).

As a rule the last feature that manipulates a geometry item (e.g. edge, surface) will become it's parent.

This is how the parametric referencing is working.

With the Reference Viewer you can see parent features and references. You should notice a difference, after you reorder the pattern.

And again: If you can send an example model, Technical Support will be able to either explain the situation in detail or open an SPR to have R&D investigate.

Re: Cannot reference pattern a merge feature

In an addition to this, when merging surfaces the surface ID is of great importance being the reference indentifyer.
As a rule always the first selected surface passes on its ID. So selection order does matter.

Mapping it to this case, even if the firt merge follows the rule and thus the ref pattern does NOT change the surface ID (checking surface ID of quilt with all merges and ID before merges), following merge patterns will fail.
This is against the logic...

Re: Cannot reference pattern a merge feature

I've just tried your solution, and it worked too. However, I had to supress the previous 2 merges instead of just one, as it will try to reference pattern to that previous merge.

I guess this is similar to me reordering/inserting the new merge pattern feature before those feature. Now we have 2 possible work-around to this problem.

Highlighted

Re: Cannot reference pattern a merge feature

Gunter,

In general, when things are done in order, the software should be able to figure out which feature/pattern to reference to. As you had mentioned, the order of selection will affect which pattern Creo chooses, but the reference merge still failed even when it choosed the correct pattern to reference. I've also tried grouping the features before patterning it, so there is no excuse to have just the merge fail. If the software doesn't know which reference to use, it needs to present the options.

When a workaround is needed, it usually means the software has a bug/deficiency. We shouldn't have to waste valuable productivity time to trouble shoot simple tasks like this.

Understand that not everyone will have the same problems, even on the same model. (I've been in situations where the model fails on one system, but regenerates perfectly on another). This will be a whole other topic.

Re: Cannot reference pattern a merge feature

Gunter Koch wrote:

<snip>

Of course I agree, that it would be nice to implement some means to warn the user of multiple possible ref patterns and explicitly ask, which to follow, but for such a thing to be worth implementing, we probably do not see this happen often enough.

...

Gunter, you said a mouthful here.

I can promise you that this happens more often than not even with very experienced users. Not only the reference pattern, but axial patterns fail all too often for some silly little reference in the feature being patterned.

Most seasoned users have learned that patterns will fail and they simply have to try and try again or manipulate the geometry in some way. A serious waste of mouse-clicks and the source of much frustration. If PTC doesn't already realize that this is an issue, maybe PTC should ask the user community.

A significant pattern enhancement could be a boon to Creo 3.0. Sometimes users just give up asking after a few decades. Can you imagine the response if you tried to take away axis patterns now that its been introduced

Any time the software has to make a choice, or is unsure, it should ask about alternate solutions. All too often I get a pattern that fails only a few instances within the pattern. A simple little change to the geometry fixes it even if the original, and several of the instances do not fail.

This one in particular was a complete failure. It would not allow me to pattern it with a largerer form tool fillet at the edges of the spherical feature which had nothing to do with the merged edges of the pattern. I spent a half a day to make this feature pattern correctly including several methods in creating the spherical dome. I ended up having to create the form tool feature 10 times rather than patterning a 10th section 10 times on the axis. I probably have 5 failed versions of this very same part all done differently, mostly because the pattern kept failing.

bearingcage.PNG

Re: Cannot reference pattern a merge feature

Antonius, Nai Yang and all,

I think I have to clarify what I meant in my previous posts, before discussion gets out of control:

When I said:

but for such a thing to be worth implementing, we probably do not see this happen often enough

I did not say that pattern as such are too exotic or that they fail too rarely. I just meant that it happens not too often that a pattern fails for the reason of two or more non-related patterns being referenced. And if it really is the case, it is not too hard to figure this cause out, if you are aware of having several pattern in place.

In fact from what I read from Nai Yang, I doubt that it is the case here either (of course I can't tell for sure, without having the model in hands). It is much more likely that a reference that was supposed to be used, has been eaten up by another feature, which also was patterned. But the second pattern was not appropriate as a reference for the ref pattern. In such a case, there would be no choice between two pattern and hence nothing Creo could ask you for.

Regarding the bearing cage shown in the picture from Antonius: If this geometry has been created with a form tool in sheetmetal, it is quite a task, even creating the original, first dome. I would not even have tried, because form features are pretty tricky about touching the boundaries of the surfaces they are added to. I'd rather try my luck with a solid or use surfaces and thicken them.

Since the part looks pretty symmetrical, I believe creating it should be a "piece of cake"! (please excuse the pun):

  • Create the geometry only for a 36 degree "piece of cake" with one spherical dome and one connector with hole (or half of them left and right from the dome) - do this as a surface quilt.
  • Copy special (rotation 36 degree)
  • Pattern the copy 9 times
  • Merge the first copy to the original geometry (which must be selected first to allow patterning)
  • Ref pattern
  • Solidify (or skip the merge and solidify the base quilt plus the pattern of quilts at the end)

In general ref pattern is no miracle:

  • It simply checks for references that belong to an existing pattern
  • Then it is building the pattern instances by replacing those references with their counterparts from the master pattern instances
  • And it is reusing all other references

So normally you can easily check, whether a pattern instance should generally work with the patterned references by redefining the leader, applying the corresponding references.

Unfortunately there are two more things that can make a pattern fail:

  • There is a possibility that previous pattern instances consume references (e.g. a referenced surface gets removed because it is merged to another). Of course you cannot test this with the trick above. But you can check this by controlling, whether the constant references and the corresponding references are still there, after the original feature has been added: Just open the Reference Viewer for the original feature and check whether the references (or corresponding references for the pattern references) can still be selected in the model.
  • The most difficult thing to check is the last point: Solid geometry and surface merges of course have to merge with the existing geometry. Creo Parametric is automatically using corresponding edges and surfaces in place, but if the geometry is significantly different (imagine a round not finding an edge or a merge not finding a surface), the instance will fail. This is where investigation really can become cumbersome. Creo cannot offer an alternative, because if it had one, it would use it without asking. The only general suggestion that applies, is to use absolute accuracy, to exclude accuracy issues, which which are totally unpredictable. By the way, my "piece of cake" suggestion above postpones this step as far as possible, to make this type of investigation easier, if necessary.

Creo Parametric tries to diagnose and assist the user, as good as possible. However, all those examples above have in common, that there is nothing wrong or unclear with the pattern definition. Just the feature references specified by the user (directly or indirectly by pattern) are not practical for the geometry they are supposed to be applied to. So Creo cannot warn of anything or offer alternate choices, before the feature fails.

And still then it can hardly make useful suggestion as it does not know, what the user wants to achieve (pattern the feature, yes - but not how to pattern it, i.e. with which references to guide the pattern and how to merge it to geometry that is not there).

This is the point where only the user can step in and reconsider the design - sorry, that I have no other news!

And again:

If you cannot figure out, why a pattern fails, open a case with PTC Support. If the situation can neither be solved nor explained in TS, an SPR will involve R&D and if they cannot solve or explain the issue, they will have to implement a fix. And they do, as they always did in the past!

This is why I can pretty safely say, that it is nowadays very unlikely that a pattern fails due to a bug or deficiency. In 99 % of failures there is a reasonable explanation and you should not ask for anything less as an answer. In those rare cases left over, the software will be fixed.

So in either case there should not be any reason to complain (at least not for a long time, after it has been reported).

Re: Cannot reference pattern a merge feature

It is sheetmetal and it was the only realistic way to create the cage. It is actually a very simple quilt form feature.

This should probably be reserved for a different discussion, however.

edit: I have submitted the bearing cage as a support case. This is a nearly perfect test case for both sheetmetal forms and patterns. In this case, one instance of the pattern fails, yet I can make the exact same form feature from the patterned form quilt at the failed location. FYI, the form can be a semi-sphere or a full sphere. The rounds on the edges are part of the form feature.

Re: Cannot reference pattern a merge feature

Hi Nai,

i wrote 'suppress all previous ones'...

Announcements