Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 40 Next »

[TODO: Describe the major themes of the release here]

We are excited to …..

RapidPlan Create

Major Improvements

Internal Note:

  1. Better to prioritize items with users/AEs
    An improvement seems to be a small change, but the impact on users can be bigger than it looks.
    - Example: Loading a project can now be cancelled

[TODO: Reorder the items based on the importance from user perspective]

Trajectory Smoothing

This feature brings a more realistic trajectory, closely mirroring the smooth paths found in real-life scenarios, which enables more accurate interference reports(New feature) and cycle time analysis.

[GIF]

Highlights:

  1. Smoothing Definition: Set smoothing values from 0.0 mm to 500 mm for realistic robot trajectories.

  2. Global and Individual Settings: Define smoothing globally or per waypoint.

  3. Enhanced Visualization: View smoothed trajectories within RPC.

Auto-Save securely save your latest work

[GIF]

We've added an automatic project saving feature. It will be automatically enabled after upgrading to this version. This function can be disabled from the project settings. You no longer have to worry about losing your work in the middle of a task!

Enhanced re-parenting feature boosts alignment process

Get ready to take your alignment to the next level with our newly enhanced re-parenting feature, designed to simplify and accelerate your workflow!

[GIF]

Smart Offsetting: Re-parenting your objects? Don't worry about the offset! Our feature automatically maintains the original offset with the old parent and calculates a new offset with the new parent, ensuring a smooth transition.

[GIF]

Bulk Re-Parenting: Now, you can effortlessly move multiple targets/frames/mates (e.g. 50 weld points) to a new parent frame while keeping the same old location! No more tedious one-by-one adjustments.

Interference and near-miss report

[GIF]

This feature has been frequently requested by our customers and aims to simplify the generation of interference and near-miss reports for interlock design.

Existing project clearance values are used for calculating robot-robot interferences as “cautions,” and near-miss values are defined in the report dialog for "warnings."

Please note that the report does not include collisions with the environment, does not consider clearance rules for robot-robot interferences, and does not include robot-self interferences.

Other Improvements

  • The joint numbering now starts from one instead of zero. Previously, users had to type in joint number 6 to refer to the additional external axis joint index 7, which was confusing. This update aligns the numbering with common expectations.

  • [TODO] [RPC] Performance Enhancements and Benchmarking

  • [TODO] RAPID-23365 - Getting issue details... STATUS

  • [TODO] RAPID-31234 - Getting issue details... STATUS

Before update

[TODO] Anything user should know about before update?

  • Auto-connect validation may take lot longer when loading older project (<2.4) [ID:33168]

    • A workaround is reduce the maximum number of iterations for the existing auto-connects before revalidation

RapidPlan Control

Major Improvements

A cleaner and more intuitive layout

Explanation

Improvement 2

[GIF]

Explanation

Improvement 3

[GIF]

Explanation

Improvement 4

[GIF]

Explanation

Improvement 5

[GIF]

Explanation

Other Improvements

Before update

[TODO] Anything user should know about before update?

RapidPlan ASCII API

Internal Note: Categorization from the perspective of users/ use cases would be nice to quickly identify relevant topics
- Example: Updated Move command with a new argument shortest_path_only.
This update is especially important for spot-welding users who want to avoid lengthy second shortest path to take

Before update

[TODO] Anything user should know about before update?

Known Bugs/Limitations

Internal Note:

  1. Breaking changes should be highlighted
    - Users need to know those changes BEFORE updating software
    Example:
    License is required after update

  2. Categorization of high priority known bugs/limitations
    - Serious bugs should be listed first
    - Carried-over bugs from previous versions should be listed below the latest found bugs

RapidPlan Create

[Remove] Remove from release note

ID

Content

Status

Added

33873

Converting multiple auto-connects to manual connections fails if the targets to be connected for those auto-connects are the same

Fixed

2.4

31952

[TODO: Update with final state of the development] No warning is provided to user for any lost target assignments or connections when transitioning from model mode to roadmap mode

Open

2.4

33589

[Remove] A value of 0 is not invalid when giving that as input to the preset dynamics dialog, but is not saved when clicking OK

Open

2.4

34443

[Limitation] Software hangs sporadically when setting voxel size to 2mm

Open

2.4

34370

When clicking on OK in a Mate dialog, the last selected state under the Mate dialog is selected as the active state and not the state of the active preset

Open

2.4

[Remove] Upon selecting a edit value field in the mate offset, units of the offset in the edit mate field are shown as different than the ones from project settings

Open

2.4

29701

[Limitation] Validate remaining does not work when jog dialog is open

Open

2.4

34016

[Remove] Loading the same project multiple times in RPC does not clear the system memory and can lead to software crash

Open

2.4

[Remove] Software crashes if more than one validation actions are sent in parallel

Open

2.4

Deterministic path planning is not guaranteed for clearances greater than 10cm

Open

2.4

Clearance Rule and Disable collision checking dialog allows creating a rule with same name across presets

Open

2.4

32765

Live Robot Connection makes the override speed of the teach pendant to be 100% upon connection

Open

2.2

Live Connect to Kawasaki robots may fail if the robot controllers have been connected in RTR

Open

2.4

controller’s control panel previously. To use Live Connect again, the /tmp/krnx folder and its contents needs to be manually removed. The location of the /tmp/krnx folder is under /var/lib/rtr_appliance_app

Open

2.4

32731

[Limitation] Stateful targets and frame are not supported. Put in another way, any objects with any descendants such as targets and frames cannot be made stateful

Open

2.4

33990

[TODO: Update with final state of the development]Reparenting a frame that is mated to an object can cause inconsistency with mates

Open

2.4

Unable to zoom projects that contains entities >10km from from origin (or from other entities)

Open

2.4

Reparenting a frame that is mated to an object can cause inconsistency with mates

Open

2.4

34623

Numerical calculation errors cause collision detection when a tool and link are in close proximity.

Fixed

2.5

31267

[Limitation] RPC only works properly with US-EN locale while no warning given in RPC when the wrong locale is selected. In many countries such as Germany, the decimal separator is a comma, this causes errors in RPC. Users must change the locale when working with RapidPlan.

[todo: Add to installation procedure]

Open

2.3

RapidPlan Control

ID

Content

Status

Added

Disconnecting one robot turns off display for all robot voxels

Upgrading from a 2.3 project will delete any existing robot control logs

No warning given in CP when the wrong locale is selected

  • Only accepts US-EN

19828

Interlock recording does not work with partial execution

  • DSM boxes, objects, and frames are tracked in the Profinet look up ID table. When items are created or removed, their Profinet IO mappings are handled as such, the handler retrieves the new id of the entity, and publishes it with Profinet. However, this does not cover cases where an external command source elicits a change in the DSM that’s unknown to a PLC.

Robot Control

  • ABB [20230621-8045099]: In very rare cases, the robot is not responding to the commanded trajectory. This is under investigation with ABB.

  • ABB [20230609-7981814]: In very rare cases, the robot reports joint out of range error for a target that’s very close to the joint limit. This is under investigation with ABB.

  • Yaskawa: if a robot is left in AcquireControl mode for more than 2 hours, a joint state loss error is reported. To avoid the error, a Yaskawa robot should be in ReleaseControl mode if left idle for an extended period of time.

  • No labels