hexagon logo
Register Sign in
  • Replies 34 replies
  • Subscribers 225 subscribers
  • Views 368 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

    I'm working offline on 2020 r2 initial release.

    I'd strongly advise you upgrade. If you're not able to move to the most recent version, you should at least move to the most recently available 2020 R2 Service Pack. We made a number of significant functionality improvements and updates to the underlying GD&T library over the course of 2020 R2. The most notable would be to allow 2D features (lines circles and slots) as datums so as to better support our vision systems (since you are typically limited to only being able to measure 2D features when using a camera). We also changed the way in which slots are handled. In the initial release of 2020 R2 and in older versions using XactMeasure, slots were treated as circles - meaning that only the centroid was considered, not the orientation of the slot. From 2020 R2 SP1 onwards, slots are treated as pre-resolved widths and there is an additional toggle in the dialog to decide whether you want to consider the slot length-wise or width-wise.
Reply
  • in reply to Mike Rivard

    I'm working offline on 2020 r2 initial release.

    I'd strongly advise you upgrade. If you're not able to move to the most recent version, you should at least move to the most recently available 2020 R2 Service Pack. We made a number of significant functionality improvements and updates to the underlying GD&T library over the course of 2020 R2. The most notable would be to allow 2D features (lines circles and slots) as datums so as to better support our vision systems (since you are typically limited to only being able to measure 2D features when using a camera). We also changed the way in which slots are handled. In the initial release of 2020 R2 and in older versions using XactMeasure, slots were treated as circles - meaning that only the centroid was considered, not the orientation of the slot. From 2020 R2 SP1 onwards, slots are treated as pre-resolved widths and there is an additional toggle in the dialog to decide whether you want to consider the slot length-wise or width-wise.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement