Стратмор вдруг увидел шанс выиграть на двух фронтах сразу, осуществить две мечты, а не одну. В шесть тридцать в то утро он позвонил Дэвиду Беккеру. ГЛАВА 97 Фонтейн стремительно вбежал в комнату для заседаний.

OPC Support. Home Create A Case More. Article Information Title. You must set the encryption password before you initiate any connection.

Please visit the Encryption section in user manual to learn more. The user has the option to turn encryption off after the installation is completed. After the installation is complete, it is recommended that you verify the DCOM settings. This configuration varies for different operating systems.

Installation Instructions: To start the installation, please double-click on the installation. If the Licensing Agreement screen is the displayed screen, go to step 5. If the Pre-Requisites screen appears, then click on the Next button to install the listed pre-requisites. This is required to ensure the software will function properly.

After all pre-requisites have been installed, the License Agreement screen appears. Read the Software License Agreement , using the scroll bar to view the entire message. Click on the Next button. The User Credentials for Services screen appears. Enter the User Name , Domain , and Password for the account that all installed Tunneller services will run under. The selected user: Should not be a personal user account Should not be an administrator account, or an account with elevated privileges.

Must have been entered correctly as per the instructions on the screen. Must Have the “Log in as a service” right granted. This is typically provided by your IT department. If this right is not granted, Tunneller may not function properly. The Setup Type screen appears. Select the type of setup to be performed. The Destination Folder screen appears. Select the folder in which to install the MatrikonOPC server, or accept the default location displayed in the Folder path field.

The Start Menu screen appears. Select the Start Menu group and specify whether you want shortcuts created only for yourself, or for all users, by selecting the applicable option button. The Licensing screen appears. Select the applicable licensing option. The Ready to Install screen appears. The Installing MatrikonOPC Tunneller screen appears, installation begins, and the product files are copied to the computer. At this point, you have the option of launching Configuration panel or User Documentation Click on the Finish button to complete the installation and exit the Wizard.

The necessary files have now been copied to the target computer, the software components are registered, and shortcut icons are created in the Start menu. Article Type Please select the Article Type which best matches your article. Article Sub-Type Please select the article sub-type which best matches your article.

URL Name. Last Published Date. Articles View All Articles. Show actions for this object. Drop Files. Upload Files Or drop files. Number of Views Why will my Windows Service not start? All rights reserved.

WebApr 08,  · MatrikonOPC Tunneller. April 08, MatrikonOPC. MatrikonOPC Tunneller. MatrikonOPC Tunneller (now with encryption and data compression) . WebMar 16,  · Click on the Next button. The Installing MatrikonOPC Tunneller screen appears, installation begins, and the product files are copied to the computer. When the . Download: Matrikon OPC UA Tunneller Free Test Trial. Matrikon OPC UA Tunneller provides an intuitive, user-friendly interface to help you get your Classic-to-Classic OPC connectivity and Classic-to-OPC UA bridging up-and-running quickly and efficiently. The OPC UA Tunneller UA-to-Classic Bridge for COM OPC Servers provides OPC UA Clients with access to legacy COM OPC DA and HDA Servers using the OPC UA specifications.

ISY Updated Copyright Information and Contacting Support sections. Added Pi usage item to Troubleshooting section. Typos fixed. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, translated, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Matrikon Inc. It may not be disclosed or transferred, directly or indirectly, to any third party without the explicit written permission of Matrikon Inc.

Matrikon makes no warranty of any kind with regard to the information contained within this document and Matrikon shall not be liable for any direct, indirect, incidental or consequential damages which may arise in connection with the furnishing, reliance, or use of the information contained within this document.

Specifications and statements as to performance in this document are Matrikon estimates, intended for general guidance. Matrikon reserves the right to change the information contained within this document and any product specification without notice. Statements in this document are not part of a contract or program product licence insofar as they are incorporated into a contract or licence by express preference.

Issue of this document does not entitle the recipient to access or use of the products described, and such access or use shall be subject to separate contracts or licenses. The receiving party shall not disclose, publish, report, communicate, or otherwise transfer any information in this document to any third party, and shall protect all information contained herein from unauthorized disclosure.

The receiving party shall permit access to this document only to its employees, agents, subcontractors, and affiliates who reasonably require access to such information contained herein, have been made aware of the confidential nature of this document and have executed a written employment or other confidentiality agreement party to maintain the confidential status of this document.

MatrikonOPC Tunneller v4. Number of Bits The majority of these problems occur not during normal operation, but at the time of installation. Quite often plant engineers face difficulties configuring cross-network communication, windows authentication, as well as start-up and run-time permissions. Tunneller provides the following: Cross-domain and cross-workgroup communication with minimal network configuration.

A finer level of control over communication timeouts. This manual explains how to install and configure the software, and how to perform common tasks. In addition, technical information about OPC data items is included, along with sections on diagnostics and troubleshooting. Overview of Manual This document uses icons to highlight valuable information. Remember these icons and what they mean, as they will assist you throughout the manual. This symbol denotes important information that must be acknowledged.

Failure to do so may result in the software not functioning properly. The Users Manual has been designed as such so that you can click on references in the document to jump to that referenced point without having to scroll through several pages in some cases. For example, if you were to see the sentence Refer to Figure 1 for more information, pressing the CTRL key and clicking your mouse on the text Figure 1 automatically takes you to the location of Figure 1 within the document.

This manual consists of several sections and is structured as follows: Introduction this introductory chapter. Getting Started provides system requirements information. Limitations provides information on specific performance and operational limitations of the software. Troubleshooting provides licensing, MatrikonOPC Support contact information, solutions for common problems that may be encountered, and answers to frequently asked questions.

OPC Compliance details supported interfaces with regard to installation, common interfaces, and data access. Provides access to process alarm and event data. A method for organizing software, specifying how to build components that can be dynamically interchanged.

CS In short form used to indicate the Client-Side machine. Provides access to real-time process data. Allows the transfer of data between two running applications. Provides access to historical process data. Device that allows interaction between the user and machine. Typically used in process control applications. Matrikon Matrikon Inc.

OPC A communication standard. Refer to www. SS In short form used to indicate the Server-Side machine. The System Requirements section shows how to avoid future problems by ensuring that the system meets the minimum software and hardware requirements.

Detailed step-by-step instructions in Appendix B – Installation walks you through the installation process. Appendix C Installed Files lists the files that are installed during this process.

Once the software is installed, refer to the Licensing section for information on how to obtain the appropriate license. The Licensing section will refer you to the Licensing Procedures document that was installed along with the server and this Users Manual.

If any problems are encountered during installation or licensing, refer to the Contacting Support section for information about how to contact the MatrikonOPC Support team for assistance. System Requirements The software has minimum Software and Hardware system requirements. These requirements must be met for the software to function properly. Note: To install and configure a MatrikonOPC server, you must be set up as an administrative user account rather than a restricted user account. NET 2.

If there are no Tunneller connections configured, then the Client-Side Gateway Configuration Utility will display no available Tunneller connections. Tunneller connections may now be added. To add a connection: 1. Note: For Tunneller to operate, at least one connection to an OPC Server must be configured local connections are also allowed. The OPC server to which Tunneller will connect must reside on the same machine as the remote Tunneller install. Option Description Connect to Allows you to enter or select from the drop-down list the name of the computer referenced either by its IP address or by the specific computer name.

Port Number Allows you to enter the port number on the remote PC to which Tunneller should establish a connection. Restarting the Tunneller service is required when this option is changed. The default port is Note: To successfully communicate, the port number configured on the Client-Side Component must match with the port number configured on the Server-Side Component.

Processing Timeout Allows you to enter the amount of time in seconds the CSC waits for a response to a request before it considers the request failed and returns an error code to OPC client. Processing Timeout should be set to a value higher than the longest time required to execute a request. The default value is 60 seconds. Communication Timeout Allows you to enter the amount of time in seconds the network communication mechanism will try to send a request or receive a response from the SSC before it considers the communication failed.

Communication Timeout should be configured to a value higher than the time required to send the largest message over the network. The default value is 10 seconds. This parameter defines how many attempts should be made after failure. The default value is 5 i. Use Compression Enable compression for remote Tunneller connections. By default this checkbox is not selected.

Note: Compression can be adjusted later for each individual OPC server. Table 2 – Add Remote Tunneller Connection Options Note: If Tunneller detects that the network path to the remote computer is unavailable because of a physical break in the network or the remote SSC is not available, it considers the sending of the command as failed and will not attempt any retries.

At that point, Tunneller will try to reconnect to the remote computer. Once the settings have been configured to the users specific network requirements, click on the OK button. Note: In version 3. One such function is to refresh settings for all tunnelled servers by reading them from the system registry. This does not affect any current connections and does not create connections to Server-Side components it only refreshes the configuration display.

To refresh the server list: 1. If there are active connections, the OPC clients must be disconnected before the Tunneller server connection is removed. When removing a Tunneller server connection and recreating it, ensure that any OPC client that has the connection information cached, clears its cache and obtains the new Tunneller server connection information.

Failure to do so may cause unpredictable behaviour. A small portion of Tunneller will be loaded in proc. Support the Shutdown call-back. This is a required interface but some clients do not support it.

It must be supported for Tunneller to relay communication failure information. The GetStatus call should be used as a heartbeat mechanism for line failure detection. Tunneller does not initiate the GetStatus call on its own. The call can be made as often as needed, depending on the required detection level.

Frequent calls at approximately one second will detect a line failure quickly. It will also detect a line that has gone down but has come back immediately. Infrequent calls can allow a momentary interruption to pass but will not detect a prolonged failure until the line is needed by an actual call.

The users specific requirements will indicate how often the GetStatus should be called. These options are described in Table 3. Clearing the checkbox will cause any GetStatus call made to Tunneller to be returned immediately with Tunneller’s own status. This option is available only when the Use Remote Status checkbox has been selected. When selected, this option forces an internally generated GetStatus message to be sent to the end OPC server.

However, it returns Tunnellers own status immediately to the calling client, so it is a non-blocking call. The remote call will be made as close as possible to the rate at which the end OPC client is calling GetStatus on Tunneller. If a communication failure is detected, Tunnellers status will be set to failed. Remote This option is available only when the Use Remote Status checkbox has been selected.

The status of the end OPC server will be returned. If there is a line interruption or some other form of communication failure between the two halves of Tunneller, the calling OPC client may hang and become unresponsive it is a blocking call. In subsequent GetStatus calls, the status field of the status structure returned by Tunneller will be set to failed.

The default time interval value is equal to half of the timeout parameter configured on the tunneller. For example, adding 15, items can take the OPC server 15 seconds to perform. If the CSC does not receive any message during the time interval set by the Communication Timeout parameter which also has a default value of 3 seconds , the CSC detects communication failure, disconnects from the SSC and tries to reconnect during the time defined in the ReconnectTime parameter in TunnellerOpts.

If reconnection is not successful, then the add items request fails and the failed result is returned to the OPC client. Furthermore, this communication may be further regulated by the use of encryption keys. Since the Server-Side machine contains the data that the Client-Side machine wishes to access, the option to operate in a more secure mode is made available on the Server-Side.

There are two security modes in which Tunneller may operate: Open – no encryption will be used and there is no restriction as to which computers may connect through Tunneller.

By default, Tunneller will operate in Open mode. Encrypted – encryption may be used and the user will be able to control which computers are permitted to connect through Tunneller. The information contained in this section is useful for those users who wish to operate in Encrypted mode.

When Open mode is selected Figure 11 , the Encryption tab is disabled and Tunneller communication will not be encrypted. When Encrypted mode is selected, the Encryption tab is enabled Figure 12 , allowing the user to configure key mappings which will regulate Tunneller encryption.

Encryption fields are described in Table 4. On the Tunneller SSC, the encryption key is read when a new communication session is created. Therefore, modifications to key mappings on the SSC will not affect existing connections. To apply modifications on the SSC, connected sessions should be recreated. Recreation of a session can be achieved from the Tunneller CSC. When the OPC client or clients connect again, the modifications will take effect.

Alternatively, if a situation occurs such as no access to the OPC client machine, then restarting the Tunneller SSC service will disconnect clients and apply the SS key mappings on start up. An existing connection will continue to communicate using their old encryption settings until the session has ended. Address can be entered in three different ways: Single IP address is defined exactly. Address range start and end addresses of the range are defined.

In this case the key will be used for all IP addresses belonging to the range. In this case if the result of a bitwise AND operation of the CSC hosts address and Mask is equal to the result of bitwise AND operation of Address value and Mask, then the corresponding key will be used for that particular address. In this case for all hosts belonging to the Using arrows the rightmost bit of Mask can be shifted to the left or to the right.

The first click on Get local button changes Address filed to local IP address. Note that for a subnet mask to be valid, its leftmost bits must be set to ‘1’. Conversely, the rightmost bits in a valid subnet mask must be set to ‘0’, not ‘1’. So all valid subnet masks contain two parts: the left side with all mask bits set to ‘1’ the extended network portion and the right side with all bits set to ‘0’ the host portion.

Note that Subnet type entries are sorted in certain order taking into account how many bits define extended network portion, for example: o When this mode is selected, the Encryption tab is disabled.

When the Encryption option is selected, the user can select which computers may connect through Tunneller and may set up encryption. Encrypt When setting up a key mapping, it must be decided if Tunneller communication for the selected IP address will be encrypted. If encryption is desired, check this box; otherwise, ensure it is unchecked.

Encryption Key When setting up a key mapping, if encryption will be used for Tunneller communication with that specific IP address or range of addresses, an encryption key may be entered. An Encryption key may contain letters, numbers, and special characters available on a keyboard.

If the Encryption key field is empty, then default hard-coded key will be used. Key Mappings This field will display the user-created key mappings. Key mappings control which computers may connect through Tunneller and contain the encryption keys being employed.

Here IP address can be just single address or range of IP addresses or the subnet mask and address combination. Clicking on a key mapping will fill the current mapping fields with the selected key mapping settings.

Note that the list of keys is ordered in the following order: 1. Single address in ascending order. Address ranges in ascending order of From address. Subnets in ascending order of address value. The first found entry in Key mapping is used for the given IP address.

Add Key Mapping Once the user has filled the IP address information and encryption key optional , pressing this button will create a new key mapping. If a key mapping containing the specified IP addresses already exists, this button will not be enabled. Update Key Mapping This button is used to update the selected key mapping with the values from fields Encrypt, Encryption key and IP address.

If the values on selected key mapping have not changed, this button will be disabled. OK This button acts exactly in the same way as the Apply button changes are saved. The difference is that after saving of key mappings the dialog window will be closed. Otherwise, its label states Close. Apply This button is enabled if changes to key mappings have been made. Note: If key mappings were modified, but not saved, and later their previous values are recovered, then the Apply button will be disabled.

Table 4 – Encryption Options The encryption level depends on the length of the user-entered encryption key. Encryption keys will be padded out to the appropriate length the greatest number of characters in that range automatically. For example, a character encryption key will be padded out to 16 characters. Modifications of encryption key mappings become effective immediately on CSC. Computer 1 with IP address Furthermore, the same encryption settings must be used.

If the key mapping on the CSC is: In the first line the IP address is defined exactly. In the second line the range of addresses from In the third line, the subnet mask and address are defined. In such a situation, the first found key is used line with bit encryption.

Compression was introduced in version 3. If compression is enabled in an attempt to communicate with an earlier version of the Tunneller SSC then this option is ignored and does not affect communication behaviour. The compression option is configured in the Client Configuration Tool by selecting the Use Compression check box Figure By default this feature is turned off. On the server side, Remote user to Local user mappings can be configured.

