Overview of CygNet Data Collector

The Historian CygNet Data Collector gathers data samples from a CygNet Server and stores the corresponding data entries into the Historian Server. This collector supports collecting of Analog, Digital and String type of data from CygNet Server. This collector supports a distributed model, where the CygNet Server, the Collector, and Historian 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.

The Cygnet collector consists of System API as well as the Collector Toolkit components.

The Cygnet collector uses unsolicited collection, whereby changes to the CygNet tags are detected, and are forwarded to the Historian server. The collector is intended to duplicate raw samples from the CygNet into the Historian data archive.

At the time of collector browse, CygNet-Collector connects with CygNet using CxScript64.dll API component and queries the CygNet FAC (Facility Service) and PNT (Point Service) services associated with the CVS (Current Value Service).

The CygNet Point Value is mapped to the GE Historian server as a Collector tag for data collection. Cygnet collector stores VHS (Value History Service) points UDCs(Uniform Data Codes) as Tag source address.

Refer to the following topics for more information:

• Summary of Cygnet collector Features
• Tag Attributes Available on a Browse (Cygnet collector)
• Selecting Data Types
• The Configuration Section for Cygnet collectors
• Collector Specific Configuration for Cygnet collector
• Hierarchical Cygnet collector Browsing
• Manual Recalculation and Bad Offline Values
• Troubleshooting the Cygnet collector