Configuring an OPC-DA collector

the opc da collector in factry historian allows you to connect to an opc da server and collect process values once configured, the data is historized and made available for further processing in factry historian, and for trending, reporting, and analysis prerequisites permissions in factry historian to manage collectors see privileges docid\ k2nnyecuxqqsiuclmpfkh an installed opc da collector if you have not done so already, first installing a collector docid\ iv4 sd56tdxcqkrkcj4kv a working opc da connection if you are running into issues or setting this up for the first time, follow our guide to testing an opc da connection docid\ v3uermlrq4s9uxj3xd 91 a configured creating a time series database connection docid\ sq5uvlchyg7umi930nyml to write the collected data to configure the collector after installing the collector, you should be able to see that the collector is in an initial state initial state and is actively running this means that the collector has established a connection to factry historian and is awaiting further configuration to configure the collector, select it from the collectors overview in factry historian and click the edit button configure the following fields progid this is the programmatic identifier of the opc da server to connect to the progid must exactly match the one exposed by your opc da server if you are unsure which one to use, check the server’s id in your opc da server configuration or discovery tool for example graybox simulator 1 matrikon opc simulation 1 if you’re having trouble connecting to the opc da endpoint, see this page testing an opc da connection docid\ v3uermlrq4s9uxj3xd 91 nodes this is a comma separated list of the nodes of the opc da server for single node servers, the default value of localhost should suffice for setups involving multiple servers with the same progid, this setting is used to specify which node or nodes to connect to collectionsource the collection source controls where data is read from cache fast read, returns data already stored on the opc da server device slower read, fetches the most up to date values from the underlying automation devices example then, click save expected outcome after you have configured the collector, a green start button will appear in the top right corner of the collector page click start to launch the collector if the connection is successful, you should observe the collector status change to collecting collecting adding measurements follow the guide on adding measurements to an opc da collector docid\ gp6 uw0fijgfgm6tbuxve best practices timestamps make sure all clocks (collector, server, devices) are synchronized, for example using ntp