If the entry is found, it takes Local user for that entry and performs impersonation using its domain, user name and password for the thread communicating with the end OPC server. As a result, the end OPC servers can behave differently based on what user is connected, for example restrict access.

If impersonation is turned ON, the fields on Impersonation tab page Figure 16 become enabled. Note: Impersonation can also be turned on or off through the tunneller. Its default value is 0 i. User impersonation mappings can be configured only using the Server- Side Gateway Configuration Tool. The behaviour of the system in case no entry is found for the provided Remote user or the Remote user is not defined this can be possible if older version of Tunneller CSC is connected depends on the state of Use Default account checkbox.

If it is turned OFF, then the connection will be rejected. If it is turned ON, the entry for [Default] Remote user will be used. If at the time when the checkbox is turned ON and no such entry is found, the Edit User Mapping window is opened and the entry will be added. Local user corresponding to [Default] Remote user can be configured either as a specific local user account or as [Default].

If User Impersonation is turned ON but there are no mappings configured, and the Default Account option is turned OFF, a warning message pops up when changes are applied.

To add a new entry into the User mappings: 1. The new Edit User mapping window Figure 17 is displayed. Enter the Remote user, Local user, and Password. The Local user field requires the user name only. Select the OK button. Note: All impersonation mappings including passwords are stored in the configuration file using encryption.

The currently selected entry can be edited by double-clicking your mouse on the entry or by selecting the Edit button. To delete an entry or entries from the User mappings, select one or more entries and click on the Delete button. Each Remote client can have a configured list of accessible OPC servers.

If the Remote client is unknown i. Settings for what fields are used to authenticate the Remote client and what Remote clients can access which OPC servers, are configured using the Access Lists tab Figure Components of this tab are described in Table 6. Starting in version 3. That provides functionality to control access rights per remote user at the OPC Items level. Therefore, if licensing conditions are changed, the Server-Side Gateway Configuration Tool should be restarted for changes to take effect.

At least one checkbox must be checked. Remote Clients The list of entries authenticating Remote clients. The number of visible columns depends on the selected Authenticate Remote client by checkboxes. Note: For each combination of selected Authenticate Remote client by checkboxes, separate lists are stored on the Remote clients list.

Use [Default] Access List for Unknown Clients This checkbox defines the behaviour of the system in case the Remote client could not be authenticated unknown. If selected, then the list of accessible OPC Servers for [Default] entry will be used all fields have [Default] value for this entry on Remote Clients list.

Otherwise, access is refused and the empty list is returned to the Client-Side Gateway Configuration Tool. Add Adds a new entry into the list of Remote clients.

Opens a new window. Delete Deletes the currently selected entry from the list of Remote clients. Select the applicable checkboxes to determine whether the corresponding OPC server is accessible to the currently selected Remote client or not. Changing the selected entry in the list of Remote clients can be done by selecting the Edit button. In either situation, the Edit Remote client host info window Figure 19 is displayed.

Components of that window are described on Table 7. Notes: The [Default] entry on Remote clients list cannot be edited or deleted. All fields selected for use for authentication, must have non-empty values. Option is disabled if the IP address checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab.

If the Host name option is disabled, click on this button to enable it. A value can then be entered into the Host name field. A second click to this button will retrieve the IP Address. Note: This can be time consuming. While processing, the button will be disabled and its text will be changed to Getting. Host Name Fully qualified Host name of Remote client. Option is disabled if the Host name checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab.

If the IP address option is disabled, click on this button to enable it. A value can then be entered into the IP address field. A second click to this button will retrieve the Host name. Note: This can be time-consuming. Note: User account, under which the OPC client application runs, might be different than the currently logged-on-to remote host user.

Select from the list of connections that were opened Click on this button to open the Select Remote Client info from the list of connections window Figure The window opened by this button contains a list of Remote client authentication data that can be selected and used to fill corresponding fields.

Entering Remote client host information by selecting from the list of connections ensures that the authentication fields have correct values and the configuration process is sped up. Notes: If no connections have yet been accepted by SSC, the connections list is empty and the button is disabled.

OK Saves changes in memory and closes the window. Note: Changes will take effect when either the OK or Apply button on the main window is selected. Advanced settings are stored in the tunneller.

Level Log level. It does not disable logging to file. Overwrite Old File If this checkbox is selected, the previous log files copy is not made. Otherwise, backup is made named as tunneller.

Commit All Log File Writes If this checkbox is selected, all information written to the log file is immediately written to disk instead of being cached.

Note: To successfully communicate, the port number configured on Server-Side Component must match with the port number configured on Client-Side Component. If this option is changed, the Tunneller service must be restarted.

Timeout Communication timeout in seconds. If the CSC version is 3. Retries Number of retries after communication failure. Maximum Size of Queue Maximum number of outgoing messages on the communication messages queue. See Update of large amount of items fails in the Troubleshooting section for more details. The default value is 5.

Session Timeout Used when communication failures occur. During the Session Timeout period, the connection to the end OPC server is not closed and the session stays open i.

When the Client-Side Component reconnects to the Server-Side Component, that session can be reused so that recovering does not take a long time. This option should have the same value as the ReconnectTime option configured on Client-Side Component versions prior to 3. Only One Connection If this checkbox is selected, it specifies that only one connection at a time is created to the OPC server.

Usually this checkbox should be selected. It takes effect in two cases. If a communication error occurs, then the session is waiting for reconnection for a defined session timeout period. But, the Client- Side Component can send a request to create a new session at that time.

If this option is selected, then the Server-Side first waits for disconnection from the OPC server and deletion of the previous session, and then only creates a new session.

Otherwise, for a session timeout period, more than one open connection to the end OPC server can exist. On the Windows box, only one instance of the Client-Side Component can run at the same time. In this case, multiple instances can run on the client-side and the Only One Connection checkbox must be cleared.

Otherwise, OpcEnum service is used. Refer to Table 9 for those settings that can be overridden. Its value is used when processing a shutdown request from OPC server: SSC waits during this time for the current operation if there is any completion before disconnecting. If an CSC version prior to 3. This default value can be changed by adding the ProcessingTimeout option into the tunneller. For connections from a CSC version prior to 3. The ReconnectTime option is configured in the TunnellerOpts.

The default value is 0 indicating that no reconnection attempts will be performed. A connection is established and normal communication is underway. A failure is detected either a broken link is detected or a Communication Timeout has been passed. If the SSC is still active i.

Cross Domains and Workgroups Authentication difficulties make DCOM connections across different domains or workgroups extremely difficult or impossible. Leap past this limitation with OPC Tunneller.

Essentially, if you can ping the PC, you can get to it with Tunneller. This causes considerable difficulty when communicating over satellite, modems, radio, and other bandwidth-limited communication types. MatrikonOPC Tunneller features lossless data compression, which reduces load on networks and saves money when paying per MB of data. Timeouts and Disconnections Plagued with timeouts?

Need recovery faster than the unconfigurable 6 minute timeout that comes with DCOM? Encryption can be selected from 64, 96, or bit AES. Easy Configuration Depending on your system, configuring DCOM just to the point of getting communication can take days! OPC Tunneller reduces your integration time to minutes!

Matrikon Inc. RT 1. RS 1. TNM 1. RN 2. LB 2. RN, LB 2. Updates to Software Requirements and Troubleshooting sections. Updates to Troubleshooting section. LB, RN 3. RN 4. Removed DEP warning. Updated DCOM hyperlink. Formatting fixes. Contacting Support section updated. SL, LB 4. Updated Installation section. LB 4. LB 5. Added Get Status Ping description to Table Replaced screenshot Figure 31 to include new field.

SN, LB 6. Updated Contacting Support section. SN, LB 7. Software updated to v3. Manual converted to standard template. LB 7. Communication Timeout field description updated to reflect same. LW, LB 7. LB 8. Software Requirements updated to included Microsoft Windows Server New sub-section added to Connection and Reconnection section.

SN, LB 9. MJL, LB LB Checkbox description added to Table 8. ISY Updated Copyright Information and Contacting Support sections. Added Pi usage item to Troubleshooting section. Typos fixed. All rights reserved. No part of this document may be reproduced, stored in a retrieval system, translated, or transmitted in any form or by any means, electronic, mechanical, photocopying, recording, or otherwise, without prior written permission of Matrikon Inc. It may not be disclosed or transferred, directly or indirectly, to any third party without the explicit written permission of Matrikon Inc.

Matrikon makes no warranty of any kind with regard to the information contained within this document and Matrikon shall not be liable for any direct, indirect, incidental or consequential damages which may arise in connection with the furnishing, reliance, or use of the information contained within this document.

Specifications and statements as to performance in this document are Matrikon estimates, intended for general guidance. Matrikon reserves the right to change the information contained within this document and any product specification without notice. Statements in this document are not part of a contract or program product licence insofar as they are incorporated into a contract or licence by express preference. Issue of this document does not entitle the recipient to access or use of the products described, and such access or use shall be subject to separate contracts or licenses.

The receiving party shall not disclose, publish, report, communicate, or otherwise transfer any information in this document to any third party, and shall protect all information contained herein from unauthorized disclosure. The receiving party shall permit access to this document only to its employees, agents, subcontractors, and affiliates who reasonably require access to such information contained herein, have been made aware of the confidential nature of this document and have executed a written employment or other confidentiality agreement party to maintain the confidential status of this document.

MatrikonOPC Tunneller v4. Number of Bits The majority of these problems occur not during normal operation, but at the time of installation. Quite often plant engineers face difficulties configuring cross-network communication, windows authentication, as well as start-up and run-time permissions. Tunneller provides the following: Cross-domain and cross-workgroup communication with minimal network configuration. A finer level of control over communication timeouts.

This manual explains how to install and configure the software, and how to perform common tasks. In addition, technical information about OPC data items is included, along with sections on diagnostics and troubleshooting.

Overview of Manual This document uses icons to highlight valuable information. Remember these icons and what they mean, as they will assist you throughout the manual. This symbol denotes important information that must be acknowledged. Failure to do so may result in the software not functioning properly. The Users Manual has been designed as such so that you can click on references in the document to jump to that referenced point without having to scroll through several pages in some cases.

For example, if you were to see the sentence Refer to Figure 1 for more information, pressing the CTRL key and clicking your mouse on the text Figure 1 automatically takes you to the location of Figure 1 within the document. This manual consists of several sections and is structured as follows: Introduction this introductory chapter. Getting Started provides system requirements information. Limitations provides information on specific performance and operational limitations of the software.

Troubleshooting provides licensing, MatrikonOPC Support contact information, solutions for common problems that may be encountered, and answers to frequently asked questions. OPC Compliance details supported interfaces with regard to installation, common interfaces, and data access. Provides access to process alarm and event data.

A method for organizing software, specifying how to build components that can be dynamically interchanged. CS In short form used to indicate the Client-Side machine. Provides access to real-time process data. Allows the transfer of data between two running applications. Provides access to historical process data.

Device that allows interaction between the user and machine. Typically used in process control applications. Matrikon Matrikon Inc. OPC A communication standard. Refer to www. SS In short form used to indicate the Server-Side machine. The System Requirements section shows how to avoid future problems by ensuring that the system meets the minimum software and hardware requirements.

Detailed step-by-step instructions in Appendix B – Installation walks you through the installation process. Appendix C Installed Files lists the files that are installed during this process. Once the software is installed, refer to the Licensing section for information on how to obtain the appropriate license.

The Licensing section will refer you to the Licensing Procedures document that was installed along with the server and this Users Manual. If any problems are encountered during installation or licensing, refer to the Contacting Support section for information about how to contact the MatrikonOPC Support team for assistance.

System Requirements The software has minimum Software and Hardware system requirements. These requirements must be met for the software to function properly. Note: To install and configure a MatrikonOPC server, you must be set up as an administrative user account rather than a restricted user account.

NET 2. If there are no Tunneller connections configured, then the Client-Side Gateway Configuration Utility will display no available Tunneller connections. Tunneller connections may now be added. To add a connection: 1. Note: For Tunneller to operate, at least one connection to an OPC Server must be configured local connections are also allowed. The OPC server to which Tunneller will connect must reside on the same machine as the remote Tunneller install.

Option Description Connect to Allows you to enter or select from the drop-down list the name of the computer referenced either by its IP address or by the specific computer name. Port Number Allows you to enter the port number on the remote PC to which Tunneller should establish a connection. Restarting the Tunneller service is required when this option is changed.

 
 

MatrikonOPC Tunneller: Worlds most used OPC Tunnelling Solution.Matrikonopc tunneller download

 
WebUsing the link below to download MatrikonOPC Tunneller from the developer’s website was possible when we last checked. We cannot confirm if there is a free download of . WebMatrikonOPC Tunneller v Users Manual 10 Connection and Reconnection presents a simple scenario demonstrating how Tunneller reacts to an interrupted network. . WebApr 08,  · MatrikonOPC Tunneller. April 08, MatrikonOPC. MatrikonOPC Tunneller. MatrikonOPC Tunneller (now with encryption and data compression) .

MatrikonOPC Tunneller 3. It does away with the headaches typically associated with DCOM configuration.

No longer are different matrikonopc tunneller download, security settings or locations a factor when sharing data between computers. Users are provided with more control over the security of their OPC systems. Data sent over satellite and other per-Megabyte connections can be reduced for significant cost savings.

Historical data can be compressed to matrikonopc tunneller download size much smaller than the original data, all without any data loss. Cross Domains and Workgroups Authentication difficulties make DCOM connections across different domains or workgroups extremely difficult or impossible. Leap past this limitation with Больше на странице Tunneller.

Essentially, if you can ping the PC, you can get to it with Tunneller. This causes considerable difficulty when communicating over satellite, modems, radio, and other bandwidth-limited communication types. MatrikonOPC Tunneller features lossless data compression, which reduces load matrikonopc tunneller download networks and saves money when paying per MB of data. Timeouts matrikonopc tunneller download Disconnections Plagued with timeouts?

Need recovery faster than the unconfigurable 6 minute timeout that comes with DCOM? Encryption can be selected from 64, 96, or bit Нажмите чтобы прочитать больше. Easy Configuration Depending on your system, configuring DCOM just to the point of такую download game contract killer 2 for pc что communication can take days!

OPC Tunneller reduces your integration matrikonopc tunneller download to minutes! Start communicating! Fast, easy and reliable Optimized for low-bandwidth infrastructures Uses only a single port.

Facebook LinkedIn Twitter. April 08, MatrikonOPC.

У нас столько времени, сколько. Сьюзан отказывалась понимать. Не появится.

If impersonation is turned ON, the fields on Impersonation tab page Figure 16 become enabled. Note: Impersonation can also be turned on or off through the tunneller.

Its default value is 0 i. User impersonation mappings can be configured only using the Server- Side Gateway Configuration Tool. The behaviour of the system in case no entry is found for the provided Remote user or the Remote user is not defined this can be possible if older version of Tunneller CSC is connected depends on the state of Use Default account checkbox.

If it is turned OFF, then the connection will be rejected. If it is turned ON, the entry for [Default] Remote user will be used.

If at the time when the checkbox is turned ON and no such entry is found, the Edit User Mapping window is opened and the entry will be added.

Local user corresponding to [Default] Remote user can be configured either as a specific local user account or as [Default]. If User Impersonation is turned ON but there are no mappings configured, and the Default Account option is turned OFF, a warning message pops up when changes are applied.

