Not too long ago, there was a extensively publicized incident the place a chess robotic system broke the finger of a seven-year-old youngster at a match in Moscow. This could by no means have occurred. The robotic was not considered one of our cobots, however we do really feel compelled to remark as a result of this robotic chess software does NOT mirror regular security requirements and well-accepted practices throughout the robotics sector.
The best way this incident was reported can distort understanding of robotics software security. An official of the Russian chess federation implied that the incident occurred as a result of the kid ‘violated’ security guidelines. That is totally unreasonable!
Robotic system integrators ought to carry out a threat evaluation
It’s globally accepted that robotic system integrator ought to carry out a threat evaluation for the supposed use and readily foreseeable misuses. If this had been performed, quite a few modifications would have been carried out together with a comfortable gripper as an alternative of 1 with exhausting edges and the usage of security sensors solely permitting motion when nobody was close by. It was fairly foreseeable that the human chess participant could be concentrating on the sport, not their robotic opponent.
Automation security is about “making the simple technique to work, the secure technique to work”. On this case, all chess motions want to have the ability to be carried out with no particular person needing to assume “am I okay to maneuver my chess piece or will I be injured?”.
The know-how exists to forestall incidents like this from taking place
Energy and drive restricted (PFL) collaborative robots (cobots) would cease transferring after contact with an individual. Know-how of this kind is available. Following the applying threat evaluation’s necessities, tens of 1000’s of cobots are working safely alongside people day by day. The truth is, cobots are more and more utilized in training settings to show programming and the event of robotic purposes.
Security requirements are established internationally and independently licensed
All respected robotic producers and integrators embrace their duty of delivering secure merchandise and options. At Common Robots, our e-Sequence robots are licensed to EN ISO 13849-1 and EN ISO 10218-1 by TÜV Nord. The cobots embody 17 superior configurable security capabilities licensed by TÜV Nord as PLd Cat 3. This implies they’ve configurable stopping time and stopping distance, joint place limits, pose restrict, instrument orientation restrict, security planes, security boundaries, secure dwelling, drive limiting (TCP) and elbow security (drive, pace, boundary restriction).
The secure deployment of cobots can convey enormous societal advantages
This chess enjoying robotic integrator displays badly upon the 1000’s of automation professionals that take security very severely. The world continues to face labor shortages. Robotics and automation can present a vital and well timed resolution and can even make workplaces significantly better environments for people to work in. However these alternatives will solely be absolutely realized when security is a precedence in software deployment.
