OPC-DA collector

basic settings the collector settings are used by the collector to connect to the opc da server progid description the programmatic identifier of the opc da server required yes example matrikon opc simulation 1 node description the node of the opc da server required yes default localhost this setting was called nodes and accepted a comma separated list before collector version 3 0 0, which removed support for multiple opc da servers a collector upgraded from an earlier version keeps only the first node of the old list collectionsource description the source from which to collect data required yes options cache | device default cache advanced settings escapenonprintablecharacters description when enabled, every string value read from the opc da server is quoted and its non printable characters are escaped before it is stored turn this off to store the raw string required no default true heartbeatinterval description the interval in milliseconds of the liveness probe that decides when the connection is declared dead and the collector reconnects this is the mechanism behind the opc da server unavailable health message required no default 10000 minimum 5000 measurement settings the measurement settings reflect the configuration possibilities for mapping a measurement to an opc da tag itemid description fully qualified opc da item name required yes example factry saw 1 collectiontype description the way this measurement should be collected from the opc da server required yes default polled options polled | monitored checkout the data collection methods docid\ kp91 lgm4jw diqr0a6z2 section for more information collectioninterval description the interval in milliseconds at which this measurement should be collected required yes default 5000 collectionoffset description the offset in milliseconds, relative to the 0th second of a minute, at which this measurement should be collected only relevant for polled measurements required yes default 0 data collection methods the opc da collector has 2 methods to collect measurement data, which are referred to as the collection type of a measurement polling polled measurements are read every x milliseconds (minimum of 1000ms), which is the collection interval this data collection method should be used for measurements for which the value changes regularly over time configure the interval depending on how frequent you want to collect data points for this measurement monitoring monitored measurements collect data on every change of the measurements value the measurement is polled at its own collection interval, raised to the minimum of 1000ms if configured lower, and each sample is compared against the last stored value; unchanged samples are dropped a change that happens between two polls is therefore not seen, so keep the collection interval short enough for the changes you care about typically, monitored measurements are configured for boolean or string data types that indicate an equipments state, f e for a valve that opens and/or closes only a few times per hour collector health opc da specific collector health messages see here docid\ cuxtvhahq2yyjjjwatdh8 for all generic collector health messages you can find the collector health and the collector health history in the detail view on the right, when selecting a collector in the historian admin webpage error connecting to opc da server the collector failed to connect to the opc da server this indicates that a collector setting hasn’t been configured correctly or that the opc da server isn’t reachable opc da server unavailable the opc da client lost connection with the opc da server limitations it is currently not possible to read arrays from the opc da server