To add a new entry into the User mappings: 1. The new Edit User mapping window Figure 17 is displayed. Enter the Remote user, Local user, and Password. The Local user field requires the user name only. Select the OK button. Note: All impersonation mappings including passwords are stored in the configuration file using encryption.

The currently selected entry can be edited by double-clicking your mouse on the entry or by selecting the Edit button. To delete an entry or entries from the User mappings, select one or more entries and click on the Delete button.

Each Remote client can have a configured list of accessible OPC servers. If the Remote client is unknown i. Settings for what fields are used to authenticate the Remote client and what Remote clients can access which OPC servers, are configured using the Access Lists tab Figure Components of this tab are described in Table 6. Starting in version 3. That provides functionality to control access rights per remote user at the OPC Items level.

Therefore, if licensing conditions are changed, the Server-Side Gateway Configuration Tool should be restarted for changes to take effect. At least one checkbox must be checked. Remote Clients The list of entries authenticating Remote clients. The number of visible columns depends on the selected Authenticate Remote client by checkboxes.

Note: For each combination of selected Authenticate Remote client by checkboxes, separate lists are stored on the Remote clients list. Use [Default] Access List for Unknown Clients This checkbox defines the behaviour of the system in case the Remote client could not be authenticated unknown.

If selected, then the list of accessible OPC Servers for [Default] entry will be used all fields have [Default] value for this entry on Remote Clients list. Otherwise, access is refused and the empty list is returned to the Client-Side Gateway Configuration Tool. Add Adds a new entry into the list of Remote clients. Opens a new window. Delete Deletes the currently selected entry from the list of Remote clients. Select the applicable checkboxes to determine whether the corresponding OPC server is accessible to the currently selected Remote client or not.

Changing the selected entry in the list of Remote clients can be done by selecting the Edit button. In either situation, the Edit Remote client host info window Figure 19 is displayed.

Components of that window are described on Table 7. Notes: The [Default] entry on Remote clients list cannot be edited or deleted. All fields selected for use for authentication, must have non-empty values. Option is disabled if the IP address checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab.

If the Host name option is disabled, click on this button to enable it. A value can then be entered into the Host name field. A second click to this button will retrieve the IP Address. Note: This can be time consuming. While processing, the button will be disabled and its text will be changed to Getting. Host Name Fully qualified Host name of Remote client.

Option is disabled if the Host name checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the IP address option is disabled, click on this button to enable it. A value can then be entered into the IP address field.

A second click to this button will retrieve the Host name. Note: This can be time-consuming. Note: User account, under which the OPC client application runs, might be different than the currently logged-on-to remote host user.

Select from the list of connections that were opened Click on this button to open the Select Remote Client info from the list of connections window Figure The window opened by this button contains a list of Remote client authentication data that can be selected and used to fill corresponding fields.

Entering Remote client host information by selecting from the list of connections ensures that the authentication fields have correct values and the configuration process is sped up. Notes: If no connections have yet been accepted by SSC, the connections list is empty and the button is disabled.

OK Saves changes in memory and closes the window. Note: Changes will take effect when either the OK or Apply button on the main window is selected. Advanced settings are stored in the tunneller. Level Log level. It does not disable logging to file.

Overwrite Old File If this checkbox is selected, the previous log files copy is not made. Otherwise, backup is made named as tunneller.

Commit All Log File Writes If this checkbox is selected, all information written to the log file is immediately written to disk instead of being cached. Note: To successfully communicate, the port number configured on Server-Side Component must match with the port number configured on Client-Side Component. If this option is changed, the Tunneller service must be restarted.

Timeout Communication timeout in seconds. If the CSC version is 3. Retries Number of retries after communication failure. Maximum Size of Queue Maximum number of outgoing messages on the communication messages queue.

See Update of large amount of items fails in the Troubleshooting section for more details. The default value is 5.

Session Timeout Used when communication failures occur. During the Session Timeout period, the connection to the end OPC server is not closed and the session stays open i. When the Client-Side Component reconnects to the Server-Side Component, that session can be reused so that recovering does not take a long time. This option should have the same value as the ReconnectTime option configured on Client-Side Component versions prior to 3. Only One Connection If this checkbox is selected, it specifies that only one connection at a time is created to the OPC server.

Usually this checkbox should be selected. It takes effect in two cases. If a communication error occurs, then the session is waiting for reconnection for a defined session timeout period. But, the Client- Side Component can send a request to create a new session at that time. If this option is selected, then the Server-Side first waits for disconnection from the OPC server and deletion of the previous session, and then only creates a new session. Otherwise, for a session timeout period, more than one open connection to the end OPC server can exist.

On the Windows box, only one instance of the Client-Side Component can run at the same time. In this case, multiple instances can run on the client-side and the Only One Connection checkbox must be cleared.

Otherwise, OpcEnum service is used. Refer to Table 9 for those settings that can be overridden. Its value is used when processing a shutdown request from OPC server: SSC waits during this time for the current operation if there is any completion before disconnecting. If an CSC version prior to 3. This default value can be changed by adding the ProcessingTimeout option into the tunneller.

For connections from a CSC version prior to 3. The ReconnectTime option is configured in the TunnellerOpts. The default value is 0 indicating that no reconnection attempts will be performed. A connection is established and normal communication is underway.

A failure is detected either a broken link is detected or a Communication Timeout has been passed. If the SSC is still active i. Note: For versions prior to 3. In version 3. If the reconnect command succeeds i.

At no time during this phase has Tunneller changed the item values, qualities, or timestamps. All alarms and events received during communication failure are buffered as long as the SSC Session Timeout has not expired and will be sent upon reconnection.

If the reconnect command fails, Tunneller CSC waits for the delay defined by the ReconnectDelay parameter default value is 10 seconds and retries a reconnection during the time period defined by the ReconnectTime parameter default value is 0 seconds. If reconnection could not be established during ReconnectTime, or communication is established but the Server-Side Component does not have a matching session in correct state, Tunneller will start full connection attempts.

At this point, Tunneller will set all of its items qualities to bad informing the end OPC client that a failure has occurred. Any items that had their qualities set to bad will have their qualities set to good only when a new value is received for the item.

If the connect command fails it will re-try the full connect command until it either succeeds or the end OPC client disconnects from the Tunnelled ProgID. Delay between retries is defined by the ConnectDelay option. In Tunneller SSC version 3. If no connection is re-established, any session state information on the SSC will be removed after the configurable time period defined by the Session Timeout. SSC will disconnect from the end OPC server immediately after the normal disconnection of CSC, or when the session has timed out defined by the Session Timeout parameter in the tunneller.

These values are used by Tunneller when sending and receiving data on the network. Problem: Network Link is Broken If the network link is broken, the time it takes Tunneller to detect the break depends on where the link broke. If it is the local connection, the detection will be quick. If the break occurs within the network e. The detection also depends on network usage. If the OPC client is not sending or receiving data for extended periods, Tunneller will not detect that the link is broken until communication resumes.

Note that if the Use Remote Status checkbox is selected, sending and receiving data will happen at least as frequently as the OPC client calls GetStatus. The longer the timeout value, the longer failure detection will take. A longer time also causes the responsiveness of Tunneller to go down because more time is spent testing the link. The retry value is used when the network itself has problems but the link to the SSC is maintained.

This could be because of a bad connection or interference caused by electrical equipment. If the network was unable to get the command to its destination because of a network problem, it will retry sending the command. However, many retry times are needed i. For example, adding a large number of items. CSC waits for Processing Timeout before detecting operation as failed. For example, if the remote OPC server returns an error result code for an update history call, additional attempts to update will not be made.

The result will be returned to the OPC client as is. The AddItems call can be retried, but it is configured using different option: the AddItemRetries parameter defined in the TunnellerOpts. Problem: Timeout Expired When running under normal conditions, default timeout and retry values are acceptable. When an unusually long command is executed e. When Communication Timeout elapses, the network link will be considered failed and Tunneller will start the reconnect procedure.

If reconnection is not established during the time defined by ReconnectTime parameter set in TunnellerOPts.

The Processing Timeout value must be set to allow the longest expected command. The Communication Timeout can come into effect when the command being sent is very long and the network has a low ability to transfer data.

The Communication Retry Attempts parameter can come into effect when network communication is not reliable. Increasing the retry amount allows the network link to continue when otherwise it would have been considered as failed. Note: If processing timeout occurs while running an add items request, by using the MaxAddMessage parameter configured in the TunnellerOpts.

Even if the OPC client adds items by small portions so that each initial add item request does not take a long time, this option can be important if the total number of added items is considerable, when the Client-Side Component establishes reconnection to the Server-Side Component without disconnection of the OPC client.

If the connection between the Client-Side and Server-Side components is closed due to some reason e. If there is any call to the OPC server in process, it waits until it is finished while Processing Timeout is not elapsed. Disconnects from OPC server. Reconnection occurs with certain delay after disconnection, which is 10 times the ConnectDelay defined by the CSC. In most cases this delay is enough for the remote OPC server to stop and be ready to start again.

If the add operation fails, a certain number of retries are performed. If all of the retries fail, or if the items are partially added some items are added and some are not , then the CSC will not perform any more attempts. It is recommended that you set this period to a value that is large enough to avoid eventual impact on the ongoing communication. Note: When upgrading from a version prior to 3. If the parameter is not present in the options file, it can be added manually, as follows: 1.

In the TunnellerOpts. Save the file and then restart the CSC service. Therefore, ORB requires that failover conditions be configured through watchdog tags i.

The client may subscribe to and receive conditional events, but cannot acknowledge them, request a refresh, or otherwise interact with the state of a condition. OPC DA 3. The last set of sampling rate and buffering parameters set apply to all of the clients.

Also addressed here are some of the most common problems encountered, and questions asked, while using this OPC server. This causes Pi to validate and add all tags in one group at a time rather than one tag at a time, resulting in significant improvements in time and network bandwidth used when initializing.

Solution: Verify that you have a valid network connection. Verify that the timeouts are set to a length of time that will allow the longest expected communication to complete. Often this is not set high enough causing Tunneller to keep re-trying commands. Why am I still receiving a good status from Tunneller?

Solution: Tunneller is set to use its own status instead of the remote OPC servers status. Set Tunneller to use either of the remote status options. When these are set, Tunneller will return a failed status if the end OPC server has failed or is unreachable.

Solution: This can be caused by: A firewall is stopping network traffic. There is a physical disconnection between the two computers on the network. The computer on the remote side is not powered on. The SSC is not running on the remote computer. The remote OPC server has returned a browse error. Browsing does not return anything Problem: I get nothing returned when browsing.

The end OPC server does not support browsing. A firewall is stopping network traffic. Tunneller is looking for the remote Tunneller on a port different than the one on which the remote Tunneller is configured.

Solution: Tunneller does its best to limit the network traffic. When an OPC client makes the above calls, they are grouped together into one call across the network. If any one of the above calls fail in the end OPC server, it is returned as a general error in either the AddItems return code or the ValidateItems return code.

To see the specific error look in the SSC log. What is the problem? This may be especially true if you are using a low-bandwidth network connection. Try adjusting the Processing and Communication Timeout periods or the number of retries in the Client-Side Configuration Utility for the particular connection.

Disconnect and then reconnect to the server. Getting incorrect values of 0 Problem: Why am I getting incorrect values of 0 when I first add items through Tunneller? Solution: When an item is first added to Tunneller there will be at least one scan interval time where it does not have a value supplied by the end OPC server. In this time, it may happen that the end OPC client requires an update of all the items that have been added.

If this is the case, the item with the invalid value may be sent to the client. To not have Tunneller send any items that have never been updated, set the AllowInitialUpdate option in the TunnellerOpts.

Fail to add items on first try Problem: Tunneller seems to fail adding items on the first try. Tunneller is often able to start faster than an OPC server. If this is the case, Tunneller may try to add items to an OPC server that is still in the start-up process and unable to accept an add request. There are a number of ways to alleviate this situation.

First, try the PostConnectDelay option in the Tunneller. Setting this value will cause a delay after connecting before any other operation can take place including adding items. The second way is configuring Tunneller to retry adding items several times if it fails. AddItemDelay delay between two attempts in milliseconds. This will cause Tunneller to start after the end OPC server. The last option is to have an external batch file that starts the OPC server then waits an applicable amount of time before starting Tunneller.

Update of large amount of items fails Problem: Tunneller fails to update a large number of DA items. At the same time, timestamps appear to fall behind compared to a directly connected client.

By default, its value is 5. When the number of messages to be sent from SSC to CSC in the queue of messages exceeds this maximum, Tunneller stores does not create new update message, but stores the latest updates for subscriptions in a cache.

Note that there is no buffering of values and each update coming from the end OPC server rewrites the previous update.

When the queue allows, it forms a new update message containing the latest updates that were not sent, and sends them. The final effect will be equivalent to the reducing of the update rate. As a result some intermediate update data will be missing. Adding multiple items causes present items to go bad Problem: When new items are added, quality for items previously added for a short period of time become bad.

If its value is set to 0, then this problem will not occur. Tunneller does not work on Stratus box Problem: When switching from primary hardware to secondary hardware on a Stratus box during installation or during normal operation, Tunneller does not function properly. Solution: Re-install Tunneller using the Custom installation type and select the Installing on a Stratus system checkbox.

That will disable checking for a hardware license key and the algorithm of software licensing will be adjusted taking into account the Stratus box features. Notes: To provide correct functioning of software licensing, the generation of software license request and installation of the software license received from MatrikonOPC should be done when Stratus runs under the same active hardware configuration. Check to see if the given client access is granted for desired OPC servers.

Solution: Probably user-impersonation functionality is turned on in the Server-Side Component. Tunneller returns different set of historical data when connection to remote OPC Server is made via Tunneller and start or end time is defined as relative time Problem: If start or end data is given in relative format for a historical read request, and the connection to a remote OPC HDA server is made via Tunneller, the Read History request returns a set of data different than it would be if returned at direct connection.

Solution: The point is that time values given in relative format for example, NOW are interpreted and converted by the Tunneller Client-Side Component. Therefore, if the system time on the Client-Side and the Server-Side is not synchronized, connection via Tunneller will cause a different data set to be returned compared to that of a direct connection between the OPC client and the remote OPC server.

Solution: The cause of this problem is that the shell Upgrade the shell Note: A file named ie4shlnt. It can also be found within an install package for Microsoft Internet Explorer version 6. Note: This is applicable for ORB versions prior to 3. This can be dangerous to your computer so do so at your own risk.

If it is not possible to configure the client application to such a filter, the following steps will configure the MatrikonOPC Tunneller SSC to override any subscription filter used, and disable the subscription to condition events. Open the tunneller. Find the section marked [AlarmsAndEvents]. When no traffic is exchanged within a period of time, the SSC attempts to check the connection to the source OPC DA server, and will disconnect and reconnect to the server to rebuild all of the group subscriptions in an effort to get the requested data moving again.

This is an option that can be disabled by the following steps: 1. Open the Services control panel by choosing Run from the Start menu, and typing in services. Right-click your mouse on the entry.

Select Restart from the displayed menu. Set the value to These instructions may be used to set or reset the settings manually. Licensing Most MatrikonOPC products require that some form of licensing criteria be met for it to function correctly. MatrikonOPC Tunneller supports both software and hardware licensing. Starting with Tunneller version 3. For all new installations, software licenses will be of a different type than the ones used in previous versions.

For upgrades from older versions, the existing software license will be still valid and therefore re- licensing is not required. There is no extra charge from MatrikonOPC for calling their after-hours support number. The server supports the following locales for result code translation: US English 0x System default 0x User default 0x Neutral 0x The server allows the client to set the client name for each connection.

The server supports the shutdown event notification client-side interface. Conditional events are subscribe only. The events will be received, but the Acknowledge, Refresh, State, and Condition Name browsing functions are not supported. Data Access 3. Note: As part of the installation process, the MatrikonOPC Analyzer tool is installed and used to detect the system settings that affect the use of this software.

No information is communicated back to Matrikon. Information is stored on this system only for future use by MatrikonOPC Support to assist with troubleshooting, if required. Tunneller should be installed on all machines where the user wishes to have communication between an OPC client and an OPC server.

There are three parts to a Tunneller install: 1. Notes: Installing Tunneller may require you to restart the computer. To limit the need for a restart, please limit the activity of existing OPC products i.

If a firewall is present and configured between the two computers using Tunneller to communicate, please ensure that the firewall will not block TCP communication on the desired port before continuing.

In previous versions of Tunneller, a mixed installation option was available allowing an installation on a computer where Tunneller 1. Mixed installation is no longer available. Please uninstall previous versions of Tunneller prior to installation of the current version; if not uninstalled, Tunneller 2. To install the software: 1. Note: The Version number located in the lower left corner indicates the version number of the software that is being installed.

The text X. X will be replaced with the specific product version. Click on the Next button. The License Agreement screen Figure 23 appears. Notes: From the License Agreement screen, you have the option of clicking on the Back button to return to the Welcome screen, or selecting the I reject the license agreement option. Selecting the I reject the license agreement option button disables the Next button so your options are to return to the previous screen, cancel the install by clicking on the Cancel button, or select the I accept the license agreement option button enabling you to proceed through the install.

From this point onward, the Back button is available allowing you to return to the previous screen or screens. Read the End-User License Agreement, using the scroll bar to view the entire message. Select the I accept the license agreement option button. The Setup Type screen Figure 24 appears. Select the type of setup to be performed. Note: Matrikon recommends that you select the Complete Setup option. The Destination Folder screen Figure 25 appears.

Select the folder in which to install Tunneller. The Start Menu screen Figure 26 appears. Select the Start Menu group and specify whether you want shortcuts created only for yourself, or for all users, by selecting the applicable option button.

The Licensing screen Figure 27 appears. Select the applicable licensing option. Otherwise, ignore this step and the next and go to step If neither of those operating systems are detected, ignore this step and proceed to step By default, the Adjust the optimization settings automatically checkbox is selected. For more information, refer to the Troubleshooting section in this Users Manual i. The Ready to Install screen Figure 30 appears. MatrikonOPC Tunneller features lossless data compression, which reduces load on networks and saves money when paying per MB of data.

Timeouts and Disconnections Plagued with timeouts? Need recovery faster than the unconfigurable 6 minute timeout that comes with DCOM? Encryption can be selected from 64, 96, or bit AES. Easy Configuration Depending on your system, configuring DCOM just to the point of getting communication can take days! OPC Tunneller reduces your integration time to minutes!

Start communicating! Fast, easy and reliable Optimized for low-bandwidth infrastructures Uses only a single port. Facebook LinkedIn Twitter. April 08, MatrikonOPC.

 

Matrikonopc tunneller download.MatrikonOPC Tunneller User Manual

 
WebMar 16,  · Click on the Next button. The Installing MatrikonOPC Tunneller screen appears, installation begins, and the product files are copied to the computer. When the . WebDCOM is the #1 most common OPC Configuration issue that OPC Technology users face. OPC Tunnelling Products such as MatrikonOPC Tunneller offer you an easy way to . WebUsing the link below to download MatrikonOPC Tunneller from the developer’s website was possible when we last checked. We cannot confirm if there is a free download of . WebOct 24,  · Download popular programs, drivers and latest updates easily. This program helps you communicate between networked computers. It helps you configure server .

Ей предстояло узнать это совсем. ГЛАВА 2 На высоте тридцать тысяч футов, над застывшим внизу океаном, Дэвид Беккер грустно смотрел в крохотный овальный иллюминатор самолета «Лирджет-60». Ему сказали, что бортовой телефон вышел из строя, поэтому позвонить Сьюзан не удастся. – Что я здесь делаю? – пробормотал .

WebOPC Client for testing and troubleshooting of any standard OPC Server. It lets the programmer to create robust and highly effective OPC Servers. Network management . WebMar 16,  · Click on the Next button. The Installing MatrikonOPC Tunneller screen appears, installation begins, and the product files are copied to the computer. When the . WebMatrikonOPC Tunneller v Users Manual 10 Connection and Reconnection presents a simple scenario demonstrating how Tunneller reacts to an interrupted network. .

The first found entry in Key mapping is used for the given IP address. Add Key Mapping Once the user has filled the IP address information and encryption key optional , pressing this button will create a new key mapping. If a key mapping containing the specified IP addresses already exists, this button will not be enabled. Update Key Mapping This button is used to update the selected key mapping with the values from fields Encrypt, Encryption key and IP address.

If the values on selected key mapping have not changed, this button will be disabled. OK This button acts exactly in the same way as the Apply button changes are saved. The difference is that after saving of key mappings the dialog window will be closed. Otherwise, its label states Close. Apply This button is enabled if changes to key mappings have been made.

Note: If key mappings were modified, but not saved, and later their previous values are recovered, then the Apply button will be disabled. Table 4 – Encryption Options The encryption level depends on the length of the user-entered encryption key. Encryption keys will be padded out to the appropriate length the greatest number of characters in that range automatically.

For example, a character encryption key will be padded out to 16 characters. Modifications of encryption key mappings become effective immediately on CSC. Computer 1 with IP address Furthermore, the same encryption settings must be used.

If the key mapping on the CSC is: In the first line the IP address is defined exactly. In the second line the range of addresses from In the third line, the subnet mask and address are defined. In such a situation, the first found key is used line with bit encryption. Compression was introduced in version 3. If compression is enabled in an attempt to communicate with an earlier version of the Tunneller SSC then this option is ignored and does not affect communication behaviour.

The compression option is configured in the Client Configuration Tool by selecting the Use Compression check box Figure By default this feature is turned off. On the server side, Remote user to Local user mappings can be configured.

If the entry is found, it takes Local user for that entry and performs impersonation using its domain, user name and password for the thread communicating with the end OPC server. As a result, the end OPC servers can behave differently based on what user is connected, for example restrict access. If impersonation is turned ON, the fields on Impersonation tab page Figure 16 become enabled.

Note: Impersonation can also be turned on or off through the tunneller. Its default value is 0 i. User impersonation mappings can be configured only using the Server- Side Gateway Configuration Tool. The behaviour of the system in case no entry is found for the provided Remote user or the Remote user is not defined this can be possible if older version of Tunneller CSC is connected depends on the state of Use Default account checkbox.

If it is turned OFF, then the connection will be rejected. If it is turned ON, the entry for [Default] Remote user will be used. If at the time when the checkbox is turned ON and no such entry is found, the Edit User Mapping window is opened and the entry will be added.

Local user corresponding to [Default] Remote user can be configured either as a specific local user account or as [Default]. If User Impersonation is turned ON but there are no mappings configured, and the Default Account option is turned OFF, a warning message pops up when changes are applied. To add a new entry into the User mappings: 1. The new Edit User mapping window Figure 17 is displayed. Enter the Remote user, Local user, and Password.

The Local user field requires the user name only. Select the OK button. Note: All impersonation mappings including passwords are stored in the configuration file using encryption. The currently selected entry can be edited by double-clicking your mouse on the entry or by selecting the Edit button. To delete an entry or entries from the User mappings, select one or more entries and click on the Delete button.

Each Remote client can have a configured list of accessible OPC servers. If the Remote client is unknown i. Settings for what fields are used to authenticate the Remote client and what Remote clients can access which OPC servers, are configured using the Access Lists tab Figure Components of this tab are described in Table 6. Starting in version 3. That provides functionality to control access rights per remote user at the OPC Items level.

Therefore, if licensing conditions are changed, the Server-Side Gateway Configuration Tool should be restarted for changes to take effect. At least one checkbox must be checked. Remote Clients The list of entries authenticating Remote clients. The number of visible columns depends on the selected Authenticate Remote client by checkboxes. Note: For each combination of selected Authenticate Remote client by checkboxes, separate lists are stored on the Remote clients list. Use [Default] Access List for Unknown Clients This checkbox defines the behaviour of the system in case the Remote client could not be authenticated unknown.

If selected, then the list of accessible OPC Servers for [Default] entry will be used all fields have [Default] value for this entry on Remote Clients list. Otherwise, access is refused and the empty list is returned to the Client-Side Gateway Configuration Tool. Add Adds a new entry into the list of Remote clients. Opens a new window. Delete Deletes the currently selected entry from the list of Remote clients. Select the applicable checkboxes to determine whether the corresponding OPC server is accessible to the currently selected Remote client or not.

Changing the selected entry in the list of Remote clients can be done by selecting the Edit button. In either situation, the Edit Remote client host info window Figure 19 is displayed. Components of that window are described on Table 7. Notes: The [Default] entry on Remote clients list cannot be edited or deleted. All fields selected for use for authentication, must have non-empty values. Option is disabled if the IP address checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab.

If the Host name option is disabled, click on this button to enable it. A value can then be entered into the Host name field. A second click to this button will retrieve the IP Address. Note: This can be time consuming. While processing, the button will be disabled and its text will be changed to Getting.

Host Name Fully qualified Host name of Remote client. Option is disabled if the Host name checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the IP address option is disabled, click on this button to enable it. A value can then be entered into the IP address field.

A second click to this button will retrieve the Host name. Note: This can be time-consuming. Note: User account, under which the OPC client application runs, might be different than the currently logged-on-to remote host user. Select from the list of connections that were opened Click on this button to open the Select Remote Client info from the list of connections window Figure The window opened by this button contains a list of Remote client authentication data that can be selected and used to fill corresponding fields.

Entering Remote client host information by selecting from the list of connections ensures that the authentication fields have correct values and the configuration process is sped up. Notes: If no connections have yet been accepted by SSC, the connections list is empty and the button is disabled. OK Saves changes in memory and closes the window. Note: Changes will take effect when either the OK or Apply button on the main window is selected.

Advanced settings are stored in the tunneller. Level Log level. It does not disable logging to file. Overwrite Old File If this checkbox is selected, the previous log files copy is not made. Otherwise, backup is made named as tunneller. Commit All Log File Writes If this checkbox is selected, all information written to the log file is immediately written to disk instead of being cached.

Note: To successfully communicate, the port number configured on Server-Side Component must match with the port number configured on Client-Side Component.

If this option is changed, the Tunneller service must be restarted. Timeout Communication timeout in seconds. If the CSC version is 3. Retries Number of retries after communication failure. Maximum Size of Queue Maximum number of outgoing messages on the communication messages queue. See Update of large amount of items fails in the Troubleshooting section for more details. The default value is 5.

Session Timeout Used when communication failures occur. During the Session Timeout period, the connection to the end OPC server is not closed and the session stays open i. When the Client-Side Component reconnects to the Server-Side Component, that session can be reused so that recovering does not take a long time.

This option should have the same value as the ReconnectTime option configured on Client-Side Component versions prior to 3.

Only One Connection If this checkbox is selected, it specifies that only one connection at a time is created to the OPC server. Usually this checkbox should be selected. It takes effect in two cases. If a communication error occurs, then the session is waiting for reconnection for a defined session timeout period. But, the Client- Side Component can send a request to create a new session at that time.

If this option is selected, then the Server-Side first waits for disconnection from the OPC server and deletion of the previous session, and then only creates a new session. Otherwise, for a session timeout period, more than one open connection to the end OPC server can exist.

On the Windows box, only one instance of the Client-Side Component can run at the same time. In this case, multiple instances can run on the client-side and the Only One Connection checkbox must be cleared. Otherwise, OpcEnum service is used. Refer to Table 9 for those settings that can be overridden.

Its value is used when processing a shutdown request from OPC server: SSC waits during this time for the current operation if there is any completion before disconnecting. If an CSC version prior to 3. This default value can be changed by adding the ProcessingTimeout option into the tunneller. For connections from a CSC version prior to 3. The ReconnectTime option is configured in the TunnellerOpts. The default value is 0 indicating that no reconnection attempts will be performed.

A connection is established and normal communication is underway. A failure is detected either a broken link is detected or a Communication Timeout has been passed. If the SSC is still active i. Note: For versions prior to 3. In version 3.

If the reconnect command succeeds i. At no time during this phase has Tunneller changed the item values, qualities, or timestamps. All alarms and events received during communication failure are buffered as long as the SSC Session Timeout has not expired and will be sent upon reconnection. If the reconnect command fails, Tunneller CSC waits for the delay defined by the ReconnectDelay parameter default value is 10 seconds and retries a reconnection during the time period defined by the ReconnectTime parameter default value is 0 seconds.

If reconnection could not be established during ReconnectTime, or communication is established but the Server-Side Component does not have a matching session in correct state, Tunneller will start full connection attempts. At this point, Tunneller will set all of its items qualities to bad informing the end OPC client that a failure has occurred. Any items that had their qualities set to bad will have their qualities set to good only when a new value is received for the item.

If the connect command fails it will re-try the full connect command until it either succeeds or the end OPC client disconnects from the Tunnelled ProgID.

Delay between retries is defined by the ConnectDelay option. In Tunneller SSC version 3. If no connection is re-established, any session state information on the SSC will be removed after the configurable time period defined by the Session Timeout. SSC will disconnect from the end OPC server immediately after the normal disconnection of CSC, or when the session has timed out defined by the Session Timeout parameter in the tunneller.

These values are used by Tunneller when sending and receiving data on the network. Problem: Network Link is Broken If the network link is broken, the time it takes Tunneller to detect the break depends on where the link broke. If it is the local connection, the detection will be quick.

If the break occurs within the network e. The detection also depends on network usage. If the OPC client is not sending or receiving data for extended periods, Tunneller will not detect that the link is broken until communication resumes. Note that if the Use Remote Status checkbox is selected, sending and receiving data will happen at least as frequently as the OPC client calls GetStatus. The longer the timeout value, the longer failure detection will take.

A longer time also causes the responsiveness of Tunneller to go down because more time is spent testing the link. The retry value is used when the network itself has problems but the link to the SSC is maintained.

This could be because of a bad connection or interference caused by electrical equipment. If the network was unable to get the command to its destination because of a network problem, it will retry sending the command.

However, many retry times are needed i. For example, adding a large number of items. CSC waits for Processing Timeout before detecting operation as failed. For example, if the remote OPC server returns an error result code for an update history call, additional attempts to update will not be made.

The result will be returned to the OPC client as is. The AddItems call can be retried, but it is configured using different option: the AddItemRetries parameter defined in the TunnellerOpts. Problem: Timeout Expired When running under normal conditions, default timeout and retry values are acceptable. When an unusually long command is executed e. When Communication Timeout elapses, the network link will be considered failed and Tunneller will start the reconnect procedure.

If reconnection is not established during the time defined by ReconnectTime parameter set in TunnellerOPts. The Processing Timeout value must be set to allow the longest expected command.

The Communication Timeout can come into effect when the command being sent is very long and the network has a low ability to transfer data. The Communication Retry Attempts parameter can come into effect when network communication is not reliable.

