This standard applies to household robots and provides performance testing and evaluation method to common feature of various household robots.This standard is neither concerned with safety nor with performance requirements.
This standard is applicable to dry cleaning robots for household use in or under conditions similar to those in households.The purpose of this standard is to specify the essential performance characteristics of dry cleaning robots and to describe methods for measuring these characteristics.This standard is neither concerned with safety nor with performance requirements.
This standard is applicable to dry cleaning robots for household use in or under conditions similar to those in households.The purpose of this standard is to specify the essential performance characteristics of dry cleaning robots and to describe methods for measuring these characteristics.This standard is neither concerned with safety nor with performance requirements.
Scope of document is to identify, select and describe use cases where the IoT data and services require data usability specifications for machines consuming data for AI (for example machine learning). Enabling data usability with AI approach will also be considered. It includes Use Cases pertianing to Robots
This document specifies the necessary system hardware components, the characteristics, the component requirements and conditions for the application of robotic ultrasonic test systems.This document specifies the general requirements and acceptance criteria for robotic ultrasonic test systems.This document is applicable to robotic ultrasonic test systems composed of one or more robot(s).This document is applicable to conventional straight beam probes and immersion technique.This document is also applicable for phased array probes but then additional tests can be necessary.
This document describes methods of specifying and evaluating the manipulation performance of service robots, notably:— grasp size. — grasp strength. — grasp slip resistance. — opening a hinged door; and— opening a sliding door.There are other grasping characteristics and use cases for manipulation of service robots. It is expected that these will be included in a future revision.This document deals with the indoor environment only. However, the depicted tests can also be applicable for robots operating in outdoor environments.This document is not applicable for the verification or validation of safety requirements.
Describes the requirements and architecture for an indoor conversational robot system. This Recommendation defines different functions to support indoor conversational robot systems.
This protocol can be used to validate the weight support level for Weight Support Systems used in the healthcare domain, where the amount of weight support can be varied by a therapist according to the need for the therapy of a subject .
This protocol can be used to validate the weight support level for Weight Support Systems used in the healthcare domain, where the amount of weight support can be varied by a therapist according to the need for the therapy of a subject.
This protocol can be used to validate the ability of a Weight Support System, used in the healthcare domain, to prevent falls by limiting the Range of Vertical Motion.
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.
Implications of standardization to BioMot - Smart Wearable Robots with Bioinspired Sensory-Motor Skill