Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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

...

[Remove] Remove from release note

ID

Content

Status

33873

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

Fixed

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

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

34443

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

Open

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

[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

29701

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

Open

34016

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

Open

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

Open

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

Open

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

Open

32765

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

→ [Fixed] The override speed is not overridden by 100%

Fixed

28237

Live Connect to Kawasaki robots may fail if the robot controllers have been connected in RTR 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

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

33990

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

Open

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

Open

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

Open

34623

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

Fixed

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

4.2. RapidPlan Control

ID

Content

Status

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.

Planning moves with DSM object attached to the robot will be rejected with an error in 2.5

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.