Skip to Content
Release notes

26.1 - February 2026

2026 kicks off with Wandelbots NOVA 26.1, including API extensions, stronger error handling and an improved experience.

BREAKING CHANGES

This release introduces a potentially breaking change in the Wandelbots NOVA API v2:

For the following endpoints when VirtualController is selected as configuration, the parameter type has been relaxed to a plain string in the API.

This allows passing values beyond the originally fixed enum set.

The endpoint Robot Configurations  is now available to fetch the currently supported string values for this parameter. Clients are encouraged to use this endpoint to dynamically discover allowed values instead of relying on hardcoded enums.

The enum is still generated in the API client for convenience and backward compatibility. Existing client code that sends values using the enum will continue to work. However, client code that receives and strictly relies on the enum for deserialization or validation may break.

What’s new?

Supported robots

Added support for 4 new robot(s):

ABB

  • ABB CRB 15000-10/1.52
  • ABB CRB 15000-12/1.27
  • ABB CRB 15000-5/0.95

YASKAWA

  • GP200S

For an up to date overview of all supported controllers and motion groups (robotic arms and external axes), refer to the Compatibility section.

Download GLB and USD models for your simulated scene

You can now download GLB and USD models for your simulated scene directly from the Wandelbots NOVA API v2 in the endpoint group Motion Group Models.

API v2

Delete Modbus and PROFINET signals with new API endpoint

A new API endpoint has been added to the BUS I/O endpoint group that allows you to delete all Modbus and PROFINET signals on the instance.

Additionally, error messaging has been improved when trying to send to inputs/outputs with int8 data type via Wandelbots NOVA API. As NOVA only supports int64, you will now receive a clear error message indicating that int8 data type is not supported.

Arguments added to Blending endpoint

The Plan trajectory  endpoint in the Wandelbots NOVA API has been extended with the following new optional arguments for blending:

BlendingPosition:

  • position_zone_percentage
  • orientation_zone_radius
  • orientation_zone_percentage
  • joints_zone_radius
  • joints_zone_percentage
  • space

BlendingAuto:

  • space

Argument added to Motion Group Description endpoint

Get motion group description  now fetches the serial number of either the motion group or the robot controller if the first is not available.

New parameter in Inverse kinematics endpoint

The parameter reference_joint_position has been added to Inverse kinematics . It accepts a joint position as a reference and returns only one solution in the same configuration.

All solutions are shifted to the same periodicity as the reference: Each individual joint angle is shifted by multiples of 2π (whole revolutions) until the reference is in the closest proximity possible. Additionally, these solutions are sorted by distance (l2 norm) from the reference.

  • Get Network State 
    Shows internet connection status, connection type, signal strength, latency & bandwidth.
  • Get Network Interfaces 
    Lists all active network interfaces with IP, MAC, and CIDR3.
  • ARP Scan 
    Scans the network and discovers all devices in the same subnet with IP, MAC & Vendor info.

Here are 4 use cases for these endpoints:

“No robot available” is displayed in Robot Pad

  1. Use Get Network Interfaces  to verify that the robot ethernet port is listed.
    If it’s not listed, the robot ethernet port is not connected.
  2. Connect a network cable to the robot ethernet port.

Wandelbots NOVA updates fail

  1. Use Get Network State  to check if the internet connection is active.
    If internet_connected: false, the internet connection is down.
  2. Check the internet connection, verify cable on internet port, check router/gateway.

Unstable connections to robot controllers

  1. Use ARP Scan  to check for IP conflicts in the network.
    If two devices have the same IP address, there is an IP conflict.
  2. Reconfigure one of the devices to resolve the IP conflict.

Wandelbots NOVA cannot connect to the robot controller

  1. Use Get Network Interfaces  to verify that the expected interface is listed.
    If the expected interface is missing, the physical port might be misconfigured.
  2. Check which physical port should be used and verify its configuration. If it doesn’t have an IP assigned (DHCP or static), assign one.

Connect multiple ABB and KUKA robot controllers to one NOVA instance

You can now connect multiple ABB and KUKA robot controllers to a single Wandelbots NOVA instance by indicating the EGM Server Port (ABB) or RSI Server Port (KUKA) for each controller during the setup process.

Use the Setup app to add additional controllers or configure them via the Wandelbots NOVA API.

More information on how to set up multiple robot controllers successfully can be found in the ABB robot setup documentation KUKA robot setup documentation.

What’s better?

  • The import dialogs for Industrial Bus Protocols in Setup app now include enhanced error handling and a new cancel option, providing better control and feedback during the import process.
  • Descriptions of the Execute Jogging endpoint in the Wandelbots NOVA API v2 have been improved for better clarity.

Filter and BUS signals in Setup app

The BUS signals table in Setup app now includes sorting and filtering capabilities, allowing you to sort signals by address and filter by IO direction for Profinet protocols. Additionally, long signal names are now fully visible regardless of column width, fixing the previous overlapping issue.

Ports for IRC5 and Omnicore controllers available in Setup app

The robot creation process now includes a more intuitive selection for two different controller ports, with options for IRC5 and Omnicore clearly labeled.

Connection reliability improved

When installing Wandelbots NOVA, real-time kernel is now included and automatically enabled. This ensures optimal performance for time-sensitive operations without requiring additional manual installation steps.

