Download Center. DDE Server; Simatic S5 Retrofit; Protocol Converter (horizontal); Integration of PLC Data; DDE Server; OPC Servers; Network Diagnostics,.
Softing dataFEED OPC Suite Product code: Softing datafeed OPC suite The All-In-One Solution for OPC Communication The dataFEED OPC Suite offers a full package of components for OPC communication within a single product. It enables access to the controllers of leading manufacturers.
Additional functionality eliminates DCOM problems and improves the communication between the PLCs, OPC Servers and OPC Clients, independent of the OPC Classic or OPC Unified Architecture (UA) Standard.
Product Overview Kepware's OPC tunneling solution includes the KEPServerEX connectivity platform with the OPC UA Client driver. The OPC Unified Architecture (UA) open standard is used to provide an ideal tunnel for device communications between two instances of KEPServerEX: one instance that functions as the tunnel client and another instance that functions as the tunnel server. The OPC UA Client driver pairs with the UA Server interface of a KEPServerEX implementation to transfer data securely and reliably. The tunneling solution uses a client/server architecture for secure and reliable real-time data tunneling through firewalls and across the internet, WAN, or LAN. It also allows for easy remote communications between devices, data sources, and applications by eliminating the reliance on Microsoft COM and DCOM technology.
6.1.601.0 4/4/2017. Enhanced the UA Client tag browser to import the components of complex variables. During import, the driver automatically imports components of complex variables when their data type derives from a supported built-in type or enumeration. Enhanced browsing to allow importing all items as default data type. Escaped spaces in OPC UA URLs caused issues for certain servers when connecting with security.
Upgrading from KEPServerEX V6.0 to V6.1 requires re-issuing certificates to fix. Upgrading from V5.X to V6.1 re-issues the certificate automatically. Resolved an issue where the driver did not re-subscribe to subscriptions that had timed out. Resolved issue where the server could crash, resulting in 'Invalid or missing user information' error messages until the server was re-installed or repaired. The issue could occur if there were multiple OPC UA Client driver channels attempting to connect simultaneously. Transport layer disconnects are detected by the session watchdog, the timeout of which is now configurable. Enhanced reconnect logic to attempt to re-use sessions, subscriptions, and republish any missed data after a transport-layer disconnect.
Added support for UA Nano, Micro, and Micro Embedded UA Server profiles by eliminating the creation of monitored items for devices in 'Polled' mode. Devices in 'Polled' mode can now be configured to use registered or unregistered reads. 6.0.2107.0. Added support for Asymmetric Key Size of up to 2048 bit. Fixed an issue with connecting with a router using port forwarding. Fixed a failure to connect to a server that doesn't support certificates or password security.
Fixed an issue with the user not being prompted to trust a certificate from the Channel Properties of the UA server when attempting to connect to an untrusted server. Added notification for connected OPC DA clients when a write failed. Fixed an issue with the MLR Switch on Failure not switching back to the primary OPC server correctly.
Added a property to control whether an explicit read occurs after a write. Added German language support. Added Japanese language support.
5.21.114.0 3/20/2017. Fixed an issue where consecutive writes of the same value could result in bad tag quality. Added a property to control whether an explicit read occurs after a write. Resolved an issue where the UA Client driver did not correctly resolve internal tags like System tags. Fixed an issue where the server could crash which would result in 'Invalid or missing user information' error messages until the server was re-installed or repaired. The issue could occur if there were multiple OPC UA Client driver channels attempting to connect simultaneously. 5.18.662.0 6/23/2015.
The driver no longer creates subscriptions and monitored items for inactive tags. This allows the driver to act in a cold redundancy mode when used with the Media Level Redundancy plug-in. Increased time for UA clients to disconnect when shutting down to allow for proper shutdowns. Changed the driver to request both the server and source timestamps from the UA server.
The driver uses the source timestamp supplied by the UA server if it is available. If it is not available, the driver uses the UA server timestamp. If that is not available, the driver sets the timestamp to the current system time. Fixed an issue to allow importing a tag branch containing a tag with an unsupported data type.
Fixed an issue wherein the initial update was not passed on to client applications. Improved the browse code to report a single failure instead of multiple failures per browse request. Added support for the browseNext method, allowing clients to browse and import nodes from a server that limits the max returned nodes. Fixed a deadband issue wherein we were not correctly passing in the client item handle for the item to which deadband was applied. Removed the driver tag address limit of 1024. Fixed duplicate browse entries when performing a full refresh through the context menu in the server browser.
The driver now reports a value, quality, and timestamp for invalid tags (tags that can't be added to the remote server). Previously we would keep attempting to read the tags, expecting an initial update.
In the case that the tag is invalid we won't receive an update, and should report the tag is BAD. Fixed issue where the requested data type was not being honored when providing tag updates on monitored items. Fixed a bug where the password was not cleared in the decryption logic if the password was empty. This caused the runtime and the configuration to get out of sync with channel passwords. The performance of Auto Tag Generation has been enhanced. Fixed an issue where we fail to connect to our own UA server if we are using a username/password and no security. The client driver now places the server certificate in the rejected store if it fails to connect with security.
In the configuration we also display a message box that allows the user to trust an untrusted endpoint. Added synchronization and error checking for session read and write callbacks. It was possible to get an invalid subscription handle in the callback. The driver now removes all items from the underlying server when the UA Client's device is configured as disabled.
Fixed an issue where the UA Client Driver returned an invalid read value when an item did not receive an update from the UA Server. We now continue to process the read request until we have a valid return value.
Benefits. Easier setup and configuration than DCOM.
Firewall-friendly. Robust portfolio of client interfaces and devices. Secure and reliable data transfer using 256-bit AES message signing and encryption. Multi-threaded architecture and non-blocking asynchronous messaging for performance, scalability, and reliability. Easy troubleshooting through diagnostic tools What Is a Driver? Is more than an —it's a connectivity platform for industrial automation and IoT. Simply download KEPServerEX, and then select from Kepware's library of more than 150 device drivers, client drivers, and advanced plug-ins to fit the communication requirements unique to your industrial control system.
A driver is a software component that enables KEPServerEX to meet the connectivity requirements of a specific device, system, or other data source. The driver handles all proprietary communications to the data source for KEPServerEX; the client interfaces handle all supported OPC, proprietary, and open standards connectivity to applications that monitor or control the devices. Drivers may be licensed individually or in suites.
Additional drivers can be licensed on demand as connectivity needs evolve.