wandelbots-api-client 25.8.0.dev34__tar.gz → 25.8.0.dev36__tar.gz

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.1
 Name: wandelbots-api-client
-Version: 25.8.0.dev34
+Version: 25.8.0.dev36
 Summary: Wandelbots Python Client: Interact with robots in an easy and intuitive way. 
 Home-page: https://wandelbots.com/
 License: Apache-2.0
@@ -35,7 +35,7 @@ Description-Content-Type: text/markdown
 Interact with robots in an easy and intuitive way.
 
 - Compatible API version: 1.0.0 (can be found at the home screen of your instance -> API)
-- Package version: 25.8.0.dev34
+- Package version: 25.8.0.dev36
 
 Sign up for our [Wandelbots Developers Beta program](https://www.wandelbots.com/developers-beta) to get access to the Wandelbots API.
 

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/README.md

@@ -2,7 +2,7 @@
 Interact with robots in an easy and intuitive way.
 
 - Compatible API version: 1.0.0 (can be found at the home screen of your instance -> API)
-- Package version: 25.8.0.dev34
+- Package version: 25.8.0.dev36
 
 Sign up for our [Wandelbots Developers Beta program](https://www.wandelbots.com/developers-beta) to get access to the Wandelbots API.
 

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/pyproject.toml

@@ -1,6 +1,6 @@
 [tool.poetry]
 name = "wandelbots_api_client"
-version = "25.8.0.dev34"
+version = "25.8.0.dev36"
 description = "Wandelbots Python Client: Interact with robots in an easy and intuitive way. "
 authors = ["Copyright (c) 2025 Wandelbots GmbH <contact@wandelbots.com>"]
 license = "Apache-2.0"

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/__init__.py

@@ -14,7 +14,7 @@
 """  # noqa: E501
 
 
-__version__ = "25.8.0.dev34"
+__version__ = "25.8.0.dev36"
 
 from . import models
 from . import api

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/api_client.py

@@ -90,7 +90,7 @@ class ApiClient:
             self.default_headers[header_name] = header_value
         self.cookie = cookie
         # Set default User-Agent.
-        self.user_agent = 'Wandelbots-Nova-API-Python-Client/25.8.0.dev34'
+        self.user_agent = 'Wandelbots-Nova-API-Python-Client/25.8.0.dev36'
         self.client_side_validation = configuration.client_side_validation
 
     async def __aenter__(self):

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/configuration.py

@@ -524,7 +524,7 @@ conf = wandelbots_api_client.Configuration(
                "OS: {env}\n"\
                "Python Version: {pyversion}\n"\
                "Version of the API: 1.0.0\n"\
-               "SDK Package Version: 25.8.0.dev34".\
+               "SDK Package Version: 25.8.0.dev36".\
                format(env=sys.platform, pyversion=sys.version)
 
     def get_host_settings(self) -> List[HostSetting]:

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/__init__.py

@@ -14,7 +14,7 @@
 """  # noqa: E501
 
 
-__version__ = "25.8.0.dev34"
+__version__ = "25.8.0.dev36"
 
 from . import models
 from . import api

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/api/bus_inputs_outputs_api.py

@@ -2618,7 +2618,7 @@ class BUSInputsOutputsApi:
     ) -> List[IODescription2]:
         """List Descriptions
 
-        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service. 
+        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2686,7 +2686,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[List[IODescription2]]:
         """List Descriptions
 
-        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service. 
+        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2754,7 +2754,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """List Descriptions
 
-        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the BUS service. 
+        List all input/output descriptions for configured BUS services.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the BUS service. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2879,7 +2879,7 @@ class BUSInputsOutputsApi:
     ) -> List[ProfinetIO]:
         """List PROFINET Input/Output Configuration
 
-        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
+        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -2947,7 +2947,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[List[ProfinetIO]]:
         """List PROFINET Input/Output Configuration
 
-        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
+        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3015,7 +3015,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """List PROFINET Input/Output Configuration
 
-        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The I/O direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an I/O variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
+        List descriptions for all configured input/output variables of the PROFINET service.  The input/output descriptions contain information such as the name, the type and the unit. The input/output direction is given in perspective of the PROFINET Device, e.g. the configured PROFINET service.  The byte and bit addresses are the locations in the PROFINET input/output process image the variable points to. The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input and output process image. The NOVA PROFINET service's configuration is modified via [addProfinetIO](addProfinetIO) and [setProfinetIOsFromFile](setProfinetIOsFromFile). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding third party software, e.g. TIA portal. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3434,7 +3434,7 @@ class BUSInputsOutputsApi:
     ) -> None:
         """Set PROFINET Inputs/Outputs from File
 
-        Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled, meaning that you can paste the exported XML file here without modifying. 
+        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3507,7 +3507,7 @@ class BUSInputsOutputsApi:
     ) -> ApiResponse[None]:
         """Set PROFINET Inputs/Outputs from File
 
