hexagon logo

Alternate Explanations to New Programmers

Good Afternoon guys.

I am creating a Powerpoint for the up and coming programmers that I am training. Right now I have a screenshot of a Circle Feature code showing all parameters. I am going through each line and creating a detailed description so that hopefully they can better understand the code itself. One thing I am struggling with and have struggled with in the past is explaining some of the concepts of programming. I usually draw a lot of pictures and use parts to explain what I am teaching but some things are just difficult to explain in a way that a newbie can understand.

So I wanted to create a thread for explanations of more complicated concepts within programming. For example I am trying to find alternate ways to explain sample hits and the purpose of using them. Simply saying its a projection plane for a circle doesn't quiet cut it. I have explained it other ways but it doesn't seem to click yet.

So if you guys have had some success in explaining something about Pcdmis that you would like to share please drop it down below. I'll start with a post below about flatness and why you must measure with more than 3 hits.
  • Why you must measure flatness with 4 or more hits.

    Lets say you have a chair with 3 legs. One of those legs is 6 inches shorter than the other two. If you sit in that chair you will be at an angle.... but the chair will not rock. Because it has leveled itself to those 3 legs. However if you were to sit in a chair with 4 legs (3 the same size and one 6 inches shorter) the chair would rock.
  • Why you must measure flatness with 4 or more hits.

    Lets say you have a chair with 3 legs. One of those legs is 6 inches shorter than the other two. If you sit in that chair you will be at an angle.... but the chair will not rock. Because it has leveled itself to those 3 legs. However if you were to sit in a chair with 4 legs (3 the same size and one 6 inches shorter) the chair would rock.


    This is the exact explanation to give to someone when explaining "fixture tolerance" for iterative alignments. target point radius is the tolerance for the level (takes care of the wobble in the THREE points) but fixture tolerance is the extra tolerances ONLY needed if you use more than 3 pnts for leveling because of the "chair rocking" (wobble induced by point#4-point#x of the leveling points). i could never understand target point radius/fixture tolerance until someone at Hex threw the wobbly chair story at me.
  • Sample Hits:

    Use if--> You want to measure a hole or something in a surface...but the top of the surface isn't very flat...OR...the surface that the geometry exists at can vary in height so you're concerned about maintaining a consistent hole depth measurement/potentially missing the geometry...

    Sample hits will level off the vector of the hits to help the CMM probe more cleanly (leveling for that specific measurement) AND it will also tell the CMM where the "top" of material is so you can set your "depth" parameters to be dependent on it (always be 0.030deep into the part regardless of where the actual surface exists at...imagine this could be a problem if the height of your surface can be ±0.050!!)
  • When measuring a true position, if you don't trust the results, recall EXTERNAL alignment "ALN_PNT31" and then check the holes back to it. If issue hasn't been resolved using this method, part is scrap.