This resolves previous connection reliability issues and random freezes experienced with Wandelbots NOVA.

Updating to 26.1 will not enable the real-time kernel.

In order to start using Wandelbots NOVA with real-time kernel, you need to manually install Wandelbots NOVA with the updated installation package available via the Developer Portal following the instructions in the NOVA installation documentation.

Find more information about the configuration of real-time performance here.

Loading modal for critical services on homescreen

The application now only displays a loading modal for critical services during startup, allowing you to interact with the homescreen even if some non-essential services are still initializing.

Search bar for the Wandelbots NOVA API

A search bar has been added to the Wandelbots NOVA API documentation page to help you find specific endpoints or topics within the API documentation.

Parameter internal update

The endpoint parameter initial_joint_positions will now be a dynamic 6-element array instead of a static 7-element one. The array length will change depending on the DOF of the robot.

Bug fixes

  • Editing TCP name in settings app is possible again
  • You can now create diagnosis packages again during the loading of the homescreen thanks to a dismissable loading modal
  • The homescreen of the Setup app is now scrollable, preventing apps from disappearing.
  • The BUS signals table in Setup no longer reloads every 10 seconds, preventing loss of unsaved data.

Motion state stream no longer unresponsive with high latency external joint stream

This bug has been fixed by increasing the timeouts for motion-group state streams in RobotPad in case of a virtual robot.

Under investigation

Python examples in the API documentation contain URL encoded characters or are escaped incorrectly

When sending unedited Python code snippets from the Wandelbots NOVA API documentation, some URL encoded characters may lead to errors when executing the code, e.g., wandelbots-nova: Action class 'Motion' does not have a valid type.

For now, you need to manually decode these characters before executing the code, e.g., in the following example:

ios=tool_out%5B1%5D

needs to be changed to

ios=tool_out[1]

Technical details

For an up to date overview of all compatible dependencies, refer to the Compatibility section.

Updated KUKA .kop file 1.7.3

Please use the updated 1.7.3 .kop file provided in the Downloads section of the Developer Portal  when setting up KUKA robots on Wandelbots NOVA 26.1 or greater.

Documentation

  • Improved the documentation for motion planner related endpoints (jogging and execution) in the API v1 and v2 documentation.
  • You can now read about NOVA licenses and how to manage them in Licenses.
  • Added TCP setup instructions for all supported robot brands in the robot setup documentation.
  • The API Quickstart now includes information on how to use the networking endpoints to diagnose networking issues.
  • Outdated safety information has been removed from the intended use documentation.

✨ Ask Python SDK documentation with DeepWiki

With this release, the documentation features an external link to the detailed Wandelbots Python SDK documentation generated with DeepWiki.

The AI generated documentation of the repository is a comprehensive resource for developers using the Wandelbots Python SDK, providing in-depth information on installation, configuration, and usage of the SDK.

External link to Python SDK documentation generated with DeepWiki, light mode
External link to Python SDK documentation generated with DeepWiki, dark mode

Major overhaul of the simulation documentation

Unnesting

The “Simulate with NVIDIA Isaac Sim” section has been unnested and is now the top-level section for “Simulation” in the documentation sidebar.

If you want to simulate using RealVirtual.io, you can find the relevant one pager under the separator in the “Simulation” section.

Sidebar featuring the simulation section with NVIDIA simulation documentation at top level, underneath the simulate with realvirtual, light mode
Sidebar featuring the simulation section with NVIDIA simulation documentation at top level, underneath the simulate with realvirtual, dark mode

Explanation of Ghost teaching viewport overlay

Added documentation for the ghost teaching viewport overlay. It explains how the overlay visualizes available joint configurations.

Instructions on how to use collision world

Added a new Collision World page that documents exporting colliders from Isaac Sim to NOVA, loading collision overlays, and configuring collision setups and tool exports. This gives you a repeatable workflow to align simulation and NOVA collision data and reduce trial-and-error.

Configure a surface gripper in Isaac Sim

A new guide on how to set up a surface gripper in Isaac Sim has been added to the documentation. The guide walks you through the steps to create a surface gripper tool that can pick and place objects. You can find the guide here.

Additional learning resources

Find additional resources for learning about NVIDIA Omniverse in the Simulation introduction.

Updated UR robot instructions using PolyScope 5.22 or greater

The documentation for UR robots has been updated to reflect changes for PolyScope 5.22 and greater. It is now mandatory to first enable the robot once before connecting:

  • Press the “Power off” button in the lower left corner of the control panel
  • Press “ON”
  • and then Press “START”

Added ABB Omnicore controller setup instructions

The documentation for ABB robots has been updated to include setup instructions for Omnicore controllers.

FAQ update

The FAQ section has been updated with some new questions.

Find more information on

Improvements to supported robot list

The names of KR 3 R540 and KR 70 R2100 have been updated in the supported robot list to remove any references to “virtual controller” or “Omniverse”.

404 handling improvements

In order to improve user experience, 404 errors are now handled gracefully by:

  • Catching 404 errors on documentation pages
  • Redirecting users back to the main documentation page after a couple of seconds
  • Displaying a user-friendly message like “Looks like this page doesn’t exist”
Last updated on
Applying normsLicenses