26.2 - March 2026
With this release, we are excited to introduce several new features and improvements to enhance your experience with Wandelbots NOVA. From expanded support for new robots and motion groups to the addition of new API endpoints, this release brings a host of enhancements to help you get the most out of your robotic applications.
What’s new?
Supported robots
Added support for 2 new motion groups:
ABB
- ABB IRT710
Universal Robots
- UR15
For an up to date overview of all supported controllers and motion groups (robotic arms and external axes), refer to the Compatibility section.
NOVA API: Two endpoints added
Merge trajectories
To enable you to stitch and blend trajectories from different sources, you can now use the new Merge Trajectories endpoint .
POST /experimental/cells/{cell}/trajectory-planning/merge-trajectories
The given velocity limits are applied only inside the blending section to stay as close as possible to the original velocity profile while still making the trajectory executable. Timescaling will be applied to the blended area to ensure all limits are respected.
If a requested blending is not possible due to out of workspace/singularity/collision we still return a stitched trajectory but without the blending.
This endpoint is currently in an experimental state and thus subject to change.
New external axis type supported: Linear axes
Next to turntables, linear axes are now supported as external axes in Wandelbots NOVA. This support was introduced across the stack in the following components:
Wandelbots NOVA API
You can now add linear axes as a motion group type in your cell configuration using the NOVA API.
Robot Pad
The visualization of linear axes has been added to Robot Pad, allowing you to see the position and movement of linear axes in your cell setup. The coordinate gizmo for linear axes is aligned with the X-axis to reflect the linear movement direction.
Additionally, the jogging panel has been adapted to accomodate for the linear movement of a single joint in mm
instead of the rotational movement in degrees for turntables.
If a turntable type is used, the joint tab will display only two joints with degree units.
If a linear axis is used, the joint tab will display only one joint with millimeter units.
The cartesian tab is now deactivated for external axes, as cartesian movement is not possible for motion groups with under 3 joints.
Wandelbots NOVA JS Components
The jogging component in the NOVA JS Components library published on GitHub has been equally updated to support linear axes.
Add motion group to Virtual Controller
You can now add motion groups to a Virtual Controller with Add motion group to Virtual Controller endpoint :
POST /cells/{cell}/virtual-controllers/{controller}/motion-groups
What’s better?
Signals app now a core app
The Signals app is now a core app, which means it is pre-installed on the homescreen of Wandelbots NOVA and can be used without any additional installation steps. Previously, the Signals app had to be installed from the App Store before it could be used.
Configuring signals remains a task in the Setup app.
Signal names are now limited to a set of restrictive characters
To avoid issues with special characters in signal names, the allowed characters for signal names have been restricted to:
- alphanumeric characters
a-z, A-Z, 0-9 - underscores
_ - hyphens
- - periods
.
This ensures that signal names are compatible with all systems and devices interacting with Wandelbots NOVA.
Hello Isaac Sim Extension, Good bye Omniservice
For clarity’s sake, the Omniservice API has been renamed to the Isaac Sim Extension API. This aligns better for consistent terminology usage across Wandelbots NOVA and NVIDIA.
Bug fixes
Wandelbots NOVA now more accurately tracks and reports controller failures, ensuring you are notified only on the initial transition from a healthy to a failed state, reducing redundant alerts and improving monitoring efficiency.
Setup app: Larger exports and imports possible
The export and import process of cell configurations in Setup have been improved to handle larger numbers of resources in the configuration. Provided, all resources are selected for export and import, the system will detect the larger export and import and adjust its request to the backend accordingly.
NOVA API: Manual mapping of values from GET Controller State and PUT Controller Mode no longer necessary
To improve your experience, the mode values for PUT /cells/{cell}/controllers/{controller}/mode now
support additional values. Previously, you had to map values themselves when using
GET /cells/{cell}/controllers/{controller}/state and PUT /cells/{cell}/controllers/{controller}/mode together.
This was because GET /cells/{cell}/controllers/{controller}/state’s values were
MODE_MONITOR and MODE_CONTROL, while PUT /cells/{cell}/controllers/{controller}/mode’s
were ROBOT_SYSTEM_MODE_MONITOR and ROBOT_SYSTEM_MODE_CONTROL.
Now PUT /cells/{cell}/controllers/{controller}/mode supports all four.
On their final mission
NOVA API v1 and Wandelscript
Announcement of upcoming end of support for the following features with Wandelbots NOVA release 26.3. Please transition to the latest versions of our tools and APIs to ensure continued support and access to new features. The following features will no longer be supported with Wandelbots NOVA 26.3:
- Wandelbots NOVA API v1
- Wandelscript
As will be announced in an upcoming release, Wandelbots NOVA will no longer support Wandelbots NOVA API v1 and Wandelscript.
We encourage all users to start transitioning to the latest versions of our tools and APIs to ensure continued support and access to new features.
This includes the transfer of Wandelscripts to Python scripts using the @nova decorator and
the migration to Wandelbots NOVA API v2 for all applications.
For more information on how to migrate to Wandelbots NOVA v2, please refer to the migration guide.
For more information on how to migrate to Python, please refer to the Python SDK documentation.
If you have any questions or need assistance with the migration process, please don’t hesitate to reach out to our support team.
Please be advised that using NOVA versions which support deprecated features may lead to security vulnerabilities.
Support for NVIDIA Omniservice 4.5
Support for NVIDIA Omniservice 4.5 is deprecated with the release of the Wandelbots NOVA Isaac Sim Extension compatible with Wandelbots NOVA 26.2.
We encourage all users to transition to at least NVIDIA Omniservice 5.0 to ensure continued support and access to new features.
For an up to date overview of all supported NVIDIA Omniservice versions, refer to the Compatibility section.
Technical details
For an up to date overview of all compatible dependencies, refer to the Compatibility section.
Updated KUKA .kop file
The KUKA custom option package has been updated to version 2.4.1. Please download the latest version of the .kop file from the Developer Portal’s Downloads section and update your controller accordingly to ensure compatibility with Wandelbots NOVA 26.2.
Documentation
- FAQ updated in the FANUC setup instructions on how to resolve safety state mastering issues.
- Signals app was added to the NOVA core apps overview and mentions of installing it via the App Store were removed.
- Added article on how to use external axis in simulation
- Added steps on how to use the new Merge Trajectories endpoint to the NOVA API collision guide and NOVA API quickstart guide.
- Removed NVIDIA Omniservice 4.5 from the list of supported NVIDIA Omniservice versions in the Compatibility section.