hexagon logo
Register Sign in
  • Replies 34 replies
  • Subscribers 225 subscribers
  • Views 360 views
  • Users 0 members are here
Options
Related

2022.1SP6 Parallelism issue

JEFMAN
I have 2 planes, PL1 is datum A (primary using minimax), and PL2 constructed from 7 basic scan/circle/plane. (least square, but it shouldn't change anything !)
Using geotol, it gives 7,1 µm
using legacy, it gives 35,1 µm
using assignments (ASSIGN/V1=DOT(PL2.HIT[1..PL2.NUMHITS].XYZ-PL1.XYZ,PL1.IJK) , then ASSIGN/V2=MAX(V1)-MIN(V1)), it gives 36,1 µm.
Then, constructing 7 planes from scans and construct a plane from their centroids, it gives about 8 µm (so I'm wondering if geotol uses them to calculate instead of hits ?)

Don Ruggieri , neil.challinor
Parents
  • I tried this as well [..] and it did not work, you can see that when you use the [..] with out the numhits the Theo and Actl do not populate with values ?
  • in reply to Mike Rivard
    and
    I finally got chance to take an initial look at this problem and it looks like the reason the feature doesn't update is because it has a space in the feature name rather than anything to do with the .. syntax. In VPT's screenshot, his feature is named PLAN MOTSATT A3 (notice the spaces). Similarly, in the routine he shared with me, his plane is named PLAN B (again, notice the space). If I add an ASSIGN/V1=PLAN B.NUMHITS assignment to VPT's routine, it turns red because it doesn't recognise the feature. As soon as I edit the feature name (either delete the space or replace it with an underscore) the plane updates, the numhits assignment returns a value and the error messages from the associated geometric tolerance commands disappear.
Reply
  • in reply to Mike Rivard
    and
    I finally got chance to take an initial look at this problem and it looks like the reason the feature doesn't update is because it has a space in the feature name rather than anything to do with the .. syntax. In VPT's screenshot, his feature is named PLAN MOTSATT A3 (notice the spaces). Similarly, in the routine he shared with me, his plane is named PLAN B (again, notice the space). If I add an ASSIGN/V1=PLAN B.NUMHITS assignment to VPT's routine, it turns red because it doesn't recognise the feature. As soon as I edit the feature name (either delete the space or replace it with an underscore) the plane updates, the numhits assignment returns a value and the error messages from the associated geometric tolerance commands disappear.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement