Skip to main content
D
dgschaefer21-Topaz II
21-Topaz II
September 14, 2011
Question

EXTERNAL: Commandments of ProE- 2nd attempt

  • September 14, 2011
  • 3 replies
  • 1650 views
That just forces the new old method of handing problems. Pro/E stopped
failing every time a reference was missing long ago, sometime around
WF1, maybe earlier. Since then, if it can find a suitable replacement
reference, it will with only a passing mention in the message area. If
you pay attention you may see 'original reference not found, using
alternate' or something similar, but they flick by so quickly you may
miss it.



With WF5, features that actually fail to regenerate at all can be
ignored. I can see where this can be useful while working through a
problem, but dangerous if not dealt with properly. Haven't had a
project on Wf5 yet to experience it firsthand.



Doug Schaefer

    3 replies

    C
    cfly1-Visitor
    1-Visitor
    September 14, 2011
    It took me a while to catch on; the documentation of the traffic light
    doesn't stand out. If there are any potential problems in the model, the
    light will remain yellow (or turn red on an actual failure). Warnings show
    in the command line during regeneration and if there are too many to see in
    your cache, you can get the entire list from Info>Session Info>Message Log.



    efefefefefefef

    Applied Research Labs

    University of Texas at Austin

    Carol Fly

    Mechanical Designer

    (512) 835-3397

    Fax (512) 835-3259

    efefefefefefef

    _____
    T
    tcarrington1-Visitor
    1-Visitor
    September 14, 2011
    Hey All:



    I know this has been asked before because I searched the archives and
    tried:, (see image below). It didn't work. What did I do wrong? Are
    the double \'s <file: \'s="> correct in the path name? I did change
    the path name to: C:\Program Files (x86)\proeWildfire 3.0\bin\.
    Thanks.



    Wildfire 3



    --Tom Carrington--
    Rexair LLC
    231-876-3932
    -






    This email and any attachments are confidential and may be legally
    privileged. If you are not the intended recipients, please notify
    the author by replying to this email message, and then delete all
    copies of the email on the system. If you are not the intended
    recipient, you must not disclose, distribute, copy, print or use
    this email in any manner.

    Email messages and attachments may contain viruses. Although we
    take precautions to check for viruses, we make no assurances about
    the absence of viruses. We accept no liability and suggest that
    you carry out your own virus checks.
    B
    BobSchwerdlin1-Visitor
    1-Visitor
    September 14, 2011
    Doug,

    In regards to your comment, " I can see where this can be useful while working through a problem, but dangerous if not dealt with properly". That is exactly my point. Although the more recent new users of Pro/E at my company like this feature because it lets them "get past" the immediate problems (failures) and then go "go back" to fix it later. But like I stated previously, they have been burned a few times because "they forgot to go back and add the missing hole or protrusion" once the models completed regeneration. I'm just saying... "watch it and... pay attention". I'd rather know that there is a snafu and I need to fix it before it gets out of hand down the road.

    "Original reference not found, using alternate" almost always makes me go back to fix the alternate's reference. Good examples are a series of holes or cuts with rounds or chamfers attached... delete a hole and then you get the message. I go back to redefine the rounds or chamfers and remove the yellow ones and of course to delete the red ones because it causes the entire feature to fail, but can be easily recovered by removing the reds and adding the new refs to the feature list.

    Bob
    Terms & ConditionsAccessibility statement