Certify products

Step 01: Get in touch with a UR+ team member to get more information, questions answered and the relationship up and running. You can find a contact list in the UR+ Contacts article.

Step 02: Solidify your go-to-market strategy for your product. Where are your target markets? How will you support your product?

Step 03: Develop and customize your product according to UR+ requirements. Read more details here. Confirm the requirements with your local contact before developing.

Step 04: Once developed, coordinate with the UR+ team in your area to schedule testing. Request a Product Submission Form to ensure all deliverables are in order.

Step 05: Review the testing report with your contact. Plan future iterations and develop a Product Lifecycle game plan.

Step 06: Work with the UR+ Ecosystem Manager in your area to publish your product page in the UR+ Showroom. Develop co-marketing activities and a launch plan.

For a certain product to qualify for the presence on the Universal Robots+ showroom and bear the "Certified by Universal Robots" logo, there are a number of criteria the product must comply with. The verification of this, is done via a certifying test of the product by Universal Robots. In general terms, a Universal Robots+ product is:

An accessory component OR APPLICATION KIT that expand or enhance the functionality of UR robots.

Meaning:

• • Accessory -hence not including the robot itself, not an OEM integrated solution
• • Expands functionality - e.g. EOAT new communication protocols, etc.
• • Enhance functionality - e.g. easier machine tending, more advanced palletizing etc.
• • UR Robots - customized to work directly / plug&play with UR

A certain level of customization is required to qualify, meaning that standard products that work using only standard interfaces on any robotic system may¹ does not fulfill the demands.

There are three major criteria for customizing UR+ products:

1. Use as minimum one, preferably all applicable interfaces (electrical, mechanical and/or software) to the UR robot.
2. The user interface should (if configuration or operation is needed) be done using UR's graphical user interface, PolyScope. This is done via a plugin called URCap. Your URCap can be developed with the URCap SDK. Meaning that any product that interacts with the robot application must interact using a URCap plugin.
3. Setting up the product should be plug & play, the product should be working flawlessly with the UR arms, and the overall user experience should be manageable to an inexperienced user. Remember that it must not compromise the robust operation of the robot or the accessory.

These three criteria should to the best extent be implemented for the product to be qualified for the UR+ Showroom.

Universal Robots is the #1 cobot brand with the key attributes:

+ Easy programming

+ Fast set-up

+ Reliable

+ Flexible deployment

+ Collaborative and safe

When a customer buys a UR+ product, they have the expectation that the UR+ product will have the same characteristics.

Products are verified for operation and functionality on the Universal Robots e-Series of robots.

It is mandatory to be compatible with this product, and the UR+ product can optionally be compatible with the CB3 generation of robots.

Almost any UR+ product will require a URCaps plugin, in order to qualify for certification. This is important since it is the best way to provide the user with a smooth, fluent, and hassle-free setup and user experience.

With respect to this certification, it is important to note, that the URCap must comply with the URCaps Style Guide, which outlines the styling URCaps should implement. If you are targeting to design GUI elements that are covering the screen area that is normally controlled by Polyscope, please consult your UR+ support contact for acceptance.

Also, it must be noted, that URCaps should to the best extent replicate the same look-and-feel, that the remaining PolyScope has. If you think you have a need to replicate a waypoint or something else, please get in contact with your UR+ support contact.

Designing a URCap requires understanding and knowledge about the UR robot and Polyscope. Please take the UR Academy free e-learning before getting started. You will get the optimal starting point by participating in the training. In addition to learning the robot, it will improve your insight into your coming customers’ mindset.

UR+ Products that do not require a URCap plugin:

• Teach pendant covers
• Robot Protective covers
• Off robot software
• Some safe components

End-effectors that the main application is handling must comply with these guidelines. This product type includes, but is not limited to electrical and pneumatic finger-grippers, suction cup tools, adaptive grippers, pneumatic pumps, or similar.

The attributes of a product that typically qualifies:

