Notations
This documentation uses the following notation:
| Notation | Explanation |
|---|---|
| C:\Program Files\inray\log_1.txt http://localhost/ | File names and paths, URL |
| Data source | Names of parameters and object properties |
| <datenquelle> | Placeholders to be replaced by the project engineer with the corresponding content (delete the angle brackets < and >!). |
... Dim TextHandle TextHandle.SetCoord 10,10 ... | Source code examples and templates |
| "Change" | Names of controls, tabs, buttons, etc. are not specially marked, but are usually enclosed in quotation marks. |
| File-New or File - New | Menu/submenu entries are connected by hyphens. |
Terms used
| Term | Explanation |
|---|---|
| Connection(s) | Plug-in instance: The individual configuration entry of a plug-in, e.g., the connection information for a specific OPC server or a specific database server. OPC server connection, DB server connection, mail server connection, etc. |
| Element (of a transfer object) | Part of a fully configured transfer object, e.g., data field of a table or OPC item or a specific variable. Elements/items are connected with arrows during connection configuration, thus forming the definition of the data transfer. |
| Item, transfer object item | See Element (of a transfer object) |
| Configuration | In the documentation, "configuration of the OPC router" refers to the basic settings and (in most cases) the creation of plug-in instances (in contrast to connection configuration). |
| Plug-in | The plug-ins provide the actual functions of the router, e.g., the connection to OPC, database, or mail servers, to ERP systems, but also router-internal variables. Some plug-ins must be licensed separately. The documentation also uses "plug-in" to refer to all instances of a particular plug-in. |
| Plug-in instance | See "Connection." |
| Project planning | This usually refers to connection project planning. |
| Snap-in | Dialog box on the left side of the screen. |
| Transfer | A data transfer at runtime. At design time, the same as "connection." |
| Transfer object | A source, destination, or trigger in a connection. |
| Variable | Usually an instance of the variable plug-in. Other variables (e.g., within templates) are referred to as template variables or placeholders if the context is not clear. |
| Connection | A combination of at least one data source, one data destination, and one trigger. Connections define how a transfer is to be executed: Which data is moved from where to where under which conditions. |
| Connection project planning | The actual assembly of a connection: (new) creation, definition of sources, targets, and triggers, activation, and deactivation. Connection project planning requires a completed configuration. |
Illustrations
In some screenshots, you will find several mouse pointers with numbers (numbers in circles). The numbers refer to the instructions to which the illustration belongs. If individual steps are not documented in the illustration, the numbering is not continuous. In the following illustration, for example, steps 3 to 7 are summarized.
Please also note that the illustrations show different dialog boxes side by side, which only open during the course of the instructions. In the following illustration, the "OPC Transfer Object" dialog box opens after step 4, and the tag browser opens after step 6.b.
-ec29a4ce94b6dd8d32dac6b78ad3a9b4.jpg)