I am leery of any software that claims to replace an experienced technician.
I have seen software that allowed a programmer to drive a CNC so hard that the tool melted the aluminum rather than cutting chips.
I also saw a CNC machine boring a 9/16' hole through a piece of 1/2" aluminum without a center drill or a pilot drill. An experienced tool maker or machinist would cringe at this description. I was called in because they wondered why the spindle bearings were sloppy.
And I have seen robotic welding applications programmed by 'computer geeks'.
Software cannot, in my experience, replace an experienced technician, but software can make an experienced technician more productive. It seems only a technician can appreciate the value of the skills of another technician.
If anyone has any specific questions pertaining to robotic welding, programming or any other questions I am a robotic welding programmer for a large company in the Midwest. I use Panasonic, Fanuc, and ABB robots currently, and experience with Epson and Kawasaki material handling. Worked with Vision for a month, but do not have much knowledge on that other than all of the problems we had with it.
As to options for small companies who want to start up with a robotic department, a great solution is simple... BUY USED! Robot cells are like cars, as soon as they step off the car lot they lose half of their value. The robots I work with range from 2003 all the way back to 1993. The ABB was our oldest robot and ALL do what we want them to do. We actually just sold our ABB which I believe should be in a museum being that it was sooo old! To back up the programs I had to use Floppy disks! haha
William, your description of programming robots by hand makes it sound excruciating, and even more demanding and tedious than coding a machine vision application. Although this package is for the low end of robotic welding applications and therefore would require simpler programming, as Chuck points out.
I like your "plant-as-a-video-game" image, Rob. This same trend has come into machine vision during the last few years. Development software for vision apps is usually sold with both types: a GUI and a "real" programmers' interface for writing your own code.
A base robot that costs less than a welder for a year would almost certainly have constraints on the number of applications it could serve. But for those applications where it fits, it would seem almost impossible to pass on, especially if it offers a long-reliable lifetime.
This is a great development, and it should wind up making automating even short production runs economical. Programming these robots will wind up being the one thing that is a cost item. I have done robot programming in the manual mode, which is an intensely exacting process. Moving to each position with the required precision is quite tedious. Model based robot programming is a whole different realm, from what I understand. But it would seem that it may be better setting up a welding path on an actual part.
Pretty cool, Ann. That whole point-and-click figuration and set-up is becoming more popular through the automation world. It's part of the whole plant-as-a-video game trend. Smart devices has helped the effort, and now apparently robots become an easier set up as well. This approach certainly keeps costs down.
For industrial control applications, or even a simple assembly line, that machine can go almost 24/7 without a break. But what happens when the task is a little more complex? That’s where the “smart” machine would come in. The smart machine is one that has some simple (or complex in some cases) processing capability to be able to adapt to changing conditions. Such machines are suited for a host of applications, including automotive, aerospace, defense, medical, computers and electronics, telecommunications, consumer goods, and so on. This radio show will show what’s possible with smart machines, and what tradeoffs need to be made to implement such a solution.