Robot control software architecture

Shapiro Wiley, New York pp. Khatib: Real-time obstacle avoidance for manipulators and mobile robots, Proc. Arkin: Integrating behavioral, perceptual, and world knowledge in reactive navigation, Robot. Arkin, T. Thesis Yale Univ.

Bonasso: Integrating Reaction Plans and layered competences through synchronous control, Proc. Rosenschein, L. Kaelbling: The synthesis of digital machines with provable epistemic properties, Proc.

Kaelbling: Goals as parallel program specifications, Proc. Bonasso, R. Firby, E. Gat, D. Kortenkamp, D. Miller, M. Slack: Experiences with an architecture for intelligent, reactive agents, J. Gat: Integrating Planning and reacting in a heterogeneous asynchronous architecture for controlling real-world mobile robots, Proc. Saridis: Architectures for Intelligent Controls. Alami, R. Chatila, S. Fleury, M.

Ghallab, F. Ingrand: An architecture for autonomy, Int. Ghallab, H. Laborie, M. Ghallab: Planning with sharable resource constraints, Proc.

Georgeff, F. Ingrand, R. Chatila, R. Alami, F. Muscettola, P. Nayak, B. Pell, B. Williams, P. Man Cybernet. Sellner, F. Heger, L. Hiatt, R. Simmons, S. Goldberg, V. Cicirello, M. Dias, R. Smith, A. II, ed. Schultz, L. Parker, F. Schneider Kluwer, Dordrecht Google Scholar. Albus, R. Lumia, H. Blidberg, S. Ocean Eng. Volpe, I. Nesnas, T. Estlin, D. Mutz, R. Petras, H. Nesnas, R. Simmons, D. Gaines, C. Kunz, A. Diaz-Calderon, T. Estlin, R. Madison, J. Guineau, M. McHenry, I.

Shu, D. Chouinard, F. Fisher, R. Judd, R. Anderson, I. Knight, G. Rabideau, S. Chien, B. Engelhardt, R. Chouinard, R. Bornstein, M. Judd, I. Musliner, E. Durfee, K. Shin: World modeling for dynamic construction of real-time control plans, Artif.

Musliner, R. Goldman, M. Kapellos, M. Berry, G. Gonthier: The Esterel synchronous programming language: Design, semantics, implementation, Sci.

Jourdan, F. Maraninchi, A. Olivero: Verifying quantitative real-time properties of synchronous programs, Proc. Pardo-Castellote, S. Kaelbling: Rex- A symbolic language for the design and parallel implementation of embedded systems, Proc. Gat: On the role of stored internal state in the control of autonomous mobile robots, AI Mag. Currie, A. Tate: O-Plan: The open planning architecture, Artif. Nau, Y. Cao, A. Lotem, H. Chien, R. Knight, A. The robot in the next work cell might be dispensing adhesive so will have a different graphical user interface even if the software is identical to the painting work cell.

Each application has a common base architecture somewhat like the operating system for personal computers which gives a computer a level of functionality. The software then verges off to the application area, such as Excel, Word or Outlook. Robot manufacturers drive to have the function of the robot match the application and make the software architecture seamless.

Wixom, Michigan. Robots with increased dexterity and those with unique link and joint configurations meet specific application needs for wafer-handling, car body transfer, non-destructive testing, confined area welding and palletizing. Tool changers have control modules. The first tool changer we designed used DeviceNet, the standard for several companies.

DeviceNet evolved over the last 15 years but companies have moved towards Ethernet or Profinet. Commonality puts more complication onto tooling vendors but less complication onto the robot. Pleasanton, California.

Robot companies spend a lot of time and money proving out their hardware and software solutions for safety and robustness. When your personal computer crashes, does a two-ton iron arm swoop down and take out your living room wall?

That possibility gives robot manufacturers pause when designing the system. These are low-priority tasks in a robot application but high priority to someone using a personal computer. Off-the-shelf personal computers are not as effective as a purposely-built robot controller because the quality is not up there and does not have high enough reliability. Into the Open Software architecture of industrial robots tend to be proprietary and dedicated to that specific robot make.

While proprietary robot software will not go away anytime soon, a trend towards open source robot operating systems got a big boost with the advent of the Robot Operating System-Industrial ROS-I. Because of this permissive software license, ROS can be deployed for commercial and proprietary applications. ROS-I extends that open source model into the industrial realm. The research community is often several years ahead of offerings by commercial robot vendors, and ROS-I provides the bridge to leverage that new research on existing industrial platforms.