hexagon logo

Hunger for knowledge

Hello everyone!

To give you a little background on myself, I program a Taurus horizontal arm for a sheet metal prototype facility. I have been programming with PC-DMIS for two years. I was initially brought into quality as an inspector and not long after begin training as a programmer, so my general knowledge of inspection is rather basic and completely relative to sheet metal stamping as i have to prior quality inspection experience. I occasionally get parts that have three dimensional features but it's not often. I have taken level 1 of PC-Dmis and a basic gd&t class.

The colleague that I have learned from said to me in the very beginning of my training " the CMM is just another tool you're using to inspect parts, at the end of the day to do your job properly it comes down to being a good inspector not just a good programmer".

My question is what sort of resources are out there for the better understanding of inspection of all types of features?

I understand the asme standard is a good reference I was just curious if there is any material that I can read up on or videos I can watch that put things into a more digestible format for someone as inexperienced as myself.

I have been told that ASQ, third-party inspection companies, even hexagon, have classes related to inspection that I can learn from.


​​​​​​What classes, resources, and informational tools do you recommend?

Thank you in advance.
Parents
  • NB is right, the hunger of knowledge is a good point.
    I would just add that trig and a little maths are important, and the main problem (in my opinion ! ) is just knowing that uncertainty exists ( I wrote "exists" : You don't have to be able to calculate them "exactly", you just have to understand that a result is never "exact", that it can vary a little on the same part, at different moments, or with different methods).
Reply
  • NB is right, the hunger of knowledge is a good point.
    I would just add that trig and a little maths are important, and the main problem (in my opinion ! ) is just knowing that uncertainty exists ( I wrote "exists" : You don't have to be able to calculate them "exactly", you just have to understand that a result is never "exact", that it can vary a little on the same part, at different moments, or with different methods).
Children
No Data