@wandelbots/nova-api 26.5.0-dev.2 → 26.5.0-dev.20

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -6,7 +6,7 @@ import { AxiosInstance, AxiosPromise, RawAxiosRequestConfig } from "axios";
6
6
  * Wandelbots NOVA API
7
7
  * Interact with robots in an easy and intuitive way.
8
8
  *
9
- * The version of the OpenAPI document: 2.4.0
9
+ * The version of the OpenAPI document: 2.5.0 dev
10
10
  *
11
11
  *
12
12
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -700,6 +700,7 @@ interface CartesianLimits {
700
700
  * 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.
701
701
  */
702
702
  interface Cell {
703
+ [key: string]: any;
703
704
  /**
704
705
  * A unique name for the cell used as an identifier for addressing the cell in all API calls. It must be a valid k8s label name as defined by [RFC 1123](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names).
705
706
  */
@@ -2259,9 +2260,9 @@ type JointVelocityResponseKindEnum = typeof JointVelocityResponseKindEnum[keyof
2259
2260
  * A 6-DOF robot with spherical wrist has up to 8 inverse kinematics solutions for a given TCP pose (2^3 branches). Each branch represents one side of a kinematic singularity boundary. The three binary choices are shoulder, elbow, and wrist. > **NOTE** > > `FRONT`/`BACK`, `UP`/`DOWN`, `NO_FLIP`/`FLIP` are conventional > labels for the two sides of each branch. The labels describe the > typical geometric interpretation for common poses, but are not absolute spatial > directions. The labels are consistent within a given solver: The same physical > arm shape maps to the same branch value. The branch values are purely > geometric and describe the same physical configuration regardless of > vendor convention.
2260
2261
  */
2261
2262
  interface KinematicBranch {
2262
- 'wrist_branch'?: KinematicBranchWrist;
2263
- 'elbow_branch'?: KinematicBranchElbow;
2264
- 'shoulder_branch'?: KinematicBranchShoulder;
2263
+ 'wrist_branch': KinematicBranchWrist;
2264
+ 'elbow_branch': KinematicBranchElbow;
2265
+ 'shoulder_branch': KinematicBranchShoulder;
2265
2266
  }
2266
2267
  declare const KinematicBranchElbow: {
2267
2268
  readonly Up: "UP";
@@ -3157,6 +3158,10 @@ interface OperationLimits {
3157
3158
  'manual_limits'?: LimitSet;
3158
3159
  'manual_t1_limits'?: LimitSet;
3159
3160
  'manual_t2_limits'?: LimitSet;
3161
+ /**
3162
+ * Flag to indicate whether the TCP velocity limit is also applied for the elbow and flange in auto mode.
3163
+ */
3164
+ 'safety_limit_elbow_flange_velocity_in_auto'?: boolean;
3160
3165
  }
3161
3166
  /**
3162
3167
  * Current operation mode of the configured robot controller. Operation modes in which the attached motion groups can be moved are: - OPERATION_MODE_MANUAL (if enabling switch is pressed) - OPERATION_MODE_MANUAL_T1 (if enabling switch is pressed) - OPERATION_MODE_MANUAL_T2 (if enabling switch is pressed) - OPERATION_MODE_AUTO (without needing to press enabling switch) All other modes are considered as non-operational.
@@ -6,7 +6,7 @@ import { AxiosInstance, AxiosPromise, RawAxiosRequestConfig } from "axios";
6
6
  * Wandelbots NOVA API
7
7
  * Interact with robots in an easy and intuitive way.
8
8
  *
9
- * The version of the OpenAPI document: 2.4.0
9
+ * The version of the OpenAPI document: 2.5.0 dev
10
10
  *
11
11
  *
12
12
  * NOTE: This class is auto generated by OpenAPI Generator (https://openapi-generator.tech).
@@ -700,6 +700,7 @@ interface CartesianLimits {
700
700
  * 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.
701
701
  */
702
702
  interface Cell {
703
+ [key: string]: any;
703
704
  /**
704
705
  * A unique name for the cell used as an identifier for addressing the cell in all API calls. It must be a valid k8s label name as defined by [RFC 1123](https://kubernetes.io/docs/concepts/overview/working-with-objects/names/#dns-label-names).
705
706
  */
@@ -2259,9 +2260,9 @@ type JointVelocityResponseKindEnum = typeof JointVelocityResponseKindEnum[keyof
2259
2260
  * A 6-DOF robot with spherical wrist has up to 8 inverse kinematics solutions for a given TCP pose (2^3 branches). Each branch represents one side of a kinematic singularity boundary. The three binary choices are shoulder, elbow, and wrist. > **NOTE** > > `FRONT`/`BACK`, `UP`/`DOWN`, `NO_FLIP`/`FLIP` are conventional > labels for the two sides of each branch. The labels describe the > typical geometric interpretation for common poses, but are not absolute spatial > directions. The labels are consistent within a given solver: The same physical > arm shape maps to the same branch value. The branch values are purely > geometric and describe the same physical configuration regardless of > vendor convention.
2260
2261
  */
2261
2262
  interface KinematicBranch {
2262
- 'wrist_branch'?: KinematicBranchWrist;
2263
- 'elbow_branch'?: KinematicBranchElbow;
2264
- 'shoulder_branch'?: KinematicBranchShoulder;
2263
+ 'wrist_branch': KinematicBranchWrist;
2264
+ 'elbow_branch': KinematicBranchElbow;
2265
+ 'shoulder_branch': KinematicBranchShoulder;
2265
2266
  }
2266
2267
  declare const KinematicBranchElbow: {
2267
2268
  readonly Up: "UP";
@@ -3157,6 +3158,10 @@ interface OperationLimits {
3157
3158
  'manual_limits'?: LimitSet;
3158
3159
  'manual_t1_limits'?: LimitSet;
3159
3160
  'manual_t2_limits'?: LimitSet;
3161
+ /**
3162
+ * Flag to indicate whether the TCP velocity limit is also applied for the elbow and flange in auto mode.
3163
+ */
3164
+ 'safety_limit_elbow_flange_velocity_in_auto'?: boolean;
3160
3165
  }
3161
3166
  /**
3162
3167
  * Current operation mode of the configured robot controller. Operation modes in which the attached motion groups can be moved are: - OPERATION_MODE_MANUAL (if enabling switch is pressed) - OPERATION_MODE_MANUAL_T1 (if enabling switch is pressed) - OPERATION_MODE_MANUAL_T2 (if enabling switch is pressed) - OPERATION_MODE_AUTO (without needing to press enabling switch) All other modes are considered as non-operational.
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@wandelbots/nova-api",
3
- "version": "26.5.0-dev.2",
3
+ "version": "26.5.0-dev.20",
4
4
  "description": "API Client to interact with Wandelbots Public API.",
5
5
  "type": "module",
6
6
  "files": [