Using OpcCmd Utility as OPC DA Client: Difference between revisions
From OPC Labs Knowledge Base
No edit summary |
|||
Line 12: | Line 12: | ||
</pre> | </pre> | ||
= Using OPC NET API implementation = | = Tips and Tricks = | ||
== Using OPC NET API implementation == | |||
If you want to use the OPC NET API implementation instead of the native implementation (in OpcCmd for .NET Framework), you can do it interactively as in the following example: | If you want to use the OPC NET API implementation instead of the native implementation (in OpcCmd for .NET Framework), you can do it interactively as in the following example: | ||
<pre> | <pre> | ||
Line 29: | Line 30: | ||
} | } | ||
</syntaxhighlight> | </syntaxhighlight> | ||
== OPC DA Optimizer settings == | |||
To turn off request merging: <code>daClient plugins configuration part DAOptimizerPluginParameters set EnableRequestMerging [Boolean]False</code> |
Revision as of 12:32, 3 February 2021
For general information about the OpcCmd tool, see Category:OpcCmd Utility.
Commands, Arguments and Options
Command: daClient subscribeItem
OpcCmd -i daClient subscribeItem OPCLabs.KitServer.2 Demo.Ramp 200
Tips and Tricks
Using OPC NET API implementation
If you want to use the OPC NET API implementation instead of the native implementation (in OpcCmd for .NET Framework), you can do it interactively as in the following example:
OpcCmd -i daClient --property InstanceParameters.EnableNativeClient=[Boolean]false subscribeItem OPCLabs.KitServer.2 Demo.Ramp 200
If you want to use such setting permanently, you can modify one of the OpcCmd Built-in Component Configuration files (JSON, INI or XML). For example, with the JSON format, put the following into the appsettings.json or appsettings.production.json file:
{
"OpcLabs.EasyOpc.DataAccess.EasyDAClient": {
"InstanceParameters": {
"EnableNativeClient": false
}
}
}
OPC DA Optimizer settings
To turn off request merging: daClient plugins configuration part DAOptimizerPluginParameters set EnableRequestMerging [Boolean]False