Increasing the retry amount allows the network link to continue when otherwise it would have been considered as failed. Note: If processing timeout occurs while running an add items request, by using the MaxAddMessage parameter configured in the TunnellerOpts. Even if the OPC client adds items by small portions so that each initial add item request does not take a long time, this option can be important if the total number of added items is considerable, when the Client-Side Component establishes reconnection to the Server-Side Component without disconnection of the OPC client.

If the connection between the Client-Side and Server-Side components is closed due to some reason e. If there is any call to the OPC server in process, it waits until it is finished while Processing Timeout is not elapsed. Disconnects from OPC server. Reconnection occurs with certain delay after disconnection, which is 10 times the ConnectDelay defined by the CSC.

In most cases this delay is enough for the remote OPC server to stop and be ready to start again. If the add operation fails, a certain number of retries are performed. If all of the retries fail, or if the items are partially added some items are added and some are not , then the CSC will not perform any more attempts. It is recommended that you set this period to a value that is large enough to avoid eventual impact on the ongoing communication. Note: When upgrading from a version prior to 3.

If the parameter is not present in the options file, it can be added manually, as follows: 1. In the TunnellerOpts. Save the file and then restart the CSC service. Therefore, ORB requires that failover conditions be configured through watchdog tags i. The client may subscribe to and receive conditional events, but cannot acknowledge them, request a refresh, or otherwise interact with the state of a condition. OPC DA 3. The last set of sampling rate and buffering parameters set apply to all of the clients.

Also addressed here are some of the most common problems encountered, and questions asked, while using this OPC server. This causes Pi to validate and add all tags in one group at a time rather than one tag at a time, resulting in significant improvements in time and network bandwidth used when initializing. Solution: Verify that you have a valid network connection. Verify that the timeouts are set to a length of time that will allow the longest expected communication to complete.

Often this is not set high enough causing Tunneller to keep re-trying commands. Why am I still receiving a good status from Tunneller? Solution: Tunneller is set to use its own status instead of the remote OPC servers status.

Set Tunneller to use either of the remote status options. When these are set, Tunneller will return a failed status if the end OPC server has failed or is unreachable.

Solution: This can be caused by: A firewall is stopping network traffic. There is a physical disconnection between the two computers on the network. The computer on the remote side is not powered on. The SSC is not running on the remote computer. The remote OPC server has returned a browse error. Browsing does not return anything Problem: I get nothing returned when browsing. The end OPC server does not support browsing. A firewall is stopping network traffic.

Tunneller is looking for the remote Tunneller on a port different than the one on which the remote Tunneller is configured. Solution: Tunneller does its best to limit the network traffic. When an OPC client makes the above calls, they are grouped together into one call across the network.

If any one of the above calls fail in the end OPC server, it is returned as a general error in either the AddItems return code or the ValidateItems return code. To see the specific error look in the SSC log. What is the problem? This may be especially true if you are using a low-bandwidth network connection.

Try adjusting the Processing and Communication Timeout periods or the number of retries in the Client-Side Configuration Utility for the particular connection. Disconnect and then reconnect to the server. Getting incorrect values of 0 Problem: Why am I getting incorrect values of 0 when I first add items through Tunneller?

Solution: When an item is first added to Tunneller there will be at least one scan interval time where it does not have a value supplied by the end OPC server. In this time, it may happen that the end OPC client requires an update of all the items that have been added.

If this is the case, the item with the invalid value may be sent to the client. To not have Tunneller send any items that have never been updated, set the AllowInitialUpdate option in the TunnellerOpts.

Fail to add items on first try Problem: Tunneller seems to fail adding items on the first try. Tunneller is often able to start faster than an OPC server. If this is the case, Tunneller may try to add items to an OPC server that is still in the start-up process and unable to accept an add request. There are a number of ways to alleviate this situation.

First, try the PostConnectDelay option in the Tunneller. Setting this value will cause a delay after connecting before any other operation can take place including adding items. The second way is configuring Tunneller to retry adding items several times if it fails. AddItemDelay delay between two attempts in milliseconds. This will cause Tunneller to start after the end OPC server. The last option is to have an external batch file that starts the OPC server then waits an applicable amount of time before starting Tunneller.

Update of large amount of items fails Problem: Tunneller fails to update a large number of DA items. At the same time, timestamps appear to fall behind compared to a directly connected client.

By default, its value is 5. When the number of messages to be sent from SSC to CSC in the queue of messages exceeds this maximum, Tunneller stores does not create new update message, but stores the latest updates for subscriptions in a cache. Note that there is no buffering of values and each update coming from the end OPC server rewrites the previous update.

When the queue allows, it forms a new update message containing the latest updates that were not sent, and sends them. The final effect will be equivalent to the reducing of the update rate. As a result some intermediate update data will be missing. Adding multiple items causes present items to go bad Problem: When new items are added, quality for items previously added for a short period of time become bad.

If its value is set to 0, then this problem will not occur. Tunneller does not work on Stratus box Problem: When switching from primary hardware to secondary hardware on a Stratus box during installation or during normal operation, Tunneller does not function properly.

Solution: Re-install Tunneller using the Custom installation type and select the Installing on a Stratus system checkbox. That will disable checking for a hardware license key and the algorithm of software licensing will be adjusted taking into account the Stratus box features. Notes: To provide correct functioning of software licensing, the generation of software license request and installation of the software license received from MatrikonOPC should be done when Stratus runs under the same active hardware configuration.

Check to see if the given client access is granted for desired OPC servers. Solution: Probably user-impersonation functionality is turned on in the Server-Side Component. Tunneller returns different set of historical data when connection to remote OPC Server is made via Tunneller and start or end time is defined as relative time Problem: If start or end data is given in relative format for a historical read request, and the connection to a remote OPC HDA server is made via Tunneller, the Read History request returns a set of data different than it would be if returned at direct connection.

Solution: The point is that time values given in relative format for example, NOW are interpreted and converted by the Tunneller Client-Side Component. Therefore, if the system time on the Client-Side and the Server-Side is not synchronized, connection via Tunneller will cause a different data set to be returned compared to that of a direct connection between the OPC client and the remote OPC server.

Solution: The cause of this problem is that the shell Upgrade the shell Note: A file named ie4shlnt. It can also be found within an install package for Microsoft Internet Explorer version 6. Note: This is applicable for ORB versions prior to 3. This can be dangerous to your computer so do so at your own risk.

If it is not possible to configure the client application to such a filter, the following steps will configure the MatrikonOPC Tunneller SSC to override any subscription filter used, and disable the subscription to condition events.

Open the tunneller. Find the section marked [AlarmsAndEvents]. When no traffic is exchanged within a period of time, the SSC attempts to check the connection to the source OPC DA server, and will disconnect and reconnect to the server to rebuild all of the group subscriptions in an effort to get the requested data moving again.

This is an option that can be disabled by the following steps: 1. Open the Services control panel by choosing Run from the Start menu, and typing in services. Right-click your mouse on the entry.

Select Restart from the displayed menu. Set the value to These instructions may be used to set or reset the settings manually. Licensing Most MatrikonOPC products require that some form of licensing criteria be met for it to function correctly. MatrikonOPC Tunneller supports both software and hardware licensing. Starting with Tunneller version 3.

For all new installations, software licenses will be of a different type than the ones used in previous versions. For upgrades from older versions, the existing software license will be still valid and therefore re- licensing is not required.

There is no extra charge from MatrikonOPC for calling their after-hours support number. The server supports the following locales for result code translation: US English 0x System default 0x User default 0x Neutral 0x The server allows the client to set the client name for each connection. The server supports the shutdown event notification client-side interface. Conditional events are subscribe only.

The events will be received, but the Acknowledge, Refresh, State, and Condition Name browsing functions are not supported. Data Access 3. Note: As part of the installation process, the MatrikonOPC Analyzer tool is installed and used to detect the system settings that affect the use of this software.

No information is communicated back to Matrikon. Information is stored on this system only for future use by MatrikonOPC Support to assist with troubleshooting, if required.

Tunneller should be installed on all machines where the user wishes to have communication between an OPC client and an OPC server. There are three parts to a Tunneller install: 1. Notes: Installing Tunneller may require you to restart the computer. To limit the need for a restart, please limit the activity of existing OPC products i. If a firewall is present and configured between the two computers using Tunneller to communicate, please ensure that the firewall will not block TCP communication on the desired port before continuing.

It does away with the headaches typically associated with DCOM configuration. No longer are different protocols, security settings or locations a factor when sharing data between computers. Users are provided with more control over the security of their OPC systems. Data sent over satellite and other per-Megabyte connections can be reduced for significant cost savings.

Historical data can be compressed to a size much smaller than the original data, all without any data loss. Cross Domains and Workgroups Authentication difficulties make DCOM connections across different domains or workgroups extremely difficult or impossible. Leap past this limitation with OPC Tunneller.

Essentially, if you can ping the PC, you can get to it with Tunneller. This causes considerable difficulty when communicating over satellite, modems, radio, and other bandwidth-limited communication types. MatrikonOPC Tunneller features lossless data compression, which reduces load on networks and saves money when paying per MB of data.

– Дьявольщина. Джабба начал яростно отдирать каплю остывшего металла. Она отвалилась вместе с содранной кожей.

When removing a Tunneller server connection and recreating it, ensure that any OPC client that has the connection information cached, clears its cache and obtains the new Tunneller server connection information.

Failure to do so may cause unpredictable behaviour. A small portion of Tunneller will be loaded in proc. Support the Shutdown call-back. This is a required interface but some clients do not support it. It must be supported for Tunneller to relay communication failure information. The GetStatus call should be used as a heartbeat mechanism for line failure detection.

Tunneller does not initiate the GetStatus call on its own. The call can be made as often as needed, depending on the required detection level.

Frequent calls at approximately one second will detect a line failure quickly. It will also detect a line that has gone down but has come back immediately. Infrequent calls can allow a momentary interruption to pass but will not detect a prolonged failure until the line is needed by an actual call. The users specific requirements will indicate how often the GetStatus should be called. These options are described in Table 3. Clearing the checkbox will cause any GetStatus call made to Tunneller to be returned immediately with Tunneller’s own status.

This option is available only when the Use Remote Status checkbox has been selected. When selected, this option forces an internally generated GetStatus message to be sent to the end OPC server. However, it returns Tunnellers own status immediately to the calling client, so it is a non-blocking call.

The remote call will be made as close as possible to the rate at which the end OPC client is calling GetStatus on Tunneller. If a communication failure is detected, Tunnellers status will be set to failed. Remote This option is available only when the Use Remote Status checkbox has been selected.

The status of the end OPC server will be returned. If there is a line interruption or some other form of communication failure between the two halves of Tunneller, the calling OPC client may hang and become unresponsive it is a blocking call.

In subsequent GetStatus calls, the status field of the status structure returned by Tunneller will be set to failed. The default time interval value is equal to half of the timeout parameter configured on the tunneller.

For example, adding 15, items can take the OPC server 15 seconds to perform. If the CSC does not receive any message during the time interval set by the Communication Timeout parameter which also has a default value of 3 seconds , the CSC detects communication failure, disconnects from the SSC and tries to reconnect during the time defined in the ReconnectTime parameter in TunnellerOpts.

If reconnection is not successful, then the add items request fails and the failed result is returned to the OPC client. Furthermore, this communication may be further regulated by the use of encryption keys. Since the Server-Side machine contains the data that the Client-Side machine wishes to access, the option to operate in a more secure mode is made available on the Server-Side.

There are two security modes in which Tunneller may operate: Open – no encryption will be used and there is no restriction as to which computers may connect through Tunneller. By default, Tunneller will operate in Open mode. Encrypted – encryption may be used and the user will be able to control which computers are permitted to connect through Tunneller. The information contained in this section is useful for those users who wish to operate in Encrypted mode.

When Open mode is selected Figure 11 , the Encryption tab is disabled and Tunneller communication will not be encrypted. When Encrypted mode is selected, the Encryption tab is enabled Figure 12 , allowing the user to configure key mappings which will regulate Tunneller encryption. Encryption fields are described in Table 4.

On the Tunneller SSC, the encryption key is read when a new communication session is created. Therefore, modifications to key mappings on the SSC will not affect existing connections. To apply modifications on the SSC, connected sessions should be recreated. Recreation of a session can be achieved from the Tunneller CSC. When the OPC client or clients connect again, the modifications will take effect. Alternatively, if a situation occurs such as no access to the OPC client machine, then restarting the Tunneller SSC service will disconnect clients and apply the SS key mappings on start up.

An existing connection will continue to communicate using their old encryption settings until the session has ended. Address can be entered in three different ways: Single IP address is defined exactly. Address range start and end addresses of the range are defined. In this case the key will be used for all IP addresses belonging to the range. In this case if the result of a bitwise AND operation of the CSC hosts address and Mask is equal to the result of bitwise AND operation of Address value and Mask, then the corresponding key will be used for that particular address.

In this case for all hosts belonging to the Using arrows the rightmost bit of Mask can be shifted to the left or to the right. The first click on Get local button changes Address filed to local IP address.

Note that for a subnet mask to be valid, its leftmost bits must be set to ‘1’. Conversely, the rightmost bits in a valid subnet mask must be set to ‘0’, not ‘1’. So all valid subnet masks contain two parts: the left side with all mask bits set to ‘1’ the extended network portion and the right side with all bits set to ‘0’ the host portion. Note that Subnet type entries are sorted in certain order taking into account how many bits define extended network portion, for example: o When this mode is selected, the Encryption tab is disabled.

When the Encryption option is selected, the user can select which computers may connect through Tunneller and may set up encryption. Encrypt When setting up a key mapping, it must be decided if Tunneller communication for the selected IP address will be encrypted. If encryption is desired, check this box; otherwise, ensure it is unchecked. Encryption Key When setting up a key mapping, if encryption will be used for Tunneller communication with that specific IP address or range of addresses, an encryption key may be entered.

An Encryption key may contain letters, numbers, and special characters available on a keyboard. If the Encryption key field is empty, then default hard-coded key will be used. Key Mappings This field will display the user-created key mappings. Key mappings control which computers may connect through Tunneller and contain the encryption keys being employed.

Here IP address can be just single address or range of IP addresses or the subnet mask and address combination. Clicking on a key mapping will fill the current mapping fields with the selected key mapping settings. Note that the list of keys is ordered in the following order: 1.

Single address in ascending order. Address ranges in ascending order of From address. Subnets in ascending order of address value. The first found entry in Key mapping is used for the given IP address. Add Key Mapping Once the user has filled the IP address information and encryption key optional , pressing this button will create a new key mapping.

If a key mapping containing the specified IP addresses already exists, this button will not be enabled. Update Key Mapping This button is used to update the selected key mapping with the values from fields Encrypt, Encryption key and IP address.

If the values on selected key mapping have not changed, this button will be disabled. OK This button acts exactly in the same way as the Apply button changes are saved.

The difference is that after saving of key mappings the dialog window will be closed. Otherwise, its label states Close. Apply This button is enabled if changes to key mappings have been made. Note: If key mappings were modified, but not saved, and later their previous values are recovered, then the Apply button will be disabled. Table 4 – Encryption Options The encryption level depends on the length of the user-entered encryption key. Encryption keys will be padded out to the appropriate length the greatest number of characters in that range automatically.

For example, a character encryption key will be padded out to 16 characters. Modifications of encryption key mappings become effective immediately on CSC. Computer 1 with IP address Furthermore, the same encryption settings must be used. If the key mapping on the CSC is: In the first line the IP address is defined exactly.

In the second line the range of addresses from In the third line, the subnet mask and address are defined. In such a situation, the first found key is used line with bit encryption. Compression was introduced in version 3. If compression is enabled in an attempt to communicate with an earlier version of the Tunneller SSC then this option is ignored and does not affect communication behaviour.

