eDNA

.NET AGENT

Overview

The eDNA connector enables Seeq to access data from eDNA Enterprise Historian, which has been associated with Aveva, Schneider Electric, Wonderware, InStep and Invensys at various times.

Prerequisites

The eDNA connector does not ship with Seeq. Please contact Seeq Support to obtain the connector.

Ensure you install the eDNA client on the machine with the remote agent.
Shut down the Seeq Server.
Make sure that you have a DNASYS.ini file that is located in C:\ProgramData\InStep. The DNASYS.ini should have the IP address and port of your eDNA server, as well as any proxies. Consult the eDNA API Software Development Kit documentation for more information on the DNASYS.ini. It should look something like this:
CODE
```
[CLIENT]
USE_REGIONAL_SETTINGS=1
SHOW_ID_SELECTOR=0
IP_ADDRESS=xxx.xxx.xxx.xxx

[PROXY]
IP_ADDRESS=xxx.xxx.xxx.xxx
PORT=7007

[SVCDIR]
SVCDIR_01=xxx.xxx.xxx.xxx
PORT=6321
```
Extract the contents of the eDNA Connector zip file to C:\ProgramData\Seeq\data\plugins\connectors (if you have changed the location of the Seeq data folder, the path will be slightly different for you). There should be a C:\ProgramData\Seeq\data\plugins\connectors\eDNA folder now.
Start Seeq Server and ensure that it is running.
A configuration file C:\ProgramData\Seeq\data\configuration\link\Aveva eDNA Connector.json should be created after Seeq starts up. Edit this file with a text editor, set Enabled to true, and save and exit the editor.
Seeq will now connect to eDNA and indexing should begin.

Configuration

This is an example configuration template that is displayed in the Additional Configuration box that appears when you click Configure for an existing datasource (or if a new datasource is being created, in the Create new datasource connection modal that appears after clicking Add Datasource) on the Datasources administration page.

CODE

{
    "RedundancyString": null,
    "ErrorStatus": null,
}

eDNA Additional Configuration

Property Name	Default Value	Data Type	Description
`RedundancyString`	null	String	eDNA has an option for redundant services which will result in duplicate points. Redundant services typically have naming conventions to be easily identifiable. This configuration option removes those redundant services based on the identifier specified.
`ErrorStatus`	null	A List of Strings	A list of error statuses that are used to exclude data points from appearing in Seeq.

Note that signals in Seeq will use the eDNA point "Extended Description" field as the Name property in Seeq; the eDNA point ID and description will be concatenated for the Description property.

Known Issues

There are no known issues for the eDNA connector. Please report any issues you find to our support portal.

Troubleshooting

If you encounter a -1 return in the logs that mention “unknown error,” more than likely, the EzDNA client has not been installed on the machine. This client must be installed to register the appropriate libraries in the system. Additionally, within the connector files, ensure EzDnaApiNet64.dll and EzDnaApi64.dll are present.

If you cannot install the client for any reason you will need to register the assembly manually.

Open a command prompt as admin
C:\Windows\SysWOW64\REGSVR32 "C:\{SeeqDataFolder}\Seeq.Link.Connector.eDNA\EzDnaApi64.dll"

If you are running into other issues with connecting to or access data from eDNA, view our guide for troubleshooting datasource issues.

Performance considerations

The eDNA connector does not have any special performance considerations. View our guide on optimizing datasource performance for general guidance.