Currently, there are no clear programming paradigms programming robotic systems, according to some authors the programming techniques which are common use today are not adequate to seal with the complexity associated with these systems. One aspect where the complexity clearly come up is integration of software. It is necessary to integrate a wide variety of software in a given normally; software dealing with hardware (such as, effectors, sensors, and others hardware), third party software, software which is not very portable because it is specific to a particular machine or operating system (or both), software done in distinct programming languages. Traditional software integration has been an underestimated problem in robotics, and it is frequently a question to which it is necessary to invest much more effort than considered initially.
Integration of software system is a task demanding so many resources that only a few research groups can afford it. It seems evident that fostering cooperation and code reuse between different research groups would be the more convenient solution, but in a practice, it has been very seldom to see research groups importing systems or architectures that has been developed by others.
Recycling and reuse of code across laboratories is difficult and recently not very common. It is clear that robotics need to develop an experimental methodology that promotes the integration and reproduction of results and software between different research groups. The approaches originated by distinct groups have not been designed to be integrated together, and the software usually for control robotic system is not easy to use software. Its use and learning is not trivial, and getting to a level of expertise high enough to have productive results takes long time. All drives frequently to develop home made software the specific necessities of each group. Other authors have made similar considerations identifying the software architectures building as the way the robotics community has chosen mainly to address the problem.
- Jun (3)
- May (31)
- Apr (30)
- Mar (31)
- Feb (28)
- Next Robotics Generation in Logistics
- Adaptable and Reconfigurable Robotics Assembly
- Surgical and Interventional Robotics
- Robotics and Manufacturing Vignettes
- Robotics Priorities for Manufacturing
- Robotics as a Key Economic Enabler
- Modular Robotics Interface
- Molecube Mechanics of Modular Robotics
- Molecubes is a Low Cost Modular Robotics
- Distribution Options of RSS Projects
- Commercial Software in Robotic
- The Advantages of Separation DA Robotic Software
- The Arguments of Separation DA Robotic Software
- Source Code Size Estimate of Robotic Software Reus...
- Source Code Make up of RSS Project
- The Standardization of Interoperation Robotic Soft...
- Subjective Evaluation Result in Robotic Software R...
- Robotic Decisional Architectures
- CoolBOT Demonstrates on Activ Media Robotics
- The Standardization of Framework Software Robotic
- Robotic Reusable Software
- Software Components for Robotic Programming
- Robotic Software Programming
- CoolBOT Port Automata
- ARDev Mobile Robot Application
- The Observation Result of Android Robot
- The Developed Android Robot
- Robotic Development on Behavior and Appearance
- Fanuc Robotics of M-420iA and M-6iB/6S
- Laboratory Activities with Robotic Control through...
- ROTSE III Telescopic Robotic
- The Specification of Robotic Optical Transient Sea...
- Dec (31)
- Nov (31)
- Oct (31)
- Sep (30)
- Aug (31)
- Jul (31)
- Jun (2)
- Apr (5)
- Mar (11)
- Feb (12)
- Jan (43)