Kit Server: Items for volume testing: Difference between revisions

From OPC Labs Knowledge Base
No edit summary
No edit summary
Line 6: Line 6:
<code>Simulation.Incrementing.Copy_''i''.Phase_''j''</code>
<code>Simulation.Incrementing.Copy_''i''.Phase_''j''</code>


where ''i'' is a number between 1 and 2000, and ''j'' is a number between 1 and 100.
where ''i'' is a number between 1 and 2000, and ''j'' is a number between 1 and 100. The total number of available incrementing items is therefore 200000.


For example, one of the simulation items may have following Item ID:
For example, one of the simulation items may have following Item ID:

Revision as of 10:48, 15 April 2018

The OPC DA "Kit Server" that is supplied with QuickOPC (ProgID "OPCLabs.KitServer.2") provides a number of simulation items that can be used for volume testing. The items contains continuously changing values, so that not only reads, but also subscriptions can be tested.

Each such items has following Item ID:

Simulation.Incrementing.Copy_i.Phase_j

where i is a number between 1 and 2000, and j is a number between 1 and 100. The total number of available incrementing items is therefore 200000.

For example, one of the simulation items may have following Item ID:

Simulation.Incrementing.Copy_1967.Phase_42

These simulation items are always present in the server and are accessible by their Item IDs, but by default, they are not visible in the address space of the OPC server (when browsing it). If you want to be able to browse for these items, you can configure the OPC Kit Server to show them in the address space by making a registry change.

To make the incrementing branches visible in (32-bit) OPC Kit Server, create or modify the IncrementingBranchesVisible DWORD value in registry under the following registry key to contain "1".

  • On 32-bit Windows or when running 32-bit registry editor: HKEY_LOCAL_MACHINE\SOFTWARE\OPC Labs\Kit Server
  • On 64-bit Windows when running 64-bit registry editor: HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\OPC Labs\Kit Server

If the OPC Kit Server is running, it needs to be restarted in order to pick up this configuration change. If it is running as a Service (installation default), you can restart it from the Service Manager in Windows.