February 2021 Volume 3

AUTOMATION

Think of it this way, if you had a handful of welders in a shop, most of the time the best welder in the group has to do with the amount of experience they have or amount of time they put into perfecting their craft. If you asked the group, they could all tell you who is the best and why. In that group, there is always a couple of young guys who admire and want to be THAT GOOD , almost like a badge of honor. No doubt they will get to that level at some point. I’ve heard a few guys who have come through my class say they think the robot is their opportunity to improve in their industry. Surprisingly, it isn’t just young programmers saying that. Younger programmers will look at the robot and see an opportunity or a fast track to being recognized within the company. While an older programmer candidate may look at the robot as an opportunity to explore technology and try something new. Some guys coming through my class have been in the industry for well over 25 years, doing the same thing over and over. They feel like the robot may be something exciting to get behind and change up the day-to-day. Sending your best guy to learn to program isn’t always a bad idea. When a company sends their very best and most experienced guy to learn the new robotic system, they still can do very well. In fact, their process knowledge can’t be matched. A huge part of having a successful robotic install is a solid understanding of the parts and production of those parts. The point that I’m trying to make is, age doesn’t matter. Not nearly as much as putting someone behind the pendant that wants the robot to be successful. Anyone can be trained if they want to be. If it is your first robot, you want that programmer to have their full attention to the system. In a job shop, we want someone who wants to champion the equipment. I’m looking for the person who is driving the success of this system and looking to add more parts for the robot to do. I typically encourage whoever comes to training that if they are not the subject matter expert, to identify and lean on whoever is the best for process knowledge. For instance, if a programmer is lacking

in the welding process, knowing who to turn to in order to reduce spatter or undercut while having the knowledge and knowing where to navigate in the teach pendant to adjust the program. From there, take good notes on what recommendations that person has so later you can duplicate that on other programs. I’m a big advocate that you don’t have to know every piece of detail to get started, but you do have to know where to turn to ask questions and not be afraid to ask them. The other suggestion has always been to train at least two people at a time to learn to program your system. Going through training is like drinking water through a fire hose. In most cases, training is packed into 3- 5 days. By having the two people go together, one might pick-up information that the other didn’t and vice versa. The key point I hope you take away from this article is: A great programmer has to do with the willingness to try, the desire to see it be successful, and a working knowledge of that process and parts. Unfortunately, there isn’t a cookie-cutter answer for programming. For some applications, buying a system turnkey could be the best answer. It could also be that developing talent within to champion the equipment could provide the best solution. And remember, play to people’s strengths over focusing on their age. ■ Brennan Palmiter Independent Applications Engineer / Robotic consultant Phone: 386-527-0757 Email: Brennan@faaspaas.com

FIA MAGAZINE | FEBRUARY 2021 26