Versionshinweise (Englisch)

Release 2026.09.30.51504

Version date: 2026-09-30

What changed

This release makes contour optimization and path planning easier, with automatic HALT-based connections and more control over contour processing order. Clearer English and German messages help identify failed contours and troubleshoot planning problems. Faster geometry checks and fixes to motion calculations, contour settings, and imported scene data improve performance and reliability. Updated documentation explains the workflows, while warnings highlight skipped geometries that require independent path validation.

• Features:

  • Added automatic path planning between HALT-defined program positions
  • Added contour optimization and connections in a user-defined order
  • Preserved successful contour results when individual optimizations fail
  • Started selected contour optimization directly from the context menu
  • Improved solution switching and mouse-wheel navigation in selection lists
  • Localized planning errors, warnings, and progress in English and German
  • Accelerated collision and distance checks for complex geometry

• Bugfixes:

  • Fixed planning task selection and start-button availability
  • Fixed contour sliders and multi-contour tool direction editing
  • Corrected external-axis unit conversion and Visual Components target configurations
  • Refreshed changed robot data and joint limits after context switches
  • Identified failed contours by name with practical troubleshooting guidance
  • Preserved path names and matched planning results to the correct requests
  • Fixed collision checks at motion starts and intermediate segment boundaries
  • Corrected collision prediction for fixed tools and external axes
  • Kept contour entry and exit motions consistent with their separate settings
  • Preserved endpoints and requested speed limits for very short PTP moves
  • Corrected angular distances between robot orientations
  • Prevented invalid inverse-kinematics results for unreachable spherical-wrist targets
  • Preserved all imported geometries and saved joint positions in scene bundles
  • Improved import, export, and optimization stability while reducing memory leaks
  • Reported malformed motion commands and invalid dynamics without backend crashes
  • Warned about skipped invalid geometries requiring independent path validation

• Documentation:

  • Updated HALT planning guidance with preparation, clearances, and troubleshooting
  • Updated contour optimization guidance for selection, connections, and solution switching
  • Removed outdated authored-path guidance from the user documentation

Known Issues

• iiQWorks 1.2/1.3 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.
• Some of the models in the eCatalog have nodes with offsets in them, that can’t be calculated correctly in backend. Generated paths and motions have to be double-checked.

Release 2026.08.25.41944

Version date: 2026-08-25

What changed

• Moved Visual Components 5.0/5.1 to full support
• Added option to trigger single contour optimization from optimization assitant
• Added more user information in specific cases
• Added URKinematics type and its Parameters adding support for the following robots:
  • Universal Robots - all robots
  • Agile Robots AG - Yu 5 Industrial
  • AUBO - all robots
  • Dobot - CR10, CR16, CR20A, CR3, CR5, Magitial E6, Nova2, Nova 5
  • Hanwha Robotics - all robots
  • JAKA - all robots
  • Omron - TM12, TM12X, TM14, TM5-700, TM5-900
  • Rainbow Robotics - all robots
  • Rozum - all robots
  • Siasun - GCR14-1400, GCR20-1100, GcR5-910
  • Techman Robot - all robots except TM25S, TM25S-X, TM30S, TM30S-X
  • Yuanda - all robots
• Reworked Wannenlage functionality
• Improved performance for path planning an program optimization
• Fixed errors with dissolving path planning and contour statements
• Fixed path simplifier issues to produce a reduced amount of statements on backend response
• Fixed smaller UI issues

Known Issues

• iiQWorks 1.2/1.3 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.07.31.34898

Version date: 2026-07-31

What changed

• Added support for Visual Components 5.1
• Added support for iiQWorks 1.3
• Added support for robots with expression based joint limits
• Fixed automatic collision list build up, when robot is attached to other components
• Fixed error message on wake up from suspend mode
• Fixed error message in process statement view for context menue commands
• Improved documentation and tooltips
• Improved backend stability for better and more reliable solutions

Known Issues

• iiQWorks 1.2/1.3 and Visual Components 5.0/5.1 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controllers specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.06.26.26691

Version date: 2026-06-26

What changed

• Fixed contour optimization to work with invalid initial request

Known Issues

• iiQWorks and Visual Components 5.0 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.06.26.26581

Version date: 2026-06-26

What changed

