Skip to main content
grocha1-Visitor
1-Visitor
May 28, 2010
Question

Round up, looks impossible tooo

  • May 28, 2010
  • 2 replies
  • 853 views

The customer have some specific issues once they produce electric towers and doesn't need that mechanic precision:

The round up should be like this:

If the dimension is 5.1 or 5.2, the representation must be 5.0
If the dimension is 5.3 or 5.4, the representation must be 5.5
If the dimension is 5.8 or 5.9, the representation must be 6.0

I already receive a answer from PTC that via traditional ways (config) it is not possible...

Warm Regards

Guilherme Rocha - Tech Support Consultant

PLM Solutions do Brasil

“A goal without a plan is just a wish.”


This thread is inactive and closed by the PTC Community Management Team. If you would like to provide a reply and re-open this thread, please notify the moderator and reference the thread. You may also use "Start a topic" button to ask a new question. Please be sure to include what version of the PTC product you are using so another community member knowledgeable about your version may be able to assist.

2 replies

rrich1-Visitor
1-Visitor
May 28, 2010
The solution for this is twofold. First you can use model check to warn
you of errors such as odd sizes, and I believe have them automatically
adjusted to your specifications. Second, don't let your designers do this.
If it should be in even .5 increments make sure they put them in that way
this is the better way just good training.



Ron


grocha1-VisitorAuthor
1-Visitor
May 28, 2010
Ok, resuming the history we had a meeting with the customer and He agreed to use the following schema for the hole representation, it doesn’t meet their diameters because it belongs to other customer so they will do something similar.

Thanks for your prompt answers!

I really liked the font tip from “Eric R. Slotty”, It can be useful in the future.



Warm Regards

Guilherme Rocha - Tech Support Consultant

PLM Solutions do Brasil

“A goal without a plan is just a wish.”

Terms & ConditionsAccessibility statement