Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Deck of Cards
id0002
Card
labelDriver Info

Driver Information

Driver Interface Type UDPDriver Class TypeOutput
UTC Driver (question) NoInput / OutputInputExecutableDrvOpcServerHandler.exe
Related Pages
Content by Label
showLabelsfalse
showSpacefalse
excerptTypesimple
cqllabel = "dm-0405"
Table of Contents
Table of Contents
maxLevel3
stylesquare
typeflat
separatorpipe

Show If
groupqps-staff, confluence-driver_format_access
Card
labelFormat

Include Page
DM-0405 - Format
DM-0405 - Format

Card
labelDecoding Notes

Decoding Notes

 This driver only supports JSON input, any other input is discarded.

Card
labelSystem Interfacing

Interfacing Notes

By default this driver listens to 127.0.0.1 : 51234. (Port number can be changed in the registry.)

If remote access is needed the host must allow DCOM access: run (WIN+R) DCOMcnfg

Make sure to access and launch allow Local and Remote Access to ALL groups.

Also check Defaults:

 

*Server plugin might not show in this list. Will only be shown if driver is online.

 

 

Also add these Firewall rules:

Port:  TCP 135  "DCOM inbound"

Program

  • C:\Windows\System32\OPCEnum.exe <OR> C:\Windows\SysWOW64\OPCEnum.exe
  • <Qinsy installation folder>\OpcClassicServer.exe

 

Card
labelQINSy Config

QINSy Configuration

To configure the OPC plugin with QINSy the driver must be added to the template and a Generic Driver .xml must be created.

Database Setup

The driver can be found under Output Systems -> OPC Server Plugin. The OPC Plugin is designed to work with the Generic Driver output and by default this driver listens to 127.0.0.1 : 51234. (Port number can be changed in the registry.)


Subsequently you have to add a Network - Generic Output driver with default settings 127.0.0.1 : 51234.

Generic Layout editor

To receive data with OPC a output driver .xml should be created in the Generic Layout Editor. It is important that the driver is outputting in JSON format so it can be read into a OPC server:

Info

To select data which has to be outputted by the Generic Driver consult out knowledge base Generic Layout Editor

 

Card
labelQINSy Online

QINSy Online

In online mode QINSy will open a Generic Output to UDP 51234 window, in here the .xml should be added:

The saved .xml will automatically be recognized when saved in the directory C:\Users\Public\Documents\QPS\QINSy\Drivers\Definitions\Output. If you have multiple .xml files select the correct one and go to the next menu:

In the Output Message Wizard you can change the output settings. Check if the Output Type is still JSON and select finish:

In the main Generic Output window the .xml file is shown with the the data which is outputted by the driver:

Card
labelAdditional Info

Additional Information

Driver can be started without QINSy:

  • Open a Cmd with admin rights
  • Go to QINSy install folder ( cd "<path>")
  • Run DrvOpcServerHandler.exe - standalone
Panel

Closing the Console without completing the process can result in unwanted behavior.

Card
labelRegistry Options

Registry Options

Adjusting the port the driver listens to can be done by changing the registry:

Panel
titleRegistry Key

HKEY_CURRENT_USER\SOFTWARE\QPS\QINSy\8.0\Utilities\OPC Server Plugin\Settings

 

  • Version 1 or higher
    • Data Quality Timeout'. (int) (milliseconds)
      Changing this value will change the time it will take for the driver to consider the received output as bad quality. (As in not updating.)

    • UDP Port'. (int) port number to listen to incoming data (default: 51234)

  • Version 3 or higher
    • \Wait For Config Attempts Configuration (int) (seconds) number of seconds the plugin will wait for configuration. After the time expires the plugin will use the last configuration