Robot software: Difference between revisions

Revision as of 15:36, 1 January 2019

Revision as of 20:03, 28 January 2019

Line 23:

Due to the highly [[Proprietary software|proprietary]] nature of robot [[software]], most manufacturers of robot hardware also provide their own software. While this is not unusual in other automated [[control systems]], the lack of standardization of programming methods for robots does pose certain challenges. For example, there are over 30 different manufacturers of [[industrial robots]], so there are also 30 different robot programming languages required. There are enough similarities between the different robots that it is possible to gain a broad-based understanding of robot programming without having to learn each manufacturer's proprietary language.<ref>{{Cite news|url=http://coro.etsmtl.ca/blog/?p=529|title=The future of robot off-line programming|date=2015-10-25|newspaper=CoRo Blog|access-date=2017-01-03}}</ref>

One method of controlling robots from multiple manufacturers is to use a [[Post processor]] and [[Off-line programming (robotics)]] software. With this method, it is possible to handle brand-specific robot programming language from a universal programming language, such as [[Python (programming language)]].<ref>{{Cite web|url=https://www.robodk.com/offline-programming|title=Offline programming - RoboDK|last=RoboDK|website=www.robodk.com|access-date=2017-01-03}}</ref> however, compiling and uploading fixed off-line code to a robot controller doesn't allow the robotic system to be state aware, so it cannot adapt it's motion and recover as the environment changes. Unified real-time adaptive control for any robot is currently only possible with [[Actin_(software)|Actin]].<ref>{{Citea web|url=https://www.energid.com/actin|title=Actin®few different Realthird-Timeparty Adaptive Online Robot Control|last=Energid|website=wwwtools.energid.com/actin|access-date=2018-07-30}}</ref>

Some examples of published robot programming languages are shown below.