Abstract:
In an apparatus for sharing device resources between robot software user components, a callback module of a robot software user component receives data forwarded from a device set to be shared between the robot software user components, a device service surrogate has a connection with a framework to forward data to the device or forward data received through the callback module to a user program of the user components; a device service surrogate manager manages the device service surrogate of each of the user components; a device channel has a connection with the device to receive data therefrom and transmit data thereto; and a device channel manager manages the device channel and connect the device channel and the device service surrogate.
Abstract:
An apparatus for processing an error of a robot component includes an event reception unit configured to receive event information; and an error detection unit configured to analyze the event information to determine whether there is a component where an error occurs from among the multiple components.Further, the apparatus includes a component relationship analysis unit configured to analyze the dependency relationship between a component where an error occurs and the remaining components and the importance of the dependency relationship and to detect a component associated with the component where an error occurs; and an error recovery management unit configured to manage an error recovery plan and the component detected by the component relationship analysis unit.
Abstract:
An apparatus manages robot components in a robot. The apparatus includes a component monitoring unit to monitor a state of the robot components and a breakdown decision unit to judge whether or not any robot components are broken down based on the monitoring results and generate breakdown information corresponding to the breakdown decision results. The apparatus further includes a recovery policy management unit to choose a recovery policy model necessary to recover the breakdown using the breakdown information and a breakdown recovery unit configured to recover the broken robot component based on the chosen recovery policy model.
Abstract:
In accordance with an embodiment, when robot service developers develop the component-based robot software, they are able to select a tight coupling or a loose coupling to develop the component-based robot software and connect the components in compliance with the coupling types that are supported by the components in the component combination tool for combining the components. Therefore, it is possible to make a robot application system in which the components having different coupling types are used all together.