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

T-value Calculation

Slug Dawson
I searched PCdmis help menu & this forum and couldn't find the formula that the software is using for calculation the reported T-values. Does anybody have this information?

I have some historic XYZ data & current data. The current data has T-values reported but the historic data does not. The customer wants to know the difference in historic & current data based only on the T-values.

Thanks in advance for your assistance.
Parents
  • You can calculate T-Value like this :
    ASSIGN/TVAL=DOT((PT1.XYZ-PT.TXYZ),PT1.TIJK)
    T-Value is the projection of the measured point along the theoritical surface vector.

    Profile tolerance is buggy in 2015.1 SP10 and it's reporting a false NG when clearly it's all in tolerance.

    Ref: 
                ASSIGN/V1=GETPROGRAMINFO("NUMOOT") 'is 0 when no dims are out of tolerance


    I used above DOT() to report the min/max of a feature set and put them in a T-Val location dimension instead of a Profile dimension.
    My process is part of an automated cell and when multiple parts are 'NG' the order finishes short and moves on to the next order on que. Big no-no when I have to explain why CMM is reporting things in 'error' and our orders are wrapping up prematurely.

    Thanks it saved my neck.
Reply
  • You can calculate T-Value like this :
    ASSIGN/TVAL=DOT((PT1.XYZ-PT.TXYZ),PT1.TIJK)
    T-Value is the projection of the measured point along the theoritical surface vector.

    Profile tolerance is buggy in 2015.1 SP10 and it's reporting a false NG when clearly it's all in tolerance.

    Ref: 
                ASSIGN/V1=GETPROGRAMINFO("NUMOOT") 'is 0 when no dims are out of tolerance


    I used above DOT() to report the min/max of a feature set and put them in a T-Val location dimension instead of a Profile dimension.
    My process is part of an automated cell and when multiple parts are 'NG' the order finishes short and moves on to the next order on que. Big no-no when I have to explain why CMM is reporting things in 'error' and our orders are wrapping up prematurely.

    Thanks it saved my neck.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement