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

Offline Deviation

Rookie
Never seen a program run OFFLINE and have deviation in the numbers. Brand new program, never been on a machine. How in the world can it have deviation in the x,y, and z?

Attaching a screenshot of the code and the point nominal deviation window. No PND... 

START      =LABEL/
A2         =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
            THEO/<-2.5357,0,-0.45882>,<-0.1857556,0,0.982596>
            ACTL/<-2.53558,-0.00011,-0.45892>,<-0.1857502,0.0000012,0.982597>
            TARG/<-2.5357,0,-0.45882>,<-0.1857556,0,0.982596>
            SNAP=NO
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=BOTH,DISTANCE=0.5
            SHOW HITS=NO
A3         =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
            THEO/<2.6563,0,-0.15247>,<0.0689165,0,0.9976224>
            ACTL/<2.65642,-0.00014,-0.1526>,<0.068922,-0.0000005,0.9976221>
            TARG/<2.6563,0,-0.15247>,<0.0689165,0,0.9976224>
            SNAP=NO
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=BOTH,DISTANCE=0.5
            SHOW HITS=NO
A1         =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
            THEO/<1.2513,15.342,-5.825>,<0,0,1>
            ACTL/<1.2513,15.342,-5.82512>,<0.0000055,-0.0000001,1>
            TARG/<1.2513,15.342,-5.825>,<0,0,1>
            SNAP=NO
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=BOTH,DISTANCE=4
            SHOW HITS=NO
            MOVE/ALL,<-5,11,-2>,TIP=T1A90B67.5,SHANKIJK=-0.92388,0.38268,0,ANGLE=90
B1         =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
            THEO/<0.33796,12.15699,-5.58651>,<-0.9614046,-0.2346412,-0.1436829>
            ACTL/<0.33814,12.15687,-5.58662>,<-0.961407,-0.2346344,-0.1436776>
            TARG/<0.33796,12.15699,-5.58651>,<-0.9614046,-0.2346412,-0.1436829>
            SNAP=NO
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=BEFORE,DISTANCE=4
            SHOW HITS=NO
B2         =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
            THEO/<-0.99702,1,-1.991>,<-0.9645677,0.2209712,-0.1441556>
            ACTL/<-0.9969,0.99998,-1.99099>,<-0.964567,0.220978,-0.1441502>
            TARG/<-0.99702,1,-1.991>,<-0.9645677,0.2209712,-0.1441556>
            SNAP=NO
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=AFTER,DISTANCE=4
            SHOW HITS=NO
            MOVE/ALL,<-7,0,0>,TIP=T1A90B67.5,SHANKIJK=-0.92388,0.38268,0,ANGLE=90
C1         =FEAT/CONTACT/VECTOR POINT/DEFAULT,CARTESIAN
            THEO/<0,0.5,0>,<0,1,0>
            ACTL/<0,0.49988,0>,<0.000007,1,0.0000001>
            TARG/<0,0.5,0>,<0,1,0>
            SNAP=NO
            SHOW FEATURE PARAMETERS=NO
            SHOW CONTACT PARAMETERS=YES
              AVOIDANCE MOVE=BOTH,DISTANCE=0.5
            SHOW HITS=NO
Attached Files
  • One possibility:
    Do you have any alignments with translations or rotations that have been keyed in? If you key in part of the transformation in an alignment and you enter the value to 3 decimal places when the actual exact value would stretch to 6 decimal places then you have built in a small amount of error into the program that will show up all over the place. I often see this crop up in position dimensions that should read "0" but instead read "0.001". There is some small error out at a decimal place that I can't see that is driving that value. I have taken to always programming with the display precision at 5 so I can see and verify everything beyond the 3 decimal places that I will report to. You can check to see if the error is coming from an alignment by placing the cursor after each alignment in the program and creating a new best-fit alignment. In the best fit dialog there is a tab for transforms where you can see the exact state of the transformation at that point in the program. Your CAD to Part and Machine to Part transforms should match exactly. I have caught all kinds of subtle errors by checking the transforms regularly.
  • I usually program at 5 decimal places also. These are the very first points that are taken. I do recall an external alignment right before these. I'll check that alignment in the morning. Thanks


    Sent from my iPhone using Tapatalk
  • I usually program at 5 decimal places also. These are the very first points that are taken. I do recall an external alignment right before these. I'll check that alignment in the morning. Thanks


    Sent from my iPhone using Tapatalk

    I hate external alignments and any manner shape or form of 'CAD = PART'. (probably because I don't understand them) If you are using a model, are you sure its correct? I usually just use auto feature dialogue boxes in manual mode, take hits on the model and look to see what numbers fill the axis and vector fields then go from there. If you have your part reasonably aligned to the machine axis, you should only need one hit to begin DCC mode. I like this better than a 'read point' because the operators won't inadvertantly start the program from out in space when they click OK before the probe is correctly positioned.
  • I guesing here but your extrenal alignment will not be "prefect" to the machine axis, then you import a cad model and now your model x,y,z, is not perfectly aligned with your external alignment and you are seeing that deviation. When you program OFFLINE from a model the only deviation you should have is from a possible programming mistake or a model that may be slightly different than the print / reported dimensions ( rounding errors / or lust plain incorrect model ).
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement