Skip to main content
V
visu1-Visitor
1-Visitor
November 18, 2013
Solved

ISO HOLE ERROR

  • November 18, 2013
  • 2 replies
  • 9665 views

Dear Folks,

Facing an issue when the iso hole created in creo/elements pro 5.0

I have attached screen shot please view it and review it.

why i can't create those?

THREAD.JPG

Thanks & Regards

Viswanathan.K

    Best answer by visu

    Dea Folks

    The ISO HOLE ERROR because of part accuracy value.

    Later i increased the part accuracy value then it is created succesfully.

    Thanks & regards

    Viswanathan.k

    2 replies

    P
    ptc-50080821-Visitor
    1-Visitor
    November 18, 2013

    Check in the 'Shape' tab and make sure that the values for the tapping drill and the thread make sense.

    V
    visu1-VisitorAuthorAnswer
    1-Visitor
    November 29, 2013

    Dea Folks

    The ISO HOLE ERROR because of part accuracy value.

    Later i increased the part accuracy value then it is created succesfully.

    Thanks & regards

    Viswanathan.k

    R
    RafaelRiquelme1-Visitor
    1-Visitor
    August 11, 2014

    Viswanathan,

    I'm going through the same annoying problem. Could you describe the steps you took to increase the part accuracy value, as I am new to Creo? Thanks in advance.

    T
    TomD.inPDX17-Peridot
    17-Peridot
    August 11, 2014

    Creo uses a relative accuracy setting in the model properties (file>prepare>model properties). You can try setting this to a more refined value. Default is .0012. There is also an "absolute" accuracy capability but you have to enable this 1st in config.pro: enable_absolute_accuracy no*/yes and you might also look at all the "accuracy" settings you can specify in config.pro. Personally, I also set default_abs_accuracy to .00005.

    I really REALLY REALLY find this whole accuracy thing annoying in Creo. I understand why it is there, but internal management of this should be transparent to the user. This would be MUCH better handled in a failure handling mechanism where accuracy would be set base don the users! needs, not the software. Warning are fine, but feature failure due to accuracy setting? Not acceptable in this day and age.

    Terms & ConditionsAccessibility statement