Overview of the CygNet Collector

The CygNet collector collects data from a CygNet server and stores it in the Historian server.

Topology: The CygNet collector supports a distributed model, where the CygNet server, the collector, and the Historian server are installed on different machines. Typically, however, the collector is installed on the same computer as the CygNet server and sends data to a remote Historian server.

Features:
  • You can browse the source for tags and their attributes on a CygNet server that supports browsing.
  • Both the polled as well as unsolicited data collection are supported. During unsolicited data collection, when changes to the CygNet tags are detected, they are forwarded to the Historian server. The collector duplicates raw samples from the CygNet server into the Historian data archive.
  • The supported timestamp resolution is 100ms.
  • The collector support manual recalculation of tag data.
  • Floating point, integer, and string data are supported.
Components:
  • System API
  • Collector Toolkit
How it works:
  1. When you browse for tags, the CygNet collector connects with CygNet using the CxScript64.dll API.
  2. The collector queries the CygNet faculty service and point service associated with the Current Value service (CVS).
  3. The CygNet point value is mapped to the Historian server as a collector tag.
  4. The collector stores the Value Historian service (VHS) and points Uniform Data Codes as the tag source address.
  5. Once all the CygNet points associated with the selected CVS/VHS have been mapped with the Historian tags, the collector begins querying from VHS to collect data from CygNet.

Supported data types:

The CygNet collector collects analog, digital, and string types of data. The following table provides the data types recommended for use with Historian.
CygNet Data Types Recommended Data Type in Historian
Analog Float
Enumeration Integer
Digital Boolean
String Variable String
Supported tag attributes:
  • Tagname
  • Source Address
  • Engineering Unit Description
  • Data Type
  • Hi Engineering Units and Lo Engineering Units (applicable only to analog and discrete data types)
Note: Although you can browse and query some of these attributes, they are not displayed in the browse interface. These attributes are used when you add a tag, but are not visible to you, regardless of attributes available from the server.