hexagon logo
Register Sign in
  • Replies 3 replies
  • Subscribers 9 subscribers
  • Views 77 views
  • Users 0 members are here
Options
Related

Dataview direction error for trim points??

jimmyD
Hello,
I'm having trouble with trim points on dataview. When dataview reports on some trim points their "T" value reports F/A when the vector is c/c. It only makes this mistake when the prehit direction (form) deviates further than the trim. So if the trim is @ nominal and trim point is in the Y the report would say F/A beside dataview trend graph on that point because the prehit measures the form with a deviation?!?!

Is there a quick fix for this?
Parents
  • Hello,
    I'm having trouble with trim points on dataview. When dataview reports on some trim points their "T" value reports F/A when the vector is c/c. It only makes this mistake when the prehit direction (form) deviates further than the trim. So if the trim is @ nominal and trim point is in the Y the report would say F/A beside dataview trend graph on that point because the prehit measures the form with a deviation?!?!

    Is there a quick fix for this?
    IF you are NOT reporting the FORM ERROR with those edge points, turn on GAP ONLY for the XYZT dimensions for the edge points. It acts like SNAP does for vector points. I still allows the surface sample hit to determine the depth of touch, but then it "projects" back to the nominal surface. That should fix it.
Reply
  • Hello,
    I'm having trouble with trim points on dataview. When dataview reports on some trim points their "T" value reports F/A when the vector is c/c. It only makes this mistake when the prehit direction (form) deviates further than the trim. So if the trim is @ nominal and trim point is in the Y the report would say F/A beside dataview trend graph on that point because the prehit measures the form with a deviation?!?!

    Is there a quick fix for this?
    IF you are NOT reporting the FORM ERROR with those edge points, turn on GAP ONLY for the XYZT dimensions for the edge points. It acts like SNAP does for vector points. I still allows the surface sample hit to determine the depth of touch, but then it "projects" back to the nominal surface. That should fix it.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement