Configuration of iFIX Data Collector-Specific Fields
Adding a Historian tag with the selected database block source address allows you to collect the history of the collector's events per minute. This is very useful for troubleshooting and optimization analysis. The following table outlines the iFIX Data Collector-specific fields.
Field | Description |
---|---|
Rate Output Address |
NTF in the iFIX database into which the collector writes the current value of the events/minute output, letting an operator or the HMI/SCADA application know the performance of the collector. Use an iFIX tag for the output address. Enter the address as This value displays the same statistic as the Report Rate field of the iFIX Data Collector in the System Statistics screen of the Historian Administrator. |
Status Output Address |
NTF in the iFIX database into which the collector writes the current value of the collector status (for example, running) output, letting an operator or the HMI/SCADA application know the current status of the collector. This address should be connected to a writable text field of at least 8 characters. This value is only updated upon a change in status of the collector Use an iFIX tag for the output address. Enter the address as The text string usually displays either |
Heartbeat Output Address |
Address in the source database into which the collector writes the heartbeat signal output. This address should be connected to a writable analog field. Use an iFIX tag for the output address. Enter the address as The iFIX Data Collector writes a value of 1 to this location every 60 seconds while it is running. Many applications use a heartbeat to indicate when something has stopped. For example, you could program the iFIX database to generate an alarm if the heartbeat output address is not written to once every 60 seconds notifying you that the iFIX Data Collector has stopped. |
Adding a Historian tag with the selected database block source address allows you to collect the history of the collector's events per minute. This is very useful for troubleshooting and optimization analysis.