Community Tip - Did you get called away in the middle of writing a post? Don't worry you can find your unfinished post later in the Drafts section of your profile page. X
Hello. I've been using CREO (first 7 now 10) for less than a year. I pick through stuff to get my job done. The training I received was = none. So, I want to show dual dimensions in the Measure results. Right now, set to English Inch. I want also Metric millimeter as well. I click on the "open options dialog box" and only see option for one unit. Does CREO 10 allow for multiple units displayed during Measure command. I searched System Options and even the search bar. I didn't find anything. That is why I'm here.
Please note I am not asking for dual dimensions for drawings. I know this is an option. Just Measure tool results display. I hate having to use calculator for every measurement.
Thanks
Solved! Go to Solution.
If you do not want to manually toggle between units then there is a workaround. Create two saved analysis features and set the units as required for comparison. You can display the results in the model tree (add a column) or create a 3D annotation in the model that uses the parameter(s) from the measures such that the values are available upon model regeneration.
Okay found somewhat an answer - you can click options and switch to mm and results update - then switch back to inches. Well, it's something. Personally - it would be nice to have this added to SW update - simple but convenient and informative.
You can start am Idea here: Creo Parametric Ideas - PTC Community
You can also create map keys to switch between different units.
Creo 7.0 example:
mapkey mi @MAPKEY_LABELMEASURE IN IN;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `4 row` `1 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `4 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `3 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `2 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `1 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `0 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `` ``;~ Activate `nmd_1` `nmd_opts_pb`;\
mapkey(continued) ~ Open `nmd_opts_dlg` `nmd_opts_len_units_opt`;\
mapkey(continued) ~ Close `nmd_opts_dlg` `nmd_opts_len_units_opt`;\
mapkey(continued) ~ Select `nmd_opts_dlg` `nmd_opts_len_units_opt` 1 `in`;\
mapkey(continued) ~ Activate `nmd_opts_dlg` `nmd_opts_done_pb`;
mapkey mm @MAPKEY_LABELMEASURE IN MM;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `4 row` `1 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `4 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `3 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `2 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `1 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `0 row` `2 column`;\
mapkey(continued) ~ Trigger `nmd_1` `nmd_report_tbl` 2 `` ``;~ Activate `nmd_1` `nmd_opts_pb`;\
mapkey(continued) ~ Open `nmd_opts_dlg` `nmd_opts_len_units_opt`;\
mapkey(continued) ~ Close `nmd_opts_dlg` `nmd_opts_len_units_opt`;\
mapkey(continued) ~ Select `nmd_opts_dlg` `nmd_opts_len_units_opt` 1 `mm`;\
mapkey(continued) ~ Activate `nmd_opts_dlg` `nmd_opts_done_pb`;
If you do not want to manually toggle between units then there is a workaround. Create two saved analysis features and set the units as required for comparison. You can display the results in the model tree (add a column) or create a 3D annotation in the model that uses the parameter(s) from the measures such that the values are available upon model regeneration.
Thanks - will look into this. Something new. Appreciate.
I asked about this even though we design in English - a ton of literature is in Metric.
If you are not aware of the fact that units can be managed in relations (parameters) then I would suggest you take a look at how that works. This would support a paradigm where you can enter values in SI units for parameters that drive a model that is set to use imperial units. I would not use this by default, but it could be useful to manage some aspects of designs in some situations where it is preferred to enter design data in one unit system and use this to create a part model in another system of units.
I've done this exact thing in a lot of top level designs. We'll get data from customers in metric but want to design our work in inches. Prevents many dumb mistakes, and its a lot easier to verify inputs in the design match the ones from the customer, especially if they're prone to changing things often. Avoids many rounding errors that can creep in with manual entry (i.e. 10mm -> 0.394 rather than the precise 0.3937...