Difference between revisions of "QuickOPC: How to enable extended tracing"

From OPC Labs Knowledge Base
Jump to navigation Jump to search
 
(2 intermediate revisions by the same user not shown)
Line 1: Line 1:
 
[[Category:How to]] [[Category:Instrumentation]] [[Category:OPC UA]] [[Category:Troubleshooting]]
 
[[Category:How to]] [[Category:Instrumentation]] [[Category:OPC UA]] [[Category:Troubleshooting]]
 
= Enabling the extended tracing =
 
= Enabling the extended tracing =
For advanced troubleshooting, it is sometimes necessary to obtain information about QuickOPC-UA internal status and activities. This can be done by enabling extended tracing, as described in this application note.
+
For advanced troubleshooting, it is sometimes necessary to obtain information about QuickOPC internal status and activities. This can be done by enabling extended tracing, as described in this application note. Most of the tracing is for OPC UA, but there is some tracing for other OPC specifications as well.
  
 
The logging is enabled by various .NET trace switches, and settings in configuration file sections. Unless you are able to observe the output in the debugger or using a special tool, you also need to direct the trace to a proper listener, using the standard means provided by .NET tracing facility. It is up to you how you enable the switches or configure the listener(s). Typically, it is done using the application configuration file, with the advantage that it can be done without rebuilding the application.
 
The logging is enabled by various .NET trace switches, and settings in configuration file sections. Unless you are able to observe the output in the debugger or using a special tool, you also need to direct the trace to a proper listener, using the standard means provided by .NET tracing facility. It is up to you how you enable the switches or configure the listener(s). Typically, it is done using the application configuration file, with the advantage that it can be done without rebuilding the application.
  
The example below shows the application configuration file with the extended tracing enabled.  
+
The example below shows the application configuration file with common parts of the extended tracing enabled.  
  
 
<syntaxhighlight lang="xml" line highlight="3-9,13-35">
 
<syntaxhighlight lang="xml" line highlight="3-9,13-35">
Line 65: Line 65:
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
! Name !! Description
+
! Name !! Description !! Type !! Default value
 
|-
 
|-
| OpcLabs.Licensing.Invoke || License invocation.
+
| OpcLabs.EasyOpcClassicRaw.OCKClient.BrowseNodes || Browsing for OPC DA nodes. || BooleanSwitch || 0<ref name="Debug_1">1 in Debug configurations</ref>
 
|-
 
|-
| OpcLabs.Licensing.Verify  || License verification.
+
| OpcLabs.Licensing.Invoke || License invocation. || BooleanSwitch || 0<ref name="Debug_1"/>
 +
|-
 +
| OpcLabs.Licensing.Verify  || License verification. || BooleanSwitch || 0<ref name="Debug_1"/>
 
|}
 
|}
  

Latest revision as of 09:39, 20 March 2020

Enabling the extended tracing

For advanced troubleshooting, it is sometimes necessary to obtain information about QuickOPC internal status and activities. This can be done by enabling extended tracing, as described in this application note. Most of the tracing is for OPC UA, but there is some tracing for other OPC specifications as well.

The logging is enabled by various .NET trace switches, and settings in configuration file sections. Unless you are able to observe the output in the debugger or using a special tool, you also need to direct the trace to a proper listener, using the standard means provided by .NET tracing facility. It is up to you how you enable the switches or configure the listener(s). Typically, it is done using the application configuration file, with the advantage that it can be done without rebuilding the application.

The example below shows the application configuration file with common parts of the extended tracing enabled.

 1  <?xml version="1.0"?>
 2  <configuration>
 3    <configSections>
 4      <section
 5        name="OpcLabs.EasyOpc.UA.Toolkit.SdkTrace"
 6        type="OpcLabs.EasyOpc.UA.Toolkit.SdkTraceSection,OpcLabs.EasyOpcUA" />
 7    </configSections>
 8    <OpcLabs.EasyOpc.UA.Toolkit.SdkTrace traceOutput="3" >
 9    </OpcLabs.EasyOpc.UA.Toolkit.SdkTrace>
