Hi all,
I use a lot of assignments in progs, and some of them are surprising :
In a loop V1, I can ASSIGN/V2="CE"+V1, then ASSIGN/V3=V2.HIT[1..12].XYZ, and it works fine.
If I change from a circle to a cone, V2 becomes "CO"+V1, and V3 gives 0 !!!!!!! If I write ASSIGN/V3=CO1.HIT[1..12].XYZ, it gives me the good values.
Another problem with cones is the generic feature "cone" :
I have a measured cone, I assign CO.XYZ, CO1.IJK, CO1.L and CO1.A.
I create a generic cone with those values, distance between both cones is 0, angle is 0 but when I create a circle/cone/height/origin/Zplus, the results are very different...
It seems that diameter option gives good results.
I tested this in 2014.1 SP6 and 2015.1 sp5.
I use a lot of assignments in progs, and some of them are surprising :
In a loop V1, I can ASSIGN/V2="CE"+V1, then ASSIGN/V3=V2.HIT[1..12].XYZ, and it works fine.
If I change from a circle to a cone, V2 becomes "CO"+V1, and V3 gives 0 !!!!!!! If I write ASSIGN/V3=CO1.HIT[1..12].XYZ, it gives me the good values.
Another problem with cones is the generic feature "cone" :
I have a measured cone, I assign CO.XYZ, CO1.IJK, CO1.L and CO1.A.
I create a generic cone with those values, distance between both cones is 0, angle is 0 but when I create a circle/cone/height/origin/Zplus, the results are very different...
It seems that diameter option gives good results.
I tested this in 2014.1 SP6 and 2015.1 sp5.