The compression option is configured in the Client Configuration Tool by selecting the Use Compression check box Figure By default this feature is turned off. On the server side, Remote user to Local user mappings can be configured. If the entry is found, it takes Local user for that entry and performs impersonation using its domain, user name and password for the thread communicating with the end OPC server.

As a result, the end OPC servers can behave differently based on what user is connected, for example restrict access. If impersonation is turned ON, the fields on Impersonation tab page Figure 16 become enabled. Note: Impersonation can also be turned on or off through the tunneller. Its default value is 0 i. User impersonation mappings can be configured only using the Server- Side Gateway Configuration Tool. The behaviour of the system in case no entry is found for the provided Remote user or the Remote user is not defined this can be possible if older version of Tunneller CSC is connected depends on the state of Use Default account checkbox.

If it is turned OFF, then the connection will be rejected. If it is turned ON, the entry for [Default] Remote user will be used. If at the time when the checkbox is turned ON and no such entry is found, the Edit User Mapping window is opened and the entry will be added.

Local user corresponding to [Default] Remote user can be configured either as a specific local user account or as [Default].

If User Impersonation is turned ON but there are no mappings configured, and the Default Account option is turned OFF, a warning message pops up when changes are applied. To add a new entry into the User mappings: 1.

The new Edit User mapping window Figure 17 is displayed. Enter the Remote user, Local user, and Password. The Local user field requires the user name only. Select the OK button. Note: All impersonation mappings including passwords are stored in the configuration file using encryption. The currently selected entry can be edited by double-clicking your mouse on the entry or by selecting the Edit button.

To delete an entry or entries from the User mappings, select one or more entries and click on the Delete button. Each Remote client can have a configured list of accessible OPC servers. If the Remote client is unknown i. Settings for what fields are used to authenticate the Remote client and what Remote clients can access which OPC servers, are configured using the Access Lists tab Figure Components of this tab are described in Table 6.

Starting in version 3. That provides functionality to control access rights per remote user at the OPC Items level. Therefore, if licensing conditions are changed, the Server-Side Gateway Configuration Tool should be restarted for changes to take effect. At least one checkbox must be checked. Remote Clients The list of entries authenticating Remote clients.

The number of visible columns depends on the selected Authenticate Remote client by checkboxes. Note: For each combination of selected Authenticate Remote client by checkboxes, separate lists are stored on the Remote clients list. Use [Default] Access List for Unknown Clients This checkbox defines the behaviour of the system in case the Remote client could not be authenticated unknown. If selected, then the list of accessible OPC Servers for [Default] entry will be used all fields have [Default] value for this entry on Remote Clients list.

Otherwise, access is refused and the empty list is returned to the Client-Side Gateway Configuration Tool. Add Adds a new entry into the list of Remote clients. Opens a new window. Delete Deletes the currently selected entry from the list of Remote clients. Select the applicable checkboxes to determine whether the corresponding OPC server is accessible to the currently selected Remote client or not.

Changing the selected entry in the list of Remote clients can be done by selecting the Edit button. In either situation, the Edit Remote client host info window Figure 19 is displayed. Components of that window are described on Table 7. Notes: The [Default] entry on Remote clients list cannot be edited or deleted. All fields selected for use for authentication, must have non-empty values.

Option is disabled if the IP address checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the Host name option is disabled, click on this button to enable it. A value can then be entered into the Host name field. A second click to this button will retrieve the IP Address.

Note: This can be time consuming. While processing, the button will be disabled and its text will be changed to Getting. Host Name Fully qualified Host name of Remote client. Option is disabled if the Host name checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the IP address option is disabled, click on this button to enable it. A value can then be entered into the IP address field.

A second click to this button will retrieve the Host name. Note: This can be time-consuming. Note: User account, under which the OPC client application runs, might be different than the currently logged-on-to remote host user. Select from the list of connections that were opened Click on this button to open the Select Remote Client info from the list of connections window Figure The window opened by this button contains a list of Remote client authentication data that can be selected and used to fill corresponding fields.

Entering Remote client host information by selecting from the list of connections ensures that the authentication fields have correct values and the configuration process is sped up. Notes: If no connections have yet been accepted by SSC, the connections list is empty and the button is disabled.

OK Saves changes in memory and closes the window. Note: Changes will take effect when either the OK or Apply button on the main window is selected. Advanced settings are stored in the tunneller. Level Log level. It does not disable logging to file. Overwrite Old File If this checkbox is selected, the previous log files copy is not made.

Otherwise, backup is made named as tunneller. Commit All Log File Writes If this checkbox is selected, all information written to the log file is immediately written to disk instead of being cached. Note: To successfully communicate, the port number configured on Server-Side Component must match with the port number configured on Client-Side Component.

If this option is changed, the Tunneller service must be restarted. Timeout Communication timeout in seconds. If the CSC version is 3.

Retries Number of retries after communication failure. Maximum Size of Queue Maximum number of outgoing messages on the communication messages queue. See Update of large amount of items fails in the Troubleshooting section for more details. The default value is 5. Session Timeout Used when communication failures occur. During the Session Timeout period, the connection to the end OPC server is not closed and the session stays open i.

When the Client-Side Component reconnects to the Server-Side Component, that session can be reused so that recovering does not take a long time. This option should have the same value as the ReconnectTime option configured on Client-Side Component versions prior to 3. Only One Connection If this checkbox is selected, it specifies that only one connection at a time is created to the OPC server.

Usually this checkbox should be selected. It takes effect in two cases. If a communication error occurs, then the session is waiting for reconnection for a defined session timeout period. But, the Client- Side Component can send a request to create a new session at that time. If this option is selected, then the Server-Side first waits for disconnection from the OPC server and deletion of the previous session, and then only creates a new session.

Otherwise, for a session timeout period, more than one open connection to the end OPC server can exist. On the Windows box, only one instance of the Client-Side Component can run at the same time. In this case, multiple instances can run on the client-side and the Only One Connection checkbox must be cleared. Otherwise, OpcEnum service is used. Refer to Table 9 for those settings that can be overridden. Its value is used when processing a shutdown request from OPC server: SSC waits during this time for the current operation if there is any completion before disconnecting.

If an CSC version prior to 3. This default value can be changed by adding the ProcessingTimeout option into the tunneller. For connections from a CSC version prior to 3. The ReconnectTime option is configured in the TunnellerOpts.

The default value is 0 indicating that no reconnection attempts will be performed. A connection is established and normal communication is underway. A failure is detected either a broken link is detected or a Communication Timeout has been passed. If the SSC is still active i. Note: For versions prior to 3. In version 3.

If the reconnect command succeeds i. At no time during this phase has Tunneller changed the item values, qualities, or timestamps. All alarms and events received during communication failure are buffered as long as the SSC Session Timeout has not expired and will be sent upon reconnection. If the reconnect command fails, Tunneller CSC waits for the delay defined by the ReconnectDelay parameter default value is 10 seconds and retries a reconnection during the time period defined by the ReconnectTime parameter default value is 0 seconds.

If reconnection could not be established during ReconnectTime, or communication is established but the Server-Side Component does not have a matching session in correct state, Tunneller will start full connection attempts. At this point, Tunneller will set all of its items qualities to bad informing the end OPC client that a failure has occurred.

Any items that had their qualities set to bad will have their qualities set to good only when a new value is received for the item. If the connect command fails it will re-try the full connect command until it either succeeds or the end OPC client disconnects from the Tunnelled ProgID.

Delay between retries is defined by the ConnectDelay option. In Tunneller SSC version 3. If no connection is re-established, any session state information on the SSC will be removed after the configurable time period defined by the Session Timeout.

SSC will disconnect from the end OPC server immediately after the normal disconnection of CSC, or when the session has timed out defined by the Session Timeout parameter in the tunneller.

These values are used by Tunneller when sending and receiving data on the network. Problem: Network Link is Broken If the network link is broken, the time it takes Tunneller to detect the break depends on where the link broke. If it is the local connection, the detection will be quick. If the break occurs within the network e.

The detection also depends on network usage. If the OPC client is not sending or receiving data for extended periods, Tunneller will not detect that the link is broken until communication resumes.

Note that if the Use Remote Status checkbox is selected, sending and receiving data will happen at least as frequently as the OPC client calls GetStatus. The longer the timeout value, the longer failure detection will take. A longer time also causes the responsiveness of Tunneller to go down because more time is spent testing the link.

The retry value is used when the network itself has problems but the link to the SSC is maintained. This could be because of a bad connection or interference caused by electrical equipment. If the network was unable to get the command to its destination because of a network problem, it will retry sending the command. However, many retry times are needed i. For example, adding a large number of items.

CSC waits for Processing Timeout before detecting operation as failed. For example, if the remote OPC server returns an error result code for an update history call, additional attempts to update will not be made. The result will be returned to the OPC client as is.

The AddItems call can be retried, but it is configured using different option: the AddItemRetries parameter defined in the TunnellerOpts. Problem: Timeout Expired When running under normal conditions, default timeout and retry values are acceptable. When an unusually long command is executed e. When Communication Timeout elapses, the network link will be considered failed and Tunneller will start the reconnect procedure.

If reconnection is not established during the time defined by ReconnectTime parameter set in TunnellerOPts. The Processing Timeout value must be set to allow the longest expected command. The Communication Timeout can come into effect when the command being sent is very long and the network has a low ability to transfer data.

The Communication Retry Attempts parameter can come into effect when network communication is not reliable. Increasing the retry amount allows the network link to continue when otherwise it would have been considered as failed. Note: If processing timeout occurs while running an add items request, by using the MaxAddMessage parameter configured in the TunnellerOpts. Even if the OPC client adds items by small portions so that each initial add item request does not take a long time, this option can be important if the total number of added items is considerable, when the Client-Side Component establishes reconnection to the Server-Side Component without disconnection of the OPC client.

If the connection between the Client-Side and Server-Side components is closed due to some reason e. If there is any call to the OPC server in process, it waits until it is finished while Processing Timeout is not elapsed.

Disconnects from OPC server. Reconnection occurs with certain delay after disconnection, which is 10 times the ConnectDelay defined by the CSC.

In most cases this delay is enough for the remote OPC server to stop and be ready to start again. If the add operation fails, a certain number of retries are performed. If all of the retries fail, or if the items are partially added some items are added and some are not , then the CSC will not perform any more attempts. It is recommended that you set this period to a value that is large enough to avoid eventual impact on the ongoing communication.

Note: When upgrading from a version prior to 3. If the parameter is not present in the options file, it can be added manually, as follows: 1.

In the TunnellerOpts. Save the file and then restart the CSC service. Therefore, ORB requires that failover conditions be configured through watchdog tags i. The client may subscribe to and receive conditional events, but cannot acknowledge them, request a refresh, or otherwise interact with the state of a condition. OPC DA 3. The last set of sampling rate and buffering parameters set apply to all of the clients. Also addressed here are some of the most common problems encountered, and questions asked, while using this OPC server.

This causes Pi to validate and add all tags in one group at a time rather than one tag at a time, resulting in significant improvements in time and network bandwidth used when initializing. Solution: Verify that you have a valid network connection. Verify that the timeouts are set to a length of time that will allow the longest expected communication to complete. Often this is not set high enough causing Tunneller to keep re-trying commands. Why am I still receiving a good status from Tunneller?

Solution: Tunneller is set to use its own status instead of the remote OPC servers status. Set Tunneller to use either of the remote status options.

When these are set, Tunneller will return a failed status if the end OPC server has failed or is unreachable. Solution: This can be caused by: A firewall is stopping network traffic. There is a physical disconnection between the two computers on the network. The computer on the remote side is not powered on. The SSC is not running on the remote computer.

The remote OPC server has returned a browse error. Browsing does not return anything Problem: I get nothing returned when browsing. The end OPC server does not support browsing. A firewall is stopping network traffic.

Tunneller is looking for the remote Tunneller on a port different than the one on which the remote Tunneller is configured. Solution: Tunneller does its best to limit the network traffic. When an OPC client makes the above calls, they are grouped together into one call across the network. If any one of the above calls fail in the end OPC server, it is returned as a general error in either the AddItems return code or the ValidateItems return code.

To see the specific error look in the SSC log. What is the problem? This may be especially true if you are using a low-bandwidth network connection. Try adjusting the Processing and Communication Timeout periods or the number of retries in the Client-Side Configuration Utility for the particular connection. Disconnect and then reconnect to the server. Users are provided with more control over the security of their OPC systems.

Data sent over satellite and other per-Megabyte connections can be reduced for significant cost savings. Historical data can be compressed to a size much smaller than the original data, all without any data loss.

Cross Domains and Workgroups Authentication difficulties make DCOM connections across different domains or workgroups extremely difficult or impossible. Leap past this limitation with OPC Tunneller. Essentially, if you can ping the PC, you can get to it with Tunneller. This causes considerable difficulty when communicating over satellite, modems, radio, and other bandwidth-limited communication types. MatrikonOPC Tunneller features lossless data compression, which reduces load on networks and saves money when paying per MB of data.

Timeouts and Disconnections Plagued with timeouts? Need recovery faster than the unconfigurable 6 minute timeout that comes with DCOM?

Table 4 – Encryption Options The encryption level depends on the length of the user-entered encryption key. Encryption keys will be padded out to the appropriate length the greatest number of characters in that range automatically.

For example, a character encryption key will be padded out to 16 characters. Modifications of encryption key mappings become effective immediately on CSC. Computer 1 with IP address Furthermore, the same encryption settings must be used.

If the key mapping on the CSC is: In the first line the IP address is defined exactly. In the second line the range of addresses from In the third line, the subnet mask and address are defined. In such a situation, the first found key is used line with bit encryption. Compression was introduced in version 3. If compression is enabled in an attempt to communicate with an earlier version of the Tunneller SSC then this option is ignored and does not affect communication behaviour.

The compression option is configured in the Client Configuration Tool by selecting the Use Compression check box Figure By default this feature is turned off. On the server side, Remote user to Local user mappings can be configured. If the entry is found, it takes Local user for that entry and performs impersonation using its domain, user name and password for the thread communicating with the end OPC server. As a result, the end OPC servers can behave differently based on what user is connected, for example restrict access.

If impersonation is turned ON, the fields on Impersonation tab page Figure 16 become enabled. Note: Impersonation can also be turned on or off through the tunneller. Its default value is 0 i. User impersonation mappings can be configured only using the Server- Side Gateway Configuration Tool. The behaviour of the system in case no entry is found for the provided Remote user or the Remote user is not defined this can be possible if older version of Tunneller CSC is connected depends on the state of Use Default account checkbox.

If it is turned OFF, then the connection will be rejected. If it is turned ON, the entry for [Default] Remote user will be used. If at the time when the checkbox is turned ON and no such entry is found, the Edit User Mapping window is opened and the entry will be added. Local user corresponding to [Default] Remote user can be configured either as a specific local user account or as [Default].

If User Impersonation is turned ON but there are no mappings configured, and the Default Account option is turned OFF, a warning message pops up when changes are applied. To add a new entry into the User mappings: 1. The new Edit User mapping window Figure 17 is displayed. Enter the Remote user, Local user, and Password. The Local user field requires the user name only.

Select the OK button. Note: All impersonation mappings including passwords are stored in the configuration file using encryption. The currently selected entry can be edited by double-clicking your mouse on the entry or by selecting the Edit button. To delete an entry or entries from the User mappings, select one or more entries and click on the Delete button.

