@wandelbots/nova-api 25.9.0-dev.14 → 25.9.0-dev.16

package/dist/v2/index.d.ts

@@ -230,7 +230,7 @@ interface AddTrajectoryError {
    */
   'message'?: string;
   /**
-   * 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
+   * 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
    */
@@ -298,7 +298,7 @@ interface AddTrajectoryResponse {
  */
 interface App {
   /**
-   * The name of the provided application. The name must be unique within the cell and is used as a identifier for addressing the application in all API calls , e.g. when updating the application.  It also defines where the application is reachable (/$cell/$name).  It must be a valid k8s label name as defined by [RFC 1035](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
+   * The name of the provided application. The name must be unique within the cell and is used as a identifier for addressing the application in all API calls , e.g., when updating the application.  It also defines where the application is reachable (/$cell/$name).  It must be a valid k8s label name as defined by [RFC 1035](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#rfc-1035-label-names).
    * @type {string}
    * @memberof App
    */
@@ -353,7 +353,7 @@ interface App {
   'diagnosis_path'?: string;
 }
 /**
- * ## BEHAVIOR_AUTOMATIC This is the default behavior. The motion groups of the controller take commanded joint configuration as actual joint state. Configures the compliance of the virtual robot with the normal ControllerState cycle time. If set, the virtual robot will act like a physical one, e.g. with a cycle time of 8ms to respond to a new joint state command. ## BEHAVIOR_AUTOMATIC_NOT_COMPLY_WITH_CYCLETIME Configures the compliance of the virtual robot with the normal ControllerState cycle time. If set, the robot will respond as fast as possible, limited only by software execution speed. Because of that the execution of a movement requires less time than with BEHAVIOR_AUTOMATIC. ## BEHAVIOR_EXTERNAL_SOURCE The external client is the only source of actual joint state changes. This mode is used to enable third party software indicating the current joint state via [externalJointsStream](externalJointsStream).
+ * ## BEHAVIOR_AUTOMATIC This is the default behavior. The motion groups of the controller take commanded joint configuration as actual joint state. Configures the compliance of the virtual robot with the normal ControllerState cycle time. If set, the virtual robot will act like a physical one, e.g., with a cycle time of 8ms to respond to a new joint state command. ## BEHAVIOR_AUTOMATIC_NOT_COMPLY_WITH_CYCLETIME Configures the compliance of the virtual robot with the normal ControllerState cycle time. If set, the robot will respond as fast as possible, limited only by software execution speed. Because of that the execution of a movement requires less time than with BEHAVIOR_AUTOMATIC. ## BEHAVIOR_EXTERNAL_SOURCE The external client is the only source of actual joint state changes. This mode is used to enable third party software indicating the current joint state via [externalJointsStream](externalJointsStream).
  * @export
  * @enum {string}
  */
@@ -627,7 +627,7 @@ interface BusIOsState {
    */
   'state': BusIOsStateEnum;
   /**
-   * A message providing additional information on the input/output service, e.g. BUS service status, encountered errors. May be empty if no additional information is available.
+   * A message providing additional information on the input/output service, e.g., BUS service status, encountered errors. May be empty if no additional information is available.
    * @type {string}
    * @memberof BusIOsState
    */
@@ -706,7 +706,7 @@ interface CartesianLimits {
   'orientation_acceleration'?: number;
 }
 /**
- * To create a robot cell, only a valid name is required. Once created, a robot cell provides access to the Wandelbots NOVA foundation services. The configuration can be customized, e.g. robot controllers, also within apps.
+ * To create a robot cell, only a valid name is required. Once created, a robot cell provides access to the Wandelbots NOVA foundation services. The configuration can be customized, e.g., robot controllers, also within apps.
  * @export
  * @interface Cell
  */
@@ -1410,7 +1410,7 @@ declare const ErrorJointLimitExceededErrorFeedbackNameEnum: {
 };
 type ErrorJointLimitExceededErrorFeedbackNameEnum = typeof ErrorJointLimitExceededErrorFeedbackNameEnum[keyof typeof ErrorJointLimitExceededErrorFeedbackNameEnum];
 /**
- * A reference joint position (e.g. start or target joint position) results in collisions that prevent processing.
+ * A reference joint position, e.g., start or target joint position, results in collisions that prevent processing.
  * @export
  * @interface ErrorJointPositionCollision
  */
@@ -1960,7 +1960,7 @@ interface IODescription2 {
    */
   'io': string;
   /**
-   * 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
    */
@@ -2247,7 +2247,7 @@ interface InitializeMovementRequest {
    */
   'trajectory': InitializeMovementRequestTrajectory;
   /**
-   * 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
+   * 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 InitializeMovementRequest
    */
@@ -2407,7 +2407,7 @@ interface InverseKinematicsRequest {
    */
   'joint_position_limits'?: Array<LimitRange>;
   /**
-   * Collision layers to be respected by the motion planner when planning for a single motion group. Each setup represents one layer, e.g. the safety zones and shapes or a fine grained tool and workpiece model. Layers are checked individually along the trajectory and independently of other layers.  To respect the safety zones of the controller and check for collision: 1. Fetch the safety zones, link and tool shapes from the controller. 2. Add the fetched zones, links and tools to a layer. 3. Create other layers from your own 3D data as needed. 4. Plan trajectory. 5. The response highlights the layer in which a collision was detected by key.
+   * Collision layers to be respected by the motion planner when planning for a single motion group. Each setup represents one layer, e.g., the safety zones and shapes or a fine grained tool and workpiece model. Layers are checked individually along the trajectory and independently of other layers.  To respect the safety zones of the controller and check for collision: 1. Fetch the safety zones, link and tool shapes from the controller. 2. Add the fetched zones, links and tools to a layer. 3. Create other layers from your own 3D data as needed. 4. Plan trajectory. 5. The response highlights the layer in which a collision was detected by key.
    * @type {{ [key: string]: CollisionSetup; }}
    * @memberof InverseKinematicsRequest
    */
@@ -2694,7 +2694,7 @@ interface JointVelocityRequest {
    */
   'message_type'?: JointVelocityRequestMessageTypeEnum;
   /**
-   * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+   * 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
    */
@@ -3269,7 +3269,7 @@ interface MotionGroupSetup {
    */
   'payload'?: Payload;
   /**
-   * Collision layers to be respected by the motion planner when planning for a single motion group. Each setup represents one layer, e.g. the safety zones and shapes or a fine grained tool and workpiece model. Layers are checked individually along the trajectory and independently of other layers.  To respect the safety zones of the controller and check for collision: 1. Fetch the safety zones, link and tool shapes from the controller. 2. Add the fetched zones, links and tools to a layer. 3. Create other layers from your own 3D data as needed. 4. Plan trajectory. 5. The response highlights the layer in which a collision was detected by key.
+   * Collision layers to be respected by the motion planner when planning for a single motion group. Each setup represents one layer, e.g., the safety zones and shapes or a fine grained tool and workpiece model. Layers are checked individually along the trajectory and independently of other layers.  To respect the safety zones of the controller and check for collision: 1. Fetch the safety zones, link and tool shapes from the controller. 2. Add the fetched zones, links and tools to a layer. 3. Create other layers from your own 3D data as needed. 4. Plan trajectory. 5. The response highlights the layer in which a collision was detected by key.
    * @type {{ [key: string]: CollisionSetup; }}
    * @memberof MotionGroupSetup
    */
@@ -3308,7 +3308,7 @@ interface MotionGroupState {
    */
   'controller': string;
   /**
-   * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+   * 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
    */
@@ -3320,13 +3320,13 @@ interface MotionGroupState {
    */
   'joint_limit_reached': MotionGroupStateJointLimitReached;
   /**
-   * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+   * 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'?: Array<number>;
   /**
-   * This structure describes a set of joint values (e.g. positions, currents, torques) of a motion group.  Float precision is the default.
+   * 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
    */
@@ -3368,7 +3368,7 @@ interface MotionGroupState {
    */
   'standstill': boolean;
   /**
-   * Data that was commanded to the motion group. Includes additional data on NOVA\'s execution components for executing trajectories and jogging. This is a convenience field to indicate the last command sent to the motion group. It is not available in all cases, e.g. if the motion group is not moved by NOVA.
+   * Data that was commanded to the motion group. Includes additional data on NOVA\'s execution components for executing trajectories and jogging. This is a convenience field to indicate the last command sent to the motion group. It is not available in all cases, e.g., if the motion group is not moved by NOVA.
    * @type {Execute}
    * @memberof MotionGroupState
    */
@@ -3887,7 +3887,7 @@ 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
+   * 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
    */
@@ -4136,13 +4136,13 @@ interface ProfinetIO {
    */
   'type': ProfinetIOTypeEnum;
   /**
-   * The direction of the input/output variable, indicating whether it is an input or output for the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * The direction of the input/output variable, indicating whether it is an input or output for the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @type {ProfinetIODirection}
    * @memberof ProfinetIO
    */
   'direction': ProfinetIODirection;
   /**
-   * The byte address of the input/output variable in the PROFINET device, e.g. NOVA\'s PROFINET service. The byte address is used to locate the specific input/output variable within the device\'s memory or data structure.
+   * The byte address of the input/output variable in the PROFINET device, e.g., NOVA\'s PROFINET service. The byte address is used to locate the specific input/output variable within the device\'s memory or data structure.
    * @type {number}
    * @memberof ProfinetIO
    */
@@ -4154,7 +4154,7 @@ interface ProfinetIO {
    */
   'bit_address'?: number;
   /**
-   * The unique identifier for the input/output value. This identifier is used to reference the specific input/output variable in the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * The unique identifier for the input/output value. This identifier is used to reference the specific input/output variable in the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @type {string}
    * @memberof ProfinetIO
    */
@@ -4179,13 +4179,13 @@ interface ProfinetIOData {
    */
   'type': ProfinetIOTypeEnum;
   /**
-   * The direction of the input/output variable, indicating whether it is an input or output for the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * The direction of the input/output variable, indicating whether it is an input or output for the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @type {ProfinetIODirection}
    * @memberof ProfinetIOData
    */
   'direction': ProfinetIODirection;
   /**
-   * The byte address of the input/output variable in the PROFINET device, e.g. NOVA\'s PROFINET service. The byte address is used to locate the specific input/output variable within the device\'s memory or data structure.
+   * The byte address of the input/output variable in the PROFINET device, e.g., NOVA\'s PROFINET service. The byte address is used to locate the specific input/output variable within the device\'s memory or data structure.
    * @type {number}
    * @memberof ProfinetIOData
    */
@@ -4198,7 +4198,7 @@ interface ProfinetIOData {
   'bit_address'?: number;
 }
 /**
- * The direction of the input/output variable, indicating whether it is an input or output for the PROFINET device, e.g. NOVA\'s PROFINET service.
+ * The direction of the input/output variable, indicating whether it is an input or output for the PROFINET device, e.g., NOVA\'s PROFINET service.
  * @export
  * @enum {string}
  */
@@ -4252,7 +4252,7 @@ interface ProfinetInputOutputConfig {
   'output_offset': number;
 }
 /**
- * An array of PROFINET slots.  PROFINET models each device’s input/output hardware as a hierarchy of slots (modules) and subslots (submodules). A slot can represent a physical or virtual input/output card and each subslot one of its individual channels or functions. Every slot and subslot has unique identifiers that the controller uses to map cyclic input/output data and parameter records to its process image. This slot/subslot separation enables e.g. addressing each input/output stream when establishing input/output application relations (I/O-AR).
+ * An array of PROFINET slots.  PROFINET models each device’s input/output hardware as a hierarchy of slots (modules) and subslots (submodules). A slot can represent a physical or virtual input/output card and each subslot one of its individual channels or functions. Every slot and subslot has unique identifiers that the controller uses to map cyclic input/output data and parameter records to its process image. This slot/subslot separation enables e.g., addressing each input/output stream when establishing input/output application relations (I/O-AR).
  * @export
  * @interface ProfinetSlotDescription
  */
@@ -4956,7 +4956,7 @@ interface 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
+   * 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
    */
@@ -5227,7 +5227,7 @@ interface TrajectoryDetails {
    */
   'trajectory': string;
   /**
-   * 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
+   * 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
    */
@@ -5526,7 +5526,7 @@ interface VirtualController {
    */
   'json'?: string;
   /**
-   * Initial joint position of the first motion group from the virtual robot controller. Provide the joint position as a JSON array containing 7 float values, each representing a joint position in radians, e.g. \"[0, 0, 0, 0, 0, 0, 0]\". If the robot has fewer than 7 joints, use \"0\" for each remaining position to ensure the array has exactly 7 values.
+   * Initial joint position of the first motion group from the virtual robot controller. Provide the joint position as a JSON array containing 7 float values, each representing a joint position in radians, e.g., \"[0, 0, 0, 0, 0, 0, 0]\". If the robot has fewer than 7 joints, use \"0\" for each remaining position to ensure the array has exactly 7 values.
    * @type {string}
    * @memberof VirtualController
    */
@@ -5722,7 +5722,7 @@ type YaskawaControllerKindEnum = typeof YaskawaControllerKindEnum[keyof typeof Y
  */
 declare const ApplicationApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
+   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
    * @summary Add Application
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {App} app
@@ -5751,7 +5751,7 @@ declare const ApplicationApiAxiosParamCreator: (configuration?: Configuration) =
    */
   deleteApp: (cell: string, app: string, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the \'Update Configuration\' endpoint.
+   * Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp).
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} app
@@ -5760,7 +5760,7 @@ declare const ApplicationApiAxiosParamCreator: (configuration?: Configuration) =
    */
   getApp: (cell: string, app: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * List all GUI applications that have been added to a cell. with the \'Add Application\' endpoint. If the cell does not contain GUI applications, the list is returned empty.
+   * List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty.
    * @summary List Applications
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -5785,7 +5785,7 @@ declare const ApplicationApiAxiosParamCreator: (configuration?: Configuration) =
  */
 declare const ApplicationApiFp: (configuration?: Configuration) => {
   /**
-   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
+   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
    * @summary Add Application
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {App} app
@@ -5814,7 +5814,7 @@ declare const ApplicationApiFp: (configuration?: Configuration) => {
    */
   deleteApp(cell: string, app: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the \'Update Configuration\' endpoint.
+   * Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp).
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} app
@@ -5823,7 +5823,7 @@ declare const ApplicationApiFp: (configuration?: Configuration) => {
    */
   getApp(cell: string, app: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<App>>;
   /**
-   * List all GUI applications that have been added to a cell. with the \'Add Application\' endpoint. If the cell does not contain GUI applications, the list is returned empty.
+   * List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty.
    * @summary List Applications
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -5848,7 +5848,7 @@ declare const ApplicationApiFp: (configuration?: Configuration) => {
  */
 declare const ApplicationApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
+   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
    * @summary Add Application
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {App} app
@@ -5877,7 +5877,7 @@ declare const ApplicationApiFactory: (configuration?: Configuration, basePath?:
    */
   deleteApp(cell: string, app: string, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the \'Update Configuration\' endpoint.
+   * Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp).
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} app
@@ -5886,7 +5886,7 @@ declare const ApplicationApiFactory: (configuration?: Configuration, basePath?:
    */
   getApp(cell: string, app: string, options?: RawAxiosRequestConfig): AxiosPromise<App>;
   /**
-   * List all GUI applications that have been added to a cell. with the \'Add Application\' endpoint. If the cell does not contain GUI applications, the list is returned empty.
+   * List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty.
    * @summary List Applications
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -5913,7 +5913,7 @@ declare const ApplicationApiFactory: (configuration?: Configuration, basePath?:
  */
 declare class ApplicationApi extends BaseAPI {
   /**
-   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  Prerequisites: A Docker hub account or similar container registry account, with valid credentials.  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](/docs/docs/development/) for more information.  <!-- theme: none --> > #### Predefined Environment Variables > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
+   * Install a basic, containerized web application to the cell to control robots with a customized frontend.  #### Prerequisites - A Docker hub account or similar container registry account, with valid credentials.  #### Workflow  After adding the application to the cell, open the application on the Wandelbots NOVA home screen.  Read [build your application](https://docs.wandelbots.io/latest/developing-introduction) for more information.  #### Predefined environment variables  <!-- theme: NOTE --> > **NOTE** > - `NOVA_API`: The API endpoint accessible from within the application container. > - `NATS_BROKER`: The NATS broker endpoint accessible from within the application container. > - `BASE_PATH`: The application\'s root path, accessible at http://$host/$BASE_PATH > - `CELL_NAME`: The name of the cell hosting the deployed application.
    * @summary Add Application
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {App} app
@@ -5945,7 +5945,7 @@ declare class ApplicationApi extends BaseAPI {
    */
   deleteApp(cell: string, app: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Get the configuration for an active GUI application in the cell. To update the configuration of a GUI application in the cell, use this configuration with the \'Update Configuration\' endpoint.
+   * Get the configuration for an active GUI application in the cell.  To update the configuration of a GUI application in the cell, use this configuration with [updateApp](updateApp).
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} app
@@ -5955,7 +5955,7 @@ declare class ApplicationApi extends BaseAPI {
    */
   getApp(cell: string, app: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<App, any>>;
   /**
-   * List all GUI applications that have been added to a cell. with the \'Add Application\' endpoint. If the cell does not contain GUI applications, the list is returned empty.
+   * List all GUI applications that have been added to a cell with [addApp](addApp).  If the cell does not contain GUI applications, the list is returned empty.
    * @summary List Applications
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -5992,7 +5992,7 @@ declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Configurati
    */
   addBusIOService: (cell: string, busIOType: BusIOType, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA\'s PROFINET service.  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 third party software, e.g. TIA portal).
+   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA\'s PROFINET service.  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 third party software, e.g., TIA portal).
    * @summary Add PROFINET Input/Output
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6011,7 +6011,7 @@ declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Configurati
    */
   clearBusIOService: (cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Removes an input/output variable configuration from the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * Removes an input/output variable configuration from the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @summary Remove PROFINET Input/Ouptut
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6053,7 +6053,7 @@ declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Configurati
    */
   getProfinetDescription: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get input/output variable configuration of the PROFINET device, e.g. NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal.
+   * Get input/output variable configuration of the PROFINET device, e.g., NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal.
    * @summary PROFINET Inputs/Outputs to File
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [inputOffset]
@@ -6063,7 +6063,7 @@ declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Configurati
    */
   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 input/output direction is given in perspective of the BUS service.
+   * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and 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.
@@ -6071,7 +6071,7 @@ declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Configurati
    */
   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 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.
+   * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and 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.
@@ -6088,7 +6088,7 @@ declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Configurati
    */
   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, 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.
+   * 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.  #### Export variables 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
@@ -6113,7 +6113,7 @@ declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
    */
   addBusIOService(cell: string, busIOType: BusIOType, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA\'s PROFINET service.  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 third party software, e.g. TIA portal).
+   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA\'s PROFINET service.  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 third party software, e.g., TIA portal).
    * @summary Add PROFINET Input/Output
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6132,7 +6132,7 @@ declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
    */
   clearBusIOService(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Removes an input/output variable configuration from the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * Removes an input/output variable configuration from the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @summary Remove PROFINET Input/Ouptut
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6174,7 +6174,7 @@ declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
    */
   getProfinetDescription(cell: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ProfinetDescription>>;
   /**
-   * Get input/output variable configuration of the PROFINET device, e.g. NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal.
+   * Get input/output variable configuration of the PROFINET device, e.g., NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal.
    * @summary PROFINET Inputs/Outputs to File
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [inputOffset]
@@ -6184,7 +6184,7 @@ 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 input/output direction is given in perspective of the BUS service.
+   * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and 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.
@@ -6192,7 +6192,7 @@ 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 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.
+   * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and 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.
@@ -6209,7 +6209,7 @@ 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, 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.
+   * 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.  #### Export variables 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
@@ -6234,7 +6234,7 @@ declare const BUSInputsOutputsApiFactory: (configuration?: Configuration, basePa
    */
   addBusIOService(cell: string, busIOType: BusIOType, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA\'s PROFINET service.  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 third party software, e.g. TIA portal).
+   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA\'s PROFINET service.  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 third party software, e.g., TIA portal).
    * @summary Add PROFINET Input/Output
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6253,7 +6253,7 @@ declare const BUSInputsOutputsApiFactory: (configuration?: Configuration, basePa
    */
   clearBusIOService(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Removes an input/output variable configuration from the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * Removes an input/output variable configuration from the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @summary Remove PROFINET Input/Ouptut
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6295,7 +6295,7 @@ declare const BUSInputsOutputsApiFactory: (configuration?: Configuration, basePa
    */
   getProfinetDescription(cell: string, options?: RawAxiosRequestConfig): AxiosPromise<ProfinetDescription>;
   /**
-   * Get input/output variable configuration of the PROFINET device, e.g. NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal.
+   * Get input/output variable configuration of the PROFINET device, e.g., NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal.
    * @summary PROFINET Inputs/Outputs to File
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [inputOffset]
@@ -6305,7 +6305,7 @@ declare const BUSInputsOutputsApiFactory: (configuration?: Configuration, basePa
    */
   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 input/output direction is given in perspective of the BUS service.
+   * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and 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.
@@ -6313,7 +6313,7 @@ declare const BUSInputsOutputsApiFactory: (configuration?: Configuration, basePa
    */
   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 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.
+   * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and 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.
@@ -6330,7 +6330,7 @@ declare const BUSInputsOutputsApiFactory: (configuration?: Configuration, basePa
    */
   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, 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.
+   * 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.  #### Export variables 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
@@ -6358,7 +6358,7 @@ declare class BUSInputsOutputsApi extends BaseAPI {
    */
   addBusIOService(cell: string, busIOType: BusIOType, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g. NOVA\'s PROFINET service.  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 third party software, e.g. TIA portal).
+   * Adds an input/output variable to or updates an input/output variable on the PROFINET device, e.g., NOVA\'s PROFINET service.  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 third party software, e.g., TIA portal).
    * @summary Add PROFINET Input/Output
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6379,7 +6379,7 @@ declare class BUSInputsOutputsApi extends BaseAPI {
    */
   clearBusIOService(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Removes an input/output variable configuration from the PROFINET device, e.g. NOVA\'s PROFINET service.
+   * Removes an input/output variable configuration from the PROFINET device, e.g., NOVA\'s PROFINET service.
    * @summary Remove PROFINET Input/Ouptut
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} io Unique identifier to address an Input/Output in the cell.
@@ -6426,7 +6426,7 @@ declare class BUSInputsOutputsApi extends BaseAPI {
    */
   getProfinetDescription(cell: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<ProfinetDescription, any>>;
   /**
-   * Get input/output variable configuration of the PROFINET device, e.g. NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g. TIA portal.
+   * Get input/output variable configuration of the PROFINET device, e.g., NOVA\'s PROFINET service as file.  You can specify byte offsets for the input and output variable addresses to get an XML tagmap that is ready to paste to the third party software, e.g., TIA portal.
    * @summary PROFINET Inputs/Outputs to File
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [inputOffset]
@@ -6437,7 +6437,7 @@ declare class BUSInputsOutputsApi extends BaseAPI {
    */
   getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): Promise<axios0.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 input/output direction is given in perspective of the BUS service.
+   * List all input/output descriptions for configured BUS services.  The input/output descriptions contain information like name, type and 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.
@@ -6446,7 +6446,7 @@ declare class BUSInputsOutputsApi extends BaseAPI {
    */
   listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): Promise<axios0.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 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.
+   * List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information like name, type and 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.
@@ -6465,7 +6465,7 @@ declare class BUSInputsOutputsApi extends BaseAPI {
    */
   setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<axios0.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, 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.
+   * 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.  #### Export variables 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
@@ -6490,7 +6490,7 @@ declare const CellApiAxiosParamCreator: (configuration?: Configuration) => {
    */
   deleteCell: (cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
    * @summary Add Cell
    * @param {Cell} cell
    * @param {number} [completionTimeout]
@@ -6499,7 +6499,7 @@ declare const CellApiAxiosParamCreator: (configuration?: Configuration) => {
    */
   deployCell: (cell: Cell, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * List all cell resources.
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -6556,7 +6556,7 @@ declare const CellApiFp: (configuration?: Configuration) => {
    */
   deleteCell(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
    * @summary Add Cell
    * @param {Cell} cell
    * @param {number} [completionTimeout]
@@ -6565,7 +6565,7 @@ declare const CellApiFp: (configuration?: Configuration) => {
    */
   deployCell(cell: Cell, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * List all cell resources.
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -6622,7 +6622,7 @@ declare const CellApiFactory: (configuration?: Configuration, basePath?: string,
    */
   deleteCell(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
    * @summary Add Cell
    * @param {Cell} cell
    * @param {number} [completionTimeout]
@@ -6631,7 +6631,7 @@ declare const CellApiFactory: (configuration?: Configuration, basePath?: string,
    */
   deployCell(cell: Cell, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * List all cell resources.
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -6691,7 +6691,7 @@ declare class CellApi extends BaseAPI {
    */
   deleteCell(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](docs/wandelbots-nova-api/#create-a-cell) for more information.
+   * Deploy an entire cell with all its resources.  A cell can be used to deploy a robot controller, one or more robots, as well as custom applications.  Refer to the [Wandelbots NOVA documentation](https://docs.wandelbots.io/latest/setup-cell) for more information.
    * @summary Add Cell
    * @param {Cell} cell
    * @param {number} [completionTimeout]
@@ -6701,7 +6701,7 @@ declare class CellApi extends BaseAPI {
    */
   deployCell(cell: Cell, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * List all cell resources.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * List all cell resources.
    * @summary Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {*} [options] Override http request option.
@@ -6754,7 +6754,7 @@ declare class CellApi extends BaseAPI {
  */
 declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * Add a robot controller to the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Add a robot controller to the cell.
    * @summary Add Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {RobotController} robotController
@@ -6764,7 +6764,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   addRobotController: (cell: string, robotController: RobotController, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with the \'Add Robot Controller\' endpoint.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with [addRobotController](addRobotController).
    * @summary Clear Robot Controllers
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [completionTimeout]
@@ -6773,7 +6773,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   clearRobotControllers: (cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Delete a robot controller from the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete a robot controller from the cell.
    * @summary Delete Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6792,7 +6792,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   getControllerDescription: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Request a coordinate system specification for a given identifier. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Request a coordinate system specification for a given identifier. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary 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.
@@ -6821,7 +6821,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   getRobotController: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.
    * @summary Virtual Controller Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6830,7 +6830,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   getVirtualControllerConfiguration: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Lists all specifications of coordinate systems from robot controllers. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Lists all specifications of coordinate systems from robot controllers. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary List 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.
@@ -6848,7 +6848,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   listRobotControllers: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Switch between monitor and control usage as default for a robot controller. Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network monitoring mode is always possible. To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state \'normal\' or \'reduced\'. If the robot controller is in `manual` operating mode, you have manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
+   * Switch between monitor and control usage as default for a robot controller.  Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network, monitoring mode is always possible.  To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state `normal` or `reduced`. If the robot controller is in `manual` operating mode, you have to manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
    * @summary Set Default Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6858,7 +6858,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   setDefaultMode: (cell: string, controller: string, mode: SettableRobotSystemMode, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER**  > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that  > - The robot is in a safe state,  > - The right payload is set (e.g by using the (getActivePayload)[getActivePayload] endpoint),  > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified response_rate. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular Collobarative Robots (\"Cobots\"). Use the (listController)[listController] endpoint to check if the robot controller supports free drive mode.
+   * <!-- theme: success -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER** > > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that > > - The robot is in a safe state, > - The right payload is set, > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified `response_rate`. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular cobots. Use [listRobotControllers](listRobotControllers) to check if the robot controller supports free drive mode.
    * @summary Stream Free Drive
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6868,7 +6868,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   streamFreeDrive: (cell: string, controller: string, responseRate?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6879,7 +6879,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
    */
   streamRobotControllerState: (cell: string, controller: string, responseRate?: number, addControllerTimeout?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.
    * @summary Update Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6896,7 +6896,7 @@ declare const ControllerApiAxiosParamCreator: (configuration?: Configuration) =>
  */
 declare const ControllerApiFp: (configuration?: Configuration) => {
   /**
-   * Add a robot controller to the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Add a robot controller to the cell.
    * @summary Add Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {RobotController} robotController
@@ -6906,7 +6906,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   addRobotController(cell: string, robotController: RobotController, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with the \'Add Robot Controller\' endpoint.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with [addRobotController](addRobotController).
    * @summary Clear Robot Controllers
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [completionTimeout]
@@ -6915,7 +6915,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   clearRobotControllers(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Delete a robot controller from the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete a robot controller from the cell.
    * @summary Delete Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6934,7 +6934,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   getControllerDescription(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<ControllerDescription>>;
   /**
-   * Request a coordinate system specification for a given identifier. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Request a coordinate system specification for a given identifier. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary 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.
@@ -6963,7 +6963,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   getRobotController(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<RobotController>>;
   /**
-   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.
    * @summary Virtual Controller Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -6972,7 +6972,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   getVirtualControllerConfiguration(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<VirtualRobotConfiguration>>;
   /**
-   * Lists all specifications of coordinate systems from robot controllers. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Lists all specifications of coordinate systems from robot controllers. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary List 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.
@@ -6990,7 +6990,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   listRobotControllers(cell: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<string>>>;
   /**
-   * Switch between monitor and control usage as default for a robot controller. Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network monitoring mode is always possible. To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state \'normal\' or \'reduced\'. If the robot controller is in `manual` operating mode, you have manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
+   * Switch between monitor and control usage as default for a robot controller.  Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network, monitoring mode is always possible.  To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state `normal` or `reduced`. If the robot controller is in `manual` operating mode, you have to manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
    * @summary Set Default Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7000,7 +7000,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   setDefaultMode(cell: string, controller: string, mode: SettableRobotSystemMode, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER**  > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that  > - The robot is in a safe state,  > - The right payload is set (e.g by using the (getActivePayload)[getActivePayload] endpoint),  > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified response_rate. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular Collobarative Robots (\"Cobots\"). Use the (listController)[listController] endpoint to check if the robot controller supports free drive mode.
+   * <!-- theme: success -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER** > > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that > > - The robot is in a safe state, > - The right payload is set, > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified `response_rate`. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular cobots. Use [listRobotControllers](listRobotControllers) to check if the robot controller supports free drive mode.
    * @summary Stream Free Drive
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7010,7 +7010,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   streamFreeDrive(cell: string, controller: string, responseRate?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<RobotControllerState>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7021,7 +7021,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
    */
   streamRobotControllerState(cell: string, controller: string, responseRate?: number, addControllerTimeout?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<RobotControllerState>>;
   /**
-   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.
    * @summary Update Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7038,7 +7038,7 @@ declare const ControllerApiFp: (configuration?: Configuration) => {
  */
 declare const ControllerApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * Add a robot controller to the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Add a robot controller to the cell.
    * @summary Add Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {RobotController} robotController
@@ -7048,7 +7048,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   addRobotController(cell: string, robotController: RobotController, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with the \'Add Robot Controller\' endpoint.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with [addRobotController](addRobotController).
    * @summary Clear Robot Controllers
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [completionTimeout]
@@ -7057,7 +7057,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   clearRobotControllers(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Delete a robot controller from the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete a robot controller from the cell.
    * @summary Delete Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7076,7 +7076,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   getControllerDescription(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<ControllerDescription>;
   /**
-   * Request a coordinate system specification for a given identifier. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Request a coordinate system specification for a given identifier. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary 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.
@@ -7105,7 +7105,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   getRobotController(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<RobotController>;
   /**
-   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.
    * @summary Virtual Controller Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7114,7 +7114,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   getVirtualControllerConfiguration(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<VirtualRobotConfiguration>;
   /**
-   * Lists all specifications of coordinate systems from robot controllers. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Lists all specifications of coordinate systems from robot controllers. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary List 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.
@@ -7132,7 +7132,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   listRobotControllers(cell: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<string>>;
   /**
-   * Switch between monitor and control usage as default for a robot controller. Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network monitoring mode is always possible. To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state \'normal\' or \'reduced\'. If the robot controller is in `manual` operating mode, you have manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
+   * Switch between monitor and control usage as default for a robot controller.  Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network, monitoring mode is always possible.  To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state `normal` or `reduced`. If the robot controller is in `manual` operating mode, you have to manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
    * @summary Set Default Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7142,7 +7142,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   setDefaultMode(cell: string, controller: string, mode: SettableRobotSystemMode, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER**  > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that  > - The robot is in a safe state,  > - The right payload is set (e.g by using the (getActivePayload)[getActivePayload] endpoint),  > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified response_rate. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular Collobarative Robots (\"Cobots\"). Use the (listController)[listController] endpoint to check if the robot controller supports free drive mode.
+   * <!-- theme: success -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER** > > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that > > - The robot is in a safe state, > - The right payload is set, > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified `response_rate`. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular cobots. Use [listRobotControllers](listRobotControllers) to check if the robot controller supports free drive mode.
    * @summary Stream Free Drive
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7152,7 +7152,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   streamFreeDrive(cell: string, controller: string, responseRate?: number, options?: RawAxiosRequestConfig): AxiosPromise<RobotControllerState>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7163,7 +7163,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
    */
   streamRobotControllerState(cell: string, controller: string, responseRate?: number, addControllerTimeout?: number, options?: RawAxiosRequestConfig): AxiosPromise<RobotControllerState>;
   /**
-   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.
    * @summary Update Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7182,7 +7182,7 @@ declare const ControllerApiFactory: (configuration?: Configuration, basePath?: s
  */
 declare class ControllerApi extends BaseAPI {
   /**
-   * Add a robot controller to the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Add a robot controller to the cell.
    * @summary Add Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {RobotController} robotController
@@ -7193,7 +7193,7 @@ declare class ControllerApi extends BaseAPI {
    */
   addRobotController(cell: string, robotController: RobotController, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with the \'Add Robot Controller\' endpoint.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete all robot controllers from the cell.  To replace all robot controllers in a cell, use this endpoint in combination with [addRobotController](addRobotController).
    * @summary Clear Robot Controllers
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {number} [completionTimeout]
@@ -7203,7 +7203,7 @@ declare class ControllerApi extends BaseAPI {
    */
   clearRobotControllers(cell: string, completionTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Delete a robot controller from the cell.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Delete a robot controller from the cell.
    * @summary Delete Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7224,7 +7224,7 @@ declare class ControllerApi extends BaseAPI {
    */
   getControllerDescription(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<ControllerDescription, any>>;
   /**
-   * Request a coordinate system specification for a given identifier. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Request a coordinate system specification for a given identifier. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary 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.
@@ -7256,7 +7256,7 @@ declare class ControllerApi extends BaseAPI {
    */
   getRobotController(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<RobotController, any>>;
   /**
-   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.  > **NOTE** > > The output generated by this endpoint can be too large for the site to handle, and may produce an error or incorrect output. > Use `curl` in combination with `> output.json` to capture the output, or use an API client like Postman.
+   * Receive data to configure a virtual robot controller based on another controller. This can be used to create a virtual clone of a specific physical robot.  When adding a virtual controller, use the Virtual configuration variant of [addRobotController](addRobotController) and pass the content string from this endpoint as the `json` field. Omit the `type` field that selects a preset configuration which is not required when providing a complete configuration.
    * @summary Virtual Controller Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7266,7 +7266,7 @@ declare class ControllerApi extends BaseAPI {
    */
   getVirtualControllerConfiguration(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<VirtualRobotConfiguration, any>>;
   /**
-   * Lists all specifications of coordinate systems from robot controllers. Use parameter orientation_type to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter orientation_type is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with \"On\" + the unique identifier of the robot controller.
+   * Lists all specifications of coordinate systems from robot controllers. Use parameter `orientation_type` to get the orientation part of the transformation offset of the coordinate system returned in the requested orientation notation. If parameter `orientation_type` is not set, the orientation part of the transformation offset of the coordinate system is returned in rotation vector notation.  The coordinate systems from the robot controller are loaded when the motion group associated with the coordinate system is activated. With deactivation of the motion group, the associated coordinate systems are removed from NOVA. The unique identifier of the coordinate systems from the robot controllers are suffixed with `On` + the unique identifier of the robot controller.
    * @summary List 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.
@@ -7286,7 +7286,7 @@ declare class ControllerApi extends BaseAPI {
    */
   listRobotControllers(cell: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<string[], any>>;
   /**
-   * Switch between monitor and control usage as default for a robot controller. Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network monitoring mode is always possible. To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state \'normal\' or \'reduced\'. If the robot controller is in `manual` operating mode, you have manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
+   * Switch between monitor and control usage as default for a robot controller.  Monitoring mode is used to read information from the robot controller and control mode is used to command the robot system. As long as the robot controller is connected via network, monitoring mode is always possible.  To switch to control mode the robot controller must be in `automatic` or `manual` operating mode and safety state `normal` or `reduced`. If the robot controller is in `manual` operating mode, you have to manually confirm the control usage activation on the robot control panel. This manual confirmation can\'t be replaced with this API. Without manual confirmation the robot controller will stay in monitor mode.  The robot system will try to activate the required operation mode for the requested usage unless no active call requires a different mode.  > **NOTE** > > `setDefaultMode` enables the robot controller to stay in control mode to keep the motors activated. > This allows for faster execution of sequential movements as no mode switches are required.  > **NOTE** > > Some robot controllers prevent the external activation of automatic operating mode. In this case, changing the operating mode manually at the robot controller is mandatory.  > **NOTE** > > The current operation mode and safety state can be requested via [getCurrentRobotControllerState](getCurrentRobotControllerState).  If a mode change is not possible, the response lists reasons for the failed change.
    * @summary Set Default Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7297,7 +7297,7 @@ declare class ControllerApi extends BaseAPI {
    */
   setDefaultMode(cell: string, controller: string, mode: SettableRobotSystemMode, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER**  > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that  > - The robot is in a safe state,  > - The right payload is set (e.g by using the (getActivePayload)[getActivePayload] endpoint),  > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified response_rate. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular Collobarative Robots (\"Cobots\"). Use the (listController)[listController] endpoint to check if the robot controller supports free drive mode.
+   * <!-- theme: success -->  > Websocket endpoint  Sets the robot controller into freedrive mode and stays in freedrive until the websocket connection is closed by the client. In freedrive mode, it is possible to move the attached motion groups by hand. This is a blocking call. As long as the websocket connection is open, no other endpoint can control or move the robot.  <!-- theme: danger -->  > **DANGER** > > Danger caused by robot. Improper assessment by the integrator of the application-specific hazards can result in people being > crushed, drawn in or caught due to the robot\'s complex movement sequences. Before opening the websocket, ensure that > > - The robot is in a safe state, > - The right payload is set, > - No humans or object are within the robot\'s reach or within the cell.  As long as the websocket connection is open you will get the current state of the robot system in the response in the specified `response_rate`. If the activation failed, the returned status will return possible reasons for the failure.  Free drive mode is only available for robot controllers that support it, in particular cobots. Use [listRobotControllers](listRobotControllers) to check if the robot controller supports free drive mode.
    * @summary Stream Free Drive
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7308,7 +7308,7 @@ declare class ControllerApi extends BaseAPI {
    */
   streamFreeDrive(cell: string, controller: string, responseRate?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<RobotControllerState, any>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the state of a robot controller.  The stream can be opened before the controller is registered. To register a controller, call [addRobotController](addRobotController).  While connecting, the stream sends initialization updates. Once the controller reaches `MODE_MONITOR`, it sends controller state updates.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7320,7 +7320,7 @@ declare class ControllerApi extends BaseAPI {
    */
   streamRobotControllerState(cell: string, controller: string, responseRate?: number, addControllerTimeout?: number, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<RobotControllerState, any>>;
   /**
-   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.  <!-- theme: warning --> > **WARNING** > > Using it in conjunction with the settings app may lead to unpredictable behavior.
+   * Update the configuration of a robot controller.  Reconfigure certain options of a robot controller, or deploy a specific container image of a robot controller.
    * @summary Update Robot Controller
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7338,7 +7338,7 @@ declare class ControllerApi extends BaseAPI {
  */
 declare const ControllerInputsOutputsApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information such as the name of the input/output, the input/output type and the input/output unit. The set of available inputs/outputs is defined by the robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, the full list of available inputs/outputs is retrieved by this endpoint. Except when a filter (direction, value_type, group) is applied. Then only the inputs/outputs matching the filter are returned.
+   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the robot controller\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7361,7 +7361,7 @@ declare const ControllerInputsOutputsApiAxiosParamCreator: (configuration?: Conf
    */
   listIOValues: (cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This might take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
+   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This can take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
    * @summary Set Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7371,7 +7371,7 @@ declare const ControllerInputsOutputsApiAxiosParamCreator: (configuration?: Conf
    */
   setOutputValues: (cell: string, controller: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > Do not request too many values simultaneously as the request is then likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. Consider that this might lead to a high amount of data transmitted.
+   * <!-- theme: success -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > If you request many values simultaneously, the request is likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. This can lead to a high amount of data transmitted.
    * @summary Stream Input/Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7381,7 +7381,7 @@ declare const ControllerInputsOutputsApiAxiosParamCreator: (configuration?: Conf
    */
   streamIOValues: (cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Wait until an input/output reaches a certain value. This call returns as soon as the condition is met or the request fails.  The comparison_type value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the value_type of the input/output, see (listIODescriptions)[listIODescriptions] for more information. Examples: If you want to wait until an analog input (\"AI_1\") is less than 10, you would set io to \"AI_1\" comparison_type to COMPARISON_LESS and only value to 10. If you want to wait until an analog input (\"AI_2\") is greater than 5.0, you would set io to \"AI_2\" comparison_type to COMPARISON_GREATER and only value to 5.0. If you want to wait until a digital input (\"DI_3\") is true, you would set io to \"DI_3\" comparison_type to COMPARISON_EQUAL and only value to true.
+   * Wait until an input/output reaches a certain value.  This call returns as soon as the condition is met or the request fails.  The `comparison_type` value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the `value_type` of the input/output. See [listIODescriptions](listIODescriptions) for more information.  **Examples**  1. Wait until analog input `AI_1` < 10:     ```     io: \"AI_1\"     comparison_type: \"COMPARISON_LESS\"     value: 10     ```  2. Wait until analog input `AI_2` > 5.0:     ```     io: \"AI_2\"     comparison_type: \"COMPARISON_GREATER\"     value: 5.0     ```  3. Wait until digital input `DI_3` is true:     ```     io: \"DI_3\"     comparison_type: \"COMPARISON_EQUAL\"     value: true     ```
    * @summary Wait For
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7397,7 +7397,7 @@ declare const ControllerInputsOutputsApiAxiosParamCreator: (configuration?: Conf
  */
 declare const ControllerInputsOutputsApiFp: (configuration?: Configuration) => {
   /**
-   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information such as the name of the input/output, the input/output type and the input/output unit. The set of available inputs/outputs is defined by the robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, the full list of available inputs/outputs is retrieved by this endpoint. Except when a filter (direction, value_type, group) is applied. Then only the inputs/outputs matching the filter are returned.
+   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the robot controller\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7420,7 +7420,7 @@ declare const ControllerInputsOutputsApiFp: (configuration?: Configuration) => {
    */
   listIOValues(cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<IOValue>>>;
   /**
-   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This might take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
+   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This can take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
    * @summary Set Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7430,7 +7430,7 @@ declare const ControllerInputsOutputsApiFp: (configuration?: Configuration) => {
    */
   setOutputValues(cell: string, controller: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > Do not request too many values simultaneously as the request is then likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. Consider that this might lead to a high amount of data transmitted.
+   * <!-- theme: success -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > If you request many values simultaneously, the request is likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. This can lead to a high amount of data transmitted.
    * @summary Stream Input/Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7440,7 +7440,7 @@ declare const ControllerInputsOutputsApiFp: (configuration?: Configuration) => {
    */
   streamIOValues(cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<StreamIOValuesResponse>>;
   /**
-   * Wait until an input/output reaches a certain value. This call returns as soon as the condition is met or the request fails.  The comparison_type value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the value_type of the input/output, see (listIODescriptions)[listIODescriptions] for more information. Examples: If you want to wait until an analog input (\"AI_1\") is less than 10, you would set io to \"AI_1\" comparison_type to COMPARISON_LESS and only value to 10. If you want to wait until an analog input (\"AI_2\") is greater than 5.0, you would set io to \"AI_2\" comparison_type to COMPARISON_GREATER and only value to 5.0. If you want to wait until a digital input (\"DI_3\") is true, you would set io to \"DI_3\" comparison_type to COMPARISON_EQUAL and only value to true.
+   * Wait until an input/output reaches a certain value.  This call returns as soon as the condition is met or the request fails.  The `comparison_type` value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the `value_type` of the input/output. See [listIODescriptions](listIODescriptions) for more information.  **Examples**  1. Wait until analog input `AI_1` < 10:     ```     io: \"AI_1\"     comparison_type: \"COMPARISON_LESS\"     value: 10     ```  2. Wait until analog input `AI_2` > 5.0:     ```     io: \"AI_2\"     comparison_type: \"COMPARISON_GREATER\"     value: 5.0     ```  3. Wait until digital input `DI_3` is true:     ```     io: \"DI_3\"     comparison_type: \"COMPARISON_EQUAL\"     value: true     ```
    * @summary Wait For
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7456,7 +7456,7 @@ declare const ControllerInputsOutputsApiFp: (configuration?: Configuration) => {
  */
 declare const ControllerInputsOutputsApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information such as the name of the input/output, the input/output type and the input/output unit. The set of available inputs/outputs is defined by the robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, the full list of available inputs/outputs is retrieved by this endpoint. Except when a filter (direction, value_type, group) is applied. Then only the inputs/outputs matching the filter are returned.
+   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the robot controller\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7479,7 +7479,7 @@ declare const ControllerInputsOutputsApiFactory: (configuration?: Configuration,
    */
   listIOValues(cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig): AxiosPromise<Array<IOValue>>;
   /**
-   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This might take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
+   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This can take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
    * @summary Set Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7489,7 +7489,7 @@ declare const ControllerInputsOutputsApiFactory: (configuration?: Configuration,
    */
   setOutputValues(cell: string, controller: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > Do not request too many values simultaneously as the request is then likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. Consider that this might lead to a high amount of data transmitted.
+   * <!-- theme: success -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > If you request many values simultaneously, the request is likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. This can lead to a high amount of data transmitted.
    * @summary Stream Input/Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7499,7 +7499,7 @@ declare const ControllerInputsOutputsApiFactory: (configuration?: Configuration,
    */
   streamIOValues(cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig): AxiosPromise<StreamIOValuesResponse>;
   /**
-   * Wait until an input/output reaches a certain value. This call returns as soon as the condition is met or the request fails.  The comparison_type value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the value_type of the input/output, see (listIODescriptions)[listIODescriptions] for more information. Examples: If you want to wait until an analog input (\"AI_1\") is less than 10, you would set io to \"AI_1\" comparison_type to COMPARISON_LESS and only value to 10. If you want to wait until an analog input (\"AI_2\") is greater than 5.0, you would set io to \"AI_2\" comparison_type to COMPARISON_GREATER and only value to 5.0. If you want to wait until a digital input (\"DI_3\") is true, you would set io to \"DI_3\" comparison_type to COMPARISON_EQUAL and only value to true.
+   * Wait until an input/output reaches a certain value.  This call returns as soon as the condition is met or the request fails.  The `comparison_type` value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the `value_type` of the input/output. See [listIODescriptions](listIODescriptions) for more information.  **Examples**  1. Wait until analog input `AI_1` < 10:     ```     io: \"AI_1\"     comparison_type: \"COMPARISON_LESS\"     value: 10     ```  2. Wait until analog input `AI_2` > 5.0:     ```     io: \"AI_2\"     comparison_type: \"COMPARISON_GREATER\"     value: 5.0     ```  3. Wait until digital input `DI_3` is true:     ```     io: \"DI_3\"     comparison_type: \"COMPARISON_EQUAL\"     value: true     ```
    * @summary Wait For
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7517,7 +7517,7 @@ declare const ControllerInputsOutputsApiFactory: (configuration?: Configuration,
  */
 declare class ControllerInputsOutputsApi extends BaseAPI {
   /**
-   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information such as the name of the input/output, the input/output type and the input/output unit. The set of available inputs/outputs is defined by the robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, the full list of available inputs/outputs is retrieved by this endpoint. Except when a filter (direction, value_type, group) is applied. Then only the inputs/outputs matching the filter are returned.
+   * Lists the input/output descriptions of the robot controller.  The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the robot controller\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7542,7 +7542,7 @@ declare class ControllerInputsOutputsApi extends BaseAPI {
    */
   listIOValues(cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<IOValue[], any>>;
   /**
-   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This might take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
+   * Set the values of outputs.  All available output identifiers and possible value ranges can be requested via [listIODescriptions](listIODescriptions).  The call will return once the values have been set on and accepted by the robot. This can take up to 200 milliseconds.  > **NOTE** > > Do not call this endpoint while another request is still in progress. The second call will fail.
    * @summary Set Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7553,7 +7553,7 @@ declare class ControllerInputsOutputsApi extends BaseAPI {
    */
   setOutputValues(cell: string, controller: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > Do not request too many values simultaneously as the request is then likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. Consider that this might lead to a high amount of data transmitted.
+   * <!-- theme: success -->  > Websocket endpoint  Continuously receive updates of input/output values via websocket. Updates are sent in the update rate of the controller.  > **NOTE** > > If you request many values simultaneously, the request is likely to fail. The amount of values that can be streamed simultaneously depends on the specific robot controller.  > **NOTE** > > The inputs and outputs are sent in the update rate of the controller to prevent losing any values. This can lead to a high amount of data transmitted.
    * @summary Stream Input/Output Values
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7564,7 +7564,7 @@ declare class ControllerInputsOutputsApi extends BaseAPI {
    */
   streamIOValues(cell: string, controller: string, ios?: Array<string>, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<StreamIOValuesResponse, any>>;
   /**
-   * Wait until an input/output reaches a certain value. This call returns as soon as the condition is met or the request fails.  The comparison_type value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the value_type of the input/output, see (listIODescriptions)[listIODescriptions] for more information. Examples: If you want to wait until an analog input (\"AI_1\") is less than 10, you would set io to \"AI_1\" comparison_type to COMPARISON_LESS and only value to 10. If you want to wait until an analog input (\"AI_2\") is greater than 5.0, you would set io to \"AI_2\" comparison_type to COMPARISON_GREATER and only value to 5.0. If you want to wait until a digital input (\"DI_3\") is true, you would set io to \"DI_3\" comparison_type to COMPARISON_EQUAL and only value to true.
+   * Wait until an input/output reaches a certain value.  This call returns as soon as the condition is met or the request fails.  The `comparison_type` value is used to define how the current value of the input/output is compared with given value. Only set the value that corresponds to the `value_type` of the input/output. See [listIODescriptions](listIODescriptions) for more information.  **Examples**  1. Wait until analog input `AI_1` < 10:     ```     io: \"AI_1\"     comparison_type: \"COMPARISON_LESS\"     value: 10     ```  2. Wait until analog input `AI_2` > 5.0:     ```     io: \"AI_2\"     comparison_type: \"COMPARISON_GREATER\"     value: 5.0     ```  3. Wait until digital input `DI_3` is true:     ```     io: \"DI_3\"     comparison_type: \"COMPARISON_EQUAL\"     value: true     ```
    * @summary Wait For
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7581,7 +7581,7 @@ declare class ControllerInputsOutputsApi extends BaseAPI {
  */
 declare const JoggingApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP (Tool Center Point). The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send InitializeJoggingRequest to configure the jogging.  Sets robot controller mode to control mode. Sets rate and coordinate system for the jogging response.  #### 2. Send JointVelocityRequest or TcpVelocityRequest to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with JointVelocityRequest or TcpVelocityRequest. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - InitializeJoggingResponse is sent to signal the success or failure of the InitializeJoggingRequest. - Jogging responses are streamed continuously after an InitializeJoggingRequest is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - JoggingErrorResponse with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the JoggingResponse, verify that the robot control is in the desired state, e.g. standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP. The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send `InitializeJoggingRequest` to configure the jogging.  - Sets the robot controller mode to control mode. - Sets rate and coordinate system for the jogging response.  #### 2. Send `JointVelocityRequest` or `TcpVelocityRequest` to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with `JointVelocityRequest` or `TcpVelocityRequest`. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - `InitializeJoggingResponse` is sent to signal the success or failure of the `InitializeJoggingRequest`. - Jogging responses are streamed continuously after an `InitializeJoggingRequest` is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - `JoggingErrorResponse` with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the `JoggingResponse`, verify that the robot control is in the desired state, e.g., standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
    * @summary Execute Jogging
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7597,7 +7597,7 @@ declare const JoggingApiAxiosParamCreator: (configuration?: Configuration) => {
  */
 declare const JoggingApiFp: (configuration?: Configuration) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP (Tool Center Point). The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send InitializeJoggingRequest to configure the jogging.  Sets robot controller mode to control mode. Sets rate and coordinate system for the jogging response.  #### 2. Send JointVelocityRequest or TcpVelocityRequest to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with JointVelocityRequest or TcpVelocityRequest. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - InitializeJoggingResponse is sent to signal the success or failure of the InitializeJoggingRequest. - Jogging responses are streamed continuously after an InitializeJoggingRequest is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - JoggingErrorResponse with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the JoggingResponse, verify that the robot control is in the desired state, e.g. standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP. The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send `InitializeJoggingRequest` to configure the jogging.  - Sets the robot controller mode to control mode. - Sets rate and coordinate system for the jogging response.  #### 2. Send `JointVelocityRequest` or `TcpVelocityRequest` to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with `JointVelocityRequest` or `TcpVelocityRequest`. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - `InitializeJoggingResponse` is sent to signal the success or failure of the `InitializeJoggingRequest`. - Jogging responses are streamed continuously after an `InitializeJoggingRequest` is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - `JoggingErrorResponse` with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the `JoggingResponse`, verify that the robot control is in the desired state, e.g., standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
    * @summary Execute Jogging
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7613,7 +7613,7 @@ declare const JoggingApiFp: (configuration?: Configuration) => {
  */
 declare const JoggingApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP (Tool Center Point). The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send InitializeJoggingRequest to configure the jogging.  Sets robot controller mode to control mode. Sets rate and coordinate system for the jogging response.  #### 2. Send JointVelocityRequest or TcpVelocityRequest to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with JointVelocityRequest or TcpVelocityRequest. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - InitializeJoggingResponse is sent to signal the success or failure of the InitializeJoggingRequest. - Jogging responses are streamed continuously after an InitializeJoggingRequest is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - JoggingErrorResponse with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the JoggingResponse, verify that the robot control is in the desired state, e.g. standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP. The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send `InitializeJoggingRequest` to configure the jogging.  - Sets the robot controller mode to control mode. - Sets rate and coordinate system for the jogging response.  #### 2. Send `JointVelocityRequest` or `TcpVelocityRequest` to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with `JointVelocityRequest` or `TcpVelocityRequest`. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - `InitializeJoggingResponse` is sent to signal the success or failure of the `InitializeJoggingRequest`. - Jogging responses are streamed continuously after an `InitializeJoggingRequest` is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - `JoggingErrorResponse` with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the `JoggingResponse`, verify that the robot control is in the desired state, e.g., standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
    * @summary Execute Jogging
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7631,7 +7631,7 @@ declare const JoggingApiFactory: (configuration?: Configuration, basePath?: stri
  */
 declare class JoggingApi extends BaseAPI {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP (Tool Center Point). The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send InitializeJoggingRequest to configure the jogging.  Sets robot controller mode to control mode. Sets rate and coordinate system for the jogging response.  #### 2. Send JointVelocityRequest or TcpVelocityRequest to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with JointVelocityRequest or TcpVelocityRequest. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - InitializeJoggingResponse is sent to signal the success or failure of the InitializeJoggingRequest. - Jogging responses are streamed continuously after an InitializeJoggingRequest is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - JoggingErrorResponse with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the JoggingResponse, verify that the robot control is in the desired state, e.g. standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a dynamically adaptable jogging motion for a motion group.  Jogging describes controlling a motion group by sending real-time commands to move either its joints or the TCP. The commands contain target velocities that may change at any time during execution, so the resulting motion cannot be computed upfront.  ### Preconditions  The motion group is not moved by any other endpoint.  ### Requests  #### 1. Send `InitializeJoggingRequest` to configure the jogging.  - Sets the robot controller mode to control mode. - Sets rate and coordinate system for the jogging response.  #### 2. Send `JointVelocityRequest` or `TcpVelocityRequest` to start the jogging motion.  #### 3. Change or stop the jogging motion  - Change the jogging direction and/or velocity during the jogging motion with `JointVelocityRequest` or `TcpVelocityRequest`. - To stop the jogging motion, send zero velocities via either request.  ### Responses  - `InitializeJoggingResponse` is sent to signal the success or failure of the `InitializeJoggingRequest`. - Jogging responses are streamed continuously after an `InitializeJoggingRequest` is processed.   Jogging responses contain the robot controller state and the state of the jogging control. - `JoggingErrorResponse` with error details is sent in case of an unexpected error, e.g., controller disconnects during jogging.  ### Tips and Tricks  - In the `JoggingResponse`, verify that the robot control is in the desired state, e.g., standstill, with JoggingState. - Ensure that the websocket connection remains open until the jogging motion is stopped to avoid unexpected stops.
    * @summary Execute Jogging
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7763,14 +7763,14 @@ declare const LicenseApiAxiosParamCreator: (configuration?: Configuration) => {
    */
   deactivateLicense: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get information on the license used with the Wandelbots NOVA instance, e.g. licensed product, expiration date, license status.
+   * Get information on the license used with the Wandelbots NOVA instance, e.g., licensed product, expiration date, license status.
    * @summary Get license
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    */
   getLicense: (options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get the license status. If `valid`, Wandelbots NOVA can be used. If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
+   * Get the license status.  - If `valid`, Wandelbots NOVA can be used. - If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
    * @summary Get license status
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
@@ -7798,14 +7798,14 @@ declare const LicenseApiFp: (configuration?: Configuration) => {
    */
   deactivateLicense(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Get information on the license used with the Wandelbots NOVA instance, e.g. licensed product, expiration date, license status.
+   * Get information on the license used with the Wandelbots NOVA instance, e.g., licensed product, expiration date, license status.
    * @summary Get license
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    */
   getLicense(options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<License>>;
   /**
-   * Get the license status. If `valid`, Wandelbots NOVA can be used. If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
+   * Get the license status.  - If `valid`, Wandelbots NOVA can be used. - If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
    * @summary Get license status
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
@@ -7833,14 +7833,14 @@ declare const LicenseApiFactory: (configuration?: Configuration, basePath?: stri
    */
   deactivateLicense(options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Get information on the license used with the Wandelbots NOVA instance, e.g. licensed product, expiration date, license status.
+   * Get information on the license used with the Wandelbots NOVA instance, e.g., licensed product, expiration date, license status.
    * @summary Get license
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    */
   getLicense(options?: RawAxiosRequestConfig): AxiosPromise<License>;
   /**
-   * Get the license status. If `valid`, Wandelbots NOVA can be used. If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
+   * Get the license status.  - If `valid`, Wandelbots NOVA can be used. - If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
    * @summary Get license status
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
@@ -7872,7 +7872,7 @@ declare class LicenseApi extends BaseAPI {
    */
   deactivateLicense(options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Get information on the license used with the Wandelbots NOVA instance, e.g. licensed product, expiration date, license status.
+   * Get information on the license used with the Wandelbots NOVA instance, e.g., licensed product, expiration date, license status.
    * @summary Get license
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
@@ -7880,7 +7880,7 @@ declare class LicenseApi extends BaseAPI {
    */
   getLicense(options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<License, any>>;
   /**
-   * Get the license status. If `valid`, Wandelbots NOVA can be used. If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
+   * Get the license status.  - If `valid`, Wandelbots NOVA can be used. - If `expired`, the license has to be renewed in order to use Wandelbots NOVA.
    * @summary Get license status
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
@@ -7905,7 +7905,7 @@ declare const MotionGroupApiAxiosParamCreator: (configuration?: Configuration) =
    */
   getCurrentMotionGroupState: (cell: string, controller: string, motionGroup: string, responseCoordinateSystem?: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc. This data might change upon connection to the robot.
+   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc.  This data can change upon connection to the robot.
    * @summary Description
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7915,7 +7915,7 @@ declare const MotionGroupApiAxiosParamCreator: (configuration?: Configuration) =
    */
   getMotionGroupDescription: (cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the motion group state. The stream will be closed from the server if the controller is disconnected.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the motion group state.  The stream will be closed from the server if the controller is disconnected.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7944,7 +7944,7 @@ declare const MotionGroupApiFp: (configuration?: Configuration) => {
    */
   getCurrentMotionGroupState(cell: string, controller: string, motionGroup: string, responseCoordinateSystem?: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<MotionGroupState>>;
   /**
-   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc. This data might change upon connection to the robot.
+   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc.  This data can change upon connection to the robot.
    * @summary Description
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7954,7 +7954,7 @@ declare const MotionGroupApiFp: (configuration?: Configuration) => {
    */
   getMotionGroupDescription(cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<MotionGroupDescription>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the motion group state. The stream will be closed from the server if the controller is disconnected.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the motion group state.  The stream will be closed from the server if the controller is disconnected.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7983,7 +7983,7 @@ declare const MotionGroupApiFactory: (configuration?: Configuration, basePath?:
    */
   getCurrentMotionGroupState(cell: string, controller: string, motionGroup: string, responseCoordinateSystem?: string, options?: RawAxiosRequestConfig): AxiosPromise<MotionGroupState>;
   /**
-   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc. This data might change upon connection to the robot.
+   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc.  This data can change upon connection to the robot.
    * @summary Description
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -7993,7 +7993,7 @@ declare const MotionGroupApiFactory: (configuration?: Configuration, basePath?:
    */
   getMotionGroupDescription(cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig): AxiosPromise<MotionGroupDescription>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the motion group state. The stream will be closed from the server if the controller is disconnected.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the motion group state.  The stream will be closed from the server if the controller is disconnected.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -8025,7 +8025,7 @@ declare class MotionGroupApi extends BaseAPI {
    */
   getCurrentMotionGroupState(cell: string, controller: string, motionGroup: string, responseCoordinateSystem?: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<MotionGroupState, any>>;
   /**
-   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc. This data might change upon connection to the robot.
+   * Get the set of parameters that describe the motion group and its configuration including safety zones, limits, etc.  This data can change upon connection to the robot.
    * @summary Description
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -8036,7 +8036,7 @@ declare class MotionGroupApi extends BaseAPI {
    */
   getMotionGroupDescription(cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<MotionGroupDescription, any>>;
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Receive updates of the motion group state. The stream will be closed from the server if the controller is disconnected.
+   * <!-- theme: success -->  > Websocket endpoint  Receive updates of the motion group state.  The stream will be closed from the server if the controller is disconnected.
    * @summary Stream State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -8058,7 +8058,7 @@ declare const MotionGroupModelsApiAxiosParamCreator: (configuration?: Configurat
    * 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).
+   * @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).
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    */
@@ -8081,7 +8081,7 @@ declare const MotionGroupModelsApiFp: (configuration?: Configuration) => {
    * 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).
+   * @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).
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    */
@@ -8106,7 +8106,7 @@ declare const MotionGroupModelsApiFactory: (configuration?: Configuration, baseP
    * 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).
+   * @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).
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    */
@@ -8133,7 +8133,7 @@ declare class MotionGroupModelsApi extends BaseAPI {
    * 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).
+   * @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).
    * @param {*} [options] Override http request option.
    * @throws {RequiredError}
    * @memberof MotionGroupModelsApi
@@ -8409,7 +8409,7 @@ declare const StoreCollisionComponentsApiAxiosParamCreator: (configuration?: Con
    */
   listStoredCollisionTools: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Stores collider.  If the collider does not exist, it will be created. If the collider exists, it will be updated.
+   * Stores collider.  - If the collider does not exist, it will be created. - If the collider exists, it will be updated.
    * @summary Store Collider
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} collider Unique identifier addressing a collider.
@@ -8419,7 +8419,7 @@ declare const StoreCollisionComponentsApiAxiosParamCreator: (configuration?: Con
    */
   storeCollider: (cell: string, collider: string, collider2: Collider, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Stores link chain.  If the link chain does not exist, it will be created. If the link chain exists, it will be updated.
+   * Stores link chain.  - If the link chain does not exist, it will be created. - If the link chain exists, it will be updated.
    * @summary Store Link Chain
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} linkChain Unique identifier addressing a collision link chain.
@@ -8431,7 +8431,7 @@ declare const StoreCollisionComponentsApiAxiosParamCreator: (configuration?: Con
     [key: string]: Collider;
   }>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Stores the tool.  If the tool does not exist, it will be created. If the tool exists, it will be updated.
+   * Stores the tool.  - If the tool does not exist, it will be created. - If the tool exists, it will be updated.
    * @summary Store Tool
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} tool Unique identifier addressing a collision tool.
@@ -8541,7 +8541,7 @@ declare const StoreCollisionComponentsApiFp: (configuration?: Configuration) =>
     };
   }>>;
   /**
-   * Stores collider.  If the collider does not exist, it will be created. If the collider exists, it will be updated.
+   * Stores collider.  - If the collider does not exist, it will be created. - If the collider exists, it will be updated.
    * @summary Store Collider
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} collider Unique identifier addressing a collider.
@@ -8551,7 +8551,7 @@ declare const StoreCollisionComponentsApiFp: (configuration?: Configuration) =>
    */
   storeCollider(cell: string, collider: string, collider2: Collider, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Collider>>;
   /**
-   * Stores link chain.  If the link chain does not exist, it will be created. If the link chain exists, it will be updated.
+   * Stores link chain.  - If the link chain does not exist, it will be created. - If the link chain exists, it will be updated.
    * @summary Store Link Chain
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} linkChain Unique identifier addressing a collision link chain.
@@ -8565,7 +8565,7 @@ declare const StoreCollisionComponentsApiFp: (configuration?: Configuration) =>
     [key: string]: Collider;
   }>>>;
   /**
-   * Stores the tool.  If the tool does not exist, it will be created. If the tool exists, it will be updated.
+   * Stores the tool.  - If the tool does not exist, it will be created. - If the tool exists, it will be updated.
    * @summary Store Tool
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} tool Unique identifier addressing a collision tool.
@@ -8677,7 +8677,7 @@ declare const StoreCollisionComponentsApiFactory: (configuration?: Configuration
     };
   }>;
   /**
-   * Stores collider.  If the collider does not exist, it will be created. If the collider exists, it will be updated.
+   * Stores collider.  - If the collider does not exist, it will be created. - If the collider exists, it will be updated.
    * @summary Store Collider
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} collider Unique identifier addressing a collider.
@@ -8687,7 +8687,7 @@ declare const StoreCollisionComponentsApiFactory: (configuration?: Configuration
    */
   storeCollider(cell: string, collider: string, collider2: Collider, options?: RawAxiosRequestConfig): AxiosPromise<Collider>;
   /**
-   * Stores link chain.  If the link chain does not exist, it will be created. If the link chain exists, it will be updated.
+   * Stores link chain.  - If the link chain does not exist, it will be created. - If the link chain exists, it will be updated.
    * @summary Store Link Chain
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} linkChain Unique identifier addressing a collision link chain.
@@ -8701,7 +8701,7 @@ declare const StoreCollisionComponentsApiFactory: (configuration?: Configuration
     [key: string]: Collider;
   }>>;
   /**
-   * Stores the tool.  If the tool does not exist, it will be created. If the tool exists, it will be updated.
+   * Stores the tool.  - If the tool does not exist, it will be created. - If the tool exists, it will be updated.
    * @summary Store Tool
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} tool Unique identifier addressing a collision tool.
@@ -8824,7 +8824,7 @@ declare class StoreCollisionComponentsApi extends BaseAPI {
     };
   }, any>>;
   /**
-   * Stores collider.  If the collider does not exist, it will be created. If the collider exists, it will be updated.
+   * Stores collider.  - If the collider does not exist, it will be created. - If the collider exists, it will be updated.
    * @summary Store Collider
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} collider Unique identifier addressing a collider.
@@ -8835,7 +8835,7 @@ declare class StoreCollisionComponentsApi extends BaseAPI {
    */
   storeCollider(cell: string, collider: string, collider2: Collider, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<Collider, any>>;
   /**
-   * Stores link chain.  If the link chain does not exist, it will be created. If the link chain exists, it will be updated.
+   * Stores link chain.  - If the link chain does not exist, it will be created. - If the link chain exists, it will be updated.
    * @summary Store Link Chain
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} linkChain Unique identifier addressing a collision link chain.
@@ -8850,7 +8850,7 @@ declare class StoreCollisionComponentsApi extends BaseAPI {
     [key: string]: Collider;
   }[], any>>;
   /**
-   * Stores the tool.  If the tool does not exist, it will be created. If the tool exists, it will be updated.
+   * Stores the tool.  - If the tool does not exist, it will be created. - If the tool exists, it will be updated.
    * @summary Store Tool
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} tool Unique identifier addressing a collision tool.
@@ -8897,7 +8897,7 @@ declare const StoreCollisionSetupsApiAxiosParamCreator: (configuration?: Configu
    */
   listStoredCollisionSetups: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Stores collision setup.  If the collision setup does not exist, it will be created. If the collision setup exists, it will be updated.
+   * Stores collision setup.  - If the collision setup does not exist, it will be created. - If the collision setup exists, it will be updated.
    * @summary Store Collision Setup
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} setup Identifier of the collision setup
@@ -8941,7 +8941,7 @@ declare const StoreCollisionSetupsApiFp: (configuration?: Configuration) => {
     [key: string]: CollisionSetup;
   }>>;
   /**
-   * Stores collision setup.  If the collision setup does not exist, it will be created. If the collision setup exists, it will be updated.
+   * Stores collision setup.  - If the collision setup does not exist, it will be created. - If the collision setup exists, it will be updated.
    * @summary Store Collision Setup
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} setup Identifier of the collision setup
@@ -8985,7 +8985,7 @@ declare const StoreCollisionSetupsApiFactory: (configuration?: Configuration, ba
     [key: string]: CollisionSetup;
   }>;
   /**
-   * Stores collision setup.  If the collision setup does not exist, it will be created. If the collision setup exists, it will be updated.
+   * Stores collision setup.  - If the collision setup does not exist, it will be created. - If the collision setup exists, it will be updated.
    * @summary Store Collision Setup
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} setup Identifier of the collision setup
@@ -9034,7 +9034,7 @@ declare class StoreCollisionSetupsApi extends BaseAPI {
     [key: string]: CollisionSetup;
   }, any>>;
   /**
-   * Stores collision setup.  If the collision setup does not exist, it will be created. If the collision setup exists, it will be updated.
+   * Stores collision setup.  - If the collision setup does not exist, it will be created. - If the collision setup exists, it will be updated.
    * @summary Store Collision Setup
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} setup Identifier of the collision setup
@@ -9068,7 +9068,7 @@ declare const StoreObjectApiAxiosParamCreator: (configuration?: Configuration) =
    */
   deleteObject: (cell: string, key: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get the object.  This request returns the object and any metadata attached to it.
+   * Returns content and metadata of a stored object.
    * @summary Get Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9077,7 +9077,7 @@ declare const StoreObjectApiAxiosParamCreator: (configuration?: Configuration) =
    */
   getObject: (cell: string, key: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get object metadata.  Objects can be large. Therefore this request only returns metadata without fetching the object\'s content.
+   * Returns metadata. Object content is not returned.
    * @summary Get Object Metadata
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9094,7 +9094,7 @@ declare const StoreObjectApiAxiosParamCreator: (configuration?: Configuration) =
    */
   listAllObjectKeys: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  Optional: Specify metadata as a dictionary with names and values.
+   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  #### Optional Specify metadata as a dictionary with names and values.
    * @summary Store Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9130,7 +9130,7 @@ declare const StoreObjectApiFp: (configuration?: Configuration) => {
    */
   deleteObject(cell: string, key: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Get the object.  This request returns the object and any metadata attached to it.
+   * Returns content and metadata of a stored object.
    * @summary Get Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9139,7 +9139,7 @@ declare const StoreObjectApiFp: (configuration?: Configuration) => {
    */
   getObject(cell: string, key: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<File>>;
   /**
-   * Get object metadata.  Objects can be large. Therefore this request only returns metadata without fetching the object\'s content.
+   * Returns metadata. Object content is not returned.
    * @summary Get Object Metadata
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9156,7 +9156,7 @@ declare const StoreObjectApiFp: (configuration?: Configuration) => {
    */
   listAllObjectKeys(cell: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<string>>>;
   /**
-   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  Optional: Specify metadata as a dictionary with names and values.
+   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  #### Optional Specify metadata as a dictionary with names and values.
    * @summary Store Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9192,7 +9192,7 @@ declare const StoreObjectApiFactory: (configuration?: Configuration, basePath?:
    */
   deleteObject(cell: string, key: string, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Get the object.  This request returns the object and any metadata attached to it.
+   * Returns content and metadata of a stored object.
    * @summary Get Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9201,7 +9201,7 @@ declare const StoreObjectApiFactory: (configuration?: Configuration, basePath?:
    */
   getObject(cell: string, key: string, options?: RawAxiosRequestConfig): AxiosPromise<File>;
   /**
-   * Get object metadata.  Objects can be large. Therefore this request only returns metadata without fetching the object\'s content.
+   * Returns metadata. Object content is not returned.
    * @summary Get Object Metadata
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9218,7 +9218,7 @@ declare const StoreObjectApiFactory: (configuration?: Configuration, basePath?:
    */
   listAllObjectKeys(cell: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<string>>;
   /**
-   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  Optional: Specify metadata as a dictionary with names and values.
+   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  #### Optional Specify metadata as a dictionary with names and values.
    * @summary Store Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9258,7 +9258,7 @@ declare class StoreObjectApi extends BaseAPI {
    */
   deleteObject(cell: string, key: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Get the object.  This request returns the object and any metadata attached to it.
+   * Returns content and metadata of a stored object.
    * @summary Get Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9268,7 +9268,7 @@ declare class StoreObjectApi extends BaseAPI {
    */
   getObject(cell: string, key: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<File, any>>;
   /**
-   * Get object metadata.  Objects can be large. Therefore this request only returns metadata without fetching the object\'s content.
+   * Returns metadata. Object content is not returned.
    * @summary Get Object Metadata
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9287,7 +9287,7 @@ declare class StoreObjectApi extends BaseAPI {
    */
   listAllObjectKeys(cell: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<string[], any>>;
   /**
-   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  Optional: Specify metadata as a dictionary with names and values.
+   * Store any data as an object.  Using a key which already contains an object will override the previously stored object. Use [getObjectMetadata](getObjectMetadata) to verify that the key does not contain objects.  #### Optional Specify metadata as a dictionary with names and values.
    * @summary Store Object
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} key
@@ -9630,7 +9630,7 @@ declare class SystemApi extends BaseAPI {
  */
 declare const TrajectoryCachingApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * <!-- theme: info -->  > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable. The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
+   * Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable.  <!-- theme: info -->  > #### NOTE > > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
    * @summary Add Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9649,7 +9649,7 @@ declare const TrajectoryCachingApiAxiosParamCreator: (configuration?: Configurat
    */
   clearTrajectories: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Delete a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
+   * Delete a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
    * @summary Delete Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9659,7 +9659,7 @@ declare const TrajectoryCachingApiAxiosParamCreator: (configuration?: Configurat
    */
   deleteTrajectory: (cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories.
+   * Get a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories.
    * @summary Get Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9669,7 +9669,7 @@ declare const TrajectoryCachingApiAxiosParamCreator: (configuration?: Configurat
    */
   getTrajectory: (cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * List currently cached trajectories. Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
+   * List currently cached trajectories.  Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
    * @summary List Trajectories
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9684,7 +9684,7 @@ declare const TrajectoryCachingApiAxiosParamCreator: (configuration?: Configurat
  */
 declare const TrajectoryCachingApiFp: (configuration?: Configuration) => {
   /**
-   * <!-- theme: info -->  > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable. The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
+   * Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable.  <!-- theme: info -->  > #### NOTE > > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
    * @summary Add Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9703,7 +9703,7 @@ declare const TrajectoryCachingApiFp: (configuration?: Configuration) => {
    */
   clearTrajectories(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Delete a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
+   * Delete a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
    * @summary Delete Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9713,7 +9713,7 @@ declare const TrajectoryCachingApiFp: (configuration?: Configuration) => {
    */
   deleteTrajectory(cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Get a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories.
+   * Get a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories.
    * @summary Get Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9723,7 +9723,7 @@ declare const TrajectoryCachingApiFp: (configuration?: Configuration) => {
    */
   getTrajectory(cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<GetTrajectoryResponse>>;
   /**
-   * List currently cached trajectories. Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
+   * List currently cached trajectories.  Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
    * @summary List Trajectories
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9738,7 +9738,7 @@ declare const TrajectoryCachingApiFp: (configuration?: Configuration) => {
  */
 declare const TrajectoryCachingApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * <!-- theme: info -->  > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable. The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
+   * Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable.  <!-- theme: info -->  > #### NOTE > > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
    * @summary Add Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9757,7 +9757,7 @@ declare const TrajectoryCachingApiFactory: (configuration?: Configuration, baseP
    */
   clearTrajectories(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Delete a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
+   * Delete a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
    * @summary Delete Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9767,7 +9767,7 @@ declare const TrajectoryCachingApiFactory: (configuration?: Configuration, baseP
    */
   deleteTrajectory(cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Get a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories.
+   * Get a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories.
    * @summary Get Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9777,7 +9777,7 @@ declare const TrajectoryCachingApiFactory: (configuration?: Configuration, baseP
    */
   getTrajectory(cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig): AxiosPromise<GetTrajectoryResponse>;
   /**
-   * List currently cached trajectories. Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
+   * List currently cached trajectories.  Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
    * @summary List Trajectories
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9794,7 +9794,7 @@ declare const TrajectoryCachingApiFactory: (configuration?: Configuration, baseP
  */
 declare class TrajectoryCachingApi extends BaseAPI {
   /**
-   * <!-- theme: info -->  > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable. The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
+   * Loads and validates the data of a trajectory into the execution cache, rendering the trajectory executable.  <!-- theme: info -->  > #### NOTE > > Using the trajectory cache is an optional performance optimization. It is not necessary to use the cache to execute trajectories.  The response contains the result of the validation of the trajectory.  Validation can lead to three different results: - Fully valid: The whole trajectory can be executed from start to end. The response will contain an unique identifier which is used to move the robot. - Partially valid: Only parts of the trajectory can be executed. The response will contain an unique identifier to move the robot   and information about the failure for the part that is not executable. - Invalid: The trajectory can not be executed. The response will tell you the reason of failure.  If the trajectory is at least partially valid, the parts of the trajectory that are valid can be executed using the [executeTrajectory](executeTrajectory) endpoint.  The workflow is as follows:   - Generate a trajectory with [planTrajectory](planTrajectory) or your own motion planner,   - Send the trajectory to this endpoint to validate it and get a unique identifier for it,   - The unique identifier will appear in the list of available trajectories, see [listTrajectories](listTrajectories) endpoint, if it is at least partially executable.   - Execute your trajectory using the [executeTrajectory](executeTrajectory) endpoint.
    * @summary Add Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9815,7 +9815,7 @@ declare class TrajectoryCachingApi extends BaseAPI {
    */
   clearTrajectories(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Delete a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
+   * Delete a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories. Trajectories are removed automatically if the motion group or the corresponding controller is disconnected.
    * @summary Delete Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9826,7 +9826,7 @@ declare class TrajectoryCachingApi extends BaseAPI {
    */
   deleteTrajectory(cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Get a previously created trajectory from cache. Use [listTrajectories](listTrajectories) to list all cached trajectories.
+   * Get a previously created trajectory from cache.  Use [listTrajectories](listTrajectories) to list all cached trajectories.
    * @summary Get Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9837,7 +9837,7 @@ declare class TrajectoryCachingApi extends BaseAPI {
    */
   getTrajectory(cell: string, controller: string, trajectory: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<GetTrajectoryResponse, any>>;
   /**
-   * List currently cached trajectories. Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
+   * List currently cached trajectories.  Use [addTrajectory](addTrajectory) to add a new trajectory. Adding trajectories is necessary to execute them. Trajectories are removed if the corresponding motion group or controller disconnects.
    * @summary List Trajectories
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9853,7 +9853,7 @@ declare class TrajectoryCachingApi extends BaseAPI {
  */
 declare const TrajectoryExecutionApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a previously planned trajectory. Enables the caller to attach input/output actions to the trajectory.  Understanding the concept of location:   The location or path parameter specifies the exact position along a trajectory.   The location is a scalar value that ranges from 0 to `n`,   where `n` denotes the number of motion commands, or trajectory segments, e.g. line, p2p, etc. See [planMotion](planMotion).   Each integer value of the location corresponds to one motion command, e.g. 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with InitializeMovementRequest. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send InitializeMovementRequest to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send StartMovementRequest to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send PauseMovementRequest before the movement has reached its end location. - Change the movement\'s velocity with PlaybackSpeedRequest after initializing the movement with InitializeMovementRequest.  ### Responses  - InitializeMovementResponse is sent to signal the success or failure of the InitializeMovementRequest. - Movement responses are streamed after a StartMovementRequest successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by InitializeMovementRequest. - Standstill reponse  is sent once the movement has finished or has come to a standstill due to a pause. - PauseMovementResponse is sent to signal the success of the PauseMovementRequest. It does not signal the end of the movement.   End of movement is signaled by Standstill reponse . - PlaybackSpeedResponse is sent to signal the success of the PlaybackSpeedRequest. - MovementError with error details is sent in case of an unexpected error, e.g. controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending PauseMovementRequest and StartMovementRequest. - Send PlaybackSpeedRequest before StartMovementRequest to reduce the velocity of the movement before it starts. - Send PlaybackSpeedRequest repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send PlaybackSpeedRequest with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending StartMovementRequest after the movement has finished.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a previously [planned trajectory](planTrajectory). Enables the caller to attach input/output actions to the trajectory.  ### Movement behavior  | Virtual controller | Physical controller | |------------------|-------------------| | Desired joint configurations are commanded to each motion group and **applied immediately** | Move to desired **actual joint configuration**, **if possible** |  ### Concept of location    - The location or path parameter specifies the exact position along a trajectory.   - The location is a scalar value that ranges from 0 to `n`, where `n` denotes the number of motion commands, or trajectory segments, e.g., line, p2p, etc. See [planTrajectory](planTrajectory).   - Each integer value of the location corresponds to one motion command, e.g., 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with `InitializeMovementRequest`. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send `InitializeMovementRequest` to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send `StartMovementRequest` to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send `PauseMovementRequest` before the movement has reached its end location. - Change the movement\'s velocity with `PlaybackSpeedRequest` after initializing the movement with `InitializeMovementRequest`.  ### Responses  - `InitializeMovementResponse` is sent to signal the success or failure of the `InitializeMovementRequest`. - Movement responses are streamed after a `StartMovementRequest` successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by `InitializeMovementRequest`. - Standstill response is sent once the movement has finished or has come to a standstill due to a pause. - `PauseMovementResponse` is sent to signal the success of the `PauseMovementRequest`. It does not signal the end of the movement.   End of movement is signaled by Standstill response. - `PlaybackSpeedResponse` is sent to signal the success of the `PlaybackSpeedRequest`. - `MovementError` with error details is sent in case of an unexpected error, e.g., controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending `PauseMovementRequest` and `StartMovementRequest`. - Send `PlaybackSpeedRequest` before `StartMovementRequest` to reduce the velocity of the movement before it starts. - Send `PlaybackSpeedRequest` repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send `PlaybackSpeedRequest` with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending `StartMovementRequest` after the movement has finished.
    * @summary Execute Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9869,7 +9869,7 @@ declare const TrajectoryExecutionApiAxiosParamCreator: (configuration?: Configur
  */
 declare const TrajectoryExecutionApiFp: (configuration?: Configuration) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a previously planned trajectory. Enables the caller to attach input/output actions to the trajectory.  Understanding the concept of location:   The location or path parameter specifies the exact position along a trajectory.   The location is a scalar value that ranges from 0 to `n`,   where `n` denotes the number of motion commands, or trajectory segments, e.g. line, p2p, etc. See [planMotion](planMotion).   Each integer value of the location corresponds to one motion command, e.g. 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with InitializeMovementRequest. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send InitializeMovementRequest to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send StartMovementRequest to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send PauseMovementRequest before the movement has reached its end location. - Change the movement\'s velocity with PlaybackSpeedRequest after initializing the movement with InitializeMovementRequest.  ### Responses  - InitializeMovementResponse is sent to signal the success or failure of the InitializeMovementRequest. - Movement responses are streamed after a StartMovementRequest successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by InitializeMovementRequest. - Standstill reponse  is sent once the movement has finished or has come to a standstill due to a pause. - PauseMovementResponse is sent to signal the success of the PauseMovementRequest. It does not signal the end of the movement.   End of movement is signaled by Standstill reponse . - PlaybackSpeedResponse is sent to signal the success of the PlaybackSpeedRequest. - MovementError with error details is sent in case of an unexpected error, e.g. controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending PauseMovementRequest and StartMovementRequest. - Send PlaybackSpeedRequest before StartMovementRequest to reduce the velocity of the movement before it starts. - Send PlaybackSpeedRequest repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send PlaybackSpeedRequest with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending StartMovementRequest after the movement has finished.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a previously [planned trajectory](planTrajectory). Enables the caller to attach input/output actions to the trajectory.  ### Movement behavior  | Virtual controller | Physical controller | |------------------|-------------------| | Desired joint configurations are commanded to each motion group and **applied immediately** | Move to desired **actual joint configuration**, **if possible** |  ### Concept of location    - The location or path parameter specifies the exact position along a trajectory.   - The location is a scalar value that ranges from 0 to `n`, where `n` denotes the number of motion commands, or trajectory segments, e.g., line, p2p, etc. See [planTrajectory](planTrajectory).   - Each integer value of the location corresponds to one motion command, e.g., 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with `InitializeMovementRequest`. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send `InitializeMovementRequest` to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send `StartMovementRequest` to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send `PauseMovementRequest` before the movement has reached its end location. - Change the movement\'s velocity with `PlaybackSpeedRequest` after initializing the movement with `InitializeMovementRequest`.  ### Responses  - `InitializeMovementResponse` is sent to signal the success or failure of the `InitializeMovementRequest`. - Movement responses are streamed after a `StartMovementRequest` successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by `InitializeMovementRequest`. - Standstill response is sent once the movement has finished or has come to a standstill due to a pause. - `PauseMovementResponse` is sent to signal the success of the `PauseMovementRequest`. It does not signal the end of the movement.   End of movement is signaled by Standstill response. - `PlaybackSpeedResponse` is sent to signal the success of the `PlaybackSpeedRequest`. - `MovementError` with error details is sent in case of an unexpected error, e.g., controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending `PauseMovementRequest` and `StartMovementRequest`. - Send `PlaybackSpeedRequest` before `StartMovementRequest` to reduce the velocity of the movement before it starts. - Send `PlaybackSpeedRequest` repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send `PlaybackSpeedRequest` with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending `StartMovementRequest` after the movement has finished.
    * @summary Execute Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9885,7 +9885,7 @@ declare const TrajectoryExecutionApiFp: (configuration?: Configuration) => {
  */
 declare const TrajectoryExecutionApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a previously planned trajectory. Enables the caller to attach input/output actions to the trajectory.  Understanding the concept of location:   The location or path parameter specifies the exact position along a trajectory.   The location is a scalar value that ranges from 0 to `n`,   where `n` denotes the number of motion commands, or trajectory segments, e.g. line, p2p, etc. See [planMotion](planMotion).   Each integer value of the location corresponds to one motion command, e.g. 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with InitializeMovementRequest. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send InitializeMovementRequest to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send StartMovementRequest to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send PauseMovementRequest before the movement has reached its end location. - Change the movement\'s velocity with PlaybackSpeedRequest after initializing the movement with InitializeMovementRequest.  ### Responses  - InitializeMovementResponse is sent to signal the success or failure of the InitializeMovementRequest. - Movement responses are streamed after a StartMovementRequest successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by InitializeMovementRequest. - Standstill reponse  is sent once the movement has finished or has come to a standstill due to a pause. - PauseMovementResponse is sent to signal the success of the PauseMovementRequest. It does not signal the end of the movement.   End of movement is signaled by Standstill reponse . - PlaybackSpeedResponse is sent to signal the success of the PlaybackSpeedRequest. - MovementError with error details is sent in case of an unexpected error, e.g. controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending PauseMovementRequest and StartMovementRequest. - Send PlaybackSpeedRequest before StartMovementRequest to reduce the velocity of the movement before it starts. - Send PlaybackSpeedRequest repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send PlaybackSpeedRequest with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending StartMovementRequest after the movement has finished.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a previously [planned trajectory](planTrajectory). Enables the caller to attach input/output actions to the trajectory.  ### Movement behavior  | Virtual controller | Physical controller | |------------------|-------------------| | Desired joint configurations are commanded to each motion group and **applied immediately** | Move to desired **actual joint configuration**, **if possible** |  ### Concept of location    - The location or path parameter specifies the exact position along a trajectory.   - The location is a scalar value that ranges from 0 to `n`, where `n` denotes the number of motion commands, or trajectory segments, e.g., line, p2p, etc. See [planTrajectory](planTrajectory).   - Each integer value of the location corresponds to one motion command, e.g., 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with `InitializeMovementRequest`. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send `InitializeMovementRequest` to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send `StartMovementRequest` to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send `PauseMovementRequest` before the movement has reached its end location. - Change the movement\'s velocity with `PlaybackSpeedRequest` after initializing the movement with `InitializeMovementRequest`.  ### Responses  - `InitializeMovementResponse` is sent to signal the success or failure of the `InitializeMovementRequest`. - Movement responses are streamed after a `StartMovementRequest` successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by `InitializeMovementRequest`. - Standstill response is sent once the movement has finished or has come to a standstill due to a pause. - `PauseMovementResponse` is sent to signal the success of the `PauseMovementRequest`. It does not signal the end of the movement.   End of movement is signaled by Standstill response. - `PlaybackSpeedResponse` is sent to signal the success of the `PlaybackSpeedRequest`. - `MovementError` with error details is sent in case of an unexpected error, e.g., controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending `PauseMovementRequest` and `StartMovementRequest`. - Send `PlaybackSpeedRequest` before `StartMovementRequest` to reduce the velocity of the movement before it starts. - Send `PlaybackSpeedRequest` repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send `PlaybackSpeedRequest` with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending `StartMovementRequest` after the movement has finished.
    * @summary Execute Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9903,7 +9903,7 @@ declare const TrajectoryExecutionApiFactory: (configuration?: Configuration, bas
  */
 declare class TrajectoryExecutionApi extends BaseAPI {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  Provides execution control over a previously planned trajectory. Enables the caller to attach input/output actions to the trajectory.  Understanding the concept of location:   The location or path parameter specifies the exact position along a trajectory.   The location is a scalar value that ranges from 0 to `n`,   where `n` denotes the number of motion commands, or trajectory segments, e.g. line, p2p, etc. See [planMotion](planMotion).   Each integer value of the location corresponds to one motion command, e.g. 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with InitializeMovementRequest. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send InitializeMovementRequest to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send StartMovementRequest to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send PauseMovementRequest before the movement has reached its end location. - Change the movement\'s velocity with PlaybackSpeedRequest after initializing the movement with InitializeMovementRequest.  ### Responses  - InitializeMovementResponse is sent to signal the success or failure of the InitializeMovementRequest. - Movement responses are streamed after a StartMovementRequest successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by InitializeMovementRequest. - Standstill reponse  is sent once the movement has finished or has come to a standstill due to a pause. - PauseMovementResponse is sent to signal the success of the PauseMovementRequest. It does not signal the end of the movement.   End of movement is signaled by Standstill reponse . - PlaybackSpeedResponse is sent to signal the success of the PlaybackSpeedRequest. - MovementError with error details is sent in case of an unexpected error, e.g. controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending PauseMovementRequest and StartMovementRequest. - Send PlaybackSpeedRequest before StartMovementRequest to reduce the velocity of the movement before it starts. - Send PlaybackSpeedRequest repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send PlaybackSpeedRequest with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending StartMovementRequest after the movement has finished.
+   * <!-- theme: success -->  > Websocket endpoint  Provides execution control over a previously [planned trajectory](planTrajectory). Enables the caller to attach input/output actions to the trajectory.  ### Movement behavior  | Virtual controller | Physical controller | |------------------|-------------------| | Desired joint configurations are commanded to each motion group and **applied immediately** | Move to desired **actual joint configuration**, **if possible** |  ### Concept of location    - The location or path parameter specifies the exact position along a trajectory.   - The location is a scalar value that ranges from 0 to `n`, where `n` denotes the number of motion commands, or trajectory segments, e.g., line, p2p, etc. See [planTrajectory](planTrajectory).   - Each integer value of the location corresponds to one motion command, e.g., 3.0 to 3.999 could be a line.  ### Preconditions  - The motion group\'s control mode is not claimed by any other endpoint. - The motion group\'s joint position are at start location specified with `InitializeMovementRequest`. - Use [executeToTrajectory](executeToTrajectory) to move the robot to the start location.  ### Requests  #### 1. Send `InitializeMovementRequest` to lock the trajectory to this connection   The following actions are executed:   - Sets robot controller mode to control mode,   - Sets start location of the execution    Keep in mind that only a single trajectory can be locked to a websocket connection at a time and not unlocked anymore.   To execute another trajectory, a new connection must be established.  #### 2. Send `StartMovementRequest` to start the movement  Sets direction of movement, default is forward.  #### **Optional**  - To pause, send `PauseMovementRequest` before the movement has reached its end location. - Change the movement\'s velocity with `PlaybackSpeedRequest` after initializing the movement with `InitializeMovementRequest`.  ### Responses  - `InitializeMovementResponse` is sent to signal the success or failure of the `InitializeMovementRequest`. - Movement responses are streamed after a `StartMovementRequest` successfully started the movement.   Movement responses are streamed in a rate that is defined as the multiple of the controller step-rate closest to   but not exceeding the rate configured by `InitializeMovementRequest`. - Standstill response is sent once the movement has finished or has come to a standstill due to a pause. - `PauseMovementResponse` is sent to signal the success of the `PauseMovementRequest`. It does not signal the end of the movement.   End of movement is signaled by Standstill response. - `PlaybackSpeedResponse` is sent to signal the success of the `PlaybackSpeedRequest`. - `MovementError` with error details is sent in case of an unexpected error, e.g., controller disconnects during movement.  ### Tips and Tricks  - A movement can be paused and resumed by sending `PauseMovementRequest` and `StartMovementRequest`. - Send `PlaybackSpeedRequest` before `StartMovementRequest` to reduce the velocity of the movement before it starts. - Send `PlaybackSpeedRequest` repeatedly to implement a slider. The velocity of the motion group can be adjusted with each controller step. Therefore, if your app needs a slider-like UI to alter the velocity of a currently running movement, you can send `PlaybackSpeedRequest` with different speed values repeatedly during the movement. - A closed trajectory (end and start joint position are equal) can be repeated by sending `StartMovementRequest` after the movement has finished.
    * @summary Execute Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -9929,7 +9929,7 @@ declare const TrajectoryPlanningApiAxiosParamCreator: (configuration?: Configura
    */
   planCollisionFree: (cell: string, planCollisionFreeRequest?: PlanCollisionFreeRequest, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the [PlanTrajectoryResponse](PlanTrajectoryResponse) will contain the joint trajectory up until the error, e.g. all samples until a collision occurs. EXCEPTION: If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
+   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the response will contain the joint trajectory up until the error, e.g., all samples until a collision occurs.   <!-- theme: info -->  > #### Exception > > If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
    * @summary Plan Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {PlanTrajectoryRequest} [planTrajectoryRequest]
@@ -9953,7 +9953,7 @@ declare const TrajectoryPlanningApiFp: (configuration?: Configuration) => {
    */
   planCollisionFree(cell: string, planCollisionFreeRequest?: PlanCollisionFreeRequest, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<PlanCollisionFreeResponse>>;
   /**
-   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the [PlanTrajectoryResponse](PlanTrajectoryResponse) will contain the joint trajectory up until the error, e.g. all samples until a collision occurs. EXCEPTION: If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
+   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the response will contain the joint trajectory up until the error, e.g., all samples until a collision occurs.   <!-- theme: info -->  > #### Exception > > If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
    * @summary Plan Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {PlanTrajectoryRequest} [planTrajectoryRequest]
@@ -9977,7 +9977,7 @@ declare const TrajectoryPlanningApiFactory: (configuration?: Configuration, base
    */
   planCollisionFree(cell: string, planCollisionFreeRequest?: PlanCollisionFreeRequest, options?: RawAxiosRequestConfig): AxiosPromise<PlanCollisionFreeResponse>;
   /**
-   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the [PlanTrajectoryResponse](PlanTrajectoryResponse) will contain the joint trajectory up until the error, e.g. all samples until a collision occurs. EXCEPTION: If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
+   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the response will contain the joint trajectory up until the error, e.g., all samples until a collision occurs.   <!-- theme: info -->  > #### Exception > > If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
    * @summary Plan Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {PlanTrajectoryRequest} [planTrajectoryRequest]
@@ -10004,7 +10004,7 @@ declare class TrajectoryPlanningApi extends BaseAPI {
    */
   planCollisionFree(cell: string, planCollisionFreeRequest?: PlanCollisionFreeRequest, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<PlanCollisionFreeResponse, any>>;
   /**
-   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the [PlanTrajectoryResponse](PlanTrajectoryResponse) will contain the joint trajectory up until the error, e.g. all samples until a collision occurs. EXCEPTION: If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
+   * Plans a new trajectory for a single motion group.  Describe the trajectory as a sequence of motion commands that the robots TCP should follow.  Use the following workflow to execute a planned trajectory: 1. Plan a trajectory. 2. Optional: Load the planned trajectory into the cache using the [addTrajectory](addTrajectory) endpoint. 3. Execute the (cached) trajectory using the [executeTrajectory](executeTrajectory) endpoint.  If the trajectory is not executable, the response will contain the joint trajectory up until the error, e.g., all samples until a collision occurs.   <!-- theme: info -->  > #### Exception > > If a CartesianPTP or JointPTP motion command has an invalid target, the response will contain the trajectory up until the start of the invalid PTP motion.
    * @summary Plan Trajectory
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {PlanTrajectoryRequest} [planTrajectoryRequest]
@@ -10020,7 +10020,7 @@ declare class TrajectoryPlanningApi extends BaseAPI {
  */
 declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * 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.
+   * Adds a coordinate system to the robot controller.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is added, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10031,7 +10031,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   addVirtualControllerCoordinateSystem: (cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When adding or updating a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The TCP may not be immediately visible or appear outdated in visualizations. > - All connections to virtual robot are closed and re-established, which introduces a short delay before the TCP is available for operation. > > The API call itself does **not wait until the restart and re-synchronization are complete**. > A successful response indicates that the request was accepted, but the TCP may not yet be visible nor usable.
    * @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.
@@ -10043,7 +10043,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   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 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is removed, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10054,7 +10054,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   deleteVirtualControllerCoordinateSystem: (cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * 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.
+   * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  <!-- theme: info -->  > #### NOTE > > When removing a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The removal of the TCP may not be immediately visible or appear outdated in visualizations. > - All connections to 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**. > A successful response indicates that the request was accepted, but the then used TCP may not yet be visible nor usable.
    * @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.
@@ -10065,7 +10065,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   deleteVirtualControllerTcp: (cell: string, controller: string, motionGroup: string, tcp: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
+   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
    * @summary Get Emergency Stop State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10093,7 +10093,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   getMotionGroups: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Requests the Operation Mode of the virtual robot controller.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  **Note:** The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Requests the operation mode of the virtual robot controller.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Get Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10102,7 +10102,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   getOperationMode: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Gets motion group mounting. The motion group is based on the origin of the returned coordinate system.
+   * Gets motion group mounting.  The motion group is based on the origin of the returned coordinate system.
    * @summary Get 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.
@@ -10121,7 +10121,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   listVirtualControllerCoordinateSystems: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Lists TCPs of the motion group. An empty TCP list is valid, for example for external axes.
+   * Lists TCPs of the motion group.  An empty TCP list is valid, e.g., for external axes.
    * @summary List TCPs
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10131,7 +10131,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   listVirtualControllerTcps: (cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths. Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
+   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths.  Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
    * @summary Push or Release Emergency Stop
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10141,7 +10141,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   setEmergencyStop: (cell: string, controller: string, active?: boolean, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state. The values are immediately applied to the joints of the motion group. We recommend to only use the endpoint when the motion group is in monitor mode. In case the motion group is controlled, currently jogging or planning motions, the values are overridden by the controller or an error may occur.
+   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state.  The values are immediately applied to the joints of the motion group.  <!-- theme: info -->  > #### NOTE > > Only use the endpoint when the motion group is in monitor mode. If the motion group is controlled, currently jogging or planning motions, > the values are overridden by the controller or an error may occur.
    * @summary Set Motion Group State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10152,7 +10152,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   setMotionGroupState: (cell: string, controller: string, motionGroup: string, motionGroupJoints: MotionGroupJoints, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Changes the Operation Mode of the virtual robot controller to the specified value.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Changes the operation mode of the virtual robot controller to the specified value.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Set Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10162,7 +10162,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
    */
   setOperationMode: (cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### Changing the mounting configuration is considered a setup change > > When the mounting is set to a new coordinate system, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or not reflect the new mounting immediately. > - Motion group state and coordinate system alignment may not be immediately visible in visualizations. > - All connections to 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**. > 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.
@@ -10179,7 +10179,7 @@ declare const VirtualControllerApiAxiosParamCreator: (configuration?: Configurat
  */
 declare const VirtualControllerApiFp: (configuration?: Configuration) => {
   /**
-   * 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.
+   * Adds a coordinate system to the robot controller.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is added, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10190,7 +10190,7 @@ 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 (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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When adding or updating a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The TCP may not be immediately visible or appear outdated in visualizations. > - All connections to virtual robot are closed and re-established, which introduces a short delay before the TCP is available for operation. > > The API call itself does **not wait until the restart and re-synchronization are complete**. > A successful response indicates that the request was accepted, but the TCP may not yet be visible nor usable.
    * @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.
@@ -10202,7 +10202,7 @@ 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 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is removed, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10213,7 +10213,7 @@ 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 (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.
+   * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  <!-- theme: info -->  > #### NOTE > > When removing a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The removal of the TCP may not be immediately visible or appear outdated in visualizations. > - All connections to 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**. > A successful response indicates that the request was accepted, but the then used TCP may not yet be visible nor usable.
    * @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.
@@ -10224,7 +10224,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   deleteVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
+   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
    * @summary Get Emergency Stop State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10252,7 +10252,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   getMotionGroups(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<MotionGroupInfo>>>;
   /**
-   * Requests the Operation Mode of the virtual robot controller.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  **Note:** The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Requests the operation mode of the virtual robot controller.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Get Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10261,7 +10261,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   getOperationMode(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<OpMode>>;
   /**
-   * Gets motion group mounting. The motion group is based on the origin of the returned coordinate system.
+   * Gets motion group mounting.  The motion group is based on the origin of the returned coordinate system.
    * @summary Get 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.
@@ -10280,7 +10280,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   listVirtualControllerCoordinateSystems(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<CoordinateSystem>>>;
   /**
-   * Lists TCPs of the motion group. An empty TCP list is valid, for example for external axes.
+   * Lists TCPs of the motion group.  An empty TCP list is valid, e.g., for external axes.
    * @summary List TCPs
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10290,7 +10290,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   listVirtualControllerTcps(cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<RobotTcp>>>;
   /**
-   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths. Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
+   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths.  Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
    * @summary Push or Release Emergency Stop
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10300,7 +10300,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   setEmergencyStop(cell: string, controller: string, active?: boolean, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state. The values are immediately applied to the joints of the motion group. We recommend to only use the endpoint when the motion group is in monitor mode. In case the motion group is controlled, currently jogging or planning motions, the values are overridden by the controller or an error may occur.
+   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state.  The values are immediately applied to the joints of the motion group.  <!-- theme: info -->  > #### NOTE > > Only use the endpoint when the motion group is in monitor mode. If the motion group is controlled, currently jogging or planning motions, > the values are overridden by the controller or an error may occur.
    * @summary Set Motion Group State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10311,7 +10311,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   setMotionGroupState(cell: string, controller: string, motionGroup: string, motionGroupJoints: MotionGroupJoints, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * Changes the Operation Mode of the virtual robot controller to the specified value.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Changes the operation mode of the virtual robot controller to the specified value.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Set Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10321,7 +10321,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
    */
   setOperationMode(cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### Changing the mounting configuration is considered a setup change > > When the mounting is set to a new coordinate system, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or not reflect the new mounting immediately. > - Motion group state and coordinate system alignment may not be immediately visible in visualizations. > - All connections to 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**. > 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.
@@ -10338,7 +10338,7 @@ declare const VirtualControllerApiFp: (configuration?: Configuration) => {
  */
 declare const VirtualControllerApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * 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.
+   * Adds a coordinate system to the robot controller.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is added, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10349,7 +10349,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   addVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When adding or updating a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The TCP may not be immediately visible or appear outdated in visualizations. > - All connections to virtual robot are closed and re-established, which introduces a short delay before the TCP is available for operation. > > The API call itself does **not wait until the restart and re-synchronization are complete**. > A successful response indicates that the request was accepted, but the TCP may not yet be visible nor usable.
    * @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.
@@ -10361,7 +10361,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   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 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is removed, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10372,7 +10372,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   deleteVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * 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.
+   * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  <!-- theme: info -->  > #### NOTE > > When removing a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The removal of the TCP may not be immediately visible or appear outdated in visualizations. > - All connections to 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**. > A successful response indicates that the request was accepted, but the then used TCP may not yet be visible nor usable.
    * @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.
@@ -10383,7 +10383,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   deleteVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
+   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
    * @summary Get Emergency Stop State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10411,7 +10411,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   getMotionGroups(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<MotionGroupInfo>>;
   /**
-   * Requests the Operation Mode of the virtual robot controller.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  **Note:** The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Requests the operation mode of the virtual robot controller.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Get Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10420,7 +10420,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   getOperationMode(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<OpMode>;
   /**
-   * Gets motion group mounting. The motion group is based on the origin of the returned coordinate system.
+   * Gets motion group mounting.  The motion group is based on the origin of the returned coordinate system.
    * @summary Get 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.
@@ -10439,7 +10439,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   listVirtualControllerCoordinateSystems(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<CoordinateSystem>>;
   /**
-   * Lists TCPs of the motion group. An empty TCP list is valid, for example for external axes.
+   * Lists TCPs of the motion group.  An empty TCP list is valid, e.g., for external axes.
    * @summary List TCPs
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10449,7 +10449,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   listVirtualControllerTcps(cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<RobotTcp>>;
   /**
-   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths. Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
+   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths.  Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
    * @summary Push or Release Emergency Stop
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10459,7 +10459,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   setEmergencyStop(cell: string, controller: string, active?: boolean, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state. The values are immediately applied to the joints of the motion group. We recommend to only use the endpoint when the motion group is in monitor mode. In case the motion group is controlled, currently jogging or planning motions, the values are overridden by the controller or an error may occur.
+   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state.  The values are immediately applied to the joints of the motion group.  <!-- theme: info -->  > #### NOTE > > Only use the endpoint when the motion group is in monitor mode. If the motion group is controlled, currently jogging or planning motions, > the values are overridden by the controller or an error may occur.
    * @summary Set Motion Group State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10470,7 +10470,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   setMotionGroupState(cell: string, controller: string, motionGroup: string, motionGroupJoints: MotionGroupJoints, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * Changes the Operation Mode of the virtual robot controller to the specified value.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Changes the operation mode of the virtual robot controller to the specified value.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Set Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10480,7 +10480,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
    */
   setOperationMode(cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig): AxiosPromise<void>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### Changing the mounting configuration is considered a setup change > > When the mounting is set to a new coordinate system, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or not reflect the new mounting immediately. > - Motion group state and coordinate system alignment may not be immediately visible in visualizations. > - All connections to 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**. > 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.
@@ -10499,7 +10499,7 @@ declare const VirtualControllerApiFactory: (configuration?: Configuration, baseP
  */
 declare class VirtualControllerApi extends BaseAPI {
   /**
-   * 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.
+   * Adds a coordinate system to the robot controller.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is added, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10511,7 +10511,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   addVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, coordinateSystemData: CoordinateSystemData, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When adding or updating a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The TCP may not be immediately visible or appear outdated in visualizations. > - All connections to virtual robot are closed and re-established, which introduces a short delay before the TCP is available for operation. > > The API call itself does **not wait until the restart and re-synchronization are complete**. > A successful response indicates that the request was accepted, but the TCP may not yet be visible nor usable.
    * @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.
@@ -10524,7 +10524,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   addVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, robotTcpData: RobotTcpData, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### NOTE > > When a new coordinate system is removed, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or appear outdated in the UI. > - Coordinate system changes are not immediately visible in visualizations. > - All connections to 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.
@@ -10536,7 +10536,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   deleteVirtualControllerCoordinateSystem(cell: string, controller: string, coordinateSystem: string, deleteDependent?: boolean, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * 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.
+   * Removes the TCP (Tool Center Point) from the motion group. An unknown TCP is a valid input and will simply be ignored.  <!-- theme: info -->  > #### NOTE > > When removing a TCP, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear. > - The removal of the TCP may not be immediately visible or appear outdated in visualizations. > - All connections to 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**. > A successful response indicates that the request was accepted, but the then used TCP may not yet be visible nor usable.
    * @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.
@@ -10548,7 +10548,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   deleteVirtualControllerTcp(cell: string, controller: string, motionGroup: string, tcp: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
+   * Requests the Emergency Stop state of the virtual robot controller.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed when using virtual robot controllers.
    * @summary Get Emergency Stop State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10579,7 +10579,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   getMotionGroups(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<MotionGroupInfo[], any>>;
   /**
-   * Requests the Operation Mode of the virtual robot controller.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  **Note:** The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Requests the operation mode of the virtual robot controller.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Get Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10589,7 +10589,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   getOperationMode(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<OpMode, any>>;
   /**
-   * Gets motion group mounting. The motion group is based on the origin of the returned coordinate system.
+   * Gets motion group mounting.  The motion group is based on the origin of the returned coordinate system.
    * @summary Get 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.
@@ -10610,7 +10610,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   listVirtualControllerCoordinateSystems(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<CoordinateSystem[], any>>;
   /**
-   * Lists TCPs of the motion group. An empty TCP list is valid, for example for external axes.
+   * Lists TCPs of the motion group.  An empty TCP list is valid, e.g., for external axes.
    * @summary List TCPs
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10621,7 +10621,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   listVirtualControllerTcps(cell: string, controller: string, motionGroup: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<RobotTcp[], any>>;
   /**
-   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths. Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state regardless of the controller type. There the Emergency Stop state is visible as the `safety_state`.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
+   * Activates or releases the Emergency Stop on the virtual robot controller.  Activating the Emergency Stop stops the execution of all motions. The stop is executed on physical controllers immediately not gracefully and not on paths.  Due to restricted physical behavior of the virtual robot controller, the Emergency Stop is executed on paths. To return to normal operation the Emergency Stop needs to be released.  Use [getCurrentMotionGroupState](getCurrentMotionGroupState) to get the Emergency Stop state with `safety_state` regardless of the controller type.  > **NOTE** > > The Emergency Stop state can only be changed via API when using virtual robot controllers.
    * @summary Push or Release Emergency Stop
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10632,7 +10632,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   setEmergencyStop(cell: string, controller: string, active?: boolean, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state. The values are immediately applied to the joints of the motion group. We recommend to only use the endpoint when the motion group is in monitor mode. In case the motion group is controlled, currently jogging or planning motions, the values are overridden by the controller or an error may occur.
+   * Sets the values for joint position, joint velocity or joint acceleration of a motion group state.  The values are immediately applied to the joints of the motion group.  <!-- theme: info -->  > #### NOTE > > Only use the endpoint when the motion group is in monitor mode. If the motion group is controlled, currently jogging or planning motions, > the values are overridden by the controller or an error may occur.
    * @summary Set Motion Group State
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10644,7 +10644,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   setMotionGroupState(cell: string, controller: string, motionGroup: string, motionGroupJoints: MotionGroupJoints, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * Changes the Operation Mode of the virtual robot controller to the specified value.  To get the Operation Mode regardless of the controller type use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The Operating Mode can only change be changed via API when using virtual robot controllers.
+   * Changes the operation mode of the virtual robot controller to the specified value.  To get the operation mode regardless of the controller type, use [getCurrentMotionGroupState](getCurrentMotionGroupState).  > **NOTE** > > The operation mode can only be changed via API when using virtual robot controllers.
    * @summary Set Operation Mode
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10655,7 +10655,7 @@ declare class VirtualControllerApi extends BaseAPI {
    */
   setOperationMode(cell: string, controller: string, mode: OperationMode, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<void, any>>;
   /**
-   * 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.
+   * 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.  <!-- theme: info -->  > #### Changing the mounting configuration is considered a setup change > > When the mounting is set to a new coordinate system, the **virtual robot is restarted** to apply the new configuration. > > During this restart: > - Robot visualization can temporarily disappear or not reflect the new mounting immediately. > - Motion group state and coordinate system alignment may not be immediately visible in visualizations. > - All connections to 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**. > 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.
@@ -10673,7 +10673,7 @@ declare class VirtualControllerApi extends BaseAPI {
  */
 declare const VirtualControllerBehaviorApiAxiosParamCreator: (configuration?: Configuration) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  This stream sends the commanded state (joint positions, velocities, accelerations, torques) for each motion group of the virtual controller and sets the joint configuration. Moving motion groups on virtual controllers can be executed by using Trajectory Planning and Trajectory Execution. Trajectory Execution commands the desired joint configuration to each motion group.  Physical motion groups move to this joint configuration.  With physical motion groups, this takes some time and only works if possible.  And you have the *actual* joint state - the current real motion group configuration.  Again, this stream is providing *commanded* joint state! > **NOTE** > > This stream provides *commanded* joint states, it **doesn\'t provide actual joint states**.  When the virtual controller receives joint commands the joint configuration is immediately adapted to match the incoming joint configuration. > **CAUTION** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  Possible use cases are: 1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.  The stream only sends data to the robot controller if a motion is executed.  If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs. Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic Freedrive motions.  <!-- theme: danger -->  > **DANGER** > > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration > will be executed with maximum speed regardless of safety zones and mechanical limits.
+   * <!-- theme: success -->  > Websocket endpoint  Sends the **commanded** state, e.g., joint positions, velocities, accelerations, torques, for each motion group of the virtual controller and sets the joint configuration.  Use [planTrajectory](planTrajectory) and [executeTrajectory](executeTrajectory) to move motion groups on virtual controllers.  Learn more about the [movement behavior of virtual controllers in comparison to physical controllers](executeTrajectory#movement-behavior).  > **NOTE** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  #### Use cases  1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.\\     The stream only sends data to the robot controller if a motion is executed.\\     If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs.     Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic freedrive motions.     <!-- theme: danger -->      > **DANGER**     >     > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration     > will be executed with maximum speed regardless of safety zones and mechanical limits.
    * @summary Stream Joint Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10692,7 +10692,7 @@ declare const VirtualControllerBehaviorApiAxiosParamCreator: (configuration?: Co
    */
   getCycleTime: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Get the current virtual controller behavior - please see the setter [setVirtualControllerBehavior](setVirtualControllerBehavior) and the enum for details.
+   * Get the current virtual controller behavior.  See [setVirtualControllerBehavior](setVirtualControllerBehavior) and the body for details.
    * @summary Get Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10701,7 +10701,7 @@ declare const VirtualControllerBehaviorApiAxiosParamCreator: (configuration?: Co
    */
   getVirtualControllerBehavior: (cell: string, controller: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Set virtual controller behavior.
+   * Set virtual controller behavior.  See query parameters for details.
    * @summary Set Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10717,7 +10717,7 @@ declare const VirtualControllerBehaviorApiAxiosParamCreator: (configuration?: Co
  */
 declare const VirtualControllerBehaviorApiFp: (configuration?: Configuration) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  This stream sends the commanded state (joint positions, velocities, accelerations, torques) for each motion group of the virtual controller and sets the joint configuration. Moving motion groups on virtual controllers can be executed by using Trajectory Planning and Trajectory Execution. Trajectory Execution commands the desired joint configuration to each motion group.  Physical motion groups move to this joint configuration.  With physical motion groups, this takes some time and only works if possible.  And you have the *actual* joint state - the current real motion group configuration.  Again, this stream is providing *commanded* joint state! > **NOTE** > > This stream provides *commanded* joint states, it **doesn\'t provide actual joint states**.  When the virtual controller receives joint commands the joint configuration is immediately adapted to match the incoming joint configuration. > **CAUTION** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  Possible use cases are: 1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.  The stream only sends data to the robot controller if a motion is executed.  If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs. Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic Freedrive motions.  <!-- theme: danger -->  > **DANGER** > > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration > will be executed with maximum speed regardless of safety zones and mechanical limits.
+   * <!-- theme: success -->  > Websocket endpoint  Sends the **commanded** state, e.g., joint positions, velocities, accelerations, torques, for each motion group of the virtual controller and sets the joint configuration.  Use [planTrajectory](planTrajectory) and [executeTrajectory](executeTrajectory) to move motion groups on virtual controllers.  Learn more about the [movement behavior of virtual controllers in comparison to physical controllers](executeTrajectory#movement-behavior).  > **NOTE** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  #### Use cases  1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.\\     The stream only sends data to the robot controller if a motion is executed.\\     If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs.     Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic freedrive motions.     <!-- theme: danger -->      > **DANGER**     >     > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration     > will be executed with maximum speed regardless of safety zones and mechanical limits.
    * @summary Stream Joint Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10736,7 +10736,7 @@ declare const VirtualControllerBehaviorApiFp: (configuration?: Configuration) =>
    */
   getCycleTime(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<CycleTime>>;
   /**
-   * Get the current virtual controller behavior - please see the setter [setVirtualControllerBehavior](setVirtualControllerBehavior) and the enum for details.
+   * Get the current virtual controller behavior.  See [setVirtualControllerBehavior](setVirtualControllerBehavior) and the body for details.
    * @summary Get Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10745,7 +10745,7 @@ declare const VirtualControllerBehaviorApiFp: (configuration?: Configuration) =>
    */
   getVirtualControllerBehavior(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Behavior>>;
   /**
-   * Set virtual controller behavior.
+   * Set virtual controller behavior.  See query parameters for details.
    * @summary Set Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10761,7 +10761,7 @@ declare const VirtualControllerBehaviorApiFp: (configuration?: Configuration) =>
  */
 declare const VirtualControllerBehaviorApiFactory: (configuration?: Configuration, basePath?: string, axios?: AxiosInstance) => {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  This stream sends the commanded state (joint positions, velocities, accelerations, torques) for each motion group of the virtual controller and sets the joint configuration. Moving motion groups on virtual controllers can be executed by using Trajectory Planning and Trajectory Execution. Trajectory Execution commands the desired joint configuration to each motion group.  Physical motion groups move to this joint configuration.  With physical motion groups, this takes some time and only works if possible.  And you have the *actual* joint state - the current real motion group configuration.  Again, this stream is providing *commanded* joint state! > **NOTE** > > This stream provides *commanded* joint states, it **doesn\'t provide actual joint states**.  When the virtual controller receives joint commands the joint configuration is immediately adapted to match the incoming joint configuration. > **CAUTION** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  Possible use cases are: 1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.  The stream only sends data to the robot controller if a motion is executed.  If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs. Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic Freedrive motions.  <!-- theme: danger -->  > **DANGER** > > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration > will be executed with maximum speed regardless of safety zones and mechanical limits.
+   * <!-- theme: success -->  > Websocket endpoint  Sends the **commanded** state, e.g., joint positions, velocities, accelerations, torques, for each motion group of the virtual controller and sets the joint configuration.  Use [planTrajectory](planTrajectory) and [executeTrajectory](executeTrajectory) to move motion groups on virtual controllers.  Learn more about the [movement behavior of virtual controllers in comparison to physical controllers](executeTrajectory#movement-behavior).  > **NOTE** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  #### Use cases  1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.\\     The stream only sends data to the robot controller if a motion is executed.\\     If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs.     Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic freedrive motions.     <!-- theme: danger -->      > **DANGER**     >     > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration     > will be executed with maximum speed regardless of safety zones and mechanical limits.
    * @summary Stream Joint Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10780,7 +10780,7 @@ declare const VirtualControllerBehaviorApiFactory: (configuration?: Configuratio
    */
   getCycleTime(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<CycleTime>;
   /**
-   * Get the current virtual controller behavior - please see the setter [setVirtualControllerBehavior](setVirtualControllerBehavior) and the enum for details.
+   * Get the current virtual controller behavior.  See [setVirtualControllerBehavior](setVirtualControllerBehavior) and the body for details.
    * @summary Get Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10789,7 +10789,7 @@ declare const VirtualControllerBehaviorApiFactory: (configuration?: Configuratio
    */
   getVirtualControllerBehavior(cell: string, controller: string, options?: RawAxiosRequestConfig): AxiosPromise<Behavior>;
   /**
-   * Set virtual controller behavior.
+   * Set virtual controller behavior.  See query parameters for details.
    * @summary Set Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10807,7 +10807,7 @@ declare const VirtualControllerBehaviorApiFactory: (configuration?: Configuratio
  */
 declare class VirtualControllerBehaviorApi extends BaseAPI {
   /**
-   * <!-- theme: danger -->  > Websocket endpoint  This stream sends the commanded state (joint positions, velocities, accelerations, torques) for each motion group of the virtual controller and sets the joint configuration. Moving motion groups on virtual controllers can be executed by using Trajectory Planning and Trajectory Execution. Trajectory Execution commands the desired joint configuration to each motion group.  Physical motion groups move to this joint configuration.  With physical motion groups, this takes some time and only works if possible.  And you have the *actual* joint state - the current real motion group configuration.  Again, this stream is providing *commanded* joint state! > **NOTE** > > This stream provides *commanded* joint states, it **doesn\'t provide actual joint states**.  When the virtual controller receives joint commands the joint configuration is immediately adapted to match the incoming joint configuration. > **CAUTION** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  Possible use cases are: 1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.  The stream only sends data to the robot controller if a motion is executed.  If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs. Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic Freedrive motions.  <!-- theme: danger -->  > **DANGER** > > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration > will be executed with maximum speed regardless of safety zones and mechanical limits.
+   * <!-- theme: success -->  > Websocket endpoint  Sends the **commanded** state, e.g., joint positions, velocities, accelerations, torques, for each motion group of the virtual controller and sets the joint configuration.  Use [planTrajectory](planTrajectory) and [executeTrajectory](executeTrajectory) to move motion groups on virtual controllers.  Learn more about the [movement behavior of virtual controllers in comparison to physical controllers](executeTrajectory#movement-behavior).  > **NOTE** > > Incoming joint configurations are not visualized and their velocity limits are not checked.  #### Use cases  1. Creating a robotic application that dynamically adapts to the configured joints on the robot controller, using this stream to feed new joint configurations back to the motion groups.\\     The stream only sends data to the robot controller if a motion is executed.\\     If the robot controller\'s joint configuration differs too much from the incoming joint configuration, a following error occurs.     Joint configurations that result in following errors are executed only for motions with a low velocity.  2. Mimic freedrive motions.     <!-- theme: danger -->      > **DANGER**     >     > If the incoming joint configuration is set to maximum velocity, the movement to reach this incoming joint configuration     > will be executed with maximum speed regardless of safety zones and mechanical limits.
    * @summary Stream Joint Configuration
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10828,7 +10828,7 @@ declare class VirtualControllerBehaviorApi extends BaseAPI {
    */
   getCycleTime(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<CycleTime, any>>;
   /**
-   * Get the current virtual controller behavior - please see the setter [setVirtualControllerBehavior](setVirtualControllerBehavior) and the enum for details.
+   * Get the current virtual controller behavior.  See [setVirtualControllerBehavior](setVirtualControllerBehavior) and the body for details.
    * @summary Get Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10838,7 +10838,7 @@ declare class VirtualControllerBehaviorApi extends BaseAPI {
    */
   getVirtualControllerBehavior(cell: string, controller: string, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<Behavior, any>>;
   /**
-   * Set virtual controller behavior.
+   * Set virtual controller behavior.  See query parameters for details.
    * @summary Set Behavior
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10865,7 +10865,7 @@ declare const VirtualControllerInputsOutputsApiAxiosParamCreator: (configuration
    */
   listIOs: (cell: string, controller: string, ios: Array<string>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
   /**
-   * Lists the input/output descriptions of the virtual robot controller.  The input/output descriptions contain information like name, type and unit. Available inputs/outputs are defined by the virtual robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, all available inputs/outputs are retrieved by this endpoint. Exception: When a filter (e.g., direction, value_type, group) is applied, only matching inputs/outputs are returned.
+   * Lists the input/output descriptions of the virtual robot controller.   The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the virtual robot controller.\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10904,7 +10904,7 @@ declare const VirtualControllerInputsOutputsApiFp: (configuration?: Configuratio
    */
   listIOs(cell: string, controller: string, ios: Array<string>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<IOValue>>>;
   /**
-   * Lists the input/output descriptions of the virtual robot controller.  The input/output descriptions contain information like name, type and unit. Available inputs/outputs are defined by the virtual robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, all available inputs/outputs are retrieved by this endpoint. Exception: When a filter (e.g., direction, value_type, group) is applied, only matching inputs/outputs are returned.
+   * Lists the input/output descriptions of the virtual robot controller.   The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the virtual robot controller.\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10943,7 +10943,7 @@ declare const VirtualControllerInputsOutputsApiFactory: (configuration?: Configu
    */
   listIOs(cell: string, controller: string, ios: Array<string>, options?: RawAxiosRequestConfig): AxiosPromise<Array<IOValue>>;
   /**
-   * Lists the input/output descriptions of the virtual robot controller.  The input/output descriptions contain information like name, type and unit. Available inputs/outputs are defined by the virtual robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, all available inputs/outputs are retrieved by this endpoint. Exception: When a filter (e.g., direction, value_type, group) is applied, only matching inputs/outputs are returned.
+   * Lists the input/output descriptions of the virtual robot controller.   The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the virtual robot controller.\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.
@@ -10985,7 +10985,7 @@ declare class VirtualControllerInputsOutputsApi extends BaseAPI {
    */
   listIOs(cell: string, controller: string, ios: Array<string>, options?: RawAxiosRequestConfig): Promise<axios0.AxiosResponse<IOValue[], any>>;
   /**
-   * Lists the input/output descriptions of the virtual robot controller.  The input/output descriptions contain information like name, type and unit. Available inputs/outputs are defined by the virtual robot controller. Each input/output has a unique identifier. If no identifiers are specified in the request, all available inputs/outputs are retrieved by this endpoint. Exception: When a filter (e.g., direction, value_type, group) is applied, only matching inputs/outputs are returned.
+   * Lists the input/output descriptions of the virtual robot controller.   The input/output descriptions contain information like name, type and unit.\\ Available inputs/outputs are defined by the virtual robot controller.\\ Each input/output has a unique identifier. - If no identifiers and no filters are specified in the request, all available inputs/outputs are retrieved by this endpoint. - If a filter, e.g., `direction`, `value_type`, `group` is applied, only matching inputs/outputs are returned.
    * @summary List Descriptions
    * @param {string} cell Unique identifier addressing a cell in all API calls.
    * @param {string} controller Unique identifier to address a controller in the cell.