Discussion...On controlling a Robot via PLC

taward31

Member
Join Date
Nov 2012
Location
Dublin
Posts
51
Hey Everyone,

I have a project that involves controlling a Abb Robot there is also a siemens plc and HMI and a Omron Vision controller,

The project has been done previously by the company I work for.

The only difference is that this time I am integrating vision to speed up the process.

The old code literally only uses the PLC for recipe selection via the HMI and Fault status and resolution etc. Basically the robot sequence is programmed entirely in the Robot controller

What I would like is people's opinion on what way you would approach this project,

My thoughts would be to control the robot via the PLC being a master.
I.e Calling small sub-routines via a PLC sequence and waiting for them to be completed before moving on.

Is there any major advantages/Disadvantages in either method

Thanks in advance

look forward to hearing you guys opinion
 
We have a ABB robot with CLX, PV+ and Sick camera. The PLC is used to call routines in the robot and handles the camera signal. The advantage for us was that as it was our first proper robot it made it simpler for the shift electricians to fault find. Also it made the integration with the camera more straight forward.
 
I set up robot cells all the time, and I make the PLC the master always.
My main objective is to keep the operators away from the teach pendant, and give them a user friendly interface on the HMI with whatever they need to run the cell. The robot controller controls only the movements, all the decision making I do in the PLC.
If you are going to use vision, then you possibly need conveyor tracking too which is an expensive option from ABB.
What model of robot are you using?
 
Hey Everyone,

I have a project that involves controlling a Abb Robot there is also a siemens plc and HMI and a Omron Vision controller,

The project has been done previously by the company I work for.

The only difference is that this time I am integrating vision to speed up the process.

The old code literally only uses the PLC for recipe selection via the HMI and Fault status and resolution etc. Basically the robot sequence is programmed entirely in the Robot controller

What I would like is people's opinion on what way you would approach this project,

My thoughts would be to control the robot via the PLC being a master.
I.e Calling small sub-routines via a PLC sequence and waiting for them to be completed before moving on.

Is there any major advantages/Disadvantages in either method

Thanks in advance

look forward to hearing you guys opinion

ABB has a software package option called IFWC Frameworks that some of my customers use with Siemen's PLCs (actually any PLC that can be a support a fieldbus). The idea is that the robot is used the same way a simple servo is used; strictly for moving from one point to another, albeit the robot has multiple servos allowing complex pathes. All logic decisions are made in the PLC and thus decides when the robot makes the next move.

Example: From a HOME position, the PLC decides when the robot should move to a POUNCE position, tells the robot to move to the POUNCE position and the robot stops and waits for the next command from the PLC. The PLC makes the logic decision to move to the WORK position and tells the robot when its okay to move. Etc, etc,etc.

The idea is that the PLC is much better suited to make the logic decisions that a cell needs for handling materials and easier to edit. The robot basically gets turned into a glorified servo controller, with its only responsibility is to move from one point to the next. Even the control of any End-of-arm-tools is controlled by the PLC. Robot projects that I do with Ford, GM, and FCA all use the same idea and Ford will most often specify to use Frameworks, GM has their robot template that is very similar, and FCA is okay with rolling your own but requires the same architecture.

Hope this helps.
 
I set up robot cells all the time, and I make the PLC the master always.
My main objective is to keep the operators away from the teach pendant, and give them a user friendly interface on the HMI with whatever they need to run the cell. The robot controller controls only the movements, all the decision making I do in the PLC.
If you are going to use vision, then you possibly need conveyor tracking too which is an expensive option from ABB.
What model of robot are you using?

Thanks for the opinion, No We are using the vision for position locations of straps that are to be cut of the top a pallet to allow for the to depalletized, Its stationary so no need for conveyor tracking

Yeah I get that, That would be my thinking as well PLC as master would be so much easier to fault find and run via the HMI,

Everything is Expensive from ABB :mad:
 
ABB has a software package option called IFWC Frameworks that some of my customers use with Siemen's PLCs (actually any PLC that can be a support a fieldbus). The idea is that the robot is used the same way a simple servo is used; strictly for moving from one point to another, albeit the robot has multiple servos allowing complex pathes. All logic decisions are made in the PLC and thus decides when the robot makes the next move.

Example: From a HOME position, the PLC decides when the robot should move to a POUNCE position, tells the robot to move to the POUNCE position and the robot stops and waits for the next command from the PLC. The PLC makes the logic decision to move to the WORK position and tells the robot when its okay to move. Etc, etc,etc.

The idea is that the PLC is much better suited to make the logic decisions that a cell needs for handling materials and easier to edit. The robot basically gets turned into a glorified servo controller, with its only responsibility is to move from one point to the next. Even the control of any End-of-arm-tools is controlled by the PLC. Robot projects that I do with Ford, GM, and FCA all use the same idea and Ford will most often specify to use Frameworks, GM has their robot template that is very similar, and FCA is okay with rolling your own but requires the same architecture.

Hope this helps.

Think you guys have convinced me,

Better to rewrite the code the right way 🔨 than to copy and paste and continue poor practices . Cheers
 

Similar Topics

What's the best way to use lots of MSG instructions in the same program? Both multiple messages with the same device, and other devices. I've read...
Replies
10
Views
1,174
Hi, I have a Master Thesis to write and my topic is Vertical Bag Packing Machine with continuous cycle. I am almost done with the mechanical...
Replies
16
Views
4,799
Hello all, There comes a time in everyone's career when you have to say enough is enough. That day for me is today. My manager is currently 630mi...
Replies
27
Views
8,714
Yup, that whole IOT 4.0 thing. Do you folks use a security gateway or router? In plants where there are isolated islanded networks that you may...
Replies
7
Views
2,318
So Last week there was a discussion on new laptop options. Looking at new ones got me trying to strategize as best I can when I also have to make...
Replies
1
Views
2,297
Back
Top Bottom