• Added support for contour statements inside scopes to be recognized as single tasks
• Fixed CommentToContour feature to regenerate contours from previoulsy standard conversion
• Fixed smaller UI bugs and added error handling
• Fixed contour properties not correctly set when copied or returned from backend
• Fixed teach handler not beeing able to generate unreachable points
• Fixed statement transfomers under KUKA
• Fixed normal readout to work version independent
• Fixed contour property not being correctly updated, when workpiece positioner gets deleted
• Fixed initial setting setup on first install
• Expanded support for more kinematic types
• Updated documentation
• Updated deafault settings for path planning and program optimization

Known Issues

• iiQWorks and Visual Components 5.0 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.06.10.23699

Version date: 2026-06-10

What changed

• Fixed context menu entries for KUKA.Sim and iiQWorks to prevent the program from crashing on start-up
• Fixed PathToContour to be independent on the external axis count
• Improved error handling for a more stable plugin integration

Known Issues

• iiQWorks and Visual Components 5.0 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.06.05.22748

Version date: 2026-06-05

What changed

• Added new licensing with offline files and online subscriptions
• Added per contour Wannenlage options
• Added selection to program optimization assistant to only optimize selected tasks
• Added info dialog for base initialization on backend request with connected workpiece positioner
• Increased prorobuf message size for larger 3D-models
• Improved localization
• Clean up UI for a better overview
• Fixed multi-selection execution of single contour requests
• Fixed transformation mismatch between front- and backend
• Fixed logging problems
• Fixed joint interpretation to extend robot support
• Fixed frontend progressbar to give a better progress overview
• Fixed possible looping in entry/exit actions on contours
• Fixed path to contour transformer for VC-based programs
• Fixed smaller UI bugs

Known Issues

• Installer for iiQworks and KUKA.Sim 4.3 / 4.10 are not working.
• iiQWorks and Visual Components 5.0 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.04.27.15838

Version date: 2026-04-27

What changed

• Added multi-instance support for Visual Components-based programs
• Added support for inverting contour path direction
• Added support for user defined self-collision sets in Visual Components-based programs
• Added workflow documentation:
  • For base intitialization with external axis
  • For user defined self-collision lists
• Fixed robot postioning on statement selection under Visual Components-based programs

Known Issues

• iiQWorks and Visual Components 5.0 still in Beta.
• Under Visual Components 4.9, when setting a node for a Base coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.04.17.14870

Version date: 2026-04-17

What changed

• Added beta support for Visual Components 5.0
• Added documentation of grpc interface with examples
• Added and improved python interface and examples
• Added basic support for safety configuraions under iiQWorks
• Added more console output about current state of backend in frontend
• Added support package button to gather all necessary information for the development team
• Added workflow documentation for process modeling
• Advanced check robot functionality to get a better overview for supported robots
• Fixed problems with external axis
• Fixed user cancelation for contour optimization
• Fixed problems with rotation in robot frames
• Fixed tool dependencies
• Fixed context menues not beeing visible after license activation
• Fixed multiple instance support for Visual Components based programs
• Fixed wrong units beeing transmitted
• Improved backend shutdown handling

Known Issues

• iiQWorks and Visual Components 5.0 still in Beta.
• Under Visual Components 4.9, when setting a node for a “Base” coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.     
• Some of the models in the eCatalog are not very accurate and have geometry flying around.
• If a Visual Components-based program is already running and a second instance is started, the running backend will be terminated. A new backend process needs to be started via the UI from one instance, while the other instance needs to check the connection.

Release 2026.03.20.11874

Version date: 2026-03-20

What changed

• Added more workflows to documentation
  • Added workflow for robot model Validation
  • Added workflow for generating collision free points in processes
• Fixed iiQworks installer to work
• Fixed setting selections bug
• Fixed robot position on contour selection under Visual Componenets

Known Issues

• Under Visual Components 4.9, when setting a node for a “Base” coordinate system this needs to be of world type to set the robots position correctly.
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process.
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.
• Some of the models in the eCatalog are not very accurate and have geometry flying around.

Release 2026.03.12.11552

Version date: 2026-03-12

What changed

