hexagon logo
Register Sign in
  • Replies 8 replies
  • Subscribers 222 subscribers
  • Views 151 views
  • Users 0 members are here
Options
Related

[2023.2 SP1] Impossible to redefine datums now?

vpt.se
Seems something has been added to 2023.2 SP1?

It appears that you can't redefine datums anymore?
For example, if I have a DATDEF C, PLANE_C it seems I cannot redefine that to another feature, like DATDEF C, CIR_1. PC-DMIS pops a dialog stating that the name must be unique (referring to "C" in this case).

For me, this is a shortcoming since we can have a 100 holes with weldnuts which all have a concentricity on the weldnuts in relation the holes (all referring to the same datum, but the datum is the hole where the weldnut is located) so we redefined the datum for every hole. This seems not to be possible anymore?

neil.challinor
Parents
  • This was a necessary change that got implemented in 2023.1 - here's the description from our internal tracking system...


    This report was initially raised because a user was editing a DATDEF command and the change was not being reflected in subsequent geometric tolerance commands. It was found that the reason for this was because they had multiple DATDEF assignments for the same datum letter in the same routine. This should not be allowed and the work done under this report removes all mechanisms a user could have employed to create multiple DATDEF references for the same datum letter. The only remaining way for a routine to arrive in such a state is via migration. This is because XactMeasure worked differently to the geometric tolerance command and did allow users to create duplicate datum references. If an XactMeasure routine containing duplicate datum references is migrated into 2023.1, it will retain the duplicate DATDEF commands and will still function correctly. However, since the geometric tolerance commands maintain a direct link to specific DATDEF commands for any datums referenced, rather than reading up the program as XactMeasure did, users should exorcise caution if they subsequently edit a migrated routine and ensure they manually refresh all inter-related commands.


Reply
  • This was a necessary change that got implemented in 2023.1 - here's the description from our internal tracking system...


    This report was initially raised because a user was editing a DATDEF command and the change was not being reflected in subsequent geometric tolerance commands. It was found that the reason for this was because they had multiple DATDEF assignments for the same datum letter in the same routine. This should not be allowed and the work done under this report removes all mechanisms a user could have employed to create multiple DATDEF references for the same datum letter. The only remaining way for a routine to arrive in such a state is via migration. This is because XactMeasure worked differently to the geometric tolerance command and did allow users to create duplicate datum references. If an XactMeasure routine containing duplicate datum references is migrated into 2023.1, it will retain the duplicate DATDEF commands and will still function correctly. However, since the geometric tolerance commands maintain a direct link to specific DATDEF commands for any datums referenced, rather than reading up the program as XactMeasure did, users should exorcise caution if they subsequently edit a migrated routine and ensure they manually refresh all inter-related commands.


Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement