We've encountered this issue a number of times, with various pieces of safety equipment. we initially blamed it on the pulse testing used on many safety outputs, like the blips you're seeing here. However, even with pulse testing turned off, we've seen 'phantom' safeguard and emergency stops occur. UR support have advised us this is a result of using OSSD or semiconductive outputs. We've addressed this issue by using a safety relay to filter the signals going to the robot. This also has the advantage of allowing you to reset the relay rather than the UR, and save some I/O. It is also possible to purchase Low Pass Filter terminal blocks from Pilz, which have worked for us in the past.
Hello DoF Community,
I am working on a project where I am using a UR10 Universal Robot. I want the station to operate as normal and have a SICK S300 Laser Floor Scanner wired into to Robot Controller dedicated safety I/O. When the floor scanner area is entered. I want the Robot to go into safeguard stop and be prevented from moving until the area is clear and the safeguard stop is reset.
The issue I am seeing is that I am seeing the robot hesitate and enter safeguard stop when nothing is in the floor scanner area. It seems that I am seeing a blip on the voltage every 125ms which I can see on oscilloscope which causes the robot to enter safeguard stop and then need resetting.
Should I be able to wire a scanner like this directly into the Safety Controller, or do I need to do anything with the signal coming from the floor scanner. Does anyone have any experience of using this type of floor scanner wired directly into the robot safety controller. I am reluctant to wire it differently as to me the safest way is floor scanner signal directly into the safety on the robot controller.
Thanks for any help
Jack