# Has anyone seen a robot ignore an input in the system I/O?

**URL:** <https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332>\
**Category:** Robot Controller\
**Tags:** rapid-continues-running, system-i-o, ignores-stop-command\
**Created:** [August 29, 2016, 8:02pm UTC](https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332 "2016-08-29T20:02:34Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![usfrcra](https://avatars.discourse-cdn.com/v4/letter/u/9fc348/32.png) [@usfrcra](https://tech-community.robotics.abb.com/u/usfrcra)\
**Post date:** [August 29, 2016, 8:02pm UTC](https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332/1 "2016-08-29T20:02:34Z")

</div>

I have a stop command setup in the system I/O, coming from a PLC. I verified the output at the PLC and I watched the input toggle from 0 to 1 on the Flex Pendant. However the rapid would continue to stay in the running state. After I verified the physical I/O was working properly and didn’t know what else to check; I powered down the robot controller and powered back up; the stop command worked as assigned after that.

---

<div class="post-metadata">

**Author:** ![graemepaulin](https://avatars.discourse-cdn.com/v4/letter/g/258eb7/32.png) [@graemepaulin](https://tech-community.robotics.abb.com/u/graemepaulin)\
**Post date:** [August 30, 2016, 9:05am UTC](https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332/2 "2016-08-30T09:05:12Z")

</div>

When you make changes to a configuration file you need to restart the controller for the change to take effect - so if you did not do the restart after adding the system input that will be why it only stated working after your fault finding and restart.

---

<div class="post-metadata">

**Author:** ![usfrcra](https://avatars.discourse-cdn.com/v4/letter/u/9fc348/32.png) [@usfrcra](https://tech-community.robotics.abb.com/u/usfrcra)\
**Post date:** [August 31, 2016, 12:18am UTC](https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332/3 "2016-08-31T00:18:21Z")

</div>

This configuration had been already in the system for around a year, and was previously working.  
No changes to a configuration had been made in many months.

---

<div class="post-metadata">

**Author:** ![graemepaulin](https://avatars.discourse-cdn.com/v4/letter/g/258eb7/32.png) [@graemepaulin](https://tech-community.robotics.abb.com/u/graemepaulin)\
**Post date:** [August 31, 2016, 2:49am UTC](https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332/4 "2016-08-31T02:49:21Z")

</div>

OK that makes a difference!

Very hard to say why it would stop working, but a restart would refresh the internal mapping.

---

<div class="post-metadata">

**Author:** ![usfrcra](https://avatars.discourse-cdn.com/v4/letter/u/9fc348/32.png) [@usfrcra](https://tech-community.robotics.abb.com/u/usfrcra)\
**Post date:** [September 1, 2016, 4:46pm UTC](https://tech-community.robotics.abb.com/t/has-anyone-seen-a-robot-ignore-an-input-in-the-system-i-o/7332/5 "2016-09-01T16:46:19Z")

</div>

I am thinking that it is just like in any other computer; Windows for example, sometimes you can select something and it took forever to respond or never responded at all.  
Sometimes it freezes, you know its working in the background but your helpless at doing anything so you need to reboot.  
I wonder if there are recommended intervals like every week or month; when you should just reboot the system; give it a clean bill of health.