Using OpcCmd Utility as OPC A&E Client: Difference between revisions
From OPC Labs Knowledge Base
Line 16: | Line 16: | ||
<pre> | <pre> | ||
OpcCmd -i | OpcCmd -i | ||
aeclient -- | aeclient --property InstanceParameters.EnableNativeClient=[Boolean]false | ||
subscribeEvents subscribeEvents OPCLabs.KitEventServer.2 | subscribeEvents subscribeEvents OPCLabs.KitEventServer.2 | ||
</pre> | </pre> |
Revision as of 19:09, 2 February 2021
For general information about the OpcCmd tool, see Category:OpcCmd Utility.
Commands, Arguments and Options
Command: aeClient subscribeEvents
OpcCmd -i aeclient subscribeEvents subscribeEvents OPCLabs.KitEventServer.2
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 aeclient --property InstanceParameters.EnableNativeClient=[Boolean]false subscribeEvents subscribeEvents OPCLabs.KitEventServer.2
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.AlarmsAndEvents.EasyAEClient": {
"InstanceParameters": {
"EnableNativeClient": false
}
}
}