OPC

OPC Node/IP Address: The OPCDA PC Name or IP address.  If the PortIO is connected to more than one OPCDA server, separate them with “;”.  If set up to have backup/fail over, use a “|” to separate them.

OPC Prog ID: The OPCDA ProgID, meaning the name of the OPCDA server.  If the PortIO is connected to more than one OPCDA server, separate them with “;”.  If set up to have backup/fail over, use a “|” to separate them. Use the “Browse for OPCs” button to find it if possible.

Browse for OPCs: Launches the Browse for OPCs window to search for and test connections to OPCDA servers.

Test Connect: Tests the connection to listed OPCDA servers.

Asynchronous Updates: If checked, tags are registered with OPC server and requested to update on their MaxFreq rate. OPC sends values as they change in the OPCDA cache. If unchecked, PortIO will read data synchronously: tag are registered with OPC server and PortIO polls the OPCDA server for values based on the tag’s MaxFreq or update rate.

Use Alternate Name: Use the tag’s LoopNum or OPCTagName from the database to add to the OPCDA server.  See sections on Tag Editor.

Global OPC Dead Band Percent: Global deadband percent to use when creating each group of tags within the OPCDA Server.

Delete Bad Tag File on Restart or Re-Initialize: When PortIO connects to an OPCDA server, it keeps track of the number of bad tags in its list, which are tags the OPCDA server did not allow to be added.  It writes those tags to a file. On restart, it will ignore any tags in that list and not try to add it to the OPCDA server to collect data for it.  This setting, if checked, would delete that file on each restart or re-initialization, therefore making it retry or re-add those tags to the OPCDA server.

Re-Test Bad Tags on Retry Based on Bad Tag Count: If the number of allowed bad tags is exceeded (set in Max Bad tags), PortIO will disconnect from the OPCDA server, wait a number of seconds (set in Wait time between tries) and connect again, add tags and start data collection.  If checked, PortIO will re-test the bad tags and try to add them.

Wait Time Between Tries: The amount of time to wait before re-connecting based on exceeding the Max Bad Tags.

Retry Bad Tags Count: Number of times to retry bad tags based on exceeding the Max Bad Tags.

Max Bad Tags: Maximum number of allowable bad tags before triggering a disconnect and wait.

Re-Check Bad Tags on a Cycle: If checked, the PortIO will re-check any of the bad tags without completely disconnecting from the OPCDA server. For example, if PortIO is started and 5 tags are marked as bad, or unable to be added to the OPCDA server, this setting will make it try to re-add those tags to the OPCDA server a number of times to see if they can be properly registered later.

Wait Time Between Recheck: The amount of time before retesting all tags marked bad, in minutes.

Number of Times to Recheck: The number of times to recheck bad tags.

Calc Hourly Averages: Obsolete. Replaced with PARCaggregate server.

Calc Daily Averages: Obsolete. Replaced with PARCaggregate server.