Table General module settings for input modules (left) and output modules (right)




Basic settings

Module Type (information only)

Indicates the type of the current module.

Locked

You can lock a module to avoid unintentional or unauthorized changing of the module settings.

Enabled

Enable the module to record signals.

Name

You can enter a name for the module here.

Comment

You can enter a comment or description of the module here. This will be displayed as a tooltip in the signal tree.

Module No.

This internal reference number of the module determines the order of the modules in the signal tree of ibaPDA client and ibaAnalyzer.

Timebase

All signals of the module are sampled on this timebase.

Use module name as prefix

This option puts the module name in front of the signal names.
Module structure (only input modules)

No. analog signals/No. digital signals

Define the number of configurable analog and digital signals in the signal tables. The default value is 32 for each. The maximum value is 1000. The signal tables are adjusted accordingly.
Trigger

Update time

You can use the update time in milliseconds to determine the following:

  • In Cyclic send mode: execution interval of the SQL statements

  • In the On change and On trigger mode: dead time after executing a statement

Send mode

Set here when to execute the SQL statements (queries and commands).

  • Cyclic: The SQL statement is executed cyclically at the set update time.

  • On change: When selecting this mode, the line Trigger signal appears. After a triggering, all other triggering value changes are ignored until the update time has expired. Only then can the SQL statement be executed again.

  • On trigger: When selecting this mode, the line Trigger signal appears. After a triggering, all other triggering triggers are ignored until the update time has expired. Only then can the SQL statement be executed again.

Trigger signal (for On change or On trigger send mode)

  • In the On change send mode: You can select any analog or digital signal here to serve as the trigger. In case of a change to the signal value, the SQL statement is executed.

  • In the On trigger send mode: You can select any digital signal here to serve as the trigger. In case of a rising edge of the signal, the SQL statement is executed.

Queue size

The queue serves as a buffer for SQL statements in the following cases:

  • The database connection is interrupted.

  • The execution of an SQL statement takes long while new SQL statements are already triggered in ibaPDA before the execution has been finished.

Use the queue size to determine how many SQL statements are intermediately stored as a maximum. If this number is exceeded, the oldest SQL statements are deleted.

  • With input modules, the queue is 1 by default: Because the results of an SQL query are mapped to signals, in most cases it is not useful to catch up on queries that were not executed due to an interrupted connection. The SQL queries buffered in the queue would then be executed in quick succession and the results transmitted to the signals. With the queue size 1, only the last triggered SQL query is always kept available.

  • With output modules, the queue size is 1000 by default: Production data, for example, can be written via SQL commands. It is important here that these are also buffered and made up for in case of a connection breakdown.

Command timeout

By setting the command timeout, you determine the maximum time for a statement to be executed. If the query or command is not completed before the command timeout has elapsed, the execution is aborted. The default settings of query and command differ:

  • SQL query: 5 s

  • SQL command: 30 s