10    <startup>
11      <supportedRuntime version="v4.0" sku=".NETFramework,Version=v4.5"/>
12    </startup>
13    <system.diagnostics>
14      <switches>
15        <add name="EasyUAClientEngineBase" value="Verbose" />
16        <add name="NetSdkEasyUAClient" value="Verbose" />
17        <add name="OpcLabs.Boxing.DisplayProgress" value="1" />
18        <add name="OpcLabs.CallDiagnostics.Display.CallPort" value="1" />
19        <add name="OpcLabs.CallDiagnostics.Display.Enabled" value="1" />
20        <add name="OpcLabs.CallDiagnostics.Display.EnterPort" value="1" />
21        <add name="OpcLabs.CallDiagnostics.Display.ExitPort" value="1" />
22        <add name="OpcLabs.CallDiagnostics.Display.LeavePort" value="1" />
23        <add name="OpcLabs.CallDiagnostics.Display.TickCount" value="1" />
24        <add name="OpcLabs.Configuration.DisplayGet" value="1" />
25        <add name="OpcLabs.EasyOpc.UA.Toolkit.Sdk.DisplayCalls" value="1" />
26        <add name="OpcLabs.EasyOpc.UA.Toolkit.SdkCallback.DisplayCalls" value="1" />
27        <add name="OpcLabs.EasyOpc.UA.Toolkit.SdkEnvironment.DisplayCalls" value="1" />
28        <add name="OpcLabs.EasyOpc.UA.Toolkit.SdkMethod.DisplayCalls" value="1" />
29        <add name="OpcLabs.EasyOpc.UA.Toolkit.SdkTarget.DisplayCalls" value="1" />
30        <add name="OpcLabs.EventTracing.TraceLogEntries" value="1" />
31        <add name="OpcLabs.Reflection.AssemblyLoading" value="1" />
32        <add name="UAClientEngineBase" value="Verbose" />
33        <add name="UAEngineBase" value="Verbose" />
34        <add name="UASmartClientEngine" value="Verbose" />
35      </switches>
36    </system.diagnostics>
37  </configuration>

Note: In QuickOPC versions prior to 2019.1, use EasyUAEngineBase instead of EasyUAClientEngineBase, and UASmartEngine instead of UASmartClientEngine.

The relevant parts of the file are highlighted. Specifically, following information will be contained in the traces:

  • All trace information from inside OPC UA .NET Stack and SDK.
  • Calls to and from OPC UA .NET Stack and SDK.
  • Log entries generated by the component.

Please refer to Microsoft documentation for details on the application configuration files, the diagnostic switches, the trace listeners, and so on. The application configuration file needs to be named the same as your application, with an added “.config” extension, and placed alongside the application. For example, for “MyApp.exe”, the configuration file is “MyApp.exe.config”. Note that the development tools sometimes provide “shortcuts” for the naming and placing procedure. For example, Visual Studio C# projects contain an app.config file, which becomes the application configuration file automatically – Visual Studio copies it to the output folder and renames it appropriately.

Note2-icon.png

Note: Under COM platform, QuickOPC objects get loaded into the process of the application that creates and calls them. You therefore need to create or modify the configuration file for the application itself (as if it were a .NET application). In hosted environments, such as ASP.NET, the name and location of the configuration file may be different as well.

By default, the traces are directed to the Windows debug output, which you can observe e.g. when you run the program under a debugger, or it can be viewed and captured using specialized tools such Sysinternals’ DebugView (http://technet.microsoft.com/en-us/sysinternals/bb896647.aspx ).

Trace Switches

Following table lists some selected trace switches and their meaning.

Name Description Type Default value
OpcLabs.EasyOpcClassicRaw.OCKClient.BrowseNodes Browsing for OPC DA nodes. BooleanSwitch 0[1]
OpcLabs.Licensing.Invoke License invocation. BooleanSwitch 0[1]
OpcLabs.Licensing.Verify License verification. BooleanSwitch 0[1]

Trace Listener Configuration

If you do not want to use the default debug trace configuration (directing the traces to the debug output), you can configure the trace listener(s) in various ways. Please refer to Microsoft documentation for details. For example, to store the output into a comma-delimited file “Trace.csv” (in the same folder as the application), use the following configuration part:

 1  <system.diagnostics>
 2      <trace autoflush="true" indentsize="4">
 3        <listeners>
 4          <add name="myListener" 
 5               type="System.Diagnostics.DelimitedListTraceListener"
 6               traceOutputOptions="DateTime, ProcessId, ThreadId"
 7               delimiter=","
 8               initializeData="Trace.csv" />
 9          <remove name="Default" />
10        </listeners>
11      </trace>
12    </system.diagnostics>
  1. 1.0 1.1 1.2 1 in Debug configurations