About the manual
This manual uses the following notations:
| C:\Program files\inray\ log_1.txt http://localhost/ | File names and paths, URL |
| Datasource | Names of parameters and objects' properties. |
| <Datasource> | Place holder to be filled during development. (Delete brackets < and >!) |
... Dim TextHandle TextHandle.SetCoord 10,10 ... | Source code samples and templates |
| “Change” | Names of controls, tabs, buttons etc. within GUI. |
| File–New or File - New | Menu/Submenu entries. |
Terms used
| (set of) access data | Technically speaking: instance of a plug-in, e. g. the access data to one specific OPC Server, a specific database server etc. as in OPC access data, database access data etc |
| element (of a transfer object) | Part of a transfer object, e. g. a table's column within a database transfer object or an OPC item within an OPC transfer object or a specific variable used. Elements (sometimes also called items) are connected during development to define a transfer. |
| item, transfer object item | see “element”. Not to be mixed up with OPC item, so mostly element is used. |
| configuration | “Configuration” means (as a rule) the basic settings and the creation of access data within the OPC Router Configuration (GUI). Whereas “development” or “projection” means defining connections (also via OPC Router Configuration GUI). |
| plug-in | Plug-ins provide the Router's functions, e. g. connection to OPC, database or mail servers, to ERP systems, as well as use of intern variables etc. Most plug-ins have to be licensed separately. The manual uses the term for all sets of access data of a specific plug-in also. |
| plug-in instance | see “access data”. |
| development | see “projection”. |
| projection | The process of defining connections (projection of transfers). i. e. the process of defining sources, destinations, triggers as well as (de-)activating. Also referred to as “development” in contrast to “configuration”. However, OPC Router is both configured and projected via OPC Router Configuration (GUI). |
| snap-in | The dialogue left of the display |
| transfer | Data transfer during runtime. During projection the same as “connection”. |
| transfer object | Source, destination or trigger of a transfer. |
| variable | As a rule, an instance of the variable plug-in, i. e. a variable to be used within transfers. Other variables carry special names like template variable or placeholder. |
| connection | Combination of at least one data source, one destination and one trigger. A connection defines how a transfer is executed: Which data is transferred under which condition to which destination. |
Images
Some of the screenshots present several numbered mouse pointers. The numbers refer to the instructions in the text. Therefore, numbers might have been left out. The following example shows steps 3 to 7 of the specific chapter.
Several pop-up dialogs might be shown side by side, even if they open one after another, just to show the results of mouse interaction:
.png)
Project planning of an OPC data source