IRB 2600 Auto Stop Conflict

Create I/O input signal. Under configuration select System input then add you newly created input and select a stop condition.

Yeah... no...

While it technically would accomplish the job, you don't want to wire safety functions to system inputs.

Depending on the age of the controller it might be a different drawing set but look at this diagram and the run-chain.

(open the cabinet do you have black or silver drives ? back wall straight ahead)

https://abb.sluzba.cz/Pages/Pu…/3HAC024480-011_rev11.pdf

You want to use general stop for gate switches and light curtains.

Quote from SAABoholic

Yeah... no...

While it technically would accomplish the job, you don't want to wire safety functions to system inputs.

Depending on the age of the controller it might be a different drawing set but look at this diagram and the run-chain.

(open the cabinet do you have black or silver drives ? back wall straight ahead)

https://abb.sluzba.cz/Pages/Pu…/3HAC024480-011_rev11.pdf

You want to use general stop for gate switches and light curtains.

Display More

I agree to using the panel board but disagree about using the general stop for the gate switch. General stop also stops you in teach so you cannot go in through the gate to teach the robot. I would use auto stop for gate, light curtain is optional for whichever. Although it is annoying when one is teaching and some goober decides to break the light curtain and gives you a general stop.

Different school of thoughts I guess...

If you're in the cell programming and some dimwit decides to walk in without you knowing / seeing them, then it's quite convenient to have the gate on G-Stop so it stops the robot...

But what I am saying is that we should be the first ones entering through the gate. I think that I do recall working in some places where another gate opening would do like you are saying, and I suppose for the very reason you are talking about.