Using OpcCmd Utility as OPC UA Server: Difference between revisions

From OPC Labs Knowledge Base
Line 7: Line 7:


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/".
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/".
=== Sub-commands ===
By default, the server runs until the you press {{Style=keyboard|X}} on the keyboard. Use the '''!wait''' sub-command to specify a finite duration.


== Command: uaServer addMesh ==
== Command: uaServer addMesh ==

Revision as of 09:40, 25 August 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/".

Sub-commands

By default, the server runs until the you press X on the keyboard. Use the !wait sub-command to specify a finite duration.

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
start