Report points to ASTM Committee F48 Exoskeletons and Exosuits; ISO TC 299 Robotics; and IEEE Wearable Robots
Provides an Overview on Projects and Programs on COLLABORATIVE ROBOTS
The purpose of the Robotics Domain Task Force is to foster the integration of robotics systems from modular components through the adoption of OMG standards.
The scope of this Technical Report is to provide test methods and metrics for validating separation distances of robot applications using Speed and Separation Monitoring (SSM) in accordance with ANSI/RIA R15.06 and RIA TR R15.606. This Technical Report also provides guidance on determining how speeds and positions of robot systems, workpieces, and obstacles should be measured, and under what conditions such measurements should be made.This document is informative in nature and is not a standard. The use of the word “shall” and “should” in a particular statement indicates the relative importance of specific criteria or features indicated in ANSI/RIA R15.06, RIA TR R15.606, and RIA R15.08.
This community group will discuss the applications of web browsers as the computer for controlling robots (robotics, in other words). And it will be also intended to feedback knowledge obtained from this discussion to standardization activity about Web of Things.What kinds of values are contained in using a Web browser not only in drawing graphical user interface but also in controlling and manipulating robots, and what kinds of difficulties and problems are there in that case? To search their answers may become the driving force of this activity.As an example, there may be the following questions in the discussion:Is a case applying a Web browser as a simple controller of the robots which does not have UI such as screens or the pointing devices still meaningful? For example, connectivity with web services and interlocking operation between robots (Swarm Robotics via web) may be one of its values.Is it possible to relate a graphical user interface of HTML to interactive and physical user interface of the robots? Is it meaningful? As an example, a relation between a physical push button and 'input' type="button" element in the HTML may deserve considering.Are cases using relatively low-level interface used in many robots such as PWM of the motor, digital or analog signal interfaces, I2C, SPI, UART and GPIOs by the application on the web browsers meaningful?Is real-time computing at the same level as RTOS feasible on the web browser-based general-purpose computing environments?An initial related activity is the Mozilla Factory Open Hardware Project.Furthermore, this group may publish specifications based on those knowledge such as webGPIO, webI2C API and so on.
This standard extends the IEEE 1873-2015™ Standard for Robot Map Data Representation from two-dimensional (2D) maps to three-dimensional (3D) maps.
This Guide for Verification of Autonomous Systems enables the user to define a customized process for verification of their autonomous system based on their available resources. It documents best practices across all levels of abstraction within a given system.
ISO 15536-1:2006 provides temperature threshold values for burns that occur when human skin is in contact with a hot solid surface. It also describes methods for the assessment of the risks of burning, when humans could or might touch hot surfaces with their unprotected skin.In addition, ISO 13732-1:2006 gives guidance for cases where it is necessary to specify temperature limit values for hot surfaces, but does not set surface temperature limit values.ISO 13732-1:2006 deals with contact periods of 0,5 s and longer.It is applicable to contact when the surface temperature is essentially maintained during the contact.It is not applicable if a large area of the skin (approximately 10 % or more of the skin of the whole body) can be in contact with the hot surface. Neither does it apply to skin contact of more than 10 % of the head or contact which could result in burns of vital areas of the face.ISO 13732-1:2006 is applicable to the hot surfaces of all kind of objects: equipment, products, buildings, natural objects, etc. It is applicable to hot surfaces of products that may be touched by healthy adults, children, elderly people and also by people with physical disabilities. For the purposes of simplification, it mentions only products; nevertheless, it applies to all other objects as well. It is applicable to products used in any environment, e.g. in the workplace, in the home.It does not provide data for the protection against discomfort or pain.
This standard defines an ontology that allows for the representation of, reasoning about, and communication of task knowledge in the robotics and automation domain. This ontology includes key terms as well as their definitions, attributes, types, structures, properties, constraints, and relationships. It will address the way that hierarchical planners represent task knowledge which will allow them to better communicate among levels of the ontology hierarchy.
A set of ontologies with different abstraction levels that contain concepts, definitions, axioms, and use cases that assist in the development of ethically driven methodologies for the design of robots and automation systems is established by this standard.
A map data representation of environments of a mobile robot performing a navigation task is specified in this standard. It provides data models and data formats for two-dimensional (2D) metric and topological maps.
This standard extends IEEE Std 1872-2015, IEEE Standard for Ontologies for Robotics and Automation, to represent additional domain-specific concepts, definitions, and axioms commonly used in Autonomous Robotics (AuR). This standard is general and can be used in many ways--for example, to specify the domain knowledge needed to unambiguously describe the design patterns of AuR systems; to represent AuR system architectures in a unified way; or as a guideline to build autonomous systems consisting of robots operating in various environments.