• Full release for KUKA iiQWorks 1.2 Advanced
• Added support for Visual Components Essentials 
• Added reverse path planning functionality 
• Added convert to standard robot program functionality to export programs to users without the plugin and also reimport to use with the plugin 
• Added converter for the Visual Components path statement to contour statement 
• Added 1:N:1 functionality to calculate a path from a point to a point and back 
• Added program optimization from selection to be able to select specific contours and optimize this subset of contours
• Added support of external axis in program optimization 
• Added single contour optimization functionality to make a contour executable with given degrees of freedom 
• Added setting selector to edit and save a set of settings and also added default settings to revert to
• Added license expiring warning when reaching 7 days or less
• Added right click quick access for check contour functionality
• Fixed Bug of KRL disabled is reset when cancelling backend calculation
• Fixed user info dialog on program startup 
• Major improvements for collision checking and program optimization 
• Improved automatic collision list generation (fixed miscellaneous bugs)
• Cleaned up context menu UI 
• Clened up Contour properties
• Improved error handling and user information to problematic user input 
• Fixed robot selection bug when editing in task list view
• Fixed robot positioning with external axis on returned motion statements 
• Fixed check contour for contours with circ motions
• Removed 1:N and N:1 functionality

Known Issues

• Under Visual Components 4.9, when setting a node for a “Base” coordinate system this needs to be of world type to set the robots position correctly. 
• Working with dynamic (expression based) joint limits in robots only take initial values of joint limits for path planning. This way dynamic joint limits are not updated within the planning process. 
• The path simplifier that runs right before sending a request from the backend back to the frontend does not work properly sometimes. This leads to many statements returned form the backend. Currently, the user must clean this up manually.
• Due to the robot controller’s specific calculations for blending, collisions may occur at large blending values. This can be fixed by adjusting the clearance value in the settings.

Release 2025.12.05.5991

Version date: 2025-12-05

What changed

• Handle coupled kinematics in Visual Components
• Path- and contour planning statements can be dissolved even when the plugin is not licensed, to be able to export programs without the plugin
• Improved path- and contour planning performance
• Added more specific error handling
• Fixed UI bugs

Known Issues

• External axis not working in Visual Components

Release 2025.11.28.5596

Version date: 2025-11-28

What changed

• Reworked entry collection so the user only gets the executable statements in the two ribbon buttons for path planning and optimization
• Under Visual Components the context menu entries for path planning and optimization are now in separate folders
• Reworked the documentation and added new guides and workflows
• Added local documentation
• Adjusted general UI and event handling to prevent input lag
• Statements can now be moved correctly in and out of contour and path planning statements
• Fixed statements not correctly created regarding the desired tool and base
• Reworked the documentation
• Enhanced Visual Components Joint Support with Expression-Based Values and Follower Joint Synchronization
• Fixed backend process now correctly starting, closing and restarting and added a health check
• Simplified HardwareID acquisition for license generation and added a better overview over available features and expire dates
• Added process statements in contours to handle collision detectors
• Redoing a path planning statement plays back the new statements in the same scope
• Improved blending support for motion statements
• Added pre request checks to path planning and path optimization settings for better user experience
• Fixed teach handling for contours with different teach actions
• Reworked collision list handling
• Increase number of supported robots
• Improved calculation time for requests

Release 2025.11.13.4619

Version date: 2025-11-13

What changed

• Increased planning speed for path planner for scenes with high number of polygons (millions and higher)

Release 2025.11.03.4089

Version date: 2025-11-03

What changed

Features

• Improved Documentation
• Added support for KUKA Sim 4.10
  • Added supported robot check for KUKA Sim 4.10
• Improved licensing overview
  • hardware id can directly copied from Plugin Overview
  • Improved overall user experience (added better error messages and fixed some UX bugs)

Fixed Bugs

• Fixed a bug where backend is not shut down correctly after closing KUKA
• Added tool and base change before creating target
• Installer distinguishes between install of KUKA 4.3 and KUKA 4.10
• Improved stability of contour planner

Release 2025.10.13.2352

Version date: 2025-10-13

What changed

First Release of byte robotics planner! This has the first version of the KUKA Sim Plugin to plan and optimize robot paths. This enables robot programmers to create the most efficient robot programs through the most efficient programming process. Simply automated. Our Technology can automatically check your process description, whether a robot program is possible. If not it enables it by using the degrees of freedoms of your manufacturing process itself. If this is possible, via cycle-time optimisation the fastest found solution is applied into your OLP software. The programmer can check, modify and proceed with his usual workflow.