I have an assembly that I created a small Pro/Program for. I am just prompting for the value of a component in the assy.
The problem is: In order for the dimensional change to the component to propagate all the way up to the main assy, I need to manually do a second regeneration.
Is there a way to force Pro/E to perform a second regen?
Thanx,
Andy
I have an assembly that I created a small Pro/Program for. I am just prompting for the value of a component in the assy.
The problem is: In order for the dimensional change to the component to propagate all the way up to the main assy, I need to manually do a second regeneration.
Is there a way to force Pro/E to perform a second regen?
Thanx,
Andy
Typically, Andy, we close out one question before starting another. So, we'd appreciate knowing if your question was answered from a few days ago because that discussion may not be finished. And it would be good to get to the bottom of it. If we didn't help you there, we will be discouraged from helping you further.
David Janes
messagenews: snipped-for-privacy@y42g2000hsy.googlegroups.com...
appreciate knowing if your question was answered from a few days ago because that discussion may not be finished. And it would be good to get to the bottom of it. If we didn't help you there, we will be discouraged from helping you further.
Sorry, I was unaware of the "one open question at a time" rule. I have been trying to figure out the real solution to the earlier question, and had not yet come up with a good answer.
I did get a suggestion on the topic above on forcing a regen. They suggested using the "EXECUTE' and "END EXECUTE" statements in Pro/ Program. I have not found any good documentation on that, so if anyone has any suggestions that would be great.
Thanx again, Andy
messagenews: snipped-for-privacy@y42g2000hsy.googlegroups.com...
appreciate knowing if your question was answered from a few days ago because that discussion may not be finished. And it would be good to get to the bottom of it. If we didn't help you there, we will be discouraged from helping you further.
That sounds like a good lead upon which you can get a more definitive answer from PTC technical support.
I for one am curious to hear what you find. The solution I've seen for this problem in the past was just for the user to be aware that 2 regens might be required to fully push the results of a change.
David
This is an unmoderated newgroup. There are no rules. I make suggestions on how to proceed with discussions, because I'm an active participant. I just act like I own it cuz I'm here every day and I care what goes on here. Too often we give advice or technical help and hear nothing about the results. Science is exceedingly difficult in the absence of information. We are trying to improve and people who tell us how we did help us improve. This is what I'd call real participation: help out, when you can, and tell your helpers when you've been helped (quality control validation per CMM2).
I have been > trying to figure out the real solution to the earlier question, and > had not yet come up with a good answer. >
Yes, this sounds like what you need, if you know how to do it. It sounds like they didn't get below the mile high, general view solution.
David Janes
PolyTech Forum website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.