hexagon logo
Register Sign in
  • Replies 31 replies
  • Subscribers 224 subscribers
  • Views 325 views
  • Users 0 members are here
Options
Related

Upper Management is looking for answers/Justification on probe breakage

SMace
Hello ALL GURU's:
Here's a great post for a lot of input on WWGD (What would Gurus Do)?
Lets start by saying there are NOT an excessive amount of probes being broken yearly. I would estimate less that $500.00 - $700.00 yearly max, if that.
However, The uppers want justification.
Now, it has been suggested to slow the rapid in the machine settings, which would cause more cycle time on check parts that are in a Pallet setting.
There is a CRASH attachment from Renishaw. Anyone currently use these?. And do they work. Say on a .7x20mm probe or a 1mmx27mm probe?.
In our shop, we have 4 Cmm's that all have touch probes and 2 have vision as well. What would a normal (realistic) probe consumption be expected
at your place?. Mind you that the specific probes that we have in question are 1.5x30mm. 1mmx27.5 and .7x20mm. Sometimes it may just be human error (can't help that).
Maybe a slight misload, part has been machined or molded not into spec. Other times, maybe doing a manual align and you forget the rapid is on and "Snap". It happens.
I was asked to figure the FORCE in which a probe breaks. Well, honestly what other factors go into that one?. Are you rapiding, your prehit/retract too close and you touch the part and snap?.
Seeing as we are a high volume molding/machine shop with multiple parts at any given time to inspect via DCC. What is the best course of action to go ZERO probe breakage a year?.
This would not include Set ups, Prove Outs as well.
I am just looking for some insight on this issue from a lot of people who know way more than me!. Hence, picking the brains of the Guru's. ANY input would be greatly appreciated and if you want to keep it short and sweet. great. I don't want to consume too much of your time writing.
Thank You All Slight smile

Parents
  • This is a little late to the party, but this is what works for us. Our operators don’t break tips very often. The programmers break most of the tips.
    • Operators most frequently break tips when they either setup the fixturing/part wrong or are running the wrong program. Putting a picture of the setup into your program solves both of these problems. When they have it setup wrong, the picture pops up and it doesn’t look right, they can make corrections before the CMM starts to move.
    • All programs that are meant for measuring production parts should be stored in a write protected folder. This protects from operators/programmers accidentally making changes and then those changes get saved into the program. Furthermore, PC-DMIS is constantly saving and overwriting the programs. Occasionally through no operator interaction, it can save something dumb in the program that causes you chaos. Don’t let it overwrite your known good programs. Write protect the folder at the OS level.
    • Minimize the chance of the operator running the wrong programs. Have separate areas for “Production Ready” programs, “Archives” of older programs, and where you develop new programs. The operators should only ever be operating out of the “Production Ready” folder and it should only have the one program that they should be running. Old versions and experimental versions should be in the archive or developmental areas.
    • Fixturing -> Rough Alignment -> Part Program. Ideally the entire program runs in DCC. The less you ask an operator to do the less problems you’ll have. You need to find a way to ensure that the part is always in the same location on the CMM. The best way to do this is with fixturing. Then the program performs a rough alignment to find the part using larger approach and retract distances. Then inspect the part after the program knows exactly where the part is. All of our parts are roughly the same size, so we have a corner nest on the CMM that all the fixtures nest into. Our operators put the part into the fixture, put the fixture into the nest, and then run the program, and then a picture pops up and they verify everything looks right and click OK, and then the program just runs. If you really need to have the operator measure the part at all, use pictures to help them so they don’t ever have to guess.
    • Use clearance planes. A lot of problems happen when you mark some stuff out and then it drives through the part. If you use clearance planes it kind of modularizes your program, where you can mark stuff out without worrying about the move points between features.
Reply
  • This is a little late to the party, but this is what works for us. Our operators don’t break tips very often. The programmers break most of the tips.
    • Operators most frequently break tips when they either setup the fixturing/part wrong or are running the wrong program. Putting a picture of the setup into your program solves both of these problems. When they have it setup wrong, the picture pops up and it doesn’t look right, they can make corrections before the CMM starts to move.
    • All programs that are meant for measuring production parts should be stored in a write protected folder. This protects from operators/programmers accidentally making changes and then those changes get saved into the program. Furthermore, PC-DMIS is constantly saving and overwriting the programs. Occasionally through no operator interaction, it can save something dumb in the program that causes you chaos. Don’t let it overwrite your known good programs. Write protect the folder at the OS level.
    • Minimize the chance of the operator running the wrong programs. Have separate areas for “Production Ready” programs, “Archives” of older programs, and where you develop new programs. The operators should only ever be operating out of the “Production Ready” folder and it should only have the one program that they should be running. Old versions and experimental versions should be in the archive or developmental areas.
    • Fixturing -> Rough Alignment -> Part Program. Ideally the entire program runs in DCC. The less you ask an operator to do the less problems you’ll have. You need to find a way to ensure that the part is always in the same location on the CMM. The best way to do this is with fixturing. Then the program performs a rough alignment to find the part using larger approach and retract distances. Then inspect the part after the program knows exactly where the part is. All of our parts are roughly the same size, so we have a corner nest on the CMM that all the fixtures nest into. Our operators put the part into the fixture, put the fixture into the nest, and then run the program, and then a picture pops up and they verify everything looks right and click OK, and then the program just runs. If you really need to have the operator measure the part at all, use pictures to help them so they don’t ever have to guess.
    • Use clearance planes. A lot of problems happen when you mark some stuff out and then it drives through the part. If you use clearance planes it kind of modularizes your program, where you can mark stuff out without worrying about the move points between features.
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement