@wandelbots/nova-api 25.7.2-rc.2 → 25.8.0-dev.100

package/v2/api.d.ts

@@ -93,7 +93,7 @@ export interface AddTrajectoryError {
      */
     'message'?: string;
     /**
-     * The location of the error in the trajectory.
+     * Location on trajectory where the execution will start. The default value is the start (forward movement) or end (backward movement) of the trajectory. If you want to start your movement from an arbitrary location, e.g. in combination with [streamMoveToTrajectoryViaJointPTP](streamMoveToTrajectoryViaJointPTP), set the location by respecting the following format: - The location is a scalar value that defines a position along a path, typically ranging from 0 to `n`,   where `n` denotes the number of motion commands - Each integer value of the location corresponds to a specific motion command,   while non-integer values interpolate positions within the segments. - The location is calculated from the joint path
      * @type {number}
      * @memberof AddTrajectoryError
      */
@@ -354,17 +354,17 @@ export interface BusIOProfinet {
      */
     'bus_type'?: BusIOProfinetBusTypeEnum;
     /**
-     * Content of Configuration XML file for PROFINET device, typically known as PND_IOD.xml. Leave empty for the default configuration.  Refer to the official PROFINET driver documentation for further information.
-     * @type {string}
+     * Used to enable IP communication through the same physical ethernet interface while PROFINET driver is active.
+     * @type {BusIOProfinetNetwork}
      * @memberof BusIOProfinet
      */
-    'config_file_content'?: string;
+    'network_config'?: BusIOProfinetNetwork;
     /**
-     * Used to enable IP communication through the same physical interface while PN Driver is running.
-     * @type {BusIOProfinetNetwork}
+     * IP address of the PLC to establish PROFINET communication with.  The IP address is used to configure the host machine\'s firewall. The firewall configuration is applied while the BUS input/output service is active. Without proper firewall configuration, PROFINET device discovery, configuration exchanges, and real-time cyclic data communication will fail.
+     * @type {string}
      * @memberof BusIOProfinet
      */
-    'network_config'?: BusIOProfinetNetwork;
+    'plc_ip': string;
     /**
      * MAC address of the physical ethernet interface that you want to use for PROFINET communication.
      * @type {string}
@@ -1708,9 +1708,22 @@ export interface GetTrajectoryResponse {
 export interface HTTPValidationError {
     /**
      *
-     * @type {Array<ValidationError>}
+     * @type {Array<ValidationError2>}
      * @memberof HTTPValidationError
      */
+    'detail'?: Array<ValidationError2>;
+}
+/**
+ *
+ * @export
+ * @interface HTTPValidationError2
+ */
+export interface HTTPValidationError2 {
+    /**
+     *
+     * @type {Array<ValidationError>}
+     * @memberof HTTPValidationError2
+     */
     'detail'?: Array<ValidationError>;
 }
 /**
@@ -1810,7 +1823,7 @@ export interface IODescription2 {
      */
     'io': string;
     /**
-     * Descriptive name of the input/output. Customize it using the respective BUS service, e.g. [addProfinetIO](addProfinetIO) for PROFINET service.
+     * Name of the input/output. Customize it using the respective BUS service, e.g. [addProfinetIO](addProfinetIO) for PROFINET service.
      * @type {string}
      * @memberof IODescription2
      */
@@ -1909,7 +1922,7 @@ export interface IOIntegerValue {
      */
     'io': string;
     /**
-     * Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > We recommend to use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value.
+     * Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > Recommended: Use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value.
      * @type {string}
      * @memberof IOIntegerValue
      */
@@ -1925,6 +1938,16 @@ export declare const IOIntegerValueValueTypeEnum: {
     readonly Integer: "integer";
 };
 export type IOIntegerValueValueTypeEnum = typeof IOIntegerValueValueTypeEnum[keyof typeof IOIntegerValueValueTypeEnum];
+/**
+ * States the source of the input/output signal.
+ * @export
+ * @enum {string}
+ */
+export declare const IOOrigin: {
+    readonly Controller: "CONTROLLER";
+    readonly BusIo: "BUS_IO";
+};
+export type IOOrigin = typeof IOOrigin[keyof typeof IOOrigin];
 /**
  * @type IOValue
  * @export
@@ -2034,24 +2057,12 @@ export interface InitializeJoggingRequest {
      * @memberof InitializeJoggingRequest
      */
     'tcp'?: string;
-    /**
-     * Update rate for the response message in milliseconds (ms).  Recommendation: As Wandelbots NOVA updates states in the controller\'s step rate, use either the controller\'s step rate or a multiple of it.                 Wandelbots NOVA will not interpolate the state but round it to the nearest step rate below the configured response rate. Use [getOptimizerConfiguration](getOptimizerConfiguration) to get the controller\'s step rate.  Minimal response rate is the step rate of the controller.
-     * @type {number}
-     * @memberof InitializeJoggingRequest
-     */
-    'response_rate'?: number;
     /**
      * Unique identifier addressing a coordinate system to which the responses are transformed. If not set, world coordinate system is used.
      * @type {string}
      * @memberof InitializeJoggingRequest
      */
     'response_coordinate_system'?: string;
-    /**
-     * Defines an input/output that is listened to during the movement. Execution pauses if the defined comparator evaluates to `true`.
-     * @type {string}
-     * @memberof InitializeJoggingRequest
-     */
-    'pause_on_io'?: string;
 }
 export declare const InitializeJoggingRequestMessageTypeEnum: {
     readonly InitializeJoggingRequest: "InitializeJoggingRequest";
@@ -2104,12 +2115,6 @@ export interface InitializeMovementRequest {
      * @memberof InitializeMovementRequest
      */
     'initial_location'?: number;
-    /**
-     * Update rate for the response message in milliseconds (ms). Default is 200 ms. Recommendation: As Wandelbots NOVA updates states in the controller\'s step rate, use either the controller\'s step rate or a multiple of it.                 Wandelbots NOVA will not interpolate the state but rather round it to the nearest step rate below the configured response rate. Minimal response rate is the step rate of controller.
-     * @type {number}
-     * @memberof InitializeMovementRequest
-     */
-    'response_rate'?: number;
     /**
      * Unique identifier addressing a coordinate system to which the responses are transformed. If not set, world coordinate system is used.
      * @type {string}
@@ -2161,7 +2166,7 @@ export declare const InitializeMovementResponseKindEnum: {
 };
 export type InitializeMovementResponseKindEnum = typeof InitializeMovementResponseKindEnum[keyof typeof InitializeMovementResponseKindEnum];
 /**
- * Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > We recommend to use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value.
+ * Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > Recommended: Use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value.
  * @export
  * @interface IntegerValue
  */
@@ -2362,9 +2367,19 @@ export type JoggingDetailsKindEnum = typeof JoggingDetailsKindEnum[keyof typeof
  * @type JoggingDetailsState
  * @export
  */
-export type JoggingDetailsState = JoggingPausedByUser | JoggingPausedNearCollision | JoggingPausedNearJointLimit | JoggingPausedOnIO | JoggingRunning;
+export type JoggingDetailsState = {
+    kind: 'PAUSED_BY_USER';
+} & JoggingPausedByUser | {
+    kind: 'PAUSED_NEAR_COLLISION';
+} & JoggingPausedNearCollision | {
+    kind: 'PAUSED_NEAR_JOINT_LIMIT';
+} & JoggingPausedNearJointLimit | {
+    kind: 'PAUSED_ON_IO';
+} & JoggingPausedOnIO | {
+    kind: 'RUNNING';
+} & JoggingRunning;
 /**
- *
+ * User has paused jogging.
  * @export
  * @interface JoggingPausedByUser
  */
@@ -2381,7 +2396,7 @@ export declare const JoggingPausedByUserKindEnum: {
 };
 export type JoggingPausedByUserKindEnum = typeof JoggingPausedByUserKindEnum[keyof typeof JoggingPausedByUserKindEnum];
 /**
- *
+ * Jogging was paused because the motion group neared a collision.
  * @export
  * @interface JoggingPausedNearCollision
  */
@@ -2404,7 +2419,7 @@ export declare const JoggingPausedNearCollisionKindEnum: {
 };
 export type JoggingPausedNearCollisionKindEnum = typeof JoggingPausedNearCollisionKindEnum[keyof typeof JoggingPausedNearCollisionKindEnum];
 /**
- *
+ * Jogging was paused because a joint is near its limit.
  * @export
  * @interface JoggingPausedNearJointLimit
  */
@@ -2427,7 +2442,7 @@ export declare const JoggingPausedNearJointLimitKindEnum: {
 };
 export type JoggingPausedNearJointLimitKindEnum = typeof JoggingPausedNearJointLimitKindEnum[keyof typeof JoggingPausedNearJointLimitKindEnum];
 /**
- *
+ * Jogging was paused because of an I/O event.
  * @export
  * @interface JoggingPausedOnIO
  */
@@ -2444,7 +2459,7 @@ export declare const JoggingPausedOnIOKindEnum: {
 };
 export type JoggingPausedOnIOKindEnum = typeof JoggingPausedOnIOKindEnum[keyof typeof JoggingPausedOnIOKindEnum];
 /**
- *
+ * Jogging is active.
  * @export
  * @interface JoggingRunning
  */
@@ -2512,10 +2527,10 @@ export interface JointLimits {
 export interface JointTrajectory {
     /**
      * List of joint positions [rad] for each sample. The number of samples must match the number of timestamps provided in the times field.
-     * @type {Array<Joints>}
+     * @type {Array<Array<number>>}
      * @memberof JointTrajectory
      */
-    'joint_positions': Array<Joints>;
+    'joint_positions': Array<Array<number>>;
     /**
      * Timestamp for each sample [s].
      * @type {Array<number>}
@@ -2523,7 +2538,7 @@ export interface JointTrajectory {
      */
     'times': Array<number>;
     /**
-     * Location for each sample, scalar value defining a position along a path. Typical range: 0 to `n`, `n` denoting the number of motion commands. Each integer value of the location corresponds to a specific motion command. If provided, the number of samples must match the number of timestamps provided in the times field.
+     *
      * @type {Array<number>}
      * @memberof JointTrajectory
      */
@@ -2542,11 +2557,11 @@ export interface JointVelocityRequest {
      */
     'message_type'?: JointVelocityRequestMessageTypeEnum;
     /**
-     * in [rad/s]
-     * @type {Joints}
+     * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+     * @type {Array<number>}
      * @memberof JointVelocityRequest
      */
-    'velocity': Joints;
+    'velocity': Array<number>;
 }
 export declare const JointVelocityRequestMessageTypeEnum: {
     readonly JointVelocityRequest: "JointVelocityRequest";
@@ -2575,19 +2590,6 @@ export declare const JointVelocityResponseKindEnum: {
     readonly JointVelocityReceived: "JOINT_VELOCITY_RECEIVED";
 };
 export type JointVelocityResponseKindEnum = typeof JointVelocityResponseKindEnum[keyof typeof JointVelocityResponseKindEnum];
-/**
- * This structure describes a set of joint values of a motion group.  We call a set of joint values describing the current position in joint space of a motion group a \"joint position\". Joint position was chosen as the term to be consistent with the terms \"joint velocity\" and \"joint acceleration\".  `joints` must have as many entries as the motion group\'s degrees of freedom to be valid.  Float precision is the default.
- * @export
- * @interface Joints
- */
-export interface Joints {
-    /**
-     *
-     * @type {Array<number>}
-     * @memberof Joints
-     */
-    'joints': Array<number>;
-}
 /**
  * The configuration of a physical KUKA robot controller has to contain an IP address. Additionally an RSI server configuration has to be specified in order to control the robot. Deploying the server is a functionality of this API.
  * @export
@@ -2618,6 +2620,12 @@ export interface KukaController {
      * @memberof KukaController
      */
     'rsi_server': KukaControllerRsiServer;
+    /**
+     * If true, uses slower cycle time of 12ms instead of 4ms.
+     * @type {boolean}
+     * @memberof KukaController
+     */
+    'slow_cycle_rate'?: boolean;
 }
 export declare const KukaControllerKindEnum: {
     readonly KukaController: "KukaController";
@@ -2743,25 +2751,6 @@ export declare const LicenseStatusEnum: {
     readonly NotFound: "NOT_FOUND";
 };
 export type LicenseStatusEnum = typeof LicenseStatusEnum[keyof typeof LicenseStatusEnum];
-/**
- *
- * @export
- * @interface LimitConfig
- */
-export interface LimitConfig {
-    /**
-     *
-     * @type {LimitSet}
-     * @memberof LimitConfig
-     */
-    'physical_limits'?: LimitSet;
-    /**
-     *
-     * @type {OperationLimits}
-     * @memberof LimitConfig
-     */
-    'operation_limits'?: OperationLimits;
-}
 /**
  * The upper_limit must be greater then the lower_limit.
  * @export
@@ -2811,6 +2800,12 @@ export interface LimitSet {
      * @memberof LimitSet
      */
     'flange'?: CartesianLimits;
+    /**
+     *
+     * @type {JointLimits}
+     * @memberof LimitSet
+     */
+    'coupled_shoulder_elbow_joint'?: JointLimits;
 }
 /**
  * If a limit is not set, the default value will be used.
@@ -2882,13 +2877,13 @@ export declare const Manufacturer: {
 };
 export type Manufacturer = typeof Manufacturer[keyof typeof Manufacturer];
 /**
- * Midpoint insertion algorithm configuration for collision-free path planning. This algorithm iteratively inserts midpoints between the start and target joint position to find collision-free paths.
+ *
  * @export
  * @interface MidpointInsertionAlgorithm
  */
 export interface MidpointInsertionAlgorithm {
     /**
-     * Algorithm discriminator.
+     * Algorithm discriminator.  Midpoint insertion algorithm configuration for collision-free path planning. This algorithm adds a single midpoint between the start and target joint position to find collision-free paths.
      * @type {string}
      * @memberof MidpointInsertionAlgorithm
      */
@@ -2976,13 +2971,13 @@ export interface MotionGroupDescription {
      * @type {Pose}
      * @memberof MotionGroupDescription
      */
-    'mounting': Pose;
+    'mounting'?: Pose;
     /**
      * Maps a TCP name to its offset relative to the flange coordinate system. Key must be a TCP identifier. Values are TcpOffsets.
      * @type {{ [key: string]: TcpOffset; }}
      * @memberof MotionGroupDescription
      */
-    'tcps': {
+    'tcps'?: {
         [key: string]: TcpOffset;
     };
     /**
@@ -3013,10 +3008,10 @@ export interface MotionGroupDescription {
     };
     /**
      *
-     * @type {LimitConfig}
+     * @type {OperationLimits}
      * @memberof MotionGroupDescription
      */
-    'global_limits': LimitConfig;
+    'operation_limits': OperationLimits;
     /**
      * Maps a payload name to its configuration. Key must be a payload identifier. Values are payload objects.
      * @type {{ [key: string]: Payload; }}
@@ -3176,11 +3171,11 @@ export interface MotionGroupState {
      */
     'controller': string;
     /**
-     * Current joint position of each joint in [rad]
-     * @type {Joints}
+     * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+     * @type {Array<number>}
      * @memberof MotionGroupState
      */
-    'joint_position': Joints;
+    'joint_position': Array<number>;
     /**
      * Indicates whether the joint is in a limit for all joints of the motion group.
      * @type {MotionGroupStateJointLimitReached}
@@ -3188,17 +3183,17 @@ export interface MotionGroupState {
      */
     'joint_limit_reached': MotionGroupStateJointLimitReached;
     /**
-     * Current joint torque of each joint in [Nm]. Is only available if the robot controller supports it, e.g. available for UR controllers.
-     * @type {Joints}
+     * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+     * @type {Array<number>}
      * @memberof MotionGroupState
      */
-    'joint_torque'?: Joints;
+    'joint_torque'?: Array<number>;
     /**
-     * Current at TCP in [A]. Is only available if the robot controller supports it, e.g. available for UR controllers.
-     * @type {Joints}
+     * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+     * @type {Array<number>}
      * @memberof MotionGroupState
      */
-    'joint_current'?: Joints;
+    'joint_current'?: Array<number>;
     /**
      * Pose of the flange. Positions are in [mm]. Oriantations are in [rad]. The pose is relative to the response_coordinate_system specified in the request. For robot arms a flange pose is always returned, for positioners the flange might not be available, depending on the model.
      * @type {Pose}
@@ -3629,6 +3624,12 @@ export interface PauseOnIO {
      * @memberof PauseOnIO
      */
     'comparator': Comparator;
+    /**
+     *
+     * @type {IOOrigin}
+     * @memberof PauseOnIO
+     */
+    'io_origin': IOOrigin;
 }
 /**
  *
@@ -3749,11 +3750,11 @@ export interface PlanTrajectoryFailedResponse {
      */
     'error_feedback': PlanTrajectoryFailedResponseErrorFeedback;
     /**
-     *
+     * Location on trajectory where the execution will start. The default value is the start (forward movement) or end (backward movement) of the trajectory. If you want to start your movement from an arbitrary location, e.g. in combination with [streamMoveToTrajectoryViaJointPTP](streamMoveToTrajectoryViaJointPTP), set the location by respecting the following format: - The location is a scalar value that defines a position along a path, typically ranging from 0 to `n`,   where `n` denotes the number of motion commands - Each integer value of the location corresponds to a specific motion command,   while non-integer values interpolate positions within the segments. - The location is calculated from the joint path
      * @type {number}
      * @memberof PlanTrajectoryFailedResponse
      */
-    'error_location_on_trajectory'?: number;
+    'error_location_on_trajectory': number;
     /**
      * The joint trajectory from the start joint position to the error.
      * @type {JointTrajectory}
@@ -3986,11 +3987,11 @@ export interface ProfinetDescription {
  */
 export interface ProfinetIO {
     /**
-     * The name of the input/output variable. This is a human-readable identifier for the value. It distinguishes between different inputs/outputs variables in the system. The variables may be used to set bits or bytes at their pointed to address via [setBusIOValues](setBusIOValues).
+     * Descriptive name or note for the input/output variable.
      * @type {string}
      * @memberof ProfinetIO
      */
-    'name': string;
+    'description': string;
     /**
      *
      * @type {ProfinetIOTypeEnum}
@@ -4029,11 +4030,11 @@ export interface ProfinetIO {
  */
 export interface ProfinetIOData {
     /**
-     * The name of the input/output variable. This is a human-readable identifier for the value. It distinguishes between different inputs/outputs variables in the system. The variables may be used to set bits or bytes at their pointed to address via [setBusIOValues](setBusIOValues).
+     * Descriptive name or note for the input/output variable.
      * @type {string}
      * @memberof ProfinetIOData
      */
-    'name': string;
+    'description': string;
     /**
      *
      * @type {ProfinetIOTypeEnum}
@@ -4164,13 +4165,155 @@ export interface ProfinetSubSlotDescription {
     'output_length': number;
 }
 /**
- * <!-- theme: danger -->  > **Experimental**  RRT Connect algorithm configuration for collision-free path planning. Rapidly-exploring Random Trees (RRT) builds trees of valid configurations by randomly sampling the joint space and connecting feasible points. RRT Connect grows two trees simultaneously from start and target positions until they meet. This is a custom implementation optimized for manipulator kinematics and collision checking in industrial contexts.
+ * A program is a collection of instructions that are executed in the robot cell.
+ * @export
+ * @interface Program
+ */
+export interface Program {
+    /**
+     *
+     * @type {string}
+     * @memberof Program
+     */
+    'program': string;
+    /**
+     *
+     * @type {string}
+     * @memberof Program
+     */
+    'name'?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Program
+     */
+    'description'?: string;
+    /**
+     *
+     * @type {string}
+     * @memberof Program
+     */
+    'app': string;
+    /**
+     *
+     * @type {object}
+     * @memberof Program
+     */
+    'input_schema'?: object;
+    /**
+     *
+     * @type {object}
+     * @memberof Program
+     */
+    'preconditions'?: object;
+}
+/**
+ * Holds the state of a program run.
+ * @export
+ * @interface ProgramRun
+ */
+export interface ProgramRun {
+    /**
+     * Unique identifier of the program run
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'run': string;
+    /**
+     * Unique identifier of the program
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'program': string;
+    /**
+     * State of the program run
+     * @type {ProgramRunState}
+     * @memberof ProgramRun
+     */
+    'state': ProgramRunState;
+    /**
+     * Logs of the program run
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'logs'?: string;
+    /**
+     * Stdout of the program run
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'stdout'?: string;
+    /**
+     * Stderr of the program run
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'stderr'?: string;
+    /**
+     * Error message of the program run, if any
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'error'?: string;
+    /**
+     * Traceback of the program run, if any
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'traceback'?: string;
+    /**
+     * Start time of the program run
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'start_time'?: string;
+    /**
+     * End time of the program run
+     * @type {string}
+     * @memberof ProgramRun
+     */
+    'end_time'?: string;
+    /**
+     * Input data of the program run
+     * @type {object}
+     * @memberof ProgramRun
+     */
+    'input_data'?: object;
+}
+/**
+ * The state of a program run.
+ * @export
+ * @enum {string}
+ */
+export declare const ProgramRunState: {
+    readonly Preparing: "PREPARING";
+    readonly Running: "RUNNING";
+    readonly Completed: "COMPLETED";
+    readonly Failed: "FAILED";
+    readonly Stopped: "STOPPED";
+};
+export type ProgramRunState = typeof ProgramRunState[keyof typeof ProgramRunState];
+/**
+ * The state of a program run.
+ * @export
+ * @interface ProgramStartRequest
+ */
+export interface ProgramStartRequest {
+    /**
+     * The arguments to pass to the program.
+     * @type {object}
+     * @memberof ProgramStartRequest
+     */
+    'arguments': object;
+}
+/**
+ *
  * @export
  * @interface RRTConnectAlgorithm
  */
 export interface RRTConnectAlgorithm {
     /**
-     * Algorithm discriminator.
+     * Algorithm discriminator.  RRT Connect algorithm configuration for collision-free path planning. Rapidly-exploring Random Trees (RRT) builds trees of valid configurations by randomly sampling the joint space and connecting feasible points with JointPTP motions. RRT Connect grows two trees simultaneously from start and target positions until they meet. This is a custom implementation optimized for manipulator kinematics and collision checking in industrial contexts.
      * @type {string}
      * @memberof RRTConnectAlgorithm
      */
@@ -4181,6 +4324,30 @@ export interface RRTConnectAlgorithm {
      * @memberof RRTConnectAlgorithm
      */
     'max_iterations'?: number;
+    /**
+     * Maximum step size for tree extension in joint space.
+     * @type {number}
+     * @memberof RRTConnectAlgorithm
+     */
+    'max_step_size'?: number;
+    /**
+     * Adjust the maximum step size during the search based on the recent success rate of tree expansion.
+     * @type {boolean}
+     * @memberof RRTConnectAlgorithm
+     */
+    'adaptive_step_size'?: boolean;
+    /**
+     * Apply smoothing after the search has succeeded. This will remove as many intermediate points as possible while keeping the path valid.
+     * @type {boolean}
+     * @memberof RRTConnectAlgorithm
+     */
+    'apply_smoothing'?: boolean;
+    /**
+     * Apply blending after the search has succeeded and smoothing has been applied. This will apply the largest viable blending at each intermediate point.
+     * @type {boolean}
+     * @memberof RRTConnectAlgorithm
+     */
+    'apply_blending'?: boolean;
 }
 export declare const RRTConnectAlgorithmAlgorithmNameEnum: {
     readonly RrtConnectAlgorithm: "RRTConnectAlgorithm";
@@ -4564,6 +4731,31 @@ export interface ServiceStatusStatus {
      */
     'reason'?: string;
 }
+/**
+ * Defines an input/output that should be set upon reaching a specified location on the trajectory.
+ * @export
+ * @interface SetIO
+ */
+export interface SetIO {
+    /**
+     *
+     * @type {IOValue}
+     * @memberof SetIO
+     */
+    'io': IOValue;
+    /**
+     * The location on the trajectory where the input/output should be set.
+     * @type {number}
+     * @memberof SetIO
+     */
+    'location': number;
+    /**
+     *
+     * @type {IOOrigin}
+     * @memberof SetIO
+     */
+    'io_origin': IOOrigin;
+}
 /**
  *
  * @export
@@ -4626,12 +4818,18 @@ export interface StartMovementRequest {
      * @memberof StartMovementRequest
      */
     'direction'?: Direction;
+    /**
+     * Location on trajectory where the execution will start. The default value is the start (forward movement) or end (backward movement) of the trajectory. If you want to start your movement from an arbitrary location, e.g. in combination with [streamMoveToTrajectoryViaJointPTP](streamMoveToTrajectoryViaJointPTP), set the location by respecting the following format: - The location is a scalar value that defines a position along a path, typically ranging from 0 to `n`,   where `n` denotes the number of motion commands - Each integer value of the location corresponds to a specific motion command,   while non-integer values interpolate positions within the segments. - The location is calculated from the joint path
+     * @type {number}
+     * @memberof StartMovementRequest
+     */
+    'target_location'?: number;
     /**
      * Attaches a list of output commands to the trajectory. The outputs are set to the specified values right after the specified location was reached. If the specified location is located before the start location (forward direction: value is smaller, backward direction: value is bigger), the output is not set.
-     * @type {Array<IOValue>}
+     * @type {Array<SetIO>}
      * @memberof StartMovementRequest
      */
-    'set_outputs'?: Array<IOValue>;
+    'set_outputs'?: Array<SetIO>;
     /**
      * Defines an input/output that is listened to before the movement. Execution starts if the defined comparator evaluates to `true`.
      * @type {StartOnIO}
@@ -4690,6 +4888,12 @@ export interface StartOnIO {
      * @memberof StartOnIO
      */
     'comparator': Comparator;
+    /**
+     *
+     * @type {IOOrigin}
+     * @memberof StartOnIO
+     */
+    'io_origin': IOOrigin;
 }
 /**
  * Array of input/output values.
@@ -4886,7 +5090,7 @@ export interface TrajectoryDetails {
      */
     'trajectory': string;
     /**
-     * Current location of motion group on the trajectory.
+     * Location on trajectory where the execution will start. The default value is the start (forward movement) or end (backward movement) of the trajectory. If you want to start your movement from an arbitrary location, e.g. in combination with [streamMoveToTrajectoryViaJointPTP](streamMoveToTrajectoryViaJointPTP), set the location by respecting the following format: - The location is a scalar value that defines a position along a path, typically ranging from 0 to `n`,   where `n` denotes the number of motion commands - Each integer value of the location corresponds to a specific motion command,   while non-integer values interpolate positions within the segments. - The location is calculated from the joint path
      * @type {number}
      * @memberof TrajectoryDetails
      */
@@ -4912,9 +5116,19 @@ export type TrajectoryDetailsKindEnum = typeof TrajectoryDetailsKindEnum[keyof t
  * @type TrajectoryDetailsState
  * @export
  */
-export type TrajectoryDetailsState = TrajectoryEnded | TrajectoryPausedByUser | TrajectoryPausedOnIO | TrajectoryRunning | TrajectoryWaitForIO;
+export type TrajectoryDetailsState = {
+    kind: 'END_OF_TRAJECTORY';
+} & TrajectoryEnded | {
+    kind: 'PAUSED_BY_USER';
+} & TrajectoryPausedByUser | {
+    kind: 'PAUSED_ON_IO';
+} & TrajectoryPausedOnIO | {
+    kind: 'RUNNING';
+} & TrajectoryRunning | {
+    kind: 'WAIT_FOR_IO';
+} & TrajectoryWaitForIO;
 /**
- *
+ * First or last sample (depending on direction) of trajectory has been sent.
  * @export
  * @interface TrajectoryEnded
  */
@@ -4941,7 +5155,7 @@ export interface TrajectoryId {
      * @type {string}
      * @memberof TrajectoryId
      */
-    'message_type'?: TrajectoryIdMessageTypeEnum;
+    'message_type': TrajectoryIdMessageTypeEnum;
     /**
      * The identifier of the trajectory which was returned by the [addTrajectory](addTrajectory) endpoint.
      * @type {string}
@@ -4954,7 +5168,7 @@ export declare const TrajectoryIdMessageTypeEnum: {
 };
 export type TrajectoryIdMessageTypeEnum = typeof TrajectoryIdMessageTypeEnum[keyof typeof TrajectoryIdMessageTypeEnum];
 /**
- *
+ * User has paused execution.
  * @export
  * @interface TrajectoryPausedByUser
  */
@@ -4971,7 +5185,7 @@ export declare const TrajectoryPausedByUserKindEnum: {
 };
 export type TrajectoryPausedByUserKindEnum = typeof TrajectoryPausedByUserKindEnum[keyof typeof TrajectoryPausedByUserKindEnum];
 /**
- *
+ * Execution was paused because of an I/O event.
  * @export
  * @interface TrajectoryPausedOnIO
  */
@@ -4988,7 +5202,7 @@ export declare const TrajectoryPausedOnIOKindEnum: {
 };
 export type TrajectoryPausedOnIOKindEnum = typeof TrajectoryPausedOnIOKindEnum[keyof typeof TrajectoryPausedOnIOKindEnum];
 /**
- *
+ * Trajectory is being executed.
  * @export
  * @interface TrajectoryRunning
  */
@@ -5011,7 +5225,7 @@ export declare const TrajectoryRunningKindEnum: {
 };
 export type TrajectoryRunningKindEnum = typeof TrajectoryRunningKindEnum[keyof typeof TrajectoryRunningKindEnum];
 /**
- *
+ * Waiting for an I/O event to start execution.
  * @export
  * @interface TrajectoryWaitForIO
  */
@@ -5114,6 +5328,31 @@ export interface ValidationError {
         [key: string]: any;
     };
 }
+/**
+ * A validation error of a program.
+ * @export
+ * @interface ValidationError2
+ */
+export interface ValidationError2 {
+    /**
+     *
+     * @type {Array<number>}
+     * @memberof ValidationError2
+     */
+    'loc': Array<number>;
+    /**
+     *
+     * @type {string}
+     * @memberof ValidationError2
+     */
+    'msg': string;
+    /**
+     *
+     * @type {string}
+     * @memberof ValidationError2
+     */
+    'type': string;
+}
 /**
  * @type ValidationErrorLocInner
  * @export
@@ -5236,11 +5475,13 @@ export declare const VirtualControllerTypes: {
     readonly KukaKr4R600: "kuka-kr4_r600";
     readonly KukaKr500L3403: "kuka-kr500_l340_3";
     readonly KukaKr50R2500: "kuka-kr50_r2500";
+    readonly KukaKr60R3: "kuka-kr60_r3";
     readonly KukaKr6R1820: "kuka-kr6_r1820";
     readonly KukaKr6R7002: "kuka-kr6_r700_2";
     readonly KukaKr6R700Sixx: "kuka-kr6_r700_sixx";
     readonly KukaKr6R900: "kuka-kr6_r900";
     readonly KukaKr6R9002: "kuka-kr6_r900_2";
+    readonly KukaKr70R2100: "kuka-kr70_r2100";
     readonly KukaLbrIisy11R1300: "kuka-lbr_iisy_11_r1300";
     readonly UniversalrobotsUr10cb: "universalrobots-ur10cb";
     readonly UniversalrobotsUr10e: "universalrobots-ur10e";
@@ -5685,7 +5926,7 @@ export declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Conf
      */
     getProfinetIOsFromFile: (cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service.
+     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service.
      * @summary List Descriptions
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -5693,7 +5934,7 @@ export declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Conf
      */
     listBusIODescriptions: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
+     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
      * @summary List PROFINET Input/Output Configuration
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -5710,7 +5951,7 @@ export declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Conf
      */
     setBusIOValues: (cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled, meaning that you can paste the exported XML file here without modifying.
+     * Sets input/output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying.
      * @summary Set PROFINET Inputs/Outputs from File
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {ProfinetInputOutputConfig} profinetInputOutputConfig
@@ -5806,7 +6047,7 @@ export declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
      */
     getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<string>>;
     /**
-     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service.
+     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service.
      * @summary List Descriptions
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -5814,7 +6055,7 @@ export declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
      */
     listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<IODescription2>>>;
     /**
-     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
+     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
      * @summary List PROFINET Input/Output Configuration
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -5831,7 +6072,7 @@ export declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
      */
     setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
     /**
-     * Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled, meaning that you can paste the exported XML file here without modifying.
+     * Sets input/output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying.
      * @summary Set PROFINET Inputs/Outputs from File
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {ProfinetInputOutputConfig} profinetInputOutputConfig
@@ -5927,7 +6168,7 @@ export declare const BUSInputsOutputsApiFactory: (configuration?: Configuration,
      */
     getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): AxiosPromise<string>;
     /**
-     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service.
+     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service.
      * @summary List Descriptions
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -5935,7 +6176,7 @@ export declare const BUSInputsOutputsApiFactory: (configuration?: Configuration,
      */
     listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<IODescription2>>;
     /**
-     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
+     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
      * @summary List PROFINET Input/Output Configuration
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -5952,7 +6193,7 @@ export declare const BUSInputsOutputsApiFactory: (configuration?: Configuration,
      */
     setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): AxiosPromise<void>;
     /**
-     * Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled, meaning that you can paste the exported XML file here without modifying.
+     * Sets input/output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying.
      * @summary Set PROFINET Inputs/Outputs from File
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {ProfinetInputOutputConfig} profinetInputOutputConfig
@@ -6059,7 +6300,7 @@ export declare class BUSInputsOutputsApi extends BaseAPI {
      */
     getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<string, any>>;
     /**
-     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service.
+     * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service.
      * @summary List Descriptions
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -6068,7 +6309,7 @@ export declare class BUSInputsOutputsApi extends BaseAPI {
      */
     listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<IODescription2[], any>>;
     /**
-     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
+     * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service\'s configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal.
      * @summary List PROFINET Input/Output Configuration
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -6087,7 +6328,7 @@ export declare class BUSInputsOutputsApi extends BaseAPI {
      */
     setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
     /**
-     * Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled, meaning that you can paste the exported XML file here without modifying.
+     * Sets input/output variable configuration on the PROFINET device (i.e. NOVA\'s PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA\'s PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA\'s PROFINET service\'s configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device\'s input is PROFINET Controller\'s output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying.
      * @summary Set PROFINET Inputs/Outputs from File
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {ProfinetInputOutputConfig} profinetInputOutputConfig
@@ -7677,7 +7918,7 @@ export declare class MotionGroupApi extends BaseAPI {
  */
 export declare const MotionGroupModelsApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupDescription](getMotionGroupDescription) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Use the `stored_link_chain` or `link_chain` field in [storeCollisionScene](storeCollisionScene) to attach additional shapes to the link reference frames. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
+     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupModels](getMotionGroupModels) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Attach additional shapes to the link reference frames by extending the link dictionaries before further use. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
      * @summary Get Collision Model
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} motionGroupModel Unique identifier for the model of a motion group, e.g. &#x60;UniversalRobots_UR10e&#x60;.  Get the &#x60;model&#x60; of a configured motion group with [getOptimizerConfiguration](getOptimizerConfiguration).
@@ -7700,7 +7941,7 @@ export declare const MotionGroupModelsApiAxiosParamCreator: (configuration?: Con
  */
 export declare const MotionGroupModelsApiFp: (configuration?: Configuration) => {
     /**
-     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupDescription](getMotionGroupDescription) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Use the `stored_link_chain` or `link_chain` field in [storeCollisionScene](storeCollisionScene) to attach additional shapes to the link reference frames. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
+     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupModels](getMotionGroupModels) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Attach additional shapes to the link reference frames by extending the link dictionaries before further use. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
      * @summary Get Collision Model
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} motionGroupModel Unique identifier for the model of a motion group, e.g. &#x60;UniversalRobots_UR10e&#x60;.  Get the &#x60;model&#x60; of a configured motion group with [getOptimizerConfiguration](getOptimizerConfiguration).
@@ -7725,7 +7966,7 @@ export declare const MotionGroupModelsApiFp: (configuration?: Configuration) =>
  */
 export declare const MotionGroupModelsApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupDescription](getMotionGroupDescription) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Use the `stored_link_chain` or `link_chain` field in [storeCollisionScene](storeCollisionScene) to attach additional shapes to the link reference frames. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
+     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupModels](getMotionGroupModels) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Attach additional shapes to the link reference frames by extending the link dictionaries before further use. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
      * @summary Get Collision Model
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} motionGroupModel Unique identifier for the model of a motion group, e.g. &#x60;UniversalRobots_UR10e&#x60;.  Get the &#x60;model&#x60; of a configured motion group with [getOptimizerConfiguration](getOptimizerConfiguration).
@@ -7752,7 +7993,7 @@ export declare const MotionGroupModelsApiFactory: (configuration?: Configuration
  */
 export declare class MotionGroupModelsApi extends BaseAPI {
     /**
-     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupDescription](getMotionGroupDescription) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Use the `stored_link_chain` or `link_chain` field in [storeCollisionScene](storeCollisionScene) to attach additional shapes to the link reference frames. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
+     * Returns the default collision link chain for a given motion group model.  See [getMotionGroupModels](getMotionGroupModels) for supported motion group models.  The default link chain is derived from 3D models and optimized for collision detection within NOVA.  The default link chain includes link shapes only. It does not include any attached components like wire feeders or sensors.  Attach additional shapes to the link reference frames by extending the link dictionaries before further use. Additional shapes may overlap each other per link and may also overlap the respective link\'s default shape.
      * @summary Get Collision Model
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} motionGroupModel Unique identifier for the model of a motion group, e.g. &#x60;UniversalRobots_UR10e&#x60;.  Get the &#x60;model&#x60; of a configured motion group with [getOptimizerConfiguration](getOptimizerConfiguration).
@@ -7773,6 +8014,180 @@ export declare class MotionGroupModelsApi extends BaseAPI {
      */
     getMotionGroupModels(cell: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<string[], any>>;
 }
+/**
+ * ProgramApi - axios parameter creator
+ * @export
+ */
+export declare const ProgramApiAxiosParamCreator: (configuration?: Configuration) => {
+    /**
+     * Get details of a program.
+     * @summary Get program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getProgram: (cell: string, program: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * List details of all existing programs.
+     * @summary List programs
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listPrograms: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * This endpoint starts a new program execution.  The program will be executed asynchronously.
+     * @summary Start the program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {ProgramStartRequest} programStartRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    startProgram: (cell: string, program: string, programStartRequest: ProgramStartRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    /**
+     * Stop a specific program run.
+     * @summary Stop program run
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    stopProgram: (cell: string, program: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+};
+/**
+ * ProgramApi - functional programming interface
+ * @export
+ */
+export declare const ProgramApiFp: (configuration?: Configuration) => {
+    /**
+     * Get details of a program.
+     * @summary Get program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getProgram(cell: string, program: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Program>>;
+    /**
+     * List details of all existing programs.
+     * @summary List programs
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listPrograms(cell: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<Program>>>;
+    /**
+     * This endpoint starts a new program execution.  The program will be executed asynchronously.
+     * @summary Start the program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {ProgramStartRequest} programStartRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    startProgram(cell: string, program: string, programStartRequest: ProgramStartRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ProgramRun>>;
+    /**
+     * Stop a specific program run.
+     * @summary Stop program run
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    stopProgram(cell: string, program: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
+};
+/**
+ * ProgramApi - factory interface
+ * @export
+ */
+export declare const ProgramApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
+    /**
+     * Get details of a program.
+     * @summary Get program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    getProgram(cell: string, program: string, options?: RawAxiosRequestConfig): AxiosPromise<Program>;
+    /**
+     * List details of all existing programs.
+     * @summary List programs
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    listPrograms(cell: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<Program>>;
+    /**
+     * This endpoint starts a new program execution.  The program will be executed asynchronously.
+     * @summary Start the program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {ProgramStartRequest} programStartRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    startProgram(cell: string, program: string, programStartRequest: ProgramStartRequest, options?: RawAxiosRequestConfig): AxiosPromise<ProgramRun>;
+    /**
+     * Stop a specific program run.
+     * @summary Stop program run
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     */
+    stopProgram(cell: string, program: string, options?: RawAxiosRequestConfig): AxiosPromise<void>;
+};
+/**
+ * ProgramApi - object-oriented interface
+ * @export
+ * @class ProgramApi
+ * @extends {BaseAPI}
+ */
+export declare class ProgramApi extends BaseAPI {
+    /**
+     * Get details of a program.
+     * @summary Get program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof ProgramApi
+     */
+    getProgram(cell: string, program: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<Program, any>>;
+    /**
+     * List details of all existing programs.
+     * @summary List programs
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof ProgramApi
+     */
+    listPrograms(cell: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<Program[], any>>;
+    /**
+     * This endpoint starts a new program execution.  The program will be executed asynchronously.
+     * @summary Start the program
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {ProgramStartRequest} programStartRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof ProgramApi
+     */
+    startProgram(cell: string, program: string, programStartRequest: ProgramStartRequest, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<ProgramRun, any>>;
+    /**
+     * Stop a specific program run.
+     * @summary Stop program run
+     * @param {string} cell Unique identifier addressing a cell in all API calls.
+     * @param {string} program
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof ProgramApi
+     */
+    stopProgram(cell: string, program: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
+}
 /**
  * StoreCollisionComponentsApi - axios parameter creator
  * @export
@@ -7841,7 +8256,7 @@ export declare const StoreCollisionComponentsApiAxiosParamCreator: (configuratio
      */
     listCollisionLinkChains: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Returns a list of colliders in a scene. This excludes colliders that are part of a motion group.
+     * Returns all stored colliders.
      * @summary List Colliders
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -7967,7 +8382,7 @@ export declare const StoreCollisionComponentsApiFp: (configuration?: Configurati
         }>;
     }>>;
     /**
-     * Returns a list of colliders in a scene. This excludes colliders that are part of a motion group.
+     * Returns all stored colliders.
      * @summary List Colliders
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -8103,7 +8518,7 @@ export declare const StoreCollisionComponentsApiFactory: (configuration?: Config
         }>;
     }>;
     /**
-     * Returns a list of colliders in a scene. This excludes colliders that are part of a motion group.
+     * Returns all stored colliders.
      * @summary List Colliders
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -8248,7 +8663,7 @@ export declare class StoreCollisionComponentsApi extends BaseAPI {
         }[];
     }, any>>;
     /**
-     * Returns a list of colliders in a scene. This excludes colliders that are part of a motion group.
+     * Returns all stored colliders.
      * @summary List Colliders
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {*} [options] Override http request option.
@@ -9468,7 +9883,7 @@ export declare class TrajectoryPlanningApi extends BaseAPI {
  */
 export declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configuration) => {
     /**
-     * Adds a coordinate system to the robot controller.
+     * Adds a coordinate system to the robot controller.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be available for visualization or program execution.
      * @summary Add Coordinate Systems
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9479,7 +9894,7 @@ export declare const VirtualControllerApiAxiosParamCreator: (configuration?: Con
      */
     addVirtualControllerCoordinateSystem: (cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Adds a new TCP or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange’s coordinate system.  > **NOTE** > > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot’s documentation or data sheet for details like joint limits or reach.
+     * Adds a new TCP (Tool Center Point) or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange\'s coordinate system.  > **NOTE** > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot\'s documentation or data sheet for details like joint limits or reach.  **Important notes:** - Adding or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Add TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9491,8 +9906,8 @@ export declare const VirtualControllerApiAxiosParamCreator: (configuration?: Con
      */
     addVirtualControllerTcp: (cell: string, controller: string, motionGroup: string, tcp: string, robotTcpData: RobotTcpData, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and remove all dependent coordinate systems which use the deleted coordinate system as reference.
-     * @summary Remove Coordinate System
+     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and also remove all dependent coordinate systems that use the deleted coordinate system as reference.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be   available for visualization or program execution.
+     * @summary Delete Coordinate System
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
      * @param {string} coordinateSystem Unique identifier addressing a coordinate system.
@@ -9502,7 +9917,7 @@ export declare const VirtualControllerApiAxiosParamCreator: (configuration?: Con
      */
     deleteVirtualControllerCoordinateSystem: (cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Removes the TCP from the motion group. An unknown TCP is a valid input.
+     * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  **Important notes:** - Removing or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Remove TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9610,7 +10025,7 @@ export declare const VirtualControllerApiAxiosParamCreator: (configuration?: Con
      */
     setOperationMode: (cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * Sets motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset. The transformation offset is defined by a unique identifier, a name for front end usage and an offset in another coordinate system referenced by the unique identifier of the reference coordinate system.
+     * Sets the motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset, which consists of: - A unique identifier - A user-facing name - An offset in another coordinate system, referenced by the unique identifier of the reference coordinate system.  **Important notes:** - Changing the mounting configuration is treated as a setup change. - When the mounting is set to a new coordinate system, the **virtual robot restarts** in the background to apply the new configuration. - During this process:   - Robot visualization may temporarily disappear or not reflect the new mounting immediately.   - Motion group state and coordinate system alignment may not be instantly updated in the UI.   - All connections to the virtual robot are closed and then re-established, which can cause a short delay before the system is ready again. - The API call itself does **not wait until the restart and synchronization are complete**.   A successful response indicates that the request was accepted, but the updated mounting may not yet be visible.
      * @summary Set Mounting
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9627,7 +10042,7 @@ export declare const VirtualControllerApiAxiosParamCreator: (configuration?: Con
  */
 export declare const VirtualControllerApiFp: (configuration?: Configuration) => {
     /**
-     * Adds a coordinate system to the robot controller.
+     * Adds a coordinate system to the robot controller.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be available for visualization or program execution.
      * @summary Add Coordinate Systems
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9638,7 +10053,7 @@ export declare const VirtualControllerApiFp: (configuration?: Configuration) =>
      */
     addVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
     /**
-     * Adds a new TCP or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange’s coordinate system.  > **NOTE** > > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot’s documentation or data sheet for details like joint limits or reach.
+     * Adds a new TCP (Tool Center Point) or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange\'s coordinate system.  > **NOTE** > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot\'s documentation or data sheet for details like joint limits or reach.  **Important notes:** - Adding or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Add TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9650,8 +10065,8 @@ export declare const VirtualControllerApiFp: (configuration?: Configuration) =>
      */
     addVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, robotTcpData: RobotTcpData, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
     /**
-     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and remove all dependent coordinate systems which use the deleted coordinate system as reference.
-     * @summary Remove Coordinate System
+     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and also remove all dependent coordinate systems that use the deleted coordinate system as reference.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be   available for visualization or program execution.
+     * @summary Delete Coordinate System
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
      * @param {string} coordinateSystem Unique identifier addressing a coordinate system.
@@ -9661,7 +10076,7 @@ export declare const VirtualControllerApiFp: (configuration?: Configuration) =>
      */
     deleteVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
     /**
-     * Removes the TCP from the motion group. An unknown TCP is a valid input.
+     * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  **Important notes:** - Removing or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Remove TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9769,7 +10184,7 @@ export declare const VirtualControllerApiFp: (configuration?: Configuration) =>
      */
     setOperationMode(cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
     /**
-     * Sets motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset. The transformation offset is defined by a unique identifier, a name for front end usage and an offset in another coordinate system referenced by the unique identifier of the reference coordinate system.
+     * Sets the motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset, which consists of: - A unique identifier - A user-facing name - An offset in another coordinate system, referenced by the unique identifier of the reference coordinate system.  **Important notes:** - Changing the mounting configuration is treated as a setup change. - When the mounting is set to a new coordinate system, the **virtual robot restarts** in the background to apply the new configuration. - During this process:   - Robot visualization may temporarily disappear or not reflect the new mounting immediately.   - Motion group state and coordinate system alignment may not be instantly updated in the UI.   - All connections to the virtual robot are closed and then re-established, which can cause a short delay before the system is ready again. - The API call itself does **not wait until the restart and synchronization are complete**.   A successful response indicates that the request was accepted, but the updated mounting may not yet be visible.
      * @summary Set Mounting
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9786,7 +10201,7 @@ export declare const VirtualControllerApiFp: (configuration?: Configuration) =>
  */
 export declare const VirtualControllerApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
     /**
-     * Adds a coordinate system to the robot controller.
+     * Adds a coordinate system to the robot controller.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be available for visualization or program execution.
      * @summary Add Coordinate Systems
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9797,7 +10212,7 @@ export declare const VirtualControllerApiFactory: (configuration?: Configuration
      */
     addVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig): AxiosPromise<void>;
     /**
-     * Adds a new TCP or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange’s coordinate system.  > **NOTE** > > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot’s documentation or data sheet for details like joint limits or reach.
+     * Adds a new TCP (Tool Center Point) or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange\'s coordinate system.  > **NOTE** > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot\'s documentation or data sheet for details like joint limits or reach.  **Important notes:** - Adding or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Add TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9809,8 +10224,8 @@ export declare const VirtualControllerApiFactory: (configuration?: Configuration
      */
     addVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, robotTcpData: RobotTcpData, options?: RawAxiosRequestConfig): AxiosPromise<void>;
     /**
-     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and remove all dependent coordinate systems which use the deleted coordinate system as reference.
-     * @summary Remove Coordinate System
+     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and also remove all dependent coordinate systems that use the deleted coordinate system as reference.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be   available for visualization or program execution.
+     * @summary Delete Coordinate System
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
      * @param {string} coordinateSystem Unique identifier addressing a coordinate system.
@@ -9820,7 +10235,7 @@ export declare const VirtualControllerApiFactory: (configuration?: Configuration
      */
     deleteVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig): AxiosPromise<void>;
     /**
-     * Removes the TCP from the motion group. An unknown TCP is a valid input.
+     * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  **Important notes:** - Removing or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Remove TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9928,7 +10343,7 @@ export declare const VirtualControllerApiFactory: (configuration?: Configuration
      */
     setOperationMode(cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig): AxiosPromise<void>;
     /**
-     * Sets motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset. The transformation offset is defined by a unique identifier, a name for front end usage and an offset in another coordinate system referenced by the unique identifier of the reference coordinate system.
+     * Sets the motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset, which consists of: - A unique identifier - A user-facing name - An offset in another coordinate system, referenced by the unique identifier of the reference coordinate system.  **Important notes:** - Changing the mounting configuration is treated as a setup change. - When the mounting is set to a new coordinate system, the **virtual robot restarts** in the background to apply the new configuration. - During this process:   - Robot visualization may temporarily disappear or not reflect the new mounting immediately.   - Motion group state and coordinate system alignment may not be instantly updated in the UI.   - All connections to the virtual robot are closed and then re-established, which can cause a short delay before the system is ready again. - The API call itself does **not wait until the restart and synchronization are complete**.   A successful response indicates that the request was accepted, but the updated mounting may not yet be visible.
      * @summary Set Mounting
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9947,7 +10362,7 @@ export declare const VirtualControllerApiFactory: (configuration?: Configuration
  */
 export declare class VirtualControllerApi extends BaseAPI {
     /**
-     * Adds a coordinate system to the robot controller.
+     * Adds a coordinate system to the robot controller.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be available for visualization or program execution.
      * @summary Add Coordinate Systems
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9959,7 +10374,7 @@ export declare class VirtualControllerApi extends BaseAPI {
      */
     addVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
     /**
-     * Adds a new TCP or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange’s coordinate system.  > **NOTE** > > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot’s documentation or data sheet for details like joint limits or reach.
+     * Adds a new TCP (Tool Center Point) or updates an existing TCP in the motion group.  The position and rotation values in the request body are defined within the flange\'s coordinate system.  > **NOTE** > Ensure the TCP\'s position is within the robot\'s reach. Refer to the robot\'s documentation or data sheet for details like joint limits or reach.  **Important notes:** - Adding or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Add TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9972,8 +10387,8 @@ export declare class VirtualControllerApi extends BaseAPI {
      */
     addVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, robotTcpData: RobotTcpData, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
     /**
-     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and remove all dependent coordinate systems which use the deleted coordinate system as reference.
-     * @summary Remove Coordinate System
+     * Deletes a coordinate system from the virtual controller. This will remove the coordinate system from the list of coordinate systems and also remove all dependent coordinate systems that use the deleted coordinate system as reference.  **Important notes:** - When a new coordinate system is added/removed, the **virtual robot is restarted** in the background in order to apply the new configuration. - During this restart:   - Robot visualization may temporarily disappear or appear outdated in the UI.   - coordinate system changes are not immediately visible in visualizations.   - All existing connections to the virtual robot are closed and re-established, which introduces a short delay before the system is fully operational again. - The API call itself does **not wait until the restart and re-synchronization are complete**.   This means that immediately after a successful response, the new coordinate system may not yet be   available for visualization or program execution.
+     * @summary Delete Coordinate System
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
      * @param {string} coordinateSystem Unique identifier addressing a coordinate system.
@@ -9984,7 +10399,7 @@ export declare class VirtualControllerApi extends BaseAPI {
      */
     deleteVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
     /**
-     * Removes the TCP from the motion group. An unknown TCP is a valid input.
+     * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  **Important notes:** - Removing or updating a TCP triggers a **virtual robot restart** to apply the new configuration. - During this restart:   - The robot visualization in the UI may temporarily disappear.   - The TCP visualization may not immediately appear, or may look outdated during the first test/rerun.   - All active connections to the virtual robot are closed and then re-established. This creates a delay before the TCP is available in both the UI and robot programs. - The API call itself does **not wait until the restart and synchronization are complete**.   Even if the request succeeds, the new or updated TCP may not yet be visible in the GUI or available for use.
      * @summary Remove TCP
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10103,7 +10518,7 @@ export declare class VirtualControllerApi extends BaseAPI {
      */
     setOperationMode(cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
     /**
-     * Sets motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset. The transformation offset is defined by a unique identifier, a name for front end usage and an offset in another coordinate system referenced by the unique identifier of the reference coordinate system.
+     * Sets the motion group mounting by specifying a coordinate system. The motion group will be based on the coordinate system\'s origin. The coordinate system defines a transformation offset, which consists of: - A unique identifier - A user-facing name - An offset in another coordinate system, referenced by the unique identifier of the reference coordinate system.  **Important notes:** - Changing the mounting configuration is treated as a setup change. - When the mounting is set to a new coordinate system, the **virtual robot restarts** in the background to apply the new configuration. - During this process:   - Robot visualization may temporarily disappear or not reflect the new mounting immediately.   - Motion group state and coordinate system alignment may not be instantly updated in the UI.   - All connections to the virtual robot are closed and then re-established, which can cause a short delay before the system is ready again. - The API call itself does **not wait until the restart and synchronization are complete**.   A successful response indicates that the request was accepted, but the updated mounting may not yet be visible.
      * @summary Set Mounting
      * @param {string} cell Unique identifier addressing a cell in all API calls.
      * @param {string} controller Unique identifier to address a controller in the cell.