1. Mechanical interface: Product directly mounts to the UR Tool flange:
2. Electrical interface: Preferably to the UR Tool Connector (M8 8-pin) using standard IO or Tool Communication Interface. If Tool Connector is not possible, external cabling to Control Box (standard IO, Ethernet, USB). Current consumption must be within UR limits, or a compatible external power supply must be supplied.
3. Software configuration and operation: The end-effector must be configured directly from PolyScope, using a URCaps plugin. The end-effector must be operated through reasonable URCaps program nodes in PolyScope.
4. UR specific user instructions guide even the inexperienced user in setup, operation, and uninstallation.

Systems based on vision, laser, or similar, which applications include inspection, positioning, or object location.

The attributes of a product that typically qualifies:

1. Software configuration and operation:

• Calibration / alignment of the robot/camera coordinate system possible through URCap.
• Possibility to trigger, retrieve data, and perform application operations using URCap,
• Ability to configure vision task (teaching object to locate, configuring inspection task, etc.) using URCap.
• No external software required for basic configuration and operation.

2. Other attributes:

• If the product require external processing power, besides from what can be delivered from UR Control Box, an appropriate GPU/processing unit must be included.

3. Mechanical interface:

• If robot mounted, including mounting adapter to UR Tool flange.
• In external processing unit is mounted in Control Box, appropriate mounting is required.

4. Electrical interface:

• If robot mounted, connected to UR Tool connector (using Tool Communication Interface).
• If scene mounted, connected to Control Box interface (Ethernet, USB).

5. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category contains quick change systems for robot Tool and Base, including manual and automatic tool changers. Zero-position systems or systems that aid manual re-alignment of robot coordinate systems after relocation.

The attributes of a product that typically qualifies:

1. Electrical interface:

• Quick changers must implement pass-through for relevant cables (Tool Connector or Robot Cable).
• Electrical connections must not affect system performance.

2. Mechanical interface:

• Mechanical tolerances must not degrade system accuracy and precision.
• Duplicates Tool or Base flange dimensions on output-side.
• Base mounted units be robust, and withstand forces and torques as specified in UR User Manual.

3. Software configuration and operation:

• Automatic changers and re-alignment systems must include URCap integration, to aid configuration.
• Automatic changers and re-alignment systems must include URCap integration, to aid operation.

4. Other attributes:

• Tool changers can optionally include an ID system, to assure a correct end-effector is mounted
• Base changers can optionally ensure, that the correct robot installation file is loaded for the location.

5. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category contains products, which enhance the safety of collaborative robot systems. It could include laser scanners, safety mats, soft-touch suits, or others.

It should be noted, that beyond the product qualifying to be a safety enhancing product, the product must also comply with other applicable product types, not related to safety. This particularly relates to the software and mechanical integration of the system. Any product that require configuration, must still be done using a URCap plugin.

The attributes of a product that typically qualifies:

1. Electrical interface:

• The product must use relevant safety-rated Inputs or Outputs in the UR Control Box.

2. Safety features:

• An example risk assessment and/or a safety configuration guide must be included, to aid the user in performing necessary safety assessment of the complete system.
• The document must consider the complete system (typical application, UR robot, and the safety enhancing device).
• Compliance with relevant safety standards on same or safer levels than UR robot.
• Relevant safety certifications, applicable to the manufacturer, must be documented.

3. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category contains products, that are performing protection based solely on mechanical design. It includes bumpers (e.g. for the Teach Pendant), cable-guidance systems and energy chains for the robot arm, or other mechanical devices, that have no form of interaction with the application programming of the robot.

This is the only category of products, that by nature are not required to include a URCap, since the product will have no interaction with the robot program or application.

The attributes of a product that typically qualifies:

1. Mechanical interface:

• Product mechanically fits well, and is specially designed for, the shape of the robot arm, teach pendant or other area of application.
• Product does not negatively impact robot performance.

2. Other notes:

• There can be an exception to 1.2, if the product by its application allow the robot to work in workspaces, that are previously impossible.
• Meaning that a reasonable downgrade in performance can be accepted, if a new application can be achieved (e.g. EX, climate extremes, etc).

3. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category includes AGV's, mobile robots, and similar platforms that increase the automatic mobility of the UR arm.

1. Electrical integration:

• When operated by a battery supply, the solution must require the usage of an OEM DC-power control box together with the UR arm. The battery supply must be compatible with the OEM DC control box, and include cabling options to connect power and communications to the UR.

2. Mechanical interface:

• Product includes instructions for, and options to, directly mounting the robot base to the unit.
• Product includes instructions for, and options to, directly mount above specifies robot control box.

3. Mechanical system is verified to be rigid enough, to take the expected forces and torques in a typical application. Refer to the UR User Manual for mounting stability instructions. Alternatively, safety requirements must ensure that the platform can sustain the maximal forces applied by the robot.
4. Software integration:

• A reasonable handshake between mobile unit and UR robot using a URCap plugin.
• Communication interface that enables robust sub-task based handshake between mobile unit and URCap.

4. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category includes products, which interface to the robot include a base mounting. Both in form of workstations / tables, and semi-mobile / manually moveable mounting platforms.

The attributes of a product that typically qualifies:

1. Mechanical interface:

• Mechanically fits the robot base, including zero-positional alignment.
• Platform withstands the forces and torques of robot base, as according to UR User Manual.
• If product is semi-mobile alignment system or docking station must be included, in a way that does not degrade robot accuracy.

2. Software integration:

• Must include a URCap plugin, that ease the configuration and operation of the products workspace.
• URCap functionality could include aiding handling of workpieces, in respect to platform specific features, e.g. pre-defined trays.

3. Electrical interface:

• In product is semi-mobile, hot-swappable or easy connection of necessary electrical signals to external machinery must be included

4. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category includes robot tool mounted sensors for measuring force, torque or touch, with the application of performing delicate work tasks, that require force or torque monitoring. This could be for applications such as mechanical assembly, polishing etc.

The attributes of a product that typically qualifies:

1. Mechanical interface:

• Mechanically fits the UR Tool flange, and duplicated the UR Tool flange output.

2. Electrical interface:

• Connects to either UR Tool Communication Interface, or Control Box interface (USB, Ethernet).

3. Software integration:

• Setup and configuration possible using URCap plugin.
• Measurement data is fed into UR Force Control RTDE loop.

4. Sensor accuracy and precision

• Sensor specifications must be superior to UR e-Series built-in force-torque sensor.

5. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category includes softwares, which main robot-centered application is to generate robot code (URScript). It includes tools that generate a robot path, based on CAD-models or other environment descriptive information, and software that can be used for application simulation and offline programming.

The attributes of a product that typically qualifies:

1. Software interface: -The product may be desktop-based, and generate code portable to th robot, or

• The product may be a URCap, where a path can be configured directly from PolyScope.

2. Software integration (desktop based):

• Product is able to output UR Program files (.urp), which contain the defined motions and commands, or
• Product is able to output URScript which is wrapped into function blocks (i.e. in a URCap that groups script code into program node blocks, based on the application)

3. Software integration (URCap):

• Outputted URScript based on environment features is sanity checked, for possibility of motion.

4. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.

This category contains products, which main purpose is feeding workpieces or objects for a robot application. This includes conveyors, vibration feeders, bowl feeders or similar.

The attributes of a product that typically qualifies:

1. Software interface:

• The product must be operated using a URCap plugin.
• Operation include starting and stopping feed, or feeding until a part is present.
• Operation can include selection of infeed or outfeed, including relevant signals (part present for pick, or area free for placing).

2. Electrical interface:

• Interface to UR Control Box using digital IO (including encoders), or Ethernet based communication.

3. Other attributes:

• Product preferable contain a sensor, for detecting when a part is present at the fed location, or
• Possibility of linkage to generic vision based detection of part presence and location.

4. UR specific user instructions guiding even the inexperienced user in setup, operation, and uninstallation.