Skip to main content
Jun 11, 2020 11:50 AM UTC
Duplicate

circular reference

Related products:Creo Parametric

whilst busy working on fairly complicated model and using in-context modelling. CREO is good enough to inform you when you have mistakenly created a circular reference but gives no idea as to where it is. it may only be 1 constraint that is causing it. it would be great and very time saving if CREO could, as well point out the circular ref , point to the feature or constraint that is cause it. this could be done with the yellow triangle in the tree and a note in the info area.

14 replies

Jun 11, 2020 12:07 PM UTC

It's always been that way...not sure why.

Creo does create a .crc file in the working directory that describes the circular reference. I learned how to read those years ago. They look confusing, but then again, it's a circular argument. I usually look at the middle, that's usually the feature that you created the problem.

You can also use the reference viewer. It's a good tool that I have yet to master...I guess because I'm stubborn.

 

There are other "ideas" on the same topic.

https://community.ptc.com/t5/Creo-Parametric-Ideas/Better-debugging-for-circular-references-besides-crc-file/idi-p/488493

https://community.ptc.com/t5/Creo-Parametric-Ideas/Better-representation-for-circular-references-besides-crc-file/idi-p/563547

 

Jun 11, 2020 1:11 PM UTC

it would be nice if the crc files was easier to read, hence why I thought having it noted in the feature tree would be great.

I try to avoid them and I've figured out whats caused the one I had. I haven't figured out how to spot it in the reference viewer but i'm still quite new to creo.

 

thanks

Jun 29, 2020 11:19 AM UTC

Tools>Refrence Viewer

Works also from model tree: Right mouse button over component, Info>Refrence Viewer.

 

The functionality "select from parents" in mini-toolbar is also handy for fast investigation.

 

 

 
 

 

Jun 29, 2020 12:04 PM UTC

that's handy to know, but will only be useful if you know which component is causing the error.

how can you tell from looking at the feature tree which is the problem component?

Jun 29, 2020 12:14 PM UTC

Well, that did not land nicely.

So, youll have you crc file for potential candidates which you may start to investigate using those two tools.

 

As a part of this Product Idea, I would suggest that Creo Parametric would have Model Tree Query, that would consume the info from crc file. Please show only the components at model tree, which are part of circular refrence loop.

Jun 29, 2020 12:22 PM UTC

hi, its all good. yeah I've used the crc files to help but it would still be great, as you then mention, to have the details easily available in the feature tree.

the crc files are not the easiest to decipher. would be good if they pointed directly to a looped part and the exact feature and then the dimensions or constraint. i'm assuming that if it pointed out the crc then it must know exactly what is causing it.

Jun 29, 2020 12:34 PM UTC

hi. ok quick question.

some model from before I started with my company have circular refs. can you please explain what the 

depth of loop means, as some have 4, 5, 7 and 8?

from the loop how do I know which component / feature is causing the issue?

thanks

Jun 29, 2020 12:45 PM UTC

Depth of loop = number of components patricipating

Break any of connections between components and you´ll break the loop.

Jun 29, 2020 12:52 PM UTC

ok. so how do you figure out where the connections between the components are. the crc gives info, but how do you know from the loop info which feature is the issue and then if its a big sketch how do you know which dim or constraint is the issue?