The interface has the following functions and configuration options.
Set all values to zero when the connection to a database is lost
If this option is enabled, all signal values in the modules are set to zero as soon as the connection is lost. ibaPDA regularly attempts to restore the database connection until it either succeeds or the acquisition stops.
If this option is disabled, ibaPDA keeps the last values in memory when the connection is lost.
Note |
|
|---|---|
|
It may take some time until the signal values are set to zero. A longer response time of a database, even in the range of several seconds, is not necessarily an indication of an interrupted connection. |
|
Start acquisition even if a database is not accessible
If this option is enabled, the acquisition starts even if one or more of the configured databases are not accessible. A warning is prompted in the validation dialog, not an error. If the system was started without a connection to a database, ibaPDA periodically tries to connect to the database.
DB connections
This area displays the configured database connections. Each database connection is clearly identified with an ID number, the database system and the connected database. You can use the buttons to create, edit and delete database connections. The coming chapters describe the configuration of the database connections.
<Open log file>
If connections to controllers have been established, all connection specific actions
are recorded in a text file. Using this button, you can open and check this file.
In the file system on the hard disk, you find the log files of this interface in the
path …\ProgramData\iba\ibaPDA\Log. The file name of the current log file is InterfaceLog.txt; the name of the archived log files is InterfaceLog_yyyy_mm_dd_hh_mm_ss.txt.
<Reset statistics>
Click this button to reset the calculated times and error counters in the table to 0.
Table with connection statistics
The bottom area of the dialog contains a table for the purpose of connection diagnostics. Statistical information, such as counter values and times, are displayed for each configured SQL module.
Note |
|
|---|---|
|
Due to the nature of relational databases, error counters may increment more slowly than success counters. Note this when diagnosing connection problems. |
|
|
Column |
Meaning |
|---|---|
|
Module |
Name of the SQL module (query and command modules) |
|
Statements |
Processed: Number of executed SQL statements Error: Number of SQL statements where failures occurred. Either SQL statements failed (database responds with error) or statements could not be executed, because the database was not accessible and the buffer was full. An empty result for a statement is not considered an error. |
|
Rows |
Max: The highest number of rows that was returned since the last start of acquisition or the last reset of the counter after a statement. Last: The number of rows that was returned after the last statement. |
|
Response time |
Time values for the duration between the execution of the SQL statement and the confirmation of the execution by the database. Min, Max, Avg: These values relate to the executed statements since the start of the acquisition or the last statistics reset. Last: Response time of the last executed statement. |