Each Remote client can have a configured list of accessible OPC servers. If the Remote client is unknown i. Settings for what fields are used to authenticate the Remote client and what Remote clients can access which OPC servers, are configured using the Access Lists tab Figure Components of this tab are described in Table 6. Starting in version 3. That provides functionality to control access rights per remote user at the OPC Items level.

Therefore, if licensing conditions are changed, the Server-Side Gateway Configuration Tool should be restarted for changes to take effect. At least one checkbox must be checked. Remote Clients The list of entries authenticating Remote clients. The number of visible columns depends on the selected Authenticate Remote client by checkboxes.

Note: For each combination of selected Authenticate Remote client by checkboxes, separate lists are stored on the Remote clients list. Use [Default] Access List for Unknown Clients This checkbox defines the behaviour of the system in case the Remote client could not be authenticated unknown. If selected, then the list of accessible OPC Servers for [Default] entry will be used all fields have [Default] value for this entry on Remote Clients list.

Otherwise, access is refused and the empty list is returned to the Client-Side Gateway Configuration Tool. Add Adds a new entry into the list of Remote clients. Opens a new window. Delete Deletes the currently selected entry from the list of Remote clients. Select the applicable checkboxes to determine whether the corresponding OPC server is accessible to the currently selected Remote client or not.

Changing the selected entry in the list of Remote clients can be done by selecting the Edit button. In either situation, the Edit Remote client host info window Figure 19 is displayed. Components of that window are described on Table 7. Notes: The [Default] entry on Remote clients list cannot be edited or deleted.

All fields selected for use for authentication, must have non-empty values. Option is disabled if the IP address checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the Host name option is disabled, click on this button to enable it. A value can then be entered into the Host name field. A second click to this button will retrieve the IP Address.

Note: This can be time consuming. While processing, the button will be disabled and its text will be changed to Getting. Host Name Fully qualified Host name of Remote client. Option is disabled if the Host name checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the IP address option is disabled, click on this button to enable it. A value can then be entered into the IP address field. A second click to this button will retrieve the Host name. Note: This can be time-consuming.

Note: User account, under which the OPC client application runs, might be different than the currently logged-on-to remote host user. Select from the list of connections that were opened Click on this button to open the Select Remote Client info from the list of connections window Figure The window opened by this button contains a list of Remote client authentication data that can be selected and used to fill corresponding fields.

Entering Remote client host information by selecting from the list of connections ensures that the authentication fields have correct values and the configuration process is sped up. Notes: If no connections have yet been accepted by SSC, the connections list is empty and the button is disabled.

OK Saves changes in memory and closes the window. Note: Changes will take effect when either the OK or Apply button on the main window is selected.

Advanced settings are stored in the tunneller. Level Log level. It does not disable logging to file. Overwrite Old File If this checkbox is selected, the previous log files copy is not made. Otherwise, backup is made named as tunneller. Commit All Log File Writes If this checkbox is selected, all information written to the log file is immediately written to disk instead of being cached. Note: To successfully communicate, the port number configured on Server-Side Component must match with the port number configured on Client-Side Component.

If this option is changed, the Tunneller service must be restarted. Timeout Communication timeout in seconds. If the CSC version is 3. Retries Number of retries after communication failure. Maximum Size of Queue Maximum number of outgoing messages on the communication messages queue. See Update of large amount of items fails in the Troubleshooting section for more details. The default value is 5.

Session Timeout Used when communication failures occur. During the Session Timeout period, the connection to the end OPC server is not closed and the session stays open i. When the Client-Side Component reconnects to the Server-Side Component, that session can be reused so that recovering does not take a long time.

This option should have the same value as the ReconnectTime option configured on Client-Side Component versions prior to 3. Only One Connection If this checkbox is selected, it specifies that only one connection at a time is created to the OPC server. Usually this checkbox should be selected. It takes effect in two cases. If a communication error occurs, then the session is waiting for reconnection for a defined session timeout period. But, the Client- Side Component can send a request to create a new session at that time.

If this option is selected, then the Server-Side first waits for disconnection from the OPC server and deletion of the previous session, and then only creates a new session. Otherwise, for a session timeout period, more than one open connection to the end OPC server can exist. On the Windows box, only one instance of the Client-Side Component can run at the same time. In this case, multiple instances can run on the client-side and the Only One Connection checkbox must be cleared.

Otherwise, OpcEnum service is used. Refer to Table 9 for those settings that can be overridden. Its value is used when processing a shutdown request from OPC server: SSC waits during this time for the current operation if there is any completion before disconnecting. If an CSC version prior to 3. This default value can be changed by adding the ProcessingTimeout option into the tunneller.

For connections from a CSC version prior to 3. The ReconnectTime option is configured in the TunnellerOpts. The default value is 0 indicating that no reconnection attempts will be performed. A connection is established and normal communication is underway. A failure is detected either a broken link is detected or a Communication Timeout has been passed. If the SSC is still active i. Note: For versions prior to 3.

In version 3. If the reconnect command succeeds i. At no time during this phase has Tunneller changed the item values, qualities, or timestamps. All alarms and events received during communication failure are buffered as long as the SSC Session Timeout has not expired and will be sent upon reconnection. If the reconnect command fails, Tunneller CSC waits for the delay defined by the ReconnectDelay parameter default value is 10 seconds and retries a reconnection during the time period defined by the ReconnectTime parameter default value is 0 seconds.

If reconnection could not be established during ReconnectTime, or communication is established but the Server-Side Component does not have a matching session in correct state, Tunneller will start full connection attempts.

At this point, Tunneller will set all of its items qualities to bad informing the end OPC client that a failure has occurred. Any items that had their qualities set to bad will have their qualities set to good only when a new value is received for the item. If the connect command fails it will re-try the full connect command until it either succeeds or the end OPC client disconnects from the Tunnelled ProgID. Delay between retries is defined by the ConnectDelay option. In Tunneller SSC version 3.

If no connection is re-established, any session state information on the SSC will be removed after the configurable time period defined by the Session Timeout. SSC will disconnect from the end OPC server immediately after the normal disconnection of CSC, or when the session has timed out defined by the Session Timeout parameter in the tunneller.

These values are used by Tunneller when sending and receiving data on the network. Problem: Network Link is Broken If the network link is broken, the time it takes Tunneller to detect the break depends on where the link broke. If it is the local connection, the detection will be quick. If the break occurs within the network e. The detection also depends on network usage.

If the OPC client is not sending or receiving data for extended periods, Tunneller will not detect that the link is broken until communication resumes. Note that if the Use Remote Status checkbox is selected, sending and receiving data will happen at least as frequently as the OPC client calls GetStatus.

The longer the timeout value, the longer failure detection will take. A longer time also causes the responsiveness of Tunneller to go down because more time is spent testing the link.

The retry value is used when the network itself has problems but the link to the SSC is maintained. This could be because of a bad connection or interference caused by electrical equipment.

If the network was unable to get the command to its destination because of a network problem, it will retry sending the command. However, many retry times are needed i. For example, adding a large number of items. CSC waits for Processing Timeout before detecting operation as failed. For example, if the remote OPC server returns an error result code for an update history call, additional attempts to update will not be made.

The result will be returned to the OPC client as is. The AddItems call can be retried, but it is configured using different option: the AddItemRetries parameter defined in the TunnellerOpts. Problem: Timeout Expired When running under normal conditions, default timeout and retry values are acceptable. When an unusually long command is executed e. When Communication Timeout elapses, the network link will be considered failed and Tunneller will start the reconnect procedure. If reconnection is not established during the time defined by ReconnectTime parameter set in TunnellerOPts.

The Processing Timeout value must be set to allow the longest expected command. The Communication Timeout can come into effect when the command being sent is very long and the network has a low ability to transfer data. The Communication Retry Attempts parameter can come into effect when network communication is not reliable.

Increasing the retry amount allows the network link to continue when otherwise it would have been considered as failed.

Note: If processing timeout occurs while running an add items request, by using the MaxAddMessage parameter configured in the TunnellerOpts. Even if the OPC client adds items by small portions so that each initial add item request does not take a long time, this option can be important if the total number of added items is considerable, when the Client-Side Component establishes reconnection to the Server-Side Component without disconnection of the OPC client.

If the connection between the Client-Side and Server-Side components is closed due to some reason e. If there is any call to the OPC server in process, it waits until it is finished while Processing Timeout is not elapsed.

Disconnects from OPC server. Reconnection occurs with certain delay after disconnection, which is 10 times the ConnectDelay defined by the CSC. In most cases this delay is enough for the remote OPC server to stop and be ready to start again. If the add operation fails, a certain number of retries are performed. If all of the retries fail, or if the items are partially added some items are added and some are not , then the CSC will not perform any more attempts.

It is recommended that you set this period to a value that is large enough to avoid eventual impact on the ongoing communication. Note: When upgrading from a version prior to 3. If the parameter is not present in the options file, it can be added manually, as follows: 1.

In the TunnellerOpts. Save the file and then restart the CSC service. Therefore, ORB requires that failover conditions be configured through watchdog tags i. The client may subscribe to and receive conditional events, but cannot acknowledge them, request a refresh, or otherwise interact with the state of a condition. OPC DA 3.

The last set of sampling rate and buffering parameters set apply to all of the clients. Also addressed here are some of the most common problems encountered, and questions asked, while using this OPC server. This causes Pi to validate and add all tags in one group at a time rather than one tag at a time, resulting in significant improvements in time and network bandwidth used when initializing.

Solution: Verify that you have a valid network connection. Verify that the timeouts are set to a length of time that will allow the longest expected communication to complete. Often this is not set high enough causing Tunneller to keep re-trying commands.

Why am I still receiving a good status from Tunneller? Solution: Tunneller is set to use its own status instead of the remote OPC servers status. Set Tunneller to use either of the remote status options. When these are set, Tunneller will return a failed status if the end OPC server has failed or is unreachable.

Solution: This can be caused by: A firewall is stopping network traffic. There is a physical disconnection between the two computers on the network. The computer on the remote side is not powered on. The SSC is not running on the remote computer. No longer are different protocols, security settings or locations a factor when sharing data between computers.

Users are provided with more control over the security of their OPC systems. Data sent over satellite and other per-Megabyte connections can be reduced for significant cost savings. Historical data can be compressed to a size much smaller than the original data, all without any data loss. Cross Domains and Workgroups Authentication difficulties make DCOM connections across different domains or workgroups extremely difficult or impossible.

Leap past this limitation with OPC Tunneller. Please visit the Encryption section in user manual to learn more. The user has the option to turn encryption off after the installation is completed. After the installation is complete, it is recommended that you verify the DCOM settings. This configuration varies for different operating systems.

Installation Instructions: To start the installation, please double-click on the installation. If the Licensing Agreement screen is the displayed screen, go to step 5. If the Pre-Requisites screen appears, then click on the Next button to install the listed pre-requisites. This is required to ensure the software will function properly.

After all pre-requisites have been installed, the License Agreement screen appears. Read the Software License Agreement , using the scroll bar to view the entire message. Click on the Next button. The User Credentials for Services screen appears. Enter the User Name , Domain , and Password for the account that all installed Tunneller services will run under.

The selected user: Should not be a personal user account Should not be an administrator account, or an account with elevated privileges. Must have been entered correctly as per the instructions on the screen.

In the second line the range of addresses from In the third line, the subnet mask and address are defined. In such a situation, the first found key is used line with bit encryption. Compression was introduced in version 3. If compression is enabled in an attempt to communicate with an earlier version of the Tunneller SSC then this option is ignored and does not affect communication behaviour.

The compression option is configured in the Client Configuration Tool by selecting the Use Compression check box Figure By default this feature is turned off.

On the server side, Remote user to Local user mappings can be configured. If the entry is found, it takes Local user for that entry and performs impersonation using its domain, user name and password for the thread communicating with the end OPC server.

As a result, the end OPC servers can behave differently based on what user is connected, for example restrict access. If impersonation is turned ON, the fields on Impersonation tab page Figure 16 become enabled. Note: Impersonation can also be turned on or off through the tunneller. Its default value is 0 i. User impersonation mappings can be configured only using the Server- Side Gateway Configuration Tool.

The behaviour of the system in case no entry is found for the provided Remote user or the Remote user is not defined this can be possible if older version of Tunneller CSC is connected depends on the state of Use Default account checkbox.

If it is turned OFF, then the connection will be rejected. If it is turned ON, the entry for [Default] Remote user will be used. If at the time when the checkbox is turned ON and no such entry is found, the Edit User Mapping window is opened and the entry will be added.

Local user corresponding to [Default] Remote user can be configured either as a specific local user account or as [Default]. If User Impersonation is turned ON but there are no mappings configured, and the Default Account option is turned OFF, a warning message pops up when changes are applied. To add a new entry into the User mappings: 1. The new Edit User mapping window Figure 17 is displayed. Enter the Remote user, Local user, and Password. The Local user field requires the user name only.

Select the OK button. Note: All impersonation mappings including passwords are stored in the configuration file using encryption. The currently selected entry can be edited by double-clicking your mouse on the entry or by selecting the Edit button.

To delete an entry or entries from the User mappings, select one or more entries and click on the Delete button. Each Remote client can have a configured list of accessible OPC servers. If the Remote client is unknown i. Settings for what fields are used to authenticate the Remote client and what Remote clients can access which OPC servers, are configured using the Access Lists tab Figure Components of this tab are described in Table 6.

Starting in version 3. That provides functionality to control access rights per remote user at the OPC Items level. Therefore, if licensing conditions are changed, the Server-Side Gateway Configuration Tool should be restarted for changes to take effect. At least one checkbox must be checked.

Remote Clients The list of entries authenticating Remote clients. The number of visible columns depends on the selected Authenticate Remote client by checkboxes. Note: For each combination of selected Authenticate Remote client by checkboxes, separate lists are stored on the Remote clients list. Use [Default] Access List for Unknown Clients This checkbox defines the behaviour of the system in case the Remote client could not be authenticated unknown.

If selected, then the list of accessible OPC Servers for [Default] entry will be used all fields have [Default] value for this entry on Remote Clients list. Otherwise, access is refused and the empty list is returned to the Client-Side Gateway Configuration Tool.

Add Adds a new entry into the list of Remote clients. Opens a new window. Delete Deletes the currently selected entry from the list of Remote clients.

Select the applicable checkboxes to determine whether the corresponding OPC server is accessible to the currently selected Remote client or not. Changing the selected entry in the list of Remote clients can be done by selecting the Edit button. In either situation, the Edit Remote client host info window Figure 19 is displayed. Components of that window are described on Table 7. Notes: The [Default] entry on Remote clients list cannot be edited or deleted. All fields selected for use for authentication, must have non-empty values.

Option is disabled if the IP address checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab. If the Host name option is disabled, click on this button to enable it. A value can then be entered into the Host name field. A second click to this button will retrieve the IP Address. Note: This can be time consuming.

While processing, the button will be disabled and its text will be changed to Getting. Host Name Fully qualified Host name of Remote client. Option is disabled if the Host name checkbox is not selected in the Authenticate Remote client by group of the Access Lists tab.

If the IP address option is disabled, click on this button to enable it. A value can then be entered into the IP address field. A second click to this button will retrieve the Host name. Note: This can be time-consuming. Note: User account, under which the OPC client application runs, might be different than the currently logged-on-to remote host user. Select from the list of connections that were opened Click on this button to open the Select Remote Client info from the list of connections window Figure The window opened by this button contains a list of Remote client authentication data that can be selected and used to fill corresponding fields.

