Using OpcCmd Utility as OPC UA Server: Difference between revisions
From OPC Labs Knowledge Base
| Line 10: | Line 10: | ||
== Command: uaServer addMesh == | == Command: uaServer addMesh == | ||
This command adds nodes to the OPC UA server address space mesh. You need to specify the mesh name, and optionally a mesh-specific parameter. Currently, only one mesh is available, named ''' | This command adds nodes to the OPC UA server address space mesh. You need to specify the mesh name, and optionally a mesh-specific parameter. Currently, only one mesh is available, named '''PerformanceNodes'''. The optional parameter is an integer specifying the count of shared counter nodes (defaults to 10000). | ||
The mesh(es) need to be added before you start the server. | The mesh(es) need to be added before you start the server. | ||
| Line 16: | Line 16: | ||
Example: | Example: | ||
<code>uaServer addMesh | <code>uaServer addMesh PerformanceNodes 20000</code> | ||
Revision as of 21:41, 6 March 2025
For general information about the OpcCmd tool, see Category:OpcCmd Utility.
Commands, Arguments and Options
Command: uaServer start
This command starts an OPC UA server with pre-defined content (data variables with various behavior and data types under the standard Objects folder). By default, it opens its endpoint on "opc.tcp://localhost:48040/".
Command: uaServer addMesh
This command adds nodes to the OPC UA server address space mesh. You need to specify the mesh name, and optionally a mesh-specific parameter. Currently, only one mesh is available, named PerformanceNodes. The optional parameter is an integer specifying the count of shared counter nodes (defaults to 10000).
The mesh(es) need to be added before you start the server.
Example:
uaServer addMesh PerformanceNodes 20000
