Skip to Content
Release notes

25.8 - September 2025

Overview: description of the release in one sentence. Engages reader to consume the release notes.

BREAKING CHANGES

Adjusting limits of endpoint Motion group description

In API v2 of Motion group Description , the field operationLimits has been added and has replaced globalLimits and its previous subcategory physicalLimits. This field contains one set of limits per operation mode (AUTO, MANUAL, etc.) of the controller so that now when you are planning, you can directly use the set of limits for the mode you want to plan for as is.

PROFINET endpoint updates

Two endpoints have had their naming conventions adjusted.

/api/v2/cells/{cell}/bus-ios/profinet/ios/{io} now takes the parameter description instead of name. /api/v2/cells/{cell}/bus-ios/profinet/ios now returns an array of objects, where the previous name is now called description.

pause_on_io no longer available when jogging

For feature clarification purposes, executeJogging will not longer contain the feature pause_on_io. However, it will remain in executeTrajectory. So searching for a point of contact between a tool and a workpiece can be implemented by planning a trajectory and adding a pause_on_io, instead of jogging with the current state. If you find that your application requires pause_on_io in executeJogging, please file a feature request via the Developer Portal.

What’s new?

Set up PROFINET via Setup app

You can now set up PROFINET directly in the Setup app on your Wandelbots NOVA instance. This allows you to connect to a PLC and configure PROFINET signals.

Refer to the updated PROFINET documentation for detailed instructions on how to set up PROFINET with Wandelbots NOVA.

Read and write PROFINET signals via API

With the following endpoints, you can now read and write PROFINET signals on trajectory execution signals using Execute Trajectory > StartMovementRequest :

  • Start on Input/Output
  • Pause on Input/Output
  • Set Input/Output on Location

Select the PROFINET controller as source of the input/output signal with io_origin=BUS_IO.

Supported robots

Two new KUKA robots are now supported:

  • KR 70 R2100 (for Omniverse simulation only)
  • KR 60-3.

OpenUSD extension

There is a now a Wandelbots OpenUSD extension. This lets you access OpenUSD prim types and APIs which represent robots, tools, and additional features in order for you to configure prims connected to NOVA.

New Isaac Sim extension SDKs

For a better experience, two packages (python  and npm ) have been generated for the Isaac Sim Extension, which aid in application building and Python SDK usage.

What’s better?

Improved transfer of simulated model to physical cell

The Isaac Sim extension API now includes the endpoint /omniservice/api/v2/physics/collision/sweep, allowing you to transfer a collision model from a simulated scene onto Wandelbots NOVA. This means that the collision data can be transferred to the Wandelbots NOVA API and be respected by physical controllers, thus improving the transfer from a simulated world to a physical cell.

Plan trajectory update

For the endpoint Plan trajectory , it is now possible to set limits for an elbow and flange, in addition to joints and tcp. This can be set with the properties of elbow and flange in global_limits.

Addition of target_location in Execute trajectory

StartMovementRequest of the endpoint Execute trajectory  now includes target_location, which allows you to debug trajectories by providing a target location in tandem with its direction. This enables breakpoints on trajectories.

Improved sequential motion executions

It is now possible to have multiple InitializeMovementRequests within the same connection without worrying about unintended movemenets in between each intended execution, thus streamlining the process.

KUKA cycle rate option

It was noted that running a KUKA robot with a 4ms cycle rate could occasionally cause stability issues, especially if Wandelbots NOVA wasn’t installed on a real-time kernel. Therefore, a new option for a 12ms cycle rate has been introduced and is available on creation in advanced settings when adding a physical KUKA robot to a cell.

Remote update of KUKA now possible

If you are using a KUKA robot with NOVA, you no longer need to go through the lengthy process of making updates yourself. It is now possible to transparently update the KRL files on the KUKA on Wandelbots NOVA end, without you needing to update the controller.

Connect from within the Wandelbots NOVA Isaac Sim Extension to your instance

By following the updated Isaac Sim documentation, you can now connect to your Wandelbots NOVA instance directly from within the Wandelbots NOVA Isaac Sim Extension.

Bug fixes

  • Setting I/Os on trajectories and adding to trajectories directly is now added to the trajectory cache as expected.
  • Creating a virtual clone of a physical robot now works as intended.

Under investigation

  • When using FANUC robots with high masses (>6 kg) attached to the flange tend to display unexpected deviation from planned paths. With velocity set to approximately 150 mm/s, movements will stop mid-motion. We are on it.
  • When adding a custom TCP, the visualization of robot and TCP can take a while to update.

Technical details

KUKA option package update

  • The MultiSubmitInterpreter option package is now required to run a physical KUKA.
  • The Wandelbots KUKA option package has been updated to 1.4.2.0.

TIA Portal v19 and 20 support

Wandelbots NOVA 25.8 adds support for TIA Portal v19 and v20. To enable compatibility, download and use the latest PROFINET GSD file.

New Wandelbots NOVA Isaac Sim extension compatibility

For those using Wandelbots NOVA extension for Isaac Sim, please be aware that with Wandelbots NOVA 25.8, version 2.4.0 or higher of the NOVA Isaac Sim Extension is required. The previous release, 25.7, is now only compatible with 2.3.0.

Documentation

Robot software and hardware requirements update

The crew instructions for several robot brands have been updated to give more accurate information on what you need for each in order for everything to run smoothly.

They are:

Last updated on
Prototyping with JupyterGlossary