Entering Remote client host information by selecting from the list of connections ensures that the authentication fields have correct values and the configuration process is sped up. Notes: If no connections have yet been accepted by SSC, the connections list is empty and the button is disabled. OK Saves changes in memory and closes the window. Note: Changes will take effect when either the OK or Apply button on the main window is selected.

Advanced settings are stored in the tunneller. Level Log level. It does not disable logging to file. Overwrite Old File If this checkbox is selected, the previous log files copy is not made. Otherwise, backup is made named as tunneller. Commit All Log File Writes If this checkbox is selected, all information written to the log file is immediately written to disk instead of being cached.

Note: To successfully communicate, the port number configured on Server-Side Component must match with the port number configured on Client-Side Component. If this option is changed, the Tunneller service must be restarted. Timeout Communication timeout in seconds. If the CSC version is 3. Retries Number of retries after communication failure. Maximum Size of Queue Maximum number of outgoing messages on the communication messages queue.

See Update of large amount of items fails in the Troubleshooting section for more details. The default value is 5. Session Timeout Used when communication failures occur. During the Session Timeout period, the connection to the end OPC server is not closed and the session stays open i. When the Client-Side Component reconnects to the Server-Side Component, that session can be reused so that recovering does not take a long time. This option should have the same value as the ReconnectTime option configured on Client-Side Component versions prior to 3.

Only One Connection If this checkbox is selected, it specifies that only one connection at a time is created to the OPC server.

Usually this checkbox should be selected. It takes effect in two cases. If a communication error occurs, then the session is waiting for reconnection for a defined session timeout period.

But, the Client- Side Component can send a request to create a new session at that time. If this option is selected, then the Server-Side first waits for disconnection from the OPC server and deletion of the previous session, and then only creates a new session. Otherwise, for a session timeout period, more than one open connection to the end OPC server can exist.

On the Windows box, only one instance of the Client-Side Component can run at the same time. In this case, multiple instances can run on the client-side and the Only One Connection checkbox must be cleared. Otherwise, OpcEnum service is used. Refer to Table 9 for those settings that can be overridden. Its value is used when processing a shutdown request from OPC server: SSC waits during this time for the current operation if there is any completion before disconnecting.

If an CSC version prior to 3. This default value can be changed by adding the ProcessingTimeout option into the tunneller. For connections from a CSC version prior to 3. The ReconnectTime option is configured in the TunnellerOpts. The default value is 0 indicating that no reconnection attempts will be performed. A connection is established and normal communication is underway.

A failure is detected either a broken link is detected or a Communication Timeout has been passed. If the SSC is still active i. Note: For versions prior to 3. In version 3. If the reconnect command succeeds i. At no time during this phase has Tunneller changed the item values, qualities, or timestamps. All alarms and events received during communication failure are buffered as long as the SSC Session Timeout has not expired and will be sent upon reconnection.

If the reconnect command fails, Tunneller CSC waits for the delay defined by the ReconnectDelay parameter default value is 10 seconds and retries a reconnection during the time period defined by the ReconnectTime parameter default value is 0 seconds.

If reconnection could not be established during ReconnectTime, or communication is established but the Server-Side Component does not have a matching session in correct state, Tunneller will start full connection attempts.

At this point, Tunneller will set all of its items qualities to bad informing the end OPC client that a failure has occurred. Any items that had their qualities set to bad will have their qualities set to good only when a new value is received for the item. If the connect command fails it will re-try the full connect command until it either succeeds or the end OPC client disconnects from the Tunnelled ProgID.

Delay between retries is defined by the ConnectDelay option. In Tunneller SSC version 3. If no connection is re-established, any session state information on the SSC will be removed after the configurable time period defined by the Session Timeout. SSC will disconnect from the end OPC server immediately after the normal disconnection of CSC, or when the session has timed out defined by the Session Timeout parameter in the tunneller.

These values are used by Tunneller when sending and receiving data on the network. Problem: Network Link is Broken If the network link is broken, the time it takes Tunneller to detect the break depends on where the link broke. If it is the local connection, the detection will be quick.

If the break occurs within the network e. The detection also depends on network usage. If the OPC client is not sending or receiving data for extended periods, Tunneller will not detect that the link is broken until communication resumes. Note that if the Use Remote Status checkbox is selected, sending and receiving data will happen at least as frequently as the OPC client calls GetStatus. The longer the timeout value, the longer failure detection will take.

A longer time also causes the responsiveness of Tunneller to go down because more time is spent testing the link. The retry value is used when the network itself has problems but the link to the SSC is maintained.

This could be because of a bad connection or interference caused by electrical equipment. If the network was unable to get the command to its destination because of a network problem, it will retry sending the command. However, many retry times are needed i. For example, adding a large number of items. CSC waits for Processing Timeout before detecting operation as failed. For example, if the remote OPC server returns an error result code for an update history call, additional attempts to update will not be made.

The result will be returned to the OPC client as is. The AddItems call can be retried, but it is configured using different option: the AddItemRetries parameter defined in the TunnellerOpts.

Problem: Timeout Expired When running under normal conditions, default timeout and retry values are acceptable. When an unusually long command is executed e. When Communication Timeout elapses, the network link will be considered failed and Tunneller will start the reconnect procedure. If reconnection is not established during the time defined by ReconnectTime parameter set in TunnellerOPts. The Processing Timeout value must be set to allow the longest expected command. The Communication Timeout can come into effect when the command being sent is very long and the network has a low ability to transfer data.

The Communication Retry Attempts parameter can come into effect when network communication is not reliable. Increasing the retry amount allows the network link to continue when otherwise it would have been considered as failed.

Note: If processing timeout occurs while running an add items request, by using the MaxAddMessage parameter configured in the TunnellerOpts. Even if the OPC client adds items by small portions so that each initial add item request does not take a long time, this option can be important if the total number of added items is considerable, when the Client-Side Component establishes reconnection to the Server-Side Component without disconnection of the OPC client.

If the connection between the Client-Side and Server-Side components is closed due to some reason e. If there is any call to the OPC server in process, it waits until it is finished while Processing Timeout is not elapsed. Disconnects from OPC server. Reconnection occurs with certain delay after disconnection, which is 10 times the ConnectDelay defined by the CSC. In most cases this delay is enough for the remote OPC server to stop and be ready to start again. If the add operation fails, a certain number of retries are performed.

If all of the retries fail, or if the items are partially added some items are added and some are not , then the CSC will not perform any more attempts.

It is recommended that you set this period to a value that is large enough to avoid eventual impact on the ongoing communication. Note: When upgrading from a version prior to 3. If the parameter is not present in the options file, it can be added manually, as follows: 1.

In the TunnellerOpts. Save the file and then restart the CSC service. Therefore, ORB requires that failover conditions be configured through watchdog tags i. The client may subscribe to and receive conditional events, but cannot acknowledge them, request a refresh, or otherwise interact with the state of a condition.

OPC DA 3. The last set of sampling rate and buffering parameters set apply to all of the clients. Also addressed here are some of the most common problems encountered, and questions asked, while using this OPC server.

This causes Pi to validate and add all tags in one group at a time rather than one tag at a time, resulting in significant improvements in time and network bandwidth used when initializing. Solution: Verify that you have a valid network connection. Verify that the timeouts are set to a length of time that will allow the longest expected communication to complete.

Often this is not set high enough causing Tunneller to keep re-trying commands. Why am I still receiving a good status from Tunneller? Solution: Tunneller is set to use its own status instead of the remote OPC servers status. Set Tunneller to use either of the remote status options.

When these are set, Tunneller will return a failed status if the end OPC server has failed or is unreachable. Solution: This can be caused by: A firewall is stopping network traffic. There is a physical disconnection between the two computers on the network.

The computer on the remote side is not powered on. The SSC is not running on the remote computer. The remote OPC server has returned a browse error. Browsing does not return anything Problem: I get nothing returned when browsing. The end OPC server does not support browsing.

A firewall is stopping network traffic. Tunneller is looking for the remote Tunneller on a port different than the one on which the remote Tunneller is configured. Solution: Tunneller does its best to limit the network traffic. When an OPC client makes the above calls, they are grouped together into one call across the network. If any one of the above calls fail in the end OPC server, it is returned as a general error in either the AddItems return code or the ValidateItems return code.

To see the specific error look in the SSC log. What is the problem? This may be especially true if you are using a low-bandwidth network connection.

Try adjusting the Processing and Communication Timeout periods or the number of retries in the Client-Side Configuration Utility for the particular connection. Disconnect and then reconnect to the server. Getting incorrect values of 0 Problem: Why am I getting incorrect values of 0 when I first add items through Tunneller? Solution: When an item is first added to Tunneller there will be at least one scan interval time where it does not have a value supplied by the end OPC server.

In this time, it may happen that the end OPC client requires an update of all the items that have been added. If this is the case, the item with the invalid value may be sent to the client. To not have Tunneller send any items that have never been updated, set the AllowInitialUpdate option in the TunnellerOpts. Fail to add items on first try Problem: Tunneller seems to fail adding items on the first try. Tunneller is often able to start faster than an OPC server.

If this is the case, Tunneller may try to add items to an OPC server that is still in the start-up process and unable to accept an add request. There are a number of ways to alleviate this situation. First, try the PostConnectDelay option in the Tunneller. Setting this value will cause a delay after connecting before any other operation can take place including adding items. The second way is configuring Tunneller to retry adding items several times if it fails.

AddItemDelay delay between two attempts in milliseconds. This will cause Tunneller to start after the end OPC server. The last option is to have an external batch file that starts the OPC server then waits an applicable amount of time before starting Tunneller. Update of large amount of items fails Problem: Tunneller fails to update a large number of DA items.

At the same time, timestamps appear to fall behind compared to a directly connected client. By default, its value is 5. When the number of messages to be sent from SSC to CSC in the queue of messages exceeds this maximum, Tunneller stores does not create new update message, but stores the latest updates for subscriptions in a cache.

Note that there is no buffering of values and each update coming from the end OPC server rewrites the previous update. When the queue allows, it forms a new update message containing the latest updates that were not sent, and sends them. The final effect will be equivalent to the reducing of the update rate. As a result some intermediate update data will be missing.

Adding multiple items causes present items to go bad Problem: When new items are added, quality for items previously added for a short period of time become bad. If its value is set to 0, then this problem will not occur. Tunneller does not work on Stratus box Problem: When switching from primary hardware to secondary hardware on a Stratus box during installation or during normal operation, Tunneller does not function properly. Solution: Re-install Tunneller using the Custom installation type and select the Installing on a Stratus system checkbox.

That will disable checking for a hardware license key and the algorithm of software licensing will be adjusted taking into account the Stratus box features. Notes: To provide correct functioning of software licensing, the generation of software license request and installation of the software license received from MatrikonOPC should be done when Stratus runs under the same active hardware configuration.

Check to see if the given client access is granted for desired OPC servers. Solution: Probably user-impersonation functionality is turned on in the Server-Side Component. Tunneller returns different set of historical data when connection to remote OPC Server is made via Tunneller and start or end time is defined as relative time Problem: If start or end data is given in relative format for a historical read request, and the connection to a remote OPC HDA server is made via Tunneller, the Read History request returns a set of data different than it would be if returned at direct connection.

Solution: The point is that time values given in relative format for example, NOW are interpreted and converted by the Tunneller Client-Side Component. Therefore, if the system time on the Client-Side and the Server-Side is not synchronized, connection via Tunneller will cause a different data set to be returned compared to that of a direct connection between the OPC client and the remote OPC server.

Solution: The cause of this problem is that the shell Upgrade the shell Note: A file named ie4shlnt. It can also be found within an install package for Microsoft Internet Explorer version 6. Note: This is applicable for ORB versions prior to 3. This can be dangerous to your computer so do so at your own risk. If it is not possible to configure the client application to such a filter, the following steps will configure the MatrikonOPC Tunneller SSC to override any subscription filter used, and disable the subscription to condition events.

Open the tunneller. Find the section marked [AlarmsAndEvents]. When no traffic is exchanged within a period of time, the SSC attempts to check the connection to the source OPC DA server, and will disconnect and reconnect to the server to rebuild all of the group subscriptions in an effort to get the requested data moving again. This is an option that can be disabled by the following steps: 1.

Open the Services control panel by choosing Run from the Start menu, and typing in services. Right-click your mouse on the entry. Select Restart from the displayed menu. Set the value to These instructions may be used to set or reset the settings manually. Licensing Most MatrikonOPC products require that some form of licensing criteria be met for it to function correctly. MatrikonOPC Tunneller supports both software and hardware licensing.

Starting with Tunneller version 3. For all new installations, software licenses will be of a different type than the ones used in previous versions. For upgrades from older versions, the existing software license will be still valid and therefore re- licensing is not required.

There is no extra charge from MatrikonOPC for calling their after-hours support number. The server supports the following locales for result code translation: US English 0x System default 0x User default 0x Neutral 0x The server allows the client to set the client name for each connection. The server supports the shutdown event notification client-side interface. Conditional events are subscribe only. The events will be received, but the Acknowledge, Refresh, State, and Condition Name browsing functions are not supported.

Data Access 3. Note: As part of the installation process, the MatrikonOPC Analyzer tool is installed and used to detect the system settings that affect the use of this software. No information is communicated back to Matrikon.

Information is stored on this system only for future use by MatrikonOPC Support to assist with troubleshooting, if required. Tunneller should be installed on all machines where the user wishes to have communication between an OPC client and an OPC server.

There are three parts to a Tunneller install: 1. Notes: Installing Tunneller may require you to restart the computer. To limit the need for a restart, please limit the activity of existing OPC products i. If a firewall is present and configured between the two computers using Tunneller to communicate, please ensure that the firewall will not block TCP communication on the desired port before continuing. In previous versions of Tunneller, a mixed installation option was available allowing an installation on a computer where Tunneller 1.

Mixed installation is no longer available. Please uninstall previous versions of Tunneller prior to installation of the current version; if not uninstalled, Tunneller 2.

To install the software: 1. Note: The Version number located in the lower left corner indicates the version number of the software that is being installed. The text X. X will be replaced with the specific product version. Click on the Next button. The License Agreement screen Figure 23 appears. Notes: From the License Agreement screen, you have the option of clicking on the Back button to return to the Welcome screen, or selecting the I reject the license agreement option.

Selecting the I reject the license agreement option button disables the Next button so your options are to return to the previous screen, cancel the install by clicking on the Cancel button, or select the I accept the license agreement option button enabling you to proceed through the install.

From this point onward, the Back button is available allowing you to return to the previous screen or screens. Read the End-User License Agreement, using the scroll bar to view the entire message. Select the I accept the license agreement option button. The Setup Type screen Figure 24 appears. Select the type of setup to be performed.

Note: Matrikon recommends that you select the Complete Setup option. The Destination Folder screen Figure 25 appears. MatrikonOPC Tunneller 3. It does away with the headaches typically associated with DCOM configuration. No longer are different protocols, security settings or locations a factor when sharing data between computers. Users are provided with more control over the security of their OPC systems. Data sent over satellite and other per-Megabyte connections can be reduced for significant cost savings.

Historical data can be compressed to a size much smaller than the original data, all without any data loss. Cross Domains and Workgroups Authentication difficulties make DCOM connections across different domains or workgroups extremely difficult or impossible. Leap past this limitation with OPC Tunneller. Essentially, if you can ping the PC, you can get to it with Tunneller. This causes considerable difficulty when communicating over satellite, modems, radio, and other bandwidth-limited communication types.