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

Do away with manual alignments - use Readpoint

Butch
Hi Everyone
I am fairly new to PCDMIS being a Mitutoyo programmer for the last 10 years (Booo). The training I had on PCDMIS was reliant on a MANUAL setup before going into DCC mode. By going straight into DCC mode position your probe over its start point. Then you can insert a READ POINT. Then put the XYZ origin on the READ POINT and hey presto your probe has a X0, Y0 and Z0 starting point. You can now do a rough setup by getting the CMM mode to search for your part elements.
This can still then be skipped if not required for further parts. Why go to the lengths of manual probing when the CMM will do it for you?

I am enjoying the new challenge of PCDMIS and can see that it is deep and dark. By using code instead of set routines like the Mitutoyo I realise it can be a lot more flexible. Now if I only knew all the codeing tricks?
Please look out for my questions appearing.

Butch
Parents
  • No it's before the 321 alignment. When I click on the model to place the first datum, X1, it's coordinates are not where they should be.

    I guess without seeing what your doing and how far it is off I'm thinking it may be due to the inaccuracy of eyeballing the probe into position. My thought was that a quick DCC 321 right after the read point should properly refine the part location accurately and eliminate any readpoint location error.
Reply
  • No it's before the 321 alignment. When I click on the model to place the first datum, X1, it's coordinates are not where they should be.

    I guess without seeing what your doing and how far it is off I'm thinking it may be due to the inaccuracy of eyeballing the probe into position. My thought was that a quick DCC 321 right after the read point should properly refine the part location accurately and eliminate any readpoint location error.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement