@wandelbots/nova-api 25.8.0-dev.35 → 25.8.0-dev.37
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.
- package/package.json +1 -1
- package/v2/api.d.ts +14 -14
- package/v2/api.js +12 -12
- package/v2/api.ts +14 -14
package/package.json
CHANGED
package/v2/api.d.ts
CHANGED
|
@@ -1916,7 +1916,7 @@ export interface IOIntegerValue {
|
|
|
1916
1916
|
*/
|
|
1917
1917
|
'io': string;
|
|
1918
1918
|
/**
|
|
1919
|
-
* Value of an input/output with integer representation. > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. >
|
|
1919
|
+
* 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.
|
|
1920
1920
|
* @type {string}
|
|
1921
1921
|
* @memberof IOIntegerValue
|
|
1922
1922
|
*/
|
|
@@ -2168,7 +2168,7 @@ export declare const InitializeMovementResponseKindEnum: {
|
|
|
2168
2168
|
};
|
|
2169
2169
|
export type InitializeMovementResponseKindEnum = typeof InitializeMovementResponseKindEnum[keyof typeof InitializeMovementResponseKindEnum];
|
|
2170
2170
|
/**
|
|
2171
|
-
* Value of an input/output with integer representation. > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. >
|
|
2171
|
+
* 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.
|
|
2172
2172
|
* @export
|
|
2173
2173
|
* @interface IntegerValue
|
|
2174
2174
|
*/
|
|
@@ -5896,7 +5896,7 @@ export declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Conf
|
|
|
5896
5896
|
*/
|
|
5897
5897
|
getProfinetIOsFromFile: (cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
|
|
5898
5898
|
/**
|
|
5899
|
-
* 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
|
|
5899
|
+
* 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.
|
|
5900
5900
|
* @summary List Descriptions
|
|
5901
5901
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
5902
5902
|
* @param {*} [options] Override http request option.
|
|
@@ -5904,7 +5904,7 @@ export declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Conf
|
|
|
5904
5904
|
*/
|
|
5905
5905
|
listBusIODescriptions: (cell: string, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
|
|
5906
5906
|
/**
|
|
5907
|
-
* 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
|
|
5907
|
+
* 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.
|
|
5908
5908
|
* @summary List PROFINET Input/Output Configuration
|
|
5909
5909
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
5910
5910
|
* @param {*} [options] Override http request option.
|
|
@@ -5921,7 +5921,7 @@ export declare const BUSInputsOutputsApiAxiosParamCreator: (configuration?: Conf
|
|
|
5921
5921
|
*/
|
|
5922
5922
|
setBusIOValues: (cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig) => Promise<RequestArgs>;
|
|
5923
5923
|
/**
|
|
5924
|
-
* Sets
|
|
5924
|
+
* 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.
|
|
5925
5925
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
5926
5926
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
5927
5927
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -6017,7 +6017,7 @@ export declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
|
|
|
6017
6017
|
*/
|
|
6018
6018
|
getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<string>>;
|
|
6019
6019
|
/**
|
|
6020
|
-
* 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
|
|
6020
|
+
* 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.
|
|
6021
6021
|
* @summary List Descriptions
|
|
6022
6022
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6023
6023
|
* @param {*} [options] Override http request option.
|
|
@@ -6025,7 +6025,7 @@ export declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
|
|
|
6025
6025
|
*/
|
|
6026
6026
|
listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<IODescription2>>>;
|
|
6027
6027
|
/**
|
|
6028
|
-
* 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
|
|
6028
|
+
* 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.
|
|
6029
6029
|
* @summary List PROFINET Input/Output Configuration
|
|
6030
6030
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6031
6031
|
* @param {*} [options] Override http request option.
|
|
@@ -6042,7 +6042,7 @@ export declare const BUSInputsOutputsApiFp: (configuration?: Configuration) => {
|
|
|
6042
6042
|
*/
|
|
6043
6043
|
setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<void>>;
|
|
6044
6044
|
/**
|
|
6045
|
-
* Sets
|
|
6045
|
+
* 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.
|
|
6046
6046
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
6047
6047
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6048
6048
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -6138,7 +6138,7 @@ export declare const BUSInputsOutputsApiFactory: (configuration?: Configuration,
|
|
|
6138
6138
|
*/
|
|
6139
6139
|
getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): AxiosPromise<string>;
|
|
6140
6140
|
/**
|
|
6141
|
-
* 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
|
|
6141
|
+
* 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.
|
|
6142
6142
|
* @summary List Descriptions
|
|
6143
6143
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6144
6144
|
* @param {*} [options] Override http request option.
|
|
@@ -6146,7 +6146,7 @@ export declare const BUSInputsOutputsApiFactory: (configuration?: Configuration,
|
|
|
6146
6146
|
*/
|
|
6147
6147
|
listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): AxiosPromise<Array<IODescription2>>;
|
|
6148
6148
|
/**
|
|
6149
|
-
* 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
|
|
6149
|
+
* 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.
|
|
6150
6150
|
* @summary List PROFINET Input/Output Configuration
|
|
6151
6151
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6152
6152
|
* @param {*} [options] Override http request option.
|
|
@@ -6163,7 +6163,7 @@ export declare const BUSInputsOutputsApiFactory: (configuration?: Configuration,
|
|
|
6163
6163
|
*/
|
|
6164
6164
|
setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): AxiosPromise<void>;
|
|
6165
6165
|
/**
|
|
6166
|
-
* Sets
|
|
6166
|
+
* 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.
|
|
6167
6167
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
6168
6168
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6169
6169
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -6270,7 +6270,7 @@ export declare class BUSInputsOutputsApi extends BaseAPI {
|
|
|
6270
6270
|
*/
|
|
6271
6271
|
getProfinetIOsFromFile(cell: string, inputOffset?: number, outputOffset?: number, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<string, any>>;
|
|
6272
6272
|
/**
|
|
6273
|
-
* 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
|
|
6273
|
+
* 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.
|
|
6274
6274
|
* @summary List Descriptions
|
|
6275
6275
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6276
6276
|
* @param {*} [options] Override http request option.
|
|
@@ -6279,7 +6279,7 @@ export declare class BUSInputsOutputsApi extends BaseAPI {
|
|
|
6279
6279
|
*/
|
|
6280
6280
|
listBusIODescriptions(cell: string, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<IODescription2[], any>>;
|
|
6281
6281
|
/**
|
|
6282
|
-
* 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
|
|
6282
|
+
* 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.
|
|
6283
6283
|
* @summary List PROFINET Input/Output Configuration
|
|
6284
6284
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6285
6285
|
* @param {*} [options] Override http request option.
|
|
@@ -6298,7 +6298,7 @@ export declare class BUSInputsOutputsApi extends BaseAPI {
|
|
|
6298
6298
|
*/
|
|
6299
6299
|
setBusIOValues(cell: string, iOValue: Array<IOValue>, options?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<void, any>>;
|
|
6300
6300
|
/**
|
|
6301
|
-
* Sets
|
|
6301
|
+
* 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.
|
|
6302
6302
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
6303
6303
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6304
6304
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
package/v2/api.js
CHANGED
|
@@ -1535,7 +1535,7 @@ export const BUSInputsOutputsApiAxiosParamCreator = function (configuration) {
|
|
|
1535
1535
|
};
|
|
1536
1536
|
},
|
|
1537
1537
|
/**
|
|
1538
|
-
* 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
|
|
1538
|
+
* 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.
|
|
1539
1539
|
* @summary List Descriptions
|
|
1540
1540
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1541
1541
|
* @param {*} [options] Override http request option.
|
|
@@ -1570,7 +1570,7 @@ export const BUSInputsOutputsApiAxiosParamCreator = function (configuration) {
|
|
|
1570
1570
|
};
|
|
1571
1571
|
},
|
|
1572
1572
|
/**
|
|
1573
|
-
* 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
|
|
1573
|
+
* 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.
|
|
1574
1574
|
* @summary List PROFINET Input/Output Configuration
|
|
1575
1575
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1576
1576
|
* @param {*} [options] Override http request option.
|
|
@@ -1645,7 +1645,7 @@ export const BUSInputsOutputsApiAxiosParamCreator = function (configuration) {
|
|
|
1645
1645
|
};
|
|
1646
1646
|
},
|
|
1647
1647
|
/**
|
|
1648
|
-
* Sets
|
|
1648
|
+
* 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.
|
|
1649
1649
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
1650
1650
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1651
1651
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -1820,7 +1820,7 @@ export const BUSInputsOutputsApiFp = function (configuration) {
|
|
|
1820
1820
|
return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
|
|
1821
1821
|
},
|
|
1822
1822
|
/**
|
|
1823
|
-
* 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
|
|
1823
|
+
* 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.
|
|
1824
1824
|
* @summary List Descriptions
|
|
1825
1825
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1826
1826
|
* @param {*} [options] Override http request option.
|
|
@@ -1833,7 +1833,7 @@ export const BUSInputsOutputsApiFp = function (configuration) {
|
|
|
1833
1833
|
return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
|
|
1834
1834
|
},
|
|
1835
1835
|
/**
|
|
1836
|
-
* 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
|
|
1836
|
+
* 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.
|
|
1837
1837
|
* @summary List PROFINET Input/Output Configuration
|
|
1838
1838
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1839
1839
|
* @param {*} [options] Override http request option.
|
|
@@ -1860,7 +1860,7 @@ export const BUSInputsOutputsApiFp = function (configuration) {
|
|
|
1860
1860
|
return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
|
|
1861
1861
|
},
|
|
1862
1862
|
/**
|
|
1863
|
-
* Sets
|
|
1863
|
+
* 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.
|
|
1864
1864
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
1865
1865
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1866
1866
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -1982,7 +1982,7 @@ export const BUSInputsOutputsApiFactory = function (configuration, basePath, axi
|
|
|
1982
1982
|
return localVarFp.getProfinetIOsFromFile(cell, inputOffset, outputOffset, options).then((request) => request(axios, basePath));
|
|
1983
1983
|
},
|
|
1984
1984
|
/**
|
|
1985
|
-
* 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
|
|
1985
|
+
* 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.
|
|
1986
1986
|
* @summary List Descriptions
|
|
1987
1987
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1988
1988
|
* @param {*} [options] Override http request option.
|
|
@@ -1992,7 +1992,7 @@ export const BUSInputsOutputsApiFactory = function (configuration, basePath, axi
|
|
|
1992
1992
|
return localVarFp.listBusIODescriptions(cell, options).then((request) => request(axios, basePath));
|
|
1993
1993
|
},
|
|
1994
1994
|
/**
|
|
1995
|
-
* 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
|
|
1995
|
+
* 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.
|
|
1996
1996
|
* @summary List PROFINET Input/Output Configuration
|
|
1997
1997
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
1998
1998
|
* @param {*} [options] Override http request option.
|
|
@@ -2013,7 +2013,7 @@ export const BUSInputsOutputsApiFactory = function (configuration, basePath, axi
|
|
|
2013
2013
|
return localVarFp.setBusIOValues(cell, iOValue, options).then((request) => request(axios, basePath));
|
|
2014
2014
|
},
|
|
2015
2015
|
/**
|
|
2016
|
-
* Sets
|
|
2016
|
+
* 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.
|
|
2017
2017
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
2018
2018
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
2019
2019
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -2141,7 +2141,7 @@ export class BUSInputsOutputsApi extends BaseAPI {
|
|
|
2141
2141
|
return BUSInputsOutputsApiFp(this.configuration).getProfinetIOsFromFile(cell, inputOffset, outputOffset, options).then((request) => request(this.axios, this.basePath));
|
|
2142
2142
|
}
|
|
2143
2143
|
/**
|
|
2144
|
-
* 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
|
|
2144
|
+
* 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.
|
|
2145
2145
|
* @summary List Descriptions
|
|
2146
2146
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
2147
2147
|
* @param {*} [options] Override http request option.
|
|
@@ -2152,7 +2152,7 @@ export class BUSInputsOutputsApi extends BaseAPI {
|
|
|
2152
2152
|
return BUSInputsOutputsApiFp(this.configuration).listBusIODescriptions(cell, options).then((request) => request(this.axios, this.basePath));
|
|
2153
2153
|
}
|
|
2154
2154
|
/**
|
|
2155
|
-
* 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
|
|
2155
|
+
* 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.
|
|
2156
2156
|
* @summary List PROFINET Input/Output Configuration
|
|
2157
2157
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
2158
2158
|
* @param {*} [options] Override http request option.
|
|
@@ -2175,7 +2175,7 @@ export class BUSInputsOutputsApi extends BaseAPI {
|
|
|
2175
2175
|
return BUSInputsOutputsApiFp(this.configuration).setBusIOValues(cell, iOValue, options).then((request) => request(this.axios, this.basePath));
|
|
2176
2176
|
}
|
|
2177
2177
|
/**
|
|
2178
|
-
* Sets
|
|
2178
|
+
* 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.
|
|
2179
2179
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
2180
2180
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
2181
2181
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
package/v2/api.ts
CHANGED
|
@@ -1999,7 +1999,7 @@ export interface IOIntegerValue {
|
|
|
1999
1999
|
*/
|
|
2000
2000
|
'io': string;
|
|
2001
2001
|
/**
|
|
2002
|
-
* Value of an input/output with integer representation. > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. >
|
|
2002
|
+
* 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.
|
|
2003
2003
|
* @type {string}
|
|
2004
2004
|
* @memberof IOIntegerValue
|
|
2005
2005
|
*/
|
|
@@ -2262,7 +2262,7 @@ export const InitializeMovementResponseKindEnum = {
|
|
|
2262
2262
|
export type InitializeMovementResponseKindEnum = typeof InitializeMovementResponseKindEnum[keyof typeof InitializeMovementResponseKindEnum];
|
|
2263
2263
|
|
|
2264
2264
|
/**
|
|
2265
|
-
* Value of an input/output with integer representation. > The integral value is transmitted as a string to avoid precision loss during conversion to JSON. >
|
|
2265
|
+
* 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.
|
|
2266
2266
|
* @export
|
|
2267
2267
|
* @interface IntegerValue
|
|
2268
2268
|
*/
|
|
@@ -6834,7 +6834,7 @@ export const BUSInputsOutputsApiAxiosParamCreator = function (configuration?: Co
|
|
|
6834
6834
|
};
|
|
6835
6835
|
},
|
|
6836
6836
|
/**
|
|
6837
|
-
* 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
|
|
6837
|
+
* 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.
|
|
6838
6838
|
* @summary List Descriptions
|
|
6839
6839
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6840
6840
|
* @param {*} [options] Override http request option.
|
|
@@ -6876,7 +6876,7 @@ export const BUSInputsOutputsApiAxiosParamCreator = function (configuration?: Co
|
|
|
6876
6876
|
};
|
|
6877
6877
|
},
|
|
6878
6878
|
/**
|
|
6879
|
-
* 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
|
|
6879
|
+
* 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.
|
|
6880
6880
|
* @summary List PROFINET Input/Output Configuration
|
|
6881
6881
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6882
6882
|
* @param {*} [options] Override http request option.
|
|
@@ -6966,7 +6966,7 @@ export const BUSInputsOutputsApiAxiosParamCreator = function (configuration?: Co
|
|
|
6966
6966
|
};
|
|
6967
6967
|
},
|
|
6968
6968
|
/**
|
|
6969
|
-
* Sets
|
|
6969
|
+
* 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.
|
|
6970
6970
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
6971
6971
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
6972
6972
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -7150,7 +7150,7 @@ export const BUSInputsOutputsApiFp = function(configuration?: Configuration) {
|
|
|
7150
7150
|
return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
|
|
7151
7151
|
},
|
|
7152
7152
|
/**
|
|
7153
|
-
* 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
|
|
7153
|
+
* 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.
|
|
7154
7154
|
* @summary List Descriptions
|
|
7155
7155
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7156
7156
|
* @param {*} [options] Override http request option.
|
|
@@ -7163,7 +7163,7 @@ export const BUSInputsOutputsApiFp = function(configuration?: Configuration) {
|
|
|
7163
7163
|
return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
|
|
7164
7164
|
},
|
|
7165
7165
|
/**
|
|
7166
|
-
* 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
|
|
7166
|
+
* 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.
|
|
7167
7167
|
* @summary List PROFINET Input/Output Configuration
|
|
7168
7168
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7169
7169
|
* @param {*} [options] Override http request option.
|
|
@@ -7190,7 +7190,7 @@ export const BUSInputsOutputsApiFp = function(configuration?: Configuration) {
|
|
|
7190
7190
|
return (axios, basePath) => createRequestFunction(localVarAxiosArgs, globalAxios, BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
|
|
7191
7191
|
},
|
|
7192
7192
|
/**
|
|
7193
|
-
* Sets
|
|
7193
|
+
* 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.
|
|
7194
7194
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
7195
7195
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7196
7196
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -7313,7 +7313,7 @@ export const BUSInputsOutputsApiFactory = function (configuration?: Configuratio
|
|
|
7313
7313
|
return localVarFp.getProfinetIOsFromFile(cell, inputOffset, outputOffset, options).then((request) => request(axios, basePath));
|
|
7314
7314
|
},
|
|
7315
7315
|
/**
|
|
7316
|
-
* 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
|
|
7316
|
+
* 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.
|
|
7317
7317
|
* @summary List Descriptions
|
|
7318
7318
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7319
7319
|
* @param {*} [options] Override http request option.
|
|
@@ -7323,7 +7323,7 @@ export const BUSInputsOutputsApiFactory = function (configuration?: Configuratio
|
|
|
7323
7323
|
return localVarFp.listBusIODescriptions(cell, options).then((request) => request(axios, basePath));
|
|
7324
7324
|
},
|
|
7325
7325
|
/**
|
|
7326
|
-
* 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
|
|
7326
|
+
* 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.
|
|
7327
7327
|
* @summary List PROFINET Input/Output Configuration
|
|
7328
7328
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7329
7329
|
* @param {*} [options] Override http request option.
|
|
@@ -7344,7 +7344,7 @@ export const BUSInputsOutputsApiFactory = function (configuration?: Configuratio
|
|
|
7344
7344
|
return localVarFp.setBusIOValues(cell, iOValue, options).then((request) => request(axios, basePath));
|
|
7345
7345
|
},
|
|
7346
7346
|
/**
|
|
7347
|
-
* Sets
|
|
7347
|
+
* 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.
|
|
7348
7348
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
7349
7349
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7350
7350
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|
|
@@ -7482,7 +7482,7 @@ export class BUSInputsOutputsApi extends BaseAPI {
|
|
|
7482
7482
|
}
|
|
7483
7483
|
|
|
7484
7484
|
/**
|
|
7485
|
-
* 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
|
|
7485
|
+
* 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.
|
|
7486
7486
|
* @summary List Descriptions
|
|
7487
7487
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7488
7488
|
* @param {*} [options] Override http request option.
|
|
@@ -7494,7 +7494,7 @@ export class BUSInputsOutputsApi extends BaseAPI {
|
|
|
7494
7494
|
}
|
|
7495
7495
|
|
|
7496
7496
|
/**
|
|
7497
|
-
* 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
|
|
7497
|
+
* 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.
|
|
7498
7498
|
* @summary List PROFINET Input/Output Configuration
|
|
7499
7499
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7500
7500
|
* @param {*} [options] Override http request option.
|
|
@@ -7519,7 +7519,7 @@ export class BUSInputsOutputsApi extends BaseAPI {
|
|
|
7519
7519
|
}
|
|
7520
7520
|
|
|
7521
7521
|
/**
|
|
7522
|
-
* Sets
|
|
7522
|
+
* 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.
|
|
7523
7523
|
* @summary Set PROFINET Inputs/Outputs from File
|
|
7524
7524
|
* @param {string} cell Unique identifier addressing a cell in all API calls.
|
|
7525
7525
|
* @param {ProfinetInputOutputConfig} profinetInputOutputConfig
|