-        Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled, meaning that you can paste the exported XML file here without modifying. 
+        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str
@@ -3580,7 +3580,7 @@ class BUSInputsOutputsApi:
     ) -> RESTResponseType:
         """Set PROFINET Inputs/Outputs from File
 
-        Sets Input/Output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The Inputs/Outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller (i.e. a connected PLC), refer to the corresponding engineering system (i.e. TIA portal).  You can export the variable configuration of the PROFINET controller as XML file from you engineering system, i.e. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled, meaning that you can paste the exported XML file here without modifying. 
+        Sets input/output variable configuration on the PROFINET device (i.e. NOVA's PROFINET service) from XML file.  The inputs/outputs map variables to specific memory addresses in the process image.  The default process image has buffer lengths of 64 bytes for input and output. The size of the buffer is determined by the `config_file_content` that is passed in [addBusIOService](addBusIOService) and has to be in accordance with the GSDML file describing the PROFINET device.  The PROFINET controller as well as NOVA's PROFINET service use an input/output variable configuration to interpret the bits of the input/output process image. The NOVA's PROFINET service's configuration can be viewed via [listProfinetIOs](listProfinetIOs). For the PROFINET controller, e.g. a connected PLC, refer to the corresponding engineering system, e.g. TIA portal.  You can export the variable configuration of the PROFINET controller as XML file from your engineering system, e.g. TIA portal. The endpoint is built so that the perspective of input and output (PROFINET Device's input is PROFINET Controller's output) is internally handled (PROFINET device input is PROFINET controller output), meaning that you can paste the exported XML file here without modifying. 
 
         :param cell: Unique identifier addressing a cell in all API calls.  (required)
         :type cell: str

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/api_client.py

@@ -90,7 +90,7 @@ class ApiClient:
             self.default_headers[header_name] = header_value
         self.cookie = cookie
         # Set default User-Agent.
-        self.user_agent = 'Wandelbots-Nova-API-Python-Client/25.8.0.dev34'
+        self.user_agent = 'Wandelbots-Nova-API-Python-Client/25.8.0.dev36'
         self.client_side_validation = configuration.client_side_validation
 
     async def __aenter__(self):

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/configuration.py

@@ -524,7 +524,7 @@ conf = wandelbots_api_client.v2.Configuration(
                "OS: {env}\n"\
                "Python Version: {pyversion}\n"\
                "Version of the API: 2.0.0 beta\n"\
-               "SDK Package Version: 25.8.0.dev34".\
+               "SDK Package Version: 25.8.0.dev36".\
                format(env=sys.platform, pyversion=sys.version)
 
     def get_host_settings(self) -> List[HostSetting]:

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/models/bus_io_profinet.py

@@ -29,11 +29,10 @@ class BusIOProfinet(BaseModel):
     PROFINET BUS inputs/outputs service configuration. 
     """ # noqa: E501
     bus_type: Optional[StrictStr] = 'profinet'
-    config_file_content: Optional[StrictStr] = Field(default=None, description="Content of Configuration XML file for PROFINET device, typically known as PND_IOD.xml. Leave empty for the default configuration.  Refer to the official PROFINET driver documentation for further information. ")
     network_config: Optional[BusIOProfinetNetwork] = Field(default=None, description="Used to enable IP communication through the same physical interface while PN Driver is running.")
     mac: StrictStr = Field(description="MAC address of the physical ethernet interface that you want to use for PROFINET communication.")
     default_route: BusIOProfinetDefaultRoute
-    __properties: ClassVar[List[str]] = ["bus_type", "config_file_content", "network_config", "mac", "default_route"]
+    __properties: ClassVar[List[str]] = ["bus_type", "network_config", "mac", "default_route"]
 
     @field_validator('bus_type')
     def bus_type_validate_enum(cls, value):
@@ -107,7 +106,6 @@ class BusIOProfinet(BaseModel):
 
         _obj = cls.model_validate({
             "bus_type": obj.get("bus_type") if obj.get("bus_type") is not None else 'profinet',
-            "config_file_content": obj.get("config_file_content"),
             "network_config": BusIOProfinetNetwork.from_dict(obj["network_config"]) if obj.get("network_config") is not None else None,
             "mac": obj.get("mac"),
             "default_route": BusIOProfinetDefaultRoute.from_dict(obj["default_route"]) if obj.get("default_route") is not None else None

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/models/integer_value.py

@@ -24,7 +24,7 @@ from typing_extensions import Self
 
 class IntegerValue(BaseModel):
     """
-    Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > We recommend to use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value. 
+    Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > Recommended: Use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value. 
     """ # noqa: E501
     value: StrictStr
     value_type: Optional[StrictStr] = 'integer'

{wandelbots_api_client-25.8.0.dev34 → wandelbots_api_client-25.8.0.dev36}/wandelbots_api_client/v2/models/io_integer_value.py

@@ -27,7 +27,7 @@ class IOIntegerValue(BaseModel):
     IOIntegerValue
     """ # noqa: E501
     io: StrictStr = Field(description="Unique identifier of the input/output.")
-    value: StrictStr = Field(description="Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > We recommend to use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value. ")
+    value: StrictStr = Field(description="Value of an input/output with integer representation.  > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. > Recommended: Use int64 in your implementation. If you want to interact with int64 in numbers, > JS bigint libraries can help you to parse the string into an integral value. ")
     value_type: Optional[StrictStr] = 'integer'
     __properties: ClassVar[List[str]] = ["io", "value", "value_type"]