In the RT-middleware, robotics elements, such as actuators, are regarded as RT-components, and the whole robotic system is constructed by connecting such components. This distributed architecture helps developers reuse the robotic elements and boosts the reliability of a system.
Each RT-component has a port as an endpoint for communicating to other RT-components. Every port has its type and the ports which have the same type can be connected each other.
RT-components also have state, so they behave as finite-state machines. The states they can have are: CREATED, INACTIVE, ACTIVE, and ERROR. States and behaviors are controlled by the execution-context. If component behavior must be changed, the execution-context can be replaced at runtime.
RT-middleware is only a standard of the Robotics platform software. Implementations include:
Ando, Noriaki; Suehiro, Takashi; Kitagaki, Kosei; Kotoku, Tetsuo; Yoon, Woo-Keun (August 2005). RT-Middleware: Distributed Component Middleware for RT (Robot Technology). IEEE/RSJ International Conference on Intelligent Robots and Systems (IROS2005). Edmonton, Canada. pp. 3555–3560. /wiki/Edmonton ↩
"Robotics Technology Component Specification version 1.0". Object Management Group (OMG). http://www.omg.org/spec/RTC/1.0/ ↩
OpenRTM-aist official website, http://www.openrtm.org/ https://www.openrtm.org/ ↩
SEC. Co., Ltd., [SEC, Robot Site http://www.sec.co.jp/robot/download_rtm.html] http://www.sec.co.jp/robot/download_rtm.html ↩
SEC. Co., Ltd., [RTM Safety http://www.sec.co.jp/english/business/rtmsafety/] http://www.sec.co.jp/english/business/rtmsafety/ ↩
"ROS – Robot Operating System". ROS.org. https://www.ros.org/ ↩
"willowgarage.com". Willow Garage. http://www.willowgarage.com/ ↩
Orocos.org http://www.orocos.org/ ↩
"OPRoS". 3 January 2011. Archived from the original on 2011-07-04. https://web.archive.org/web/20110704131738/http://210.115.36.125:8001/opros_en/dokuwiki/doku.php ↩
"KAR". Korea Association of Robot Industry. https://www.korearobot.or.kr/ ↩